Slice-timing correction representation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 18
- Avg merge
- 21h 48m
- Merged PRs (30d)
- 1
Description
I haven't had the time to sit down and really understand this, but nipy has STC implemented as part of realign4d. It uses affine transforms, so I suspect we can find a compact serializable representation of STC for nitransforms.
This is brought up in the context of attempting to reduce the outputs of preprocessing to a minimum while preserving flexibility for downstream uses. In the absence of an STC transform, the ST-corrected BOLD series would be a required output, if calculated.
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 reading the linked nipy file, algorithms/registration/groupwise_registration.py, to understand how STC is represented with affine transforms. Done means establishing and implementing a compact serializable STC representation for nitransforms, while clarifying whether the ST-corrected BOLD series remains a required output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100