The Run Plan can be found at http://www-d0.fnal.gov/runcoor/runplans/runplan.html
The Run Plan Standard Instructions (last update: 9-May-2002) can be found at http://www-d0.fnal.gov/runcoor/runplans/runplan_standard.html
This run plan covers:
Mon 09-May-2002 23:15
Store 1305 is colliding and will be dumped at about 11:00 Friday morning.
The plan is to stack and shoot through the
weekend. Shots are planned from a pbar stack of 120 mA.
There are currently no planned accesses.
An hour of quiet time (i.e. no beam in the Tevatron) has been requested for SMT calibrations at the end of the store. Harald Fox should be paged at least one hour before the start of the quiet time (cellular 847-414-4044). Reinhard Schwienhorst should be called as well to remove L2 while the SMT calibration is taken.
We are now running the global trigger list v7.00. Snapshots of the stable trigger rates in the DAQ Monitor GUI and the Luminosity monitor should be made several times during the run for the next two stores - note on the printout the Run number, date and time, instantaneous luminosity. Collect the printouts in the binder by the DAQ console.
The Level 2 Trigger system is now part of regular operations for colliding beam. L2 personnel will be on-call. Do not hesitate to contact the L2 on-call person if there is any trouble with the L2 trigger system.
COOR should take care of crate configurations for runs that are not explicitly using L2. Old trigger configuration files should work. Contact Reinhard Schwienhorst (shwier@fnal.gov) if there are any problems about setting up configurations.
During beam studies periods, L2 will be removed from the DAQ system (except for DAQ tests) to enable faster running and to have less inteference between subsystems.
The BLM radiation dose integration thresholds have been modified. If there are still issues with constant integrated beam, contact Naeem at (630) 788-6940 or Ron Lipton.
SMT would like to take an sDAQ run approximately every 4 hours during colliding beam to monitor the noise levels. The run would take about 10 minutes. During the usual stops and restarts of runs on the 4 hour boundaries or when prescale files are changed would be a good opportunity. Contact Harald Fox if there are problems.
There have been some instabilities in the DAQ system, mostly related to reading out crates on MCH2 and possibly related to L3. Contact the L3 on-call person if there are similar problems. (see the L3 call list - http://d0onlinelx.fnal.gov/www/groups/l3daq/shifter/call_list.html).
Tests of DAQ components, especially multi-buffer VRBC readout and L2 trigger integration tests may continue at times when there is no beam and when the DAQ system is not needed for critical commissioning or calibration of detectors. Contact the Commissioning Coordinator if there are unresolved conflicts.
The SMT will run monitoring of their system with an sDAQ run during normal data taking. If there are problems with the sDAQ supervisor, see Maciej Przybycien's instructions. Notify Maciej by e-mail maciej@fnal.gov if the sDAQ runs needs to be stopped during global data taking.
See instructions for Shift Captains for improving the data taking efficiency of the experiment. Captains should start the Store Checklist as soon as the MCR announces they are in shot setup.
Captains are responsible for 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 runs and reduce HV in an orderly fashion. 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.
Stable rates into L3 of ~80 Hz have been achieved. Rate to tape
is limited to about 25 Hz. 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.
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 tests of 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 has been updated to include L2 and L3 muon filters:
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.
See the Special Run Request Binder for details
Special run forms are available in the Special Run Requests
binder in the control room.