-
Notifications
You must be signed in to change notification settings - Fork 56
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
Use of spatial null models on non whole-brain maps per hemisphere #79
Comments
Hey Peer sorry about the late reply! Also this is definitely a good place to ask questions! Best, |
Hi @justinehansen, thx for the reply and no problemo at all!
I thus basically mimics the existing workflows but adds the Thanks again. Best, Peer |
Hey @PeerHerholz , this sounds awesome!! We should totally add it to neuromaps. If you'd like, you could open a PR with the "rough" code and we could work with it from there? I'm flexible, happy to proceed however you see fit 🙂 (And there's obviously no urgency - can be whenever) |
Ahoi hoi everyone,
thank you very much for your hard and dedicated work on this fantastic resource.
I'm currently using
neuromaps
to compare some of the provided maps to maps obtained within my analysesand would like to ask a question regarding the null models (Sorry, I wasn't sure if y'all are answering questions through
neurostars.org. Thus, I'm very sorry if this is the wrong place to ask questions.).
My plan was to compare maps within a mask (parts of the temporal lobe) for each hemisphere separately using the
burt2020
approach. However, it seems that all related functions assume either whole-brain or parcellated maps from both hemispheres (e.g.compare_images
,get_surface_distance
, etc.). Therefore, it seems like I would have to compute thedistance matrix
ofvertices
within my mask and then usebrainsmash
to create thesurrogate maps
. However, I wanted to ask if that's actually the case or if I missed something.Sorry once more if this is not the right place to ask such questions.
Thanks again.
Best, Peer
The text was updated successfully, but these errors were encountered: