[Met_help] [rt.rap.ucar.edu #42058] History for RE: Stat-Analysis Warning Message (UNCLASSIFIED)

Tue Nov 16 09:52:26 MST 2010

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

Classification: UNCLASSIFIED
Caveats: NONE

I performed a follow-up experiment to test the occurrence of the warning
reported on 27 OCT in the email below.

On 28 OCT 10, My system administrator changed the version of MET we use from
MET V3.0 back to MET V2.0 (specifically "v20p2" with patches).

I confirmed from my account that I was using MET V2.0.

I deleted the 0-sized Stat-Analysis files reported below from my directory.

On 28 OCT, I reran Stat-Analysis for the same case reported below and using
the same Point-Stat .stat files as before and found that the Stat-Analysis
files were not 0-sized and contained normal looking results.

I checked the log file after the run completed and found no warnings or
errors.

I've attached the log file showing the warnings I got BEFORE the switch back
to MET V2.0 and the log file generated AFTER the switch from the rerun which
started on 28 OCT.

The log file names were changed to show "before" and "after" so you know
which log file is which.

All I can conclude now is that this warning seems to be associated with our
implementation of MET V3.0

Any suggestions for troubleshooting?

Thanks.

R/
John

-----Original Message-----
From: Raby, John (Civ, ARL/CISD) 
Sent: Wednesday, October 27, 2010 2:44 PM
To: 'met_help at ucar.edu'
Subject: Stat-Analysis Warning Message (UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

I have been running Stat-Analysis on Point-Stat results we generated this
past summer. This proceeded well until I started noticing that the output
.txt files on the last couple of runs were 0-sized files which is
unexpected. 

I have attached examples of Stat-Analysis log files which show the dialog
before and after. The after file shows a warning about "no matching stat
lines" after having read in and retained 1565906 stat lines.

I checked sample stat lines (.stat files) before and after and note no
obvious differences or problems.

The only change which I'm aware of which occurred between the two cases was
that our new MET V3.0 was compiled on OCT 7. 

The processing of the "before" case which occurred on SEP 13 and the
processing for the "after" case on OCT 21.

Can you assist me in troubleshooting this?

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.raby at us.army.mil

Please begin using the email address within this signature block for all
future correspondence.  The current @arl.army.mil address will be
decommissioned in upcoming months.

"When you can measure what you are speaking about and express it in numbers,
you know something about it, but when you cannot measure it, when you cannot
express it in number, your knowledge is of a meagre and unsatisfactory
kind". - Lord Kelvin

Classification: UNCLASSIFIED
Caveats: NONE

Classification: UNCLASSIFIED
Caveats: NONE

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

Subject: Re: [rt.rap.ucar.edu #42058] RE: Stat-Analysis Warning Message (UNCLASSIFIED)
From: John Halley Gotway
Time: Thu Nov 11 15:20:08 2010

John,

I gave it some thought, and unfortunately, I don't have any useful
suggestions for you.  I suspect that there's some minor technical
issue causing you to get zero matching lines when using the METv3.0
version of STAT-Analysis.

You already sent me some of this data in the past, and when I ran it
through METv2.0 STAT-Analysis and METv3.0 STAT-Analysis, I did get
matching lines for both.  So there's nothing else I can really
do with the data you've already sent me.

I wonder if you'd be able to put together a concise test case that
illustrates the problem you're having.  Basically, copy over a handful
of your .stat files from the "results_m1o1_P2" or
"results_m1o1_T3" directory.  Then run a single STAT-Analysis job on
that subset of data using METv2.0 and METv3.0 STAT-Analysis which give
you matches for METv2.0 but no matches for METv3.0.  Then
send me your data and the *exact* STAT-Analysis command line jobs you
ran.  If you can make a very concise test case, I might be able to
reproduce your problem here and figure out where the issue lies.

John

On 11/10/2010 11:41 AM, RAL HelpDesk {for Raby, John} wrote:
>
> Wed Nov 10 11:41:39 2010: Request 42058 was acted upon.
> Transaction: Ticket created by john.raby at us.army.mil
>        Queue: met_help
>      Subject: RE: Stat-Analysis Warning Message (UNCLASSIFIED)
>        Owner: Nobody
>   Requestors: john.raby at us.army.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42058 >
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I performed a follow-up experiment to test the occurrence of the
warning
> reported on 27 OCT in the email below.
>
> On 28 OCT 10, My system administrator changed the version of MET we
use from
> MET V3.0 back to MET V2.0 (specifically "v20p2" with patches).
>
> I confirmed from my account that I was using MET V2.0.
>
> I deleted the 0-sized Stat-Analysis files reported below from my
directory.
>
> On 28 OCT, I reran Stat-Analysis for the same case reported below
and using
> the same Point-Stat .stat files as before and found that the Stat-
Analysis
> files were not 0-sized and contained normal looking results.
>
> I checked the log file after the run completed and found no warnings
or
> errors.
>
> I've attached the log file showing the warnings I got BEFORE the
switch back
> to MET V2.0 and the log file generated AFTER the switch from the
rerun which
> started on 28 OCT.
>
> The log file names were changed to show "before" and "after" so you
know
> which log file is which.
>
> All I can conclude now is that this warning seems to be associated
with our
> implementation of MET V3.0
>
> Any suggestions for troubleshooting?
>
> Thanks.
>
> R/
> John
>
>
> -----Original Message-----
> From: Raby, John (Civ, ARL/CISD)
> Sent: Wednesday, October 27, 2010 2:44 PM
> To: 'met_help at ucar.edu'
> Subject: Stat-Analysis Warning Message (UNCLASSIFIED)
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I have been running Stat-Analysis on Point-Stat results we generated
this
> past summer. This proceeded well until I started noticing that the
output
> .txt files on the last couple of runs were 0-sized files which is
> unexpected.
>
> I have attached examples of Stat-Analysis log files which show the
dialog
> before and after. The after file shows a warning about "no matching
stat
> lines" after having read in and retained 1565906 stat lines.
>
> I checked sample stat lines (.stat files) before and after and note
no
> obvious differences or problems.
>
> The only change which I'm aware of which occurred between the two
cases was
> that our new MET V3.0 was compiled on OCT 7.
>
> The processing of the "before" case which occurred on SEP 13 and the
> processing for the "after" case on OCT 21.
>
> Can you assist me in troubleshooting this?
>
> 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.raby at us.army.mil
>
> Please begin using the email address within this signature block for
all
> future correspondence.  The current @arl.army.mil address will be
> decommissioned in upcoming months.
>
> "When you can measure what you are speaking about and express it in
numbers,
> you know something about it, but when you cannot measure it, when
you cannot
> express it in number, your knowledge is of a meagre and
unsatisfactory
> kind". - Lord Kelvin
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>

------------------------------------------------
Subject: RE: Stat-Analysis Warning Message (UNCLASSIFIED)
From: Raby, John
Time: Tue Nov 16 07:08:46 2010

Classification: UNCLASSIFIED
Caveats: NONE

John -

Thanks for your offer to help troubleshoot. For the purpose of
completing the
generation of results from our UTAH WRF case studies, we plan to
continue
using MET V2.0. We were in the midst of this processing when we
compiled and
tried to use MET V3.0. We decided that it would be better to continue
with MET
V2.0 from the stand point of consistency of statistical results for
this
particular project.

After we complete this project, we will revisit this and get back with
you on
providing further test case data.

R/
John

-----Original Message-----
From: RAL HelpDesk {for John Halley Gotway} [mailto:met_help at ucar.edu]
Sent: Thursday, November 11, 2010 3:20 PM
To: Raby, John (Civ, ARL/CISD)
Cc: Brown, Bob (Civ, ARL/CISD); Flanigan, Robert (Civ, ARL/CISD)
Subject: Re: [rt.rap.ucar.edu #42058] RE: Stat-Analysis Warning
Message
(UNCLASSIFIED)

John,

I gave it some thought, and unfortunately, I don't have any useful
suggestions
for you.  I suspect that there's some minor technical issue causing
you to get
zero matching lines when using the METv3.0
version of STAT-Analysis.

You already sent me some of this data in the past, and when I ran it
through
METv2.0 STAT-Analysis and METv3.0 STAT-Analysis, I did get matching
lines for
both.  So there's nothing else I can really
do with the data you've already sent me.

I wonder if you'd be able to put together a concise test case that
illustrates
the problem you're having.  Basically, copy over a handful of your
.stat files
from the "results_m1o1_P2" or
"results_m1o1_T3" directory.  Then run a single STAT-Analysis job on
that
subset of data using METv2.0 and METv3.0 STAT-Analysis which give you
matches
for METv2.0 but no matches for METv3.0.  Then
send me your data and the *exact* STAT-Analysis command line jobs you
ran.  If
you can make a very concise test case, I might be able to reproduce
your
problem here and figure out where the issue lies.

John

On 11/10/2010 11:41 AM, RAL HelpDesk {for Raby, John} wrote:
>
> Wed Nov 10 11:41:39 2010: Request 42058 was acted upon.
> Transaction: Ticket created by john.raby at us.army.mil
>        Queue: met_help
>      Subject: RE: Stat-Analysis Warning Message (UNCLASSIFIED)
>        Owner: Nobody
>   Requestors: john.raby at us.army.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=42058 >
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I performed a follow-up experiment to test the occurrence of the
warning
> reported on 27 OCT in the email below.
>
> On 28 OCT 10, My system administrator changed the version of MET we
use from
> MET V3.0 back to MET V2.0 (specifically "v20p2" with patches).
>
> I confirmed from my account that I was using MET V2.0.
>
> I deleted the 0-sized Stat-Analysis files reported below from my
directory.
>
> On 28 OCT, I reran Stat-Analysis for the same case reported below
and using
> the same Point-Stat .stat files as before and found that the Stat-
Analysis
> files were not 0-sized and contained normal looking results.
>
> I checked the log file after the run completed and found no warnings
or
> errors.
>
> I've attached the log file showing the warnings I got BEFORE the
switch back
> to MET V2.0 and the log file generated AFTER the switch from the
rerun which
> started on 28 OCT.
>
> The log file names were changed to show "before" and "after" so you
know
> which log file is which.
>
> All I can conclude now is that this warning seems to be associated
with our
> implementation of MET V3.0
>
> Any suggestions for troubleshooting?
>
> Thanks.
>
> R/
> John
>
>
> -----Original Message-----
> From: Raby, John (Civ, ARL/CISD)
> Sent: Wednesday, October 27, 2010 2:44 PM
> To: 'met_help at ucar.edu'
> Subject: Stat-Analysis Warning Message (UNCLASSIFIED)
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I have been running Stat-Analysis on Point-Stat results we generated
this
> past summer. This proceeded well until I started noticing that the
output
> .txt files on the last couple of runs were 0-sized files which is
> unexpected.
>
> I have attached examples of Stat-Analysis log files which show the
dialog
> before and after. The after file shows a warning about "no matching
stat
> lines" after having read in and retained 1565906 stat lines.
>
> I checked sample stat lines (.stat files) before and after and note
no
> obvious differences or problems.
>
> The only change which I'm aware of which occurred between the two
cases was
> that our new MET V3.0 was compiled on OCT 7.
>
> The processing of the "before" case which occurred on SEP 13 and the
> processing for the "after" case on OCT 21.
>
> Can you assist me in troubleshooting this?
>
> 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.raby at us.army.mil
>
> Please begin using the email address within this signature block for
all
> future correspondence.  The current @arl.army.mil address will be
> decommissioned in upcoming months.
>
> "When you can measure what you are speaking about and express it in
numbers,
> you know something about it, but when you cannot measure it, when
you cannot
> express it in number, your knowledge is of a meagre and
unsatisfactory
> kind". - Lord Kelvin
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>

Classification: UNCLASSIFIED
Caveats: NONE

------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #42058] RE: Stat-Analysis Warning Message (UNCLASSIFIED)
From: John Halley Gotway
Time: Tue Nov 16 09:51:49 2010

John,

That sounds fine.  I'll go ahead and resolve this ticket.  But feel
free to write when you need some assistance.

Thanks,
John

On 11/16/2010 07:08 AM, RAL HelpDesk {for Raby, John} wrote:
> After we complete this project, we will revisit this and get back
with you on

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