[Met_help] [rt.rap.ucar.edu #60836] History for No matching stat lines for wind direction
John Halley Gotway via RT
met_help at ucar.edu
Fri May 24 10:28:24 MDT 2013
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi John,
I am seeing a similar error when I use stat_analysis (version 2.0) to
compute wind direction:
WARNING: do_job_aggr_stat() -> no matching STAT lines found for job: -job
aggregate_stat -fcst_thresh >= 1.000 -line_type VL1L2 -dump_row
/NWP/scratch/MET/results/aggr_stat_wdir.stat -out_line_type WDIR
I am running the command: "stat_analysis -lookin ${results_dir} -job
aggregate_stat -dump_row ${results_dir}/aggr_stat_wdir.stat -fcst_thresh
ge1.0 -line_type VL1L2 -out_line_type WDIR -v 2"
This appears to be the same issue I'm currently having with computing the
GO Index using stat_analysis. I still haven't been able to figure that one
out.
Thanks for any help,
Kiana
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60836] No matching stat lines for wind direction
From: John Halley Gotway
Time: Mon Apr 01 15:49:50 2013
Kiana,
Are you able to send me some sample data to illustrate this problem
and the GO Index problem? If you carefully describe the behavior
you're seeing, and I'm able to replicate it here, I should be able
to explain what's going on.
Here's instructions for sending us data:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 04/01/2013 03:40 PM, Kiana L Ross via RT wrote:
>
> Mon Apr 01 15:40:48 2013: Request 60836 was acted upon.
> Transaction: Ticket created by Kiana.L.Ross at aero.org
> Queue: met_help
> Subject: No matching stat lines for wind direction
> Owner: Nobody
> Requestors: Kiana.L.Ross at aero.org
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
>
> Hi John,
>
> I am seeing a similar error when I use stat_analysis (version 2.0)
to
> compute wind direction:
>
> WARNING: do_job_aggr_stat() -> no matching STAT lines found for job:
-job
> aggregate_stat -fcst_thresh >= 1.000 -line_type VL1L2 -dump_row
> /NWP/scratch/MET/results/aggr_stat_wdir.stat -out_line_type WDIR
>
> I am running the command: "stat_analysis -lookin ${results_dir} -job
> aggregate_stat -dump_row ${results_dir}/aggr_stat_wdir.stat
-fcst_thresh
> ge1.0 -line_type VL1L2 -out_line_type WDIR -v 2"
>
> This appears to be the same issue I'm currently having with
computing the
> GO Index using stat_analysis. I still haven't been able to figure
that one
> out.
>
> Thanks for any help,
> Kiana
>
------------------------------------------------
Subject: No matching stat lines for wind direction
From: Kiana L Ross
Time: Mon Apr 01 16:16:45 2013
Hi John,
Should I ftp only my .stat files? I emailed a zip folder of them to
you
last week for the GO Index, but those files don't contain VL1L2 line
types...
Thanks,
Kiana
From: "John Halley Gotway via RT" <met_help at ucar.edu>
To: Kiana.L.Ross at aero.org,
Date: 04/01/2013 02:49 PM
Subject: Re: [rt.rap.ucar.edu #60836] No matching stat lines
for
wind direction
Kiana,
Are you able to send me some sample data to illustrate this problem
and
the GO Index problem? If you carefully describe the behavior you're
seeing, and I'm able to replicate it here, I should be able
to explain what's going on.
Here's instructions for sending us data:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 04/01/2013 03:40 PM, Kiana L Ross via RT wrote:
>
> Mon Apr 01 15:40:48 2013: Request 60836 was acted upon.
> Transaction: Ticket created by Kiana.L.Ross at aero.org
> Queue: met_help
> Subject: No matching stat lines for wind direction
> Owner: Nobody
> Requestors: Kiana.L.Ross at aero.org
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
>
> Hi John,
>
> I am seeing a similar error when I use stat_analysis (version 2.0)
to
> compute wind direction:
>
> WARNING: do_job_aggr_stat() -> no matching STAT lines found for job:
-job
> aggregate_stat -fcst_thresh >= 1.000 -line_type VL1L2 -dump_row
> /NWP/scratch/MET/results/aggr_stat_wdir.stat -out_line_type WDIR
>
> I am running the command: "stat_analysis -lookin ${results_dir} -job
> aggregate_stat -dump_row ${results_dir}/aggr_stat_wdir.stat
-fcst_thresh
> ge1.0 -line_type VL1L2 -out_line_type WDIR -v 2"
>
> This appears to be the same issue I'm currently having with
computing
the
> GO Index using stat_analysis. I still haven't been able to figure
that
one
> out.
>
> Thanks for any help,
> Kiana
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60836] No matching stat lines for wind direction
From: John Halley Gotway
Time: Mon Apr 01 16:42:11 2013
Kiana,
Hmmm, I never received the zip file for the GO Index problem.
Perhaps, it was rejected by our mail system.
Could you please resend the email message, and then post the zip file
to our anonymous ftp site?
Thanks,
John
On 04/01/2013 04:16 PM, Kiana L Ross via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> Hi John,
>
> Should I ftp only my .stat files? I emailed a zip folder of them to
you
> last week for the GO Index, but those files don't contain VL1L2 line
> types...
>
> Thanks,
> Kiana
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/01/2013 02:49 PM
> Subject: Re: [rt.rap.ucar.edu #60836] No matching stat lines
for
> wind direction
>
>
>
> Kiana,
>
> Are you able to send me some sample data to illustrate this problem
and
> the GO Index problem? If you carefully describe the behavior you're
> seeing, and I'm able to replicate it here, I should be able
> to explain what's going on.
>
> Here's instructions for sending us data:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
> On 04/01/2013 03:40 PM, Kiana L Ross via RT wrote:
>>
>> Mon Apr 01 15:40:48 2013: Request 60836 was acted upon.
>> Transaction: Ticket created by Kiana.L.Ross at aero.org
>> Queue: met_help
>> Subject: No matching stat lines for wind direction
>> Owner: Nobody
>> Requestors: Kiana.L.Ross at aero.org
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>>
>>
>> Hi John,
>>
>> I am seeing a similar error when I use stat_analysis (version 2.0)
to
>> compute wind direction:
>>
>> WARNING: do_job_aggr_stat() -> no matching STAT lines found for
job:
> -job
>> aggregate_stat -fcst_thresh >= 1.000 -line_type VL1L2 -dump_row
>> /NWP/scratch/MET/results/aggr_stat_wdir.stat -out_line_type WDIR
>>
>> I am running the command: "stat_analysis -lookin ${results_dir}
-job
>> aggregate_stat -dump_row ${results_dir}/aggr_stat_wdir.stat
-fcst_thresh
>> ge1.0 -line_type VL1L2 -out_line_type WDIR -v 2"
>>
>> This appears to be the same issue I'm currently having with
computing
> the
>> GO Index using stat_analysis. I still haven't been able to figure
that
> one
>> out.
>>
>> Thanks for any help,
>> Kiana
>>
>
>
------------------------------------------------
Subject: No matching stat lines for wind direction
From: Kiana L Ross
Time: Mon Apr 01 18:06:46 2013
Hi John,
I just posted my stat files to the ftp site you indicated. The errors
I
get with both the GO Index and wind direction are from these files. It
seems like the same error in both cases: "No matching STAT lines..."
I'll forward my GO Index email sans attachment.
Thanks again,
Kiana
From: "John Halley Gotway via RT" <met_help at ucar.edu>
To: Kiana.L.Ross at aero.org,
Date: 04/01/2013 03:42 PM
Subject: Re: [rt.rap.ucar.edu #60836] No matching stat lines
for
wind direction
Kiana,
Hmmm, I never received the zip file for the GO Index problem.
Perhaps, it
was rejected by our mail system.
Could you please resend the email message, and then post the zip file
to
our anonymous ftp site?
Thanks,
John
On 04/01/2013 04:16 PM, Kiana L Ross via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> Hi John,
>
> Should I ftp only my .stat files? I emailed a zip folder of them to
you
> last week for the GO Index, but those files don't contain VL1L2 line
> types...
>
> Thanks,
> Kiana
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/01/2013 02:49 PM
> Subject: Re: [rt.rap.ucar.edu #60836] No matching stat lines
for
> wind direction
>
>
>
> Kiana,
>
> Are you able to send me some sample data to illustrate this problem
and
> the GO Index problem? If you carefully describe the behavior you're
> seeing, and I'm able to replicate it here, I should be able
> to explain what's going on.
>
> Here's instructions for sending us data:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
> On 04/01/2013 03:40 PM, Kiana L Ross via RT wrote:
>>
>> Mon Apr 01 15:40:48 2013: Request 60836 was acted upon.
>> Transaction: Ticket created by Kiana.L.Ross at aero.org
>> Queue: met_help
>> Subject: No matching stat lines for wind direction
>> Owner: Nobody
>> Requestors: Kiana.L.Ross at aero.org
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836
>
>>
>>
>> Hi John,
>>
>> I am seeing a similar error when I use stat_analysis (version 2.0)
to
>> compute wind direction:
>>
>> WARNING: do_job_aggr_stat() -> no matching STAT lines found for
job:
> -job
>> aggregate_stat -fcst_thresh >= 1.000 -line_type VL1L2 -dump_row
>> /NWP/scratch/MET/results/aggr_stat_wdir.stat -out_line_type WDIR
>>
>> I am running the command: "stat_analysis -lookin ${results_dir}
-job
>> aggregate_stat -dump_row ${results_dir}/aggr_stat_wdir.stat
-fcst_thresh
>> ge1.0 -line_type VL1L2 -out_line_type WDIR -v 2"
>>
>> This appears to be the same issue I'm currently having with
computing
> the
>> GO Index using stat_analysis. I still haven't been able to figure
that
> one
>> out.
>>
>> Thanks for any help,
>> Kiana
>>
>
>
------------------------------------------------
Subject: No matching stat lines for wind direction
From: Kiana L Ross
Time: Mon Apr 08 15:36:33 2013
Hi John,
I'm still getting the same error for computing wind direction, even
after
modifying my obs_field[] to match UGRD and VGRD at exact pressure
levels
(as opposed to ranges). The stat_analysis call I'm making is:
stat_analysis -lookin ${results_dir} -job aggregate_stat -dump_row
${results_dir}/aggr_stat_wdir.stat -fcst_thresh ge1.0 -line_type VL1L2
-out_line_type WDIR -v 2
Should I upload my latest .stat files to the location you previously
sent
me?
Thanks,
Kiana
From: "John Halley Gotway via RT" <met_help at ucar.edu>
To: Kiana.L.Ross at aero.org,
Date: 04/03/2013 08:47 AM
Subject: [rt.rap.ucar.edu #60836] Resolved: No matching stat
lines
for wind direction
According to our records, your request has been resolved. If you have
any
further questions or concerns, please respond to this message.
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching stat lines for wind direction
From: John Halley Gotway
Time: Tue Apr 09 11:08:34 2013
Kiana,
Hmmm, I'm not sure what's going on. I ran METv2.0 as originally
released and with the latest patches and wasn't able to reproduce the
problem you're seeing. My guess was that it has to do with
-fcst_thresh option, but that wasn't a problem in the data I tested.
Are you sure that there are VL1L2 lines present in the .stat files in
${results_dir}? What do you get when you remove the "-fcst_thresh
ge1.0" option from that job?
If you're still stuck, please send me some .stat files that contain
the VL1L2 lines you're trying process. Then I'll run the job you sent
using METv2.0. Is that correct?
Can can upload .stat files to our anonymous ftp site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 04/08/2013 03:36 PM, Kiana L Ross via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> Hi John,
>
> I'm still getting the same error for computing wind direction, even
after
> modifying my obs_field[] to match UGRD and VGRD at exact pressure
levels
> (as opposed to ranges). The stat_analysis call I'm making is:
>
> stat_analysis -lookin ${results_dir} -job aggregate_stat -dump_row
> ${results_dir}/aggr_stat_wdir.stat -fcst_thresh ge1.0 -line_type
VL1L2
> -out_line_type WDIR -v 2
>
> Should I upload my latest .stat files to the location you previously
sent
> me?
>
> Thanks,
> Kiana
>
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/03/2013 08:47 AM
> Subject: [rt.rap.ucar.edu #60836] Resolved: No matching stat
lines
> for wind direction
>
>
>
> According to our records, your request has been resolved. If you
have any
> further questions or concerns, please respond to this message.
>
------------------------------------------------
Subject: No matching stat lines for wind direction
From: Kiana L Ross
Time: Wed Apr 10 11:47:25 2013
John,
When I removed "-fcst_thresh ge1.0" from the command line call, the
job
completed correctly. (Although my stats are abysmal.) Does that mean
all
of my wind forecast values fell under 1 m/s? That doesn't seem to be
right
given the information in my MPR files.
Kiana
From: "John Halley Gotway via RT" <met_help at ucar.edu>
To: Kiana.L.Ross at aero.org,
Date: 04/09/2013 10:08 AM
Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching
stat
lines for wind direction
Kiana,
Hmmm, I'm not sure what's going on. I ran METv2.0 as originally
released
and with the latest patches and wasn't able to reproduce the problem
you're seeing. My guess was that it has to do with
-fcst_thresh option, but that wasn't a problem in the data I tested.
Are you sure that there are VL1L2 lines present in the .stat files in
${results_dir}? What do you get when you remove the "-fcst_thresh
ge1.0"
option from that job?
If you're still stuck, please send me some .stat files that contain
the
VL1L2 lines you're trying process. Then I'll run the job you sent
using
METv2.0. Is that correct?
Can can upload .stat files to our anonymous ftp site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 04/08/2013 03:36 PM, Kiana L Ross via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> Hi John,
>
> I'm still getting the same error for computing wind direction, even
after
> modifying my obs_field[] to match UGRD and VGRD at exact pressure
levels
> (as opposed to ranges). The stat_analysis call I'm making is:
>
> stat_analysis -lookin ${results_dir} -job aggregate_stat -dump_row
> ${results_dir}/aggr_stat_wdir.stat -fcst_thresh ge1.0 -line_type
VL1L2
> -out_line_type WDIR -v 2
>
> Should I upload my latest .stat files to the location you previously
sent
> me?
>
> Thanks,
> Kiana
>
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/03/2013 08:47 AM
> Subject: [rt.rap.ucar.edu #60836] Resolved: No matching stat
lines
> for wind direction
>
>
>
> According to our records, your request has been resolved. If you
have
any
> further questions or concerns, please respond to this message.
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching stat lines for wind direction
From: John Halley Gotway
Time: Wed Apr 10 12:23:11 2013
Kiana,
The STAT-Analysis tool filters data by the values in the header
columns in the .stat files. So the "-fcst_thresh ge1.0" option tells
STAT-Analysis to look at the FCST_THRESH column for each .stat
line it reads. If that column contains the threshold specified, use
that line in the analysis. If not, do not use the line.
I suspect that the FCST_THRESH column in the VL1L2 lines in your .stat
files contain "NA". The only way they'd contain a non-NA value would
be if you'd configured Point-Stat to apply wind speed
thresholding for the VL1L2 line. Take a look at the
"fcst_wind_thresh" entry in the Point-Stat configuration file. You
could try the following settings:
fcst_wind_thresh[] = [ "ge1.0", "ge2.0", "ge3.0", "ge4.0", "ge5.0" ];
Then rerun Point-Stat. For each VL1L2 line you were getting prior to
this change, you should now be getting 5 - one for each of the wind
speed thresholds. For example, for "ge3.0", the VL1L2 line
will contain all U/V pairs who wind speed was at least 3 m/s. Make
sense?
Then, you can rerun the STAT-Analysis job using "-fcst_thresh ge1.0",
and then run it again for ge2.0, and so on. Then you can see how the
wind direction performance changes at the wind speed increases.
Also note that Point-Stat contains a setting for the
"obs_wind_thresh". In the above example, we're only conditioning on
the forecast wind speed, but you could condition on the observation
wind
speed, or both of them.
Here's a section from the recent MET in-person tutorial on wind
direction. This is based on METv4.0, so the config file syntax
differs a bit, but overall the idea is the same:
http://www.dtcenter.org/met/users/support/OnLinePractical/OnLinePractical_213/point_stat/wind_dir.php
And slides 17-20 of this powerpoint show it too:
http://www.dtcenter.org/met/users/docs/presentations/MET_Tutorial_20130204/session3.pdf
Hope that helps.
John
On 04/10/2013 11:47 AM, Kiana L Ross via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> John,
>
> When I removed "-fcst_thresh ge1.0" from the command line call, the
job
> completed correctly. (Although my stats are abysmal.) Does that mean
all
> of my wind forecast values fell under 1 m/s? That doesn't seem to be
right
> given the information in my MPR files.
>
> Kiana
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/09/2013 10:08 AM
> Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching
stat
> lines for wind direction
>
>
>
> Kiana,
>
> Hmmm, I'm not sure what's going on. I ran METv2.0 as originally
released
> and with the latest patches and wasn't able to reproduce the problem
> you're seeing. My guess was that it has to do with
> -fcst_thresh option, but that wasn't a problem in the data I tested.
>
> Are you sure that there are VL1L2 lines present in the .stat files
in
> ${results_dir}? What do you get when you remove the "-fcst_thresh
ge1.0"
> option from that job?
>
> If you're still stuck, please send me some .stat files that contain
the
> VL1L2 lines you're trying process. Then I'll run the job you sent
using
> METv2.0. Is that correct?
>
> Can can upload .stat files to our anonymous ftp site:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
> On 04/08/2013 03:36 PM, Kiana L Ross via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>>
>> Hi John,
>>
>> I'm still getting the same error for computing wind direction, even
> after
>> modifying my obs_field[] to match UGRD and VGRD at exact pressure
levels
>> (as opposed to ranges). The stat_analysis call I'm making is:
>>
>> stat_analysis -lookin ${results_dir} -job aggregate_stat -dump_row
>> ${results_dir}/aggr_stat_wdir.stat -fcst_thresh ge1.0 -line_type
VL1L2
>> -out_line_type WDIR -v 2
>>
>> Should I upload my latest .stat files to the location you
previously
> sent
>> me?
>>
>> Thanks,
>> Kiana
>>
>>
>>
>>
>> From: "John Halley Gotway via RT" <met_help at ucar.edu>
>> To: Kiana.L.Ross at aero.org,
>> Date: 04/03/2013 08:47 AM
>> Subject: [rt.rap.ucar.edu #60836] Resolved: No matching stat
> lines
>> for wind direction
>>
>>
>>
>> According to our records, your request has been resolved. If you
have
> any
>> further questions or concerns, please respond to this message.
>>
>
>
------------------------------------------------
Subject: No matching stat lines for wind direction
From: Kiana L Ross
Time: Thu Apr 11 12:51:03 2013
Hi John,
You were right, I wasn't setting the thresholds correctly in my
PointStat
config file. I should have caught that one myself. Things look much
better
now.
Thanks also for sending the slides from the recent in-person MET
tutorial.
Those have been useful. Will another MET in-person tutorial be offered
this July?
Thanks as always,
Kiana
From: "John Halley Gotway via RT" <met_help at ucar.edu>
To: Kiana.L.Ross at aero.org,
Date: 04/10/2013 11:23 AM
Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching
stat
lines for wind direction
Kiana,
The STAT-Analysis tool filters data by the values in the header
columns in
the .stat files. So the "-fcst_thresh ge1.0" option tells STAT-
Analysis
to look at the FCST_THRESH column for each .stat
line it reads. If that column contains the threshold specified, use
that
line in the analysis. If not, do not use the line.
I suspect that the FCST_THRESH column in the VL1L2 lines in your .stat
files contain "NA". The only way they'd contain a non-NA value would
be
if you'd configured Point-Stat to apply wind speed
thresholding for the VL1L2 line. Take a look at the
"fcst_wind_thresh"
entry in the Point-Stat configuration file. You could try the
following
settings:
fcst_wind_thresh[] = [ "ge1.0", "ge2.0", "ge3.0", "ge4.0", "ge5.0" ];
Then rerun Point-Stat. For each VL1L2 line you were getting prior to
this
change, you should now be getting 5 - one for each of the wind speed
thresholds. For example, for "ge3.0", the VL1L2 line
will contain all U/V pairs who wind speed was at least 3 m/s. Make
sense?
Then, you can rerun the STAT-Analysis job using "-fcst_thresh ge1.0",
and
then run it again for ge2.0, and so on. Then you can see how the wind
direction performance changes at the wind speed increases.
Also note that Point-Stat contains a setting for the
"obs_wind_thresh". In
the above example, we're only conditioning on the forecast wind speed,
but
you could condition on the observation wind
speed, or both of them.
Here's a section from the recent MET in-person tutorial on wind
direction.
This is based on METv4.0, so the config file syntax differs a bit,
but
overall the idea is the same:
http://www.dtcenter.org/met/users/support/OnLinePractical/OnLinePractical_213/point_stat/wind_dir.php
And slides 17-20 of this powerpoint show it too:
http://www.dtcenter.org/met/users/docs/presentations/MET_Tutorial_20130204/session3.pdf
Hope that helps.
John
On 04/10/2013 11:47 AM, Kiana L Ross via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> John,
>
> When I removed "-fcst_thresh ge1.0" from the command line call, the
job
> completed correctly. (Although my stats are abysmal.) Does that mean
all
> of my wind forecast values fell under 1 m/s? That doesn't seem to be
right
> given the information in my MPR files.
>
> Kiana
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/09/2013 10:08 AM
> Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching
stat
> lines for wind direction
>
>
>
> Kiana,
>
> Hmmm, I'm not sure what's going on. I ran METv2.0 as originally
released
> and with the latest patches and wasn't able to reproduce the problem
> you're seeing. My guess was that it has to do with
> -fcst_thresh option, but that wasn't a problem in the data I tested.
>
> Are you sure that there are VL1L2 lines present in the .stat files
in
> ${results_dir}? What do you get when you remove the "-fcst_thresh
ge1.0"
> option from that job?
>
> If you're still stuck, please send me some .stat files that contain
the
> VL1L2 lines you're trying process. Then I'll run the job you sent
using
> METv2.0. Is that correct?
>
> Can can upload .stat files to our anonymous ftp site:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
> On 04/08/2013 03:36 PM, Kiana L Ross via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>>
>> Hi John,
>>
>> I'm still getting the same error for computing wind direction, even
> after
>> modifying my obs_field[] to match UGRD and VGRD at exact pressure
levels
>> (as opposed to ranges). The stat_analysis call I'm making is:
>>
>> stat_analysis -lookin ${results_dir} -job aggregate_stat -dump_row
>> ${results_dir}/aggr_stat_wdir.stat -fcst_thresh ge1.0 -line_type
VL1L2
>> -out_line_type WDIR -v 2
>>
>> Should I upload my latest .stat files to the location you
previously
> sent
>> me?
>>
>> Thanks,
>> Kiana
>>
>>
>>
>>
>> From: "John Halley Gotway via RT" <met_help at ucar.edu>
>> To: Kiana.L.Ross at aero.org,
>> Date: 04/03/2013 08:47 AM
>> Subject: [rt.rap.ucar.edu #60836] Resolved: No matching stat
> lines
>> for wind direction
>>
>>
>>
>> According to our records, your request has been resolved. If you
have
> any
>> further questions or concerns, please respond to this message.
>>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching stat lines for wind direction
From: John Halley Gotway
Time: Thu Apr 11 13:13:19 2013
Kiana,
Great - glad you were able to work that out. Unfortunately no, we
won't be having an in-person tutorial in July. It likely will be next
January. At our current funding level, we're only able to afford one
per year. However, we will be updating the online tutorial shortly
after the upcoming METv4.1 release.
Thanks,
John
On 2013-04-11 12:51, Kiana L Ross via RT wrote:
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>
> Hi John,
>
> You were right, I wasn't setting the thresholds correctly in my
> PointStat
> config file. I should have caught that one myself. Things look much
> better
> now.
>
> Thanks also for sending the slides from the recent in-person MET
> tutorial.
> Those have been useful. Will another MET in-person tutorial be
> offered
> this July?
>
> Thanks as always,
> Kiana
>
>
>
> From: "John Halley Gotway via RT" <met_help at ucar.edu>
> To: Kiana.L.Ross at aero.org,
> Date: 04/10/2013 11:23 AM
> Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching
> stat
> lines for wind direction
>
>
>
> Kiana,
>
> The STAT-Analysis tool filters data by the values in the header
> columns in
> the .stat files. So the "-fcst_thresh ge1.0" option tells
> STAT-Analysis
> to look at the FCST_THRESH column for each .stat
> line it reads. If that column contains the threshold specified, use
> that
> line in the analysis. If not, do not use the line.
>
> I suspect that the FCST_THRESH column in the VL1L2 lines in your
> .stat
> files contain "NA". The only way they'd contain a non-NA value
would
> be
> if you'd configured Point-Stat to apply wind speed
> thresholding for the VL1L2 line. Take a look at the
> "fcst_wind_thresh"
> entry in the Point-Stat configuration file. You could try the
> following
> settings:
>
> fcst_wind_thresh[] = [ "ge1.0", "ge2.0", "ge3.0", "ge4.0", "ge5.0"
];
>
> Then rerun Point-Stat. For each VL1L2 line you were getting prior
to
> this
> change, you should now be getting 5 - one for each of the wind speed
> thresholds. For example, for "ge3.0", the VL1L2 line
> will contain all U/V pairs who wind speed was at least 3 m/s. Make
> sense?
>
> Then, you can rerun the STAT-Analysis job using "-fcst_thresh
ge1.0",
> and
> then run it again for ge2.0, and so on. Then you can see how the
> wind
> direction performance changes at the wind speed increases.
>
> Also note that Point-Stat contains a setting for the
> "obs_wind_thresh". In
> the above example, we're only conditioning on the forecast wind
> speed, but
> you could condition on the observation wind
> speed, or both of them.
>
> Here's a section from the recent MET in-person tutorial on wind
> direction.
> This is based on METv4.0, so the config file syntax differs a bit,
> but
> overall the idea is the same:
>
>
>
http://www.dtcenter.org/met/users/support/OnLinePractical/OnLinePractical_213/point_stat/wind_dir.php
>
>
> And slides 17-20 of this powerpoint show it too:
>
>
>
http://www.dtcenter.org/met/users/docs/presentations/MET_Tutorial_20130204/session3.pdf
>
>
> Hope that helps.
>
> John
>
> On 04/10/2013 11:47 AM, Kiana L Ross via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>>
>> John,
>>
>> When I removed "-fcst_thresh ge1.0" from the command line call, the
>> job
>> completed correctly. (Although my stats are abysmal.) Does that
mean
>> all
>> of my wind forecast values fell under 1 m/s? That doesn't seem to
be
> right
>> given the information in my MPR files.
>>
>> Kiana
>>
>>
>>
>> From: "John Halley Gotway via RT" <met_help at ucar.edu>
>> To: Kiana.L.Ross at aero.org,
>> Date: 04/09/2013 10:08 AM
>> Subject: Re: [rt.rap.ucar.edu #60836] Resolved: No matching
>> stat
>> lines for wind direction
>>
>>
>>
>> Kiana,
>>
>> Hmmm, I'm not sure what's going on. I ran METv2.0 as originally
> released
>> and with the latest patches and wasn't able to reproduce the
problem
>> you're seeing. My guess was that it has to do with
>> -fcst_thresh option, but that wasn't a problem in the data I
tested.
>>
>> Are you sure that there are VL1L2 lines present in the .stat files
>> in
>> ${results_dir}? What do you get when you remove the "-fcst_thresh
> ge1.0"
>> option from that job?
>>
>> If you're still stuck, please send me some .stat files that contain
>> the
>> VL1L2 lines you're trying process. Then I'll run the job you sent
>> using
>> METv2.0. Is that correct?
>>
>> Can can upload .stat files to our anonymous ftp site:
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>
>> Thanks,
>> John
>>
>> On 04/08/2013 03:36 PM, Kiana L Ross via RT wrote:
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60836 >
>>>
>>> Hi John,
>>>
>>> I'm still getting the same error for computing wind direction,
even
>> after
>>> modifying my obs_field[] to match UGRD and VGRD at exact pressure
> levels
>>> (as opposed to ranges). The stat_analysis call I'm making is:
>>>
>>> stat_analysis -lookin ${results_dir} -job aggregate_stat -dump_row
>>> ${results_dir}/aggr_stat_wdir.stat -fcst_thresh ge1.0 -line_type
>>> VL1L2
>>> -out_line_type WDIR -v 2
>>>
>>> Should I upload my latest .stat files to the location you
>>> previously
>> sent
>>> me?
>>>
>>> Thanks,
>>> Kiana
>>>
>>>
>>>
>>>
>>> From: "John Halley Gotway via RT" <met_help at ucar.edu>
>>> To: Kiana.L.Ross at aero.org,
>>> Date: 04/03/2013 08:47 AM
>>> Subject: [rt.rap.ucar.edu #60836] Resolved: No matching
stat
>> lines
>>> for wind direction
>>>
>>>
>>>
>>> According to our records, your request has been resolved. If you
>>> have
>> any
>>> further questions or concerns, please respond to this message.
>>>
>>
>>
------------------------------------------------
More information about the Met_help
mailing list