More advanced deadtime accounting (Livetime Counter)

[MRiganSUSX]

We currently have a simple code to do basic deadtime accounting: LivetimeCounter. This should be revisited and the logic updated. Also check that this works with trigger replay app.

[ArturSztuc]

@MRiganSUSX can you provide more details on the "revised and logic updated" part? What needs updating in the LivetimeCounter? I'm split between closing the issue, or delaying it until replay app is merged (although, looking at the LivertimeCounter with replay should be part of tests before the replay is merged...)

[MRiganSUSX]

@ArturSztuc
The original implementation of the LivetimeCounter [LC] was made mostly from DAQ side/view. It (only) has 3 states:

• Live: triggering (or ready to)
• Dead: cannot trigger (forced)
• Paused: not triggering (by choice)

The original idea - although perhaps not anymore - was to also make this useful for physics 'measurements' that focus on trigger efficiency (physics sensitivity/efficiency). This would mean expanding the states (and propagating the changes in states). Additionally, the LC is (or at least was) only controlled by MLT with no other input (MLT of course has a link to DFO, so that indirectly affects it). So for example when MLT issued a trigger but the data was no longer available this would not be reflected in the LC.

I think Josh (or was it Alessandro) had few other ideas of how this could have been extended.

So my opinion is we should keep this open, but there should be a design discussion first; and it is not urgent.