Combine Triggered and Triggerable outputs, define MC trigger bits

[michaelmackenzie]

This defines MC trigger bits with bits below 100 (where the real triggers begin) but beyond what was likely used previously. Users will now have both triggered events and "triggerable" events (in the case of MC processing) in a single dataset, where checking the trigger results for path names or bits will be necessary when handling MC from now on instead of relying on the dataset to select the OR of the triggers of interest.

This should reduce the output dataset tape usage by about a factor of 2 (due to the high overlap between triggerable and triggered), while also making trigger efficiency checks easier on users.

[FNALbuild]

Hi @michaelmackenzie,
You have proposed changes to files in these packages:

• JobConfig

which require these tests: build.

@Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main.

⌛ The following tests have been triggered for 69fb87d: build (Build queue - API unavailable)

About FNALbuild. Code review on Mu2e/Offline.

[FNALbuild]

☀️ The build tests passed at 69fb87d.

Test	Result	Details
test with	✅	Command did not list any other PRs to include
merge	✅	Merged 69fb87d at 408fdd7
build (prof)	✅	Log file. Build time: 04 min 47 sec
ceSimReco	✅	Log file.
g4test_03MT	✅	Log file.
transportOnly	✅	Log file.
POT	✅	Log file.
g4study	✅	Log file.
cosmicSimReco	✅	Log file.
cosmicOffSpill	✅	Log file.
ceSteps	✅	Log file.
ceDigi	✅	Log file.
muDauSteps	✅	Log file.
ceMix	✅	Log file.
rootOverlaps	✅	Log file.
g4surfaceCheck	✅	Log file.
FIXME, TODO	✅	TODO (0) FIXME (0) in 0 files
clang-tidy	✅	0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 69fb87d after being merged into the base branch at 408fdd7.

For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

[FNALbuild]

📝 The HEAD of main has changed to 1b4b11f. Tests are now out of date.

[brownd1978]

This is an important upgrade that will require changes to all analysis workflows.

Beyond the scope of this PR, I notice there's no KL triggerable path. That isn't needed for current Extracted digitization, but it will be needed for FieldOff digitization, including run1b scenario.

[michaelmackenzie]

@FNALbuild run build test

[FNALbuild]

⌛ The following tests have been triggered for be154d1: build (Build queue - API unavailable)

[FNALbuild]

☀️ The build tests passed at be154d1.

Test	Result	Details
test with	✅	Command did not list any other PRs to include
merge	✅	Merged be154d1 at 192f431
build (prof)	✅	Log file. Build time: 04 min 35 sec
ceSimReco	✅	Log file.
g4test_03MT	✅	Log file.
transportOnly	✅	Log file.
POT	✅	Log file.
g4study	✅	Log file.
cosmicSimReco	✅	Log file.
cosmicOffSpill	✅	Log file.
ceSteps	✅	Log file.
ceDigi	✅	Log file.
muDauSteps	✅	Log file.
ceMix	✅	Log file.
rootOverlaps	✅	Log file.
g4surfaceCheck	✅	Log file.
FIXME, TODO	✅	TODO (0) FIXME (0) in 0 files
clang-tidy	✅	0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at be154d1 after being merged into the base branch at 192f431.

For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.