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.
Adam, Sounds like your GEMTBL environmental variable is not set. The pqact entres for dcgrib2 can be generated from $NAWIPS/ldm/etc/gen_pqact.csh (as described at the top of http://my.unidata.ucar.edu/content/software/gempak/GEMPAK5.7/configuration.html) The gen_pqact.csh will use your GEMTBL environmental variable setting for creating the pqact.conf entries. Your GEMTBL variable is set by sourcing $NAWIPS/Gemenviron. The dcgrib2 entries use the -e GEMTBL=location setting for the decoder to find the necessary tables to decoder grib. If this is not set, and not in the environment of the LDM account that started the pqact process, you will not get the proper tables. Steve Chiswell Unidata User Support >From: address@hidden >Organization: UCAR/Unidata >Keywords: 200405061848.i46ImJtK016553 >I have upgraded gempak to the newest version about a week ago 5.7. Since then > >I have been getting alot of core files in the LDM directory. greping through >the logs has shown them all to be from the dcgrib2 decoder. My dcgrib logs >shows everything from "no file template", "Grid to large", "table grib3.tbl >cannot be opened", "bulletin to long", and "Grid navigation 255 incompatible >with file ....." > >HELP!!!! > >-- >Adam Taylor >Computing Center >University of Louisiana at Monroe > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publically 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.