Changes between Version 8 and Version 9 of access/BomAccessDocumentation/bom-conda


Ignore:
Timestamp:
Nov 28, 2019 9:11:20 AM (10 months ago)
Author:
Vinod Kumar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • access/BomAccessDocumentation/bom-conda

    v8 v9  
    9797
    9898== Various family of environments ==
    99 * [wiki:access/BomAccessDocumentation/bom-conda/nwp-pytools nwp-pytools]
     99* [wiki:access/BomAccessDocumentation/bom-conda/nwp-pytools nwp_pytools]
    100100
    101101== Gadi transition ==
     
    105105The python environments in Gadi will also be called nwp_pytools. After discussions between Milton, Jin and Vinod, it has been agreed that the naming scheme could be of the format nwp_pytools2/YYYY.MM and nwp_pytools3/YYYY.MM. That is, two different "package names" for python 2 and 3 variants, with each environment identified by installation date (similar to Intel compilers). Users will get the latest environment by loading the package without specifying a version (e.g. module load nwp_pytools2).
    106106
    107 It was found that for the same yml file, two versions of miniconda produce two different environments. This highlights the risk of depending on third party miniconda installations. Hence it is agreed that Bureau manages its own miniconda versions on Gadi. Wenming has already done this for the {{{conda/nwp_pytools27}}} environment on Raijin, where it used conda 4.4 (see section `Base installation`).
     107It was found that for the same yml file, two versions of miniconda produce two different environments. This highlights the risk of depending on third party miniconda installations. Hence it is agreed that Bureau manages its own miniconda versions on Gadi. Wenming has already done this for the {{{conda/nwp_pytools27}}} environment on Raijin, where it used conda 4.4.11 (see section `Base installation`).
    108108
    109109The environment related locations proposed by Wenming is: