[Image normalization workflow]: Normalize by ROI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
Executive summary
It should be possible in the reduction workflow after normal normalization to also re-normalize again by the spectrum of a chosen ROI
Context and background knowledge
This requirement came up in a meeting with the ODIN team today where we saw Shuqi's work on reducing and analyzing a data-set on duplex steel. In his reduction, he noticed that the regions of the normalized image without a sample wasn't a horizontal line close to 1, as such he re-normalized his image using the spectrum from a region without the sample, a so-called open-area, which provided a much better reduced data-set that was easier to analyze.
Inputs
The normalized image after normal reduction and a chosen region of interest to re-normalize it with.
Methodology
Dividing the time-of-flight spectrum for each pixel with the spectrum gained from summing up a specific region-of-interest.
Outputs
A re-normalized image.
Which interfaces are required?
Integrated into reduction workflow
Test cases
We can try to get Shuqi's data to use for testing. I do not currently have it.
Existing implementations
No response
Comments
No response
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 reduction workflow that produces the normalized image and its handling of a chosen region of interest. Confirm how a region spectrum can be summed and divided into each pixel's time-of-flight spectrum, then use Shuqi's data if it becomes available to verify the resulting image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100