CDF EventNtuple : Instructions

Instructions on how to add stuff ( namely ntuplizing a storableObject/bank)

The modules

The eN executable consists mainly of 4 modules ( in the package PADSMods):

HepRootManager() to manage the ROOT Tree
NtupleOutputModule to book /initialize the ntuplizers and capture data
UserNtupleModule ( optional) to allow the generic user to add her own branches to evtNtuple
FinalNtupleModule to do the final capture and clearData calls.

This structure allows to add a user module (UserNtupleModule) between NtupleOutputModule and FinalOutput module to fill private user branches. In the beginJob method of the user module just use the following commands:

_tManager = fileManager() ;

if (_tManager){

_tManager->cd("//AC++/eN");

_ntuple = &_tManager->retrieveNtuple("evtNtuple" );

}

return AppResult::OK;

When using a path different than AllPath, all the modules need to be added to it:
for example:
path enable myPath path
append myPath HepRootManager EZfilter eN eNFinal

Filling the branches is controlled via talk-to and there is a an easy filter (module EZFilter ) to select events based on simple cuts or for example L1/L2 trigger bits: example tcl files of how to run eN can be found in the PADSMods/test/ directory.

If you want to test new ntuplizers you need to addpkg -h PADSMods and edit :
NtupleOutputModule .hh and NtupleOutputModule.cc following the many examples already in.

Besides this you need to modify the GNUmakefile in order to include the right libraries needed to build the executable ( Namely your new MyObjects_ntuple library and MyObjects library, if not already in)