discrepancy in voxel size/FOV
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 249
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
When I try to set leap image volume parameters using an initialState.sct file, or when I set the parameters using setDefaultVolume(), I get a slight difference. Consider an image that is S x S, and the pixelsize is P
When using initialState.sct, the FOV = S x P, but when I use setDefaultVolume(), the FOV =(S-1) x P.
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
Compare the volume-parameter handling for initialState.sct with setDefaultVolume(), focusing on how an S × S image and pixel size P produce their field of view. Reproduce both cases and verify that the resulting FOV is consistent with the intended convention; the issue is done when both paths agree.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100