The Run Plan can be found at http://www-d0.fnal.gov/runcoor/runplans/runplan.html
The Run Plan Standard Instructions can be found at http://www-d0.fnal.gov/runcoor/runplans/runplan_standard.html
This run plan covers:
Sun 03-Mar-2002 20:45
Store 1045 is colliding and will be dumped at 00:00. Shot setup should occur
after that.
Captains are responsible with communicating with the MCR about end of stores. The MCR will inform the D0 control room 15 minutes before the store end, so that D0 is able to end run/reduce HV orderly. As soon as we are ready, D0 Captain has to call MCR and confirm that D0 is "ready for store termination". In order to maintain clear communication with MCR the Captain should be the only shifter communicating with the MCR.
In order to be able to remove runs with problems and not lose large data samples and because luminosity conditions change over a few hours, the "size" of the global run should be dictated by:
Sustained, stable rates into L3 of 100 Hz have been achieved. Rate to tape
is limited by the online system to about 40-50 Hz maximum. Global runs
should use the prescale files established by the Trigger Meisters (TM). See the TM
instructions for more details.
If for some reason a different set of prescales is needed other than the
standard ones, the TM should be notified.
[http://www-d0.fnal.gov/runcoor/runplans/TM_instructions_11Feb02.txt]
There is an automatic process that logs the DAQ monitor information to the e-log every two hours. DAQ shifters should still be aware of the trigger rates and can use the DAQ monitor print to capture occassional snapshots. The output file for these is stored as /online/log/mon/dmp.L3_Filter_n where n = a number that is incremented. Dump the file to the printer and write the date and time and stick this into a binder. The snapshot gives the total numbers of triggers seen by L3 for the run with the rejection and acceptance.
The Alarm Watcher is now active and will be issuing alarms warning of
situations
which would have paused a run - the run-pause step has not been activated yet
but the verbal warning is issued. All alarms need to be investigated.
If a HV channel has tripped, the run should be paused and the voltage
reset. All occurences should be noted in the logbook, real and "fake".
Captains and DAQ shifters should keep careful note of alarms (in the logbook)
that are issued
and that will be displayed in the Alarm display window:
> setup d0online; start_daq alarm_display
Geoff Savage should be contacted if there are
problems with the Significant Event Server of Alarm Watcher. See further
instructions from Geoff.
By default, all crates should be included in global runs unless
experts have removed them.
Experts should be contacted if there are problems
with any of the readout crates.
Note that there have been occassional problems with L2 crates going missing.
During colliding beam operation, if problems cannot be resolved quickly by
the DAQ and detector shifters
the L2 on-shift person should be contacted immediately. If the L2 expert
cannot be reached quickly (< 10 minutes), the L2 crate(s) should be removed
from the run. The crates should only be reinstated in the global run if a
L2 expert is present AND there is a "natural break" in the run.
Any work that will be disruptive to data taking during colliding beam (e.g. DAQ system tests, L3 tests, TFW work, sDAQ etc.) must be approved by the Run Coordinator.
All work in the MCH must be done with the full knowledge and presence of the experts and can only occur during times when there is no colliding beam. No cables, configurations, crates etc should be changed without the experts' explicit approval. Also the shift captain and DAQ shifter must be kept informed of any activity in the MCH (this includes test systems for L2, L3, STT, etc.) and this work needs to be recorded in the electronic logbook, with the names of the people involved. There are logging pages available for Detector/L2 and Detector/L3.
For colliding beam, the default trigger configuration file is now:
During non-colliding beam, the zero_bias_only trigger should be run with all available crates to exercise the DAQ as long as this does not conflict with commissioning or calibration efforts. Recording should be kept off unless tests of data transfer to the Feynman Computer Center are needed. These rates to FCC should be kept low (1 Hz) unless there is good reason to push data faster.
Looper Study (Approved) - Ron Lipton/Naeem Said Requestor
See the Special Run Request Binder for details
Special run forms are available in the Special Run Requests
binder in the control room.