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, 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