reading ECAT8 listmode for TOF scanners
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Until we merge the TOF PR, we cannot read listmode data for the mCT etc. however, this seems easy enough.
I believe we just need to modify
https://github.com/UCL/STIR/blob/7dc238f5ec228554f594f1f2228450eb4618472b/src/listmode_buildblock/CListRecordECAT8_32bit.cxx#L62
to first data
data_offset = this->data_offset / num_TOF_bins
(that's assuming that the TOF index runs fastest).
Uglier is that in the non-TOF code, we don't have info on TOF bins, but we could hardwire the mCT value in to test.
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 with src/listmode_buildblock/CListRecordECAT8_32bit.cxx at line 62 and review how the TOF PR represents the number of TOF bins. Test the proposed offset handling against mCT listmode data, including the non-TOF path; done means TOF listmode data from mCT and similar scanners can be read successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100