-
Notifications
You must be signed in to change notification settings - Fork 24
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
Added support for ComputeSegmentIndexFile worker job #7471
Conversation
Co-authored-by: Florian M <[email protected]>
…ebknossos into segment_index_worker_job
@@ -152,7 +152,7 @@ WEBKNOSSOS requires several metadata properties for each dataset to properly dis | |||
+ `dataLayers.largestSegmentId`: The highest ID that is currently used in the respective segmentation layer. This is required for volume annotations where new objects with incrementing IDs are created. Only applies to segmentation layers. | |||
+ `dataLayers.dataFormat`: Should be `wkw`. | |||
|
|||
#### NML Files | |||
### NML Files |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Somewhat unrelated change, but the indentation for this was one level too deep.
@philippotto Can you please have a quick look at the frontend changes. NO need to deep test this with the worker running. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the front-end looks good to me 👍
This PR adds support for triggering the
ComputeSegmentIndexFile
worker job through a REST route. This is very similar to the theComputeMeshFile
job.UI Changes:
URL of deployed dev instance (used for testing):
Steps to test:
Use the button (only visible for superusers) or send a POST request (needs auth cookie), e.g.:
TODOs:
Issues:
(Please delete unneeded items, merge only when none are left open)