Skip to content

Mu2e/EventNtuple

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

EventNtuple

Table of Contents

  1. Introduction
  2. Structure
  3. How to Analyze an EventNtuple
  4. How to Create an EventNtuple
  5. Validation
  6. Notes for Developers
  7. Previous Verisons
  8. Other Useful Links

Introduction

The EventNtuple is a simplified data format that can be used for Mu2e analyses.

Structure

The EventNtuple structure is complex.

A list of branches is available

The help understand what all the branches and leaves mean, we have an ntuplehelper tool

How to Analyze an EventNtuple

To help with analyzing the EventNtuple given its complex structure, we have two sets of utilities:

  • RooUtil for ROOT-based analyses, and
  • PyUtil for python-based analyses.

Both of these are currently undergoing rapid development. Feel free to use these prototypes and let us know your thoughts.

How to Create an EventNtuple

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

Notes for developers contributing to EventNtuple are here

Validation

Validation scripts and instructions are here

Previous Versions

The version history of EventNtuple is here.

Upgrading from v5 to v6

  • For analyzers: a list of branch/leaf/name changes is here
  • For developers: instructions to update your development area are here

Other Useful Links