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.

Sign up for GitHub

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

Jump to bottom

confirm space of data and atlases #23

Closed
wrgr opened this issue Feb 3, 2016 · 3 comments
Closed

confirm space of data and atlases #23

wrgr opened this issue Feb 3, 2016 · 3 comments
Assignees
@gkiar

Comments

@wrgr
Copy link
Contributor

wrgr commented Feb 3, 2016

We now read data with nibabel - confirm that headers and data are in a consistent (or at least not misleading to our algorithms space).

We discovered an issue when looking at them in mipav.
@wrgr
Copy link
Contributor Author

wrgr commented Feb 3, 2016

note that trt was nearly perfect with a totally weird set of atlases, although perhaps that just means we were registering to the wrong thing consistently?

@wrgr
Copy link
Contributor Author

wrgr commented Feb 4, 2016

@gkiar - fixed?

@gkiar gkiar closed this as completed Feb 4, 2016
@gkiar
Copy link
Collaborator

gkiar commented Feb 4, 2016

Yup, fixed using nilearn's resample. Also, atlases were re-aligned such
that the mask and parcellations overlay in both real and voxel space.

Greg Kiar gkiar07@gmail.com

On Thu, Feb 4, 2016 at 10:06 AM, William Gray notifications@github.com
wrote:

@gkiar https://github.com/gkiar - fixed?

—
Reply to this email directly or view it on GitHub
#23 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gkiar gkiar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wrgr @gkiar