The pitch in helical reconstruction
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 249
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hi, Recently, I've been working on reconstructing multi-energy photon-counting CT data using LEAP. The reconstruction geometry is for a helical scan with a pitch of 10 mm.
I noticed that in [d03,](https://github.com/LLNL/LEAP/blob/main/demo_leapctype/d03_helical.py#L34) there’s a parameter called leapct.set_normalizedHelicalPitch(0.5). What unit is used here, and why is it referred to as "normalized" helical pitch?
Alternatively, should I be specifying the pitch directly in the following line instead?
```
leapct.set_conebeam(numAngles, numRows, numCols, pixelSize, pixelSize, 0.5*(numRows-1), 0.5*(numCols-1), leapct.setAngleArray(numAngles, 360.0*numTurns), 1100, 1400, pitch = 10)
```
Thanks!
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 demo_leapctype/d03_helical.py at the set_normalizedHelicalPitch(0.5) call, then compare it with the set_conebeam call and its pitch argument. Determine the units and meaning of normalized helical pitch from the referenced example and relevant API definitions. Done means the parameter usage and relationship to a direct pitch value are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100