Re: 20050718: Gempak - gdbiint

Steve,

Thanks for your quick response!

I've downloaded version 5.8.2a and gdbiint works fine with
the new SPC grid files. 

Still curious why gdbiint from version 5.7.3 doesn't work correctly
with the SPC new grids files. I've placed the 
following files on our ftp anonymous ftp site:

ftp ftp.ssec.wisc.edu
cd pub/incoming
binary
get sfc_ced_sav.gz
get sfc_in_sav.gz
quit

Note:  sfc_in_sav is the SPC grid file
       sfc_ced_sav is the CED projection file created with gdcfil:

PROJ      Map projection/angles/margins|dr  ced
GRDAREA   Area covered by grid              20;-130;70;-60
KXKY      Number of grid points in x;y      #.25;.25
MAXGRD    Maximum number of grids           200
ANLYSS    Grid analysis block               4/2;2;2;2

gdbiint is run with the following:

GDFILE=sfc_in_sav
GDOUTF=sfc_ced_sav
GFUNC=MELT
GLEVEL=0
GVCORD=none
GDATTIM=LAST
GDNUM=LIST

Thanks!
        -Bob
For your information!



On Tue, Jul 19, 2005 at 10:19:57AM -0600, Unidata Support wrote:
> 
> Bob,
> 
> I checked the 5.8.2a distribution and both gdcfil and gdbiint were in the 
> linux
> binary.
> 
> The changes in GEMPAK since 5.8.1 now allow GEMPAK to do computations
> on grids with differing navigations, so at some point, the need to interpolate
> grids may not be necessary. That aside, there shouldn't be anything in the
> 5.8.3 grid files that prevents reading with your 5.7.3, unless they have 
> increased their
> maximum grid size to larger than what you have. I've always tried to keep the 
> Unidata
> release ahead of the NCEP version for that reason - our LLMXGD has been 
> 400,000 for several
> years, and NCEP's is 275,000.
> 
> I have a preliminary Linux binary of 5.8.3a ready for our workshops next week 
> that
> you can download...but the LLMXGD is the same as it has been. If you want to
> send me any grid file from SPC, or some more information about whether 
> gdbiint is finding the
> grid in the source file, and not writing the output, or failing before then 
> etc,
> I'd be happy to look int this more. Since you indicate that you had been 
> sucessful
> with previous grids from SPC with that same 5.7.3 binary you have, I was 
> leaning to wondering if SPC in particular has redefined their maximum grid 
> size 
> (I know that AWC produces some 1.6 million point grids!).
> 
> Steve Chiswell
> Unidata User Support
> 
> 
> >From: "Bob Rabin" <address@hidden>
> >Organization: UCAR/Unidata
> >Keywords: 200507182309.j6IN9Y8r000507
> 
> >Institution: NOAA / OAR NSSL
> >Package Version: 5.8.2a
> >Operating System: Linux
> >Hardware Information: SGI Linux
> >Inquiry: I am using the routine GDBIINT to interpolate from one grid 
> >projectio
> > n to another (CED). I have been using version 5.7.3 with grids from the SPC 
> > (
> > generated with 5.8.1). Recently, the SPC has started producing grids with 
> > ver
> > sion 5.8.3. Since then, my version of GDBIINT no longer works. It doesn\'t 
> > gi
> > ve an error message, but no data is written to the output grid (created 
> > with 
> > GDCFIL version 5.7.3). Must I use a more recent version of GDCFIL and 
> > GDBIINT
> > ? If so, which version? I couldn\'t find a binary for these in version 
> > 5.8.2a
> > ? Is there another solution?
> >
> >Thanks! -Bob Rabin
> >
> >
> >
> --
> **************************************************************************** <
> Unidata User Support                                    UCAR Unidata Program <
> (303)497-8643                                                  P.O. Box 3000 <
> address@hidden                                   Boulder, CO 80307 <
> ---------------------------------------------------------------------------- <
> Unidata WWW Service              http://my.unidata.ucar.edu/content/support  <
> ---------------------------------------------------------------------------- <
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.