-
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
working on perturbation detectors #51
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.
We can also add a NoisePerturbationDetector to evaluate robustness to noise
except (ImportError, ModuleNotFoundError) as e: | ||
raise GiskardImportError(["giskard"]) from e | ||
|
||
relative_delta = (test_result.metric_value_test - test_result.metric_value_ref) / test_result.metric_value_ref |
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.
We should use what we implemented in the meta data detector for this function, for instance here the metric can be absolute or relative
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.
agreed
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.
taken care of in #53
* ENH: adding noise perturbation detector with Gaussian noise * FIX: docstring * FIX: the IoU metric now handles prediction batches * renaming metric IoU to IoUMean --------- Co-authored-by: Rabah Khalek <[email protected]>
refactoring detectors
We can keep the scope limited to coloring and blurring for now. @bmalezieux maybe you can support
predict_gray_image
for the rest of the models we have?