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
Check the updated HV instructions.
This run plan covers:
Work that causes disruption in data taking during a store or will influence the DAQ at anytime needs to be scheduled ahead of time. Detector, online and trigger groups need to send needs and requests for special running conditions and work to d0runrequests@fnal.gov. The default running condition for a store, unless otherwise specified, is to run with all available readout crates in the global run. Captains are responsible for enforcing the run plans and resolving conflicts. Contact the Run or Commissioning Coordinators if there are unresolved questions.
Requests for access should be sent to d0accessrequests@fnal.gov.
Store 641 is colliding (01:00) with initial luminosity 4.7E30. The plan is to keep this in until at least Sunday or probably Monday morning.
During collisions, the captain should run the Vertex Examine and monitor Dzero's luminosity relative to CDF. If things look bad (much worse than they were before) then please contact Gregor Geurkov (pager) and he will attempt to correct things. If things look good (much better or the same as before) then Gregor will be in during the day to finish measuring time delays.
CFT will conduct further measurements at the new SMT temperature to measure their light response. At least 100k events should be taken with both the solenoid and toroids off. If sufficient data is collected during this store, then the magnets will be turned on before the next shot. No magnets should be ramped during a store. Contact Don Lincoln or the CFT shifter if present if there are concerns that the data are not useful.
L3 VRC3c tests are mostly done and they are now running in monitoring mode mostly. The CAL crates can and should be used for normal data taking.
During normal data taking, attempts should be made to get the DAQ rate up above 6 Hz if possible. Report rates where instabilities occur.
Calorimeter has at least one triple sample run still to take of 20k events.
Other global runs may need to stop if there are problems with the L3 nodes.
Once these test runs are complete, the calorimeter should be returned
to global running.
SMT will start their timing studies with their special trigger. The SMT crates will need to stay out of the global runs for this.
Check the Standing Instructions for updated instructions on running the magnets.
Access requests should be sent to d0accessrequests@fnal.gov.
The default trigger configuration file for collisions is still
global_L1CalMuon-1.2.xml. This
trigger file emphasizes muon triggers and some high Et jet and EM triggers.
The rates should be kept in the range as indicated in the prescale file
global_L1CalMuon-1.2-4e30_6Hz.prescales but should be tuned to
a maximum data rate of about 6 Hz for now until we can get the data rate
through the Level 3 VRCs up reliably. Attempts to go above this rate should be
made. The prescale files is tuned
expecting about 4E30 so will need to be tuned to achieve the desired rate.
There is a lower luminosity trigger file also available (1E30).
Note that there is a shifter prescale file that shifters can edit so that rates
do not have to be typed in after every reconfigure of the trigger. Pay special
attention that the prescales and resulting trigger rates match the desired
bandwidths specified in the trigger file.
DAQ Shifters should set prescales to maintain the desired data rates as specified in the trigger files. Captains should check to make sure the rates make sense and are within the desired ranges. Contact the Triggermeisters or the Commissioning Coordinators if there are problems.