User Tools

Site Tools


other:uvcdat:conda_notes

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
other:uvcdat:conda_notes [2018/03/14 14:27]
jypeter [Misc] updated a link
other:uvcdat:conda_notes [2021/12/21 10:33] (current)
jypeter [Installation history]
Line 17: Line 17:
     * If you know that you are going to use UV-CDAT, you might as well use the ''​conda''​ from //​Miniconda//​ to avoid uselessly duplicating packages downloaded from the official Anaconda repository (used by Anaconda) with the same packages downloaded from the conda-forge repository (used by UV-CDAT).     * If you know that you are going to use UV-CDAT, you might as well use the ''​conda''​ from //​Miniconda//​ to avoid uselessly duplicating packages downloaded from the official Anaconda repository (used by Anaconda) with the same packages downloaded from the conda-forge repository (used by UV-CDAT).
  
 +  * When you are done with this page (not just this section), you should have a look at the [[https://​www.freecodecamp.org/​news/​why-you-need-python-environments-and-how-to-manage-them-with-conda-85f155f4353c/​|Why You Need Python Environments and How to Manage Them with Conda]] page that covers interesting topics
 ===== Miniconda ===== ===== Miniconda =====
  
Line 146: Line 147:
   * Deleting an environment   * Deleting an environment
     * ''​conda remove %%--%%name crap_environment %%--%%all''​\\ ''​conda clean --all''​     * ''​conda remove %%--%%name crap_environment %%--%%all''​\\ ''​conda clean --all''​
-  ​* Activating or going back to //root// +    * The following seems to do the same: ''​conda env remove -n crap_environment''​ 
-    * ''​source activate existing_environment''​ +  ​* Activating or going back to //root/base// 
-      * ''​source ​activate''​ will activate the //root// environment +    * ''​conda activate existing_environment''​ (used to be ''​source activate existing_environment'' ​in older versions of conda) 
-    * You can use ''​which python''​ to determine where is the current Python you are using, or ''​which -a python''​ to display all the Python executables in the currrent ​search path +      * ''​conda activate''​ will activate the //root/base// environment 
-    * ''​source deactivate''​+    * You can use ''​which python''​ to determine where is the current Python you are using, or ''​which -a python'' ​(''​-a''​ will only work in //​bash//​) ​to display all the Python executables in the current ​search path 
 +    * ''​conda deactivate''​ (used to be ''​source deactivate''​)
   * Installed packages   * Installed packages
     * ''​conda list''​     * ''​conda list''​
Line 164: Line 166:
     * ''​conda remove package1 package2 packageN''​     * ''​conda remove package1 package2 packageN''​
   * Updating conda (update the //conda// package, not the full Miniconda)   * Updating conda (update the //conda// package, not the full Miniconda)
-    * ''​conda update conda''​+    * ''​conda update ​-n base -c defaults ​conda''​
   * Downgrading conda (required for installing UV-CDAT 2.10)   * Downgrading conda (required for installing UV-CDAT 2.10)
     * <​code>​bash-4.1$ conda install -n root "​conda<​4.3.13"​     * <​code>​bash-4.1$ conda install -n root "​conda<​4.3.13"​
Line 191: Line 193:
     * ''​conda clean %%--%%all''​     * ''​conda clean %%--%%all''​
  
 +==== Installation history ====
 +
 +You can get the current list of installed packages with ''​conda list'',​ but it may also be useful to know the installation order:
 +
 +  * ''​conda list %%--%%revisions''​ revisions will display **exactly** what was installed and when (including the updates, and automatic dependencies installation)
 +    * You can theoretically roll back to a previous ''​RR''​ //​revision//​ number with: ''​conda install %%--%%revision RR''​
 +  * There is more information in the ''​conda-meta/​history''​ installation log files. e.g., if you need to know the list of installation commands used:\\ <​code>​ $ egrep -e '​cmd:'​ -e '​==>'​ /​home/​share/​unix_files/​cdat/​miniconda3/​envs/​cdatm18_py2/​conda-meta/​history
 +==> 2019-03-07 16:19:55 <==
 +# cmd: /​home/​share/​unix_files/​cdat/​miniconda3/​bin/​conda create -n cdatm18_py2 --clone cdat-8.1_py2
 +==> 2019-03-07 16:35:11 <==
 +# cmd: /​home/​share/​unix_files/​cdat/​miniconda3/​bin/​conda install -n cdatm18_py2 -c conda-forge pillow pandas statsmodels seaborn scikit-image seawater gsw netcdf4 pyferret basemap-data-hires xlsxwriter cmocean rpy2 gdal windspharm
 +==> 2019-03-07 16:57:50 <==
 +# cmd: /​home/​share/​unix_files/​cdat/​miniconda3/​bin/​conda install -n cdatm18_py2 -c conda-forge -c vacumm vacumm
 +==> 2019-03-12 14:35:31 <==
 +# cmd: /​home/​share/​unix_files/​cdat/​miniconda3/​bin/​conda install -n cdatm18_py2 -c conda-forge pillow pandas statsmodels seaborn scikit-image seawater gsw netcdf4 pyferret basemap-data-hires xlsxwriter cmocean rpy2 gdal windspharm
 +==> 2019-03-12 15:49:54 <==
 +# cmd: /​home/​share/​unix_files/​cdat/​miniconda3/​bin/​conda install -n cdatm18_py2 -c stefraynaud -c conda-forge spanlib
 +==> 2019-03-12 17:30:26 <==
 +# cmd: /​home/​share/​unix_files/​cdat/​miniconda3/​bin/​conda install -n cdatm18_py2 -c conda-forge cmor</​code>​
 +    * You can also, use a script and the ''​conda''​ module available **in the ''​base''​ environment**:​ [[https://​github.com/​conda/​conda/​issues/​4545#​issuecomment-469984684|example]]
 ==== Misc ==== ==== Misc ====
  
other/uvcdat/conda_notes.1521037627.txt.gz · Last modified: 2018/03/14 14:27 by jypeter