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.
David, All the GEMPAK programs and GUIS (NMAP/NMAP2) use the $GEMTBL/config/datatype.tbl file (see the template file description in the tutorial). The datatype.tbl file entries use the $MODEL environmental variable. Historically, Garp uses its own template scheme, and the $HDS environmental variable is used in the Garp_defaults.tbl. Typically, the Gemenviron file I send out sets: setenv HDS $GEMDATA/hds setenv MODEL $GEMDATA/model for realtime data, I assume $GEMDATA/hds is a link to $GEMDATA/model (or vice versa). Or they could both point to $GEMDATA/hds. Basically, you can set $MODEL to the same thing as $HDS...but Garp expects all the files in the directory to conform to its idea of a file name template (Garp developed at COMET), and all the grid data is in the same directory. The rest of GEMPAK allows you to set GDFILE to any template which is looked up in $GEMTBL/config/datatype.tbl. Theoretically, this could be different directories for every model, and different template schemes for every model (for example, some models could have each forecast hour in its own file using the FFF template). So, I kept the environmental variables distinct in case the user wanted to use that feature. Eg, I wanted to guaranteee Garp that all grid files would be in the $HDS directory, but $MODEL could be used to point to a tree of directories with a common root. In NMAP, when you click on "grid" for data type, it searches the $GEMTBL/nmap/mod_res.tbl file for all grid file aliases and presents these as the choices for data sets. Once you have picked one, such as eta104, it looks that alias up in the $GEMTBL/config/datatype.tbl file for the template which is used for the GDFILE parameter. By default GDFILE=eta104 would return the latest eta104 file. Using GDFILE=eta104|021104/0000 for example would use that specific run. Steve Chiswell >From: David Ovens <address@hidden> >Organization: UCAR/Unidata >Keywords: 200211042112.gA4LC3X23961 >Help, please. I've just spent 20 minutes trying to figure out how to >point NMAP/NMAP2 to my additional model data with absolutely no >success. There are data sets working, but I've got lots more in $HDS >that don't show up at all, plus I've got ETA 104 and 1-degree AVN >grids that I want to display. > >I know how to do this in GARP, it's quite easy, but I've >found nothing in the online or printed documentation to tell me what >to do. Somewhere I must need to associate filename extensions with >entries for the "Data Source: GRID" widget, but where? I've found >$GEMNTS/nmap/restore/ but have found no GDFILE types of entries.... > >Floundering in Seattle, > >David >-- > >David Ovens e-mail: address@hidden >(206) 685-8108 plan: Real-time MM5 forecasting for Pacific Northwest >Research Meteorologist >Dept of Atmospheric Sciences, Box 351640 >University of Washington >Seattle, WA 98195 >