-
Notifications
You must be signed in to change notification settings - Fork 13
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
Google colab integration #17
Comments
I would be concerned about versioning of jax/pytorch for GPU in colab as well as the startup cost of installing and creating a conda env. |
Yeah, that's not ideal... but what would you suggest to do? Just not
support it at all?
…On Fri, 9 Dec 2022 at 07:22, Adam Gayoso ***@***.***> wrote:
I would be concerned about versioning of jax/pytorch for GPU in colab as
well as the startup cost of installing and creating a conda env.
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVZRV4IWT4CT4A57OICZXTWMLF3HANCNFSM6AAAAAASYDMSGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I think this is fine if, for example, all scvi-tools models are loaded from disk. However, I'm assuming we will make it easy to run these locally? In that case it would be good to have guides on how to install things locally with a GPU |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would be nice to have integration with google colab in addition to binder.
To make this work we need some hack that allow the use of conda envs with colab
The text was updated successfully, but these errors were encountered: