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.
Ahhhhhhhh....... Here you show: -g /npfos/noaaport/nawips/gempak/tables In your ldm pqact.conf action below, you had: -g /npfos/noaaport/nawips/gempak/tables/grid Your pqact.conf GEMTBL location should be the level up. Steve Chiswell Unidata User SUpport >From: "Glenn Rutledge" <address@hidden> >Organization: UCAR/Unidata >Keywords: 200106281731.f5SHVl107097 >I ran- >npfos:/npfos/noaaport/ldm->cat GRID_YORI92_KWBE_20010628_1200 | dcgrib -d >/npfos/noaaport/nawipsdata/logs/%Y%m%d_dcgrib.log -g >/npfos/noaaport/nawips/gempak/tables PACK >/npfos/noaaport/nawipsdata/hds/YYYYMMDDHH_eta@@@.gem >and it replies- > Changing center table to cntrgrib1.tbl > Changing vertical coord table to vcrdgrib1.tbl > Changing WMO parameter table to wmogrib2.tbl > Changing center parameter table to ncepgrib2.tbl >npfos:/npfos/noaaport/ldm-> > >It created an eta file (franly I did not determine if this was an eta grid or > not- >how is this done with gdinfo? i.e., the command??). > >The grid shows up under GARP (unlike the auto ones- they crash the system). S > Ince >I don't know the gdinfo command off hand, I can't quicly plot it up). It look > s >like it works however. What's next? Glenn > > > >Unidata Support wrote: > >> Glenn, >> >> Have you tried running the grib decoder from the command line as >> the LDM user with a sample data set like: >> >> cat gribfile | dcgrib -d - ....etc.... >> >> Steve Chiswell >> Unidata User Support >> >> >From: "Glenn Rutledge" <address@hidden> >> >Organization: UCAR/Unidata >> >Keywords: 200106281527.f5SFRS101355 >> >> >Steve- >> >I doubled checked the umask (2) . It looks like permissions are OK. and th > e g >> > rid >> >tables are in the propoer location. I'm at a loss as to why the GEMTBL can > 't >> > be >> >located by the grib decoders. >> > >> >Unidata Support wrote: >> > >> >> Glenn, >> >> >> >> The dcgrib errors in the logs is likely the problem with the grid files >> >> being used by the GUIs. It says that the decoder can't find the >> >> $GEMTBL/grid/ directory for the tables. The reasons could be that >> >> the ldm process does not have permission to look in the >> >> /npfos/noaaport/nawips/gempak/tables/grid directory. >> >> >> >> Or, the /npfos/noaaport/nawips/gempak/tables/grid is not the >> >> correct $GEMTBL/grid location on your system. >> >> >> >> Check as the LDM user to make sure you do have permission to look >> >> in that directory. It is possible that your user setup or umask >> >> does not allow that. >> >> >> >> I'm assuming if you try to use gdinfo on any of your grid files, you >> >> won't find any data in the files. >> >> >> >> Steve Chiswell >> >> Unidata User SUpport >> >> >> >> >From: "Glenn Rutledge" <address@hidden> >> >> >Organization: UCAR/Unidata >> >> >Keywords: 200106261330.f5QDUh116711 >> >> >> >> >Hi Steve- >> >> >1) Yes, In yesterday's file I deleted all but one day's worth of grids. >> >> >2) Yes, I cannot display any models. btw- in nmap2, I can select files > (se >> > e >> >> >times), but when I select a time, nothing is selected). >> >> > >> >> >I changed the default widget to eta212. Now, the popup displays nothing > be >> > for >> >> > e >> >> >crashing- with a core dump. I looked into the decoder logs (dcgrib) and > se >> > e: >> >> >npfos:/npfos/noaaport/nawipsdata/logs->tail 20010626_dcgrib.log >> >> >Jun 26 13:16:47 dcgrib[20518]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:47 dcgrib[20519]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:48 dcgrib[20520]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:49 dcgrib[20521]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:49 dcgrib[20522]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:49 dcgrib[20523]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:50 dcgrib[20524]: can't open grib tables, set GEMTBL -19 >> >> >Jun 26 13:16:50 dcgrib[20525]: can't... >> >> > >> >> >Is this a persmissions pblm? >> >> > >> >> >Also, here's my pqact log errors: >> >> >npfos:/npraid/noaaport/ldm/logs->tail nawips_pqact.log >> >> >Jun 26 13:22:03 pqact[11548]: child 20759 exited with status 2 >> >> >Jun 26 13:22:03 pqact[11548]: pbuf_flush (3) write: Broken pipe >> >> >Jun 26 13:22:03 pqact[11548]: pipe_dbufput: >> >> >/npfos/noaaport/nawips/bin/sol/dcgrib-d/npfos/noaaport/nawipsdata/logs/2 > 001 >> > 062 >> >> > 6_dcgrib.log-g/npfos/noaaport/nawips/gempak/tables/gridPACK/npfos/noaap > ort >> > /na >> >> > wipsdata/hds/YYYYMMDDHH_ruc@@@.gem >> >> >write error >> >> >Jun 26 13:22:03 pqact[11548]: pipe_prodput: trying again >> >> >Jun 26 13:22:03 pqact[11548]: child 20760 exited with status 2 >> >> >Jun 26 13:22:03 pqact[11548]: pbuf_flush (3) write: Broken pipe >> >> >Jun 26 13:22:03 pqact[11548]: pipe_dbufput: >> >> >/npfos/noaaport/nawips/bin/sol/dcgrib-d/npfos/noaaport/nawipsdata/logs/2 > 001 >> > 062 >> >> > 6_dcgrib.log-g/npfos/noaaport/nawips/gempak/tables/gridPACK/npfos/noaap > ort >> > /na >> >> > wipsdata/hds/YYYYMMDDHH_ruc@@@.gem >> >> >write error >> >> >Jun 26 13:22:03 pqact[11548]: pipe_prodput: trying again >> >> >Jun 26 13:22:03 pqact[11548]: child 20761 exite.. >> >> > >> >> >I'll set some logging for garp and get back to you, Thanks, Glenn >> >> > >> >> > >> >> >Unidata Support wrote: >> >> > >> >> >> Glenn, >> >> >> >> >> >> Off hand, I don't see anything that would be the problem. >> >> >> How many AVN213 files are in the /npfos/noaaport/nawipsdata/hds/ >> >> >> directory? Your ls only shows 1 day, but the messages are >> >> >> from further back...though I don't know if that was just >> >> >> because you sent the message yesterday, and I answered >> >> >> you back today. >> >> >> >> >> >> I'm assuming you can't get any model grids to display. >> >> >> Do the "too many files open" messages start when you initially >> >> >> pop up the model window? >> >> >> >> >> >> Since you don't have an eta211, you might need to check the >> >> >> default "model" value, which would be a problem initially >> >> >> when poping up the window: >> >> >> >> >> >> # >> >> >> # Widget defaults >> >> >> # >> >> >> # Choose default values for the model, vertical coordinate, levels, >> >> >> # function, default fdf chapters, cross-section line, time-height >> >> >> # station, vertical profile axis types, radar ring station, upper >> >> >> # air levels and upper air filter. >> >> >> # >> >> >> model : eta211 >> >> >> >> >> >> After that, I would suggest using the "option" pulldown for logging >> >> >> to verbosely log all the information about what files are being opened > . >> >> >> >> >> >> Steve CHiswell >> >> >> >> >> >> >From: "Glenn Rutledge" <address@hidden> >> >> >> >Organization: UCAR/Unidata >> >> >> >Keywords: 200106251742.f5PHg8102532 >> >> >> >> >> >> >Thanks Steve, >> >> >> >Yes, that was the first thing I looked at. Here's the list of models > I' >> > m >> >> >> >selecting: >> >> >> >2001062500_avn201.gem 2001062500_thin.gem 2001062512_eta215.gem >> >> >> >2001062500_avn202.gem 2001062506_avn201.gem 2001062512_ngm213.gem >> >> >> >2001062500_avn213.gem 2001062506_avn202.gem 2001062512_ruc211.gem >> >> >> >2001062500_mrf.gem 2001062506_avn213.gem 2001062514_ruc211.gem >> >> >> >2001062500_mrf202.gem 2001062512_avn202.gem 2001062515_ruc211.gem >> >> >> >2001062500_ngm213.gem 2001062512_avn213.gem 2001062516_ruc211.gem >> >> >> >2001062500_spec.gem 2001062512_eta212.gem 2001062517_ruc211.gem >> >> >> > >> >> >> >Here's my modelkeys and labels: >> >> >> >modelkeys : "avn202,avn213,eta212,eta215,mrf202,ngm213,ruc211" >> >> >> >modellabels : "AVN202,AVN213,Eta,mesoEta,MRF,NGM,RUC" >> >> >> > >> >> >> >It looks right to me... >> >> >> > >> >> >> >Glenn >> >> >> > >> >> >> >Unidata Support wrote: >> >> >> > >> >> >> >> Glenn, >> >> >> >> >> >> >> >> Make sure your model keys in $GARPHOME/config/Garp_defaults >> >> >> >> are correct and unique. Eg, make sure the key is "avn213" and >> >> >> >> not just "avn" if you have other avn201, avn202, etc grids that >> >> >> >> the key would match. That might be the cause of "too many" >> >> >> >> files being opened. >> >> >> >> >> >> >> >> Steve Chiswell >> >> >> >> Unidata User Support >> >> >> >> >> >> >> >> >From: "Glenn Rutledge" <address@hidden> >> >> >> >> >Organization: UCAR/Unidata >> >> >> >> >Keywords: 200106251312.f5PDC5120758 >> >> >> >> >> >> >> >> >Hello Steve, >> >> >> >> >Getting nawips (garp) back up. I have two pblms at the moment: >> >> >> >> >1) some err msg about Whoa!!! and the other >> >> >> >> >2) can't get at my grids. Here's the errors. Any thoughts? Thx, > Gl >> > enn >> >> >> >> > >> >> >> >> >npfos:/npraid/noaaport/nawipsdata/hds->ntl >> >> >> >> >Resource File: /npfos/noaaport/nawips/resource/Ntop >> >> >> >> >graphic, satellite, radar -- 33 95 20 >> >> >> >> > Invoke ... /npfos/noaaport/nawips/bin/sol/garp >> >> >> >> >G A R P - v2.1 starting... >> >> >> >> >!!!!!Whoa!!!!!! Free() got a 0x0 >> >> >> >> >GEMPAK: [DM -3] Too many files open. >> >> >> >> >GEMPAK: [GD -2] File >> >> >> >> >/npfos/noaaport/nawipsdata/hds/2001062318_avn213.gem cannot be ope > ned >> > . >> >> >> >> >GEMPAK: [DM -3] Too many files open. >> >> >> >> >GEMPAK: [GD -2] File >> >> >> >> >/npfos/noaaport/nawipsdata/hds/2001062400_avn213.gem cannot be ope > ned >> > . >> >> >> >> >GEMPAK: [DM -3] Too many files open. >> >> >> >> >GEMPAK: [GD -2] File >> >> >> >> >/npfos/noaaport/nawipsdata/hds/2001062406_avn213.gem cannot be ope > ned >> > . >> >> >> >> >GEMPAK: [DM -3] Too many files open. >> >> >> >> >GEMPAK: [GD -2] File >> >> >> >> >/npfos/noaaport/nawipsdata/hds/2001062412_avn213.gem cannot be ope > ned >> > . >> >> >> >> >GEMPAK: [DM -3] Too many files open. >> >> >> >> >GEMPAK: [GD -2] File >> >> >> >> >/npfos/noaaport/nawipsdata/hds/2001062418_avn213.gem cannot be ope > ned >> > . >> >> >> >> >GEMPAK: [DM -3] Too many files open. >> >> >> >> >GEMPAK: [GD -2] File >> >> >> >> >/npfos/noaaport/nawipsdata/hds/2001062500_avn213.gem cannot be ope > ned >> > . >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> ******************************************************************* > *** >> > *** >> >> > *** >> >> >> >> Unidata User Support UCAR Unidat > a P >> > rog >> >> > ram >> >> >> >> (303)497-8644 P.O. > Bo >> > x 3 >> >> > 000 >> >> >> >> address@hidden Boulder, > CO >> > 80 >> >> > 307 >> >> >> >> ------------------------------------------------------------------- > --- >> > --- >> >> > --- >> >> >> >> Unidata WWW Service http://www.unidata.ucar.e > du >> > / >> >> >> >> ******************************************************************* > *** >> > *** >> >> > *** >> >> >> > >> >> >> >> >> >> ********************************************************************** > *** >> > *** >> >> >> Unidata User Support UCAR Unidata P > rog >> > ram >> >> >> (303)497-8644 P.O. Bo > x 3 >> > 000 >> >> >> address@hidden Boulder, CO > 80 >> > 307 >> >> >> ---------------------------------------------------------------------- > --- >> > --- >> >> >> Unidata WWW Service http://www.unidata.ucar.edu/ >> >> >> ********************************************************************** > *** >> > *** >> >> > >> >> >> >> ************************************************************************* > *** >> >> Unidata User Support UCAR Unidata Prog > ram >> >> (303)497-8644 P.O. Box 3 > 000 >> >> address@hidden Boulder, CO 80 > 307 >> >> ------------------------------------------------------------------------- > --- >> >> Unidata WWW Service http://www.unidata.ucar.edu/ >> >> ************************************************************************* > *** >> > >> >> **************************************************************************** >> Unidata User Support UCAR Unidata Program >> (303)497-8644 P.O. Box 3000 >> address@hidden Boulder, CO 80307 >> ---------------------------------------------------------------------------- >> Unidata WWW Service http://www.unidata.ucar.edu/ >> **************************************************************************** >