Central DQM Shift Tutorial Online/Offline

Overview of the CMS DAQ and useful terminology 2 Detector signals are collected through individual data acquisition systems (cables and boards) that end up at the FEDs: the first element of Global Data Acquisition system (DAQ) FED ( detector FrontEnd boards): multiple FEDs per detector collect event fragments that are sent to the online event processing farm Builder Units: Computing farm that collects event fragments from all FEDs and merge them to produce full event information Filter Units: Computing farm where the High Level Trigger (HLT) is run to filter interesting events Storage Manager: application that saves to local disks events selected by the HLT Detector signals are collected through individual data acquisition systems (cables and boards) that end up at the FEDs: the first element of Global Data Acquisition system (DAQ) FED ( detector FrontEnd boards): multiple FEDs per detector collect event fragments that are sent to the online event processing farm Builder Units: Computing farm that collects event fragments from all FEDs and merge them to produce full event information Filter Units: Computing farm where the High Level Trigger (HLT) is run to filter interesting events Storage Manager: application that saves to local disks events selected by the HLT Storage Manager

Online DQM Online DQM: suite of CMSSW applications that run either on all events in the Filter Farm or on a selection of events served by the Storage manager Since Dec2009 Online DQM consume DCS information in addition to Event data Online DQM Infrastructure is completed by the DQM data transfer system up to the DQM servers where the histograms and other DQM data are uploaded and visible to the shifters and the CMS community Scope of Online DQM Shifts: Identify problems with detector performance or data integrity during the run 3 Storage Manager

Offline Data Processing and Offline DQM Online environment T0, CAF Prompt Reconstruction at T0 and CAF is performed from within one hour up to 48 hours after data is transferred from P5 to T0 and CAF (CERN) T1 Subsequent iterations of re-reconstruction at the T1’s follow periodically the Prompt Reco with improved Alignment and Calibration constants, bug fixes. Offline DQM is part of the Offline data processing that, in addition to detector data analyses, includes higher level reconstruction objects, aka Physics Objects (POG’s) Scope of Offline DQM Shifts: Produce the data certification for various reconstruction iterations  USED FOR CMS OFFICIAL GOOD RUN LISTS!!! 4

Online Shifts at P5 (3/day for 24 hours coverage) 23:00-7:00 | 7:00-15:00 | 15:00-23:00 On the first day of global running, shifts start at 9:00 (for this shift you can use regular 8:15 shuttle) For latest run plan updates (shift cancelations), inscribe to: Offline Shifts run at Control Rooms away from P5(4/day) 1:00 – 7:00 at Fermilab 7:00 – 13:00 at CERN-CMS Centre (Meyrin site) 13:00 – 19:00 at DESY 19:00 – 1:00 at Fermilab In order to certify reprocessing data,Offline DQM shifts can also be scheduled outside of global data taking periods DQM Shifts - Overview 5

6 Access to Control Rooms on CERN Site Safety requirements for P5: –Online CMS level 4C safety class must be passed. –Each shifter should have appropriate access rights: through EDH: request access to « CMS CR » for P5 request access to « CMS CEN » for CMS Center at Meyrin Regular shuttle service which runs 7 days per week. -

7 In preparation for the shift Read the DQM shift instructions, even if you have been on shift before: Check the instructions at the beginning of each shift to find out if something has changed since your last shift

8 In preparation for the shift For newcomers: Schedule your first shift in the daytime so assistance will be readily available if needed Attend the shift tutorial on Monday (possibly the latest one before your shift or the one before that) Attend a trainee shift between the tutorial and your first shift – Arranged by DQM shift managers and you will the receive mail in time

DQM Shift Tools DQM GUI: Graphical User Interface, for histogram viewing DQM Run Registry: web interface to the Database that holds run information. Used by shifters to register interesting runs (Online shifters) and to collect quality information Elog: for end of shifts and problem reports TWiki pages: for shift instructions 9

10 Task 0: Applications (1) Make sure DQM applications and GUI are running during data taking: –Online: check update of histograms during runs –Offline: check arrival of histograms from Tier-0/CAF processing (2) Check correct updating of Run Registry (3) In case of problems in DQM Tools (persisting longer than 15 mins), call: (4) During Online shifts stay in close contact with the Shift Leader (P5) DQM on-call Expert :

Task 1: Histogram Inspection Follow online/offline shift instructions Run-by-run procedure: –(1) Enter significant runs in the Run Registry –Online Shift : decide on significant runs (cosmics/Commissioning) to register in the Run Registry (confirm with the Shift Leader!) ALL Collision runs should be registered (even if for 1 LS) –Offline Shift: analyze runs previously registered during online shift –(2) Shift histogram Inspection Look at the Summary, the Reports, and Shift Workspace in the DQM GUI Make an effort to look at all the plots one by one. If you spot a problem or have a question regarding a specific plot Check the sub-system instruction and take action(s) accordingly If not explained in the instruction, discuss with P5 shift leader and if needed inform him to call Detector On Call (DOC) In offline, inform sub-system DQM experts, as noted in the instruction page by mail or phone – Make Elog entry (Type : “Problem Report”) 11

GUI – Summary Workspace 12

13 GUI – Summary Workspace

14 GUI – Reports Workspace

15 GUI – Shift Workspace

16 GUI – Shift Workspace I nspect Error plots (Online GUI -> Work Space -> Shift -> Errors They show plots that indicate errors. Please read sub-system short term instruction about the evaluation Keep this page and the summary page always open throughout your shift at P5

17 DQM Shift Instructions

18 DQM Shift Instructions Check HV information on the DQM GUI summary ( "Info" histogram) and the Run Registry ( "LumiSec" table) are consistent.DQM Sometimes "LS" in the Runs table shows 0. If this happens: make an ELOG entry "Problem report" indicating the run number ensure that the DQM expert on-call is aware of the problem. put the information manually into the general comments section of the Run Registry. format: Example: LS 0 = CASTOR, Strips, RPC, Pixel, and DT with HV OFF. All others with HV ON. When stable beam is declared, all the subdetector should be switched on including Pixel and Strip If the HV is still off, ask shift leader or DCS shifter Correlation between Data Cert and HV conditions: If HV remains OFF throughout the entire run corresponding sub-system would appear as Yellow (no need to check histograms if not specifically mentioned in documentation) If HV is ON in at least one LS, follow usual procedure to certify

19 Task 2: Online Run Registry Hover over the quality flag to see the comment The Online Run Registry can be found here: You need your NICE password to log in! Run Registry collects automated run summary and information filled by the DQM shifters: Data quality and Comments. There are two tables in the Online Run Registry: - Run Summary - Selected Runs

The Run Summary table contains information that is automatically entered All Runs are entered in this table, from short start/stop runs to stable long runs This table is used by the ONLINE DQM SHIFTER to select Significant runs: – Register all the collisions runs! – F or commissioning or cosmic runs, register only runs that have more than 10,000 events and/or have been running for more than 10 minutes (if you are in doubt, ask the shift leader). – Follow the run-by-run workflow inspecting the shift histograms. Ask the shift leader for confirmation on the info reported and then move the entry to « SIGNOFF » Online Run Registry: Run Summary Table 20

22 Register Runs in Run Registry During the run: Click Run to select it  Manage  Edit Based on the shift histogram instructions, set the online subsystem flags (GOOD/BAD) and enter comments If a subsystem is BAD, inform the shift leader and the subsystem expert, and enter comment Try to provide complete information by adding info like Beam status, etc. in the “comments” field. Online

Online Run Registry: Editing Reference PanelHelp Panel Run class Stop reason General comment Components Component information: -Status (restricted list) -Cause (restricted list) -Comment (free text)

23 After the run: Enter the ‘stop reason’ (in the stop reason field, NOT under comments) The certification results must be confirmed by the shift leader, before the status of a given run is moved to « SIGNOFF » Click Run to select it  Move  to SIGNOFF Once the run is in SIGNOFF state, it cannot be modified by the Online shifter. Register Runs in Run Registry

Online DQM Shifter: Run Classification 24 Note that Runs are classified though the Group name in the RunRegistry: A ssigning correct Run class is of vital importance as it will affect Offline determination of Runs to be used for different analyses Current rules follow, make sure you check updated shift instructions at start of your Online DQM Text 1. "Collisions" if the run is taken for physics analysis purposes and contains at least one lumi section with two stable beams (colliding or non-colliding). 2."Cosmics" if the run is taken for analysis purposes with cosmics trigger with atleast one muon system + Tracker in DAQ and there is no beamactivity throughout the run, i.e. stable "no beam" conditions 3."Commissioning" for all other runs, i.e. those taken for tests or specific detector studies only, i.e. not meant for general offline physics analysis. Runs are classified automatically by RR. In case of doubt as the shift leader

Prompt Reconstruction GUI For collision runs Sub-systems use different promary datasets – For cosmic runs Cosmic Prompt dataset used for all sub-systems To ease pp certification workflow a dedicated application (a layer on top of the GUI) is prepared – Default GUI is used for cosmic certification Subsystem switches to select proper Pds for each of them

26 Task 2: Offline Run Registry The Offline Run Registry can be found here: You need your NICE password to log in! Run Registry collects information filled by the DQM shifters: Data quality and Comments. There are two tables in the Offline Run Registry: - Waiting List - (Offline) Datasets

Offline Run Registry: Shifter’s use 27 Refresh Offline Datasets table (or add automatic refresh) and wait for the dataset in OPEN state to appear Edit the dataset and proceed with subsystem evaluation based on relevant histograms in the GUI, assign quality flags Move the dataset entry to SIGNOFF when all subsystems are analyzed

28 ELOG Log in with your AFS account –Click on "Elog" and choose Subsystems -> "Event Display and DQM" Problem Report ( 1 entry per problem ) –For each problem arising during your shift make a "Problem Report" entry – Please use “Elog” to report problems! Shift Summary ( 1 entry per shift ) –Summarize the run numbers you checked during your shift –During collision runs check histograms every hours and make an entry in this elog N.B. (!!!): –Use Types "Problem Report" or "Shift Summary" only, do NOT create new –No need to create elogs for each run. Make sure run-by-run information entered in the Run Registry correctly

Run ECAL barrel Trigger Primitive Digi and RecHit Occupancy DQM Shift crew took 2hours to report

Run We lost 70pb-1 of data due to problem in fill 2536

Run Software issue, no fortunately no data loss DQM shift crew did not notice it for a few days

TOTEM test fill 2783 There was a problem in the HLT menu and DQM applications did not get events from Storage manager DQM shift crew did not notice that all histograms were missing. He realised ONLY when sub-system people enquired about this......

Commissioning Runs DQM shift crew did not notice that all SiStrip/Tracking histograms were missing for about 18 hours during 13/9 to 14/9. We realized ourselves and informed the shift crew !! It was only commissioning runs so no loss of data but we were blind about the SiStrip detector Software issue and got fixed quickly

33 Shift Hand-over Make sure to arrive 5-10 minutes early for shift hand-over. Upon your arrival in the control room, the previous shifter will be there –Get from her/him the information about the current status of the data taking and what happened during the previous shift. –The shift person will show you where the tools are running, which you will be using (DQM GUI, CMS Online page, Run Registry). –Make sure you have logged in to all the tools (ELOG, RR) as yourself! –If anything with your tasks is not clear, ask at that moment! –At the end of your shift, wait for the next shift person to arrive and provide the same support.

34 Links Shift instructions: – – – – DQM Online GUI: – – – –Follow certificate instructions at Run Registry pages: – OnlineShift Usage : – Offline Shift Usage : – CMS Users: –Elog: –

Final Suggestions From now to your shift: - Get familiar with the DQM TWiki pages (general structure & dedicated On/Offline): Shortly before each shift you MUST read : - Short term instructions - Commissioning and EvFDQM Hypernews Announcements Online/Offline Shift Histograms by Subsystem <---- especially Online shifters - Read the Elog of the shift before yours to be aware of the recent activity (please read both Shift Leader Elog and Event Display and DQM Elog)Shift Leader Elog DQM Elog) 35