Skip to content
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

Make the output segmentation layer name of materialize job configurable for users #8117

Open
MichaelBuessemeyer opened this issue Oct 8, 2024 · 0 comments

Comments

@MichaelBuessemeyer
Copy link
Contributor

MichaelBuessemeyer commented Oct 8, 2024

Currently, the materialize volume annotation job is fixed by #8118. It was broken due to the missing outputSegmentationLayerName argument. This is now autofilled by the frontend. But it should be configurable by the user.

Context

When trying to materialize a volume annotation it is not possible to configure the name of the newly created segmentation layer.

Expected Behavior

One should be able to enter a name for the materialized segmentation layer and this should be sent to the backend together with the job starting request.

Current Behavior

The frontend sends <segmentation_layer_name>_materialized as outputSegmentationLayerName to the backend. But the user should be able to configure outputSegmentationLayerName and the frontend should validate that this is a new layer name and not an already existing one.

Steps to Reproduce the bug

  1. Create an annotation & open the materialize volume annotation job modal as shown in the images.
    image
    image
  2. The modal does not allow to input an output layer name. => This param is missing in the form.
  3. Submitting should succeed

Your Environment for bug

  • shouldn't matter
@fm3 fm3 added the frontend label Oct 8, 2024
@MichaelBuessemeyer MichaelBuessemeyer changed the title Fix materialize volume annotation job Make the output segmentation layer name of materialize job configurable for users Oct 8, 2024
@fm3 fm3 added enhancement and removed bug labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants