Data Acquisition

Work Flow

When a data taking run is over(typically 8 hours):

Bulk rec uses majority of tier0 resources.

  • AOD: Analysis Object Data, physics output like electrons, muons, tracks, etc.
  • HIST: Histograms for monitoring.
  • ESD: Event Summary Data, contained detailed reconstruction output like calorimeter cells and tracking hits (not produced for physics_main)
  • DRAW/DESD: for selected events.

Calibration Loop over express stream:

  • Histograms to monitor.
  • Alignment work of inner tracker can be done.
  • The beamspot is determined (with new alignment).
Calibration loop (48hrs)

calib1.png

calib2.png

Defects and GRL: take Muon DQ as an example: MyMuonDQTutorial. Good quality of data, 'quality' measured by subdetector performance.

Practical info

Data Streams

Different data stream, coming from different trigger chain, for different purpose

Dataset Nomenclature:

nom.png

Useful links

-- RongkunWang - 2019-05-03

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng calib1.png r1 manage 129.1 K 2017-09-25 - 12:56 RongkunWang  
PNGpng calib2.png r1 manage 228.4 K 2017-09-25 - 12:56 RongkunWang  
PNGpng nom.png r1 manage 186.0 K 2017-09-25 - 12:56 RongkunWang  
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2019-05-03 - RongkunWang
 
    • 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-2020 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