[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051102: uppercase gpnids output filenames?

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.

  • Subject: 20051102: uppercase gpnids output filenames?
  • Date: Wed, 02 Nov 2005 16:46:05 -0700
Neil,

The output file name is processed by the GEMLIB routine
$GEMPAK/source/gemlib/in/inoutt.f, so the behavior is
common to all GEMPAK programs.

The problem is that you have mixed uppercase in your file name,
so the porocessing of the filename is converted to uppercase
(I'm assuming an old VMS type of convention).

Try specifying an output file name all in lower case.

Steve Chiswell
Unidata User Support


>From: "Neil R. Smith" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200511022319.jA2NJt7s029253

>Steve,
>I've got gpnids (gempak 5.8.3a) scripted to generate VAD winds output. I
>find that whatever filename I set 'OUTPUT' to, the characters are
>converted to uppercase.
>
>eg. if during gpnids execution,
>
>OUTPUT=f / /data/vad/out.FileName
>
>then gpnids will try to write to 
>    /DATA/VAD/OUT.FILENAME
>But since these uppercase directories don't exist, the output defaults
>to terminal.
>
>This is a problem if I can't include full path naming with lower case
>directory names.
>
>Is there something I'm missing about gempak program output, or gpnids
>output in particular?
>
--
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.