Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Output fsLR meshes on subject surfaces #460

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

effigies
Copy link
Member

Closes #447.

Copy link

codecov bot commented Dec 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.21%. Comparing base (9a6385b) to head (7e93927).
Report is 5 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #460       +/-   ##
===========================================
+ Coverage   63.02%   74.21%   +11.19%     
===========================================
  Files          25       25               
  Lines        1947     1955        +8     
  Branches      242      245        +3     
===========================================
+ Hits         1227     1451      +224     
+ Misses        682      439      -243     
- Partials       38       65       +27     
Flag Coverage Δ
ds054 45.59% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@effigies effigies marked this pull request as ready for review December 12, 2024 20:47
@effigies
Copy link
Member Author

@tsalo Could I bother you for a review?

Copy link
Collaborator

@tsalo tsalo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks awesome!

The looping in init_resample_surfaces_wf goes a little over my head, but everything looks great.

One question- would it make sense to calculate the inflated and veryinflated surfaces in fsLR space, or would you prefer to leave that to the post-processing workflow?

@effigies
Copy link
Member Author

One question- would it make sense to calculate the inflated and veryinflated surfaces in fsLR space, or would you prefer to leave that to the post-processing workflow?

I don't have a strong preference not to do it, but I also don't want to hold up this feature on my understanding another. Feel free to open a follow-up issue.

@effigies effigies merged commit 7f2863a into nipreps:master Dec 12, 2024
18 checks passed
@effigies effigies deleted the enh/fslr_surfs branch December 12, 2024 21:42
effigies added a commit to nipreps/fmriprep that referenced this pull request Dec 17, 2024
effigies added a commit that referenced this pull request Dec 19, 2024
0.17.0 (December 19, 2024)

New feature release in the 0.17.x series.

This release improves handling of datasets where T1w images are not
the primary modality. It also supports the generation of fsLR meshes
on the subject surface with the names:

    sub-<label>/anat/sub-<label>_hemi-<L|R>_space-fsLR_den-<label>_<surface>.surf.gii

These are useful for plotting CIFTI results on subject anatomy.

* FIX: Stop excluding FS minc_modify_header used during fallback registration (#453)
* ENH: Output fsLR meshes on subject surfaces (#460)
* ENH: Support spatial normalization to alternative modalities (#459)
* ENH: Add `t2w_file` output to `TemplateFlowSelect` (#457)
* MNT: Enable pre-release tests (#461)
* MNT: Complete transition from flake8/black to ruff (#435)
* MNT: Adopt src/ layout and tox (#458)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write out fsnative surface files registered to fsLR space
2 participants