[Met_help] [rt.rap.ucar.edu #65367] History for MET-TC TK_ERR, MSLP_ERR?
John Halley Gotway via RT
met_help at ucar.edu
Mon Aug 17 12:14:56 MDT 2015
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi ,
I have a cursory knowledge of tc_pairs and tc_stats now, and am moving
on from the example in the tutorial. In that example, track error is
analyzed. This is done by simply specifying the TK_ERR column. Next I
would like to the same thing with MSLP error. Is there an equivalent
way to do this? I figured there would be a MSLP_ERR column, but
couldn't find it. . .
Dave
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65367] MET-TC TK_ERR, MSLP_ERR?
From: John Halley Gotway
Time: Mon Feb 10 11:08:34 2014
Dave,
The .tcst files created by tc_pairs contain some "error" columns that
are computed by comparing the ADECK and BDECK track locations: TK_ERR,
ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
along-track, cross-track, east-west error, and north-south error.
Those types of errors are not trivial to compute, so tc_pairs does it
for you.
Other types of errors, like the difference of the mean sea level
pressures or differences in wind radii are trivial to compute. If we
had included all possible differences in the .tcst output line
that would have made an already long output line even longer.
Instead, tc_stat supports the use of the minus sign and/or "ABS".
For example, try the following...
-column AMSLP-BMSLP # For the MSLP error
-column ABS\(AMSLP-BMSLP\) # For the absolute MSLP error
-column ABS\(Y_ERR\) # For the absolute value of the north-
south track error
If you're running this on the command line, you'll need to escape the
'(' and ')' characters. If you use a config file, you shouldn't need
to.
So you can define arbitrary differences of the .tcst output columns
with/without absolute values. Hope that helps clarify.
Thanks,
John
On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
>
> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
> Transaction: Ticket created by ahijevyc
> Queue: met_help
> Subject: MET-TC TK_ERR, MSLP_ERR?
> Owner: Nobody
> Requestors: ahijevyc at ucar.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
>
>
> Hi ,
> I have a cursory knowledge of tc_pairs and tc_stats now, and am
moving
> on from the example in the tutorial. In that example, track error
is
> analyzed. This is done by simply specifying the TK_ERR column.
Next I
> would like to the same thing with MSLP error. Is there an
equivalent
> way to do this? I figured there would be a MSLP_ERR column, but
> couldn't find it. . .
>
> Dave
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #65367] MET-TC TK_ERR, MSLP_ERR?
From: David Ahijevych
Time: Mon Feb 10 13:23:26 2014
I think this is exactly what I was looking for - thanks for taking the
time to answer this!
On 2/10/14 11:08 AM, John Halley Gotway via RT wrote:
> Dave,
>
> The .tcst files created by tc_pairs contain some "error" columns
that are computed by comparing the ADECK and BDECK track locations:
TK_ERR, ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
> along-track, cross-track, east-west error, and north-south error.
Those types of errors are not trivial to compute, so tc_pairs does it
for you.
>
> Other types of errors, like the difference of the mean sea level
pressures or differences in wind radii are trivial to compute. If we
had included all possible differences in the .tcst output line
> that would have made an already long output line even longer.
Instead, tc_stat supports the use of the minus sign and/or "ABS".
>
> For example, try the following...
> -column AMSLP-BMSLP # For the MSLP error
> -column ABS\(AMSLP-BMSLP\) # For the absolute MSLP error
> -column ABS\(Y_ERR\) # For the absolute value of the
north-south track error
>
> If you're running this on the command line, you'll need to escape
the '(' and ')' characters. If you use a config file, you shouldn't
need to.
>
> So you can define arbitrary differences of the .tcst output columns
with/without absolute values. Hope that helps clarify.
>
> Thanks,
> John
>
> On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
>> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
>> Transaction: Ticket created by ahijevyc
>> Queue: met_help
>> Subject: MET-TC TK_ERR, MSLP_ERR?
>> Owner: Nobody
>> Requestors: ahijevyc at ucar.edu
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
>>
>>
>> Hi ,
>> I have a cursory knowledge of tc_pairs and tc_stats now, and am
moving
>> on from the example in the tutorial. In that example, track error
is
>> analyzed. This is done by simply specifying the TK_ERR column.
Next I
>> would like to the same thing with MSLP error. Is there an
equivalent
>> way to do this? I figured there would be a MSLP_ERR column, but
>> couldn't find it. . .
>>
>> Dave
>>
>>
------------------------------------------------
Subject: MET-TC TK_ERR, MSLP_ERR?
From: David Ahijevych
Time: Wed Aug 05 11:14:42 2015
Hi everyone,
As far as I can tell, MET-TC software (which would be ideal for this)
doesn't calculate error statistics for radius of maximum wind (RMW).
It
does MSLP, VMAX, and distance to 34, 50, and 64kt winds in all 4
quadrants,
but no RMW. Is it possible to add this?
Thanks!
Dave
On Mon, Feb 10, 2014 at 1:23 PM, Dave Ahijevych <ahijevyc at ucar.edu>
wrote:
> I think this is exactly what I was looking for - thanks for taking
the
> time to answer this!
>
>
> On 2/10/14 11:08 AM, John Halley Gotway via RT wrote:
>
>> Dave,
>>
>> The .tcst files created by tc_pairs contain some "error" columns
that are
>> computed by comparing the ADECK and BDECK track locations: TK_ERR,
>> ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
>> along-track, cross-track, east-west error, and north-south error.
Those
>> types of errors are not trivial to compute, so tc_pairs does it for
you.
>>
>> Other types of errors, like the difference of the mean sea level
>> pressures or differences in wind radii are trivial to compute. If
we had
>> included all possible differences in the .tcst output line
>> that would have made an already long output line even longer.
Instead,
>> tc_stat supports the use of the minus sign and/or "ABS".
>>
>> For example, try the following...
>> -column AMSLP-BMSLP # For the MSLP error
>> -column ABS\(AMSLP-BMSLP\) # For the absolute MSLP error
>> -column ABS\(Y_ERR\) # For the absolute value of the
>> north-south track error
>>
>> If you're running this on the command line, you'll need to escape
the '('
>> and ')' characters. If you use a config file, you shouldn't need
to.
>>
>> So you can define arbitrary differences of the .tcst output columns
>> with/without absolute values. Hope that helps clarify.
>>
>> Thanks,
>> John
>>
>> On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
>>
>>> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
>>> Transaction: Ticket created by ahijevyc
>>> Queue: met_help
>>> Subject: MET-TC TK_ERR, MSLP_ERR?
>>> Owner: Nobody
>>> Requestors: ahijevyc at ucar.edu
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367
>>> >
>>>
>>>
>>>
>>> Hi ,
>>> I have a cursory knowledge of tc_pairs and tc_stats now, and am
moving
>>> on from the example in the tutorial. In that example, track error
is
>>> analyzed. This is done by simply specifying the TK_ERR column.
Next I
>>> would like to the same thing with MSLP error. Is there an
equivalent
>>> way to do this? I figured there would be a MSLP_ERR column, but
>>> couldn't find it. . .
>>>
>>> Dave
>>>
>>>
>>>
>
------------------------------------------------
Subject: MET-TC TK_ERR, MSLP_ERR?
From: John Halley Gotway
Time: Wed Aug 05 11:48:12 2015
Dave,
Good point. It looks like we stopped dumping out ADECK and BDECK
information after the 34, 50, and 64 kt wind radii. Here's the ATCF
file
format description:
http://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html
After the winds, there are several quantities that could be added:
RRP, MRD, GUSTS, EYE, SUBREGION, MAXSEAS, INITIALS, DIR, SPEED,
DETH,
SEAS, and then the seas radii (just like the wind info)
Listing values for ADECK and BDECK in the TCMPR output line would add
twice
as many columns to the output file.
Is it just radius of maximum winds you're after or would these other
quantities be useful as well?
I've CC'ed Tara Jensen (the MET project lead) and Kathryn Newman (MET-
TC
expert) to get their take on it.
Thanks,
John
On Wed, Aug 5, 2015 at 11:14 AM, David Ahijevych via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
>
> Hi everyone,
>
> As far as I can tell, MET-TC software (which would be ideal for
this)
> doesn't calculate error statistics for radius of maximum wind (RMW).
It
> does MSLP, VMAX, and distance to 34, 50, and 64kt winds in all 4
quadrants,
> but no RMW. Is it possible to add this?
> Thanks!
>
> Dave
>
>
> On Mon, Feb 10, 2014 at 1:23 PM, Dave Ahijevych <ahijevyc at ucar.edu>
wrote:
>
> > I think this is exactly what I was looking for - thanks for taking
the
> > time to answer this!
> >
> >
> > On 2/10/14 11:08 AM, John Halley Gotway via RT wrote:
> >
> >> Dave,
> >>
> >> The .tcst files created by tc_pairs contain some "error" columns
that
> are
> >> computed by comparing the ADECK and BDECK track locations:
TK_ERR,
> >> ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
> >> along-track, cross-track, east-west error, and north-south error.
Those
> >> types of errors are not trivial to compute, so tc_pairs does it
for you.
> >>
> >> Other types of errors, like the difference of the mean sea level
> >> pressures or differences in wind radii are trivial to compute.
If we
> had
> >> included all possible differences in the .tcst output line
> >> that would have made an already long output line even longer.
Instead,
> >> tc_stat supports the use of the minus sign and/or "ABS".
> >>
> >> For example, try the following...
> >> -column AMSLP-BMSLP # For the MSLP error
> >> -column ABS\(AMSLP-BMSLP\) # For the absolute MSLP error
> >> -column ABS\(Y_ERR\) # For the absolute value of the
> >> north-south track error
> >>
> >> If you're running this on the command line, you'll need to escape
the
> '('
> >> and ')' characters. If you use a config file, you shouldn't need
to.
> >>
> >> So you can define arbitrary differences of the .tcst output
columns
> >> with/without absolute values. Hope that helps clarify.
> >>
> >> Thanks,
> >> John
> >>
> >> On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
> >>
> >>> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
> >>> Transaction: Ticket created by ahijevyc
> >>> Queue: met_help
> >>> Subject: MET-TC TK_ERR, MSLP_ERR?
> >>> Owner: Nobody
> >>> Requestors: ahijevyc at ucar.edu
> >>> Status: new
> >>> Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367
> >>> >
> >>>
> >>>
> >>>
> >>> Hi ,
> >>> I have a cursory knowledge of tc_pairs and tc_stats now, and am
moving
> >>> on from the example in the tutorial. In that example, track
error is
> >>> analyzed. This is done by simply specifying the TK_ERR column.
Next I
> >>> would like to the same thing with MSLP error. Is there an
equivalent
> >>> way to do this? I figured there would be a MSLP_ERR column, but
> >>> couldn't find it. . .
> >>>
> >>> Dave
> >>>
> >>>
> >>>
> >
>
>
------------------------------------------------
Subject: MET-TC TK_ERR, MSLP_ERR?
From: David Ahijevych
Time: Wed Aug 05 13:45:30 2015
Hi John,
Radius of max winds is the main thing. It's much more useful than
anything
else.
RRP MRD GUSTS EYE DEPTH could be useful, but most models don't output
these
parameters.
I'd say MAXSEAS and SEAS are even less useful because the models I
look at
don't have wave height information to compare to.
And it seems pointless to compare fields like SUBREGION and INITIALS.
Dave
On Wed, Aug 5, 2015 at 11:48 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Dave,
>
> Good point. It looks like we stopped dumping out ADECK and BDECK
> information after the 34, 50, and 64 kt wind radii. Here's the ATCF
file
> format description:
>
http://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html
>
> After the winds, there are several quantities that could be added:
> RRP, MRD, GUSTS, EYE, SUBREGION, MAXSEAS, INITIALS, DIR, SPEED,
DETH,
> SEAS, and then the seas radii (just like the wind info)
>
> Listing values for ADECK and BDECK in the TCMPR output line would
add twice
> as many columns to the output file.
>
> Is it just radius of maximum winds you're after or would these other
> quantities be useful as well?
>
> I've CC'ed Tara Jensen (the MET project lead) and Kathryn Newman
(MET-TC
> expert) to get their take on it.
>
> Thanks,
> John
>
>
>
> On Wed, Aug 5, 2015 at 11:14 AM, David Ahijevych via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
> >
> > Hi everyone,
> >
> > As far as I can tell, MET-TC software (which would be ideal for
this)
> > doesn't calculate error statistics for radius of maximum wind
(RMW). It
> > does MSLP, VMAX, and distance to 34, 50, and 64kt winds in all 4
> quadrants,
> > but no RMW. Is it possible to add this?
> > Thanks!
> >
> > Dave
> >
> >
> > On Mon, Feb 10, 2014 at 1:23 PM, Dave Ahijevych
<ahijevyc at ucar.edu>
> wrote:
> >
> > > I think this is exactly what I was looking for - thanks for
taking the
> > > time to answer this!
> > >
> > >
> > > On 2/10/14 11:08 AM, John Halley Gotway via RT wrote:
> > >
> > >> Dave,
> > >>
> > >> The .tcst files created by tc_pairs contain some "error"
columns that
> > are
> > >> computed by comparing the ADECK and BDECK track locations:
TK_ERR,
> > >> ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
> > >> along-track, cross-track, east-west error, and north-south
error.
> Those
> > >> types of errors are not trivial to compute, so tc_pairs does it
for
> you.
> > >>
> > >> Other types of errors, like the difference of the mean sea
level
> > >> pressures or differences in wind radii are trivial to compute.
If we
> > had
> > >> included all possible differences in the .tcst output line
> > >> that would have made an already long output line even longer.
> Instead,
> > >> tc_stat supports the use of the minus sign and/or "ABS".
> > >>
> > >> For example, try the following...
> > >> -column AMSLP-BMSLP # For the MSLP error
> > >> -column ABS\(AMSLP-BMSLP\) # For the absolute MSLP error
> > >> -column ABS\(Y_ERR\) # For the absolute value of the
> > >> north-south track error
> > >>
> > >> If you're running this on the command line, you'll need to
escape the
> > '('
> > >> and ')' characters. If you use a config file, you shouldn't
need to.
> > >>
> > >> So you can define arbitrary differences of the .tcst output
columns
> > >> with/without absolute values. Hope that helps clarify.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
> > >>
> > >>> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
> > >>> Transaction: Ticket created by ahijevyc
> > >>> Queue: met_help
> > >>> Subject: MET-TC TK_ERR, MSLP_ERR?
> > >>> Owner: Nobody
> > >>> Requestors: ahijevyc at ucar.edu
> > >>> Status: new
> > >>> Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>> Hi ,
> > >>> I have a cursory knowledge of tc_pairs and tc_stats now, and
am
> moving
> > >>> on from the example in the tutorial. In that example, track
error is
> > >>> analyzed. This is done by simply specifying the TK_ERR
column.
> Next I
> > >>> would like to the same thing with MSLP error. Is there an
equivalent
> > >>> way to do this? I figured there would be a MSLP_ERR column,
but
> > >>> couldn't find it. . .
> > >>>
> > >>> Dave
> > >>>
> > >>>
> > >>>
> > >
> >
> >
>
>
------------------------------------------------
Subject: MET-TC TK_ERR, MSLP_ERR?
From: David Ahijevych
Time: Wed Aug 05 13:49:47 2015
Oh, and DIR and SPEED could be useful. DIR error is a little tricky
to do
since it's a circular variable.
Dave
On Wed, Aug 5, 2015 at 1:45 PM, David Ahijevych <ahijevyc at ucar.edu>
wrote:
> Hi John,
>
> Radius of max winds is the main thing. It's much more useful than
> anything else.
> RRP MRD GUSTS EYE DEPTH could be useful, but most models don't
output
> these parameters.
>
> I'd say MAXSEAS and SEAS are even less useful because the models I
look at
> don't have wave height information to compare to.
>
> And it seems pointless to compare fields like SUBREGION and
INITIALS.
>
> Dave
>
>
> On Wed, Aug 5, 2015 at 11:48 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Dave,
>>
>> Good point. It looks like we stopped dumping out ADECK and BDECK
>> information after the 34, 50, and 64 kt wind radii. Here's the
ATCF file
>> format description:
>>
http://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html
>>
>> After the winds, there are several quantities that could be added:
>> RRP, MRD, GUSTS, EYE, SUBREGION, MAXSEAS, INITIALS, DIR, SPEED,
DETH,
>> SEAS, and then the seas radii (just like the wind info)
>>
>> Listing values for ADECK and BDECK in the TCMPR output line would
add
>> twice
>> as many columns to the output file.
>>
>> Is it just radius of maximum winds you're after or would these
other
>> quantities be useful as well?
>>
>> I've CC'ed Tara Jensen (the MET project lead) and Kathryn Newman
(MET-TC
>> expert) to get their take on it.
>>
>> Thanks,
>> John
>>
>>
>>
>> On Wed, Aug 5, 2015 at 11:14 AM, David Ahijevych via RT <
>> met_help at ucar.edu>
>> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
>> >
>> > Hi everyone,
>> >
>> > As far as I can tell, MET-TC software (which would be ideal for
this)
>> > doesn't calculate error statistics for radius of maximum wind
(RMW). It
>> > does MSLP, VMAX, and distance to 34, 50, and 64kt winds in all 4
>> quadrants,
>> > but no RMW. Is it possible to add this?
>> > Thanks!
>> >
>> > Dave
>> >
>> >
>> > On Mon, Feb 10, 2014 at 1:23 PM, Dave Ahijevych
<ahijevyc at ucar.edu>
>> wrote:
>> >
>> > > I think this is exactly what I was looking for - thanks for
taking the
>> > > time to answer this!
>> > >
>> > >
>> > > On 2/10/14 11:08 AM, John Halley Gotway via RT wrote:
>> > >
>> > >> Dave,
>> > >>
>> > >> The .tcst files created by tc_pairs contain some "error"
columns that
>> > are
>> > >> computed by comparing the ADECK and BDECK track locations:
TK_ERR,
>> > >> ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
>> > >> along-track, cross-track, east-west error, and north-south
error.
>> Those
>> > >> types of errors are not trivial to compute, so tc_pairs does
it for
>> you.
>> > >>
>> > >> Other types of errors, like the difference of the mean sea
level
>> > >> pressures or differences in wind radii are trivial to compute.
If we
>> > had
>> > >> included all possible differences in the .tcst output line
>> > >> that would have made an already long output line even longer.
>> Instead,
>> > >> tc_stat supports the use of the minus sign and/or "ABS".
>> > >>
>> > >> For example, try the following...
>> > >> -column AMSLP-BMSLP # For the MSLP error
>> > >> -column ABS\(AMSLP-BMSLP\) # For the absolute MSLP error
>> > >> -column ABS\(Y_ERR\) # For the absolute value of
the
>> > >> north-south track error
>> > >>
>> > >> If you're running this on the command line, you'll need to
escape the
>> > '('
>> > >> and ')' characters. If you use a config file, you shouldn't
need to.
>> > >>
>> > >> So you can define arbitrary differences of the .tcst output
columns
>> > >> with/without absolute values. Hope that helps clarify.
>> > >>
>> > >> Thanks,
>> > >> John
>> > >>
>> > >> On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
>> > >>
>> > >>> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
>> > >>> Transaction: Ticket created by ahijevyc
>> > >>> Queue: met_help
>> > >>> Subject: MET-TC TK_ERR, MSLP_ERR?
>> > >>> Owner: Nobody
>> > >>> Requestors: ahijevyc at ucar.edu
>> > >>> Status: new
>> > >>> Ticket <URL:
>> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367
>> > >>> >
>> > >>>
>> > >>>
>> > >>>
>> > >>> Hi ,
>> > >>> I have a cursory knowledge of tc_pairs and tc_stats now, and
am
>> moving
>> > >>> on from the example in the tutorial. In that example, track
error
>> is
>> > >>> analyzed. This is done by simply specifying the TK_ERR
column.
>> Next I
>> > >>> would like to the same thing with MSLP error. Is there an
>> equivalent
>> > >>> way to do this? I figured there would be a MSLP_ERR column,
but
>> > >>> couldn't find it. . .
>> > >>>
>> > >>> Dave
>> > >>>
>> > >>>
>> > >>>
>> > >
>> >
>> >
>>
>>
>
------------------------------------------------
Subject: MET-TC TK_ERR, MSLP_ERR?
From: John Halley Gotway
Time: Wed Aug 05 14:42:41 2015
Dave,
Thanks for sending the details. I created a new development ticket to
track this request and included the notes you sent. We're working on
the
next release, 5.1, now and the question is whether we'll have
time/funding
to get these changes into 5.1 or if we'll have to wait until the next
release.
I'll talk to Tara about it at our development meeting tomorrow.
Thanks,
John
On Wed, Aug 5, 2015 at 1:49 PM, David Ahijevych via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
>
> Oh, and DIR and SPEED could be useful. DIR error is a little tricky
to do
> since it's a circular variable.
>
> Dave
>
>
> On Wed, Aug 5, 2015 at 1:45 PM, David Ahijevych <ahijevyc at ucar.edu>
wrote:
>
> > Hi John,
> >
> > Radius of max winds is the main thing. It's much more useful than
> > anything else.
> > RRP MRD GUSTS EYE DEPTH could be useful, but most models don't
output
> > these parameters.
> >
> > I'd say MAXSEAS and SEAS are even less useful because the models I
look
> at
> > don't have wave height information to compare to.
> >
> > And it seems pointless to compare fields like SUBREGION and
INITIALS.
> >
> > Dave
> >
> >
> > On Wed, Aug 5, 2015 at 11:48 AM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Dave,
> >>
> >> Good point. It looks like we stopped dumping out ADECK and BDECK
> >> information after the 34, 50, and 64 kt wind radii. Here's the
ATCF
> file
> >> format description:
> >>
http://www.nrlmry.navy.mil/atcf_web/docs/database/new/abrdeck.html
> >>
> >> After the winds, there are several quantities that could be
added:
> >> RRP, MRD, GUSTS, EYE, SUBREGION, MAXSEAS, INITIALS, DIR,
SPEED, DETH,
> >> SEAS, and then the seas radii (just like the wind info)
> >>
> >> Listing values for ADECK and BDECK in the TCMPR output line would
add
> >> twice
> >> as many columns to the output file.
> >>
> >> Is it just radius of maximum winds you're after or would these
other
> >> quantities be useful as well?
> >>
> >> I've CC'ed Tara Jensen (the MET project lead) and Kathryn Newman
(MET-TC
> >> expert) to get their take on it.
> >>
> >> Thanks,
> >> John
> >>
> >>
> >>
> >> On Wed, Aug 5, 2015 at 11:14 AM, David Ahijevych via RT <
> >> met_help at ucar.edu>
> >> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367 >
> >> >
> >> > Hi everyone,
> >> >
> >> > As far as I can tell, MET-TC software (which would be ideal for
this)
> >> > doesn't calculate error statistics for radius of maximum wind
(RMW).
> It
> >> > does MSLP, VMAX, and distance to 34, 50, and 64kt winds in all
4
> >> quadrants,
> >> > but no RMW. Is it possible to add this?
> >> > Thanks!
> >> >
> >> > Dave
> >> >
> >> >
> >> > On Mon, Feb 10, 2014 at 1:23 PM, Dave Ahijevych
<ahijevyc at ucar.edu>
> >> wrote:
> >> >
> >> > > I think this is exactly what I was looking for - thanks for
taking
> the
> >> > > time to answer this!
> >> > >
> >> > >
> >> > > On 2/10/14 11:08 AM, John Halley Gotway via RT wrote:
> >> > >
> >> > >> Dave,
> >> > >>
> >> > >> The .tcst files created by tc_pairs contain some "error"
columns
> that
> >> > are
> >> > >> computed by comparing the ADECK and BDECK track locations:
TK_ERR,
> >> > >> ALTK_ERR, CRTK_ERR, X_ERR, and Y_ERR for track,
> >> > >> along-track, cross-track, east-west error, and north-south
error.
> >> Those
> >> > >> types of errors are not trivial to compute, so tc_pairs does
it for
> >> you.
> >> > >>
> >> > >> Other types of errors, like the difference of the mean sea
level
> >> > >> pressures or differences in wind radii are trivial to
compute. If
> we
> >> > had
> >> > >> included all possible differences in the .tcst output line
> >> > >> that would have made an already long output line even
longer.
> >> Instead,
> >> > >> tc_stat supports the use of the minus sign and/or "ABS".
> >> > >>
> >> > >> For example, try the following...
> >> > >> -column AMSLP-BMSLP # For the MSLP error
> >> > >> -column ABS\(AMSLP-BMSLP\) # For the absolute MSLP
error
> >> > >> -column ABS\(Y_ERR\) # For the absolute value of
the
> >> > >> north-south track error
> >> > >>
> >> > >> If you're running this on the command line, you'll need to
escape
> the
> >> > '('
> >> > >> and ')' characters. If you use a config file, you shouldn't
need
> to.
> >> > >>
> >> > >> So you can define arbitrary differences of the .tcst output
columns
> >> > >> with/without absolute values. Hope that helps clarify.
> >> > >>
> >> > >> Thanks,
> >> > >> John
> >> > >>
> >> > >> On 02/07/2014 03:18 PM, David Ahijevych via RT wrote:
> >> > >>
> >> > >>> Fri Feb 07 15:18:55 2014: Request 65367 was acted upon.
> >> > >>> Transaction: Ticket created by ahijevyc
> >> > >>> Queue: met_help
> >> > >>> Subject: MET-TC TK_ERR, MSLP_ERR?
> >> > >>> Owner: Nobody
> >> > >>> Requestors: ahijevyc at ucar.edu
> >> > >>> Status: new
> >> > >>> Ticket <URL:
> >> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=65367
> >> > >>> >
> >> > >>>
> >> > >>>
> >> > >>>
> >> > >>> Hi ,
> >> > >>> I have a cursory knowledge of tc_pairs and tc_stats now,
and am
> >> moving
> >> > >>> on from the example in the tutorial. In that example,
track error
> >> is
> >> > >>> analyzed. This is done by simply specifying the TK_ERR
column.
> >> Next I
> >> > >>> would like to the same thing with MSLP error. Is there an
> >> equivalent
> >> > >>> way to do this? I figured there would be a MSLP_ERR
column, but
> >> > >>> couldn't find it. . .
> >> > >>>
> >> > >>> Dave
> >> > >>>
> >> > >>>
> >> > >>>
> >> > >
> >> >
> >> >
> >>
> >>
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list