cet-is » art

The bit ordering in the TriggerResults does not seem to follow the post-processed trigger_paths parameter ordering.

Example: in a uboone larsoft filtering job, trigger_paths looked like:

trigger_paths: [ "pi0", "NuCC", "ncpi0"]

But the detailed summary showed this:

TrigReport ---------- Path   Summary ------------
TrigReport  Trig Bit#        Run     Passed     Failed      Error Name
TrigReport     1    0        496         68        428          0 NuCC
TrigReport     1    1        496          3        493          0 ncpi0
TrigReport     1    2        496          5        491          0 pi0

That is, it looks like it gets resorted alphabetically? Though I wouldn't know that for sure.

I can provide more details as necessary, but would probably be best to reproduce in a simple test setting.