-
Notifications
You must be signed in to change notification settings - Fork 27
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
Update the Zamba installation instructions #246
Comments
Can you say more about which parts require substantial expertise? The pip install is a one line command. Is it the ffmpeg piece that feels trickiest? |
This is based on my initial reaction, from the POV of a hypothetical user: when I read that page, I had no confidence I would be able to get a working environment set up. The Makefile uses conda to install cudatoolkit and cudann, then pip to install the other requirements. For someone following the instructions in the docs, I wondered how they would handle this (or know to handle it). Now I see that there are instructions at the end, but I wonder if we'd want to change the order to install CUDA first? Also, one issue that I ran into (despite my using the Makefile): I have a GPU but did not have the driver working successfully, so cudatoolkit installed successfully, but Zamba did not find my GPU. It might be good to provide instructions for users to check the configuration of the GPU (using tools like nvidia-smi) before they start the install. Anyway, these are mostly notes as I go through the process. Whether and when we want to make changes in the docs depends in part on who we imagine is installing Zamba locally (as opposed to using Zamba cloud). |
Some ideas that are relevant and may improve the situation:
|
Current the installation instructions require substantial expertise to follow
https://zamba.drivendata.org/docs/stable/install/
Since we have a Makefile in the repo, I wonder if we should advise users to use the Makefile.
The text was updated successfully, but these errors were encountered: