RPC & LVL1 Mu Barrel
Online Monitoring during
LS1
M. Della Pietra
Overview
 Status of ATLAS DataFlow changes during LS1
 Changes for gnam based monitoring
 Monitoring @ SFI not more possible: future?
 Trigger and readout extension in feet region
 Noisy and dead channel mapping campaign

M. Della Pietra
08/05/13
2
Changes in Atlas DF
Online Monitoring Architecture
FROM
S. KOLOS
DQMF
Archiving
Displays
(OHP, DQMD)
Data Flow/LVL1/HLT
Information
Service (IS)
Event samples
Event Analysis
(GNAM, Athena)
IS Mirror
(outside P1)
Web IS
Web Browser
• The actual system behaved extremely well in the npast years
– It’s efficient ad scales well with number
f
o CPUs(cores)
– Functionality is rather complete
• No changes for the overall architecture of the online monitoring system
have been planned
4/17/2013
M. Della Pietra
Discussion on LS1 plans, CERN
3
08/05/13
3
Changes in Atlas DF
However … during
S
L1
FROM
S. KOLOS
• Some components will undergo substantial
modifications, motivated by:
– Changes in the T/DAQ system
– Monitoring experts requests
– Usability improvements
• We plan to achieve thehfollowing (rather
contradictory) goals:
– Make the system more flexible
– Make the system easier to use
– Keep backward compatibility of te us er API (whenever it’s possible)
4/17/2013
M. Della Pietra
Discussion on LS1 plans, CERN
4
08/05/13
4
Changes in Atlas DF
The changes driven by the T/DAQ redesign: Event Sampling
FROM
• Current implementation allows event sampling
S. KOLOS
after_L2 as well as after_EFs
• New T/DAQ system will have no visible L2 trigger:
• Such thing ae “A full event sl ected by
2 L system” will not exist any more
• Events can be sampled only after full HLT chain:
• One can
a smp l e normal physics streams or …
• Request monitoring specific stream(s) to be added to the
trigger menu - events, which are normally rejected by HLT
will end up in those streams
M. Della Pietra
4/17/2013
Discussion on LS1 plans, CERN
5
08/05/13
5
Changes in gnam code?
 No changes has to be done in gnam code about sampling
 We have just to reconfigure gnam application in OKS
attaching them to a new event sampler (new DCMs in TDAQ
dataflow) or to a specific output stream.
 We can monitor on many sources (many streams)
 Also there should be no modification in gnam API foreseen,
but no decision have been taken up to now.
 I will ask again for naming the file saved by gnam with
something more the the file number to have more than on file
for each run
M. Della Pietra
08/05/13
6
What about monitoring at SFI?
 At tree level, is fine for us to monitor a full event after the
HLT chain instead of before it.
 We started to monitor at SFI only because it was the first (and
actually only) place where we can sample a complete event to
compare many RODs
 But there is a second order problem
 Are we interested in monitoring events discarded by HLT
chain?
 Up to now is not clear how it can be possible:
 Full rejected events by HLT can be monitored easily
 If we want to sample only MUON HLT discarded events we have
to agree a change of trigger configuration with Trigger Group
M. Della Pietra
08/05/13
7
Changes in Atlas DQMF
The changes driven by experts requests:
The Data Quality Framework
Off-line
Configuration
ROOT Files
Histograms,
DQ Statuses
FROM
S. KOLOS
DQ Algorithms
On-line
4/17/2013
M. Della Pietra
Configuration
IS
DQM Core
OKS
• The DQM Core SW is used by both
Online and Offline DQM frameworks:
– Allows sharing DQ Algorithms
– Assures the same definition and
meaning of DQ Results
• Offline community is willing to
continue using this approach
• What could be improved:
– Closer integration between Online and
Offline DQ configurations
– Executing thread-safe algorithms
concurrently
– Making existing algorithms more
consistent with respect to thresholds
treatment
Discussion on LS1 plans, CERN
6
08/05/13
8
Changes in Atlas DQMF
Online DQMF: what has already been
requested (in brief)
FROM
• Algorithms parameters may depend on running conditions,
S. KOLOS e.g. run types, luminosity
l
value, etc.
• It’s not c ear yet how far we
h soul d go with that
l
f exibility
• Some use cases would very useful
• Values of the algorithm parameters could be modified
dynamically during a run:
– Requires further clarification
• Having a complete archive of DQ Results histories for old runs:
– Where to store them? How they have to be displayed? How much
time they have to be kept in archive?
• Etc. …
M. Della Pietra
4/17/2013
Discussion on LS1 plans, CERN
7
08/05/13
9
Changes in Atlas DQMF
What about DQ Displays?
FROM
S. KOLOS
OHP
• Displays histograms with respect to
some configuration (XML files)
• Histograms are checked by eyes
DQM Display
• Displays DQ Results together with the
respective input histograms
• Histograms are checked automatically
• There is no convergence between sub-systems yet:
•
•
Some want to use DQM Display only
Others want to keep both displays
• Ideally all DQ checks have to be automatized in the future:
•
It’s not h
yet t e case for some important histograms
• Our plan for the moment is to keep supporting both displays
4/17/2013
M. Della Pietra
Discussion on LS1 plans, CERN
8
08/05/13
10
DQM & OHP
 Do we have request to be forward to the MWG?
 New functionalities?
 Do we think to still use both displays?
 I think so…
M. Della Pietra
08/05/13
11
Feet extensions
 We have to add the readout of the new trigger
chambers in feet region
 Add some more histos accordingly (1 day work)
 Write the new mapping file (a couple of week)
M. Della Pietra
08/05/13
12
Noisy and dead channels
 At the restart I suggest to start a campaign in finding
(by scratch) dead and noisy channels
 Now we have a tool (not available during
commissioning, never used in the last period) to run a
macro (even automatically) on online histograms
 Work done by Arturo Sanchez
 We need to debug also the automatic storage in DB of
dead/noisy channels
M. Della Pietra
08/05/13
13