Project

General

Profile

Feature #2946

SelectEvents for analyzer modules

Added by Rob Kutschke almost 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Paul Russo
Category:
Navigation
Target version:
Start date:
10/10/2012
Due date:
09/30/2013
% Done:

100%

Estimated time:
48.00 h
Spent time:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration: 356

Description

art currently supports SelectEvents for output modules - the module will only be run if some expression on the completion status of trigger paths evaluates to true. We would like analyzers modules to also have this feature.


Related issues

Related to art - Feature #4361: Implement the selective disablement/renablement of modules [ds50daq-related]Closed07/17/201307/31/2013

Blocks art - Support #4731: Release new version with less alarming messages about trigger and end pathsClosed09/30/2013

History

#1 Updated by Marc Paterno almost 8 years ago

  • Status changed from New to Accepted

This worked is planned, but not yet scheduled.

#2 Updated by David Brown over 7 years ago

I'd like to give a concrete example to this request. A common use case is for a user to want to run the event display on a subset of events. Within art the natural way to do this is to write a filter which selects the interesting events, then pass them to the event display module. This doesn't work, as the event display is an observer, it lives in the endpath, and the endpath ignores filtering. We're left with the unpleasant choices of trying to incorporate filter functionality in the event display module, or having to write out intermediate files using the filter (since outputmodule is the only endpath module which can key to filters), and read them back in a separate event display process. This is of course just one example (I can think of many more). I'd like to hear from the art developers what they think the right way to do this is.

#3 Updated by David Brown over 7 years ago

I have a concrete implementation suggestion for this feature. Since art can support multiple end-paths, I suggest making the execution of a specific end-path contingent on a particular trigger path. This keeps the current default behavior plus allows selective endpaths. I'm imagining something like the following, though certainly you guys can come up with something better.

xxx : [ a, b, c]
yyy : [ d,e,f ]
trigger_paths : [xxx]
end_paths: [ yyy:xxx]

#4 Updated by Christopher Green about 7 years ago

  • Category set to Navigation
  • Status changed from Accepted to Assigned
  • Assignee set to Paul Russo
  • Target version set to 363

#5 Updated by Brendan Kiburg about 7 years ago

The g-2 experiment also wants to note that we desire this functionality.

Our current approach involves running art in two steps: One step where art produces that makes an intermediate file that outputs only the events we wish to analyze. In a second step, we read in the intermediate file and run the analyzer on all of those events.

This implementation of SelectEvents for analyzer modules would be a welcome addition for our purposes.

#6 Updated by Christopher Green almost 7 years ago

  • Target version changed from 363 to 1.08.00

#7 Updated by Christopher Green almost 7 years ago

  • Due date set to 09/30/2013
  • Target version changed from 1.08.00 to 1.09.00
  • Estimated time set to 48.00 h
  • Scope set to Internal
  • Experiment - added
  • SSI Package art added

Unclear why this attached itself to 1.08.00. It has not yet been implemented.

#8 Updated by Christopher Green almost 7 years ago

  • Status changed from Assigned to Resolved
  • Target version changed from 1.09.00 to 401
  • Start date changed from 09/07/2012 to 10/10/2012
  • % Done changed from 0 to 100

#9 Updated by Christopher Green over 6 years ago

  • Target version changed from 401 to 1.08.09

#10 Updated by Lynn Garren over 6 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF