%% Template Last modified: 29-Oct-2011 by H AbouZeid
%%
%% This e-log template is to be used for the LAr / Forward / Tile Detector shift summary.
%%
%% When posting the elog, choose Message Type: Shift Summary, ShiftSummary_Desk: Calo
%%
%% Please submit a Bug Report (link on the combined whiteboard) if
%% you encounter any issues with documentation, etc
%%
%% Please REMOVE the comments before pasting it in the ATLAS e-log web interface.
%%  Assuming you have been editing file "tmp.elog", you may use the following command from a terminal:
%%  > grep -v \%\% tmp.elog >! elog_nocomments.elog
%%

Shift Crew:
===========
ACR shifter(s) :
LAr Run Coordinator :
Tile Run Coordinator :
LBCF (Fwd Det) On-Call :

General Summary & Ongoing problems:
==================================
%% Summarize the big picture:
LHC Activity :
Runs with Stable Beams :
Calibrations Taken :
Major Problems :

Data-Taking Conditions:
======================
%% Overview:
%% LAr includes 8 partitions: EMBA,EMBC,EMECA,EMECC,HECA,HECC,FCALA,FCALC
%% The Forward Detectors include LUCID (LCD), ZDC, and ALFA/RPO.
%% Please cross-check with the WhiteBoard; any differences should be recorded here.

  Overview:
  --------
  Overall Forward Detector status from FSM :
    o) LCD (LUCID) :
    o) ZDC :
    o) ALFA (RPO) :
  Overall LAr status from FSM :
    o) ROD :
    o) FEC/LVPS :
    o) COOLING :
    o) HV :
  LAr Partitions Enabled : X/8

%% LAr Configuration:
%% These parameters are found in the TDAQ GUI / Load Panels / Larg.Panels.MasterPanel / H/W Control / ATLAS / LArg / PARAMS_GLOBAL
%% Please cross-check with the WhiteBoard; any differences should be reported to the LAr Run Coordinator

  LAr Configuration:
  -------------
  Number of Samples [nbOfSamples] :
  Gain [gainType] :
  L1 Latency [l1aLatency] :
  First Sample [firstSample] :
  Data Format [format]:
  RunType [runType]:
  TowerBuilder Delay Type [delayType]:
  DSP Version [dspExeFile] :
  DSP Threshold 1 (ADC) :
  DSP Threshold 2 (Qfactor+time) :
%% The DSP thresholds can be found from OHP (Run_Parameters/Global/DSP ADC thresholds): give the mean of both distributions.

%% Data streams:
%% List the streams from OHP under Run_Info / Run_Parameters / Stream_Info
%% Please especially check for
%%    all runs: physics_CosmicCalo, calibration_LArCellsEmpty
%%    runs with stable beams: physics_Egamma, physics_JetTauEtmiss, calibration_LArCells, physics_ZeroBias

  Data Streams:
  ------------
  physics_* :
  calibration_* :
  others :
  
Shift Chronology:
================
%% List *all* the events that happened during your shift with their times, including start/stop times of each run that has been taken.
%% The general suggested format is:
%% [time stamp] [summary of the event, comment] [link to elog entry]

XX:XX -- Start of Shift
%% Other events
YY:YY -- End of Shift

Run-by-Run Summary:
==================
%% You do NOT need to list runs where neither LAr nor the Fwd Detectors were not included or short, transitional runs without stable beams.
%% For some reason if you could not note all the relevant information, please recover them with the run query tool:
%%    http://atlas-runquery.cern.ch/query.py?q=find+run+last+5+%2F+show+all
%%
%% o) Project tag: from TDAQ GUI / Run Information.
%% o) Detector Coverage: For LAr, please check OHP at the beginning of each new run
%% o) Change in Conditions: list any change of conditions with respect to the above "Data-Taking Conditions" with the associated LBs.
%%    This includes HV trips, HV variations, dead OTXs, removal of busy devices or failure of hardware while running.
%% o) Number of Events Recorded: from TDAQ GUI / Counters. Specify if the run is ongoing or finished.
%% o) Trigger Rates: list the L1 trigger items and stream rates using the trigger presenter tool:
%%    -- [Under L1 tab] L1_EM5_EMPTY,L1_TAU8_EMPTY,L1_J10_EMPTY,L1_FJ10_EMPTY
%%    -- [Under EF tab] str_CosmicCalo_physics(output), str_LArCells_calibration(output)
%%    -- [Under L2 tab] str_LArCellsEmpty_calibration(output)
%%    Write down your best evaluation of the average, excluding spikes, not just the instantaneous rate at the end of the run.
%% o) Data Quality: your evaluation of the quality of the data recorded
%%    -- Green means there was no particular problems.
%%    -- Yellow means there were some Data Integrity problems, but nothing that affected data-taking conditions.
%%    -- Red means there were changes in Conditions or major problems with data acquisition flow or hardware.
%%    By indicating Y/R, you're telling the experts to have a deeper look at this run offline.
%% o) Summary of QPLL Unlock occurrences
%%    -- Please summarize the occurrences here, rather than posting a separate elog (new!)
%% o) Additional Information: any other piece of information or elog that may be of interest for the offline analysis of this run.
%%
%% Copy the following template for each new run.

  ------------------------------------------------------------------
  Run: NNNNNN
  -----------
  Project tag:
  Stable Beams [y/n]:
  List of FWD detectors included in the run: 
  Detector Coverage:
  Change in Conditions with respect to the above:
  Number of Events Recorded:
  Start/Stop Time:
  Total LB:
  Average Tile Fraction Busy:
  %% From OHP
  LAr # of readout FEBs :
  LAr # of FEB Errors :  %% Please indicate Partition, FT/Slot, and type of error
  Trigger Rates (TAP, in Hz):
  +
  %% If not Green, partition(s) and LumiBlock(s) affected:
  Data Quality (LAr/Fwd) [G/Y/R]:
  
  %% For TIL make sure to check digital errors.  Are they increasing for any module?
  %% Check occupancy map.  Any holes, or hot-spots?
  %% Check Tile performance: E,Phase offline vs online
  Data Quality (TIL):
  %% Include link to specific elog if applicable
 
  +
  LAr QPLL Unlock Occurrences:
  Time | LB | DQ Errors [Y/N] | Half-Crate affected [e.g., EMECC1_03R] | FT
  %%
  Additional Information / Comments:

  ------------------------------------------------------------------

Observed Problems:
=================
%% Go into more detail here about problems (DCS Alarms, MRS Errors/Warnings not on the Whiteboard) 
%% that you encountered during your shift. If not explicitely mentionned above, include the run number
%% in which each error has occurred.
%%
%% If there is a significant or pressing problem, please enter it into the elog
%% immediately as a separate entry, with the time the work was done.
%% 

%% List all DCS alarms with elog entries when applicable.
  DCS alarms (LAr/Fwd):
  ---------------------
  
  
  DCS alarms (Til):
  -----------------


%% List new MRS errors and warnings (short version).
%% Only give a sample for cases with a large number of instances, or those which have been recorded in a separate elog.
%% Please only summarize QPLL Unlock messages in the area above for each run; it is not neccessary to paste them here
%% A reminder the TIL trip MRS messages must go into a *separate* dedicated elog for each run. The template for this is on the whiteboard.
  MRS messages (LAr):
  ------------------


  MRS messages (Lucid):
  -------------------


  MRS messages (ZDC):
  ------------------
  
  
  MRS messages (TIL):
  -------------------

%%List any other issues (not mentioned previously) that needs/needed expert intervention

Description of Major Problems
=============================


Important Messages at End of Shift:
==================================

%% Please list here important messages or instructions for the next shift crew.
  Next Shift Crew:
  ---------------