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
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
Create an annotation & open the materialize volume annotation job modal as shown in the images.
The modal does not allow to input an output layer name. => This param is missing in the form.
Submitting should succeed
Your Environment for bug
shouldn't matter
The text was updated successfully, but these errors were encountered:
MichaelBuessemeyer
changed the title
Fix materialize volume annotation job
Make the output segmentation layer name of materialize job configurable for users
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
asoutputSegmentationLayerName
to the backend. But the user should be able to configureoutputSegmentationLayerName
and the frontend should validate that this is a new layer name and not an already existing one.Steps to Reproduce the bug
Your Environment for bug
The text was updated successfully, but these errors were encountered: