Florian M
Florian M
Some Ad-hoc meshing (a.k.a. isosurface) datastore requests failed with 30s timeouts. Since the chunk size is relatively small, this duration is suspiciously long. Maybe something could be optimized here. Note...
The REST-API response schemas are not present in the current swagger.json – the client auto-generates them from recorded responses, which is very fragile and cannot infer which fields are optional...
When downloading and re-uploading a volume annotation, the largestSegmentId and elementClass properties are lost. In case of an existing fallback layer, the latter is harmless, as the elementClass of the...
When merging multiple volume tracings, the dtype should become large enough to encompass all IDs
In #6369 and also https://github.com/scalableminds/webknossos/pull/6367 and the existing zarr streaming for volume annotations, the tracingstore requests data from the datastore for the unchanged segmentation buckets. It may be worth changing...
Some datasets use only a small range of their data type’s possible intensity range. The wk frontend histogram sliders allow looking at that range in detail, but thumbnails will remain...
Follow-up for reading zarr images in wk-backend backend (https://github.com/scalableminds/webknossos/pull/6019) - [x] handle multi-layers/ngff - [x] handle OME-NGFF metadata https://github.com/scalableminds/webknossos/pull/6335 - [x] handle non-standard axis order (as specified by ome metadata?)...
Follow-up for reading zarr-datasets in wk backend: - [ ] cache clear for file system handles (when password for an account changes / file system breaks somehow) - [ ]...
Needed steps: - discuss if we want this at all - introduce organization (name) parameter in task creation for dataset disambiguation (currently datasets are looked up using the user’s organization)...
#5771 introduced the concept of annotation layers. An annotation can for example have multiple volume annotation layers (which can later be toggled visible vs invisible) – There should be routes...