[MacPorts] #45703: cdo installation doesn't find grib_api tables
MacPorts
noreply at macports.org
Fri Oct 31 08:16:28 PDT 2014
#45703: cdo installation doesn't find grib_api tables
----------------------------+--------------------------------
Reporter: shona.mackie@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.2
Keywords: cdo grib_api | Port: cdo
----------------------------+--------------------------------
I am on Mac OSX 10.7.5. I installed cdo +grib_api and the build seemed
fine. I think my problem is an issue with the way cdo links to the
grib_api - is there a way to check the configuration for an installed port
(so that I could check it searches for grib_api in the right place)? I've
described my problem below..
The grib_api was not installed before so I checked that it had been
installed properly by testing the commandline tools that come with it on a
grib edition 1 file, eg.
> grib_ls -P stepType filename.grib
returns:
stepType edition centre typeOfLevel level dataDate
stepRange dataType shortName packingType gridType
avgfc 1 ecmf surface 0 20130101
6 fc lsp grid_simple regular_ll etc etc
This worked fine. When I try cdo sinfo filename.grib for the same file, I
get an error because cdo can't find the definition table - the same
definition table that was successfully accessed by the grib_ls command to
define avgfc above:
> cdo sinfo filename.grib
returns:
cgribexGetTsteptype : GRIB time range 113 unsupported!
The definition that can't be found by cdo, but can be found by grib_ls, is
'time range 113' so I searched for where the definitions are:
> echo `grib_info | grep ":" | grep "definition" | cut -d ":" -f2 | tr -d
" "`
returns:
/opt/local/share/grib_api/definitions
I then looked to make sure that the definitions that cdo can't find are
actually there (eg time range 113 should be defined in 5.table):
> grep 113 `grib_info | grep ":" | grep "definition" | cut -d ":" -f2 | tr
-d " "`/grib1/5.table
returns:
113 113 Average of N forecasts (or initialized analyses); each product has
forecast period of P1 (P1=0 for initialized analyses); products have
reference times at intervals of P2, beginning at the given reference time.
The grib_api installation therefore appears to be working fine, but I
think there is a problem with how the cdo installation uses the grib_api.
I have tried with and without sudo, and have tried setting environment
variables such as GRIB_DEFINITION_PATH (sometimes required for the
grib_api, although in my case it seems to work fine without). Here's some
more information:
> cdo -V
returns:
Compiler: /usr/bin/clang -pipe -Os -arch x86_64 -D_THREAD_SAFE -pthread
version: unknown
Features: PTHREADS NC4 OPeNDAP Z JASPER UDUNITS2 PROJ.4 FFTW3
Libraries: proj/4.7
Filetypes: srv ext ieg grb grb2 nc nc2 nc4 nc4c
CDI library version : 1.6.4 of Oct 31 2014 14:44:25
CGRIBEX library version : 1.6.4 of Jun 27 2014 14:00:04
GRIB_API library version : 1.12.1
netCDF library version : 4.3.2 of Oct 30 2014 15:33:13 $
HDF5 library version : 1.8.13
SERVICE library version : 1.3.2 of Oct 31 2014 14:44:22
EXTRA library version : 1.3.2 of Oct 31 2014 14:44:21
IEG library version : 1.3.2 of Oct 31 2014 14:44:21
FILE library version : 1.8.2 of Oct 31 2014 14:44:21
I'm using macports version 2.3.2 and did port selfupdate before port
install cdo +grib_api.
Any suggestions are much appreciated.
--
Ticket URL: <https://trac.macports.org/ticket/45703>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list