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

20051108: Gempak - GARP forecast soundings crash

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: 20051108: Gempak - GARP forecast soundings crash
  • Date: Tue, 08 Nov 2005 12:15:57 -0700
David,

This "new" bug in model soundings is caused by gcc's handling of string 
constants
when passed to a Fortran routine. The code hasn't changed in many years, but 
now 
gcc is having trouble. I have patched this routine for the upcoming 5.8.4 
release
but you can update your current version as needed. It you want to patch the 
source code,
I can send you the reference to our site where I posted the fix. If you are 
running
a binary release, I can send you the new executable.

Steve Chiswell
Unidata User Support



>From: "David Nolan" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200511081743.jA8HhDCs014535

>Institution: University of Miami
>Package Version: 2.1
>Operating System: Linux
>Hardware Information: x86
>Inquiry: Greetings from Miami.
>
>I'm using GARP to teach a course on Weather Analysis here at the University of
>  Miami. The program works quite well, but I just discovered that it crashes e
> very time I try to plot a model forecast sounding - either Skew-T or Stuve. I
> t works if I choose Linear or Logarithmic vertical coordinates - but those ar
> e hard to infer stability from.
>
>When it crashes, it gives the "Segmentaion Error" message.
>
>Do you have any suggestions?
>
>Thanks!
>
>Dave Nolan
>
>
>
--
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.