Skip to content

Commit

Permalink
explicit export source for object classification
Browse files Browse the repository at this point in the history
in the past nothing was passed to the workflow, which defaulted to
`Object Predictions` output.
This makes it explicit and fixes the previous binding to input type.
While it would be cool to choose the export source, and we should
definitely do it, see #64.
  • Loading branch information
k-dominik committed Sep 25, 2023
1 parent d92223e commit 3f709b8
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 7 deletions.
Binary file modified doc/screenshots/IJ-Menu.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -46,13 +46,7 @@ public final class ObjectClassificationCommand<T extends NativeType<T> & RealTyp

@Override
protected List<String> workflowArgs() {
if (ROLE_PROBABILITIES.equals(secondInputType)) {
return Collections.singletonList("--export_source=Object Probabilities");
}
if (ROLE_SEGMENTATION.equals(secondInputType)) {
return Collections.singletonList("--export_source=Object Predictions");
}
throw new IllegalStateException("Unexpected value: " + secondInputType);
return Collections.singletonList("--export_source=Object Predictions");
}

@Override
Expand Down

0 comments on commit 3f709b8

Please sign in to comment.