[Met_help] [rt.rap.ucar.edu #81452] History for CANCEL - unexpected MODE output (UNCLASSIFIED)

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

CLASSIFICATION: UNCLASSIFIED

I discovered the source of the problem I just reported a few minutes ago.
The output, which was seemingly generated despite the ERROR, had been
generated by a previous (successful) MODE run earlier the same day. I didn't
notice the difference in the timestamp until now.

Sorry for the confusion.

R/
John

-----Original Message-----
From: Raby, John W CIV USARMY RDECOM ARL (US) 
Sent: Thursday, August 03, 2017 8:56 AM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Subject: unexpected MODE output (UNCLASSIFIED)

CLASSIFICATION: UNCLASSIFIED

I ran MET V5.2 MODE over a series of fcsts and obs where I explicitly
specified the fcst/ob pairs to be used as input. I did this using a script
which simply executed multiple MODE commands each preceded by the setting of
environmental variables which specified the correct set of fcst/ob inputs to
be used in the config file. There was a mistake in one MODE command out of
97 total commands which resulted in the log file showing and ERROR which
flagged the fact that MODE was "unable to open input file" and it listed the
path to my config file. I discovered that the config file was mistakenly
named in the MODE run command in that one instance, so naturally MODE could
not find the config file. All the other 96 run commands in the script did
not have this mistake. I discovered that, despite the ERROR cited in the log
file, MODE output was successfully generated and appears to have used the
settings which I specified in the config file. How is this possible if MODE
had an ERROR?

I can provide all the necessary files by separate file transfer if you could
provide me with an email address (@ucar.edu) to receive the download link.

Thanks.

R/
John

Mr John W. Raby, Meteorologist
U.S. Army Research Laboratory
White Sands Missile Range, NM 88002
(575) 678-2004 DSN 258-2004
FAX (575) 678-1230 DSN 258-1230
Email: john.w.raby2.civ at mail.mil






CLASSIFICATION: UNCLASSIFIED


CLASSIFICATION: UNCLASSIFIED


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: CANCEL - unexpected MODE output (UNCLASSIFIED)
From: John Halley Gotway
Time: Thu Aug 03 10:38:01 2017

John,

Great, glad you got it straightened out.

John

On Thu, Aug 3, 2017 at 9:12 AM, Raby, John W USA CIV via RT <
met_help at ucar.edu> wrote:

>
> Thu Aug 03 09:12:31 2017: Request 81452 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>        Queue: met_help
>      Subject: CANCEL - unexpected MODE output (UNCLASSIFIED)
>        Owner: Nobody
>   Requestors: john.w.raby2.civ at mail.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81452 >
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> I discovered the source of the problem I just reported a few minutes
ago.
> The output, which was seemingly generated despite the ERROR, had
been
> generated by a previous (successful) MODE run earlier the same day.
I
> didn't
> notice the difference in the timestamp until now.
>
> Sorry for the confusion.
>
> R/
> John
>
> -----Original Message-----
> From: Raby, John W CIV USARMY RDECOM ARL (US)
> Sent: Thursday, August 03, 2017 8:56 AM
> To: 'met_help at ucar.edu' <met_help at ucar.edu>
> Subject: unexpected MODE output (UNCLASSIFIED)
>
> CLASSIFICATION: UNCLASSIFIED
>
> I ran MET V5.2 MODE over a series of fcsts and obs where I
explicitly
> specified the fcst/ob pairs to be used as input. I did this using a
script
> which simply executed multiple MODE commands each preceded by the
setting
> of
> environmental variables which specified the correct set of fcst/ob
inputs
> to
> be used in the config file. There was a mistake in one MODE command
out of
> 97 total commands which resulted in the log file showing and ERROR
which
> flagged the fact that MODE was "unable to open input file" and it
listed
> the
> path to my config file. I discovered that the config file was
mistakenly
> named in the MODE run command in that one instance, so naturally
MODE could
> not find the config file. All the other 96 run commands in the
script did
> not have this mistake. I discovered that, despite the ERROR cited in
the
> log
> file, MODE output was successfully generated and appears to have
used the
> settings which I specified in the config file. How is this possible
if MODE
> had an ERROR?
>
> I can provide all the necessary files by separate file transfer if
you
> could
> provide me with an email address (@ucar.edu) to receive the download
link.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.w.raby2.civ at mail.mil
>
>
>
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>

------------------------------------------------