Project

General

Profile

Bug #23317

TriggerResults path ordering

Added by Wesley Ketchum about 2 months ago. Updated 9 days ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/24/2019
Due date:
% Done:

0%

Estimated time:
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

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 about 2 months 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 about 2 months ago

  • Occurs In 3.01.02 added
  • Occurs In deleted (3.01.02)

#3 Updated by Kyle Knoepfel about 2 months ago

Yeah, the redmine version-selection is somewhat error prone. I think I got it, though.

#4 Updated by Kyle Knoepfel about 1 month 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 16 days 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 9 days ago

Thanks, Giuseppe, for the reminder. We will take a look.

#7 Updated by Rob Kutschke 9 days ago

Mu2e is using the TriggerNamesService and has not had issues. The person doing the work is Giani Pezzullo.



Also available in: Atom PDF