-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Captum Insights not working in Google Colab #116
Comments
Hi @floscha , thank you so much for posting the issue. Google Colab notebook support would be great! We haven't had time to look into it. cc: @edward-io |
Feel free to give it a shot and send in a PR. Thanks! |
This would be excellent! I wonder if this is also the issue seen in SageMaker at #138 . @edward-io and @J0Nreynolds, thoughts? |
@J0Nreynolds is going to investigate here as well. |
This will be essential for all remote work beyond Colab, too, e.g. if running a jupyter lab server on a remote cluster. |
Great job @J0Nreynolds! |
@floscha , @J0Nreynolds if this is merged and working, can we close the issue ? |
When trying to run the Getting started with Captum Insights tutorial in a Google Colab notebook, I stumbled upon the following issue: When calling
visualizer.render(debug=False)
, the result looks like in the screenshot below.The reason for this behavior is that Captum's render() method does not redirect requests as e.g. shown in TensorBoard's _display_colab() method. While the current implementation works fine with regular IPython notebooks, Colab requires some additional tweaks as described in the TensorBoard code.
Do you have any plans to support Colab or is this even a priority? If no one is already working on this, I could make a PR adding some code similar to TensorBoard as a proof of concept.
The text was updated successfully, but these errors were encountered: