-
Notifications
You must be signed in to change notification settings - Fork 39
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
RISE returns different heatmap for same input #6
Comments
@SuryaKalia could you please look into this? |
That behaviour is due to the randomly generated masks in the visualize function. Each call generates a new set of masks while the
|
Ok will do that now, quick side question: have you also looked into grad-cam visualization techniques? |
Hi! Any updates on this? |
Hi, thanks for pointing out. I've fixed that issue. The first solution should work now. The 3rd solution - increasing the number of masks is still bound to give different visualizations. This is an inherent limitation of the RISE visualization method. Grad-CAM is a good alternative. However, that had an issue with images which had very high predictive confidence for a given class, causing gradient saturation. To eliminate those issues we used RISE visualizations. |
Hey, after making your model torch>1.0 compatible I got the RISE "explainer" predictions for the covid-19 file "4-x-day1.jpg" twice. The predictions are the same:
but the heatmaps produced by RISE look totally different:
Does the same happen to your torch<1.0 model? If not, do you know what could be the issue?
The text was updated successfully, but these errors were encountered: