LAr/Tile/Forward Detectors Whiteboard

Daily Plan and important messages from the RC

• At the start of each shift ensure you read the "Current Status" of the three sub-detectors. Known MRS/DCS warnings/errors are printed there.
• Click here to see who is in shift in ACR at the moment. Clicking on the shifter's name, you can also see who are the next shifters.
• Please report bugs or missing documentation on bug report page
• Post suggestions or discussions on bug report page(new category)

• Calibration period (experts are working with calibration)
• 17:00 Join to combined run for data tacking
  • Run Parameters for these runs: samples: 5 latency: 94 first sample: 2 format: Format1/Results
• Take LAr calibration (Daily/Weekly) according to available time (1h/2h). Please use LAr Calibration (beta) panel.
• Notes:
  • If there are HV trips, shifters should mask them from the FSM Alarm Screen (later, the HW on-call will check the masked alarms)
• Shifters please always study the whiteboard and check ATLAS and LHC programs (yellow box on the right).
• Items to follow-up (experts only): Pt1:LArRunCoordination GPN:LArRunCoordination

Link to LAr Monitoring Spy

• Notes: If a big part of the detector is OFF call immediately to the *Tile DCS on-call* and to the *Tile Emergency Phone*.

Call immediately to the *Tile DAQ on-call* and to the *Tile Emergency Phone* if you see the following error/alarm messages in MRS:

• • TileXXX_RODRCD rc:HardwareError TileXXX_RODX_ChanX_XXX-XXX_ROLXX TileXXX_RODRCD
  • TileXXX_RODRCD TileRCD::Issue TileXXX_RODX_ChanX_XXX-XXX_ROLXX has been disabled by TileCalXXX_RODModule_X and check with the Run Control shifter if he did the stopless removal

Until this message is deleted:
LBC41 sometimes does not recover properly after a trip (giving high fraction of digital errors). If this happen, try one power-cycle (calling DCS on-call). If this does not cure the problem DO NOT try to power-cycle again, but report in the elog for the Summary of run. Usually the module recovers itself at a new start of run. Check again the module at the next start of run and report in the elog if the module was recovered.

Until this message is deleted:
Do NOT submit one elog for every trip. Trips should be reported in the run summary elog and if there were particular problems with trip recovery, this information should also apper in the run summary elog.

From May 23, until this message is deleted:
Shifter should NOT log in into FSM panel, the ERRORs after a trip will be cleared automatically.

Until this message is deleted:
Do NOT call Tile DCS expert if shift leader sees "LHC TILE CurrentData no update" on DCS Alarm screen. This is a known problem that Tile shifter is not monitoring (only central DCS). There is people trying to solve this, it does not affect standard readout.

• Run Plan:
  • ALFA: standalone operation ocasionally by experts, usually in shutown state, in general out of the combined run until further notice. Around October 18: 2nd special ALFA run at beta* =90 m, ALFA included in the partition, dedicated trigger menue, latency for all other detectors shifted by 20 BX.
  • ZDC: in global partition (edited on 22.10.2011)
  • LUCID: in global partition.
• Detector:
  • LUCID: all ON, DCS should be green.. In the unlikely event of LUCID becoming busy, a procedure for stopless removal is started. Tell RunControl shifter to always answer yes to the related pop-up window. This will NOT stop the measurement of luminosity.
  • ZDC: all ON, DCS should be green. If HV or Crates will turn orange/red please call the expert. If Scalers turn orange/red, check via the Log Manager whether there are any messages/errors from the application zdc_publish_scalers in the initial partition. If the problem persists for more than 5 minutes call the expert and indicate all messages you found. Data Quality: ZDC flags in the DQMD (Data Quality Monitoring Display) are under revision so they can be safely ignored until further notice.
  • RPO (Roman pots or ALFA): all OFF, DCS should be green. The default settings for RPO are OFF to minimize the risk of radiation damage of the electronics. DCS alarms should be (i) e-logged (under ALFA/RPO) and (ii) during working hours, reported by telephone to Sebastien Franz, 16-5217 while outside working hours the FD on call should be called. In particular, if the online value of the temperature exceeds 45 deg., call ALFA expert Sune Jakobsen at 16-8853. In case experts plan measurements they will contact the shift leader and LAr shifter in advance. When the measurements are finished or stopped for any reason the system has to be set back to the OFF state.
• Calibrations:
  • LUCID: calibration ought to be performed once per day with the new automatic procedure LUCID Calibration (Beta). Instructions can be found in the Shifter's Manual
  • ZDC: calibrations ought to be performed twice per week, preferably Monday and Thursday with the new automatic procedure (Menu CAL->CalibrationMenu->LUCID Calibration Beta).
• e-log policy:
  • When making an e-log entry that concerns ONLY forward detectors, please use the "Default" message type and select the relevant detector(s) as "System affected" (ALFA and/or LUCID and/or ZDC). Do NOT use the "LAr" message type, as this defaults to LAr (+ possibly others) as System Affected, and sends a lot of spam to the LAr experts and coordinators.

Weekly based calibration plan

Combined Calibration Tool Twiki

• (1) For LAr, take the full or remainder of the weekly set on Monday if it couldn't be completed on Sunday. Plan 1h30 for the full set.
• (2) For LUCID, the default calibration is called 'Daily'; an attempt should be made to have one calibration everyday in between fills.
• (3) For L1Calo+LAr combined calibrations, experts will be in charge of taking this set until the panels are fully automatized.
• (4) For Tile: You can finish them all in less than 1 hour. The last laser calibration is the slowest. If there is not enough time before ATLAS needs TileCal again, take the fast calibrations first, and wait for another opportunity to take the long laser calibration. If ATLAS needs TileCal, stop whatever calibration you are doing, and close the TILE partition. Check if the shifter before you has already taken some of the calibrations.

• LAr: LAr Calibration panel, through CAL/Calibration Menu/LAr Calibration(Beta)
• Tile: Tile Calibration panel, through Tile/Tile Calibration - More info in Tile Calibrations Twiki
• LUCID:
• L1Calo+LAr: calibration tool, through CAL/Calibration Menu/L1Calo Calibration), then 'LAr Energy Scan' in the bottom section

Elog Templates

Elogs for calibrations can be submitted from the combined Calibration Panel.

Important Phone Numbers

ATLAS Daily Schedule

Important Links

LAr Current Status

Tile Current Status

FWD Current Status

• LAr Troubleshooting Twiki
• LAr Operations Page
• LAr ID Translator (GUI to translate LAr coordinates)

This part should contain the links with the important information for the run coordination, and for the shifters. Maybe it can be divided into three session (different subsystems) + a general list of links

This list should contain the KNOWN issues for each subdetectors, the detailed description of the DCS status and the links for the documentation (twiki, training)

Tile DAQ Configuration

Tile DCS