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
updates to register_objects to allow relabelling #8
base: master
Are you sure you want to change the base?
Conversation
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.
It's not something I'd generally encourage people to do, as it could lead to many issues if relabeling is performed before registration. This may fuse many existing objects, especially for secondary segmentations and thus be very confusing to users.
If we can add some sort of warning / indication that this is an advanced feature and not an option to play around with, then that's ok
@@ -1,4 +1,4 @@ | |||
# Copyright (C) 2016 University of Zurich. | |||
# Copyright 2016 Markus D. Herrmann, University of Zurich |
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.
Don't see a reason to Markus back in now that you're changing the module
type: Boolean | ||
value: false | ||
help: > | ||
Should objects be relabeled on registration. |
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.
Can we add a warning here that this shouldn't normally be done? Some users just seem to try out options at this is definitely an advanced feature
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.
LGTM, waiting for Scott's reply.
In certain cases it is useful, but I can't exactly remember when...anyway the default is
False