[Met_help] [rt.rap.ucar.edu #85250] History for ref: Averaging Track Errors

[John Halley Gotway via RT]

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

Does METPLUS have the capability to average a series of extratropical
cyclones to
a single value?

ie

108,GFSO,ML0302532015,20150327_120000,TK_ERR,609.49759
108,GFSO,ML0100872015,20150112_000000,TK_ERR,588.38804
108,GFSO,ML0101032015,20150114_120000,TK_ERR,575.01756
108,GFSO,ML0101032015,20150114_060000,TK_ERR,507.32313
108,GFSO,ML0201242015,20150214_120000,TK_ERR,494.24908


for ht 108 hr, average the above data( 5 entries)ll to as single TK_ERR
value

  108 hr TK_ERR = 525,34572 (example)

if so, what codes are used.

Thanks,
Steve


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

Subject: ref: Averaging Track Errors
From: John Halley Gotway
Time: Mon May 21 13:25:47 2018

Hi Steve,

This is John Halley Gotway.  I just talked to Minna Win, a python MET+
developer.  She ported over this use case into MET+ but I don't think
that
it includes stand-alone calls to tc_stat.

Let me tell you *how* you'd compute an average values for TK_ERR
across
multiple cases using the MET tools, and then we can figure out if/how
to
incorporate them into the MET+ Python scripts.

So this is pretty straight-forward.  You'd run a tc_stat "summary"
job.
You pass to the output files from tc_pairs as input to tc_stat.  Pick
a
line type of interest... TCMPR for the TK_ERR data.  Pick any set of
filtering criteria for the input data.  Pick one or more columns of
interest.  And pick any stratification info you'd like.

To demonstrate, I've attached a sample output file from tc_pairs
(alal2010.tcst).

Here's a summary job you could run:
   met-7.0/bin/tc_stat -job summary -lookin ~/alal2010.tcst -line_type
TCMPR -column TK_ERR

That selects the TK_ERR column of data from the input lines and
reports
summary info about the data, including the MEAN value.

Perhaps you're only interested in the 108 hour lead time (-lead
108)... and
you want to results broken out separately for each model (-by
AMODEL)...
and you also want to see the maximum wind speed (-column AMAX_WIND) :
   met-7.0/bin/tc_stat -job summary -lookin ~/alal2010.tcst -line_type
TCMPR -column TK_ERR,AMAX_WIND -lead 108 -by AMODEL

So there's definitely functionality to do what you'd like... and you
can
find more info in the online tutorial:

https://dtcenter.org/met/users/support/online_tutorial/METv6.1/tutorial.php?name=tc_stat&category=index

But it may not be clearly laid out how to call tc_stat in this way
through
METplus.

Thanks,
John



On Mon, May 21, 2018 at 11:12 AM, Steven Lilly - NOAA Federal via RT <
met_help at ucar.edu> wrote:

>
> Mon May 21 11:12:11 2018: Request 85250 was acted upon.
> Transaction: Ticket created by steven.lilly at noaa.gov
>        Queue: met_help
>      Subject: ref: Averaging Track Errors
>        Owner: Nobody
>   Requestors: steven.lilly at noaa.gov
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85250 >
>
>
> Does METPLUS have the capability to average a series of
extratropical
> cyclones to
> a single value?
>
> ie
>
> 108,GFSO,ML0302532015,20150327_120000,TK_ERR,609.49759
> 108,GFSO,ML0100872015,20150112_000000,TK_ERR,588.38804
> 108,GFSO,ML0101032015,20150114_120000,TK_ERR,575.01756
> 108,GFSO,ML0101032015,20150114_060000,TK_ERR,507.32313
> 108,GFSO,ML0201242015,20150214_120000,TK_ERR,494.24908
>
>
> for ht 108 hr, average the above data( 5 entries)ll to as single
TK_ERR
> value
>
>   108 hr TK_ERR = 525,34572 (example)
>
> if so, what codes are used.
>
> Thanks,
> Steve
>
>

------------------------------------------------
Subject: ref: Averaging Track Errors
From: Steven Lilly - NOAA Federal
Time: Tue Jul 09 14:51:18 2019

Thank you for your assistance.

Steve

On Tue, Jul 9, 2019 at 2:17 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:

> According to our records, your request has been resolved. If you
have any
> further questions or concerns, please respond to this message.
>

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