[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20050406:CODIAC grib-gempak problems

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20050406:CODIAC grib-gempak problems
  • Date: 06 Apr 2005 10:53:58 -0600
Jeff,

You should definitely be using dcgrib2 for all decoding!!! 

Since I don't see any output from the first 2 entries, it would
appear that there is nothing found in the file that looks like a GRIB
entry that would cause the decoder to open the appropriate tables.

So, I'd suggest looking at the files in question...and did I mention,
using dcgrib2?!

Chiz

Steve Chiswell
Unidata User Support






On Wed, 2005-04-06 at 10:38, Jeff Weber wrote:
> Hey Chiz,
> 
> Any insight?
> 
> Case 8 is using data from Jan '97
> 
> Case 10 is using data from May '97
> 
> Besides the obvious "upgrade to 5.8.1" response, do you know of any reason
> why this would be failing...with no error message?
> 
> I suppose the Case 8 data could be bad, but would suspect error messages
> of some sort...
> 
> Hoping you may have some clues before I go into de-bug mode ;)
> 
> Thanks,
> 
> Jeff
> ---------------------------------------------------------------------
> 
> ---------- Forwarded message ----------
> Date: Wed, 6 Apr 2005 10:27:47 -0600 (MDT)
> From: John J. Allison <address@hidden>
> To: address@hidden, address@hidden
> Subject: grib-gempak problems
> 
> A user is trying to get comet case 8's RUC data in gempak format.
> The format conversion from grib to gempak is failing.
> There are no error messages and the exit status is 0 (success),
> yet no output file is produced. This seems to happen with all
> RUC data up to case 9, and no other data. Both gempak 5.4 and 5.7.4
> do the same. Below are examples. The 1st 2 fail, the next 2 succeed.
> 
> hurricane[108]% cat 
> /archive/codiac/comet/ccs008/grib/ruc/97010312f09_ruc.grib | 
> /opt/gempak5.4-thunder/bin/sol/dcgrib -g 
> /opt/gempak5.4-thunder/gempak5.4/tables PACK /codiac_tmp/out1
> 
> hurricane[109]% cat 
> /archive/codiac/comet/ccs008/grib/ruc/97010312f09_ruc.grib | 
> /opt/gempak5.7.4/bin/sol_gcc/dcgrib -g /opt/gempak5.7.4/gempak/tables PACK 
> /codiac_tmp/out2
> 
> hurricane[110]% cat 
> /archive/codiac/comet/ccs010/grib/ruc/ruc.970526.ruc.T06Z.PGrbF12 | 
> /opt/gempak5.4-thunder/bin/sol/dcgrib -g 
> /opt/gempak5.4-thunder/gempak5.4/tables PACK /codiac_tmp/out3
>  Changing center table to cntrgrib1.tbl
>  Changing vertical coord table to vcrdgrib1.tbl
>  Changing WMO parameter table to wmogrib2.tbl
>  Changing center parameter table to ncepgrib2.tbl
> 
> hurricane[111]% cat 
> /archive/codiac/comet/ccs034/grib/ruc/us008_gf086_00081201_ZxQBx | 
> /opt/gempak5.7.4/bin/sol_gcc/dcgrib -g /opt/gempak5.7.4/gempak/tables PACK 
> /codiac_tmp/out4
>  Changing center table to cntrgrib1.tbl
>  Changing vertical coord table to vcrdgrib1.tbl
>  Changing WMO parameter table to wmogrib2.tbl
>  Changing center parameter table to ncepgrib2.tbl
> 
> 
> Any ideas?
> 
> Thanks,
> 
> John Allison
> address@hidden