-
Notifications
You must be signed in to change notification settings - Fork 22
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
Use segment-index for ad-hoc meshing to enable rendering non-connected segments #7143
Comments
This is about the tracingstore route The frontend then typically continues by requesting the isosurface for the same segment id, but for those neighbor volumes. This heuristic yields incomplete meshes when the segment is not connected. Now using the segment index (if it exists it can be acquired by If you get to this, maybe you could coordinate with @philippotto what a sensible protocol for this may be. Note that the segment index does not always exist. The add-hoc meshing for on-disk segmentations should also not be broken (there is a route in the datastore as well, which ultimately uses the same IsosurfaceService) @valentin-pinkau also mentioned that this non-connected heuristic may actually be what the user wants in some cases (e.g. all synapses have the same segment id, but the user is interested in the mesh of only one synapse). I’m not sure if this should be configurable or if the fault here lies with the user who “abuses” what a segment id is? Any opinions welcome :) |
Sure, we can do that. Just as a short note: This API could probably look like a slimmed-down variant of the precomputed mesh case. There, a first request to get the available chunks for a segment id is also sent (compare route
Ok, this means that the heuristic with segments "touching the walls" will stay for the case where we don't have the segment statistics, right? |
I'd vote for showing all non-connected meshes, nevertheless. If the user wants them separated, different ids should be used (by the user). In general, it's better to show too much data than too little, I'd argue. |
I’d say so, yes.
Not sure I understand what you mean. Can the frontend find out how to split them? |
Sorry, I used the wrong word. I meant "different ids should be used by the user". |
Backend: Create a route in tracingstrore to expose segment index |
The segment index introduced in #7063 could be used (if present) to find the buckets that marchingCubes for ad-hoc meshing (aka isosurface routes) needs to traverse. This could then replace the edge-pixel heuristic that is currently used to determine when marchingCubes stops.
The text was updated successfully, but these errors were encountered: