z-slices outside detected FOV should be zero, but are repeats of last valid slice
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 249
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
The attached modification of d01_standard_geometries.py demonstrated that if the number of detector rows is set so the detector z-span is less than the scaled recon volume, the slices outside the detected FOV are repeats of the last valid slice, but should be zero
[d01_standard_geometries_bug.py](https://github.com/user-attachments/files/23318470/d01_standard_geometries_bug.py)
Slice 511:
Slice: 266 is identical
Contributor guide
No contributing guide indexed for this repository
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 the reported behavior with the attached d01_standard_geometries_bug.py modification, then trace how detector rows and the scaled reconstruction volume determine z-slices. Done means slices outside the detected field of view contain zeros rather than repeats of the last valid slice; no specific test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100