Current Situation and Plans

• Run Plan is "stack and store". Collect quality data with the full detector in readout. Commissioning activities should occur between stores, unless approved by the run coordinator. Between stores, collect zero-bias data with as much of the detector as possible.
• The trigger list to run is 12.37

• Prescale sets:
  
  1. The rule: "use the prescale set closest to the luminosity at the beginning of the run".
  2. See below for the list of available prescale sets. The 'Emergency' prescale set has been replaced with '64E30' and '75E30' prescale sets.
  3. See below for the instantaneous luminosity dependent run limits which have been optimized with prescale sets because the luminosity is dropping quickly at the beginning of the store.

• Procedure in the case of rescraping and beam loss tuning by MCR:
  1. To tune losses for CDF, MCR usually does one or more of the following:
     • Change tunes and chromaticities
     • Move indidividual collimators, typically E03 (H&V) and/or D173 (H&V)
     This should not have any impact on D0 data taking. If MCR calls and announces one of the above, keep taking data with SMT and Muon HV up. Watch our halo rates carefully until MCR has finished.
  2. If MCR announces a full rescrape, end the run, put the detector to standby, and end the store. Begin with the same store number again once the recraping is completed. This is the usual rescraping procedure as before. In particular, the DAQ shifter should issue corresponding store_end and store_begin commands; for the luminosity accounting it is perfectly OK to fragment a single store into separate time periods.
  3. If MCR announces anything not falling into the above two categories, remember that protecting the detector has priority. Put SMT & Muon to standby if in doubt, and/or call the run coordinator.
  4. FPD: as a basic (new) rule, the FPD will stay ON when SMT and Muons stay on. Refer to the FPD instructions for details, or ask an FPD on-call person.
• The Shift Captain should follow the MCR e-log and call MCR as needed to keep up with the schedule of the AD. MCR may give D0 quiet time or a Controlled Access. Page the run coordinator for Controlled Access approval. See the white board for Controlled Access requests.
• Please read the D0 Logbook before your shift in order to be better prepared.

Magnet Polarities

from Tuesday June 22, 8:00:

   Solenoid = Reverse
   Toroid   = Reverse

from Tuesday June 29, 8:00:

   Solenoid = Reverse
   Toroid   = Forward

from Tuesday July 6, 8:00:

   Solenoid = Forward
   Toroid   = Forward

See also Magnet Operations

Trigger Configuration

Rules for Changing Prescales: choose the prescale set which has a name closest to the luminosity at the start of the run.

Available prescale sets for the above trigger are:

   02E30, 05E30, 08E30, 10E30, 13E30, 17E30, 20E30, 25E30,
   28E30, 35E30, 40E30, 45E30, 48E30, 55E30, 64E30, 75E30, and scraping.

In this configuration, we see typical L1/L2/L3 accept rates of 600-1400/300-850/30-60 Hz, depending on the instantaneous luminosity and prescale set. If the rates are too high - L1>1500 or L2>900 or L3>65 Hz - or the global FEB exceeds 10%: contact the Triggermeister. A good effort should be made to keep the average global FEB rate below 6%.

Recorded Physics Run Limit:

• default 4 hours
• or if the prescale is '75E30': until the lumi falls below 69E30, but at least 1 hour
• or if the prescale is '64E30': until the lumi falls below 60E30, but at least 1 hour
• or 2 hours with prescale 45E30, 48E30 and 55E30
• or when the instantaneous rate in the Taker is < 25 Hz

The DØ Shift Schedule (D0 Shift Calendar)

Other shifters can be on-call:

1. if there is no Store,
2. if MCR states there is no shot setup expected for 4 or more hours,
3. if the situation with the sub-detector is stable,
4. if there are no sub-detector tasks to perform (checklist, calibration, special runs, monitoring), and
5. if the Shift Captain is in agreement

Calorimeter, Muon and CFT Shifters do not need confirmation from their sub-detector coordinators. However, there are Special Instructions for Muon Shifters and Special Instructions for CFT/CPS/FPS Shifters which must be followed before leaving.

Shifters must report in with the Shift Captain to give a contact number before leaving.

Global Monitoring: Trigger & Physics Examines

The name of an institution will be listed next to the GM shifter when the Global Monitoring shift is being run remotely. There is a GM Web Communicator GUI to be used by the Shift Captain, remote GM Shifter, and other shifters as needed. The interface is very simple; shifters communicate via typed text. The gui should be open by default on the Captain console. If not, the gui can be launched with the following command sequence: setup d0online; start_daq gmwebcom.

The Shift Captain is running the vertex examine (currently on d0ol27). Michiel Sanders has documented the Vertex Examine Instructions (pdf and html). For reference, look at the VE plots entered in the logbook during previous shifts.

Periods Without a Shot Setup or Colliding Beams

By default, 'Recording' should be ON as we would like to monitor the full data path from the detectors to tape at the Feynman Computing Center.

There are three trigger bits with prescales which have been tuned both to exercise the L1, L2 and L3 rates and to send an average of 1 Hz to tape, and a low rate L3 mark and pass trigger that writes to the monitor stream. The prescales should only be changed by or with approval of the triggermeisters.

If there is a request for cosmic ray data: the default cosmics trigger list is official/special/cosmics-3.00.xml. If the CTT is available, official/special/cosmics_trk-1.00.xml can also be used.