[Image normalization workflow]: parameter to indicate how many frames should be combined
Open
Nobody has claimed this yet.
essimaging
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
In the image normalization workflow, we have:
- a dark run (camera shutter closed) that would typically have e.g. 5 frames
- an open beam run (camera open but no sample), typically also 5 frames
- a sample run with any number of frames
We will:
- sum the dark frames together (averaging out the noise)
- sum the open beam frames together (same reason)
- for the sample run, it could be that each frame represents one rotation (in the case of tomography), or it could be that 10 frames were recorded per rotation (also to average out noise).
Hence, we need to add an additional parameter on the workflow that says how many sample run frames should be combined for a single rotation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the image normalization workflow and the code that groups sample-run frames into rotations. Check how dark and open-beam frames are currently combined. Done means the workflow accepts a parameter for the number of sample frames combined per rotation and applies it to sample data without changing the dark or open-beam handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100