Page History

...

• Currently the Step object has two pieces of metadata that represent the scan step:  "docstring" and "value"
• The actual "complex" changes on a step are updated in the epics store (epics scans) or the appropriate configuration objects (configuration scans)
• We should support scanning multiple detectors at the same time
• Feels like that requires some known structure in the meta data, e.g. if we are scanning 3 epix detectors:
• Mikhail suggests maybe we should use json for the docstring instead of creating our own language?

formularule for the docstring:? "detname_scanname_step"
scanname "chargeinj7" means every 7th pixel
scanname "chargeinj3" means every 3rd pixel

step_value = 0
step_docstring = "epix0_chargeinj_0; epix3_chargeinj_0; epix7_chargeinj_0"

step_value = 1
step_docstring = "epix0_chargeinj_1; epix3_chargeinj_1; epix7_chargeinj_1"

...