You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As for using a regular ToolHandle, create it with an auto-declaring inline constructor, e.g. change:
asg::AnaToolHandleTrig::TrigDecisionTool m_trigDec;
to:
ToolHandleTrig::TrigDecisionTool m_trigDec {this, "trigDec", "Trig::TrigDecisionTool/TrigDecisionTool"};
And then move the configuration to python, e.g. something like:
addPrivateTool (alg, "trigDec", "Trig::TrigDecisionTool")
addPrivateTool (alg, "trigDec.ConfigTool", "TrigConf::xAODConfigTool")
alg.trigDec.TrigDecisionKey = "xTrigDecision"
and then you don't need anything in the constructor and in initialize() you just need:
ANA_CHECK (m_trigDec.retrieve());
Please note that the trigger people are always very insistent that we can't just prepare some trigger sequence that will work for everyone, but that we will need a number of sequences for different cases and then there will still be a sizable number of users who need something custom just for their analysis. I don't know if that is an accurate assessment or if they are just really proud of how complicated the trigger is.
Cheers,
Nils
The text was updated successfully, but these errors were encountered:
From Nils:
As for using a regular ToolHandle, create it with an auto-declaring inline constructor, e.g. change:
asg::AnaToolHandleTrig::TrigDecisionTool m_trigDec;
to:
ToolHandleTrig::TrigDecisionTool m_trigDec {this, "trigDec", "Trig::TrigDecisionTool/TrigDecisionTool"};
And then move the configuration to python, e.g. something like:
addPrivateTool (alg, "trigDec", "Trig::TrigDecisionTool")
addPrivateTool (alg, "trigDec.ConfigTool", "TrigConf::xAODConfigTool")
alg.trigDec.TrigDecisionKey = "xTrigDecision"
and then you don't need anything in the constructor and in
initialize()
you just need:ANA_CHECK (m_trigDec.retrieve());
There also seems to be a Trigger CP sequence defined, but I never used it: https://gitlab.cern.ch/atlas/athena/-/blob/21.2/PhysicsAnalysis/Algorithms/TriggerAnalysisAlgorithms/python/TriggerAnalysisSequence.py
Please note that the trigger people are always very insistent that we can't just prepare some trigger sequence that will work for everyone, but that we will need a number of sequences for different cases and then there will still be a sizable number of users who need something custom just for their analysis. I don't know if that is an accurate assessment or if they are just really proud of how complicated the trigger is.
Cheers,
Nils
The text was updated successfully, but these errors were encountered: