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

Why is the browser stuck when visualizing the generated surface mesh? #160

Open
BoyuLyu opened this issue Oct 6, 2023 · 7 comments
Open

Comments

@BoyuLyu
Copy link

BoyuLyu commented Oct 6, 2023

I have been trying to visualize a large volume, with 2000x2000x1000 voxels. I created a configuration file using CloudVolume.create_new_info, which I set the chunk to be 100x100x50 voxels. And then I use the following code to create downsampled data and visualizing in neuroglancer. However, when I tried to visualize the mesh in the neuroglancer, it become very laggy, which is almost impossible to interact with. I am wondering if there were ways to make it faster for visulization? I tried downsample the image with --mip-level 4 added, but still it was not helping.

igneous image downsample file://./ --mip 0 --queue ./ds-queue 
igneous --parallel 20 execute -x ./ds-queue
igneous mesh forge file://./ --mip 0 --queue ./mesh-queue 
igneous --parallel 20 execute -x ./mesh-queue
igneous mesh merge file://./ --queue ./mesh-queue 
igneous --parallel 20 execute -x ./mesh-queue
igneous view ./ --port 6220
@william-silversmith
Copy link
Contributor

william-silversmith commented Oct 7, 2023 via email

@BoyuLyu
Copy link
Author

BoyuLyu commented Oct 8, 2023

Thank you. Now, with the mip-level 4 as the input for generating the mesh, I can visualize in the browser more smoothly. However, the quality is really bad due to the low resolution. I am wondering if I can generate more levels of mesh? so that when I zoom in, the finer details of the mesh will be displayed.

@william-silversmith
Copy link
Contributor

Yes, you can do that by generating the sharded multi-resolution meshes.

@BoyuLyu
Copy link
Author

BoyuLyu commented Oct 8, 2023

Is the parameter nlod used to decide how many levels of mesh to generate?

@william-silversmith
Copy link
Contributor

william-silversmith commented Oct 8, 2023 via email

@BoyuLyu
Copy link
Author

BoyuLyu commented Oct 9, 2023

Thanks a lot! I have tried using the shared format, but I still found it only displays the mesh with only one resolution. Are there any issues in my following command? Thanks,

igneous image downsample file://./ --mip 0 --num-mips 4 --queue ./ds-queue
igneous --parallel 20 execute -x ./ds-queue/
igneous mesh forge file://./ --mip 4 --queue ./mesh-queue --sharded 
igneous --parallel 20 execute -x ./mesh-queue
igneous mesh merge-sharded file://./ --queue ./mesh-queue --nlod 4
igneous --parallel 20 execute -x ./mesh-queue  
igneous view ./ --port 6220

@william-silversmith
Copy link
Contributor

I think you'll want to forge from a lower mip level for meshing if you want the multi-res stuff to be usable. The mip level sets the floor on the resolution you can obtain.

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