[Met_help] [rt.rap.ucar.edu #92899] History for GO_INDEX Messages
John Halley Gotway via RT
met_help at ucar.edu
Fri Nov 1 13:30:14 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, first of all there should be 13 attached files. Let me know if you
didn't get all of them. When I run "go_index_calculation" to generate a GO
index for the mdl and ref, I get a lot of warning messages which I am not
sure what is causing them. The list file is the MET listing I got from the
run. Notice all the warning messages. The main issue that stands out is
that I have defined my four forecast hours to be 12 24 72 120. The listing
reflects this at the beginning but at some point it reverts to using 12 24
36 48. Why is this the case? The second issue seems to be that if the
Fcst valid begin dates differ, then it skips that item. I assume this is
the correct behavior.
Thanks
Bob
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: GO_INDEX Messages
From: John Halley Gotway
Time: Fri Nov 01 09:30:47 2019
Bob,
Yes, I did received 13 files. I was able to replicate the behavior
you
describe with your data. I started writing up a lot of details, but
will
just skip to the punchline. Please switch from using "*-job
go_index*" to
using "*-job ss_index*". And then your job should run fine and
produce:
COL_NAME: SS_INDEX
SS_INDEX: 0.99407
When we initially added support for the GO Index, we realized that it
was
just a special case of a more generalized weighted average of skill
scores. So we added support for a general Skill-Score Index
(ss_index) job
type where the user defines the input terms in a config file. And
then we
defined the GO Index job type as a special case of the Skill-Score
Index
where STAT-Analysis automatically reads this config file "
*met-8.1/share/met/config/STATAnalysisConfig_GO_Index*" to define the
terms. The intention was to make the GO Index easier to run. So
that's
why the definition of the terms changed... since you ran "*-job
go_index*",
STAT-Analysis automatically read in the GO Index definition file and
overrode your settings.
Looking at the "*list*" file you sent, I see that there's no log
message
indicating that STAT-Analysis is reading that GO Index config file.
I'll
add that log message for met-9.0 to make the processing logic more
transparent.
Thanks,
John
On Fri, Nov 1, 2019 at 8:29 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri Nov 01 08:29:02 2019: Request 92899 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: GO_INDEX Messages
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92899 >
>
>
> John, first of all there should be 13 attached files. Let me know
if you
> didn't get all of them. When I run "go_index_calculation" to
generate a GO
> index for the mdl and ref, I get a lot of warning messages which I
am not
> sure what is causing them. The list file is the MET listing I got
from the
> run. Notice all the warning messages. The main issue that stands
out is
> that I have defined my four forecast hours to be 12 24 72 120. The
> listing
> reflects this at the beginning but at some point it reverts to using
12 24
> 36 48. Why is this the case? The second issue seems to be that if
the
>
> Fcst valid begin dates differ, then it skips that item. I assume
this is
> the correct behavior.
>
>
>
> Thanks
>
> Bob
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #92899] GO_INDEX Messages
From: robert.craig.2 at us.af.mil
Time: Fri Nov 01 10:42:19 2019
John, That was it. Will you update the user's manual as well.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, November 1, 2019 10:31 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92899] GO_INDEX
Messages
Bob,
Yes, I did received 13 files. I was able to replicate the behavior
you describe with your data. I started writing up a lot of details,
but will just skip to the punchline. Please switch from using "*-job
go_index*" to using "*-job ss_index*". And then your job should run
fine and produce:
COL_NAME: SS_INDEX
SS_INDEX: 0.99407
When we initially added support for the GO Index, we realized that it
was just a special case of a more generalized weighted average of
skill scores. So we added support for a general Skill-Score Index
(ss_index) job type where the user defines the input terms in a config
file. And then we defined the GO Index job type as a special case of
the Skill-Score Index where STAT-Analysis automatically reads this
config file "
*met-8.1/share/met/config/STATAnalysisConfig_GO_Index*" to define the
terms. The intention was to make the GO Index easier to run. So
that's why the definition of the terms changed... since you ran "*-job
go_index*", STAT-Analysis automatically read in the GO Index
definition file and overrode your settings.
Looking at the "*list*" file you sent, I see that there's no log
message indicating that STAT-Analysis is reading that GO Index config
file. I'll add that log message for met-9.0 to make the processing
logic more transparent.
Thanks,
John
On Fri, Nov 1, 2019 at 8:29 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri Nov 01 08:29:02 2019: Request 92899 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: GO_INDEX Messages
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92899
> >
>
>
> John, first of all there should be 13 attached files. Let me know
if
> you didn't get all of them. When I run "go_index_calculation" to
> generate a GO index for the mdl and ref, I get a lot of warning
> messages which I am not sure what is causing them. The list file is
> the MET listing I got from the run. Notice all the warning
messages. The main issue that stands out is
> that I have defined my four forecast hours to be 12 24 72 120. The
> listing
> reflects this at the beginning but at some point it reverts to using
12 24
> 36 48. Why is this the case? The second issue seems to be that if
the
>
> Fcst valid begin dates differ, then it skips that item. I assume
this
> is the correct behavior.
>
>
>
> Thanks
>
> Bob
>
>
>
------------------------------------------------
Subject: GO_INDEX Messages
From: John Halley Gotway
Time: Fri Nov 01 13:29:09 2019
Bob,
Thanks for pointing that out. I found two spots in the user's guide
that
should list the ss_index job type and have updated the documentation
for
met-9.0.
Thanks,
John
On Fri, Nov 1, 2019 at 10:42 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92899 >
>
> John, That was it. Will you update the user's manual as well.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, November 1, 2019 10:31 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92899] GO_INDEX
Messages
>
> Bob,
>
> Yes, I did received 13 files. I was able to replicate the behavior
you
> describe with your data. I started writing up a lot of details, but
will
> just skip to the punchline. Please switch from using "*-job
go_index*" to
> using "*-job ss_index*". And then your job should run fine and
produce:
> COL_NAME: SS_INDEX
> SS_INDEX: 0.99407
>
> When we initially added support for the GO Index, we realized that
it was
> just a special case of a more generalized weighted average of skill
> scores. So we added support for a general Skill-Score Index
(ss_index) job
> type where the user defines the input terms in a config file. And
then we
> defined the GO Index job type as a special case of the Skill-Score
Index
> where STAT-Analysis automatically reads this config file "
> *met-8.1/share/met/config/STATAnalysisConfig_GO_Index*" to define
the
> terms. The intention was to make the GO Index easier to run. So
that's
> why the definition of the terms changed... since you ran "*-job
go_index*",
> STAT-Analysis automatically read in the GO Index definition file and
> overrode your settings.
>
> Looking at the "*list*" file you sent, I see that there's no log
message
> indicating that STAT-Analysis is reading that GO Index config file.
I'll
> add that log message for met-9.0 to make the processing logic more
> transparent.
>
> Thanks,
> John
>
>
> On Fri, Nov 1, 2019 at 8:29 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Nov 01 08:29:02 2019: Request 92899 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: GO_INDEX Messages
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92899
> > >
> >
> >
> > John, first of all there should be 13 attached files. Let me know
if
> > you didn't get all of them. When I run "go_index_calculation" to
> > generate a GO index for the mdl and ref, I get a lot of warning
> > messages which I am not sure what is causing them. The list file
is
> > the MET listing I got from the run. Notice all the warning
messages.
> The main issue that stands out is
> > that I have defined my four forecast hours to be 12 24 72 120.
The
> > listing
> > reflects this at the beginning but at some point it reverts to
using 12
> 24
> > 36 48. Why is this the case? The second issue seems to be that
if the
> >
> > Fcst valid begin dates differ, then it skips that item. I assume
this
> > is the correct behavior.
> >
> >
> >
> > Thanks
> >
> > Bob
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list