-
Notifications
You must be signed in to change notification settings - Fork 1
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
Apply model explainability tools to the images output by similarity search #6
Comments
A quick note on this as I may not make time to finish the branch, to the extent worth doing so, this week Initial output was a lot more inconclusive than i'd hoped for. Could be a range of reasons including
It's worth running the same attempted interpretations over a CEFAS plankton test set before drawing any conclusions. This seems not worth pursuing much more because using the scivision model for classification was never the intention, this was only to throw light on how and why it seems to work pretty well for feature extraction. It's also worth going back a step, to extract and compare embeddings using different networks - using a generic ImageNet-type Resnet50 that's never specifically looked at plankton, and a default network as a sense check. short video dataviz of occlusion output - most of the other methods i tried were even more garbled. we should expect to see much more consistency here |
I was on the point of closing #7 as
It's a useful line in the sand though. Low-priority but still actionable? |
Closed this along with #7 - see comments there |
Exploration of model explainability techniques using the prediction capabilities of the CEFAS model, in complement to using it as a source of embeddings.
E.g. we take the images resulting from a similarity search of the embeddings, make predictions with the original model and look at the visual features that influenced the predictions
SHAP / LIME are the ones I'm familiar with but there's a whole toolbox in the Captum API - suggestions of approaches that worked well during development of AMI-system would be appreciated, @albags !
The text was updated successfully, but these errors were encountered: