Opened 9 years ago

Closed 7 years ago

Last modified 5 years ago

#1068 closed enhancement (duplicate)

[trigger-sim] traysegment should read GCD from frame-stream not file

Reported by: Marcel Zoll Owned by: Alex Olivas
Priority: normal Milestone:
Component: combo simulation Keywords:
Cc:

Description

currently the trigger-sim tray-segment needs the pointer/path to the GCD file to configure itself. It should be possible to write the subordinated modules as such that they can read the information from the stream of frames!

the tray-segment is for example used in the simprod-scripts/segments:

tray.AddSegment?(trigger_sim.TriggerSim?, name+'_triggersim',

gcd_file=dataio.I3File(GCDFile), # for trigger auto-configuration

...
)

Change History (8)

comment:1 Changed 9 years ago by Alex Olivas

  • Component changed from cmake to simulation
  • Milestone set to September 2015
  • Status changed from new to accepted

You'd think so, and I have to admit when I accepted this ticket I couldn't quite remember off the top of my head, why it required a GCD file.

It requires a GCD file because it uses that to determine which modules to add to the tray. Once they're added they do actually figure out how to configure themselves from the status in the stream.

I can't see good ways to do this right now, for example, having three instances of the SMT trigger and having them disable themselves if they don't find the information they're looking for in the trigger status. We'd also probably have to disable ULEE support, but that's not the worst decision ever. ULEE shouldn't really be around anymore anyway.

We can provide a base segment without auto-configuration support or keep a running dictionary of modules and config_ids for each season, which shouldn't be too bad. The segment could then use that if gcd_file is None.

In any case, I'm kicking this can down the road a couple months until we could come up with a better implementation.

comment:2 Changed 9 years ago by Alex Olivas

The way to go (mostly cweaver's idea) is to make triggers standalone classes that an I3TriggerModule manages. On the DetectorStatus? stop it can figure out which triggers to instantiate based on what's in the I3TriggerStatus object.

The DAQ stop would just run each trigger, passing the launch map to it, collect the resulting triggers, and put them in the frame.

comment:3 Changed 9 years ago by Alex Olivas

  • Milestone changed from September 2015 to November 2015

Development has started on a branch, but needs to be put on hold for the time being. Gotta get releases out.
http://code.icecube.wisc.edu/svn/projects/trigger-sim/branches/trigger_module_refactor

comment:4 Changed 9 years ago by Alex Olivas

  • Milestone changed from November 2015 to IceSim 5.0

comment:5 Changed 8 years ago by Alex Olivas

  • Milestone changed from IceSim 5.0 to IceSim 5.1

This is not going to make it into 5.0. Pushing to 5.1.

comment:6 Changed 8 years ago by Alex Olivas

  • Summary changed from Trigger-sim traysegment should read GCD from frame-stream not file to [trigger-sim] traysegment should read GCD from frame-stream not file

comment:7 Changed 7 years ago by Alex Olivas

  • Resolution set to duplicate
  • Status changed from accepted to closed

Folded into #1933.

comment:8 Changed 5 years ago by Alex Olivas

  • Milestone IceSim 5.1 deleted

Milestone IceSim? 5.1 deleted

Note: See TracTickets for help on using tickets.