D0 Run Plan Standard Instructions

The current Beams Division schedule can be found on the web at http://www-bdnew.fnal.gov/operations/schedule/schedule.html.

Detector and Other Specific Instructions

Electronic Logbook

Silicon Microstrip Detector

Standing Instructions and Shift Tasks

The major shift tasks are:

• Keep DAQ running collecting colliding beam data. Recording must be kept ON for all runs.
• All test runs and trigger configurations must be stopped and freed before starting the global data taking run with colliding beam. CFT special runs may only start after the global run is going.
• Captains will inform the DAQ shifter when the begin store command should be issued (after scraping is complete) and when to issue the end store command.
• Include all front-end and readout crates in the data taking; experts have to be called in the case of problems.
  Detector experts should clearly indicate the status of crates on the white board in the Control Room.
• Conduct Captain and shifters' walkthroughs, fill check lists and report all problems to experts.
• Run all detectors at full voltages (beam conditions permitting).
• Monitor beam losses and silicon radiation doses.
• Help experts with short controlled accesses.
• Run all detector Examines under Detector shifter control. Report any problems to the subdetector coordinators. Until further notice the Global Examine is broken and need not be run.
• When there is no beam, calibration runs should be taken. These runs should be coordinated with the DAQ shifter.
• The offline farms will process all data in global physics runs i.e. no special shiftsets are required. If there are special runs (cosmics, halo, etc) that needs to be reprocessed on the farms, then the persons requesting the special data collection is required to fill in the shiftset request form and to send mail to d0-farms@fnal.gov.

Colliding Beam

Shot Setup

To ensure that we maximize our data collecting ability with colliding beam, here is the procedure for shot setup:

• Shot setup can last 2-3 hours sometimes. Once all the anti-protons are loaded and they are injecting protons then things are getting serious!
• Stop all calibration, test runs etc and download the global trigger file and start a non-recorded global run with all crates included. If there are DAQ or system problems you still have time to contact the DOC or experts to get things working before collisions start.
  Note that the HV on the Muon of SMT does not have to be on to run global runs.
• As soon as scraping is complete, stop the run, the SMT and Muon shifters should be notified by the Captain to raise their High Voltage and the DAQ expert should be notified to issue the begin_store command and to dowload the appropriate prescale file, and start a recorded run.
• If there are DAQ or other problems at this point, do not hesitate to contact the experts and have them come in if the problems can not be solved remotely.

At the begin of stores, the store number must be entered into COOR by the DAQ shifter via

setup d0online

store_begin number.

store_end

No Collisions (e.g. proton only or anti-proton only beam)

No Beam in the Tevatron

Standard Trigger Files

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

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

General Shifter Tasks

Silicon Radiation Monitoring

The Captain should make sure that the Silicon Radiation Monitoring is running. See the online instructions for details.
(http://d0server1.fnal.gov/users/lipton/www/radmon_shift.html)

There are some modified limits for the SMT radiation monitoring system represented on page E35 on ACNET. These limits are more representative of what the MCR actually uses for alarms and aborts. The procedures for this are being updated. See the mail below from Naaem for details:

Date: Thu, 11 Apr 2002 14:37:58 -0700 (PDT)
From: syed-naeem ahmed 
Subject: E35 Application

Hi,

I have modified and loaded the E35 application:

- it now accesses the sum trip levels from the same
devices that are set by MCR sequencer. Right now only
C:D0BRUT is set by the sequecer while the other
devices are not touched. So the shift crew is expected
to note change only in this value at the start of
store, shot setup or studies. Other variables are at
the moment set at 4-4.5krads which can be changed
manually. Changing limits on devices other than
upstream top would not affect operation and would not
even be noticed by MCR. So, unless we decide to modify
the shift procedure for MCR, these numbers will be
good for "local use" only.

- the instantaneous rate in E35 now has the new
conversion factor. It now shows the right trip
threshold  of ~12.6 R/s.

- local integrated dose alarm is still set at ~20 rads
for 1 min integration. This can be changed via
C:D0BAxy devices recently created by Paul Derwent
through any parameter page client, such as E63.
Alternatively one can change them directly in C336.

Regards,

naeem
x4250
naeema@fnal.gov

SAM Dataset Definitions

Examines and Monitoring

The default event display d0ve should be run at all times for colliding data
start_daq d0ve

Run Examines and Event displays at all times. In particular:

COOR records the begin and end of runs along with the crate configurations. DAQ shifters must still enter the relevant information in the taker pop-up windows. For details, see the message from Alan Stone. DAQ Shifter should print the L1 and L3 trigger monitor output page once per shift during colliding beam or after any major configuration change.

Captains should summarize the runs taken with colliding beam and indicate their quality:

  
 start  end  run#  trigger  #events  toroid/solenoid  crate list  data quality (good/bad/unknown)  Comments
                                      (off,for,rev)                   (CAL,CFT,CPS,MUO,SMT)