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.
Frank, Please provide the testruc.log output of: cat gribfile | dcgrib2 -v 2 -d testruc.log YYYYMMDDHH_ruc@@@.gem as well as the listing from gdinfo for the resulting grid file. Are you able to plot the grid file with gdplot2/gdcntr? Steve Chiswell >From: Frank Colby <address@hidden> >Organization: UMass Lowell >Keywords: 200512062226.jB6MQ97s009032 >This is a multi-part message in MIME format. >--------------000104030703060902070501 >Content-Type: text/plain; charset=ISO-8859-1; format=flowed >Content-Transfer-Encoding: 7bit > >Dear Unidata Support, > >I have used dcgrib2 to convert RUC grib files downloaded from the NOMADS >server into gempak format, and the decoding process seemed to work >fine. The log file shows bulletins being processed, and normal >termination. When I move the gempak file into the $HDS directory and try >to select RUC2 as the model, GARP crashes with a segmentation fault. I >have tried just decoding a single time with the same result. I suspect >is it something small but significant, since I have no trouble with >other model files. > >thanks, >Frank > >--------------000104030703060902070501 >Content-Type: text/x-vcard; charset=utf-8; > name="Frank_Colby.vcf" >Content-Transfer-Encoding: 7bit >Content-Disposition: attachment; > filename="Frank_Colby.vcf" > >begin:vcard >fn:Frank Colby >n:Colby;Frank >org:University of Massachusetts Lowell;Environmental, Earth & Atmospheric Scie > nces >email;internet:address@hidden >title:Professor of Meteorology >tel;work:(978) 934-3906 >version:2.1 >end:vcard > > >--------------000104030703060902070501-- > -- 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.