a value-jump error with axial scan FBP reconstruction
Open
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 249
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
when I use Projector class to project and fbp with an axial scan geometry, the reconstructed first slice and the last slice have a value-jump compared to the other slices in the middle, but there are no artefacts occured. why this happened?
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 with the Projector class and the axial-scan FBP reconstruction path, then reproduce the reported value jump by comparing the first and last slices with the middle slices. Trace the reconstruction inputs and slice-boundary handling to identify whether the behavior is expected or a bug; done means the cause and appropriate resolution are established.
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
- Needs clarification
- Newbie friendliness
- 25/100