Project

General

Profile

Bug #25588

trigger bit reassignment

Added by Gianantonio Pezzullo about 2 months ago. Updated 17 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Kyle Knoepfel
Category:
Infrastructure
Target version:
3.09.00
Start date:
03/03/2021
Due date:
% Done:

100%

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

Description

Hello, I found a case where art re-assigns the trigger bits in a non-controlled way. Here is an example; if I set the otrgger_paths like I do below:

physics.trigger_paths[0] : path0
physics.trigger_paths[1] : path1
physics.empty_path       : []
physics.trigger_paths[2] : empty_path
physics.trigger_paths[3] : empty_path

physics.trigger_paths[4] : path2

art will assign to path2 the bit number 2 instead of 4.

Related issues

Related to art - Feature #24918: make "trigger_paths" a non-dense arrayResolved09/06/2020

History

#1 Updated by Kyle Knoepfel about 2 months ago

  • Description updated (diff)

#2 Updated by Kyle Knoepfel about 2 months ago

  • Status changed from New to Under Discussion

#3 Updated by Kyle Knoepfel about 1 month ago

  • Related to Feature #24918: make "trigger_paths" a non-dense array added

#4 Updated by Kyle Knoepfel 24 days ago

  • Target version set to 3.09.00

#5 Updated by Kyle Knoepfel 17 days ago

  • % Done changed from 0 to 100
  • Assignee set to Kyle Knoepfel
  • Status changed from Under Discussion to Resolved
  • Category set to Infrastructure
  • Experiment Mu2e added
  • Experiment deleted (-)

With the addition of feature #24918, the post-processed trigger paths for the example above will be:

trigger_paths: ["0:path0", "1:path1", "4:path2"]

Equivalent behavior will be achieved by specifying:

physics.trigger_paths: []
physics.trigger_paths[0]: path0
physics.trigger_paths[1]: path1
physics.trigger_paths[4]: path2

Also available in: Atom PDF