DØ Current Daily Run Plan

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:

From : Eve shift Feb 18, 2002

Through: Eve shift Feb 20, 2002

Toroid: Reverse

Solenoid: Forward

Current Situation and Plans

Mon 18-Feb-2002 22:45
Store 1002 colliding. Beam studies will commence Tuesday 08:00 until Thursday 06:00 when Dzero will go into Supervised Access on Thursday morning while the Beams Division repairs the Recycler. Here is the current schedule. Note that is subject to revision based on information from the Wednesday 9am meeting.

Tue 02/19 08:00	Beam studies start Reconfiguration of IP addresses by Stu Fuess for the L3 nodes will disrupt some of the pDAQ activities for a while
Wed 02/20 14:00-18:00	L3 commodity DAQ tests - no pDAQ running
Thu 02/21 06:00	Supervised Access starts
Thu 02/21 12:00	Access to cathedral
Fri 02/22 10:00	Close up of detector
Fri 02/22 16:00	Search and Secure
Fri 02/22 Eve	Shot setup

D0 shifts plan for this week:

1. Captains and DAQ shifts are 24/7. During Thursday and Friday Captains are responsible for issuing SA keys.
2. Day and evening detector shifts are ON.
3. Owl detector shifts 02/20, 02/21, 02/22 are "on call". That means that shifters have to report to shift and, if agreed by Captain and detector groups leaders, could leave providing Captain with phone(s) where they can be reached during the shift.

Control Room Activities

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:

• less then 4 hours
• less then 500k events

Muon crate 0x18 is now being read out through a SBC and not by a VBD/VRC. The Muon shifters have specific instructions on how to reset/restart the SBC if necessary. Contact the L3 on-call people if there are problems.

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 maintain highest stable running conditions within the prescales 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]

DAQ shifters should use the DAQ Monitor to print out the L3 trigger page once every 2 hours during colliding beam running. 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.

There have been communication problems between the TCC and the Luminosity Server. If the luminosity stops updating in Acnet or in the Luminoisty GUI, contact Michael Begel or the Luminoisty on-call person who needs to debug this.

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 test systems for L2, STT, etc.) and this work needs to be recorded in the electronic logbook, with the names of the people involved.

Standard Trigger Files

For colliding beam, the default trigger configuration file is now:

global_CalMuon-4.10.xml

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.

Planned Special Runs or Activities

See the Special Run Request Binder for details
Special run forms are available in the Special Run Requests binder in the control room.