-
Notifications
You must be signed in to change notification settings - Fork 1
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
Ideas for the integration of BrainGlobe atlases within napari #1
Comments
What should this napari plugin be called? |
I like |
The Layer group PR to Napari has not been merged yet. A possible temporary approach would be to encapsulate the conversion from BG atlas api Atlases to our napari atlas type in just one place, so we can easily change how this is done later? For now, this would just add appropriate layers for each of the images and meshes to napari? |
Yeah I think so, unless there's something we can do to help push the layer group PR forwards. |
FYI for loading meshes into napari - https://github.com/GenevieveBuckley/napari-meshio |
@adamltyson what are your thoughts on when/how users can add meshes as napari surface layers?
|
I'm leaning towards 2. It could be a tree like structure with checkboxes. I think this is what the brainrender GUI uses. |
I'm also not sure 3. would be much use to people. I can see instances when it might be helpful to visualise a sub-sub division of area A along with the whole of area B. |
Currently BrainGlobe atlases are used by napari plugins (e.g.
brainreg
,brainreg-segment
), but these are not accessible by napari plugins directly (only by usingbg-atlasapi
in the plugin code). It would be useful to be able to load, visualise and manipulate these atlases for many reasons, e.g.:As a first pass, my idea is to create a napari plugin that will include some of the functionality of the brainglobe atlas API and CLI, including:
bg-atlasapi
represents atlases as an abstract object. It would also be useful to do the same within napari. i.e. represent all the information within an atlas object as a "thing". It won't be a new layer type, but as close to this as possible (layer group?).A sketch of my idea:
cc @alessandrofelder @dstansby
The text was updated successfully, but these errors were encountered: