[Met_help] [rt.rap.ucar.edu #67290] History for a question about ‘point_stat' tool
John Halley Gotway via RT
met_help at ucar.edu
Wed May 28 09:23:26 MDT 2014
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear Professor,
I have a question about ‘point_stat' tool. In the configurable items for point-stat, set
output_flag = {
fho = NONE;
ctc = BOTH;
cts = BOTH;
mctc = NONE;
mcts = NONE;
cnt = BOTH;
sl1l2 = NONE;
sal1l2 = NONE;
vl1l2 = NONE;
val1l2 = NONE;
pct = NONE;
pstd = NONE;
pjc = NONE;
prc = NONE;
mpr = BOTH;
};
After run it, I find the OBS_VALID_BEG is 20140320_110000 in the result file named ‘point_stat_APCP_24_240000L_20140320_110000V_mpr’, and it is right. But the OBS_VALID_BEG is 20140320_093000 in the file named ‘point_stat_APCP_24_240000L_20140320_110000V_cnt’, it is strange, could you tell me why.
I have posted the scripts and data to the ftp site. The folder is /met_help/qiu
Look forward to your feedbacks.Your help is highly appreciated.
Thanks,
Crystal
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #67290] a question about ‘point_stat' tool
From: John Halley Gotway
Time: Tue May 27 10:20:29 2014
Crystal,
Yes that's correct. The times listed in the OBS_VALID_BEG and
OBS_VALID_END columns differ between the matched pair lines (MPR) and
the other line types (like CNT, CTS, and so on). And there's a
good reason for that.
When you run Point-Stat, you're comparing gridded fields that are
valid a single point in time to point observations. Rather than
requiring the point observations to have *exactly* the same valid
time as the forecast, the user can define a matching time window
around the forecast valid time. Any observations who time falls
within that window are used. This is set in the config file using
"obs_window" and is specified in seconds. For example, this is a time
window of +/- 1.5 hours:
obs_window = {
beg = -5400;
end = 5400;
}
Continuous statistics (CNT line type) or categorical statistics (CTS
line type) are computed over all the matched pairs. The observations
used to compute CNT and CTS lines may have fallen before the
forecast valid time, some after, and perhaps some at the exact same
time. So the OBS_VALID_BEG and OBS_VALID_END columns for those line
types list the matching time window that was used since the
observations may have fallen anywhere in that range.
However, the matched pair line type (MPR) contains information for
single observation values. Those single observations are valid at a
specific time. We could have chosen to list the matching time
window, as we did for the CNT and CTS line types, but we figured it
would be more useful to list the exact valid time for that observation
value.
So that's why they differ. The times in the MPR line type are the
exact valid time for that observation value while the times in the
other line types indicate the matching time window as defined in
the config file.
Hope that helps clarify.
Thanks,
John Halley Gotway
met_help at ucar.edu
On 05/25/2014 07:20 AM, Crystal via RT wrote:
>
> Sun May 25 07:20:16 2014: Request 67290 was acted upon.
> Transaction: Ticket created by jinjing_qiu at 163.com
> Queue: met_help
> Subject: a question about ‘point_stat' tool
> Owner: Nobody
> Requestors: jinjing_qiu at 163.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67290 >
>
>
> Dear Professor,
>
>
>
> I have a question about ‘point_stat' tool. In the configurable
items for point-stat, set
>
> output_flag = {
>
> fho = NONE;
>
> ctc = BOTH;
>
> cts = BOTH;
>
> mctc = NONE;
>
> mcts = NONE;
>
> cnt = BOTH;
>
> sl1l2 = NONE;
>
> sal1l2 = NONE;
>
> vl1l2 = NONE;
>
> val1l2 = NONE;
>
> pct = NONE;
>
> pstd = NONE;
>
> pjc = NONE;
>
> prc = NONE;
>
> mpr = BOTH;
>
> };
>
> After run it, I find the OBS_VALID_BEG is 20140320_110000 in the
result file named ‘point_stat_APCP_24_240000L_20140320_110000V_mpr’,
and it is right. But the OBS_VALID_BEG is 20140320_093000 in the file
named ‘point_stat_APCP_24_240000L_20140320_110000V_cnt’, it is
strange, could you tell me why.
>
> I have posted the scripts and data to the ftp site. The folder is
/met_help/qiu
>
> Look forward to your feedbacks.Your help is highly appreciated.
>
> Thanks,
>
> Crystal
>
------------------------------------------------
Subject: a question about ‘point_stat' tool
From: Crystal
Time: Tue May 27 19:50:56 2014
Dear Professor,
I have solved the problem with your kind help!
Thanks very much!
Crystal
At 2014-05-28 00:20:29,"John Halley Gotway via RT" <met_help at ucar.edu>
wrote:
>Crystal,
>
>Yes that's correct. The times listed in the OBS_VALID_BEG and
OBS_VALID_END columns differ between the matched pair lines (MPR) and
the other line types (like CNT, CTS, and so on). And there's a
>good reason for that.
>
>When you run Point-Stat, you're comparing gridded fields that are
valid a single point in time to point observations. Rather than
requiring the point observations to have *exactly* the same valid
>time as the forecast, the user can define a matching time window
around the forecast valid time. Any observations who time falls
within that window are used. This is set in the config file using
>"obs_window" and is specified in seconds. For example, this is a
time window of +/- 1.5 hours:
> obs_window = {
> beg = -5400;
> end = 5400;
> }
>
>Continuous statistics (CNT line type) or categorical statistics (CTS
line type) are computed over all the matched pairs. The observations
used to compute CNT and CTS lines may have fallen before the
>forecast valid time, some after, and perhaps some at the exact same
time. So the OBS_VALID_BEG and OBS_VALID_END columns for those line
types list the matching time window that was used since the
>observations may have fallen anywhere in that range.
>
>However, the matched pair line type (MPR) contains information for
single observation values. Those single observations are valid at a
specific time. We could have chosen to list the matching time
>window, as we did for the CNT and CTS line types, but we figured it
would be more useful to list the exact valid time for that observation
value.
>
>So that's why they differ. The times in the MPR line type are the
exact valid time for that observation value while the times in the
other line types indicate the matching time window as defined in
>the config file.
>
>Hope that helps clarify.
>
>Thanks,
>John Halley Gotway
>met_help at ucar.edu
>
>
>On 05/25/2014 07:20 AM, Crystal via RT wrote:
>>
>> Sun May 25 07:20:16 2014: Request 67290 was acted upon.
>> Transaction: Ticket created by jinjing_qiu at 163.com
>> Queue: met_help
>> Subject: a question about ‘point_stat' tool
>> Owner: Nobody
>> Requestors: jinjing_qiu at 163.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67290 >
>>
>>
>> Dear Professor,
>>
>>
>>
>> I have a question about ‘point_stat' tool. In the configurable
items for point-stat, set
>>
>> output_flag = {
>>
>> fho = NONE;
>>
>> ctc = BOTH;
>>
>> cts = BOTH;
>>
>> mctc = NONE;
>>
>> mcts = NONE;
>>
>> cnt = BOTH;
>>
>> sl1l2 = NONE;
>>
>> sal1l2 = NONE;
>>
>> vl1l2 = NONE;
>>
>> val1l2 = NONE;
>>
>> pct = NONE;
>>
>> pstd = NONE;
>>
>> pjc = NONE;
>>
>> prc = NONE;
>>
>> mpr = BOTH;
>>
>> };
>>
>> After run it, I find the OBS_VALID_BEG is 20140320_110000 in the
result file named ‘point_stat_APCP_24_240000L_20140320_110000V_mpr’,
and it is right. But the OBS_VALID_BEG is 20140320_093000 in the file
named ‘point_stat_APCP_24_240000L_20140320_110000V_cnt’, it is
strange, could you tell me why.
>>
>> I have posted the scripts and data to the ftp site. The folder is
/met_help/qiu
>>
>> Look forward to your feedbacks.Your help is highly appreciated.
>>
>> Thanks,
>>
>> Crystal
>>
>
------------------------------------------------
More information about the Met_help
mailing list