LmToProjData should handle/check non-increasing time tags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
Julian Matthews reports that there are sometimes non-increasing time in HRRT data, or even Biograph.
He says that on (older?) Siemens scanners, the timing tag get reset to zero which is then scan start. Kris/Ben say that on mMR this doesn’t happen. Instead, the first timing tag is occasionally very high (feedback from Siemens says this value doesn’t mean anything).
What do we do with all this?
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 by locating the LmToProjData entry point and inspect how it reads and validates time tags. Compare the reported HRRT, Biograph, and mMR cases, then seek maintainer guidance on the intended behavior; the work is done when an agreed policy for non-increasing or anomalously high tags is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100