Differences

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

--- other:uvcdat:cdat_conda:miniconda3_install [2021/04/22 13:22]
jypeter [Using mamba instead of conda] Added missing information
+++ other:uvcdat:cdat_conda:miniconda3_install [2024/03/22 13:58]
jypeter [What? Why?] Improved
@@ Line 3: / Line 3: @@
 ===== What? Why? =====
-  * //Miniconda3// is a minimal python environment/distribution that can be used for creating more complete work environments. It will basically make the ''conda'' command available on your computer, and you can then use ''conda'' to install and update more python packages and their dependencies.
+  * //Miniconda3// is a minimal/bootstrap Python distribution that can be used for creating more complex Python distributions. It will basically make a recent ''conda'' command available on your computer, and you can then use this ''conda'' to create independent Python distributions, where you can install and update Python packages and their dependencies.
-  * A python //environment// is basically where you install python. A python //distribution// is the collection of packages you have chosen to install together in the environment.
+  * A conda //environment// is basically where you install the Python that you will use (independently of //Miniconda3// itself). A python //distribution// is the collection of packages you have chosen to install together in this environment.
+    * Example: initializing an environment named ''cdatm_py3''<code> >which conda
+conda:   aliased to source /path_to_miniconda/etc/profile.d/conda.csh
-  * You don't need to be (and **you should not be**) //root// when you install Miniconda3. You just need enough disk space where you have write access
+ > conda activate cdatm_py3
-  * If you are installing Miniconda3 in a Linux environment on a [[other:win10wsl|Windows 10 computer using Windows Subsystem for Linux (WSL)]], pay special attention to the instructions on the **WSL** lines
+(cdatm_py3) > which python
+/path_to_miniconda/envs/cdatm_py3/bin/python
+</code>
+    * The special environment where //miniconda// itself is installed is called ''base''<code>  > conda activate base
+(base) > which python
+/path_to_miniconda/bin/python
+</code>
+  * You don't need to be (and **you should not be**) //root// when you install Miniconda3. You just need enough disk space where you have write access
+    * **WARNING**: by default, miniconda will install itself and subsequent Python environments in a hidden sub-directory of your home (''~/.conda'' on Linux). **Do not use the default installation location**, if you want to avoid disk space related problems (//disk full//, q//uota exceeded//, ...)
+    * Choose carefully where you will install miniconda, because the size of the installation directory will start at a few Gb and will keep on growing
-  * The way you do things will depend on how you are going to use python. There may be some slight differences if you are installing the environment just for you, or if you need a more stable environment because you are installing for multiple users.
+  * If you are installing Miniconda3 in a Linux environment on a [[other:win10wsl|Windows 10 computer using Windows Subsystem for Linux (WSL)]], pay special attention to the specific instructions on the **WSL** lines
-  * You could also start with the //Anaconda// installer that will install a much more complete python environment, ready for use, but we choose not to do that because Anaconda requires more disk space at the beginning, and all its packages come from the ''default'' //channel// (or //repository//) provided by the [[https://docs.conda.io/projects/conda/en/latest/glossary.html#conda-repository|conda repository]]. This is not very useful because we will be mostly using (the same) packages provided by the [[https://conda-forge.org/feedstock-outputs/|conda-forge]] channel.
+  * You could also start with the full //Anaconda// installer that will install a much more complete python environment, ready for use. We choose not to do that because Anaconda requires more disk space at the beginning, and all its packages come from the ''default'' //channel// (or //repository//) provided by the [[https://docs.conda.io/projects/conda/en/latest/glossary.html#conda-repository|conda repository]]. This is not very useful because we will be mostly using (the same) packages provided by the [[https://conda-forge.org/feedstock-outputs/|conda-forge]] //channel//.
 Note: some extra details are available on the much older page //Installing and maintaining UV-CDAT with conda//. You can check later the [[other:uvcdat:conda_notes#useful_conda_commands|Useful conda commands]], but the [[https://docs.conda.io/projects/conda/en/latest/index.html|official conda documentation]] and the [[https://docs.conda.io/projects/conda/en/latest/user-guide/cheatsheet.html|Cheat sheet]] are probably more up-to-date.
@@ Line 141: / Line 154: @@
 The only solution seems to replace ''conda'' with [[https://github.com/mamba-org/mamba|mamba]], a reimplementation of the conda package manager in C++ ([[https://wolfv.medium.com/making-conda-fast-again-4da4debfb3b7|Making conda fast again]]):
-  * Install ''mamba'' in the //base// (i.e. miniconda) environment\\ ''conda install mamba -n base -c conda-forge''
+  * Install ''mamba'' in the //base// (i.e. //miniconda//) environment\\ ''conda install mamba -n base -c conda-forge''
-  * Use ''mamba'' instead of ''conda'' when installing packages\\ ''mamba install -c conda_forge lots_of_packages''
+  * Use ''mamba'' instead of ''conda'' when installing packages.\\ Theoretically, you don't need to specify ''install -c conda forge'' any more, because ''conda-forge'' is now the default source of new packages\\ ''mamba install lots_of_packages''

PMIP3 wiki

User Tools

Site Tools

Differences

Page Tools