-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enhance ScriptModelConfig to validate and infer missing configuration… #21
base: main
Are you sure you want to change the base?
Conversation
update from main
…ancer utilities with web browser support
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.
i didn't get the point of the pyramid test if key not found check different key. i think the user should give a specific one key value altribute, if not evailable then he gets an error. we can't use this logic as we can never handle all the possible keys
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.
@mzouink If we want a strict schema, can we use the one already employed by the cellmap-segmentation-challenge, which groups the input and output array info (shape/scale)?:
input_array_info = {
"shape": <input shape>,
"scale": <input voxel size>
}
target_array_info = {
"shape": <model output shape>,
"scale": <model output voxel size>
}
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.
that seems ok to me, since we haven't really decided on an enforced schema yet.
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.
or I can make it work for either your old way or the CSC schema?
In the initial PR I tried to make it as universal an adapter as reasonable, combining the conventions you had been using with CSC conventions. So I allowed split definitions or unified (input_array_info["shape"]
vs. just read_shape
), as well as "scale" vs. "voxel_size" keywords in *_array_info dicts. seems user friendly to me, but too loose for @mzouink it seems 🙃
I forced the ScriptModelConfig parsing to require 1 of 2 schemas or a mix of the two that yields the complete necessary description:
What do you say @mzouink / @davidackerman ? |
good for me. feel free to go through config loader and the examples existing and change them to the new schema |
most of the examples require |
… attributes