-
Notifications
You must be signed in to change notification settings - Fork 32
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
Cutting atlases out of mni_atlas_reader
#4
Comments
Awesome idea @rmarkello. |
@rmarkello - Yes, I think it should be split from this project. I think it makes sense to have a new repo where all of this can be combined. Anybody has any idea for such a repo? |
Not my idea! All credit to @chrisfilo and @miykael. I love the markdown table, though! That'll be a great launching pad. I'm deeply terrible at naming, but will happily vote on other suggestions! |
At lunch we came up with Corgi - cortical generalized inventory or something lile this. |
OMG I love it!
Best,
Chris
…On Tue, Aug 7, 2018 at 12:47 PM Michael Notter ***@***.***> wrote:
At lunch we came up with Corgi - cortical generalized inventory or
something lile this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOkpw9QpSwFsjE0v9fHxPi03qtlkc6pks5uOe7NgaJpZM4VytU->
.
|
There was some talk here at the hackathon about trying to splice the atlases out of the current repository and make them into their own repository, which could serve as a very useful resource for anyone looking for brain atlases! This question was previously raised on the BIDS Discussion List and some relevant discussion occurred there.
@PeerHerholz mentioned that Lead DBS has already collected a good number of atlases which might be a good place to start!
What are peoples' thoughts? Should a new repo be created to host atlases (this package could then grab that repo as additional "package data" when downloaded!). If so, what should the name be? @miykael
The text was updated successfully, but these errors were encountered: