-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Using Pre Processors in Prediction (ART classifier) #2335
Comments
Hi @RoeyBokobza Thank you for your interest in ART! Have you observed that pre-processing steps are not being applied in your experiments? |
Hey, thank you for responding! |
As a user, you would anticipate that adding a preprocessor defense to the estimator's 'preprocessing_defences' list would automatically activate it on the input inside the predict function.
Instead, the user must explicitly activate any of those defenses before sending the result to the predict function. This entire operation renders the attribute 'preprocessing_defences' obsolete.
Implementing the 'forward' function for this defense, and adding the defense instance to the 'preprocessing_operations' list are prerequisites for using the current implementation of the 'self._apply_preprocessing' function. Here is an example of the 'self._apply_preprocessing' function in Estimator.py file:
In the case of postprocessors, everything is as a user would anticipate. All post processors in the list of 'postprocessing_defeces' attribute are automatically activated as part of the predict function of the estimator. Here is an example from the Estimator.py file :
For now, adding a similar piece of code inside the 'self._apply_preprocessing' method is a straightforward workaround for it, as demonstrated in this little example:
The text was updated successfully, but these errors were encountered: