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

Remove the white outer layer on the mouse atlas in siibra explorer #1480

Open
Majpuc opened this issue Feb 4, 2025 · 3 comments
Open

Remove the white outer layer on the mouse atlas in siibra explorer #1480

Majpuc opened this issue Feb 4, 2025 · 3 comments

Comments

@Majpuc
Copy link

Majpuc commented Feb 4, 2025

The regions delineations of the mouse atlas are not visible in siibra explorer from the 3D window.
Could you remove the outer layer? You can ask Gergely if you don't find the atlas volumes.

Thanks!!

Image

Image

@xgui3783
Copy link
Member

xgui3783 commented Feb 4, 2025

I believe this can be achieved by disabling both Auxiliary Mesh and Remove frontal octant toggle at perspective view configuration

Image

When nothing is selected, we opt to show the root mesh (coloured white). We feel this is a good balance between giving user a good anatomical context and performance. (loading all meshes, even gzipped is a good 76mb. Espcially on a poor internet connection, this could be less than ideal)

@Majpuc
Copy link
Author

Majpuc commented Feb 4, 2025

No, not really. At least I can't get the view I pasted (the second one). This should be the view when no specific region is selected. It should be comparable to the rat atlas.

@xgui3783
Copy link
Member

xgui3783 commented Feb 4, 2025

Hmm, I understand the sentiment.

We are quite concerned about the speed at which the atlas loads. for waxholm v4, where all meshes were loaded downloads 384MB of compressed data, which took ~6 minutes on a fast 4g connection ( ~1.6 Mbps down ). mouse atlas took only 10 seconds on the same setting.

But I think we can come to a reasonable compromise:

  • by default, atlas viewer will "choose" to either load fast, or load all, based on user's connection speed^
  • user can override this to set to "load fast" or "load all" or switch back to "default"

^: However, it seems that the API checking user internet speed is quite shoddy (https://caniuse.com/?search=navigator.connection ). We can probably only realiably expect it to work on desktop chrome and android chrome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants