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.
Hi Charles, Thank you for writing back and for the attached pic. I need to carve out some time to look at this but it's likely a small change to the grib tables will fix it. I will get back to you when I have more. Michael > Michael, > > Thank you for your quick response. Here is some more info: > > 1) Yes, I am decoding each forecast hour to its own file. > 2) The full file size is 386 MB. However, I have also tried using a file that > only included the 10 meter UGRD and VGRD (1.4 MB) to plot WND and I end up > with the same errors. > 3) I have attached a gif of what happens when trying to plot MSPL, 10 meter > wind barbs and isotachs. The script I used for this will plot the rap, nam > 218 and gfs without issue. > > I continued my search on the support page after I sent the original email and > found this, > http://www.unidata.ucar.edu/mailing_lists/archives/gembud/2012/msg00062.html > > I attempted using the MDGDEC grib packing method as stated in this, but it > still either returns a segmentation fault or plots the winds as in the > attached gif. > > Thanks again, > > Charles > > -----Original Message----- > From: Unidata GEMPAK Support [mailto:address@hidden] > Sent: Thursday, April 18, 2013 3:50 PM > To: Lubensky, Charles A. > Cc: address@hidden > Subject: [GEMPAK #VQK-601999]: NAM NEST Grid 227 Segmentation Fault > > Hi Charles, > > This is the first I have heard of problems with the nam 227 nest. My first > guess is that the decoded files is too large that some limit (# of grids open > at once, size of file) was reached and that caused the segfault or > incorrectly displayed data. > > But I need more information from you, such as > > 1) are you decoding each forecast time to it's own file? > 2) how large is the file you're using as GDFILE? > 3) what does this "incorrectly displayed" data look like? attach screenshots > or gif produced with GDPLOT2 if you can. > > Thank you, > > Michael James > Unidata > > > > > Hello, > > > > I seem to be having trouble with the NCEP grib2 data for the NAM 227. I am > > running GEMPAK 6.8.0 on CentOS 6.4. I have been using dcgrib2 for a couple > > months to decode RAP, NAM 218/221 and GFS grib2 files from NCEP without > > issue. However, I decoded a few NAM 227 files today and when attempting to > > build a few maps using GDPLOT2 I either get a map with incorrectly > > displayed data or a segmentation fault. I was just curious first off if > > there are any known issues with decoding the NAM 227? Any help is greatly > > appreciated. > > > > Charles Lubensky > > IT Specialist I > > CEMR, Price College of Business > > University of Oklahoma > > address@hidden > > (405) 325-1181 > > Adams Hall 4 L > > > > > > > > > Ticket Details > =================== > Ticket ID: VQK-601999 > Department: Support GEMPAK > Priority: Normal > Status: Open > > Ticket Details =================== Ticket ID: VQK-601999 Department: Support GEMPAK Priority: Urgent Status: Open