Page History
...
- ssh -X psreldev@sdfiana001
source /sdf/group/lcls/ds/ana/sw/conda1/manage/bin/psconda.sh
for psana2
- ssh -X psrel@sdfiana001
source /sdf/group/lcls/ds/ana/sw/conda2/manage/bin/psconda.sh
Create a New Environment
- the new env will be empty and the packages will be stored in the system env (\"/cds/sw/ds/ana/conda1 2/inst/envs/\")
- conda deactivate
- conda create --name \"new_env_name\"
- conda activate \"new_env_name\"
- the new env will be the clone of the \"from_env_name\" and the packages will be stored in the system env (\"/cds/sw/ds/ana/conda1 2/inst/envs/\")
- conda deactivate
- conda create --clone \"from_env_name\" --name \"new_env_name\"
- conda activate \"new_env_name\"
If one runs these commands without using the psrel or psreldev user, the files will be instead stored in the local folder
/cds/home/a-z/\"user_name\"/.conda/envs/
home folders have limited storage.
...
- conda env list (lists every environment available)
- conda deactivate
- conda activate \"the environment to be changed\"
and then the user can install or uninstall packages from that environment.
N.B.
This WILL modify PRODUCTION
List of
...
recipes for environments:
...
Overview
Content Tools