DiamondLightSource / DiamondLightSource/crystallography-bluesky
I15-1: Allow setting a calibrated temperature on the blower
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 21h 40m
- Merged PRs (30d)
- 8
Description
When a temperature collection is run we want to first calibrate the blower hardware for that temperature, this is done by:
1. There is a temperature calibrant plan that runs a data collection on a calibrant at a range of temperatures, for these the raw setpoints are used (do these collections also need the setpoints in the nexus or do we assume readback ~= setpoint?)
2. Beamline staff can manually run this
3. Processing is done - for now this is acceptable to be manual
4. A file is put somewhere that gives a mapping of set point -> calibrated setpoint
5. For future data collections this mapping is used to set the temperature
## Acceptance Criteria
- We can take calibration temperature datasets with no calibration on the device
- We can take regular datasets with some calibration on the device
Contributor guide
Research direction
Start by locating the temperature collection plans and the blower hardware control, then trace how setpoints are passed into regular data collections. Review how calibration data and the setpoint-to-calibrated-setpoint mapping can be represented and applied. Done means calibration datasets run without device calibration and regular datasets use an available calibration mapping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100