-
Notifications
You must be signed in to change notification settings - Fork 0
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
Automated deployment of Deeplabcut #5
base: main
Are you sure you want to change the base?
Conversation
We might want to rename the role as it installs DeepLabCut3. Or we split it up into several roles:
Up to installing conda could be a reasonable split. Afterwards pytorch could also be installed with RocM on AMD hardware. Also deeplabcut works with pytorch only from 3.0 on (see DeepLabCut/DeepLabCut#2613) and needs tensorflow for earlier versions... |
This is quite the mess for a declarative setup. the constraint tf <=2.10 applies also for ubuntu (not 2.12 as indicated. tf 2.10 limits us to python <=3.10. We should adapt our default parameter values accordingly! |
A better approach might be to directly checkout a repo that contains some analysis performed with DeepLabCut and fetch the dlc version form the repo's requirements.txt. |
This implements an ansible role to setup and configure a vanilla ubuntu machine (with nvidia gpu) for DeepLabCut