ML_norm not working as expected when a scanner with an odd number of crystals per block
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
a strange pattern is output in efficiencies and geometrical factor even when the model and the measured data are filled with 1s
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 reproducing ML_norm with a scanner having an odd number of crystals per block, using model and measured data filled with 1s. Compare the resulting efficiencies and geometrical factor with the expected uniform output shown by the report. The issue names no source file or test, so locating the relevant ML_norm entry point and regression coverage is part of the investigation; done means the strange pattern is resolved and the case is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100