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

Fsaverage transform #334

merged 20 commits into from Sep 27, 2019


Copy link

commented Jul 16, 2019

Incorporating transformation matrices to fsaverage transform


This comment has been minimized.

Copy link

commented Jul 16, 2019

@marklescroart marklescroart force-pushed the fsaverage_transform branch from 18ec720 to ab78e41 Aug 8, 2019

This comment has been minimized.

Copy link

commented Aug 14, 2019

This is almost ready to go. Pls to test. Relevant new function is


I think it would be good to additionally have a transparent function, perhaps a method of the vertex class (and maybe of the volume class too...?) that makes use of this function and the matrices it generates to do mapping to other subjects. For example,

vx = cortex.Vertex(data, subject).map_to('fsaverage', 'fiducial')

Not married to the idea of making this a method of vertex, nor to the name, but I like that syntax. Thoughts? Suggestions? Vetoes?

…handled in freesurfer re-import of flatmaps.
…to vertex object of another subject. Inheritance of Vertex, Volume, etc objects is complex.
… changes to function (preserving vmin, vmax, cmap)
@marklescroart marklescroart merged commit 3ad1939 into master Sep 27, 2019
1 check passed
1 check passed
continuous-integration/travis-ci/push The Travis CI build passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.