software:miniconda:caviness

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
software:miniconda:caviness [2025-11-06 15:05] – [Installing Applications with Conda] thuachensoftware:miniconda:caviness [2025-11-06 15:38] (current) – [Migrating Environments] thuachen
Line 24: Line 24:
 </note> </note>
 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, 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,
-<code> +<code bash> 
-conda create -p /work/workgroup/sw/myenv <my_package>+[(my_workgroup:user)@login01 ~]$ conda create -p /work/workgroup/sw/myenv <my_package>
 </code> </code>
  
Line 32: Line 32:
 </note> </note>
 After creating the Conda environments, you can activate the local conda environment using, After creating the Conda environments, you can activate the local conda environment using,
-<code> +<code bash> 
-conda activate myenv+[(my_workgroup:user)@login01 ~]$ conda activate /work/workgroup/sw/myenv
 </code> </code>
 You can install the desired packages in the current environment, for example, You can install the desired packages in the current environment, for example,
-<code> +<code bash> 
-(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$conda install <my_package>+(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda install <my_package>
 </code> </code>
 To list packages in the currently active environment, use To list packages in the currently active environment, use
-<code> +<code bash> 
-conda list+(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda list 
 +# packages in environment at /work/workgroup/sw/myenv: 
 +# 
 +# Name                    Version                   Build  Channel 
 +_libgcc_mutex             0.1                 conda_forge    conda-forge 
 +_openmp_mutex             4.5                       2_gnu    conda-forge 
 +absl-py                   2.3.1                    pypi_0    pypi 
 +astunparse                1.6.3                    pypi_0    pypi 
 +bzip2                     1.0.8                hda65f42_8    conda-forge 
 +ca-certificates           2025.10.5            hbd8a1cb_0    conda-forge 
 +certifi                   2025.10.5                pypi_0    pypi
 </code> </code>
 To deactivate the environment, do: To deactivate the environment, do:
-<code> +<code bash> 
-conda deactivate+(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda deactivate 
 +[(my_workgroup:user)@login01 ~]$
 </code> </code>
 To remove an environment, run: To remove an environment, run:
-<code> +<code bash> 
-conda remove -p </path/to/myenv> --all+[(my_workgroup:user)@login01 ~]$ conda remove -p /work/workgroup/sw/myenv --all
 </code> </code>
 +To remove the unused packages and caches, do
 +<code bash>
 +[(my_workgroup:user)@login01 ~]$ conda clean --all
 +</code>
 +
 ===== Migrating Environments ===== ===== Migrating Environments =====
  
 In the terminal window, to view the environments available to you, use In the terminal window, to view the environments available to you, use
-<code> +<code bash> 
-conda env list+[(my_workgroup:user)@login01 ~]$ conda env list 
 +# conda environments: 
 +# 
 +base                   /opt/shared/miniconda/25.1.1.2 
 +                      */work/workgroup/sw/myenv
 </code> </code>
  
 After activating the desired environment, export the current environment, After activating the desired environment, export the current environment,
-<code> +<code bash> 
-conda activate myenv +[(my_workgroup:user)@login01 ~]$ conda activate /work/workgroup/sw/myenv 
-conda export --file=environment.yaml    # Auto-detects YAML format +(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda export --file=myenv.yaml 
-conda export --file=environment.json    # Auto-detects JSON format +name: /work/workgroup/sw/myenv 
-conda export --file=explicit.txt        # Auto-detects explicit format +channels: 
-conda export --file=requirements.txt    # Auto-detects requirements format+  - conda-forge 
 +dependencies: 
 +  - _libgcc_mutex=0.1=conda_forge 
 +  - _openmp_mutex=4.5=2_gnu 
 +  - bzip2=1.0.8=hda65f42_8 
 +  - ca-certificates=2025.10.5=hbd8a1cb_0 
 +  - cuda-version=11.8=h70ddcb2_3 
 +  - cudatoolkit=11.8.0=h4ba93d1_13 
 +  - cudnn=8.9.7.29=hbc23b4c_3  
 +... 
 +... 
 + 
 +prefix: /work/workgroup/sw/myenv  
 </code> </code>
-Then you can create the same environment with +Then you can duplicate the same environment with 
-<code> +<code bash> 
-conda create -p myenv -f environment.yml+(/work/workgroup/sw/myenv)[(my_workgroup:user)@login01 ~]$ conda deactivate 
 +[(my_workgroup:user)@login01 ~]$ conda create -p /work/workgroup/sw/myenv_2 -f myenv.yml
 </code> </code>
  
  • software/miniconda/caviness.1762459515.txt.gz
  • Last modified: 2025-11-06 15:05
  • by thuachen