Bug #23317
TriggerResults path ordering
Description
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.
History
#1 Updated by Wesley Ketchum over 1 year ago
oof, I don't know what happened on the "Occurs In" part of this. Should be art v3_01_02 (e17:prof, if it matters).
#2 Updated by Kyle Knoepfel over 1 year ago
- Occurs In 3.01.02 added
- Occurs In deleted (
3.01.02)
#3 Updated by Kyle Knoepfel over 1 year ago
Yeah, the redmine version-selection is somewhat error prone. I think I got it, though.
#4 Updated by Kyle Knoepfel over 1 year ago
- Status changed from New to Accepted
We will investigate and develop an interface that allows looking up the bit number/path name by the path name/bit number.
#5 Updated by Giuseppe Cerati about 1 year ago
Isn't the TriggerNamesService (http://nusoft.fnal.gov/larsoft/doxsvn/html/TriggerNamesService_8h_source.html) supposed to do this lookup?
(except that it's not working for me now)
#6 Updated by Kyle Knoepfel about 1 year ago
Thanks, Giuseppe, for the reminder. We will take a look.
#7 Updated by Rob Kutschke about 1 year ago
Mu2e is using the TriggerNamesService and has not had issues. The person doing the work is Giani Pezzullo.
#8 Updated by Kyle Knoepfel 8 months ago
- Target version set to 3.06.00
#9 Updated by Kyle Knoepfel 7 months ago
- % Done changed from 0 to 100
- Assignee set to Kyle Knoepfel
- Category set to Infrastructure
The trigger-paths ordering bug has been fixed with commit art:17101a90.
#10 Updated by Kyle Knoepfel 7 months ago
- Status changed from Accepted to Resolved
#11 Updated by Kyle Knoepfel 6 months ago
- Status changed from Resolved to Closed