-
Notifications
You must be signed in to change notification settings - Fork 17
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
Implements Prediction Mask for Pixel Classification #65
base: main
Are you sure you want to change the base?
Conversation
This still doesn;t work as a backwards compatible macro, since using pixel classification as a macro will require the value for 'useMask'. I could not find a way to have this extra parameter with a default value that would be picked up also by the macro usage. Either the input is marked as resolved and doesn't show up in the UI, or it is not marked as resolved, but requires the macro usage to specify the value interactively.
required = false, | ||
description = "An image with same dimensions as Raw Data, where the black pixels will be masked out of the predictions" | ||
) | ||
public Dataset predictionMask; |
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.
Did you try:
public Dataset predictionMask; | |
public Dataset predictionMask = null; |
to see whether that solves the issue with a default value?
I'm also hitting an error with the ci, anyone know how to resolve it?
looks like we reference a dependency that's not there anymore (since yesterday?!) |
That's a temporary issue with server hosting maven.scijava.org. |
phew, thank you @imagejan I already saw myself editing xml files... |
This still doesn't work as a backwards compatible macro,
since using pixel classification as a macro will require the
value for 'useMask'.
I could not find a way to have this extra parameter with a default
value that would be picked up also by the macro usage. Either
the input is marked as resolved and doesn't show up in the UI,
or it is not marked as resolved, but requires the macro usage to specify
the value interactively.
fixes #7