GenerateTriggerFcl: Difference between revisions
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
</pre> | </pre> | ||
where <code>myInput.config</code> contains the list of the trigger paths you want to include in the fcl, together with their prescale factors if needed, <code>myTrigFcl.fcl</code> is the name of the file that will be generated by the script. | where <code>myInput.config</code> contains the list of the trigger paths you want to include in the fcl, together with their prescale factors if needed, <code>myTrigFcl.fcl</code> is the name of the file that will be generated by the script. | ||
By default, the generated fcl will include also the <code>ReadTriggerInfo</code> module in the output path; this module is a useful tool that provides summary info of the Trigger results. | |||
== | |||
==Trigger paths available== | |||
The simplest way is to run the python script with the <code>help</code> option: | The simplest way is to run the python script with the <code>help</code> option: | ||
<pre> | <pre> | ||
python Trigger/scripts/genTriggerFcl.py -h | python Trigger/scripts/genTriggerFcl.py -h | ||
</pre> | </pre> | ||
In the following we report the list of the currently available trigger paths: | |||
Revision as of 21:54, 24 November 2018
Intro
In this page, we organized the info needed to generate and run a Trigger executable within the Mu2e Offline.
How to generate and run a Trigger executable in the Offline
The Mu2e offline provides a dedicated python script Trigger/scripts/genTriggerFcl.py that allows the user to generate an fcl starting from a trigger configuration file. Examples of config file can be found on Trigger/scripts/inputs directory. The configuration file allows the user to set a general event prescale factor and also a second prescale factor that is applied to the good events.
caloCosmicMuon 10 100 tprDeMSeed cprDeMSeed ...
To run the python script you need to use the following command:
python Trigger/scripts/genTriggerFcl.py -c myInput.config -o myTrigFcl.fcl
where myInput.config contains the list of the trigger paths you want to include in the fcl, together with their prescale factors if needed, myTrigFcl.fcl is the name of the file that will be generated by the script.
By default, the generated fcl will include also the ReadTriggerInfo module in the output path; this module is a useful tool that provides summary info of the Trigger results.
Trigger paths available
The simplest way is to run the python script with the help option:
python Trigger/scripts/genTriggerFcl.py -h
In the following we report the list of the currently available trigger paths: