TWiki> Main Web>TestCWB (revision 3)EditAttachPDF

LAr/Tile/Forward Detectors White Board

Important Phone Numbers

LAr Calorimeter Number
ACR Desk   xxx xxx
SCR Desk   xxx xxx
Emergency Phone   xxx xxx
Run Coordinator xxx xxx  
Tile Calorimeter Number Backup
Emergency Phone   16-2581 +41 76 487 2581
ACR Desk   71408 +41 22 767 1408
SCR Desk   71408 +41 22 767 1408
DAQ on-call Jalal Abdallah 16-0418 Oleg Solovyanov (16-3436)
DCS on-call Claudio Santoni 16-3476 Gabriel Ribeiro (16-9659)
Run Coordinator Paolo Francavilla 16-3155
Deputy Run Coord. Maria Fiascaris 16-1950
important Tile phone numbers      
Forward Detectors Number
xxx   xxx xxx
Run Coordinator xxx xxx  

LAr Monitoring Spy

Weekly based calibration plan

System Monday Tuesday Wednesday Thursday Friday Saturday Sunday
LAr Weekly(1) Daily - Daily - Daily Weekly
Tile - All - All - -
LUCID(2) Daily Daily Daily Daily Daily Daily Daily
ZDC YES - - YES - - -
L1Calo - - - - YES - -
L1Calo+LAr - - Combined: expert(3) - - - -
L1Calo+Tile YES - - - - - -
  • (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.
Tools: these are the tools used for production. Unless the run coordinator or experts tells you otherwise, please use the following tools when a calibration is needed:
  • 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

Template for the end of run summary (physics)
Template for the end of shift summary Here an example
For Calibration cut-and-paste information from the Calibration Panel

ATLAS Daily Schedule

Daily Plan and important messages from the RC

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.

LAr Calorimeter

  • 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

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

Forward Detectors

DAQ Panel Configuration

Check these values in the corresponding setup items of the DAQ Panel For the OHP configuration, Please synchronize your action with the other CAL shifter, in order to have the Tile OHP configured in one desk, and the LAr OHP configured on the other desk.

Global Setup
Version TDAQ-03-00-01, HLT-
Setup Script /det/tdaq/scripts/
Partition Name ATLAS
Database File /atlas/oks/tdaq-03-00-01/combined/partitions/
MRS Filter (*TIL*|*Til*|LAR|LAr|Lar|lar|*ZDC*|*Zdc*|*zdc*|*LUCID*|*Lucid*)&(^(*TIL*RODRCD|*Til*RODRCD|*Til*TTCRCD*|*TIL*TTCRCD*))&(ERROR|FATAL|WARNING)
OHP Opt -c /atlas/moncfg/tdaq-03-00-01/tile/ohp/Tile.ohp.xml
OMD Opt /atlas/moncfg/tdaq-03-00-01/daq/omd/OMD-generic-config.xml
TriP Opt -c /atlas/moncfg/tdaq-03-00-01/trigger/trp/trp_gui_conf.xml
Tile Remote Monitoring Setup
Instructions are in the TileRemoteMonitoring page (outside Point1)

LAr DAQ Configuration

Text and schreenshots

FWD DAQ Configuration

Text and schreenshots (this can be moved on the right column if needed)

Tile DAQ Configuration

DSP Configuration to be checked at the beginning of a run

DCS Status

CHECK FSM at least once every 30 minutes! If warnings come and go, during day shift call DCS-expert-on-call and make e-log entry, during night shift write e-log and instruct morning shifter to call DCS on-call.


Text and schreenshots

FWD DAQ Configuration

Text and schreenshots (this can be moved on the right column if needed)

Tile DCS

Important Links

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)

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng 2011_10_24_fsm.png r1 manage 116.4 K 2011-11-07 - 07:54 PaoloFrancavilla  
PNGpng DSP_Config.png r1 manage 12.4 K 2011-11-07 - 07:46 PaoloFrancavilla  
Edit | Attach | Watch | Print version | History: r7 | r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r3 - 2011-11-07 - PaoloFrancavilla
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback