Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support Kaggle and Colab Environments

See original GitHub issue

Is your feature request related to a problem? Please describe.

Kaggle and Colab are free and great resources to do quick experiments. Currently, I’ve found that it’s not possible to run anomalib on these environments. I guess, when the PIP packages get ready, it would be possible. Supporting these environments would be a great opportunity for the end-user for sure.

Issue Analytics

State:
Created 2 years ago
Comments:13 (12 by maintainers)

Top GitHub Comments

1reaction

samet-akcaycommented, Mar 28, 2022

Done:)

1reaction

alexriedel1commented, Mar 24, 2022

Hello, this notebook contains all the necessary steps to get anomalib running on Google Colab https://colab.research.google.com/drive/1yFtIJP7OkE4-zF8S3kg9lQnqS53Nh95H?usp=sharing

Anyways, you will run into an import error for OpenVino. Just patch that by commenting out the OpenVino in the respective file.

I guess some things should be done in order to make this easier:

install the matching torchtext version in the requirements
install the right open-cv version in the requirements (check which one is actually necessary)
figure out the issue with the folder names. if you import anomalib on colab and it’s inside a dir called anomalib, it will be imported from there and not the installed version. thats why you have to clone into a differently named dir…
offer a version that doesnt import openvino