Current Situation and Plans

• DAQ Rates -
  • We are presently running with two additional triggers for calorimeter calibration. These triggers write to the monitor stream and may cause the monitor stream to be more than 20% of the total rate. This is acceptable. This may cause our total L3 rate to be in excess of 70 Hz.
  • The total rate for any stream should be kept below 50 Hz.
    • An exception is given for Luminosities below 40E30 where the rate in the ALL stream may go to 60 Hz.
  • If a given stream exceeds its allowed maximum rate by more than 10%, you should go up by one prescale file.
  • Anytime the L3 rate exceeds the maximum, please check for hot cells and email the triggermeisters and run coordinators.

• Any configuration change of a system needs to be approved by the Run Coordinator.

• Luminosity HV and rates: During a store, the HV of the luminosity counters will be at the normal 100% value, but while we are out of a store the HV will be ramped down to 70%. The effect of this is that if there is beam, but we are not in a store, the luminosity we will report will be approximately half. This will also affect our halo rates. You will need to know what halo values are acceptable while the luminosity system is at 70% in order to declare a store. At the moment, we are still investigating the optimum maximum values, so these numbers are somewhat arbitrary. In order to declare a store, the proton halo rate should be below 8 kHz and the antiproton halo rate should be below 4 kHz.

  When a store_begin command is issued, the HV will start ramping. As soon as as the Luminosity HV is at full, call the MCR to inform them.

• Starting a parallel run that reads out Cal crates: When a global run is in progress and a second run that reads out the Cal crates, such as a FPD special run and a L1Cal2b special run, is going to be taken, the global run must be paused first and the second run started. After the second run is started, the global run can be resumed.

• 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 Shift Captain should follow the AD Run Coordinator and MCR e-logs and call MCR as needed to keep up with the schedule of the AD. MCR may give D0 quiet time or a Controlled Access. Get approval from the run coordinator before requesting a Controlled Access or quiet time. See the white board for Controlled Access requests (ask the Run Coordinator about approved work).
• Please read the D0 Logbook before your shift in order to be better prepared.

Magnet Polarities

Magnet ramps must be approved by the Run Coordinator.

since Saturday October 22, 2005 :

   Solenoid = Reverse
   Toroid   = Forward

We will change polarities twice each month, normally when the magnets already need to be ramped down. This still requires run coordinator approval. The next change will be around 6 November and the polarity set will be:

   Solenoid = Forward
   Toroid   = Reverse

See also Magnet Operations

Trigger Configuration

Rules for Selecting Prescales: The prescale files have names with luminosity ranges. Choose the prescale file for which the luminosity at the beginning of the run is within that range. The luminosity may fall below the lower bound during the run. Unless instructed otherwise by the trigger meisters, do not start a run with an initial luminosity not inside the correct prescale set.

Available prescale sets for the above trigger are:

     00-10E30, 10-15E30, 15-20E30, 20-25E30, 25-30E30, 30-35E30, 35-40E30, 
     40-45E30, 45-50E30, 50-55E30, 55-60E30, 60-68E30, 68-76E30, 76-84E30, 
     84-92E30, 92-100E30, 100-108E30, 108-116E30, 116-124E30, 124-132E30,
     132_and_up and scraping 

   

In this configuration, we should see typical L1/L2/L3 accept rates of 300-1600/200-850/30-60 Hz, depending on the instantaneous luminosity and prescale set. If the rates are too high - L1>1700 or L2>900 or L3>60 Hz (high luminosity) or 75 Hz (low luminosity) - or the global FEB exceeds 10%: page the Triggermeister. A good effort should be made to keep the global FEB rate below 7%.

Anytime the L3 disables are above 15%, change to the next higher prescale set.

Recorded Physics Run Limit:

• default 4 hours
• or 2 hours with a prescale set that is greater than 50E30.
• or change prescale if 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

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. Calorimeter and SMT sub-detector coordinators would need to be contacted before their shifter goes on call.

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

Global Monitoring: Trigger & Physics Examines

The vertex examine runs automatically (currently on d0ol77) and the Shift Captain looks at the plots. Michiel Sanders has documented the Vertex Examine. 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.10.xml.