Changes between Initial Version and Version 1 of Ticket #45703
- Timestamp:
- Oct 31, 2014, 4:45:53 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #45703
- Property Owner changed from macports-tickets@… to takeshi@…
- Property Keywords cdo grib_api removed
-
Ticket #45703 – Description
initial v1 1 I am on Mac OSX 10.7.5. I installed cdo +grib_apiand 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..1 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.. 2 2 3 3 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. 4 {{{ 4 5 > grib_ls -P stepType filename.grib 6 }}} 5 7 returns: 8 {{{ 6 9 stepType edition centre typeOfLevel level dataDate stepRange dataType shortName packingType gridType 7 10 avgfc 1 ecmf surface 0 20130101 6 fc lsp grid_simple regular_ll etc etc 11 }}} 8 12 9 This worked fine. When I try cdo sinfo filename.gribfor 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:13 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: 10 14 15 {{{ 11 16 > cdo sinfo filename.grib 17 }}} 12 18 returns: 19 {{{ 13 20 cgribexGetTsteptype : GRIB time range 113 unsupported! 21 }}} 14 22 15 23 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: 16 24 {{{ 17 25 > echo `grib_info | grep ":" | grep "definition" | cut -d ":" -f2 | tr -d " "` 26 }}} 18 27 returns: 28 {{{ 19 29 /opt/local/share/grib_api/definitions 30 }}} 20 31 21 32 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): 22 33 {{{ 23 34 > grep 113 `grib_info | grep ":" | grep "definition" | cut -d ":" -f2 | tr -d " "`/grib1/5.table 35 }}} 24 36 returns: 37 {{{ 25 38 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. 39 }}} 26 40 27 41 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. … … 29 43 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: 30 44 45 {{{ 31 46 > cdo -V 47 }}} 32 48 returns: 49 {{{ 33 50 Compiler: /usr/bin/clang -pipe -Os -arch x86_64 -D_THREAD_SAFE -pthread 34 51 version: unknown … … 45 62 IEG library version : 1.3.2 of Oct 31 2014 14:44:21 46 63 FILE library version : 1.8.2 of Oct 31 2014 14:44:21 64 }}} 47 65 48 66 I'm using macports version 2.3.2 and did port selfupdate before port install cdo +grib_api.