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

The current Beams Division schedule can be found on the web.

This run plan covers:

From : Eve shift Feb 12, 2002

Through: Eve shift Feb 14, 2002 (Happy Valentine's Day!)

Toroid: On Reverse

Solenoid: On Reverse

Current Situation and Plans

Tue 12-Jan-2002 20:30
Beam studies period will last through Eve shift Wednesday 02/13. Shot setup planned for Thursday 02/14 Owl.

Shift plan:

1. Until Tuesday 02/12 evening shift: full crew.
2. Tuesday 02/12 evening and Wednesday 02/13 owl shifts: Captain and DAQ shifters must be in the control room, detector shifters could be "on call" if agreed by shift Captain and detector group leaders. Detector shifters have to come to the control room at the begining of their shift and provide Captain with phone number where they can be reached.
3. Starting from Wednesday 02/13 day shift: full crew.

d0ol07 seems to be stable for the DAQ shifters use. Server processes are still on d0ol04.
d0ol04 should remain available to the DAQ shifter for the next day or two as a backup in case d0ol07 goes down.

Problems with L3 allocating nodes should be resolved. Contact L3 personnel if problems are still seen.

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 35-40 Hz maximum. Global runs should maintain highest stable running conditions within the prescales established by the Trigger Meisters (TM). See the TM instructions below for more details. If for some reason a different set of prescales is needed other than the standard ones, the TM should be notified.

Date: Mon, 11 Feb 2002 16:04:38 -0600
From: Elizabeth Gallas 
Subject: New prescale file procedure

Dear all,

The prescale sets we have decided to use during a Run
depend on Run conditions as well as the current instantaneous
luminosity.  Sometimes we want to use the set designed for
a different luminosity. -- this is okay, as the filenames are
intended as a guideline, not a strict rule.
It is not possible for us to rename all files instantly and we depend
on DAQ shifters to communicate special instructions
from one shift to the next (and communicate to us any problems).

There are 2  triggers in every global list that are special:
min_bias and zero_bias.

zero_bias (L1 name ALiveBX - a trigger on the beam crossing signal):
the prescale should always be 3400000 regardless of luminosity.

min_bias (L1 name Afastz - a trigger on the North and South LUM counters):
the prescale should be set according to the current instantaneous luminosity
so that we record about 0.5 events per second of this type.  We have entered
the needed prescales for this trigger into files called
minbias_*E30.prescales,
where * is the luminosity factor in E30 units.
Here are the prescales we recommend:
LUM      prescale       prescale file
01E30     56000         minbias_01E30
02E30    110000         minbias_02E30
04E30    220000         minbias_04E30
06E30    340000         minbias_06E30
08E30    440000         minbias_08E30
10E30    560000         minbias_10E30
12E30    670000         minbias_12E30
...
If you use a prescale file that is named a luminosity where there is
a minbias_* file closer to the current luminosity, then
AFTER downloading that set, download the above minbias_*E30 set
which will override the min_bias prescale with the correct value.

Thanks,
Elizabeth and Levan

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.

Monitoring CDF Pot motion

The Captain should monitor the motion of the pots and the D0 losses.

Control Room Activities

Note from Geoff:

Date: Mon, 11 Feb 2002 17:11:10 -0600
From: Geoff Savage 
Subject: automatic pausing of runs

The significant event system now has the ability to automatically pause
runs when a severe condition is detected.  The actual run pausing is
handled by COOR and has not been turned on the configuration files.  You
will hear the speakers notify you that a run pause condition has been
detected and the alarm will appear in the Alarm watcher row of the alarm
display.  If the alarm condition is a glitch (i.e. it goes bad then good
so quickly it does not appear in the major column of the alarm display)
it will appear in the good column of the alarm display.

If the alarm condition persists you will hear a reminder every two
minutes.  There are two ways to eliminate the run pause alarm condition:
1. resolve the problem or 2. acknowledge the alarm in the alarm display.
Remember that an acknowledged alarm will never again say anything so
unacknowledge as soon as possible.

During shifts the shifter and captain should monitor the accuracy of the
system to see if conditions which arise need to pause a run.  Please
note any conditions that you feel should have paused a run but did not.
 This will allow the detector groups to configure their software
appropriately.

If any problems arise please email me.

Geoff

The maximum input rate into Level 3 will be dictated by stable running. By default, all crates should be included in global runs unless experts have removed them, with the exception of the CFT (see Standard Run Plan). 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.00.xml

For cosmic ray running, the default file is: cosmics-1.30.xml

For proton-only beam running: proton_halo_only-1.2.xml

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.