Investigate scaling workflow.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
The scaling workflow fails and it's probably because there are too many nan values after processing.
We would like to go through step by step.
Here is the documentation of the overview of data processing:
https://scipp.github.io/essnmx/generated/modules/ess.nmx.scaling.average_roughly_scaled_intensities.html
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 with the linked documentation for ess.nmx.scaling.average_roughly_scaled_intensities and follow the data-processing overview step by step. Reproduce the scaling workflow failure, checking where NaN values appear after processing. Done means documenting the failing stage and the observed cause or a clear next step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100