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

Add freesurfer and brainvoyager options to LN2_RIMIFY #74

Open
1 of 2 tasks
ofgulban opened this issue Apr 12, 2023 · 2 comments
Open
1 of 2 tasks

Add freesurfer and brainvoyager options to LN2_RIMIFY #74

ofgulban opened this issue Apr 12, 2023 · 2 comments

Comments

@ofgulban
Copy link
Collaborator

ofgulban commented Apr 12, 2023

There are requests to easily convert such segmentation files (e.g. whole brain) to LayNii rim format and use e.g. LN2_LAYERS.
Therefore, I want to add two convenience flags to LN2_RIMIFY:

  • freesurfer (aseg)
  • brainvoyager (100 & 150, 240 & 243)
@ofgulban ofgulban modified the milestones: v2.5.0, v2.4.0 Apr 12, 2023
@layerfMRI
Copy link
Owner

layerfMRI commented Apr 14, 2023

I agree, this would be very useful for many people.
I think the relabeling of segmentation valued from freesurfer might be relatively straight forward. The harder part might be to have a documentation about how to convert freesurfer surfaces in freesurfer-space to the EPI space of functional slab protocols. I am not sure if you also envision the latter part?

@ofgulban
Copy link
Collaborator Author

ofgulban commented Apr 24, 2023

The harder part might be to have a documentation about how to convert freesurfer surfaces in freesurfer-space to the EPI space of functional slab protocols. I am not sure if you also envision the latter part?

I was planning to implement the easy part (relabeling of each voxel). So I am not planning to look into converting the surfaces. At least not within the scope of LN2_RIMIFY right now.

ofgulban added a commit that referenced this issue Apr 24, 2023
@ofgulban ofgulban modified the milestones: v2.4.0, v2.5.0 Apr 24, 2023
@ofgulban ofgulban removed this from the v2.5.0 milestone Jul 11, 2023
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

No branches or pull requests

2 participants