1994 1995 1996 1997 1998 1999 2000 2001 2002 <2003> 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 <2003> 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Question on waveform monitoring |
From: | Marty Kraimer <[email protected]> |
To: | "Chestnut, Ronald P." <[email protected]> |
Cc: | "'[email protected]'" <[email protected]> |
Date: | Fri, 06 Jun 2003 07:07:18 -0500 |
We have a special record to deal with digitizers, where the waveforms associated with each channel have fields with imaginative names like .ARY1, .ARY2 etc. These waveforms hold the past few pulses of Low-level RF data, and are meant to be picked up by the archiver when a trip occurs and new data are available. These internal arrays (ARY1, ARY2, etc.) are only read from the hardware (SIS or Joerger digitizers) upon a trip.
It seems that these fields are not being successfully monitored. Two stray waveforms have appeared in the archiver, but hundreds of others have not.
We could strobe these data out to traditional waveform records (and have in some cases). Data handled in this way do appear in the archiver, indicating that the monitoring worked.
Is there a way to have our cake and eat it too? Can we monitor these separate fields in the channel archiver or do we have to copy the data one more time to trigger a monitor?
/Ron Chestnut