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.
>From: Clint Rowe <address@hidden> >Organization: UCAR/Unidata >Keywords: 200303042252.h24Mqd316047 >Chiz > >1) is it possible to "personalize" the gempak gui programs (esp. nmap/nmap2) > so that a user can have his/her own set of restore scripts? That is, can > a user have their own mod_res.tbl pointing to their own restores? > >Clint > >==================================================================== >Clinton M. Rowe >Associate Professor >Meteorology/Climatology Program phone:(402)472-1946 >Department of Geosciences fax:(402)472-4917 >University of Nebraska-Lincoln address@hidden > > Clint, Yes, the order in which the program searches for most tables (including mod_res.tbl) is: * 1. filename (local) * * 2. path/filename (table as given) * * 3. $NCDESK/type/filename * * 4. $NCSITE/type/filename * * 5. $GEMTBL/type/filename (above, path/filename is mod_res.tbl, and type is nmap for the grid pulldown) ) So, the mod_res.tbl file in the local directory will always take precedence. The least precedence will be given to $GEMTBL/nmap/mod_res.tbl. You can also use the $NCDESK and $NCSITE environmental variables for certain application specific (eg case study, class project) tables. The mod_res.tbl typically references the files under $NMAP_RESTORE, which can also be changed by the environmental variable...or users can use their own variables, or hardcoded paths in their local mod_res.tbl file. Steve Chiswell