D0 Control Room Procedures

Questions, comments and requests should be sent to the D0 Run Coordinator
Last modified: Sun May 18 17:54:26 CDT 2003




D0 Run Plan

BLS Power Supplies

Calorimeter for Non-CAL Shifters

CFT Shifter On-Call

CFT Operations

CFT Inputs to L1 Muon

Changing Prescales

Controlled Accesses

Combined Test Stand Operations

Disable/Enable Muon Front-End

FPD Operations

FPD Procedures for Non-Experts

D0 High Voltage

L1CTT Operations

L1 Muon Trigger

Luminosity

Magnet Operations

Muon Shifter On-Call

Power Outage Recovery

Resetting Trips Due to Water Drip Detection

SCL Inits

SMT Voltage

STT Operations

TLD Badges

Training

Standard Run Procedures

The default running condition for a store - unless otherwise specified and approved by the Run Coordinator - is to run with all available readout crates in the global run with Recording On. Please review the D0 Run Plan for current plans and situations. Shift Captains are responsible for enforcing the Run Plan and resolving conflicts.

Work that influences or impacts the DAQ between stores must be scheduled in advance and approved by the Run Coordinator.

See the sections on CFT Operations & CFT Inputs to L1 Muon & Combined Test Stand Operations & STT Operations for special instructions.

CFT Operations   last updated 4 February 2003

To assist in the commissioning the CFT+PS, the following plan is in effect until further notice. When there is no colliding beam, the CFT crates are under the control of the CFT shifter.

During colliding beam:

The CFT shifter will communicate with the Shift Captain and DAQ shifter whether or not the CFT crates (0x50,0x51,0x52,0x53) should be included in the primary global run. Removal of CFT crates from the global run for reasons other then fixing immediate hardware or software problems must be approved by George Ginther or Andrew Alton. Unless explicitly approved, the default condition is to leave the crates in the global run (running in suppressed mode).

The CFT crate(s) can be excluded from the global run and CFT-only sDAQ runs may be run independently.

If independent CFT pDAQ runs or unsuppressed CFT running in the global runs are requested, the Run Coordinator must approve the run. This does not apply to sDAQ runs.

STT Operations   last updated 12 March 2003

The STT crates x70, x71, x72, x73, x74, and x75 are now part of the Crater GUI. These crates are in "NO-VBD Mode". Readout to Level 3 is not enabled in the STT crates, and L3 does not expect them to be in the readout. Moreover, the parallel cables back to the trigger Hub are not connected for these crates, meaning they cannot cause any busies or errors.

Even if the crates are powered down or in some kind of error state, they *cannot* have any impact on the global run. To support STT commissioning, crates x70 and x74 should always be part of the global run to provide trigger information. Other crates may be added upon request.

The STT group might request special runs between stores to exercise the STT system at higher L1 accept rates. These will be global runs with only a few crates in the run to reduce front end busy rates.

In case of questions, please call Georg Steinbrueck x4348 or Bill Lee x2490.

These procedures will be reviewed and/or changed when an SBC is added to the STT crate so that data is sent to L3.

Magnet Operations   last updated 13 May 2003

The Shift Captain is responsible for providing the D0 Ops Shifter with instructions on turning the D0 magnets ON/OFF or changing the polarities. The solenoid takes about 20 minutes to discharge and the toroid about 10 minutes. The shift captain should verify with the Ops Shifter that the magnet power supplies are interlocked after being ramped down. Before the solenoid or toroid are turned on or off, MCR must be notified.

During shot setup, while following the Store Checklist, the Shift Captain will check that the magnets are ON, at full current and at the correct polarity as defined in the Run Plan. The Solenoid and Toroid Power Supply displays can be found on the Ops Shifter console between the CFT and SMT Shifter consoles.

Read the current at the magnet, not at the power supply and check the polarity of both Solenoid and Toroid in the Rev. Switch box.

Any changes in magnet currents should occur when there is no store in the Tevatron. The MCR should be notified by the Shift Captain at least 10 minutes before any changes to the D0 magnet operating conditions.

The polarity of the magnets is to be changed every week. Changes are to be done before the first store that starts after the beams studies period that normally occurs on Tuesday and Wednesday of each week, and will be done independent of the amount of data collected during previous week(s) or any other conditions.

Future polarity sequences (R - Reverse, F - Forward):
Week of  5/6 5/13 5/20 5/27 6/3 6/10 6/17 6/24 7/1 7/8 7/15
Solenoid
Toroid 

Special modes of operation for the magnets (no field for detector studies, etc.) will be described on a case by case basis in the run plan. As soon as such studies are over, we should return to the sequence outlined above.

In order to reduce operating expenses, the solenoid and toroids should be powered OFF if it is known that collisions are not expected within the next 24 hours. They should be turned ON at least 1 hour before the expected shot setup.

During magnet current changes, follow the procedures outlined in the run plan for operating the luminosity counters' high voltage. No other detectors are known to be affected by the magnetic field changes.

D0 High Voltage   last updated 1 August 2002

Shift Captains are responsible for communicating to all detector shifters about the beginning of a store. The Shift Captain should specifically instruct the Muon & SMT detector shifters to set their HV to 100%. Data taking should be started after HV is at 100% for all detectors in trigger/readout.

The MCR should call D0 about planned store terminations. Near the end of a store, the Shift Captain will instruct the DAQ Shifter to end global data taking, followed by asking the Muon and SMT detector shifters to set their detector HV to "Standby". To avoid confusion, refer to the table below for which systems need to regulate their HV depending on beam conditions.

The Luminosity HV stays ON at all times, even during beam studies, but the setting of the HV to lower or higher percentages depends on the solenoidal field being off or on.

Beam conditions
  Detector    Shifter     Collisions    Injection     Beam studies    No Beam  
(Calibrations)
SMTSMT shifter 100% OFF OFF 100%
CALCAL shifter 100% at all times
ICDCAL shifter 100% at all times
MUONMUON shifter 100% Standby Standby Standby
LUM Captain 70% at all times with solenoid off
100% at all times with solenoid on

Forward Proton Detector Operations   last updated 8 December 2002

For more details and default positions, read the FPD Run Plan.

The D0 Roman pots move to standard positions for most stores not earlier than one half hour after the beginning of the store. The Shift Captain must notify MCR before any pot is moved. CDF no longer needs to be notified when we insert our pots. The pots will remain at these positions for most of the store. The pots are retracted prior to the beam being aborted or machine studies. An FPD Expert will be present for all pot insertion.

The D0 FPD information is contained on ACNET page C72.

  • Subpage 1 shows if the home limit switch is set. When the system is in standby, these should all be 1.
  • Subpage 2 shows the Linear Variable Differential Transformer (LVDT) values. When the system is in standby, these should all be fluctuating around 0. As the pots are inserted, the fluctuations become small allowing precision of at least 0.1mm.
  • Subpage 4 shows the single counting rates for each pot that is instrumented with a trigger PMT. It also shows the losses for D0 and CDF at the bottom.

The D0 Roman pot operating positions are determined by one of two things, whichever occurs first. If the singles rate at a location increases much beyond 100kHz we stop there. Otherwise, we only insert until the first indication of increased losses at CDF or a 10% increase in losses at D0 (cumulative for all inserted pots). The Shift Captain can monitor D0 losses at C:D0PHTL and C:D0AHTL.

A-side pots affect p-halo and P-side pots affect a-halo. (Dipole pots don't affect halo up to nominal positions).

CDF will be moving their forward proton pots at the end of some stores. CDF should inform D0 before they start. CDF has a similar ACNET page at S4 subpage 4. In the middle of the page, the three readouts of the Tokyo Pot LVDTs is displayed (C:TPOT1M, C:TPOT2M, C:TPOT3M). Normal CDF LVDT readings when CDF pots inserted are approximately ~-871mils for pot1, -901mils for pot2 and -854mils for pot3. The Shift Captain should watch D0 losses during the motion of CDF pots.

FPD Procedures for Non-Experts   last updated 18 May 2003

Full details on FPD Procedures for Non-Experts and Emergency Pot Removal.

FPD Expert pager numbers are posted at the FPD & CAL consoles.

To assist in the 24/7 operations of the Forward Proton Detector & collection of the FPD standalone data, the Shift Captains are trained and have been approved to perform many of the FPD tasks when an FPD Expert is not in the control room. There will be an FPD Expert on-call for day (08:00-20:00) and night (20:00-08:00) shifts to help in inserting pots and resolving any problems.

The FPD Expert will insert the pots (pot insertion will only occur between 08:00-24:00) and verify that everything is in working condition (FPDGui, DAQ, HV, alarms). The FPD Expert will:

  • Gather the pedestal file and set up the FPD DAQ to run properly
  • Determine the next run number to be used and pass this information on to the Calorimeter shifter
  • Record initial conditions in the e-log book
  • Review these instructions with the new Calorimeter shifter as they switch over

The Shift Captain tasks are:

  • To collect data and monitor rates
  • Watch for fire alarms (none have ever happened)
  • Putting the FPD system into standby (removing pots, putting HV into standby, turning off control lines) at the end of store, of if the store ends unexpectedly (for example, quench)

If the computer stops responding to the mouse or the FPDGui becomes unresponsive contact the FPD Expert to bring back up the system. If you have to remove pots while the system is in an unresponsive state, then use the Emergency line to remove the pots. Verify the pots are at home in the C72 window (window 3 of ACNET display). Click in the upper right corner where you see -<4>+ on the - until you see -<1>+. On this page all of the pots should show a value of 1 if they are home. If you click on the + you will go to -<2>+ where you should see values hovering around 0. When the pots are home, turn the Emergency Line off. To put the FPD HV on standby, open an xterm from the Calorimeter console, and then do the the following:

  • Type setup d0online
  • Type /online/config/fpd/hv/fpd.hv &
  • Follow normal instruction for putting HV into standby
  • Close the HV Gui by clicking on File then Exit

The Shift Captain must make sure the FPD system is in standby before the store ends. If anything happens that is not covered in these instructions, contact the on-call FPD Expert at any time. IF IN DOUBT, TAKE THE POTS OUT.

Luminosity   last updated 7 November 2002

During magnet current changes, follow the procedures outlined in the Run Plan for operating the luminosity counters' high voltage. No other detectors are known to be affected by the magnetic field changes.

How to tell if the Luminosity information is updating in ACNET

Comments on the lmCaptain/lmShifter GUIs:

  • lmOnline acquires information from COOR and DataLogger. The COOR record should only update when there is an end run; the DL record should update whenever a new partition is written to disk. If there is no recorded activity, then the lmOnline keys can become very late. That is one reason why they never turn red in the GUI.
  • The lmACNETGW process is not critical. If the timestamp is stale, send email to d0luminosity@fnal.gov.
  • The L3SR and L3SRRATE applications usually require a reset of the server that sends L3 information to the Luminosity DAQ and DAQ_Monitor. Since it isn't a Luminosity DAQ application, the Lumi expert should not be called. It is a standard procedure for the DAQ shifters to restart the server; it fails quite often.
    • setup d0online
    • stop_daq l3fserver
    • start_daq l3fserver

Controlled Accesses   last updated 9 January 2003

Controlled accesses are often made available during unscheduled Tevatron down time - quench, power glitch, vaccum failure - which could happen 24/7. It requires significant coordination and cooperation between MCR and D0, and between the Run Coordinator, Shift Captain, Controlled Access Coordinator and Detector Experts. A maximum of eight people are allowed inside the D0 Collision Hall at one time during a controlled access. Each access is restricted to a maximum of four hours, although most are less than an hour. In order to take full advantage of an access opportunity, we need to be prepared and organized. If you have a job that can be done during a Controlled Access, then send email to the D0 Run Coordinator with:

  • a brief description of job,
  • the level of urgency,
  • the amount of time needed to complete the job, and
  • the persons who will perform the job.
With approval from the Run Coordinator, make a note on the Controlled Access whiteboard in the D0 Control Room, with your contact info & availability.

The Shift Captain should contact the MCR at the beginning of each shift, and as needed, to keep up with the dynamic schedule of the accelerator. D0 may be able to take advantage of unscheduled downtime to make a controlled access. Contact Dmitri Denisov, the D0 Run Coordinator (or the acting Run Coordinator when Dmitri is away from the lab). for approval if there is an access opportunity. The list of Controlled Access Coordinators with their contact information is in the General Personnel Call Lists binder.

Your training must be current in order to enter the collision hall during accesses. See the section on Training for more details. Contact Bill Freeman or the D0 Run Coordinator if there are problems.

TLD badges and hard hats must be worn in the collision hall. A rate meter is also required for each location. Sandals and open-toe shoes are not appropriate footwear because of saftey concerns. Leather gloves and safety glasses may be required for some jobs.

Controlled Accesses - which we need in order to make periodic repairs and upgrades to our detector - are a privilege, not a right, extended to D0 by the Beams Division. Please be prepared, attentive and safe!

Training   last updated 23 August 2002

All shifters are required to have D0 Hazard Awareness Training [valid for 2 years] and Lock-Out Tag-Out (LOTO) I Training [valid for 100 years].

Verify your training at the ES&H Training Plans page [FNAL domain]. Enter your ID (employee or visitor) and select ITH (Individual Training History) under Option 1. The Due Date shows when your training will expire or has expired. To renew your training, simply enroll yourself in a class or challenge exam session which are usually offered weekly.

D0 Hazard Awareness handouts & quizzes are available on the web (in PDF). Copies are in the control room as well in the rack near the MCH1 door. Keep the handout, but return the quiz and the form on the last page to the appropriate slot in the rack. Send email to Bill Freeman to arrange LOTO I training.

Access to the D0 collision hall will either be Supervised or Controlled. To make any access, Radiological Worker Training [valid for 2 years] is required. Additional training - Fermilab Controlled Access Training [valid for 1 year] - is required in order to make a controlled access. It is strongly recommended that shifters get Rad Worker and Controlled Access training, and keep current, so D0 can take full advantage of all opportunites to access the detector for repairs, maintenance and upgrades.

TLD Badges   last updated 12 January 2003

Please read the Information for Temporary Badge Holders document (copies are also available in the control room), before asking the Shift Captain or Controlled Access Coordinator for a temporary TLD (thermoluminescent dosimeter) badge - they are the only ones authorized to distribute the temporary TLD badges! Please follow the Instructions for Issuing a Temporary TLD Badge.

Temporary TLD badges should be dropped in the box when:

  • the user has completed the one time access to the D0 Collision Hall, or
  • the user will not be entering a Radiation Area in the near future, or
  • the 3 month period (quarter) has ended.

If you will be at D0 for an extended period of time, and expect to enter Radiation Areas such as the D0 Collision Hall, you should fill out the permanent TLD badge form in the control room and leave the completed form in the box near the MCH1 door. Or, one can print the Permanent Badge Service Request Form from the web, and send to Dosimetry at MS119. The permanent badges (black plastic) are stored on racks near the DAB1 elevators. Every three months, the permanent badges are collected for testing and replaced with a new one. You will receive an email reminder at the end of each quarter to return your badge to the rack.

Please do not take your TLD badge off-site. The TLD badges (permanent and temporary) are used to measure the radiation exposure you receive while in Radiation Areas at Fermilab. It is a good habit to leave your TLD badge on the racks next to the elevator before you leave DAB1.

Temporary TLD badges & Permanent TLD request forms will be collected weekly and shipped to Dosimetry at MS119.

Power Outage Recovery   last updated 3 December 2002

In the event of an unscheduled power outage or interruption, please follow these procedures:

  1. DAQ, Ops and detector shifters have instructions on how to bring their systems back after a power outage. The Shift Captain should monitor their progress and help with the paging or calling of appropriate experts.
  2. Groups which want their on-call experts paged by the Shift Captain are:
    • CFT+PS
    • Luminosity
    • L1 Muon
    • FPD
    • L2
    • Online (Stu Fuess)
    • Rich Smith - restart the Hall monitors for the D0 solenoid
  3. Run Coordinator should be paged as well
  4. Other experts should to be paged or called in the case of problems only

SMT Voltage   last updated 13 August 2002

The SMT system is the only sub-detector in which damage can occur from high voltage (HV) being ON during beam losses. In the Calorimeter, ICD, Muon and Luminosity systesm - while the HV channels could trip - this will NOT damage the detectors.

The SMT shifter should not leave the control room for long periods of time (>10 minutes) while even the LV is up, especially not when the HV is up, unless there is another SMT shifter or expert to relieve him/her.

The Shift Captain MUST check with the SMT shifter that the SMT HV (and low voltage) is OFF before excusing him/her from the control room shift. The SMT shifter must also contact the SMT On-Call expert before leaving.

We require Shift Captains to be around during all shifts with beam (even if there are no collisions) due to a single reason - SMT radiation protection.

L1 CTT Operations   last updated 9 April 2003

The CFT+PS shifters and experts are allowed the opportunity to attempt to incorporate the L1 CTT crates x13 and x14 into the global run at any point between stores - even up to scraping. If the crate is made to run during that time period, then it will be allowed to remain in the global run. If the crate goes FEB, then the shifters will attempt a few well-defined steps detailed on the CTT Instructions web page. If either crate fails to behave after these steps have been taken, then it should be removed from the global run and left out until the experts have a chance to try to get it going again between stores.

The only exception is when Stefan Gruenendahl, Brigitte Vachon or Yurii Maravin is on shift. If either crate is not in the global run, and one of the L1 CTT Experts feels it is ready to be included, then during a natural pause between runs (but not a special stop just to include the crate), crate x13 and/or x14 can be added. However, if smooth data taking does not occur within 3-5 minutes, then the run will be ended to remove the offending crate until the next natural opportunity.

Combined Test Stand (CTS) Operations   last updated 4 February 2003

The Combined Test Stand (CTS) resides on the third floor of DAB, and is used to test AFEs, sequencers, sequencer controllers and the CTT.

The CTS runs can continue to be performed as SDAQ runs on an as needed basis. The person operating the CTS is required to keep the CFT+PS Shifter informed of CTS activities and the DAQ Shifter of CTS runs.

The CTS runs should have prescales set to provide L1 trigger rates of less than 50 Hz. If higher trigger rates are required, such studies should be performed between stores, and only after notifying the Shift Captain and DAQ Shifter.

Sometimes, crate x9 shows up at the DAQ Console as 100% L1 FEB, but this has no impact on the data taking, and can be ignored.

Changing Prescales   last updated 13 April 2003

There are many factors which affect the optimization of prescale sets for global running: trigger and DAQ rate capabilities, off-line farm production status, physics goals of the experiment, etc. Trigger Meisters with guidance from Trigger Board are creating/optimizing prescale sets. For trigger version 11.03 we currently have prescale sets in increments of 5E30 from 05 to 60E30 initial luminosity.

The selection rule for choosing a prescale file is rather simple: at the beginning of the global run select the prescale file with the name closest to the current D0 luminosity. Run with such prescales for a maximum of 4 hours or 500,000 events unless major hardware/software problems which affects run quality occur.

For global runs, the rate to tape is not a measure of the D0 efficiency. It could be that we are limited by L1 or L2 rates, rather then rate to tape. It is the Trigger Meisters who optimize all rates. In the case of serious problems with some of the rates you should page Trigger Meisters, rather then try to modify prescales or use higher/lower prescale files. They will help you to resolve problems, if any, or will make long term changes in the prescale files.

As of now typical ranges for the rates during global runs are (all rates are in Hz):

L1: 600-1200    L2: 300-800    L3: 30-60

BLS Power Supplies   last updated 7 November 2002

Rick Hance and Mike Cherry have prepared a safety document which details the Procedures for Changing a Calorimeter BLS Power Supply.

This procedure is for those times when Electrical/Electronics Operations personnel are not available - such as at short controlled accesses during off-hours. The urgency of replacing a BLS power supply will be determined by Nirmalya Parua (or by the Calorimeter Expert on-call when Nirmalya is away). Spare power supplies are located at the NE and SW corners of the D0 Collision Hall.

The procedure requires two physically fit, strong and healthy helpers to maneuver the heavy (50 kg) power supplies. One of the helpers should always be the Operations Tech on duty who is familar with the process. Nirmalya has provided a List of Qualified Helpers. The qualified helpers must wear leather gloves and steel-toed shoes during the maneuvering of the BLS power supply. The person(s) handling the water hoses must wear safety glasses.

If the bad BLS supply is on the north or south central platform, first notify the SMT shifter or expert to turn off their supplies (IB and sequencer). This is a preventative measure to protect against accidental power trips due to water leak detection.

Tools required: Flashlight; Phillips & Standard screwdriver; two disconnect fitting plugs for water hoses; bucket & box of Kimwipes.

CFT Inputs to L1 Muon   last updated 4 February 2003

To assist in the Central Tracking Trigger (CTT) commissioning, the DFEA outputs to L1 Muon are now incorporated into triggers which will eventually be used in the global runs on a regular basis. As a result, any changes to the status of the mixer or the DFEAs should be coordinated through the CFT+PS shifter and must be clearly documented in the logbook. Whenever possible, the LVDS links and the DFEAs should be in data taking mode prior to the start of a store.

Studies which require that the AFES, Mixer, or DFEAs to be configured in other than data taking mode should be performed between stores whenever possible.

If for some reason we are unable to put the trigger into a configuration to provide tracks to L1 Muon, then the CFT+PS shifter and the muon shifter must be clearly informed. Under those circumstances, the muon shifter must be asked to disable the CTT inputs to L1 Muon.

To help insure that the CFT inputs will not generate problems for the L1 Muon system, the following additional guidelines should be carefully followed. After a (quick or full) download of crate x50 or x52 is performed during a store:

  • Request an SCL init (to be issued by the DAQ shifter)
  • Verify the synch gap signal is correct using the DFEA Monitor
  • Inform the muon shifter of the download and request that appropriate checks of muon triggers be performed.

More details for CFT+PS Shifters on Troubleshooting & Preparation for Store

For the Muon Shifter, a problem with the CFT inputs might present itself in the following ways:

  • AND/OR terms 193 and 194 (the "beginning of turn" triggers) in the DAQ Monitor have values other than 47712 Hz.
  • The L1 Muon crates (0x16, 0x17, 0x18) go "Out of Synch" and do not recover after the DAQ Shifter issues an SCL init.
  • The L3 input rate drops suddenly and stays low.

If the Muon Shifter sees a problem, then:

  • Check with the CFT+PS Shifter to see if there is a CFT-related problem. If so, let the CFT+PS Shifter attempt to recover and, after the DAQ Shifter issues an SCL init, check the above conditions again.
  • If the problem persists, request that the run be paused, and then disable the CFT inputs using the GUI. An illustrated guide is in the L1 Muon Documentation binder, or click on Disabling CFT Inputs to L1 Muon.
  • After disabling inputs, ask the DAQ Shifter to issue an SCL init. The AND/OR terms 192 and 193 should both be 47712 Hz. If so, request that the run be resumed. If not, page the L1 Muon expert!

In the case where something goes wrong, the system is returned to the configuration with no CFT inputs enabled to L1 Muon, and the L1 Muon expert will study the problem between stores.

CFT Shifter On-Call   last updated 15 May 2003

Please note: If one of the CFT+PS crates exhibits 100% L1 FEB which cannot be cleared by an SCL init, then either summon the on-call Shifter to the control room (consultation by phone is not sufficient) to address the issue(s), or, if necessary, exclude the offending crate(s) from the global run under non-critical conditions (no shot setup for hours).

During extended periods without colliding beams, the Shift Captain might explore the option of releasing the CFT+PS shifter to "on call" status. If you are the CFT+PS shifter and the captain offers you this option, you may exercise this on-call option under the following conditions:

  1. There are no outstanding special instructions regarding tasks which should be accomplished by the CFT+PS shifter.
  2. Before leaving the control room you must perform the following operations:
    1. Perform a standard round of checklist checks to insure that the CFT+PS system is in good condition. If it is not, then clearly document the problems observed and consult with an expert as necessary.
    2. Verify that there are no unaddressed major CFT+PS alarms.
    3. Check that all CFT+PS crates are capable of being readout in the zero_bias run (unless specifically removed from running by experts).
    4. Document the CFT+PS status in the logbook.
    5. Provide shift Captain with phone number where you could be reached if CFT+PS problems arise during the remainder of your shift, and post that number at the CFT+PS console.
    6. Be sure to contact the next CFT+PS shifter at the appropriate shift transition time to address any questions the next shifter may have.

If you are coming on shift following an on-call shift, be sure to carefully review the status of the system to insure that it is in proper operating condition.

L1 Muon Trigger   last updated 16 October 2002

To assist in the commissioning the L1 Muon trigger, the following plan is in effect during colliding beam, until further notice:

From time to time, the L1 Muon team (Rob McCroskey, Ken Johns, Jeff Temple or Stefan Anderson) will have new logic for their trigger manager which is designed to add new terms for triggering. They can check most of the terms with no beam, but they need to do a final check during a store.

This work will be performed at the end of the store. When new logic is ready, the L1 Muon Expert will request a page from the Shift Captain about 1-2 hours before the scheduled termination of a store. The logic change should be performed in the last hour of the store. The total time to change logic and record rates is about 10 minutes. If there is a problem with the new logic, it takes about 10 minutes to change back to the old logic.

Muon Shifter On-Call   last updated 11 December 2002

In the case of long periods of no colliding beams, the Shift Captain might release the muon shifter to on-call status. Before the muon shifter leaves the control room:

  1. Be sure that the HV on all muon detectors is set to Standby and locked. Document the HV status in the e-log.
  2. Check that there are no major muon alarms. Document this check in the e-log.
  3. Check that all muon crates can be readout in the zero bias run (unless specifically removed from the run by experts). Document this check in the e-log.
  4. Provide the Shift Captain with a phone number where you can be reached if there is a problem with the muon system during the remainder of your shift.

Calorimeter for Non-CAL Shifters   last updated 31 December 2002

Nirmalya Parua has written a four page PDF with basic calorimeter instructions for Shift Captains and DAQ Shifters for the times or shifts when there is no Calorimeter Shifter in the D0 Control Room. It is also available in [PPT].


There will be periods, particularly on owl shifts with no beam or chance of beam, when the Calorimeter Shifter is on-call and not in the Control Room. By default the Calorimeter crates are left in the global zero-bias run, but on occasion one of the CAL crates (x40-x4b) will assert 100% L1 FEB, such that data taking has stopped.

Solution:

  1. DAQ Shifter should pause the run
  2. Go to the CAL console, screen 1 (on right), Supply GUI, Mode Shift tab
  3. Click on 'Global T&C Reset'
  4. Click on 'Global ADC Reset'
  5. Click on 'Global T&C Reset' again
  6. DAQ Shifter should issue an SCLinit
  7. DAQ Shifter should resume run

If for some reason the 'Supply GUI' is not open, you can do:

setup d0online
/online/config/cal/supplies/supply_all &

in order to complete Step 2 above.

Issuing SCL Inits   last updated 12 January 2003

Only the DAQ Shifter should issue the manual SCL inits during global physics data taking:
  • To clear Muon Readout errors (PDT,MDT,etc.)
  • Before resuming a run after a Calorimeter ADC error
  • Before resuming a run after a CFT+PS download
  • To clear L1 CTT FEB (with approval from CFT shifter)
  • Before resuming a run after an SMT download
All shifters should clearly communicate requests for Pauses and SCL inits with the DAQ Shifter, and vice versa!

Resetting Trips Due To Water Drip Detection   last updated 22 January 2003

In many D0 systems, water is used to cool down the electronics. We do have a protection system which turns off water to the affected area(s) in the case of a water leak detection. This system works reliably - most of the alarms were caused by a real water leak. In the past we have had cases when the control room shifters were trying to reset water drip alarms multiple times without investigating the problem. As a result, every time the alarm was reset, water valves were opened and even more water leaked. Water can be very seriously damage the detectors and electronics.

Based on experience accumulated over the last 2 years of operations, we have developed rules for handling water related alarms. Please read and follow them from now on.

  1. The rules cover water drip and water flow trips both in MCH and in the D0 Collision Hall.
  2. In the case of a water related trip, the shifter responsible for the affected sub-system should NOT reset it, rather:
    • Call the Ops shifter who will document the trip in the logbook, check the level of the water in the cooling system and investigate reason(s) for the trip in the MCH or Collision Hall (if latter is accessible)
    • Inform detector group leader(s).
  3. If the leak is in the MCH, the Ops shifter will investigate the area affected and, if no water is found, could proceed with resetting the trip condition. If in the same area a trip will occur within 12 hours, the Ops shifter has to call the D0 Mechanical Operations Leader. Only after his/her approval and development of a specific plan of handling the situation should the trip be reset.
  4. If the leak is in the D0 Collision Hall and the hall is accessible (shutdown), the Ops shifter should proceed according to Item 3 above. If the hall is not accessible (collider operation), the detector group leader in consultation with the Ops shifter can instruct the detector shifter(s) to reset the trip. If a second trip occurs within 12 hours, the Run Coordinator has to approve further attempts to reset a trip after a detailed plan of handling each specific case is developed.

In summary: control room shifters should NOT reset water trips without consultation with both the Ops shifter and the detector group leader(s). If the same water trip repeats within less than 12 hours, the D0 Mechanical Operations Leaders and/or Run Coordinator must approve resetting a trip condition.

Disable/Enable Muon Front-End

  last updated 5 May 2003

This message is just to serve as a quick reminder for muon shifters (and an update for Shift Captains/DAQ Shifters) on who you need to contact when you disable/enable a muon front end with the readout_client gui.

  1. If you have a problem with a front end, contact the subsystem expert before disabling the front end! It is the subsystem expert who should make the decision to disable (or enable) the front end.
  2. Once the decision has been made to disable the front end, the front end must also be disabled at level 1. You DO NOT need to call the L1 Muon expert for this. You can disable the front end by running the l1muon_inputs.py gui (in /projects/l1muo/vme_gui).
    There is documentation on how to run the gui.
  3. Finally, the front end must also be disabled at level 2. The L2 expert must be called to do this.

General Information

General Information