You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been working on implementing the multiscale mesh layer for graphene. I think I have most of it in place (#460).
However meshes seem to disappear if zoomed out or zoomed in too much. See attached video:
graphene-multiscale.mp4
Graphene manifest is generated following the octree specification here.
However, a chunkedgraph octree node may contain more than 8 children and something we call "skip connections" - parent_layer - child_layer >= 1 instead of parent_layer - child_layer == 1 in a standard octree representation. I think this is not a problem (?) because we can still see the meshes.
Another thing to note is that graphene multiscale meshes are generated by simplifying the finest meshes at each layer. They are not generated by meshing downsampled segmentation. So technically we are trying to use the same meshes for both legacy and multiscale graphene mesh layers.
Let me know if you need anything else to look into this. Myself or @sdorkenw can provide additional details.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi Jeremy,
I have been working on implementing the multiscale mesh layer for graphene. I think I have most of it in place (#460).
However meshes seem to disappear if zoomed out or zoomed in too much. See attached video:
graphene-multiscale.mp4
Graphene manifest is generated following the octree specification here.
However, a chunkedgraph octree node may contain more than 8 children and something we call "skip connections" -
parent_layer - child_layer >= 1
instead ofparent_layer - child_layer == 1
in a standard octree representation. I think this is not a problem (?) because we can still see the meshes.Another thing to note is that graphene multiscale meshes are generated by simplifying the finest meshes at each layer. They are not generated by meshing downsampled segmentation. So technically we are trying to use the same meshes for both legacy and multiscale graphene mesh layers.
Let me know if you need anything else to look into this. Myself or @sdorkenw can provide additional details.
Thanks!
The text was updated successfully, but these errors were encountered: