Version 2 (modified by Vinod Kumar, 7 months ago) (diff)



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).

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 nwp_pytools27 environment on Raijin, where it used conda/4.4.11 (?) (see section Base installation).

The environment related locations proposed by Wenming is:

conda software: ~access/bom/conda/software
conda channel: ~access/bom/conda/channel
conda envs: ~access/bom/conda/env
conda installations: ~access/apps/miniconda, 
modules files: ~access/modules/bom_conda_env

Later on, a decision was taken to name the environment as nwptools_py2.


The development and installation of nwp_pytools2 is described in the following links.

nwptools_py2 development

nwptools_py2 installation