DØ Control Room Procedures  

D0 Run Plan	Contacting servicedesk	Acnet to Elog	Rescraping	BLS Power Supplies	Calorimeter for Non-CAL Shifters	TRK shifter On-Call	CFT Operations	Changing Prescales
Controlled Accesses	Combined Test Stand Operations	Countdown Timer	Disable/Enable Muon Front-End	FPD Operations	FPD Procedures for Non-Experts	Halo Rates	D0 High Voltage	L1CTT Inputs to L1 Muon
Luminosity	Magnet Operations	Muon Shifter On-Call	Power Outage Recovery	RADMON Alarm Instructions	Recovery from Online Database Disruption	Resetting the NIKHEF Hall Probes	Resetting Trips Due to Water Drip Detection	SCL Inits
SMT Voltage	Standard Acnet Plots	STT Operations	TLD Badges	Training	Vertex Examine	Importing pictures

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. During colliding beam: Each detector shifter will communicate with the Shift Captain and DAQ shifter whether or not the crates should be included in the primary global run. Removal of any crates from the global run for reasons other then fixing immediate hardware or software problems must be approved by the the appropriate detector expert. Unless explicitly approved, the default condition is to leave the crates in the global run. 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 & L1CTT Inputs to L1 Muon & Combined Test Stand Operations & STT Operations for special instructions.

Contacting servicedesk   last updated 30 March 2010 There are several portions of the online system where we will have to contact the servicedesk to get problems solved. These are problems dealing with online Linux system administration, the database administration, and the network. Note that in general, D0 should be able to handle any single node failure, so you should not need the service desk. If you are unsure if you should contact service desk, you should contact a D0 Online expert (Bill, Geoff, or Stu) first. During normal business hours, 8:30-4:30, you reach the servicedesk by calling x2345 and explaining the problem. For online Linux system administration, you should say that you need the ticket assigned to the FEF group. If you are not sure which group you should contact, you can just describe the problem and/or node, or contact a D0 online expert to help direct the request. Outside of business hours, for online Linux system administration you may use this web page for 24/7 issues. For the online system, 24/7 issues are those that are affecting data taking and require an administrator to fix. You will need to use your services account to login. If you have problems with the web page, you will need to still call x2345. You will be routed to a voice mailbox which will then page the servicedesk to call you. When filling out the web page or calling the service desk, make sure that you leave the control room number as the contact number. In most cases, we should not need to contact the servicedesk after hours. If a single node goes down, we should move to another node. If an application dies we should restart it. We should contact servicedesk if a cluster goes down, for file access problems, or more global online problems. If you are in doubt, you should contact the D0 online expert or run coordinator. You can also send email to d0onlineexpert@fnal.gov if the issue is not urgent. Note that the DAQ back end is now being supported by the D0 Online group. If there are urgent problems with the back end, you should contact Bill Lee, Stu Fuess, or Geoff Savage.

Procedure for putting acnet plots in the elog   last updated 18 August 2008 From /mnt/www/htdocs/groups/cap/instructions/how-to-insert-plots-into-logbook.txt. Go to the Lumberjack Datalogger (section D44 on ACNET). Select 'Pgm_Tools' in the upper right corner. Select 'Screen Copy' from the pull-down menu. Select 'Copies' from the pull-down menu (2 sub-menus should will open). Select the window you want to copy: Click on 'Copy From< (window you want to copy) >'. A sub-menu will open. Select the title of the window you want to copy from this list, e.g. "GxPA 1:D0 Store Luminosity" Click on 'To < (this is where you want to copy to) >'. Select 'Save to GIF' from the pull-down menu. Click on 'Title' and edit it if you wish to do so. Note that this is the title that you will find on the web (see below). Click on 'Directory'. A pull-down menu opens. You will have to locate the following directory from the list: '/usr/local/userb/pic/capture/dzero'. Use the scroll-bar on the right side of the pull-down menu to browse through the list. Once you have found it in the list, click on the directory and select 'OK'. Set invert image colors to yes (if so desired). Select '>>Copy<<'. The window you want to copy will briefly shift around on the screen. At this point you are done at the ACNET console. Move over to continue on d0ol108. Go to the electronic logbook. Drag the 'Text' button into the logbook entry area. Select 'Insert'. A pull-down menu opens. Go to 'Image' and select 'From a URL'. A dialog window opens into which you have to paste the URL of your picture. Open the 'Runplan' website on the web browser. Select 'DZero ACNET' from the menu on the left (http://www-bd.fnal.gov/userb/pic/capture/dzero/). Click on 'Last modified' until the list is sorted by date, with the most recent file on top of the list. That's the file you want to paste into the electronic logbook! Click on the file name. Copy the URL from the browser into the dialog window of the electronic logbook, and click 'OK'. You deserve a break!

Procedure in the case of rescraping and beam loss tuning by MCR   last updated 28 January 2008 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) Clean the abort gap using the TEL. 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. If MCR announces a full rescrape or some other period where their activity will be destructive to the beam, end the run, end the store, and put the detector to standby. If time permits, MCR should wait for us to inform that our detector is in standby. If requested, we can keep the Luminosity HV at full. While we are out of store, we should take a non-recorded run using the Global trigger list. Once the recraping is completed,and MCR calls to inform us that the beam is stable, Ramp the detector to full and then begin with the same store number again. 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. If MCR announces anything not falling into the above two categories, remember that protecting the detector has priority. End the store, and put SMT & Muon to standby if in doubt, and/or call the run coordinator.

CFT Operations   last updated 3 January 2010 When there is no colliding beam, the CFT crates are under the control of the TRK shifter.

STT Operations   last updated 3 January 2010 The 6 STT crates (x70-x75) are regularly part of the global run. These crates get inputs from the CTT and SMT and are monitored by the TRK shifter. In case of problems that cannot be solved by the TRK shifter, the STT primary (and then secondary) experts should be paged. The pager numbers along with phone numbers are posted at the SMT/STT console and on the STT Operations web-page. In case of questions, please contact Junjie Zhu, x4097 (junjie@fnal.gov).

Magnet Operations   last updated 30 August 2011 (SG) When necessary 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 locked out 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 to the left of the TRK Shifter console. 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. Ask the Run Coordinator before any change. The MCR should be notified by the Shift Captain at least 10 minutes before any changes to the D0 magnet operating conditions. The magnet polarity set will be changed twice per month. The solenoid polarity will flip once per month normally in the first week of the month, but this flip may be advanced or delayed by a week if there is some other impending need to power down the solenoid. The toroid may change with the solenoid and will change in the middle of the month. Future polarity sequences (R - Reverse, F - Forward) are given in the following table: Date changed  5/19 6/18 7/1 8/21 9/7 9/24 10/7 10/25 11/9 11/23 12/8 12/21 1/14 2/3 2/18 3/10 3/29 4/13 5/1 5/16 5/28 6/17 6/30 7/13 7/28 8/29 9/13 Solenoid R  F  F  R  R  F  F  R  R  F  F  R  R  F  F  F  R  F  F  R  R  F  F  R  R  F  F  R  Toroid R  F  R  R  F  R  F  F  R  F  R  R  F  R  F  R  R  F  R  F  R  F  R  F  R  F  R  F  # days 30  13  17  17  17  13  18  15  14  15  13  12  20  15  20  19  15  18  15  12  20  13  13  15  32  15      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 toroid should be powered OFF if it is known that collisions are not expected within the next 24 hours. Do not ramp down the solenoid. The toroid 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. If the solenoid polarity changes, the TRK shifter should be told in order to download new Lookup tables to the STT. No other detectors are known to be affected by the magnetic field changes.

D0 High Voltage   last updated 3 January 2010 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, as well as to the store state. It is the captains responsibility to change the Luminosity HV based on the solenoidal field, comics will automatically ramp for changes in store. Beam conditions   Detector     Shifter     Collisions     Injection     Beam studies     No Beam   (Calibrations) SMT TRK shifter 100% OFF OFF 100% CAL CAL shifter 100% at all times ICD CAL shifter 100% at all times MUON MUON shifter 100% Standby Standby Standby LUM Captain 70% when solenoid off, or when there is not a store declared. 100% when solenoid on and in a store

Forward Proton Detector Operations   last updated 9 June 2009 The forward proton detector is not in use anymore.

FPD Procedures for Non-Experts   last updated 6 May 2005 removed 9 June 2009 - FPD is not in use anymore. -(SG)

Halo Rates   last updated 6 May 2010 Having the luminosity at 70% prior to declaring the store will keep the halo rates at a lower than normal value until the store is declared. In order to declare a store, the proton halo rate at 70% HV should be below 30 kHz and the antiproton halo rate should be below 15 kHz. If the rates at 70% HV are above 15 kHz (proton)/ 8 kHz (antiproton), notify the MCR, but do not delay data taking.

Luminosity   last updated 6 May 2010 The luminosity HV should be at 100% if the solenoid is fully energized/stable AND if we are in store. ? If the solenoid current is changing, the luminosity HV should be ramped to 0% as a precaution. ? In most other situations the HV will be set to 70%. ? These changes are supposed to happen automatically, but it is the captain's responsibility to check. Please see the instructions for the luminosity HV for the operating procedures. Note:? The Captain is responsible for ramping the luminosity HV back up after the solenoid ramps down or up!?

Controlled Accesses   last updated 22 March 2005 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 the D0 Run Coordinator 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 Eric McHugh or the D0 Run Coordinator if there are problems. A Controlled Access must be performed by a team. A team goes into the collision hall and a team comes out from the collision hall. A single person can not be left in the collision hall for safety reasons. 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 safety 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 17 February 2006 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]. LOTO1 is being replaced by Electrical Safety Orientation, so either of these are valid. 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. Copies are 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. To renew D0 Hazard Awareness, you can also take the online quiz available here. Send email to Eric McHugh 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 22 March 2005 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. The web page for issuing Temporary TLD Badges can be found here. 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: 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. Groups which want their on-call experts paged by the Shift Captain are: CFT+PS Luminosity L1 Muon FPD L2 Online (Bill Lee) Rich Smith - restart the Hall monitors for the D0 solenoid Run Coordinator should be paged as well Other experts should to be paged or called in the case of problems only

RADMON Alarm Instructions   last updated 17 May 2010 Purpose: The D0 SMT Radmon system is designed to protect the Dzero silicon tracker from excessive accelerator-induced radiation damage. It monitors momentary and time-integrated radiation levels and automatically issues alarms and beam aborts. Interfaces: The shift captain uses a dedicated ACNET application to track radiation levels in the vicinity of the SMT. Alarm buzzers and a push button interface for alarm silencing and for abort reset are located in the console to the left of the tracking shifter. Only the D?Run Coordinator (or designee) can authorize the reset of the SMT Abort. Do not push the 'Abort Acknowledge' button unless instructed to do so by the Run Coordinator. Procedures: Complete instructions can be found at http://d0server1.fnal.gov/Projects/UpgradeProject/Run_II_Procedures/D0-OP-SMT-010.pdf . Instruction summary: If a RADMON alarm goes off, the shift captain, with the help of the tracking shifter, shall collect the relevant information, post it in the electronic logbook and inform via pager the SMT Radmon experts and via email the Dzero Run Coordinator (d0rc@fnal.gov). Silence the alarm buzzer at your convenience. If a RADMON abort is issued, the shift captain, with the help of the tracking shifter, shall collect the relevant information, post it in the electronic logbook and immediately page the SMT Radmon expert on duty and the Dzero Run Coordinator. Only the D?Run Coordinator (or designee) can authorize the reset of the SMT Abort. Do not push the 'Abort Acknowledge' button unless instructed to do so by the Run Coordinator. ACNET posting: To make the R/s plot: On the D44 acnet page choose recall and select "SMTDOSE SEC" set T1 and T2 to cover the relevant time period (e.g. the squeeze), for example T1 = 13:00:00 and T2 = 13:04:00 click on one of the variables to make the plot If the values go off the top of the plot, change the upper limits from 1.5 to the appropriate value click on one of the variables to make the plot now you can save this plot To make the R/min plot recall and select "SMTDOSE MIN" T1,T2 are the same as before click on one of the variables to make the plot

Recovery from Online Database disruption   last updated 3 January 2010 After completion of any work on online database, or after any disruption in the work of online database, ask TRK shifter to restart cft_gui.

SMT Voltage   last updated 3 January 2010 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 TRK 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 TRK shifter or expert to relieve him/her. The Shift Captain MUST check with the TRK shifter that the SMT HV (and low voltage) is OFF before excusing him/her from the control room shift. The TRK 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.

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.

Countdown Timer for End of Store   last updated 31 January 2011 Use start_daq countdown to bring up the countdown timer.

Changing Prescales   last updated 20 July 2004 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. The current trigger list and prescales can be found in the Run Plan. We have run durations optimized for the for the instantaneous luminosity profile in a store. The run duration limits can also be found in the Run Plan. 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. Do always use the prescale sets as per Run Plan. 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.

BLS Power Supplies   last updated 3 January 2010 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 TRK shifter or expert to turn off the SMT 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.

L1CTT Inputs to L1 Muon   last updated 3 January 2010 If problems are noticed in L1Muon, ask both the CAL/Muon and TRK shifters to check their respective subsystem. The L1CTT sends track information to the L1Muon and therefore both systems are coupled.

TRK shifter On-Call   last updated 3 January 2010 If any CFT major alarms occurs while the TRK shifter is on-call, summon the on-call shifter to the control room (consultation by phone is not sufficient) to address the issue. If for any reason the TRK shifter is unable to personally return to the control room within minutes, page the CFT on-call expert.

Muon Shifter On-Call   last updated 19 December 2003 In the case of long periods of no colliding beams, the Shift Captain might release the shifter responsible for the muon system (the CALMUON shifter) to on-call status. Before the shifter leaves the control room: Be sure that the HV on all muon detectors is set to Standby and locked. Document the HV status in the e-log. Check that there are no major muon alarms. Document this check in the e-log. 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. 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 22 July 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: DAQ Shifter should pause the run Go to the CAL console, screen 1 (on right), Supply GUI, Mode Shift tab Click on 'Global T&C Reset' Click on 'Global ADC Reset' Click on 'Global T&C Reset' again DAQ Shifter should issue an SCLinit 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 3 January 2010 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 TRK 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 the NIKHEF Hall Probes   last updated 13 January 2004 Once an hour the NIKHEF hall probes between the CFT and the Solenoid and on the faces of the Central Calorimeter are read out and logged to the D0 online production database. On rare occasions the readout system crashes. Experience has shown that most often simply cycling the power to the hall probes enables the readout system to reawaken and proceed normally. The Shift Captain may be requested by a member of the Hall Probe team (Paul Balm, Pieter Houben, Rich Smith, Gene Fisk) to cycle the power to the hall probe system. This is accomplished by walking to rack M214 (2nd floor MCH, far end, N side), locating the lowest panel in the rack (gold anodized, labeled "Power Supply Nikhef Hall Probes"), noting a green LED and switch on the right end of the panel, moving the switch from "Bypass/On" to "Remote/Off", then verifying that the gray cable (emerging from the rack just above the panel) with metallic connector body is properly plugged into the port marked "Cannode 2" on the panel, waiting 15 seconds, then moving the switch handle to "Bypass/On" once again.

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. The rules cover water drip and water flow trips both in MCH and in the D0 Collision Hall. 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). 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. 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 16 July 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. 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. 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. The L2 input configuration file is automatically updated when the input is disabled in the muon GUI. To make the change active, the DAQ shifter should re-initialize COOR and then start the global run. At this point the input configuration in the L2 crate is updated. Starting the run will fail with a timeout while the SLIC cards in the L2 muon crates are downloading their new configuration. After this, the run can be started properly and the L2 dataflow GUI will show the corresponding SLIC input as a gray box. The L2 expert does not need to be contacted.

Standard Acnet Plots   last updated 24 October 2005 There are two sets of ACNET plots that captains should place in the logbook during their shift. If there is beam during the shift, ple3ase make a summary plot of the shift. This can be done a half hour before the end of the shift. From the 'D0 STORE II' page, plot D0PHTL, D0AHTL, and D0FLTL. If there is a shot setup during the shift, after things have calmed down, put the following three plots in the logbook: "SMT DOSE SUM" page. A good choice for the upper bound would be 50-100. Choose the time frame from when the rates started to rise to just after when the values were reset to zero. "SMT DOSE SEC" page. Here a good choice for the upper bound would be 0.5-1.0. "SMT DOSE MIN" page. If v:CLDRST does not work, just comment it out. If you do not know how to put plots in the logbook, consult the vade mecum, or talk to another captain. Please make sure that you invert the image.

Vertex Examine and Beam Spot Monitor Shift Instructions   last updated March 2nd, 2009 The vertex examine and the BeamSpotMonitor monitor the tracking performance and the beamposition at DØ. Detailed instructions can be found here. The BeamSpotMonitor takes care of running the vertex examine during physics runs in a store, and it actively monitors the beamposition. It also transfers the beamposition values to COOR, from where they get downloaded to L3 and L2STT at the start of a run. Distributions of tracks, vertex position and beamposition can be monitored using the vertex browser. The browser can be kept running at all times; it will automatically load new runs. If the browser needs to be (re)started, do the following: Log in to d0ol77 (d0ssh d0ol77) Type setup d0online Type start_daq vertex_browser If the BeamSpotMonitor process dies, it will show up as a major alarm on the Alarm Display. It can be restarted with the following procedure: Log in to any online node as user d0run (d0ssh -l d0run <node name>) Type setup d0online Type start_daq beamspotmonitor In the very rare case where the BeamSpotMonitor and/or the vertex examine seem to be in a confused state, it may be necessary to manually kill the vertex examine process, then stop (stop_daq beamspotmonitor) and restart (start_daq beamspotmonitor) the BeamSpotMonitor. There should be no need to manually start the vertex examine and/or restart the GMbrowser. The logfile of the BeamSpotMonitor can be found in the directory /online/log/beamspotmonitor. Consult this file first before restarting the BeamSpotMonitor. The vertex examine and the BeamSpotMonitor both run on d0ol77 (or the VERTEX_ADDR and BSM_ADDR nodes listed in d0online_names.py).

Importing pictures into the elog   last updated 9 April 2009 Instructions on how to paste a GUI picture into the elog: Open a GUI Open a command line window In the command line window, type 'import name.jpg' The mouse cursor turns into a cross. Either directly click on the GUI that you want to import, or hold-click the left mouse button and draw a frame around the area of the screen that you want to import. Then release the left mouse button. Go to elog Drag the 'text' button into the logbook area Click on 'Insert' Select 'Image' -> 'From a file' A sub-menu opens. Click on 'Browse' Browse to your jpg file and select it