- Introduction
- Structure
- How to get the version of EventNtuple
- How to Analyze an EventNtuple
- How to Create an EventNtuple
- Validation
- Tagging a New Release
- Notes for Developers
- Previous Verisons
- Other Useful Links
The EventNtuple is a simplified data format that can be used for Mu2e analyses.
The EventNtuple structure is complex. Some branches consist of a single object (e.g. evtinfo), some are vectors of objects (e.g. trk) and some are vectors-of-vectors of objects (e.g. trksegs).
A list of branches is available
The help understand what all the branches and leaves mean, we have an ntuplehelper tool
For versions of EventNtuple later than v6.3.0, we store the version number in the ROOT file. You can check the version number with the checkEventNtuple tool:
checkEventNtuple file1.root file2.root
To help with analyzing the EventNtuple given its complex structure, we have two sets of utilities:
Feel free to send questions, comments, or suggestions for improvement to the #analysis-tools Slack channel.
In case you need to create your own EventNtuple you can do the following from a clean login in your working directory with the list of files you want to run over in a text file called your-art-filelist.txt:
mu2einit
muse setup EventNtuple
mu2e -c EventNtuple/fcl/from_mcs-mockdata.fcl -S your-art-filelist.txt
This will create a file called nts.owner.description.version.sequencer.root that contains the EventNtuple. The EventNtuple will then be in the ROOT file as EventNtuple/ntuple.
Note: Other fcl files are available. See table here to see if another one is more appropriate for your use case.
Notes for developers contributing to EventNtuple are here
Validation scripts and instructions are here
Don't forget to set the new version number in src/EventNtupleMaker_module.cc!
The version history of EventNtuple is here.