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.
What you don't have to compare with are _warn.gem files written by the LDM, right? I can confirm that the gempak files downloaded from motherlode display correctly in NMAP2, so I have to assume that the seg fault you're seeing is due to a compilation problem with glibc/gfortran. On a related note, you may want to try building with g77 instead of gfortran, it's possible that could serve as a workaround for the runtime errors until I can figure out the gfortran 4.6+ issue. Michael > I was using this in my script -- curl -O " > http://motherlode.ucar.edu/decoded/gempak/storm/warn/${yy}${mm}${dd}${hh}_warn.gem" > to download the file. So I tried using wget. I used this syntax -- wget > http://motherlode.ucar.edu/decoded/gempak/storm/warn/2013050819_warn.gem > Each one downloaded the file into my $GEMDATA/storm/warn directory. I > tired changing user and owner to ldm and also to gempak. Each time when I > tried to display it via NMAP... the NMAP gui crashed. When I tried to run > a script to display the warnings and create a gif image when it got to the > warnings file I got this message -- > > Program received signal SIGSEGV: Segmentation fault - invalid memory > reference. > > Backtrace for this error: > #0 0x7F5C547C7037 > #1 0x7F5C547C7604 > #2 0x7F5C53EF4C1F > #3 0x7F5C53FFE5C4 > #4 0x7F5C54883818 > #5 0x7F5C54887C7B > #6 0x44D58C in gg_warn_ at ggwarn.f:419 > #7 0x4063BA in gpmap at gpmap.f:450 > Segmentation fault (core dumped) > > > I am not sure why this is happening and I agree...if I have the decoded > file and download it then it should display. What do you suggest I try > next? > > > Kevin > > > > address@hidden> wrote: > > > Have you tried wget vs download in a browser? > > > > As long as the wtch and warn files are put where GEMPAK programs can find > > them (e.g. $GEMDATA/storm/wtch/), you will be able to display them. > > > > Michael > > > > > > > > > > > Hi Michael, > > > > > > I was wondering while you are working on the decoder issue (at least on > > my > > > machine...lol) is if there is a way I can download watches and warnings > > via > > > motherlode? I went to the website (motherlode) that has the decoded and > > > raw data but when I tried to download the decoded watch/warning files > > they > > > wouldn't display on my system. Would I need to ftp the data or was it > > > "operator error" and I just need to save the files differently? I wrote a > > > script to download the files and then moved them to the proper directory > > > but when I tried to display the warning files on NMAP it crashed. > > > > > > KP > > > > > > > > > > > > Ticket Details > > =================== > > Ticket ID: JZH-369433 > > Department: Support GEMPAK > > Priority: High > > Status: Open > > > > > > Ticket Details =================== Ticket ID: JZH-369433 Department: Support GEMPAK Priority: High Status: Open