combine/merge 'acqMode=TRIGGERED/POST-MORTEM/SNAPSHOT' and 'triggerName=XXX' query parameter
The TRIGGERED
, POST-MORTEM
and SNAPSHOT
acquisition modes presently require an additional triggerName=XXX
filter query parameter.
This is not intuitive for new users or those who haven't read the documentation/description yet.
The proposal is to make the 'acqMode' value-type a string and to overload the possible 'acqMode` parameters such that if none of the other parameters is matching, the provided parameter is taken as (in order of matching)
- a snapshot time stamp if a
ms
suffix is specified (implying the 'SNAPSHOT' acquisition mode), - a trigger event name (implying the 'TRIGGERED' acquisition mode),
- POST-MORTEM acquisition if the event name matches a pre-defined post-mortem trigger name, or
- throwing an exception is none of the above is matching.
This would make it also more independent w.r.t. other (non-FAIR) timing systems and/or timing modeling.
Examples:
# | request | internal acquisition mode |
---|---|---|
1 | ...acqMode=0 | STREAMING |
2 | ...acqMode=STREAMING | STREAMING |
3 | ...acqMode=1 | FULL-CYCLE |
4 | ...acqMode=FULL-CYCLE | FULL-CYCLE |
5 | ...acqMode=0ms |
SNAPSHOT acquisition at 0 ms
|
6 | ...acqMode=101ms |
SNAPSHOT acquisition at 101 ms
|
7 | ...acqMode=CMD_BEAM_INJECTION |
TRIGGERED triggering on event CMD_BEAM_INJECTION
|
8 | ...acqMode=CMD_SEQ_START |
TRIGGERED triggering on event CMD_BEAM_INJECTION
|
7 | ...acqMode=CMD_POST_MORTEM_1 |
POST-MORTEM triggering on the first post-mortem event |
8 | ...acqMode=CMD_POST_MORTEM_2 |
POST-MORTEM triggering on the first post-mortem event |