[ESSSANS] Direct beam: dealing with insufficient signal
Open
Nobody has claimed this yet.
esssans
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
Based on chat with Judith about direct-beam iteration:
- NaN-regions should probably be masked, or else we will get NaN in the workflow result. Should we mask the direct beam file, or should the reduction workflow perform its own masking?
- Should NaN-regions be "filled" with approximate values based on non-NaN neighbours?
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 direct-beam iteration and reduction workflow referenced in the issue. Decide whether NaN regions belong masked in the direct-beam file or in the workflow, and whether neighbouring values should fill them; done means the chosen behavior prevents invalid workflow results and is documented or tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100