Author: Initially Christian Hansen, then mostly Yoshi Uchida (with major contributions from Clark McGrew and Thomas Lindner)

Description

Writes out event information in a summarised, pure-ROOT format in a modular way.

Introduction

eventAnalysis sits at the end of the chain of offline software that is the nd280 suite and handles information coming from all the subsystems.

All the packages that work upstream of eventAnalysis save their output in the oaEvent format, which is fully flexible and can contain everything from raw data blocks to simulated and reconstructed event information with associated errors etc. These files tend to be very large and contain a lot of low-level information.

eventAnalysis reduces this information and puts them in pure-ROOT format and provides tools to make this format as easy to use as possible.

eventAnalysis "modules" represent classes which distil the event information into mutually-related chunks. Each module saves a tree to the output analysis file. These are selected and run from the application RunEventAnalysis.exe, using the event loop in the class TAnalysisLoop.

The tools to read in the eventAnalysis files and perform analyses reside in the analysisMasterTools package.

Instructions on reading eventAnalysis files can be found at analysisMasterTools.

Writing Analysis Output Files

The infrastructure for writing out analysis files is intended to be relatively stable once the general reconstruction and analysis chain is more mature. Until then, we expect more modules (which define the trees that are written out) to appear in eventAnalysis and some evolution in the selection of modules which are run by default.

Documentation on running eventAnalysis and creating modules can be found at Creating Analysis Output Files using eventAnalysis.

Truth Information

Information about the truth information can be found here Truth information stored in an eventAnalysis file.