DQM Status and Plans

Y. Foka(GSI)

ALICE Offline week8.03.12

Last DQM meeting 8 Feb 2012; see minutes and ToDo Lists https://indico.cern.ch/conferenceDisplay.py?confId=170615

Main points discussed on 8 Feb with the aim to make DQM more efficient- Preparation for 2012 run-DQM plot review-Merging DQM/Offline shiftsDetailed ToDo Lists, strategies on implementation, timelines

Work has advanced Detectors were followed up individuallyRunning in ACR, debugging and testing going on as detectors are ready to participateTest the stability of the system before collisions

Merging of DQM/Offline shifts is reality in ACR

Today, updates on status; where we are

At the end of the meeting clear ToDo Lists and deadlinesWe need to be super-ready for collisions

DQM ToDo Lists followup

Provide information to judge the quality of data online, in ACR-Basic detector signals (current status)-Reconstructed quantities (vertex, via online event display)

Identify, collect, find best way to present such info (aim of review)

Based on this information the run could be stopped or other needed immediate actions are to be taken (detector issues)

Use this information to mark the quality of data

Facilitate DQM shifter spotting problems and Shift Leader taking decisions

Components needed to achieve it in ACR1.Provide the data2.Process the data and produce the information3.Publish/visualise the information

Synergy of many different systems is neededThe complexity is reflected in the actual architecture in ACR

DQM Tasks

CR1

ACR

GenericGUI

GenericGUI

DetectorShifterDQM/QA Shifter

eLogBookeLogBookOn-CallExperts

DetectorGUI

DetectorGUI

DetectorShifterDQM/QA Shifter

Detector Team

Offline Core & ROOT Teams

ACRProjectorAliEveAliEve

CR2HLT nodes

Detectorcode

Detectorcode

DA/DQM nodes

AMOREDB

AMOREDBDetector

QAs (expert & shifter)

DetectorQAs (expert

& shifter)

Detectoragents

Detectoragents

DA’sDA’s

Histo, objects

Obj.

Histograms

DAQ Team

Images

Code within AliRoot

Prompt offline recoOffline QA run onlinewith AMORE

AMORE

DQM between online and offline world

Shifter with 2 heads

Input Data DAQ

Data processing and visualisation AMORE: Bart Von Haller (100%) and Adriana Telesca (10%) QA: offline team OCDB: thanks to Chiara Event Display: Mihai Niculescu

Users interface: Francesca Bellini (20%)

DQM support: alice-dqm-support@cern.chYF, FB, BVH, AT, MN

DQM support

DQM/Offline shifts merging (FB, FC)

DQM plots review, status of implementation and To Do Lists (FB)

Software status- AMORE (BVH)- Offline-DQM interface (BVH)- Online Event Display (MN)

Subsystems updates•Vertex: SPD/DA reconstructed vertex•SSD: number of problems understood, status•TPC: example on implementing QAchecker, macro etc•TRD: new developments (coming to standard)•V0: status, QAchecker

•Trigger: related to aliases•HLT: DQM plots (access reconstructed quantities)

DQM today’s agenda

7

Requirement for all detectors to provide thresholds and quality flag in synch with what is displayed on the plot

DQM thresholds and quality flag

Essential for “judging automatically” the quality of data

Thresholds on the plots have to mark “good” or “bad” statusThis status has to be correctly reflected to the quality flag of the AMORE/GUI tree

Plots that do not conform to this will not be displayed for pp

The values of thresholds have to be reliable in different conditions (pp, PbPb…)-have to be fine-tuned in ACR with collisions- need to change according to real life conditions in ACR lumi, rates, background, detector configuration

The tools to set them and change them in ACR have to be ready

DQM thresholds and quality flag

Need to change thresholds online in ACR despite the AliRoot weekly releases

Work-around (see i.e. presentation of TPC) 1. use macro if post-processing is needed (does not pass thresholds to offline)

2. new procedure (config file) to replace the macro was developed (pass thresholds to offline; thanks to Chiara and Barth!)

For startup detectors were asked to have proper implementation ofQAchecker and use macro (to set thresholds and calculate quality flag)

For status of implementation see FB summary and reports from detectors

Details and status of new developments by Barth

DQM thresholds and quality flag

The framework is ready and was tested during 2011 PbPb runthanks to Ruben!!

In 2011 FB prepared the config files with the trigger classes aliases definitionsand requests for splitting detector-by-detectorsee 8 Feb FB presentation

In 2012 the detector experts are responsible to provide individual config files with the triggers split definitions

Only one config file with the trigger classes aliases will be handled either by trigger coordination or DQM supportEvgeny Kryshen (deputy TC) offered to take care; see his presentation

Trigger aliases details to be decided by PB/Offline/Trigger Coordinations

DQM plots by trigger classes

Identify “top level – Run Conditions” plots give info on run/beam conditions that would trigger end of run

Identify “2nd level – Detector Main Plots” plots (summary plots) give red/green status, easy and fast to spot

Identify “backup” monitoring plots give extra information to detectors on-call if a problem is spotted

Identify “logbook” plots give extra info for experts in the logbook, not displayed on the shifters layout available via the trees upon request if needed

DQM plots reviewIndividual meetings with all subsystems to accommodate multiple requirements-Make system “automatic” (red/green status)-Provide all necessary info (detectors are living objects!)

Only high level plots on layout for shifter

For each available (or future) plot we asked details about:

- content of the histograms- priority level- if meaningful in technical runs- which event species it can be populated for- if it has to be splitted by trigger classes- if and what kind of thresholds are set- which criteria to be used to state the quality- what kind of check can be performed automatically on the plot- implementation status: - is it in QADatamakerRec? - is the check implemented in QAchecker or macro?- is the splitting by trigger classes defined in the right config file?

Reviewed topics

DQM Implementation Status 8 Feb

DQM Implementation Status 8 March

Resumed weekly installations of DQM software at P2

15 March: deadline for code delivery14 March: start machine commissioning

30 March: documentation readyEnd March: special runs

Beginning April: collisions

Easter at P2…..

Roughly 3 weeks left till collisions

Implementation and Deadlines

Merging DQM/Offline shifts is reality in ACR

Common policy for accepting/validating shifters

More details in presentations by Francesca and Frank

DQM/Offline shifts

Next meetings

DQM/offline shifters training 19 March at 14:00see details by Francesca and Frank

DQM Forumwe propose 30 March or 4 April6 April black Friday

Call for DQM on-call

DQM on-call!

Subsystem responsibles good candidates!Contact us for special training

DQM shifts are merged with Offline shifts•Make system easy, provide automatic checks• Detectors are living objects, conditions depend on lumi, background… provide way to adjust automatic checks online

Preparation for 2012 run after review of last year’s experience•DQM/AMORE system•DQM plots and thresholds•Online event display

Shifters training and shift booking

Deadlines and planning

DQM in 2012