Lima: Accumulation mode is not persistent
In the Lima implementation of BLISS, the acq_mode
is not a setting but something passed to the detector with an acq_settings
.
For example people use to setup that with a DefaultChain
.
- device: $lima_simulator
acquisition_settings:
acq_mode: ACCUMULATION
For tomo beamline people use see this param as a setting: Something you setup in your detector, and that's it. You use the detector in this state when it is part of the scan.
For now in the ebs-tomo project, this setting will be implemented directly inside one of our dedicated detector tomo/ebs-tomo#81.
- Could we imagine this setting to be part of the BLISS lima controller?
For example
lima_simulator.acq_mode = "DEFAULT" # Actual behaviour in BLISS
"SINGLE"
"ACCUMULATION"
- Could we imagine an improvement of the yml default chain to pick the right setup based on this param?
For example we have to switch between such chains depending on the acq_mode. Could we imagine to merge that config together?
# Actually
- name: MRTOMO_ext_chain
plugin: default
chain_config:
- device: $det3_edgehs
acquisition_settings:
acq_trigger_mode: EXTERNAL_TRIGGER_MULTI
master: $musst
- name: MRTOMO_ext_chain_acc
plugin: default
chain_config:
- device: $det3_edgehs
acquisition_settings:
acq_trigger_mode: EXTERNAL_TRIGGER_MULTI
acq_mode: ACCUMULATION
master: $musst_acc
# For example
- name: MRTOMO_chain
plugin: default
chain_config:
# In case of the default
single_chain_config:
- device: $det3_edgehs
acquisition_settings:
acq_trigger_mode: EXTERNAL_TRIGGER_MULTI
master: $musst
accumulation_chain_config:
- device: $det3_edgehs
acquisition_settings:
acq_trigger_mode: EXTERNAL_TRIGGER_MULTI
acq_mode: ACCUMULATION
master: $musst_acc
Edited by Valentin Valls