Combine Triggered and Triggerable outputs, define MC trigger bits #484
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.