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
For on-disk segmentation layers (no annotation layers), the ad-hoc meshing could use the same optimization as the one for volume annotation layers if there is a segment index file.
Needs
Datastore route to expose the available positions from the segment index (same format as tracingstore has) – Maybe for datastore-tracingstore communication that could then also be used, in place of current GET /datasets/:organizationName/:dataSetName/layers/:dataLayerName/segmentIndex/:segmentId
Frontend to use that
Should also be used by the fullMesh.stl route
The text was updated successfully, but these errors were encountered:
For on-disk segmentation layers (no annotation layers), the ad-hoc meshing could use the same optimization as the one for volume annotation layers if there is a segment index file.
Needs
GET /datasets/:organizationName/:dataSetName/layers/:dataLayerName/segmentIndex/:segmentId
Should also be used by the fullMesh.stl route
The text was updated successfully, but these errors were encountered: