This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
populate build-environment #7
Comments
see |
I think we can get some useful info from Farshid/Chaopeng about their compute machine/cluster, and I already have info I can add about the python package environment on that cluster. Also want to add a reference to the environment.ymls. |
Just need to stick this formatted python module list somewhere temporarily:
from readr::read_lines('pyenv.R') %>% strsplit(split=' +') %>% purrr::map(.f=function(strs) sprintf('%s, v%s', strs[1], strs[2])) %>% unlist %>% paste(collapse='; ') |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Jordan has used the R build environment (the one used to create the data). I think this is fine, especially given that I've got some conda environment YAMLs going for the model code. I also think meddle offers a way to populate the build-environment with your current environment automatically?
The text was updated successfully, but these errors were encountered: