From: Frank Geurts (geurts_at_rice.edu)
Date: Mon Jul 14 2003 - 18:36:10 EDT
Bill, below you can find most of my comments.
cheers,
frank
W.J. Llope wrote:
> hi tof det experts.....
>
> for the operations critique mtg on wednesday:
>
> 1. do you have any comments/complaints regarding
> the interactions between us and the shift crews
> and/or between us and TRG and/or DAQ during the
> last run?
* last year we moved much of our monitoring capabilities to Slow
Control, essentially putting them under shift crew control. I noticed
that most shift crew members were eager to learn about the system just
because it was now in the SC tree.
* in detail:
- we introduced the monitoring functions of TOFp HV, TOFr HV and TOFr gas
- we set yellow and red alerts on critical systems (esp. tof gas and
TOFr HV)
- we relocated the pVPD SC panel to the TOF branch so that the shift
crew realizes that this system is part of the TOF systems.
- nice tof-top GUI allowing single click access to the relevant systems
* operation:
- we needed some time to increase thresholds on certain yellow-alert
levels.
- the TOFrHV has an auto-ramper which automatically ramps up the HV
after a trip occured. However, for a couple of minutes yellow alert will
sound on the TOFrHV branch indicating such a recovery phase. Not sure
whether this yellow-alert should be in for the upcoming run.
- only one time red-alert on tofgas (3/19 -- Jamie's shift): quick
response by crew & detector experts, perfectly according to TOF SC
instructions. (Cause: stuck freon regulator, short peak in isob/freon
ratio triggered red-alert)
- repeated yellow-alerts (week of 3/21) on TOFr HV indicated a problem
with one of the CAEN HV units (this kind of answers my question about
the necessity of TOFr HV yellow alerts)
* TOF TCD problem (part 1, Jan '03)
- the specs of the new (pECL) TCD were not exactly the same as the old one
- time-outs on the Bira unit: unable to read the trigger command words.
- thanks to BiRa, John M. and Fred B. we were able to diagnose the
problem and after reprogramming the TCD (thanks to Dan P.) communication
between TCD and Bira was back to old specs
* L2 latency problems (early March)
- latency problems in L2 were identified by the TOF daq.
- no feedback or heads-up from the TRG group (would have helped a lot)
- TOF daq was the only local daq system that reacted to these problems
by notifying the RTS crew member, however ...
- typical response by shift crew: "Kill the messenger" :(
- after the L2-act got cleared up: no more "TOF problems"
* TOF TCD problem (part 2): 100% busy after random# events
- started after a detector access. However, no TOF activities
before,during or after this access: no hardware nor software changes.
- but, lots of TRG activity on the platform.
- Conclusion after a full diagnosis of the TOF daq and trigger
systems: most likely a loose connection on the TCD side (too many flat
cables in the back of 1A1 racks ...)
- problems dissapeared as mysteriously as they appeared: after an
access in which no changes were made to TOF but during which the TRG
group worked on the TCDs.
>
> 2. what operations-related changes to the procedures
> or detector configurations or whatever
> do you feel are necessary for run-4?
>
> please respond to this today if you can? thanks... regrds,
> bill
>
>
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:42 EDT