search

xpdAcq / mission-control

Releases, Installers, Specs, and more!
0 stars 4 forks source link

detector switch : configure image_field at analysis window #136

Closed adelezh closed 5 years ago

adelezh commented 6 years ago

Can we configure image_field at analysis window instead of edit xpd.yml at /.config/acq/

CJ-Wright commented 6 years ago

Ideally this data would be in the start document(maybe?)

CJ-Wright commented 6 years ago

think this is a plan:

  1. We chunk the raw data pipelines (see https://github.com/xpdAcq/xpdtools/pull/51)
  2. We add the calibration to each detector so that the calibration is now in the descriptors.
  3. We produce sub-pipelines for each detector. Each sub-pipeline pulls the calibration from the descriptor. Note that this means we need to handle stop documents in SHED elegantly, since it is very possible that we will get no data through a pipeline (eg we only ran with 1 detector but three are registered). There are two potential outcomes, we either issue a start and stop with no data or don't issue a start or stop (aka it never happened). I think the second option is best since we don't create a bunch of useless headers. This means that on stop document we need to check if any data entered the pipeline (including buffers). If nothing came in then we don't issue any documents. Note that we should add the available detectors to the start document so we know what pipelines to build.

This approach also helps with the "use multiple detectors at once use case" and so might be a good overall approach.