hpc documentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Miniconda on Caviness ======
<note warning> This page is under construction.
</note>

Miniconda is available through the VALET packages on the Caviness cluster. To check the versions, use
<code>
$ 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)
</code>
To load it, use
<code>
$ vpkg_require miniconda/25.1.1.2
Adding package `miniconda/25.1.1.2` to your environment
</code>

===== Installing Applications with Conda =====
<note tip>
Note: In the examples below, please modify paths, usernames, and environment names (e.g., ''/work/workgroup/sw/''..., ''myenv'') to match your own account and project setup. 
</note>
You can create a new Conda environment either by name or by path. For example, to create an environment in a specific path, such as your ''/work/workgroup'' directory,
<code>
conda create -p /work/workgroup/sw/myenv python=3.13
</code>
You can also create a new environment by name,
<code>
conda create --name myenv python=3.13
</code>
<warning important>
By default, Conda environments created by '''--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 in your work directory instead of ''$HOME'' to avoid quota issues.
</warning>
After creating the Conda environments, you can activate the local conda environment using,
<code>
conda activate myenv
</code>
Then you can install the desired packages, for example,
<code>
conda install <package_name>
</code>