Tasks and Responsibilities of the Data Preparation area

This area is in charge of the the first three steps of analysis after the data arrive at the Tier0, and of the corresponding aspects for the simulated events:

1) Offline data quality and data treatment

2) Reconstruction, calibration and alignment at the (sub-)detector level, that is up to clusters in the individual calorimeters and tracks in the Inner Detector and Muon Spectrometer separately. This is performed for both the real data and the simulated data.

3) First combined reconstruction of physics objects (electrons, muons, jets, etc.) by putting together the information of various sub-detectors, and use of these objects to align and calibrate the various sub-detectors. These studies are made with both the real data and the simulated data. Here “first reconstruction” indicates that the target is to understand the detector performance rather than to optimize the algorithms for their use in different physics channels (the latter is a task of the Combined Performance WGs).

4) Improvement and maintenance of the sub-detector G4-simulations, in particular injecting more realism based on information from the data (simulation of electronic noise, cross-talk, dead regions, of the response variation with time, etc.).

Points 1), 2) and 4) above are the tasks and responsibility of the (sub-)systems and are described here

General tasks of the Data Preparation area are:

  • Provide coordination, as well as ATLAS-wide coherence, synchronization and discussion forum, for Points 1), 2), 4) above.
  • Provide the official list of good runs, including the luminosity information, based on the status of the trigger, DAQ and of the various sub-detectors.
  • Execute Point 3) above. This may be achieved by bringing together the relevant detector communities into common activities and discussions or by using the existing structure of the Combined Performance groups and adding a specific reporting line to the Data Preparation Coordinator (a more detailed development of the structure and internal organization of the Data Preparation area is beyond the scope of this document).
  • Carry the overall responsibility that data corrections, calibration and alignment constants for first-pass reconstruction at the Tier-0 are ready within a latency of 24 hours after data taking.
  • Validate (fully-simulated) Monte Carlo samples against the data.
  • Contribute to strategies and schedules for Software releases, Monte Carlo production (e.g. definition of samples with realistic detector response, etc.), and data (re-)processings, within the context of the TOB.

It should be noted that most of the above work will be based on physics samples (inclusive electron and muon streams, Z--> ll events, di-jet events, etc.). The links with the Trigger and Physics areas are therefore very strong.

-- SteinarStapnes - 25 Aug 2005 -- FabiolaGianotti - 21 Sep 2005

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2015-01-12 - NicolasBerger
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main 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