Analysis Subsystems

Complete: 4


Provide a standard organization of packages containing code that defines algorithms and data formats for analysis. This note was revised after the initial proposal.

Analysis Code Organization

Analysis code should be divided in two types of packages:
  • definition of persistent data formats
  • definition of algorithms and framework modules

Persistent data formats for analysis that are not intended to be stored in RECO or AOD are convenient to use in analysis skims in order to add new quantities to the standard AOD/RECO for interactive analysis with FWLite or for subsequent analysis via framework modules.

According to CMSSW requirements, Framework modules can't be defined in the same package where persistent data are defined. This will avoid clashes among plug-in libraries.

Analysis Specific Subsystems

The proposed standard for analysis specific subsystems is:

  • AnalysisDataFormats/
  • XYZAnalysis/

Where XYZ would correspond to the name of the Physics Analysis Group. It is important that all data formats for all analysis groups are located under the same sub-system, namely AnalysisDataFormats, because this will become part of the FWLite distribution.

Object types designed to be stored as part of the RECO/AOD should instead be defined, as usual, in the subsystem DataFormats.

Analysis groups (both Physics Analysis Groups and Detector Performance Groups) can define one or more package for their analysis in the two subsystems with clear naming conventions. For instance, we could have:

  • AnalysisDataFormats/ZReco
  • ElectroWeakAnalysis/ZReco


  • AnalysisDataFormats/Tracking
  • TrackingAnalysis/Tracking

Package Requests

The request of new packages, once agreed with the group, should be done via the Tag Collector following the link to "Create New Package".

If a subsystem is not existing yet, it will be created automatically the first time a new package is requested in that subsystem.

Package Administrators

Conveners of Physics Analysis Groups (PAG), Physics Objects Groups (POG) and Detector Performance Groups (DPG) should appoint one or a two administrators for the packages that will be requested under their groups. The administrators will also act as contact persons with the Analysis Tools group.

Review Status

Reviewer/Editor and Date (copy from screen) Comments
LucaLista - 25 Jan 2007 page last content
JennyWilliams - 02 Feb 2007 editing to include in SWGuide

Responsible: LucaLista
Last reviewed by: Reviewer

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r8 - 2007-07-27 - DavidLange

    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback