[Met_help] [rt.rap.ucar.edu #96724] History for Help with MET tools: Retaining individual station statistics
John Halley Gotway via RT
met_help at ucar.edu
Wed Sep 16 12:48:36 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I am using point_stat to generate statistics for WRF model performance. the *.stat files save the aggregated/accumulated stats, but how does one save the information for each station used in the analysis? For example, I'd like to know what the MAE and BIAS was for individual stations, and have that information retained rather than just for all the stations. Is that possible with MET tool?
Thanks,
A.J. Eiserloh - Data Scientist
PG&E - Meteorology Operations & Analytics
Applied Technology Services
3400 Crow Canyon Rd., San Ramon, CA 94583-1393
925-307-4492
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Help with MET tools: Retaining individual station statistics
From: Julie Prestopnik
Time: Tue Sep 15 14:21:45 2020
Hi A.J.
I see that you have a question about point_stat. I have assigned your
ticket to John. Please allow a few business days for a response.
Julie
On Tue, Sep 15, 2020 at 1:20 PM Eiserloh Jr., A.J. via RT
<met_help at ucar.edu>
wrote:
>
> Tue Sep 15 13:20:48 2020: Request 96724 was acted upon.
> Transaction: Ticket created by AJEB at pge.com
> Queue: met_help
> Subject: Help with MET tools: Retaining individual station
statistics
> Owner: Nobody
> Requestors: AJEB at pge.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96724 >
>
>
> Hello,
>
> I am using point_stat to generate statistics for WRF model
performance.
> the *.stat files save the aggregated/accumulated stats, but how does
one
> save the information for each station used in the analysis? For
example,
> I'd like to know what the MAE and BIAS was for individual stations,
and
> have that information retained rather than just for all the
stations. Is
> that possible with MET tool?
>
> Thanks,
>
> A.J. Eiserloh - Data Scientist
> PG&E - Meteorology Operations & Analytics
> Applied Technology Services
> 3400 Crow Canyon Rd., San Ramon, CA 94583-1393
> 925-307-4492
>
>
>
--
Julie Prestopnik (she/her/hers)
Software Engineer
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
My working day may not be your working day. Please do not feel
obliged to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: Help with MET tools: Retaining individual station statistics
From: John Halley Gotway
Time: Tue Sep 15 14:34:08 2020
A.J.,
I see that you're running MET's point-stat tool and are interested in
the
pairs for each station. We call each fcst/obs pair a "matched pair"
and
those can be written to the output using the MPR line type. In the
Point-Stat config file, just turn on that "mpr" line type in the
"output_flag" setting.
Setting "mpr = STAT;" will cause 1 line to be written to the output
.stat
file for each matched pair.
Setting "mpr = BOTH;" will write them to both the .stat file and also
a
"*_mpr.txt" file.
Using BOTH essentially doubles the output. So I'd recommend using
STAT, if
possible.
Also be aware that if you have many, many observations, the output
could get quite large. Storing this type of data in ASCII format makes
it
easy for a human to read and process, but really isn't very efficient.
Here's a table which describes the contents of each MPR line:
https://dtcenter.github.io/MET/Users_Guide/point-stat.html#id24
If you find the output is too large and you're only interested in a
few
stations, you could specify those using the "mask.sid" option (sid =
station id's) in the Point-Stat config files.
So you still run Point-Stat once for each model output time and write
MPR
output to the .stat files. But then you can run the Stat-Analysis tool
to
aggregate those MPR lines over many cases and compute statistics
separately
for each station. The example command below reads MPR lines and for
each
unique combination of forecast lead time and station id, it compute
continuous statistics, like RMSE:
stat_analysis -lookin out/point_stat -job aggregate_stat -line_type
MPR
-out_line_type CNT -by FCST_VAR,FCST_LEAD,OBS_SID -out_stat
mpr_to_cnt_by_sid.stat
That should write an output file named mpr_to_cnt_by_sid.stat which
contains CNT lines... one for each unique combination of forecast
variable,
lead time, and observation station id.
Hope that helps explain the process.
Thanks,
John
On Tue, Sep 15, 2020 at 2:21 PM Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96724 >
>
> Hi A.J.
>
> I see that you have a question about point_stat. I have assigned
your
> ticket to John. Please allow a few business days for a response.
>
> Julie
>
> On Tue, Sep 15, 2020 at 1:20 PM Eiserloh Jr., A.J. via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Tue Sep 15 13:20:48 2020: Request 96724 was acted upon.
> > Transaction: Ticket created by AJEB at pge.com
> > Queue: met_help
> > Subject: Help with MET tools: Retaining individual station
> statistics
> > Owner: Nobody
> > Requestors: AJEB at pge.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96724 >
> >
> >
> > Hello,
> >
> > I am using point_stat to generate statistics for WRF model
performance.
> > the *.stat files save the aggregated/accumulated stats, but how
does one
> > save the information for each station used in the analysis? For
example,
> > I'd like to know what the MAE and BIAS was for individual
stations, and
> > have that information retained rather than just for all the
stations. Is
> > that possible with MET tool?
> >
> > Thanks,
> >
> > A.J. Eiserloh - Data Scientist
> > PG&E - Meteorology Operations & Analytics
> > Applied Technology Services
> > 3400 Crow Canyon Rd., San Ramon, CA 94583-1393
> > 925-307-4492
> >
> >
> >
>
> --
> Julie Prestopnik (she/her/hers)
> Software Engineer
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #96724] Help with MET tools: Retaining individual station statistics
From: Eiserloh Jr., A.J.
Time: Wed Sep 16 09:23:23 2020
Hi John,
Thanks for the quick reply. That is very helpful. I also have another
question on ascii2nc tool. I'm using that to convert my obs values to
.netcdf. Table 4.4 of the v8.1 user guide shows the values of what
should be in the columns for ascii2nc. I have a specific question
about the height and elevation of the observation (column 9). I want
to make sure I am putting in those values correctly and that I
understand it. For example, if I have a station that has elevation =
500 m asl, and my observation height is 10-m above ground, then what
should my value for column 9 be? Should it be 10 m agl or 510 m asl
?
Thanks,
A.J.
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Tuesday, September 15, 2020 1:34 PM
To: Eiserloh Jr., A.J. <AJEB at pge.com>
Subject: Re: [rt.rap.ucar.edu #96724] Help with MET tools: Retaining
individual station statistics
*****CAUTION: This email was sent from an EXTERNAL source. Think
before clicking links or opening attachments.*****
A.J.,
I see that you're running MET's point-stat tool and are interested in
the pairs for each station. We call each fcst/obs pair a "matched
pair" and those can be written to the output using the MPR line type.
In the Point-Stat config file, just turn on that "mpr" line type in
the "output_flag" setting.
Setting "mpr = STAT;" will cause 1 line to be written to the output
.stat file for each matched pair.
Setting "mpr = BOTH;" will write them to both the .stat file and also
a "*_mpr.txt" file.
Using BOTH essentially doubles the output. So I'd recommend using
STAT, if possible.
Also be aware that if you have many, many observations, the output
could get quite large. Storing this type of data in ASCII format makes
it easy for a human to read and process, but really isn't very
efficient.
Here's a table which describes the contents of each MPR line:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdtcenter.github.io%2FMET%2FUsers_Guide%2Fpoint-
stat.html%23id24&data=02%7C01%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661aece641aabc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=MWdUqlLmgram76EbaWkJyQfrFUM%2BXXZUytyt8Kh4jc4%3D&reserved=0
If you find the output is too large and you're only interested in a
few stations, you could specify those using the "mask.sid" option (sid
= station id's) in the Point-Stat config files.
So you still run Point-Stat once for each model output time and write
MPR output to the .stat files. But then you can run the Stat-Analysis
tool to aggregate those MPR lines over many cases and compute
statistics separately for each station. The example command below
reads MPR lines and for each unique combination of forecast lead time
and station id, it compute continuous statistics, like RMSE:
stat_analysis -lookin out/point_stat -job aggregate_stat -line_type
MPR -out_line_type CNT -by FCST_VAR,FCST_LEAD,OBS_SID -out_stat
mpr_to_cnt_by_sid.stat
That should write an output file named mpr_to_cnt_by_sid.stat which
contains CNT lines... one for each unique combination of forecast
variable, lead time, and observation station id.
Hope that helps explain the process.
Thanks,
John
On Tue, Sep 15, 2020 at 2:21 PM Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
>
> <URL:
>
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt.r
>
ap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=02%7C01
>
%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661aece641a
>
abc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=kgm99wqjSWVDS
> QK1T8WcQZcAgnozmpmL%2Fhh3arVV5cI%3D&reserved=0 >
>
> Hi A.J.
>
> I see that you have a question about point_stat. I have assigned
your
> ticket to John. Please allow a few business days for a response.
>
> Julie
>
> On Tue, Sep 15, 2020 at 1:20 PM Eiserloh Jr., A.J. via RT <
> met_help at ucar.edu>
> wrote:
>
> >
> > Tue Sep 15 13:20:48 2020: Request 96724 was acted upon.
> > Transaction: Ticket created by AJEB at pge.com
> > Queue: met_help
> > Subject: Help with MET tools: Retaining individual station
> statistics
> > Owner: Nobody
> > Requestors: AJEB at pge.com
> > Status: new
> > Ticket <URL:
> >
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt
> >
.rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=02%
> >
7C01%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661ae
> >
ce641aabc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=kgm99
> > wqjSWVDSQK1T8WcQZcAgnozmpmL%2Fhh3arVV5cI%3D&reserved=0 >
> >
> >
> > Hello,
> >
> > I am using point_stat to generate statistics for WRF model
performance.
> > the *.stat files save the aggregated/accumulated stats, but how
does
> > one save the information for each station used in the analysis?
For
> > example, I'd like to know what the MAE and BIAS was for individual
> > stations, and have that information retained rather than just for
> > all the stations. Is that possible with MET tool?
> >
> > Thanks,
> >
> > A.J. Eiserloh - Data Scientist
> > PG&E - Meteorology Operations & Analytics Applied Technology
> > Services
> > 3400 Crow Canyon Rd., San Ramon, CA 94583-1393
> > 925-307-4492
> >
> >
> >
>
> --
> Julie Prestopnik (she/her/hers)
> Software Engineer
> National Center for Atmospheric Research Research Applications
> Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
> My working day may not be your working day. Please do not feel
> obliged to reply to this email outside of your normal working hours.
>
>
------------------------------------------------
Subject: Help with MET tools: Retaining individual station statistics
From: John Halley Gotway
Time: Wed Sep 16 10:15:56 2020
A.J.,
"For example, if I have a station that has elevation = 500 m asl, and
my
observation height is 10-m above ground, then what should my value for
column 9 be? Should it be 10 m agl or 510 m asl ?"
I would recommend setting elevation = 500 m ASL, and height = 10 m
AGL.
MET does not include logic to differentiate between ASL and AGL
directly.
Instead, we just want to make sure the observation heights are
consistent
with the height conventions used by the model. For example, models
typically output winds at 10-m AGL... not winds for 510 ASL. So you
should
make the 10-m observation height consistent with the 10-m AGL from the
model so that they can easily be compared.
MET doesn't actually use the station elevation very much. For numeric
entries which are unknown, just fill them with a bad data value of
-9999.
Thanks,
John
On Wed, Sep 16, 2020 at 9:23 AM Eiserloh Jr., A.J. via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96724 >
>
> Hi John,
>
> Thanks for the quick reply. That is very helpful. I also have
another
> question on ascii2nc tool. I'm using that to convert my obs values
to
> .netcdf. Table 4.4 of the v8.1 user guide shows the values of what
should
> be in the columns for ascii2nc. I have a specific question about
the
> height and elevation of the observation (column 9). I want to make
sure I
> am putting in those values correctly and that I understand it. For
example,
> if I have a station that has elevation = 500 m asl, and my
observation
> height is 10-m above ground, then what should my value for column 9
be?
> Should it be 10 m agl or 510 m asl ?
>
> Thanks,
> A.J.
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Tuesday, September 15, 2020 1:34 PM
> To: Eiserloh Jr., A.J. <AJEB at pge.com>
> Subject: Re: [rt.rap.ucar.edu #96724] Help with MET tools: Retaining
> individual station statistics
>
> *****CAUTION: This email was sent from an EXTERNAL source. Think
before
> clicking links or opening attachments.*****
>
> A.J.,
>
> I see that you're running MET's point-stat tool and are interested
in the
> pairs for each station. We call each fcst/obs pair a "matched pair"
and
> those can be written to the output using the MPR line type. In the
> Point-Stat config file, just turn on that "mpr" line type in the
> "output_flag" setting.
>
> Setting "mpr = STAT;" will cause 1 line to be written to the output
.stat
> file for each matched pair.
> Setting "mpr = BOTH;" will write them to both the .stat file and
also a
> "*_mpr.txt" file.
> Using BOTH essentially doubles the output. So I'd recommend using
STAT, if
> possible.
>
> Also be aware that if you have many, many observations, the output
could
> get quite large. Storing this type of data in ASCII format makes it
easy
> for a human to read and process, but really isn't very efficient.
> Here's a table which describes the contents of each MPR line:
>
>
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdtcenter.github.io%2FMET%2FUsers_Guide%2Fpoint-
stat.html%23id24&data=02%7C01%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661aece641aabc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=MWdUqlLmgram76EbaWkJyQfrFUM%2BXXZUytyt8Kh4jc4%3D&reserved=0
>
> If you find the output is too large and you're only interested in a
few
> stations, you could specify those using the "mask.sid" option (sid =
> station id's) in the Point-Stat config files.
>
> So you still run Point-Stat once for each model output time and
write MPR
> output to the .stat files. But then you can run the Stat-Analysis
tool to
> aggregate those MPR lines over many cases and compute statistics
separately
> for each station. The example command below reads MPR lines and for
each
> unique combination of forecast lead time and station id, it compute
> continuous statistics, like RMSE:
>
> stat_analysis -lookin out/point_stat -job aggregate_stat -line_type
MPR
> -out_line_type CNT -by FCST_VAR,FCST_LEAD,OBS_SID -out_stat
> mpr_to_cnt_by_sid.stat
>
> That should write an output file named mpr_to_cnt_by_sid.stat which
> contains CNT lines... one for each unique combination of forecast
variable,
> lead time, and observation station id.
>
> Hope that helps explain the process.
>
> Thanks,
> John
>
> On Tue, Sep 15, 2020 at 2:21 PM Julie Prestopnik via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL:
> >
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt.r
> >
ap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=02%7C01
> >
%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661aece641a
> >
abc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=kgm99wqjSWVDS
> > QK1T8WcQZcAgnozmpmL%2Fhh3arVV5cI%3D&reserved=0 >
> >
> > Hi A.J.
> >
> > I see that you have a question about point_stat. I have assigned
your
> > ticket to John. Please allow a few business days for a response.
> >
> > Julie
> >
> > On Tue, Sep 15, 2020 at 1:20 PM Eiserloh Jr., A.J. via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Tue Sep 15 13:20:48 2020: Request 96724 was acted upon.
> > > Transaction: Ticket created by AJEB at pge.com
> > > Queue: met_help
> > > Subject: Help with MET tools: Retaining individual station
> > statistics
> > > Owner: Nobody
> > > Requestors: AJEB at pge.com
> > > Status: new
> > > Ticket <URL:
> > >
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt
> > >
.rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=02%
> > >
7C01%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661ae
> > >
ce641aabc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=kgm99
> > > wqjSWVDSQK1T8WcQZcAgnozmpmL%2Fhh3arVV5cI%3D&reserved=0 >
> > >
> > >
> > > Hello,
> > >
> > > I am using point_stat to generate statistics for WRF model
performance.
> > > the *.stat files save the aggregated/accumulated stats, but how
does
> > > one save the information for each station used in the analysis?
For
> > > example, I'd like to know what the MAE and BIAS was for
individual
> > > stations, and have that information retained rather than just
for
> > > all the stations. Is that possible with MET tool?
> > >
> > > Thanks,
> > >
> > > A.J. Eiserloh - Data Scientist
> > > PG&E - Meteorology Operations & Analytics Applied Technology
> > > Services
> > > 3400 Crow Canyon Rd., San Ramon, CA 94583-1393
> > > 925-307-4492
> > >
> > >
> > >
> >
> > --
> > Julie Prestopnik (she/her/hers)
> > Software Engineer
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
> > obliged to reply to this email outside of your normal working
hours.
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #96724] Help with MET tools: Retaining individual station statistics
From: Eiserloh Jr., A.J.
Time: Wed Sep 16 11:54:10 2020
Thanks John!
-AJ
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Wednesday, September 16, 2020 9:16 AM
To: Eiserloh Jr., A.J. <AJEB at pge.com>
Subject: Re: [rt.rap.ucar.edu #96724] Help with MET tools: Retaining
individual station statistics
*****CAUTION: This email was sent from an EXTERNAL source. Think
before clicking links or opening attachments.*****
A.J.,
"For example, if I have a station that has elevation = 500 m asl, and
my observation height is 10-m above ground, then what should my value
for
column 9 be? Should it be 10 m agl or 510 m asl ?"
I would recommend setting elevation = 500 m ASL, and height = 10 m
AGL.
MET does not include logic to differentiate between ASL and AGL
directly.
Instead, we just want to make sure the observation heights are
consistent with the height conventions used by the model. For example,
models typically output winds at 10-m AGL... not winds for 510 ASL. So
you should make the 10-m observation height consistent with the 10-m
AGL from the model so that they can easily be compared.
MET doesn't actually use the station elevation very much. For numeric
entries which are unknown, just fill them with a bad data value of
-9999.
Thanks,
John
On Wed, Sep 16, 2020 at 9:23 AM Eiserloh Jr., A.J. via RT
<met_help at ucar.edu>
wrote:
>
> <URL:
>
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt.r
>
ap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=02%7C01
>
%7CAJEB%40pge.com%7C31830efafd114669774308d85a5bcc5c%7C44ae661aece641a
>
abc967c2c85a08941%7C0%7C0%7C637358697719759234&sdata=2LJEVpPgXqRny
> %2BqeKJpUYaQkCPBT4YhkPYcHRhdy8To%3D&reserved=0 >
>
> Hi John,
>
> Thanks for the quick reply. That is very helpful. I also have
another
> question on ascii2nc tool. I'm using that to convert my obs values
to
> .netcdf. Table 4.4 of the v8.1 user guide shows the values of what
should
> be in the columns for ascii2nc. I have a specific question about
the
> height and elevation of the observation (column 9). I want to make
> sure I am putting in those values correctly and that I understand
it.
> For example, if I have a station that has elevation = 500 m asl, and
> my observation height is 10-m above ground, then what should my
value for column 9 be?
> Should it be 10 m agl or 510 m asl ?
>
> Thanks,
> A.J.
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Tuesday, September 15, 2020 1:34 PM
> To: Eiserloh Jr., A.J. <AJEB at pge.com>
> Subject: Re: [rt.rap.ucar.edu #96724] Help with MET tools: Retaining
> individual station statistics
>
> *****CAUTION: This email was sent from an EXTERNAL source. Think
> before clicking links or opening attachments.*****
>
> A.J.,
>
> I see that you're running MET's point-stat tool and are interested
in
> the pairs for each station. We call each fcst/obs pair a "matched
> pair" and those can be written to the output using the MPR line
type.
> In the Point-Stat config file, just turn on that "mpr" line type in
> the "output_flag" setting.
>
> Setting "mpr = STAT;" will cause 1 line to be written to the output
> .stat file for each matched pair.
> Setting "mpr = BOTH;" will write them to both the .stat file and
also
> a "*_mpr.txt" file.
> Using BOTH essentially doubles the output. So I'd recommend using
> STAT, if possible.
>
> Also be aware that if you have many, many observations, the output
> could get quite large. Storing this type of data in ASCII format
makes
> it easy for a human to read and process, but really isn't very
efficient.
> Here's a table which describes the contents of each MPR line:
>
>
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdtce
> nter.github.io%2FMET%2FUsers_Guide%2Fpoint-
stat.html%23id24&data=0
>
2%7C01%7CAJEB%40pge.com%7C31830efafd114669774308d85a5bcc5c%7C44ae661ae
>
ce641aabc967c2c85a08941%7C0%7C0%7C637358697719759234&sdata=dNYtmPO
> W%2BMvNY%2FrwfYks1h2g41hzl3%2BdRjgPqLe%2FM0E%3D&reserved=0
>
> If you find the output is too large and you're only interested in a
> few stations, you could specify those using the "mask.sid" option
(sid
> = station id's) in the Point-Stat config files.
>
> So you still run Point-Stat once for each model output time and
write
> MPR output to the .stat files. But then you can run the Stat-
Analysis
> tool to aggregate those MPR lines over many cases and compute
> statistics separately for each station. The example command below
> reads MPR lines and for each unique combination of forecast lead
time
> and station id, it compute continuous statistics, like RMSE:
>
> stat_analysis -lookin out/point_stat -job aggregate_stat -line_type
> MPR -out_line_type CNT -by FCST_VAR,FCST_LEAD,OBS_SID -out_stat
> mpr_to_cnt_by_sid.stat
>
> That should write an output file named mpr_to_cnt_by_sid.stat which
> contains CNT lines... one for each unique combination of forecast
> variable, lead time, and observation station id.
>
> Hope that helps explain the process.
>
> Thanks,
> John
>
> On Tue, Sep 15, 2020 at 2:21 PM Julie Prestopnik via RT
> <met_help at ucar.edu
> >
> wrote:
>
> >
> > <URL:
> >
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frt
> > .r
> >
ap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=02%7C
> > 01
> >
%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661aece64
> > 1a
> >
abc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=kgm99wqjSWV
> > DS
> > QK1T8WcQZcAgnozmpmL%2Fhh3arVV5cI%3D&reserved=0 >
> >
> > Hi A.J.
> >
> > I see that you have a question about point_stat. I have assigned
> > your ticket to John. Please allow a few business days for a
response.
> >
> > Julie
> >
> > On Tue, Sep 15, 2020 at 1:20 PM Eiserloh Jr., A.J. via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Tue Sep 15 13:20:48 2020: Request 96724 was acted upon.
> > > Transaction: Ticket created by AJEB at pge.com
> > > Queue: met_help
> > > Subject: Help with MET tools: Retaining individual station
> > statistics
> > > Owner: Nobody
> > > Requestors: AJEB at pge.com
> > > Status: new
> > > Ticket <URL:
> > >
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > > rt
> > >
.rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D96724&data=0
> > > 2%
> > >
7C01%7CAJEB%40pge.com%7C05f77d5442714a8182e508d859b6b3d2%7C44ae661
> > > ae
> > >
ce641aabc967c2c85a08941%7C0%7C0%7C637357988524176437&sdata=kgm
> > > 99
> > > wqjSWVDSQK1T8WcQZcAgnozmpmL%2Fhh3arVV5cI%3D&reserved=0 >
> > >
> > >
> > > Hello,
> > >
> > > I am using point_stat to generate statistics for WRF model
performance.
> > > the *.stat files save the aggregated/accumulated stats, but how
> > > does one save the information for each station used in the
> > > analysis? For example, I'd like to know what the MAE and BIAS
was
> > > for individual stations, and have that information retained
rather
> > > than just for all the stations. Is that possible with MET tool?
> > >
> > > Thanks,
> > >
> > > A.J. Eiserloh - Data Scientist
> > > PG&E - Meteorology Operations & Analytics Applied Technology
> > > Services
> > > 3400 Crow Canyon Rd., San Ramon, CA 94583-1393
> > > 925-307-4492
> > >
> > >
> > >
> >
> > --
> > Julie Prestopnik (she/her/hers)
> > Software Engineer
> > National Center for Atmospheric Research Research Applications
> > Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
> > My working day may not be your working day. Please do not feel
> > obliged to reply to this email outside of your normal working
hours.
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list