Conda environments are are divided in 2 groups (for psana1 and for psana2), to create new environments (for production) or modify an existing one (in production) the user must login as psreldev (psana1) or psrel (psana2) respectively.
remember to update your kerberos ticket:
- kinit
for pcds:
for psana1
- ssh -X psreldev@psbuild-rhel7
- source /cds/sw/ds/ana/conda1/manage/bin/psconda.sh
for psana2
- ssh -X psrel@psbuild-rhel7
- source /cds/sw/ds/ana/conda2/manage/bin/psconda.sh
If even with a valid ticket the connection fails, use psbuild-rhel7-01 (you may have valid credential only for a specific node)
Instead for s3df:
one can use:
for psana1
- 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.
Modify existing Environment
Once sourced the correct psconda.sh and having used the correct username (psrel/psreldev), one can activate any environment needed:
- 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