Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
titleGRIB/GRIB_API related questions

Also see: GRIB_API Frequently Asked Questions.

Expand
titleClick here to expand for questions and answers...

Q. I get an error message from GRIB_API when I run the model saying 'boot.def' not found?

The 'boot.def' file is the GRIB definitions file. The location of the boot.def file is hardcoded into the GRIB_API library when it is compiled. Make sure that the directory where GRIB_API was installed has not moved. If it has this hardcoded location will be wrong. You can override this location by using the environment variable: GRIB_DEFINITION_PATH and set this to the directory containing the boot.def file.

Q. OpenIFS fails with an error message from GRIB_API.

A. This usually indicates an error in the GRIB file rather than the model. Please email openifs-support@ecmwf.int and include the model output file (NODE_001.01) and the job log.

Q. What are the GRIB_API environment variables and what do they mean?

A. The environment variables for GRIB_API are described on the GRIB_API software support page.

Q. When compiling GRIB_API on Mac OS X I get an error: ld: duplicate symbol _grib_file_not_found in .libs/action_class_alias.o and .libs/action.o

A. This is a known issue with compiling on Mac OS X. See this page on the GRIB_API Installation FAQ for the workaround.

Q. How do I convert from GRIB to netCDF?

Q.What software will read/write GRIB files?

...

Panel
titleMac OS X specific questions
Expand
titleClick to expand
for questions and answers

Q. When compiling GRIB_API on Mac OS X I get an error: ld: duplicate symbol _grib_file_not_found in .libs/action_class_alias.o and .libs/action.o

A. This is a known issue with compiling on Mac OS X. See this page on the GRIB_API Installation FAQ for the workaround.

Q. I'm using the Intel compiler and the MKL library but get this error: dyld: Library not loaded: libmkl_intel_lp64.dylib when I run OpenIFS.

A. On Mac OS X, the MKL library is a dynamic (shared) library which is loaded at runtime and not when the model is compiled. To ensure the library is found you need to add the directory containing the library to your dynamic library path environment variable (DYLD_LIBRARY_PATH). The Intel compiler supplies a script that correctly sets the compile environment for you which should be run. This is normally found in the Intel compiler install directory: /opt/intel/Compiler/11.0/054/Frameworks/mkl/tools/environment/mklvars.sh.

 

See also:

GRIB_API Frequently Asked Questions

...