Changeset 2245 in lmdz_wrf
- Timestamp:
- Nov 19, 2018, 8:19:04 PM (6 years ago)
- Location:
- trunk/tools/documentation
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/tools/documentation/PyNCplot.css
r2129 r2245 35 35 /* Environments */ 36 36 div.codetxt{width:80%;height:10%;text-align:left;text-indent:0px;background-color:rgb(192,192,192); 37 font-size:0.9em;font-family:"Courier New";color:rgb(0,0,0);} 38 div.largecodetxt{width:80%;text-align:left;text-indent:0px;background-color:rgb(192,192,192); 37 39 font-size:0.9em;font-family:"Courier New";color:rgb(0,0,0);} 38 40 -
trunk/tools/documentation/install.html
r1709 r2245 62 62 <LI>Now all the scripts are held in ${HOME}/PyNCplot. It might be desirable to set an environment variable to make life easier: 63 63 <DIV CLASS="codetxt">$ export pyHOME=${HOME}/PyNCplot</DIV> 64 <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 9 with gcc compilers) there is one example as `Makefile.llamp'. Take one and specify a series of different variables specifically for the given machine65 <DIV CLASS=" codetxt">64 <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 CIMA's machines, different LMD/IPSL and French HPC machines. For a standard linux 64-bits machine (debain 9 with gcc compilers) there is one example as `Makefile.llamp'. Take one and specify a series of different variables specifically for the given machine 65 <DIV CLASS="largecodetxt"> 66 66 FC = gfortran # Fortran compiler<BR> 67 67 F2PY = /usr/bin/f2py # Path to the f2py tool<BR> 68 F2PYF = # Fortran compiler (when system's one is not used)<BR> 68 69 NCLIBFOLD = /usr/lib/x86_64-linux-gnu # Path to netcdf libraries<BR> 69 70 NCINCFOLD = /usr/include # Path to netcdf includes<BR> 71 NCLIBFFOLD = /usr/lib/x86_64-linux-gnu # Path to netcdf-fortran interface libraries<BR> 72 NCINCFFOLD = /usr/include # Path to netcdf-fortran interface includes<BR> 73 </DIV> 74 <LI><B>NOTE:</B> One will not be able to compile all the set of programs within an anaconda environment due to problems with anaconda. Installation of netcdf4 colides with installed <A CLASS="la" HREF="https://anaconda.org/matthewharrison/libnetcdff" TARGET="_blank">libnetcdff</A>. When installing it:</LI> 75 <DIV CLASS="largecodetxt"> 76 $ conda install netcdf4 <BR> 77 (...) <BR> 78 - netcdf4<BR> 79 The following packages will be downloaded:<BR> 80 <BR> 81 package | build<BR> 82 ---------------------------|-----------------<BR> 83 libnetcdf-4.6.1 | h10edf3e_2 1.3 MB<BR> 84 <BR> 85 The following NEW packages will be INSTALLED:<BR> 86 <BR> 87 netcdf4: 1.4.2-py27h4b4f87f_0 <BR> 88 <BR> 89 The following packages will be REMOVED:<BR> 90 <BR> 91 libnetcdff: 4.4.4-0 matthewharrison<BR> 92 <BR> 93 The following packages will be UPDATED:<BR> 94 <BR> 95 libnetcdf: 4.4.0-hf6ef953_0 matthewharrison --> 4.6.1-h10edf3e_2 96 </DIV> 97 <LI> Because of that, Makefile is split in two compilation sub-sets 98 <DIV CLASS="codetxt"> 99 $ make pymods: compilation of Fortran modules used in the python scripts<BR> 100 $ make NCfortran: compiation of Fortran modules and main programs which require <BR> 101 netCDF-fortran interface: (for: DistriCorrection and trajectories_overlap)<BR> 102 $ make: compiles all components 70 103 </DIV> 71 104 <LI>Then one only needs to link the Makefile and compile</LI> 72 105 <DIV CLASS="codetxt"> 73 106 $ ln -s Makefile.[machine].[compiler] ./Makefile<BR> 74 $ make >& run_make.log107 $ make [OptionalFlags] >& run_make.log 75 108 </DIV> 76 109 <LI>At the end one should have: </LI>
Note: See TracChangeset
for help on using the changeset viewer.