Subject: cross-uVax calibration veto now works!
From: Erik Katsavounidis (Erik.Katsavounidis@lngs.infn.it)
Date: Wed Jan 12 2000 - 07:39:00 EST
Hi all,
After many years left without debugging, we finally have a cross-uVax
veto scheme during calibration runs that works. The idea is to veto
all cross-uV CSPAM/FMT/HIPT triggers in a uV that takes normal
data when its adjacent uV is being calibrated; e.g., you run
calibrations in uV2, then all CSPAM23/FMT23/HIPT23 inputs to the
uV1 SPU will be vetoed. This is fundamental is being able to take
normal data in uV1 while calibrating uV2 (in this example).
Having this scheme now working, one would expect that "streamer" uV'es
(:==uV 1/2/3) not being calibrated should be included together with
the PHRASE uV'es in the traditional PHRASE-only RUNs we take while
calibrating. This means in the previous example, uV1/3/5/6 should
collect normal data in the VXMACA acq system while uV2 will collect
calibration data on the backup VSMAC1 acq system.
Unfortunately, the way the synchronization module is set up
(for uV1/2/3), the above scheme can not work.
Thus, if we want to collect normal data for any of uV1/2/3 while
one of them is being calibrated, they all have to collect data
under the same acquisition system.
Bottom line: while calibrating any uV we now have the option to
include in the same acquisition (or under the PHRASE one, if somebody
knows how to tell the sync excatly what we wanna do) the rest
of the "streamer" uV'es that can collect normal data completely
undistrurbed by the calibrations. I think this will be useful
in case we ever need redundant GC info and/or streamer tube info
for bursts etc.
All calibration runs taken today include the full detector (i.e. uV1/2/3)
where only one of them is being calibrated.
Please let me know if you object in this scheme.
A presto,
--Erik
This archive was generated by hypermail 2a24 : Wed Jan 12 2000 - 07:39:05 EST