fimex:install

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
fimex:install [2012-08-21 07:20:37]
heikok [Build] 		fimex:install [2022-05-31 09:29:32] (current)
Line 1: Line 1:
 ====== Installation ====== ====== Installation ======
  
-===== Pre-build Packages ===== +===== Pre-built Packages =====
- +
-If you are lucky to run one of the following operating systems, you can install fimex from a package repository: +
- +
-==== Ubuntu 10.04 Lucid ==== +
- +
-Ubuntu Lucid packages are available since 0.28 at: https://launchpad.net/~heiko-klein/+archive/fimex +
- +
-==== Ubuntu 8.04 Hardy ==== +
- +
-Ubuntu Lucid packages are available up to 0.25 at: https://launchpad.net/~heiko-klein/+archive/fimex+
  
 +If you are lucky to run one of the following operating systems, you can install fimex from a package repository, please check the [[fimex:download|download]] page.
  
 ===== Dependencies ===== ===== Dependencies =====
  
 Fimex requires at least the following libraries to be installed for compilation: Fimex requires at least the following libraries to be installed for compilation:
-  * c99/c++ compiler+  * c99/c++11 compiler
   * [[http://www.xmlsoft.org|libxml2]] >= 2.5.0   * [[http://www.xmlsoft.org|libxml2]] >= 2.5.0
-  * [[http://www.boost.org/|boost library]] >= 1.32 
   * [[http://proj.maptools.org|proj-4]] >= 4.4.9   * [[http://proj.maptools.org|proj-4]] >= 4.4.9
-  * [[http://www.unidata.ucar.edu/packages/udunits/|udunits]] 1.12.x or >= 2.1.x+  * [[http://www.unidata.ucar.edu/packages/udunits/|udunits]] >= 2.1.x 
 +  * [[https://github.com/metno/mi-cpptest|mi-cpptest]] 
 +  * [[https://github.com/metno/mi-programoptions|mi-programoptions]] 
 +  * [[https://github.com/pybind/pybind11|pybind11]]
   
-To configure the different file formats it requires:+To configure the different file formats or features it requires:
   * [[http://www.unidata.ucar.edu/software/netcdf/|NetCDF]] (netcdf-3 > 3.6)   * [[http://www.unidata.ucar.edu/software/netcdf/|NetCDF]] (netcdf-3 > 3.6)
-  * Felt (libmi or libfelt (bundled)) +  * [[https://software.ecmwf.int/wiki/display/ECC/ecCodes+Home|ecCodes]] 
-  * [[http://www.ecmwf.int/products/data/software/grib_api.html|grib_api]] (> 1.4)+  * [[http://log4cpp.sourceforge.net/|Log4cpp]]: advanced logging library 
 +  * [[http://www.openmp.org/|OpenMP-3.0]] enable compiler: Parallelization 
 +  * [[http://en.wikibooks.org/wiki/Fortran_2003|Fortran-2003]] compiler (tested with gfortran-4.6 and ifortran-12)
  
 ===== Build ===== ===== Build =====
  
-The installation follows the usual autoconf rules, see 'INSTALL' for +See [[https://github.com/metno/fimex/blob/master/README.md|README.md]] for build instructions.
-extensive information. Since Fimex makes some floating-point calculations +
-in large loops, it is advisable to switch on SIMD/SSE operations in your +
-compiler. On a Xeon machine with a x386 machine and gcc, I use the  +
-following flags (those are default for x86-64) (see [[http://heikok.blogspot.com/2008/08/microbenchmark-of-sse-in-c-revisited.html|microbenchmark of sse]] for more information) +
- +
-Since fimex 0.21 +
-<code> +
-CFLAGS='-O2 -mfpmath=sse -msse2 -ftree-vectorize -fno-math-errno' CXXFLAGS='-O2 -mfpmath=sse -msse2 -ftree-vectorize -fno-math-errno' ./configure --with-netcdf=/usr --with-udunits=/usr +
-make +
-make check +
-make install +
-</code> +
- +
-==== Static netcdf4 ==== +
- +
-Use nc-config or package-config scripts to detect library dependencies, e.g.  +
-<code> +
-./configure --with-netcdf=/paht/to/nc-config +
-</code> +
- +
- +
-==== Static grib_api ==== +
- +
-The static grib_api does not come with an automatic library detection program like package-config. When linking against grib_api, you need to know the required library flags, e.g. ''-L/path/to/jasper -ljasper -lpng -ljpeg'' or ''-L/path/to/openjpeg -lopenjpeg -lpng -ljpeg''. Put this string into the ''LDFLAGS'' variable before running configure, e.g.  +
-<code> +
-export LDFLAGS='-L/path/to/openjpeg -lopenjpeg -lpng -ljpeg' +
-./configure --with-grib_api=/path/to/grib_api +
-</code> +
  
 ==== Optimizations with gcc ==== ==== Optimizations with gcc ====
Line 78: Line 44:
   * interpolation: fill2d (good parallelization on z-axis)   * interpolation: fill2d (good parallelization on z-axis)
   * interpolation with coord_nearestneighbor (good parallelization in startup)   * interpolation with coord_nearestneighbor (good parallelization in startup)
- 
-=== CAVEAT === 
- 
-Due to a bug in libtool, the options required for linking again a parallelized libfimex are not set automatically and need be entered manually by the programmer using libfimex: https://lists.gnu.org/archive/html/bug-libtool/2011-03/msg00022.html 
- 
  
 ===== Test ===== ===== Test =====
Line 89: Line 50:
   * Put this file into the test-catalogue   * Put this file into the test-catalogue
   * gunzip the file   * gunzip the file
-  * run 'make check' (make check will work even without the testdata and skip a lot of tests)+  * run ''make test'' (it will work even without the testdata and skip a lot of tests) 
 + 
 +===== Known Problems ===== 
 + 
 +==== udunits1 and FMRC ==== 
 + 
 +udunits1 does not differ between a date and a timespan, e.g.  
 +<code> 
 +$ ./udunits 
 +You have: hours 
 +You want: hours since 2010-01-01 00:00:00 
 +    <hours since 2010-01-01 00:00:00> = <hours>*1 - 78888 
 +    <hours since 2010-01-01 00:00:00> = <hours>/1 - 78888 
 +</code> 
 + 
 +Therefore, data with two time-axis, e.g. in [[http://www.unidata.ucar.edu/software/netcdf/ncml/v2.2/FmrcAggregation.html|ForecastModelRuntimeConvention]] cannot get read proberly. This results in a 
 +test-failure: 
 +<code> 
 +unknown location:0: fatal error in "test_cs_slicebuilder_reftime": unknown type 
 +testCoordinateSystemSliceBuilder.cc:69: last checkpoint 
 + 
 +*** 1 failure detected in test suite "Master Test Suite" 
 +FAIL: testCoordinateSystemSliceBuilder 
 +</code> 
 + 
 +If you don't intend to use FMRC, you can ignore this error, otherwise, you should upgrade to udunits2. 
 + 
 + 
 +==== udunits1 and udunits2 ==== 
 + 
 +If both udunits1 and udunits2 are available on the machine, fimex might prefer udunits1 unless explicitly disabled. To explicitly disable udunits1, use: 
 +<code> 
 +./configure --without-udunits --with-udunits2 ... 
 +</code> 
 + 
 +==== MacOS X and gcc ==== 
 + 
 +Under MacOS X strings may come in different flavour for gcc, either static or fully dynamic. Libraries compiled with one type of strings don't work well with programs/libraries compiled with the other type. This might result in an segmentation fault when running ''fimex'' with the message: 
 +<code> 
 + pointer being freed not allocated 
 +</code> 
 + 
 +boost::program_options is affected by this and must be compiled with the same compiler as fimex is compiled, e.g. 
 +  * download boost 
 +  * add ''using darwin : : g++-mp-4.6 ;'' in ''user-config.jam'' 
 +  * run <code> 
 +./bootstrap.sh --prefix=/usr/local 
 +./b2 install 
 +</code> 
 +For more information, see http://lists.boost.org/boost-users/2010/06/59548.php 
 + 
 + 
 +==== AIX ==== 
 + 
 +The boost libraries (1.44) are not compatible with the AIX XL/C++ compiler V10 and we had to compile boost and fimex with gcc to get it working under AIX. This might have been improved with newer versions of the AIX compiler, but hasn't been tested: http://www-01.ibm.com/support/docview.wss?uid=swg27018656 
  • fimex/install.1345533637.txt.gz
  • Last modified: 2022-05-31 09:23:15
  • (external edit)