DiamondLightSource / DiamondLightSource/daq-queuing-service

i15-1: Full calibration/backgrounds logic

Open
#117 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
1
Avg merge
1d 3h
Merged PRs (30d)
16

Description

### My current understanding of what is needed for background and calibration scans
**Each experiment requires:**
- An air scan
- A scan of an empty capillary of the same type as used in the experiment (or the closest that's on the standards puck, it looks like there's some options in the schema that aren't on the puck described in https://diamondlightsource.slack.com/docs/T0E7J0J2V/F0B1HTV8N9H), at the range of temperatures in the experiment. Or at room temp if it's a room temp experiment.
- A scan with a known material (calibrant), at room temperature, in the same capillary type as used in the experiment (with the same caveat as above?)

Wherever the above can be shared between experiments within the same visit, they will be. Links to these scans needs to exist in the nexus file for the experiment for analysis.
~~I think that the top two are referred to as 'backgrounds' with the calibrant scan called a 'calibration'?~~ These are all types of 'background' scans

**Additionally:**
- Every so often, we need to calibrate the blower/cobra, see https://github.com/DiamondLightSource/crystallography-bluesky/issues/142

## Acceptance Criteria
- The above is handled in the queue plugin (other than device calibration which can be manual for now)

Contributor guide

Open the contributing guide

Research direction

Start by tracing the queue plugin and how experiment queue items produce Nexus files. Review the background and calibration requirements in this issue, including the linked blower/cobra calibration issue #142, and identify how scans can be shared within a visit. Done means the queue plugin handles the listed scans and links them in each experiment's Nexus file; device calibration may remain manual.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.