Differences

This shows you the differences between two versions of the page.

--- software:miniconda:caviness [2025-10-15 15:40] – thuachen
+++ software:miniconda:caviness [2025-10-16 09:41] (current) – [Installing Applications with Conda] thuachen
@@ Line 3: / Line 3: @@
 </note>
-Miniconda is available through the VALET packages on Caviness clusters. To check the versions,
+Miniconda is available through the VALET packages on the Caviness cluster. To check the versions, use
 <code>
 $ vpkg_versions miniconda
@@ Line 20: / Line 20: @@
 ===== Installing Applications with Conda =====
-You can create a new Conda environment either by name or by path.
+<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 --name myenv python=3.13
+conda create -p /work/workgroup/sw/myenv python=3.13
 </code>
-By default, Conda environments are created in your home directory. However, the limited home directory quotas (20 GB) can be filled up quickly. You can create an environment in a specific path, such as your /work/workgroup directory,
+You can also create a new environment by name,
 <code>
-conda create -p $WORKDIR/$USER/myenv python=3.13
+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>