Changeset 1442 in lmdz_wrf for trunk/tools/documentation


Ignore:
Timestamp:
Feb 9, 2017, 11:02:08 PM (8 years ago)
Author:
lfita
Message:

Adding more information about `python-netcdf4'

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/tools/documentation/install.html

    r1356 r1442  
    3434      <DIV CLASS="codetxt"># apt-get install dvipng</DIV>
    3535
    36       <LI>install netcdf4, python API interface to netCDF files (following <A CLASS="la" HREF="https://github.com/Unidata/netcdf4-python"  TARGET="_blank">https://github.com/Unidata/netcdf4-python</A>)</LI>
    37       <DIV CLASS="codetxt"># git clone https://github.com/Unidata/netcdf4-python.git<BR>
    38       cd netcdf4-python/</DIV>
    39         <UL>
    40         <LI>Editing `setup.cfg' to add/change some values (there are installation issues if `nc-config' is used along installation)</LI>
    41         <PRE><CODE>
     36      <LI>install netcdf4, python API interface to netCDF files</LI>
     37        <OL>
     38          <LI> Some new linux distributions (at least Debian >8) provide the netcdf4 API in the package systems:</LI>
     39            <DIV CLASS="codetxt"># apt-get install python-netcdf4</DIV>
     40          <LI> Otherwise, it can be manually done. Be careful with interferencies with anaconda (some issues on mixture of netcdf libraries have been detected).
     41          <UL>
     42            <LI>Following <A CLASS="la" HREF="https://github.com/Unidata/netcdf4-python"  TARGET="_blank">https://github.com/Unidata/netcdf4-python</A>)</LI>
     43            <DIV CLASS="codetxt"># git clone https://github.com/Unidata/netcdf4-python.git<BR>
     44              cd netcdf4-python/</DIV>
     45            <LI>Editing `setup.cfg' to add/change some values (there are installation issues if `nc-config' is used along installation)</LI>
     46            <PRE><CODE>
    4247use_ncconfig=False
    4348netCDF4_dir = /usr/local
     
    4651HDF5_INCDIR = /usr/include/hdf5/serial
    4752</CODE></PRE>
    48         </UL>
    49       <DIV CLASS="codetxt">
     53            <DIV CLASS="codetxt">
    5054# python setup.py build >& run_pysetup.log<BR>
    5155# python setup.py install >& run_pyinstall.log</DIV>
     56          </UL>
     57        </OL>
    5258      <LI>Getting the scripts, no need to be root:</LI>
    53       <DIV CLASS="codetxt"># exit<BR>
     59        <DIV CLASS="codetxt"># exit<BR>
    5460      $ cd $HOME <BR>
    5561      $ svn co http://svn.lmd.jussieu.fr/LMDZ_WRF/trunk/tools PyNCplot</DIV>
    56       <LI>Now all the scripts are held in ${HOME}/PyNCplot. It might be desirable to set an environment variable to make life easier:
     62     <LI>Now all the scripts are held in ${HOME}/PyNCplot. It might be desirable to set an environment variable to make life easier:
    5763      <DIV CLASS="codetxt">$ export pyHOME=${HOME}/PyNCplot</DIV>
    5864      <LI>Finally one need to compile the Fortran modules using the same python to run the scripts. This is done using a standard `Makefile' and the tool <A CLASS="la" HREF="https://docs.scipy.org/doc/numpy-dev/f2py/" TARGET="_blank">f2py</A> to link Fortran compiled codes to python. There are different versions for different LMD/IPSL and French HPC machines. For a standard linux 64-bits machine (debain 7) there is one example as `Makefile.foudre'. Follow the instructions there in after linking the appropriated file:</LI>
Note: See TracChangeset for help on using the changeset viewer.