LAr/Tile/Forward Detectors White Board

Important Phone Numbers

LAr Monitoring Spy

• Link to LAr online monitoring plots

Weekly based calibration plan

• (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

ATLAS Daily Schedule

Daily Plan and important messages from the RC

here

• 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

• 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.

LAr DAQ Configuration

FWD DAQ Configuration

Tile DAQ Configuration

LAr DCS

FWD DAQ Configuration

Tile DCS