other:uvcdat:cdat_conda:cdat_8_0_py2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
other:uvcdat:cdat_conda:cdat_8_0_py2 [2019/03/01 16:12] jypeter |
other:uvcdat:cdat_conda:cdat_8_0_py2 [2019/03/04 10:47] jypeter [Getting ready for a moving default CDAT] Added warning |
||
|---|---|---|---|
| Line 248: | Line 248: | ||
| <code>$ conda create -n cdat-8.0_py3 -c cdat/label/v80 -c conda-forge -c cdat python=3.6 cdat</code> | <code>$ conda create -n cdat-8.0_py3 -c cdat/label/v80 -c conda-forge -c cdat python=3.6 cdat</code> | ||
| + | |||
| + | ==== Installing CDAT nightly ==== | ||
| + | |||
| + | Notes: | ||
| + | |||
| + | * This page is about CDAT 8.0, but we have added a short nightly section here as a convenient shortcut. This should probably be moved to a stand-alone nightly page later | ||
| + | * [[https://github.com/CDAT/cdat/wiki/Obtain-CDAT-nightly-packages|Official nightly page]] | ||
| + | |||
| + | === Python 2.7 version === | ||
| + | |||
| + | <code>$ conda create -n cdat-nightly_py2 -c cdat/label/nightly -c conda-forge -c cdat python=2.7 cdat</code> | ||
| + | |||
| + | <wrap hi>Not tested!</wrap> Can this be updated with ''conda update -n cdat-nightly_py2 -c cdat/label/nightly -c conda-forge -c cdat --all'' ??? | ||
| + | |||
| + | === Python 3.6 version === | ||
| + | |||
| + | <code>$ conda create -n cdat-nightly_py3 -c cdat/label/nightly -c conda-forge -c cdat python=3.6 cdat</code> | ||
| ===== Cloning cdat to add specific packages for LSCE ===== | ===== Cloning cdat to add specific packages for LSCE ===== | ||
| Line 275: | Line 292: | ||
| </code> | </code> | ||
| + | |||
| + | ==== cdat nightly case ==== | ||
| + | |||
| + | ''conda create -n cdatm-nightly_py2 %%--%%clone cdat-nightly_py2'' | ||
| ===== Getting ready for a moving default CDAT ===== | ===== Getting ready for a moving default CDAT ===== | ||
| + | |||
| + | <note warning>This step should probably be listed at the **end**, especially in a multi-user environment! If there is already a ''cdatm'' link, make sure that the new version is stable and working correctly before updating the ''cdatm'' link</note> | ||
| We create a **//cdatm// symbolic link** in the ''envs'' directory, that has a //stable name// but can be moved to point to the latest default CDAT. In that case, most users can just activate this //cdatm// version and always get the latest stable version | We create a **//cdatm// symbolic link** in the ''envs'' directory, that has a //stable name// but can be moved to point to the latest default CDAT. In that case, most users can just activate this //cdatm// version and always get the latest stable version | ||
other/uvcdat/cdat_conda/cdat_8_0_py2.txt · Last modified: 2021/02/27 13:55 by jypeter
