Offline DQM short term instructions

General offline shift Instructions -- Shift histogram description by subsystem

Goals of this page:

Here are some important short-term notes/instructions for current reconstruction conditions. Notes here are supposed to represent temporary changes with respect to the normal instructions the shifter was given. In case of doubt, contact the subsystem expert.

  • Shifters
    • The instructions in this page supersede the Offline Shift instructions.
    • If the dates in which the instructions were written are very old, suggest to the subsystem expert to move them to the general Offline Shift instructions or remove them.
  • Experts
    • When adding/updating instructions, always update the date and your name.

Contents

General short term instructions
(last updated: Suchandra Dutta/Kaori Maeshima, 9th Jan 2011)

Instructions for Jan. 2011 Special Offline DQM shifts for Dec22 ReReco Data

All the data to be certified are proton-proton collision runs. Please follow DQM shift instructions for proton-proton collisions (NOT Heavy Ion run instructions).

1. Run Range allocations:

  • CC Meyrin: Run range 146428 - 149442 (Run2010B)
  • DESY: Run range 136033 - 141881 (First half of Run2010A)
  • Fermilab: Run range 141882 - 144114 (Second half of Run2010A)

2. Dataset names in the Run Registry (which have been already set-up):

  • /Run2010A-Dec22ReReco_v1/DQM (Run range 136033 - 144114)
  • /Run2010B-Dec22ReReco_v1/DQM (Run range 146428 - 149442)

3.Link for the DQMGUI html page:

4. Important --> Two step validation process:
Please note that the certification needs to be done in two steps :

  • step-1: validate CSC, DT, ECAL, ES, RPC, EGamma and Muon subsystems, for the complete allocated run ranges, first. Datasets to validate above subsystems exist already in DQMGUI. Make sure NOT to sign-off each run in RunRegistry at the end of this step-1. This step should be done, before starting certifying any other subsystems.
  • Step-2: Validate rest of the subsystems (CASTOR, HCAL, HLT, JetMet, L1T, L1TEMU, Pixel, SiStrip, Track). Sign-off each run only after step-2 is complete in RunRegistry.
  • Please don't forget to read short term instruction for each subsystem below.

5. End of each shift, and towards the end of the week:
Please summarize which runs have been certified in which step (step one or two) at the end of each shift in the DQM elog carefully. Depending on the situation, we may consider adjusting the run range allocations among different sites towards the end of the week.

General short term instructions
(last updated: Kaori Maeshima, Nov 10h, 2010)

Current instructions for Heavy Ion running

For the Heavy Ion DQM Shift Operation, please go to the following links:

Links to Offline DQM Instruction for Heavy Ion runs:
Offline DQM Shift Instructions
Offline DQM short-term Shift Instructions
Offline Shift Histograms for all Subsystems

General short term instructions
(last updated: Virginia Azzolini, 9th Nov 2010)

Datasets to be certified

New Collisions10 runs should be certified with first priority; using the dataset /StreamExpress/H1Run2010-Express-v3/DQM. Then in terms of priority Cosmics10 runs should be certified, same datasets as Collisions10. With low priority comissioning e postcollisions should be evaluated too.

Please notice that ReReco datasets in the Everything->Info->ProvInfo-> runIsComplete plot * always shows 0*. Please skip this check for the ReReco certification. If the run is in RR AND in GUI=> proceed to the certification. |

  • A new run group PostCollisions10 has been introduced to mark runs taken with collisions triggers, but without beam, for the purpose of the Heavy Stable Charged Particle (HSCP) search. No instructions or reference histograms are available for this run type yet. So, check only the HV status of the sub-systems as usual, but ignore anything else.

  • Please use the procedure described here to check the high voltage status of the subdetectors during a run. If the HV for a subdetector is off for the ENTIRE run, the subdetector should be marked BAD. The POG flags may also be affected in these situations.

  • Don't check the high voltage status for CASTOR. Please follow the short-term instructions given below to certify that subsystem.

  • We would like to validate the HV and GT vs Lumi histogram, which shows the subdetector high voltage status vs lumi section. Please compare the information in this histogram (ignoring the PhysDecl row) with the run registry DCS table used for the HV status check; report any discrepancies in the elog. The histogram may be found in the offline GUI (under /StreamExpress/*) in workspace Summary (subsystem "Info") or in workspace Everything -> Info -> EventInfo.

  • For new runs, please use the procedure described here to check that processing is complete before certifying a run.

CASTOR instructions
(last updated: Virginia Azzolini/Ilaria Segoni - 12 Mar 2010)

No Offline CASTOR Certification possible yet, copy the Online quality flag.

CSC instructions
(last updated: ValdasRapsevicius - 15-Apr-2010)

CSC shift instructions updated DQMShiftCSC!

DT instructions
(last updated: Paolo Bellan - 29.6.2010 )

If DTs were included in the run, with HV ON and no read-out problems, the run should be labeled as GOOD.

At the moment the DT are BAD only if in standby or while having serious troubles with the read-out. This is monitored on-line, but you should cross-check it indipendently, performing respectively the two following actions:

  • check the DT HV status in the by-LumiSection table in the run registry. If DT were off for most part of the run, mark the run BAD for the DT. In order to confirm this information, please also verify that basically all segments' histograms are empty. The status can be monitored also on the 'reportSummaryMap' histo (Everything->Info->EventInfo->reportSummaryMap) for the HV. In case of mismatching, trust the run registry, but report the case to the expert.

  • check the DT read-out status in the 'ROChannelSummary' histo (DT->00-ROChannels-> ROChannelSummary). If you see many (> ~10) sectors RED, then mark the run BAD for the DT and inform the expert.

IF the online flag is BAD because DT were OFF(standby), you can replicate it, but please perform these checks anyway.

About other histograms of the DT summary, be aware that efficiency 2D plot in particular, and the occupancy one can suffer for low statistics, and likely to appear with many sectors red or empty; please DO NOT set DT as BAD because of them. Due to new alignment constants, the histograms of mean and sigma of segments' residuals instead should be quite right, that is corresponding to the requirements of nominal DT Shift Instructions. Please mail the expert if you see anomalous distributions in runs with significant statistics.

ECAL barrel / endcap instructions
(last updated: Douglas Berry - 19 May 2010)

  • ECAL Barrel:
    • The ECAL Barrel Summary Map will have an occasional red tower, but the majority will be green with a few orange towers. There is also normally a little extra noise in the ECAL Barrel in EB+4 to EB+12. Below is a typical image of the ECAL Barrel Summary Map and ECAL Barrel Pedestals.

  • ECAL Endcap:
    • There is a red area in the ECAL Endcap Status Summary Map in EE-07. This problem is known, do not mark the ECAL bad for this.

No major difference wrt previous round of certification due to reconstruction changes. Keep the same flags as before

ES instructions
(last updated: - )

No major difference wrt previous round of certification due to reconstruction changes. Keep the same flags as before

HCAL instructions
(last updated: Jeff Temple - 18 October 2010)

The HCAL DQM reportSummaryMap currently uses a value of "-1" to indicate that either (a) no DAQ for HCAL or (b) insufficient events have been processed to certify HCAL . This behavior will be changed in CMSSW release 3_9 to mean only "no DAQ". In the meantime, there are instructions at this link explaining how to identify whether HCAL was out of the run, or in the run but with insufficient statistics to make a certification judgment.

There is a known hot channel in the Hcal Barrel (HB) at HB(14,31,1). This channel may show up as either yellow, green, or white in the hot cell monitor. If the problem shows up in red, then it should be reported to the Hcal experts. Otherwise, it can be ignored, since the channel has already been masked in the channel status database.

UPDATE on 7 October 2010: The color scheme for known bad channels has been changed, so that known bad channels now appear as white, instead of black:

pink.png

Any white channels can be ignored -- they represent problems that are already known.

UPDATE on 18 October 2010: There are some bad channels in HO ring 1 (ieta=5-10) that have been showing up as BAD (red) in the digi and dead cell monitors. However, HO ring 1 is not used in calotower/jet reconstruction. As long as the HB, HE, HF, and HO0 values in the reportSummaryMap are in the good (green) range, the dead cells in HO ring 1 do not need to be reported. The bad HO ring 1 channels appear like this in the dead cell monitor:

ProblemDeadCells_148058.png

HLT instructions
(last updated: Vladimir Rekovic - 2 Nov 2010)

  • If the path is prescaled then the plateau of the efficiency will not be at 1, but at the level of 1/prescale. In that case mark as GOOD.

L1T instructions
(last updated: Dimitrije Maletic - March 2010 )

  • (24th of March) Don't look at "L1T Report Summary Map" until further notice.The plot in not refreshing for Offline shifters.
  • (Feb. 22nd) Please check the status of Muon Detector (which part is excluded in a run). For example, if the bottom of the GMT is empty, the part would be excluded in the run. Check trigger configuration, DAQ setup, Detector status.
  • Until further notice, please ignore "RED" in FED Report Summary Map in Summary layout. It is caused by excluding some muon subsystem.
  • All emulator bins (right-hand column of L1T Report Summary Map) should be empty (white) until further notice.
  • For the data bins, Jets, TauJets, IsoEM, NonIsoEM, and MET should all be empty (white) until further notice.
  • Also, check the L1T histograms 04 Global Muon Trigger DT-CSC BX, 05 Global Muon Trigger DT-RPC BX, and 06 Global Muon Trigger CSC-RPC BX. The red maximum should be in the middle of all three 3x3 histograms. If it is shifted (usually on two histograms, because of the timing problem in CSC, DT, or RPC) the TGMT (muon trigger) group should be notified, and L1T should be marked BAD .
  • If in doubt, call the TPG on call expert at 161958.

No major difference wrt previous round of certification due to reconstruction changes. Keep the same flags as before

L1T emulator instructions
(last updated: Nuno Leonardo - Feb 2010 )

The emulator based dqm results are not available offline temporarily, given the offline reco+dqm workflow currently continues excluding the required emulator sequence. A resolution for this is awaited, Trigger and Offline management advised.

Pixel instructions
(last updated: October 13th 2010)

The low numbers for Barrel Pixels on the Report page as well as the red bin for Errors in the Barrel in the reportSummaryMap plot on the same page are under investigation. Most likely they are caused by a bug in the code. Do not mark the run BAD for Pixels because of these.

We do not expect any changes in the Pixel histograms due to ReReco. The usual instructions apply.

RPC instructions
(last updated: Anna Cimmino - 20 Sept 2010)

The percentage in the Summary report has a bug. To have the correct percentage do as follows:

New_Percentage = ( Old_Percentage - 100)/5

If New_Percentage < 95% put the system to BAD.

Oncall phone is NOT available. In case of problems, please send an email to: anna.cimminoATcern.ch

: Use the instructions above.

SiStrip and Tracking instructions
(last updated: Laura Borrello 17th September 2010)

  • Some discrepancies with the reference histograms can be observed since a new release is used for data processing.
  • We are observing a bump in #of track distribution in Minimim Bias sample. It is due to L1 Algorithmic bit 63 starting from Run 136100. The shape of this distribution changes based on Trigger bits so it may not always be similar with reference distribution. Please do not mark the runs BAD due to the shape of the distribution.
  • Special Treatment for Cosmic Runs :
    • During cosmic runs some histograms in the Express Dataset will be empty as the collision reconstruction is used there
    • The distributions will not match with reference
    • Please don't flag the run as bad for this mismatch


For the certification of reprocessed data follow the standard instruction.
The reprocessed data include a trigger selection (to exclude beam halo events and splash events): small difference can be observed in the number of tracks per event (layout #3, plot #1).
The reference file for old runs is different for the histogram "Number Of Track" (layout #3, plot #1). This difference is due to a change in the CMSSW release (the x axis was 200 and later was changed to 300).

E/Gamma POG instructions instructions
(last updated: Jamie Antonelli - Feb 2010)

  • This is an issue with the webserver that is preventing many of the histograms from displaying, so for the time being the E/Gamma flag should be set in terms of other subsystem flags as follows:

ECAL & SiSTRIP & Pixel = GOOD ==> EGamma = GOOD
ECAL || SiSTrip || Pixel = BAD/EXCL ==> EGamma BAD (which is in anycase a standard rule for BAD runs)

  • The E/Gamma POG offline DQM is not as vital for cosmics running as it will be for collisions.
    For cosmics running, BAD should be applied for runs with high statistics (>50M) in which the shift histograms differ greatly from the reference histograms. GOOD should be applied in any other case.

Jet/MET POG instructions
(last updated: )

Basically follow the standard instruction at this twiki.

  • IMPORTANT: If your certification results change wrt to previous rerecos or express stream, PUT a comment why (even if GOOD ) and send an email to the DQMShiftOfflineJetMET experts, so they are aware.
  • If plots are missing: send an email to the DQMShiftOfflineJetMET experts, so they are aware.

  • Try to use Jet*** datasets (Jet PD/JetMET PD/JetMETTau PD) if available. In the Minimum Bias dataset you see sometimes low pt spikes. Cross check with Express Stream and Jet PD (less sensitive to these issues)! No spikes there ->mark GOOD
  • If ECAL = EXCL || HCAL = EXCL, mark the run BAD.
  • If ECAL = BAD || HCAL = BAD: we do not automatically mark runs BAD even if ECAL, HCAL etc consider runs as bad. Check the JetMET plots! But, runs with test such as B-field off, Time scans should be marked as BAD. It's to risky to use them for physics analysis.
  • If you see a Hot Spot in the Calo Tower plot, mark the run only BAD if you see this effect also in other shift plots, otherwise GOOD. If there are white holes in the plot (HCAL parts missing in the read out), mark the run BAD.
  • Some discrepancies with the reference histograms can be observed since a new release is used for data processing. The typical example is the reduction of the MET tail.
  • You may observe discontinuity in jet pt distributions, but they may be due to different triggers with different prescales. Do not mark those runs bad automatically..
  • You will find that tcmet and pfmet plots are empty in some runs or spikey, but do not mark those runs bad automatically. If the calomet plots look ok, please keep the runs GOOD.

Muon POG instructions
(last updated: Silvia Goy Lopez - 24 Feb 2010)

  • Muon POG offline DQM is under review. At this moment is only based on a subset of the available information, as explained in the main twiki.

  • No differences are expected with respect to previous processings. The reprocessing does not include any feature to recover any particular muon problem. Therefore standard certification would still be valid and should provide the same flags as in the original dataset.
  • The only exception is for runs 142317,142318,142319, where there was a PS accident in the TOB. This incident does not show an effect on the results of the muon quality tests. However it has been decided to mark these runs as BAD for muons for consistency in any case. For all other runs please follow standard muon instructions.

Track POG instructions
(last updated: )

Review Status
(last updated: -- VirginiaAzzolini - 24-Feb-2009)

Reviewer/Editor and Date Comments
Paolo Bellan - 29 Jun 2010 DT instructions reviewed
ValdasRapsevicius - 15-Mar-2010 Removed outdated entry - CSC offline DQM is fine now.
VirginiaAzzolini - 24-Feb-2010 Reviewed for outdated entries before start up.
Ilaria Segoni - 27 Jan 2010 updated instructions relative to Tracker HV, Jan23rd rereco, cleaned up obsolete part of General section
Virginia Azzolini - 28 Oct 2009 added instruction for Reprocessed Runs certification
Volker Adler - 14 Aug 2009 Created new page and entered first entries for switch from /Cosmics to /ExpressMuon
Volker Adler - 19 Aug 2009 Reviewed for outdated entries before general clean-up.

-- KaoriMaeshima - 10-Jan-2011

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2011-01-10 - KaoriMaeshima
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 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