"Attempts to set up a grid submission using TrkAna fcl files with mu2ejobdef will result in an error relating to the fact that physics.trigger_paths and physics.end_paths are not defined."
I've added trigger_paths and end_paths in every file where TrkAnaTrigPath and/or TrkAnaEndPath appears. I know that this works for TrkAnaExtracted.fcl and TrkAnaReco.fcl.
There is one case where I'm not sure if I'm handling things correctly, which is in fcl/TrkAnaReco_wTrkQualFilter.fcl where there are two trigger paths: TrkAnaTrigPath and TrkAnaNegTrigPath.
Overall, I'm confident that this approach is correct for TrkAnaExtracted.fcl and TrkAnaReco.fcl, but I may need some advice for the others!
-Sam
PS: Maybe an alternative approach would to create an epilog.fcl, where you define the trigger and end paths globally?
Referring to Mu2e/TrkAna/issues/169:
"Attempts to set up a grid submission using TrkAna fcl files with
mu2ejobdef
will result in an error relating to the fact thatphysics.trigger_paths
andphysics.end_paths
are not defined."I've added
trigger_paths
andend_paths
in every file whereTrkAnaTrigPath
and/orTrkAnaEndPath
appears. I know that this works forTrkAnaExtracted.fcl
andTrkAnaReco.fcl
.There is one case where I'm not sure if I'm handling things correctly, which is in
fcl/TrkAnaReco_wTrkQualFilter.fcl
where there are two trigger paths:TrkAnaTrigPath
andTrkAnaNegTrigPath
.Overall, I'm confident that this approach is correct for
TrkAnaExtracted.fcl
andTrkAnaReco.fcl
, but I may need some advice for the others!-Sam
PS: Maybe an alternative approach would to create an
epilog.fcl
, where you define the trigger and end paths globally?