This is an old revision of the document!
Miniconda on Caviness
Miniconda is available through the VALET packages on the Caviness cluster. To check the versions, use
$ vpkg_versions miniconda Available versions in package (* = default version): [/opt/shared/valet/2.1/etc/miniconda.vpkg_yaml] miniconda A free, miniature installation of Anaconda Distribution * 25.1.1.2 Miniconda py39 25.1.1-2 for Linux (x86_64)
To load it, use
$ vpkg_require miniconda/25.1.1.2 Adding package `miniconda/25.1.1.2` to your environment
Installing Applications with Conda
/work/workgroup/sw/…, myenv) to match your own account and project setup.
You can create a new Conda environment with a specific package and in a specific path. For example, to create an environment in a specific path, such as your /work/workgroup directory,
[(my_workgroup:user)@login01 ~]$ conda create -p /work/workgroup/sw/myenv <my_package>
--name or -n are in your home directory. However, the limited home directory quotas (20 GB) can be filled up quickly. It is recommended to create environments by specifying path -p in your work directory instead of $HOME to avoid quota issues.
After creating the Conda environments, you can activate the local conda environment using,
[(my_workgroup:user)@login01 ~]$ conda activate myenv
You can install the desired packages in the current environment, for example,
(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda install <my_package>
To list packages in the currently active environment, use
(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda list
To deactivate the environment, do:
conda deactivate
To remove an environment, run:
conda remove -p </path/to/myenv> --all
Migrating Environments
In the terminal window, to view the environments available to you, use
conda env list
After activating the desired environment, export the current environment,
conda activate myenv conda export --file=environment.yaml # Auto-detects YAML format conda export --file=environment.json # Auto-detects JSON format conda export --file=explicit.txt # Auto-detects explicit format conda export --file=requirements.txt # Auto-detects requirements format
Then you can create the same environment with
conda create -p myenv -f environment.yml
Recipes
Examples documented as recipes to be used for specific installations, including using a workgroup directory as well as creating VALET packages for these environments and job scripts setup for batch runs, but can also perhaps help others in solving similar installation dilemmas.