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.
Wenxian, When a GEMPAK program starts, it lists out the previous settings in gemglb.nts (eg what you had previously used), then your redirection from "<< EOD" will occur, so you won't see those settings unless you use the "display" command such as: gdinfo << EOD GDFILE = $MODEL/${model_lc}/${model_lc}_${ymdh} TEXT = 1.5/2//hw display run exit EOD The "display" command will sow the current settings after the parameters have been set you the redirection, but it is not necessary for the program to be run with the values that were set- though your script snippet never runs the prigram velow. Steve Chiswell Unidata User Support >From: Lu <address@hidden> >Organization: UCAR/Unidata >Keywords: 200502071726.j17HQ5v2028654 > >Dear Steve, > >I wonder if the script ezset is accurate. The block > >gdinfo << EOD > GDFILE = $MODEL/${model_lc}/${model_lc}_${ymdh} > TEXT = 1.5/2//hw > exit >EOD > >on the terminal always displays the GDFILE name previously entered >although it correctly sets the currently defined GDFILE for all future >gempak programs eventually. This is a little bit confused. Maybe I >am wrong. > >Regards, > >Wenxian > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly 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.