[GEMPAK #AWI-238233]: GDDIAG seg fault

Hi Kelly,

There is no known bug that would cause this behavior in GEMPAK 6.2.0.  I still 
have the gfdl grid files from our earlier discussion and can verify that GDDIAG 
performs as intended with the given inputs you listed.

I'm thinking this might be a version conflict issue.  Can you verify that the 
GDDIAG executable was in fact built from 6.2.0 source?

"which gddiag" should provide this information.

If the output is /home/gempak/GEMPAK5.11.4/os/.../bin/gddiag then you're still 
sourcing the old Gemenviron file.  Check that ~gempak/NAWIPS/ is pointing to 
the updated GEMPAK6.2.0/ directory and not an older version.

Michael
Unidata


> Hi Michael,
> I apologize for just now getting back to you about this issue, but my
> local cluster folks were just now able to install 6.2.0.
> In trying to test it out for them, I have gone back to my original
> objective with gddiag -- while the segmentation fault goes away, it
> unfortunately still does not work.
> I can't figure out what is going on -- when I enter all the same things
> as below, this is what is returned:
> 
> GEMPAK-GDDIAG>l
> GDFILE   = gfdl_fut_comp_test_d02_f0500_pres.gem
> GDOUTF   = gfdl_fut_comp_d02_f0500_pres_full.gem
> GFUNC    = wg
> GDATTIM  = f05
> GLEVEL   = 800
> GVCORD   = pres
> GRDNAM   =
> GRDTYP   =
> GPACK    =
> GRDHDR   =
> PROJ     =
> GRDAREA  =
> KXKY     =
> MAXGRD   = 99999
> CPYFIL   = gfdl_fut_comp_test_d02_f0500_pres.gem
> ANLYSS   =
> GEMPAK-GDDIAG>r
> [DG -7]  Input grid WG ^400716/0000F005 @800 %PRES cannot be found.
> Parameters requested: GDFILE,GDOUTF,GFUNC,GDATTIM,GLEVEL,GVCORD,GRDNAM,
> GRDTYP,GPACK,GRDHDR,PROJ,GRDAREA,KXKY,MAXGRD,CPYFIL,ANLYSS.
> GEMPAK-GDDIAG>
> 
> BUT...if I then just go and do gdinfo on the file being used,
> 
> GEMPAK-GDINFO>l
> GDFILE   = gfdl_fut_comp_test_d02_f0500_pres.gem
> LSTALL   = YES
> OUTPUT   = T
> GDATTIM  = f05
> GLEVEL   = 800
> GVCORD   = pres
> GFUNC    = wg
> GEMPAK-GDINFO>r
> 
> GRID FILE: gfdl_fut_comp_test_d02_f0500_pres.gem
> 
> GRID NAVIGATION:
> PROJECTION:          LCC
> ANGLES:                39.2  -102.7    39.2
> GRID SIZE:          573 600
> LL CORNER:              35.38   -108.90
> UR CORNER:              42.71   -100.26
> 
> GRID ANALYSIS BLOCK:
> ANALYSIS TYPE:        BARNES
> DELTAN:               0.028
> DELTAX:           -9999.000
> DELTAY:           -9999.000
> GRID AREA:            34.00 -111.00   44.00  -99.00
> EXTEND AREA:          34.00 -111.00   44.00  -99.00
> DATA AREA:            34.00 -111.00   44.00  -99.00
> 
> Number of grids in file:   389
> 
> Maximum number of grids in file:  29999
> 
> NUM       TIME1              TIME2           LEVL1 LEVL2  VCORD PARM
> 67     400716/0000F005                        800         PRES WG
> Parameters requested: GDFILE,LSTALL,OUTPUT,GDATTIM,GLEVEL,GVCORD,GFUNC.
> GEMPAK-GDINFO>
> 
> 
> ....there it is!
> The grid is there, but gddiag insists that it's not.
> I know my gempak might be getting rusty from under-use lately, but I'm
> drawing a blank here, and would at a minimum, be able to tell my cluster
> folks if they've installed the correct version of gempak and done so
> correctly.
> 
> Thank you for any insight you might be able to offer!
> Best,
> Kelly
> 
> 
> 
> 
> 
> 
> On 12/30/2010 1:46 PM, Unidata GEMPAK Support wrote:
> > Kelly,
> >
> > I confirmed GDDIAG correctly creates the new file and adds the grid WG to 
> > the file with 6.2.0.  Hopefully you are able to update from 5.11.4 to 6.2.0 
> > without any major problems, but if you encounter anything problematic let 
> > me know and I'll assist you.
> >
> >   GDFILE   = gfdl_fut_comp_test_d02_f0500_pres.gem
> >   GDOUTF   = gfdl_fut_comp_d02_f0500_pres_full.gem
> >   GFUNC    = WG
> >   GDATTIM  = 400716/0000F005
> >   GLEVEL   = 800
> >   GVCORD   = pres
> >   GRDNAM   =
> >   GRDTYP   =
> >   GPACK    =
> >   GRDHDR   =
> >   PROJ     =
> >   GRDAREA  =
> >   KXKY     =
> >   MAXGRD   = 99999
> >   CPYFIL   = gfdl_fut_comp_test_d02_f0500_pres.gem
> >   ANLYSS   =
> >   GEMPAK-GDDIAG>R
> >
> >      TIME1             TIME2         LEVL1 LEVL2   VCORD PARM
> > 400716/0000F005                       800          PRES WG
> > Enter a new grid parameter name,<cr>  to accept or type EXIT:
> >
> >
> > Best,
> >
> > Michael
> >
> >
> >> Hi Michael,
> >> Thank you so much for your fast reply.
> >> I just uploaded three files to the repository -- the two files I'm
> >> trying to combine, and the script I'm trying to use (however, the seg
> >> fault occurs when just running interactively and adding one grid at a
> >> single level too).
> >> Thanks again very much for your help,
> >> Kelly
> >>
> >>
> >>
> >>
> >> On 12/30/2010 1:33 PM, Unidata GEMPAK Support wrote:
> >>> Hi Kelly,
> >>>
> >>> With the information provided I can't tell if you're experiencing the 
> >>> problems reported with 5.11.4 (due to a bug in the grid diagnostics 
> >>> libraries) or if you're experiencing something different.
> >>>
> >>> My first suggestion would be to upgrade to 6.2.0 and try the exact same 
> >>> process.  Other than that, I would need a copy of your GDFILE 
> >>> (gfdl_fut_comp_test_d02_f0500_pres.gem) to test on my system here.
> >>>
> >>> If possible, could you upload this file to the RAMADDA GEMPAK repository 
> >>> located at
> >>>
> >>> http://motherlode.ucar.edu/repository/alias/gempakuploads/
> >>>
> >>> Best,
> >>>
> >>> Michael James
> >>> Unidata
> >>>
> >>>
> >>>
> >>>> Hi,
> >>>>
> >>>> I am trying to run GDDIAG on the system listed below, but whenever I try
> >>>> to write a grid to a file, it segmentation faults with no other error.
> >>>>
> >>>> While searching around for a solution, I came across some gempak support
> >>>> threads that mention a past issue with RH5 and gfortran, which I think
> >>>> is what I'm using...but I can't tell what the solution to the problem is
> >>>> (or if that is even my problem)?
> >>>>
> >>>> The version is 5.11.4, and it was installed on the system below in June
> >>>> 2010.
> >>>>
> >>>> Thanks in advance for any help or suggestions you may be able to offer!
> >>>> Kelly Mahoney
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> [kmahoney@fe1 CFAD]$ uname -a
> >>>> Linux fe1 2.6.18-194.11.4.el5-perfctr #1 SMP Wed Oct 27 18:35:31 GMT
> >>>> 2010 x86_64 x86_64 x86_64 GNU/Linux
> >>>>
> >>>> [kmahoney@fe1 CFAD]$ gcc --version
> >>>> gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)
> >>>> Copyright (C) 2006 Free Software Foundation, Inc.
> >>>> This is free software; see the source for copying conditions.  There is 
> >>>> NO
> >>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
> >>>> PURPOSE.
> >>>>
> >>>>>    GEMPAK-GDDIAG>l
> >>>>>    GDFILE   = gfdl_fut_comp_test_d02_f0500_pres.gem
> >>>>>    GDOUTF   = gfdl_fut_comp_d02_f0500_pres_full.gem
> >>>>>    GFUNC    = WG
> >>>>>    GDATTIM  = 400716/0000F005
> >>>>>    GLEVEL   = 800
> >>>>>    GVCORD   = pres
> >>>>>    GRDNAM   =
> >>>>>    GRDTYP   =
> >>>>>    GPACK    =
> >>>>>    GRDHDR   =
> >>>>>    PROJ     =
> >>>>>    GRDAREA  =
> >>>>>    KXKY     =
> >>>>>    MAXGRD   = 99999
> >>>>>    CPYFIL   = gfdl_fut_comp_test_d02_f0500_pres.gem
> >>>>>    ANLYSS   =
> >>>>>    GEMPAK-GDDIAG>r
> >>>>> Segmentation fault
> >>>>
> >>>>
> >>>>> Kelly,
> >>>>>
> >>>>> I  have solved the problem with GEMPAK and I was able to link your
> >>>>> code.  I have installed GEMPAK 5.11.4 on the system.  You will have to
> >>>>> logout and login again to get the environment set correctly to use it.
> >>>>>
> >>>>> The variable $GEMPAK is defined as the base directory.  To
> >>>>> link against the libraries, use $GEMPAKLIB.  Both $GEMPAK/bin
> >>>>> and $GEMPAK/os/linux64/bin are on the path by default.
> >>>>>
> >>>>> Craig
> >>>>>
> >>> Ticket Details
> >>> ===================
> >>> Ticket ID: AWI-238233
> >>> Department: Support GEMPAK
> >>> Priority: Normal
> >>> Status: Open
> >>>
> >>
> >
> > Ticket Details
> > ===================
> > Ticket ID: AWI-238233
> > Department: Support GEMPAK
> > Priority: Normal
> > Status: Open
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: AWI-238233
Department: Support GEMPAK
Priority: Normal
Status: Open