Page History

...

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

...

• 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

1. 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\"

1. 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.

...

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:

• keras_env