DØ Current Daily Run Plan

The Run Plan can be found at http://www-d0.fnal.gov/runcoor/runplans/runplan.html

Updated 27-Apr-2002
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 Apr 27, 2002

Through: Eve shift Apr 29, 2002

Solenoid: Forward

Toroid: Forward

Current Situation and Plans

Sat 27-Apr-2002 18:55
Shot setup delayed for Linac quad power supply replacment. The plan is to stack and shoot until Tuesday morning when beam studies will commence. There are higher luminosity prescale files available.

Two CAMAC C335, C336 beam abort modules for downstream BLNs were replaced Friday afternoon, however we are still seeing strange readbacks. If there will be no beam in the Tevatron for two or more hours, the Captain should contact Ron Lipton and Naeem Ahmed to check the BLM electronics.

Date: Sat, 27 Apr 2002 18:28:16 -0500 (CDT)
From: Dmitri_Denisov 
Subject: BLM readings

For the last few days we are experiencing strange readings for some of
BLMs dose integration monitors. See summary from Stu Fuess during April 27
owl shift in the logbook. This is most probably instrumentation problem for
some BLMs having pedestal reading just above threshold and causing linear
increase in the dose with time. We clearly see that during shot setups
(when doses are well above threshold) BLMs are behaving well, so D0
silicon is well protected. Single BLM which is used by BD to abort
the beam C:D0BRUT is (almost) not affected by this problem. Ron Lipton
and Naeem Ahmed are working on resolving this issue.

Captains should continue monitoring D0 BLM rates and doses following
D0 SMT protection documentation and contact Ron Lipton/myself in the case
if integrated doses will get close to alarm limits.

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).

There are a number of Special Run Requests in the binder in the Control Room. Contact the experts and collect these data when there is stable beam and stable DAQ. Most runs can be performed nearer the end of the store. The special run for muons should be collected during Sat 04/27 Eve shift when Victor Abazov is on shift. Rapidity gap trigger run requires one of the FPD experts. The CFT special run requires one of the CFT experts to set up the gains before starting the run.

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.

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.

Control Room Activities

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.
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.

Standard Trigger Files

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

global_CalMuon-5.01.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. These rates to FCC should be kept low (1 Hz) unless there is good reason to push data faster.

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.