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.
Eric, The log message: >[6405] 030806/0906 [DCGRIB -51] can't open grib tables [NA -51], set >GEMTBL Means that you don't have $GEMTBL defined in the LDM environment, and have not defined it using the -e GEMTBL=path option to the dcgrib2 decoder. Or, you have a typo in your GEMTBL path for that invocation. The decoder needs that environmental variable to find its tables. Steve Chiswell >From: Eric Nelson <address@hidden> >Organization: UCAR/Unidata >Keywords: 200308061829.h76IT3Ld023320 > >Steve, > >We are ingesting the Eta 212, 215, and 104, as well as the RUC 236 and 252 >via conduit and sending it thru dcgrib2. I checked all the files from the >12z runs and they all are below the max grid #. > >I looked at the dcgrib_conduit.log and the only thing that caught my eye >was the following. > >[6405] 030806/0906 [DCGRIB -51] can't open grib tables [NA -51], set >GEMTBL > >These have a fairly common occurence while model data is arriving. Common >enough that it seems to be connected with RUC arrival. > >I have not noticed any problems with the files themselves. > >-Eric > > >On Wed, 6 Aug 2003, Unidata Support wrote: > >> >> Eric, >> >> This probably means that the file is full. I have been making updates to the >> $GEMTBL/grid/gribkey.tbl file for mamimum number of grids in a file. >> >> If you use gdinfo, you will see how many grids and the >> limit for the file. >> >> Here are the ETA sizes I am currently using (are you still just using the >> ETA from CONDUIT?) >> >> center sub modelid grid Output grid file name max_grids >> ! >> ! ETA >> 007 x 084,085 212 data/gempak/model/YYYYMMDDHH_eta@@@.gem 18000 >> 007 x 084,085 216 data/gempak/model/YYYYMMDDHH_eta@@@.gem 18000 >> 007 x 084,085 104 data/gempak/model/YYYYMMDDHH_eta@@@.gem 18000 >> 007 x 084,085 @@@ data/gempak/model/YYYYMMDDHH_eta@@@.gem 5000 >> ! >> >> If its more frequent than 4x per day, then it would sound more like RUC: >> ! >> ! RUC >> 007 x 105 @@@ data/gempak/model/YYYYMMDDHH_ruc@@@.gem 15000 >> 007 x 086 @@@ data/gempak/model/YYYYMMDDHH_ruc@@@.gem 2000 >> >> >> Steve Chiswell >> >> >From: Eric Nelson <address@hidden> >> >Organization: UCAR/Unidata >> >Keywords: 200308052023.h75KNuLd026061 >> >> > >> >While switching my CONDUIT source, I noticed the following in my >> >ldmd.log file... >> > >> >Aug 05 20:18:05 climate pqact[22916]: pbuf_flush (11) write: Broken pipe >> >Aug 05 20:18:05 climate pqact[22916]: pbuf_flush (11) write: Broken pipe >> >Aug 05 20:18:05 climate >> >pqact[22916]: pipe_dbufput: decoders/gempak/dcgrib2-ddata/gempak/logs/dcgri > b_c >> > onduit.log-eGEMTBL=/home/gempak/gempak-5.6.j/gempak/tables >> >write error >> > >> >Is there something I need to do about this or is it harmless? A cursory >> >look reveals that this error message is fairly common in our logs. >> > >> >-Eric >> > >> >-- >> >________________________________________________________________________ >> >Eric Nelson | >> > | >> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | >> >+ College of Dupage Meteorology Dept. + Research Applications Prog. + | >> >+ Weather Data Manager + UCAR/NCAR + | >> >+ http://weather.cod.edu + http://www.rap.ucar.edu + | >> >+ address@hidden + address@hidden + | >> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | >> > | >> >"I love deadlines. I especially like the whooshing sound they make as | >> >they go flying by." --Douglas Adams | >> >________________________________________________________________________ >> > >> >> **************************************************************************** >> Unidata User Support UCAR Unidata Program >> (303)497-8643 P.O. Box 3000 >> address@hidden Boulder, CO 80307 >> ---------------------------------------------------------------------------- >> Unidata WWW Service http://my.unidata.ucar.edu/content/support >> **************************************************************************** >> > >