Users use two detectors in measurement or the detector distance actually change during the measurement. In this case, each image needs different calibration metadata according to the motor position and detector ID.
Current Behavior
Currenlty, our system can only process images from one detector using one calibration result. This result is the latest calibration result.
Possible Solution
Instead of saving a poni file at specific place, we need to dump the calibration "metadata" as actual data in a databroker database (or some other kinds of database) and when we need to use them, we query the database to find out what we need. The hash key for the calibration data can be the name of the detector and the positions of certain interesting motors. In the motor case, we need to have a tolerance for the position since the position may not be exactly the same every time.
Users use two detectors in measurement or the detector distance actually change during the measurement. In this case, each image needs different calibration metadata according to the motor position and detector ID.
Current Behavior
Currenlty, our system can only process images from one detector using one calibration result. This result is the latest calibration result.
Possible Solution
Instead of saving a poni file at specific place, we need to dump the calibration "metadata" as actual data in a databroker database (or some other kinds of database) and when we need to use them, we query the database to find out what we need. The hash key for the calibration data can be the name of the detector and the positions of certain interesting motors. In the motor case, we need to have a tolerance for the position since the position may not be exactly the same every time.
Steps to Reproduce (for bugs)
1. 2. 3.
Context
Priority
Your Environment