search

xpdAcq / mission-control

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

xpdAcq supports 2-detector positions #201

Closed sbillinge closed 3 years ago

sbillinge commented 3 years ago

Support 2 detector position scans in xpdAcq. Not sure if we just need new built-in scanplans or sthg else

Expected Behavior

tbd. Simply speaking it could be interleaved runs (near,far,near,far) etc. but it could be other logic. Need UCs from instrument scientists

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Priority

Your Environment

st3107 commented 3 years ago

some design:

  1. Xpdacq: inject information of "xraydectector: [det1, det2, ...]" to sepcify the names of the xray detector names that will be processed by PDFstream. PDFstream read the names to know what detectors are there.
  2. PDFstream: find the calibration data when the images come according to the detector names and the motor position. When it searches the value, it should have some tolerance, like x = 19.9999 can use the calibration from x = 20.0
  3. PDFstream: dump the calibraiton into the database with the detector name and the motor position.
  4. Xpdacq: when a run starts, load the calibraiton data from the database accordng to the motor position and the dector name. Here, in the start document, there should be a mapping from the detector names and motor positions to the calibration metedata.
st3107 commented 3 years ago 
def xpdacq_count(dets, indeps, calibration_md):