variablesToNtuple.py

#!/usr/bin/env python3
 
 
 
# The VariablesToNtuple module saves variables from the VariableManager
# to a candidate-based (or event-based) TTree
#
# For full documentation please refer to https://software.belle2.org
# Anything unclear? Ask questions at https://questions.belle2.org
 
import basf2
import modularAnalysis as ma  # a shorthand for the analysis tools namespace
 
mypath = basf2.Path()  # create a new path
 
# add input data and ParticleLoader modules to the path
ma.inputMdstList('default', [basf2.find_file('analysis/tests/mdst.root')], path=mypath)
ma.fillParticleLists([('K-', 'kaonID > 0.2'), ('pi+', 'pionID > 0.2')], path=mypath)
ma.reconstructDecay('D0 -> K- pi+', '1.750 < M < 1.95', path=mypath)
ma.matchMCTruth('D0', path=mypath)
 
# Add the VariablesToNtuple module explicitly.
# This will write out one row per candidate in the D0 list
mypath.add_module('VariablesToNtuple',
                  particleList='D0',
                  variables=['dM', 'isSignal', 'mcErrors', 'p', 'E',
                             'daughter(0, kaonID)', 'daughter(1, pionID)'],
                  fileName='CandidateVariables.root')
 
# Add another instance of the VariablesToNtuple module.
# If the particle list is empty one row per event is written to the Ntuple,
# but all the variables to specify have to be event-based
mypath.add_module('VariablesToNtuple',
                  particleList='',
                  variables=['nTracks', 'isMC', 'year'],
                  fileName='EventVariables.root')
 
# you might also like to uncomment the following, and read the help for the
# convenient wrapper function:
# print(help(ma.variablesToNtuple))
 
# process the data
basf2.process(mypath)
print(basf2.statistics)