Config
Last updated
Last updated
The TRTFramework
config file utility has some standard options and the ability to use custom commands.
If you look at out "default" config file, you'll see all the standard options.
Option
description
GRL
Activitate the GRL tool (YES or NO)
GRLFiles
Comma separated list of GRL files to use, if default
use 2015+2016
PRWConf
Comma separated list of PRW config files (set to none
if PRW: NO
PRWLumi
Comma separated list of PRW lumi calc files (set to none
if PRW: NO
IDTS
Activate the InDetTrackSelectionTool
s (YES or NO)
Trig
Activate the trigger tools (YES or NO)
Trig.Electron
Comma separated list of single electron triggers to use
Trig.Dielecton
Comma separated list of dielectron triggers to use
Trig.Muon
Comma separated list of single muon triggers to use
Trig.Dimuon
Comma separated list of dimuon triggers to use
Trig.Misc
Comma separated list of misc. triggers to use
selectedTracks()
, selectedElectrons()
, and selectedMuons()
containers:Option
description
Tracks.p
Track momentum cut in GeV
Tracks.pT
Track transverse momentum cut in GeV
Tracks.eta
Track absolute value eta cut to use
Tracks.nSi
Track number of silicon hits cut (pixel + SCT)
Tracks.nPix
Track number of pixel hits cut
Tracks.nTRT
Track number of TRT hits cut
Tracks.nTRTprec
Track number of TRT precision hits cut
Electrons.p
Electron momentum cut in GeV
Electrons.pT
Electron pT cut in GeV
Electrons.eta
Electron abs eta cut
Electrons.UseTrackCuts
YES
or NO
to use track cuts on the associated track
Electrons.RelpT
relative pT cut
Electrons.TruthMatched
Require truth matched electron in MC
Electrons.FromZ
Require electron be truth from Z in MC
Electrons.FromJPsi
Require electron be truth from JPsi in MC
Electrons.FromZorJPsi
Require electron be truth from Z OR JPsi in MC
Muons.p
Muon cuts... Self explanatory.
Muons.pT
--
Muons.eta
--
Muons.UseTrackCuts
--
Muons.RelpT
--
Muons.TruthMatched
--
Muons.FromZ
--
Muons.FromJPsi
--
Muons.FromZorJPsi
--
To add a custom option, you simply define it in the config file, list so:
The main algorithm class xTRT::Algorithm
has two functions which will get the xTRT::Config
object (one templated function for non strings, and a specific one for strings), and you can grab a custom option from that (in your algorithm's histInitialize()
function you can do:
It is highly recommended to avoid calling this function in execute()
. If you have custom options you should define a member variable in your algorithm class (using //!
) and set it in histInitialize()
or initialize()
.