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

20030723: Trying to use GRIBDEC/mcgribdec on Linux with AMPS data (cont.)

>From: Matthew Lazzara <address@hidden>
>Organization:  SSEC/AMRC
>Keywords:  200307221750.h6MHovLd006453 McIDAS gribdec

Hi Matthew,

>Yes, I can appreciate the "busy, busy, busy" - not much different for me.
>Here is a sample AMPS grib file:
>
>ftp://antarctica.ssec.wisc.edu/pub/requests/unidata/amps.grb
>
>Let me know what you find out....let me know if I need to do something
>differently or get new code from you.

Here is what I did:

- download the amps.grb file using binary mode in anonymous FTP
- decode the file first using gribdec.k built under Sun Solaris 9 linked
  against McIDAS-X v2003 built using gcc/g77
- logged onto a Unidata RedHat 7.3 Linux machine and rebuilt the
  gribdec distribution linking against McIDAS-X v2003 built with
  gcc/g77
- reran the decoding of the AMPS data with no problems:

% ./gribdec.k /home/mcidas/gribdata/amps.grb 6000
 Input GRIB file: /home/mcidas/gribdata/amps.grb
Output GRID file: GRID6003
GRIB messages:: Found: 137 Decoded: 137 Written: 137
GRIBDEC: Done

I then tried your initial invocation line:

% rm GRID6003
% ./gribdec.k /home/mcidas/gribdata/amps.grb 6000 'AMPS_22/07/2003_0_UTC_D1'
 Input GRIB file: /home/mcidas/gribdata/amps.grb
Output GRID file: GRID6003
GRIB messages:: Found: 137 Decoded: 137 Written: 137
GRIBDEC: Done

My conclusion is that gribdec.k is working correctly and the format of
the title is OK.

So, the questions are:

- when did you grab the gribdec.tar.Z bundle
- how did you run make to build gribdec.k
- is amps.grb _really_ located in the same directory you were in when
  you ran gribdec.k

>Thanks so much!

This is a puzzler.

Tom