[Met_help] [rt.rap.ucar.edu #99156] History for point_stat obs dict
John Halley Gotway via RT
met_help at ucar.edu
Mon Apr 19 11:30:44 MDT 2021
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
In the obs dictionary of the point_stat config file, I have the following:
69 obs = {
70 field = [
71 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
72 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
73 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
74 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
75 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
76 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
77 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
78 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
79 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
80 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];}
81 ];
82 }
When I specify a level of say, level=["P199.5-200.5"], what happens in
point_stat when it finds ONE radiosonde that has, say 10 measurements whose
pressure levels fall within this range? Does some interpolation occur or
will point_stat just return 10 measurements Matched pairs?
Justin
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: point_stat obs dict
From: John Halley Gotway
Time: Fri Mar 19 23:39:41 2021
Hi Justin,
I see you have a question about what happens when multiple vertical
level
matches are found by point-stat for a particular station.
And the answer is that they will all be included in the verification.
So 10
obs within the vertical level range should result in 10 matched pairs.
If
the forecast vertical level range includes model levels above/below,
the
obs then the model values above/below will be interpolated linear in
the
log of pressure to the pressure level of the observation. If the
forecast
range includes only one model level, no vertical interpolation is
performed.
If you search for “obs_summary” on this page:
https://met.readthedocs.io/en/v9.1.3/Users_Guide/data_io.html#data-io-
met-configuration-file-options
You’ll see that that config option controls what happens a when
multiple
obs are found for a station within the time window. However, in your
case,
this logic wouldn’t apply since the pressure level values are
different. So
they don’t count as the same station reporting multiple times.
199.5-200.5 seems like a pretty tight range. What sort of logic to
handle
obs at multiple vertical levels were you going for?
Thanks
John Halley Gotway
On Fri, Mar 19, 2021 at 4:05 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> Fri Mar 19 16:05:19 2021: Request 99156 was acted upon.
> Transaction: Ticket created by justin.tsu at nrlmry.navy.mil
> Queue: met_help
> Subject: point_stat obs dict
> Owner: Nobody
> Requestors: justin.tsu at nrlmry.navy.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99156 >
>
>
> Hello,
>
>
>
> In the obs dictionary of the point_stat config file, I have the
following:
>
>
>
> 69 obs = {
>
> 70 field = [
>
> 71 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 72 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 73 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 74 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 75 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 76 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 77 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 78 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 79 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 80 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];}
>
> 81 ];
>
> 82 }
>
>
>
> When I specify a level of say, level=["P199.5-200.5"], what happens
in
> point_stat when it finds ONE radiosonde that has, say 10
measurements whose
> pressure levels fall within this range? Does some interpolation
occur or
> will point_stat just return 10 measurements Matched pairs?
>
>
>
> Justin
>
>
>
------------------------------------------------
Subject: point_stat obs dict
From: Tsu, Mr. Justin
Time: Mon Mar 22 13:14:18 2021
Thanks for the response John,
The way this is handled in our system is the software searches up to
25 mb above and below the significant level (so in this case it would
be 200 mb and verify searches from 175 to 225 mb). If verify cannot
find a station at exactly 200 mb, it searches in this range for the
closest measurement above AND below 200 mb. At this point, the system
will stop searching and vertically interpolate the two measurements
(above and below) to 200 mb. If either measurement (above or below)
is missing, the search will stop and the ob will not be used. Does
MET have something similar to this?
Justin
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, March 19, 2021 10:40 PM
To: Tsu, Mr. Justin <justin.tsu at nrlmry.navy.mil>
Subject: Re: [rt.rap.ucar.edu #99156] point_stat obs dict
Hi Justin,
I see you have a question about what happens when multiple vertical
level matches are found by point-stat for a particular station.
And the answer is that they will all be included in the verification.
So 10 obs within the vertical level range should result in 10 matched
pairs. If the forecast vertical level range includes model levels
above/below, the obs then the model values above/below will be
interpolated linear in the log of pressure to the pressure level of
the observation. If the forecast range includes only one model level,
no vertical interpolation is performed.
If you search for “obs_summary” on this page:
https://met.readthedocs.io/en/v9.1.3/Users_Guide/data_io.html#data-io-
met-configuration-file-options
You’ll see that that config option controls what happens a when
multiple obs are found for a station within the time window. However,
in your case, this logic wouldn’t apply since the pressure level
values are different. So they don’t count as the same station
reporting multiple times.
199.5-200.5 seems like a pretty tight range. What sort of logic to
handle obs at multiple vertical levels were you going for?
Thanks
John Halley Gotway
On Fri, Mar 19, 2021 at 4:05 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> Fri Mar 19 16:05:19 2021: Request 99156 was acted upon.
> Transaction: Ticket created by justin.tsu at nrlmry.navy.mil
> Queue: met_help
> Subject: point_stat obs dict
> Owner: Nobody
> Requestors: justin.tsu at nrlmry.navy.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99156
> >
>
>
> Hello,
>
>
>
> In the obs dictionary of the point_stat config file, I have the
following:
>
>
>
> 69 obs = {
>
> 70 field = [
>
> 71 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 72 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 73 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 74 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 75 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 76 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 77 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 78 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
>
> 79 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
>
> 80 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];}
>
> 81 ];
>
> 82 }
>
>
>
> When I specify a level of say, level=["P199.5-200.5"], what happens
in
> point_stat when it finds ONE radiosonde that has, say 10
measurements
> whose pressure levels fall within this range? Does some
interpolation
> occur or will point_stat just return 10 measurements Matched pairs?
>
>
>
> Justin
>
>
>
------------------------------------------------
Subject: point_stat obs dict
From: John Halley Gotway
Time: Mon Mar 22 20:21:01 2021
Justin,
Thanks for describing the desired approach. MET does not currently
support
that processing logic. As I mentioned before, it does include logic
for
handling multiple reports from the same station in the time window.
But it
doesn’t support that handling of multiple reports from the same
sounding
with differing vertical levels.
But I definitely see how that logic could be added to Point-Stat and
Ensmble-Stat. I’d recommend that we write up a GitHub issue to
describe
this feature request and then touch base with Tara and Liz to see
how/when
to get it done.
Tara and I are both out of the office this week on leave. But we can
follow
up next week. We’ll need to think carefully about how to implement
this.
Thanks,
John
On Mon, Mar 22, 2021 at 1:14 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99156 >
>
> Thanks for the response John,
>
> The way this is handled in our system is the software searches up to
25 mb
> above and below the significant level (so in this case it would be
200 mb
> and verify searches from 175 to 225 mb). If verify cannot find a
station
> at exactly 200 mb, it searches in this range for the closest
measurement
> above AND below 200 mb. At this point, the system will stop
searching and
> vertically interpolate the two measurements (above and below) to 200
mb.
> If either measurement (above or below) is missing, the search will
stop and
> the ob will not be used. Does MET have something similar to this?
>
>
> Justin
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, March 19, 2021 10:40 PM
> To: Tsu, Mr. Justin <justin.tsu at nrlmry.navy.mil>
> Subject: Re: [rt.rap.ucar.edu #99156] point_stat obs dict
>
> Hi Justin,
>
> I see you have a question about what happens when multiple vertical
level
> matches are found by point-stat for a particular station.
>
> And the answer is that they will all be included in the
verification. So
> 10 obs within the vertical level range should result in 10 matched
pairs.
> If the forecast vertical level range includes model levels
above/below, the
> obs then the model values above/below will be interpolated linear in
the
> log of pressure to the pressure level of the observation. If the
forecast
> range includes only one model level, no vertical interpolation is
performed.
>
> If you search for “obs_summary” on this page:
>
> https://met.readthedocs.io/en/v9.1.3/Users_Guide/data_io.html#data-
io-met-configuration-file-options
>
> You’ll see that that config option controls what happens a when
multiple
> obs are found for a station within the time window. However, in your
case,
> this logic wouldn’t apply since the pressure level values are
different. So
> they don’t count as the same station reporting multiple times.
>
> 199.5-200.5 seems like a pretty tight range. What sort of logic to
handle
> obs at multiple vertical levels were you going for?
>
> Thanks
> John Halley Gotway
>
> On Fri, Mar 19, 2021 at 4:05 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Fri Mar 19 16:05:19 2021: Request 99156 was acted upon.
> > Transaction: Ticket created by justin.tsu at nrlmry.navy.mil
> > Queue: met_help
> > Subject: point_stat obs dict
> > Owner: Nobody
> > Requestors: justin.tsu at nrlmry.navy.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99156
> > >
> >
> >
> > Hello,
> >
> >
> >
> > In the obs dictionary of the point_stat config file, I have the
> following:
> >
> >
> >
> > 69 obs = {
> >
> > 70 field = [
> >
> > 71 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 72 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 73 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 74 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 75 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 76 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 77 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 78 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 79 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 80 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];}
> >
> > 81 ];
> >
> > 82 }
> >
> >
> >
> > When I specify a level of say, level=["P199.5-200.5"], what
happens in
> > point_stat when it finds ONE radiosonde that has, say 10
measurements
> > whose pressure levels fall within this range? Does some
interpolation
> > occur or will point_stat just return 10 measurements Matched
pairs?
> >
> >
> >
> > Justin
> >
> >
> >
>
>
>
------------------------------------------------
Subject: point_stat obs dict
From: Tsu, Mr. Justin
Time: Tue Mar 23 10:22:06 2021
Thanks John,
I've forwarded this to Liz. Catch up with you next week
Justin
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Monday, March 22, 2021 7:21 PM
To: Tsu, Mr. Justin <justin.tsu at nrlmry.navy.mil>
Subject: Re: [rt.rap.ucar.edu #99156] point_stat obs dict
Justin,
Thanks for describing the desired approach. MET does not currently
support that processing logic. As I mentioned before, it does include
logic for handling multiple reports from the same station in the time
window. But it doesn’t support that handling of multiple reports from
the same sounding with differing vertical levels.
But I definitely see how that logic could be added to Point-Stat and
Ensmble-Stat. I’d recommend that we write up a GitHub issue to
describe this feature request and then touch base with Tara and Liz to
see how/when to get it done.
Tara and I are both out of the office this week on leave. But we can
follow up next week. We’ll need to think carefully about how to
implement this.
Thanks,
John
On Mon, Mar 22, 2021 at 1:14 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99156 >
>
> Thanks for the response John,
>
> The way this is handled in our system is the software searches up to
> 25 mb above and below the significant level (so in this case it
would
> be 200 mb and verify searches from 175 to 225 mb). If verify cannot
> find a station at exactly 200 mb, it searches in this range for the
> closest measurement above AND below 200 mb. At this point, the
system
> will stop searching and vertically interpolate the two measurements
(above and below) to 200 mb.
> If either measurement (above or below) is missing, the search will
> stop and the ob will not be used. Does MET have something similar
to this?
>
>
> Justin
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Friday, March 19, 2021 10:40 PM
> To: Tsu, Mr. Justin <justin.tsu at nrlmry.navy.mil>
> Subject: Re: [rt.rap.ucar.edu #99156] point_stat obs dict
>
> Hi Justin,
>
> I see you have a question about what happens when multiple vertical
> level matches are found by point-stat for a particular station.
>
> And the answer is that they will all be included in the
verification.
> So
> 10 obs within the vertical level range should result in 10 matched
pairs.
> If the forecast vertical level range includes model levels
> above/below, the obs then the model values above/below will be
> interpolated linear in the log of pressure to the pressure level of
> the observation. If the forecast range includes only one model
level, no vertical interpolation is performed.
>
> If you search for “obs_summary” on this page:
>
> https://met.readthedocs.io/en/v9.1.3/Users_Guide/data_io.html#data-
io-
> met-configuration-file-options
>
> You’ll see that that config option controls what happens a when
> multiple obs are found for a station within the time window.
However,
> in your case, this logic wouldn’t apply since the pressure level
> values are different. So they don’t count as the same station
reporting multiple times.
>
> 199.5-200.5 seems like a pretty tight range. What sort of logic to
> handle obs at multiple vertical levels were you going for?
>
> Thanks
> John Halley Gotway
>
> On Fri, Mar 19, 2021 at 4:05 PM Tsu, Mr. Justin via RT
> <met_help at ucar.edu>
> wrote:
>
> >
> > Fri Mar 19 16:05:19 2021: Request 99156 was acted upon.
> > Transaction: Ticket created by justin.tsu at nrlmry.navy.mil
> > Queue: met_help
> > Subject: point_stat obs dict
> > Owner: Nobody
> > Requestors: justin.tsu at nrlmry.navy.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99156
> > >
> >
> >
> > Hello,
> >
> >
> >
> > In the obs dictionary of the point_stat config file, I have the
> following:
> >
> >
> >
> > 69 obs = {
> >
> > 70 field = [
> >
> > 71 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 72 {name="ght";desc
> > ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
> >
> > 73 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 74 {name="ght";desc
> > ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
> >
> > 75 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 76 {name="ght";desc
> > ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
> >
> > 77 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 78 {name="ght";desc
> > ="CAPE_Nest1a0127x0127";level=["P200.0-200.0"];},
> >
> > 79 {name="t";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];},
> >
> > 80 {name="ght";desc ="CAPE_Nest1a0127x0127";level=["P200.0-
200.0"];}
> >
> > 81 ];
> >
> > 82 }
> >
> >
> >
> > When I specify a level of say, level=["P199.5-200.5"], what
happens
> > in point_stat when it finds ONE radiosonde that has, say 10
> > measurements whose pressure levels fall within this range? Does
> > some interpolation occur or will point_stat just return 10
measurements Matched pairs?
> >
> >
> >
> > Justin
> >
> >
> >
>
>
>
------------------------------------------------
More information about the Met_help
mailing list