[Met_help] [rt.rap.ucar.edu #99015] History for Error running PointStatConfig for QPF (APCP)
John Halley Gotway via RT
met_help at ucar.edu
Thu Mar 18 11:03:40 MDT 2021
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
Below is the error that we are getting and the debug line that is our
concern:
DEBUG 2: Processing APCP_24A24 versus APCP/A24, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using 0
matched pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 1492
DEBUG 3: Rejected: station id = 0
*DEBUG 3: Rejected: obs type = 1492*DEBUG 3: Rejected: valid time
= 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 0
DEBUG 3: Rejected: topography = 0
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: bad climo mean = 0
DEBUG 3: Rejected: bad climo stdev = 0
DEBUG 3: Rejected: duplicates = 0
When looking at reference material, we do not understand where to identify
this "obs type" within the PointStatConfig. Can you provide information on
where we might address this issue within this file? The netCDF file
obtained from running ascii2nc does not appear to contain anything by the
name "obs type".
Based on the debug return above, is the bolded line even the issue, or is
some other information included here that we are not noticing?
I appreciate any help you can provide.
Best,
Matt
--
Matthew R. Green
Professional Research Assistant
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: John Halley Gotway
Time: Thu Mar 11 12:44:40 2021
Hi Matt,
I see you have a question about interpreting the reason code from the
output of Point-Stat:
*DEBUG 3: Rejected: obs type = 1492*
By "obs type" we really mean the observation variable name. But I
definitely do understand why that's confusing! In fact, I see that for
the
upcoming met-10.0.0 we've changed the log message to print "*Rejected:
obs
var name*" instead:
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
So that must have been confusing to other users as well!
Please take a look in your Point-Stat config file at "obs.field"
entries.
This log message is telling you that it can't find any point
observations
named "APCP" with an accumulation interval of 24 hours.
Hope that helps clarify.
Thanks,
John
On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA Affiliate via RT
<
met_help at ucar.edu> wrote:
>
> Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
> Transaction: Ticket created by matthew.r.green at noaa.gov
> Queue: met_help
> Subject: Error running PointStatConfig for QPF (APCP)
> Owner: Nobody
> Requestors: matthew.r.green at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
>
>
> Hi,
>
> Below is the error that we are getting and the debug line that is
our
> concern:
>
> DEBUG 2: Processing APCP_24A24 versus APCP/A24, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
0
> matched pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 1492
> DEBUG 3: Rejected: station id = 0
>
> *DEBUG 3: Rejected: obs type = 1492*DEBUG 3: Rejected: valid
time
> = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 0
> DEBUG 3: Rejected: topography = 0
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: bad climo mean = 0
> DEBUG 3: Rejected: bad climo stdev = 0
> DEBUG 3: Rejected: duplicates = 0
>
> When looking at reference material, we do not understand where to
identify
> this "obs type" within the PointStatConfig. Can you provide
information on
> where we might address this issue within this file? The netCDF file
> obtained from running ascii2nc does not appear to contain anything
by the
> name "obs type".
>
> Based on the debug return above, is the bolded line even the issue,
or is
> some other information included here that we are not noticing?
>
> I appreciate any help you can provide.
>
> Best,
> Matt
> --
> Matthew R. Green
>
> Professional Research Assistant
> Cooperative Institute for Research in Environmental Sciences (CIRES)
> NOAA/NWS/Weather Prediction Center
>
>
------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: Matthew Green - NOAA Affiliate
Time: Thu Mar 11 13:53:53 2021
Hi John,
Thank you for your prompt reply.
In the config file I have the following code:
obs = {
field = [
{
message_type = ["ADPSFC"];
name = "APCP";
level = [ "A24" ];
cat_thresh = [ >=0.254, >=2.54, >=6.35, >=12.7, >=25.4,
>=38.1,
>=50.8, >=76.2, >=101.6, >=127.0, >=152.4 ];
}
So, I have defined the variable name. I am unsure how else to define
the
variable to locate. In the NetCDF files that are used for the
observations,
the variable name is "APCP". So, these two match, what might be the
next
thing to test?
Thank you,
Matt
--
Matthew R. Green
Professional Research Assistant
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
On Thu, Mar 11, 2021 at 12:44 PM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi Matt,
>
> I see you have a question about interpreting the reason code from
the
> output of Point-Stat:
> *DEBUG 3: Rejected: obs type = 1492*
>
> By "obs type" we really mean the observation variable name. But I
> definitely do understand why that's confusing! In fact, I see that
for the
> upcoming met-10.0.0 we've changed the log message to print
"*Rejected: obs
> var name*" instead:
>
>
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
>
> So that must have been confusing to other users as well!
>
> Please take a look in your Point-Stat config file at "obs.field"
entries.
> This log message is telling you that it can't find any point
observations
> named "APCP" with an accumulation interval of 24 hours.
>
> Hope that helps clarify.
>
> Thanks,
> John
>
> On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
> > Transaction: Ticket created by matthew.r.green at noaa.gov
> > Queue: met_help
> > Subject: Error running PointStatConfig for QPF (APCP)
> > Owner: Nobody
> > Requestors: matthew.r.green at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
> >
> >
> > Hi,
> >
> > Below is the error that we are getting and the debug line that is
our
> > concern:
> >
> > DEBUG 2: Processing APCP_24A24 versus APCP/A24, for observation
type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 0
> > matched pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 1492
> > DEBUG 3: Rejected: station id = 0
> >
> > *DEBUG 3: Rejected: obs type = 1492*DEBUG 3: Rejected:
valid time
> > = 0
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 0
> > DEBUG 3: Rejected: topography = 0
> > DEBUG 3: Rejected: level mismatch = 0
> > DEBUG 3: Rejected: quality marker = 0
> > DEBUG 3: Rejected: message type = 0
> > DEBUG 3: Rejected: masking region = 0
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: bad climo mean = 0
> > DEBUG 3: Rejected: bad climo stdev = 0
> > DEBUG 3: Rejected: duplicates = 0
> >
> > When looking at reference material, we do not understand where to
> identify
> > this "obs type" within the PointStatConfig. Can you provide
information
> on
> > where we might address this issue within this file? The netCDF
file
> > obtained from running ascii2nc does not appear to contain anything
by the
> > name "obs type".
> >
> > Based on the debug return above, is the bolded line even the
issue, or is
> > some other information included here that we are not noticing?
> >
> > I appreciate any help you can provide.
> >
> > Best,
> > Matt
> > --
> > Matthew R. Green
> >
> > Professional Research Assistant
> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > NOAA/NWS/Weather Prediction Center
> >
> >
>
>
------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: John Halley Gotway
Time: Thu Mar 11 13:58:42 2021
There might be something tricky going on here with accumulated precip.
Are
you running on a shared NOAA machine, like hera, jet, or wcoss. If so,
I
could log on and take a closer look.
If not, could you send me files I could use to run point-stat locally?
That'd be the forecast file, the NetCDF point observation file, and
your
Point-Stat config file.
If the data is too big, you could post to our anonymous ftp site:
http://www.dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk#ftp
John
On Thu, Mar 11, 2021 at 1:54 PM Matthew Green - NOAA Affiliate via RT
<
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
>
> Hi John,
>
> Thank you for your prompt reply.
>
> In the config file I have the following code:
>
> obs = {
>
>
> field = [
> {
> message_type = ["ADPSFC"];
> name = "APCP";
> level = [ "A24" ];
> cat_thresh = [ >=0.254, >=2.54, >=6.35, >=12.7, >=25.4,
>=38.1,
> >=50.8, >=76.2, >=101.6, >=127.0, >=152.4 ];
> }
>
> So, I have defined the variable name. I am unsure how else to define
the
> variable to locate. In the NetCDF files that are used for the
observations,
> the variable name is "APCP". So, these two match, what might be the
next
> thing to test?
>
> Thank you,
> Matt
> --
> Matthew R. Green
>
> Professional Research Assistant
> Cooperative Institute for Research in Environmental Sciences (CIRES)
> NOAA/NWS/Weather Prediction Center
>
>
> On Thu, Mar 11, 2021 at 12:44 PM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hi Matt,
> >
> > I see you have a question about interpreting the reason code from
the
> > output of Point-Stat:
> > *DEBUG 3: Rejected: obs type = 1492*
> >
> > By "obs type" we really mean the observation variable name. But I
> > definitely do understand why that's confusing! In fact, I see that
for
> the
> > upcoming met-10.0.0 we've changed the log message to print
"*Rejected:
> obs
> > var name*" instead:
> >
> >
>
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
> >
> > So that must have been confusing to other users as well!
> >
> > Please take a look in your Point-Stat config file at "obs.field"
entries.
> > This log message is telling you that it can't find any point
observations
> > named "APCP" with an accumulation interval of 24 hours.
> >
> > Hope that helps clarify.
> >
> > Thanks,
> > John
> >
> > On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA Affiliate
via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
> > > Transaction: Ticket created by matthew.r.green at noaa.gov
> > > Queue: met_help
> > > Subject: Error running PointStatConfig for QPF (APCP)
> > > Owner: Nobody
> > > Requestors: matthew.r.green at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015
> >
> > >
> > >
> > > Hi,
> > >
> > > Below is the error that we are getting and the debug line that
is our
> > > concern:
> > >
> > > DEBUG 2: Processing APCP_24A24 versus APCP/A24, for observation
type
> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 0
> > > matched pairs.
> > > DEBUG 3: Number of matched pairs = 0
> > > DEBUG 3: Observations processed = 1492
> > > DEBUG 3: Rejected: station id = 0
> > >
> > > *DEBUG 3: Rejected: obs type = 1492*DEBUG 3: Rejected:
valid
> time
> > > = 0
> > > DEBUG 3: Rejected: bad obs value = 0
> > > DEBUG 3: Rejected: off the grid = 0
> > > DEBUG 3: Rejected: topography = 0
> > > DEBUG 3: Rejected: level mismatch = 0
> > > DEBUG 3: Rejected: quality marker = 0
> > > DEBUG 3: Rejected: message type = 0
> > > DEBUG 3: Rejected: masking region = 0
> > > DEBUG 3: Rejected: bad fcst value = 0
> > > DEBUG 3: Rejected: bad climo mean = 0
> > > DEBUG 3: Rejected: bad climo stdev = 0
> > > DEBUG 3: Rejected: duplicates = 0
> > >
> > > When looking at reference material, we do not understand where
to
> > identify
> > > this "obs type" within the PointStatConfig. Can you provide
information
> > on
> > > where we might address this issue within this file? The netCDF
file
> > > obtained from running ascii2nc does not appear to contain
anything by
> the
> > > name "obs type".
> > >
> > > Based on the debug return above, is the bolded line even the
issue, or
> is
> > > some other information included here that we are not noticing?
> > >
> > > I appreciate any help you can provide.
> > >
> > > Best,
> > > Matt
> > > --
> > > Matthew R. Green
> > >
> > > Professional Research Assistant
> > > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > > NOAA/NWS/Weather Prediction Center
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: Matthew Green - NOAA Affiliate
Time: Thu Mar 11 14:16:05 2021
John,
I think the forecast file is just too big (34 MB), so I will try to
upload them to the ftp site. I will email you again when I have done
this.
Matt
--
Matthew R. Green
Professional Research Assistant
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
On Thu, Mar 11, 2021 at 1:58 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> There might be something tricky going on here with accumulated
precip. Are
> you running on a shared NOAA machine, like hera, jet, or wcoss. If
so, I
> could log on and take a closer look.
>
> If not, could you send me files I could use to run point-stat
locally?
> That'd be the forecast file, the NetCDF point observation file, and
your
> Point-Stat config file.
>
> If the data is too big, you could post to our anonymous ftp site:
>
> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>
> John
>
> On Thu, Mar 11, 2021 at 1:54 PM Matthew Green - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
> >
> > Hi John,
> >
> > Thank you for your prompt reply.
> >
> > In the config file I have the following code:
> >
> > obs = {
> >
> >
> > field = [
> > {
> > message_type = ["ADPSFC"];
> > name = "APCP";
> > level = [ "A24" ];
> > cat_thresh = [ >=0.254, >=2.54, >=6.35, >=12.7, >=25.4,
>=38.1,
> > >=50.8, >=76.2, >=101.6, >=127.0, >=152.4 ];
> > }
> >
> > So, I have defined the variable name. I am unsure how else to
define the
> > variable to locate. In the NetCDF files that are used for the
> observations,
> > the variable name is "APCP". So, these two match, what might be
the next
> > thing to test?
> >
> > Thank you,
> > Matt
> > --
> > Matthew R. Green
> >
> > Professional Research Assistant
> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > NOAA/NWS/Weather Prediction Center
> >
> >
> > On Thu, Mar 11, 2021 at 12:44 PM John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Hi Matt,
> > >
> > > I see you have a question about interpreting the reason code
from the
> > > output of Point-Stat:
> > > *DEBUG 3: Rejected: obs type = 1492*
> > >
> > > By "obs type" we really mean the observation variable name. But
I
> > > definitely do understand why that's confusing! In fact, I see
that for
> > the
> > > upcoming met-10.0.0 we've changed the log message to print
"*Rejected:
> > obs
> > > var name*" instead:
> > >
> > >
> >
>
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
> > >
> > > So that must have been confusing to other users as well!
> > >
> > > Please take a look in your Point-Stat config file at "obs.field"
> entries.
> > > This log message is telling you that it can't find any point
> observations
> > > named "APCP" with an accumulation interval of 24 hours.
> > >
> > > Hope that helps clarify.
> > >
> > > Thanks,
> > > John
> > >
> > > On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA Affiliate
via RT
> <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
> > > > Transaction: Ticket created by matthew.r.green at noaa.gov
> > > > Queue: met_help
> > > > Subject: Error running PointStatConfig for QPF (APCP)
> > > > Owner: Nobody
> > > > Requestors: matthew.r.green at noaa.gov
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > Below is the error that we are getting and the debug line that
is our
> > > > concern:
> > > >
> > > > DEBUG 2: Processing APCP_24A24 versus APCP/A24, for
observation type
> > > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 0
> > > > matched pairs.
> > > > DEBUG 3: Number of matched pairs = 0
> > > > DEBUG 3: Observations processed = 1492
> > > > DEBUG 3: Rejected: station id = 0
> > > >
> > > > *DEBUG 3: Rejected: obs type = 1492*DEBUG 3: Rejected:
valid
> > time
> > > > = 0
> > > > DEBUG 3: Rejected: bad obs value = 0
> > > > DEBUG 3: Rejected: off the grid = 0
> > > > DEBUG 3: Rejected: topography = 0
> > > > DEBUG 3: Rejected: level mismatch = 0
> > > > DEBUG 3: Rejected: quality marker = 0
> > > > DEBUG 3: Rejected: message type = 0
> > > > DEBUG 3: Rejected: masking region = 0
> > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > DEBUG 3: Rejected: bad climo mean = 0
> > > > DEBUG 3: Rejected: bad climo stdev = 0
> > > > DEBUG 3: Rejected: duplicates = 0
> > > >
> > > > When looking at reference material, we do not understand where
to
> > > identify
> > > > this "obs type" within the PointStatConfig. Can you provide
> information
> > > on
> > > > where we might address this issue within this file? The netCDF
file
> > > > obtained from running ascii2nc does not appear to contain
anything by
> > the
> > > > name "obs type".
> > > >
> > > > Based on the debug return above, is the bolded line even the
issue,
> or
> > is
> > > > some other information included here that we are not noticing?
> > > >
> > > > I appreciate any help you can provide.
> > > >
> > > > Best,
> > > > Matt
> > > > --
> > > > Matthew R. Green
> > > >
> > > > Professional Research Assistant
> > > > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > > > NOAA/NWS/Weather Prediction Center
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: Matthew Green - NOAA Affiliate
Time: Thu Mar 11 15:26:27 2021
For some reason, I have been struggling with the ftp. I think I
managed to
upload to the forecast file and the observation file. The point stat
config
file is attached, because I was not able to upload it properly.
- Matt
--
Matthew R. Green
Professional Research Assistant
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
On Thu, Mar 11, 2021 at 2:15 PM Matthew Green - NOAA Affiliate <
matthew.r.green at noaa.gov> wrote:
> John,
>
> I think the forecast file is just too big (34 MB), so I will try to
> upload them to the ftp site. I will email you again when I have done
this.
>
> Matt
> --
> Matthew R. Green
>
> Professional Research Assistant
> Cooperative Institute for Research in Environmental Sciences (CIRES)
> NOAA/NWS/Weather Prediction Center
>
>
> On Thu, Mar 11, 2021 at 1:58 PM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> There might be something tricky going on here with accumulated
precip. Are
>> you running on a shared NOAA machine, like hera, jet, or wcoss. If
so, I
>> could log on and take a closer look.
>>
>> If not, could you send me files I could use to run point-stat
locally?
>> That'd be the forecast file, the NetCDF point observation file, and
your
>> Point-Stat config file.
>>
>> If the data is too big, you could post to our anonymous ftp site:
>>
>> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>>
>> John
>>
>> On Thu, Mar 11, 2021 at 1:54 PM Matthew Green - NOAA Affiliate via
RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
>> >
>> > Hi John,
>> >
>> > Thank you for your prompt reply.
>> >
>> > In the config file I have the following code:
>> >
>> > obs = {
>> >
>> >
>> > field = [
>> > {
>> > message_type = ["ADPSFC"];
>> > name = "APCP";
>> > level = [ "A24" ];
>> > cat_thresh = [ >=0.254, >=2.54, >=6.35, >=12.7, >=25.4,
>=38.1,
>> > >=50.8, >=76.2, >=101.6, >=127.0, >=152.4 ];
>> > }
>> >
>> > So, I have defined the variable name. I am unsure how else to
define the
>> > variable to locate. In the NetCDF files that are used for the
>> observations,
>> > the variable name is "APCP". So, these two match, what might be
the next
>> > thing to test?
>> >
>> > Thank you,
>> > Matt
>> > --
>> > Matthew R. Green
>> >
>> > Professional Research Assistant
>> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
>> > NOAA/NWS/Weather Prediction Center
>> >
>> >
>> > On Thu, Mar 11, 2021 at 12:44 PM John Halley Gotway via RT <
>> > met_help at ucar.edu> wrote:
>> >
>> > > Hi Matt,
>> > >
>> > > I see you have a question about interpreting the reason code
from the
>> > > output of Point-Stat:
>> > > *DEBUG 3: Rejected: obs type = 1492*
>> > >
>> > > By "obs type" we really mean the observation variable name. But
I
>> > > definitely do understand why that's confusing! In fact, I see
that for
>> > the
>> > > upcoming met-10.0.0 we've changed the log message to print
"*Rejected:
>> > obs
>> > > var name*" instead:
>> > >
>> > >
>> >
>>
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
>> > >
>> > > So that must have been confusing to other users as well!
>> > >
>> > > Please take a look in your Point-Stat config file at
"obs.field"
>> entries.
>> > > This log message is telling you that it can't find any point
>> observations
>> > > named "APCP" with an accumulation interval of 24 hours.
>> > >
>> > > Hope that helps clarify.
>> > >
>> > > Thanks,
>> > > John
>> > >
>> > > On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA Affiliate
via
>> RT <
>> > > met_help at ucar.edu> wrote:
>> > >
>> > > >
>> > > > Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
>> > > > Transaction: Ticket created by matthew.r.green at noaa.gov
>> > > > Queue: met_help
>> > > > Subject: Error running PointStatConfig for QPF (APCP)
>> > > > Owner: Nobody
>> > > > Requestors: matthew.r.green at noaa.gov
>> > > > Status: new
>> > > > Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015
>> > >
>> > > >
>> > > >
>> > > > Hi,
>> > > >
>> > > > Below is the error that we are getting and the debug line
that is
>> our
>> > > > concern:
>> > > >
>> > > > DEBUG 2: Processing APCP_24A24 versus APCP/A24, for
observation type
>> > > > ADPSFC, over region FULL, for interpolation method
NEAREST(1),
>> using 0
>> > > > matched pairs.
>> > > > DEBUG 3: Number of matched pairs = 0
>> > > > DEBUG 3: Observations processed = 1492
>> > > > DEBUG 3: Rejected: station id = 0
>> > > >
>> > > > *DEBUG 3: Rejected: obs type = 1492*DEBUG 3: Rejected:
valid
>> > time
>> > > > = 0
>> > > > DEBUG 3: Rejected: bad obs value = 0
>> > > > DEBUG 3: Rejected: off the grid = 0
>> > > > DEBUG 3: Rejected: topography = 0
>> > > > DEBUG 3: Rejected: level mismatch = 0
>> > > > DEBUG 3: Rejected: quality marker = 0
>> > > > DEBUG 3: Rejected: message type = 0
>> > > > DEBUG 3: Rejected: masking region = 0
>> > > > DEBUG 3: Rejected: bad fcst value = 0
>> > > > DEBUG 3: Rejected: bad climo mean = 0
>> > > > DEBUG 3: Rejected: bad climo stdev = 0
>> > > > DEBUG 3: Rejected: duplicates = 0
>> > > >
>> > > > When looking at reference material, we do not understand
where to
>> > > identify
>> > > > this "obs type" within the PointStatConfig. Can you provide
>> information
>> > > on
>> > > > where we might address this issue within this file? The
netCDF file
>> > > > obtained from running ascii2nc does not appear to contain
anything
>> by
>> > the
>> > > > name "obs type".
>> > > >
>> > > > Based on the debug return above, is the bolded line even the
issue,
>> or
>> > is
>> > > > some other information included here that we are not
noticing?
>> > > >
>> > > > I appreciate any help you can provide.
>> > > >
>> > > > Best,
>> > > > Matt
>> > > > --
>> > > > Matthew R. Green
>> > > >
>> > > > Professional Research Assistant
>> > > > Cooperative Institute for Research in Environmental Sciences
(CIRES)
>> > > > NOAA/NWS/Weather Prediction Center
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: John Halley Gotway
Time: Fri Mar 12 10:58:59 2021
Matt,
Thanks for sending the sample data. I was able to run it right out of
the
box (using met-9.1) and get the exact same behavior you describe:
DEBUG 2: Processing APCP_24A24 versus APCP/A24, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using 0
matched pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 1492
DEBUG 3: Rejected: station id = 0
DEBUG 3: Rejected: obs type = 1492
Indeed, the issue is something "weird" related to precip. The trouble
comes
from the following line of code:
https://github.com/dtcenter/MET/blob/8a3ee59f069bc4eff8d9d75b452a19f0a80a6c8a/met/src/libcode/vx_data2d/var_info.cc#L678
I suspect this logic was intended as a way to make verifying precip
more
convenient and intuitive, but we're now finding it more confusing!
Basically, when you request 'name = "APCP"; level = "A24";' this
library
code translates that into a string "APCP_24". But that string doesn't
exist
in your obs... only "APCP" does.
If you have ability to modify these point observations, you could
either
replace "APCP" with "APCP_24" or use some other string entirely.
I did that (changed APCP to APCP_24) with the sample data you sent and
was
able to get 614 matched pairs:
DEBUG 2: Processing APCP_24/A24 versus APCP_24/Z0, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
614
matched pairs.
DEBUG 3: Number of matched pairs = 614
DEBUG 3: Observations processed = 1492
DEBUG 3: Rejected: station id = 0
DEBUG 3: Rejected: obs var name = 0
DEBUG 3: Rejected: valid time = 878
Sorry this is so confusing! We really should revisit whether or not
automatically appending the accumulation to the variable name helps or
hurts. I'm sure the original motivation was avoiding confusion when
verifying multiple precip accumulations... differentiating by variable
name
(APCP_01, APCP_06, APCP_24) is more clear than them all being named
APCP
with level = A1, A6, or A24.
Please give that a try and let me know if you're still stuck.
Thanks,
John
On Thu, Mar 11, 2021 at 3:27 PM Matthew Green - NOAA Affiliate via RT
<
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
>
> For some reason, I have been struggling with the ftp. I think I
managed to
> upload to the forecast file and the observation file. The point stat
config
> file is attached, because I was not able to upload it properly.
>
> - Matt
> --
> Matthew R. Green
>
> Professional Research Assistant
> Cooperative Institute for Research in Environmental Sciences (CIRES)
> NOAA/NWS/Weather Prediction Center
>
>
> On Thu, Mar 11, 2021 at 2:15 PM Matthew Green - NOAA Affiliate <
> matthew.r.green at noaa.gov> wrote:
>
> > John,
> >
> > I think the forecast file is just too big (34 MB), so I will try
to
> > upload them to the ftp site. I will email you again when I have
done
> this.
> >
> > Matt
> > --
> > Matthew R. Green
> >
> > Professional Research Assistant
> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > NOAA/NWS/Weather Prediction Center
> >
> >
> > On Thu, Mar 11, 2021 at 1:58 PM John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> There might be something tricky going on here with accumulated
precip.
> Are
> >> you running on a shared NOAA machine, like hera, jet, or wcoss.
If so, I
> >> could log on and take a closer look.
> >>
> >> If not, could you send me files I could use to run point-stat
locally?
> >> That'd be the forecast file, the NetCDF point observation file,
and your
> >> Point-Stat config file.
> >>
> >> If the data is too big, you could post to our anonymous ftp site:
> >>
> >>
> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
> >>
> >> John
> >>
> >> On Thu, Mar 11, 2021 at 1:54 PM Matthew Green - NOAA Affiliate
via RT <
> >> met_help at ucar.edu> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
> >> >
> >> > Hi John,
> >> >
> >> > Thank you for your prompt reply.
> >> >
> >> > In the config file I have the following code:
> >> >
> >> > obs = {
> >> >
> >> >
> >> > field = [
> >> > {
> >> > message_type = ["ADPSFC"];
> >> > name = "APCP";
> >> > level = [ "A24" ];
> >> > cat_thresh = [ >=0.254, >=2.54, >=6.35, >=12.7, >=25.4,
> >=38.1,
> >> > >=50.8, >=76.2, >=101.6, >=127.0, >=152.4 ];
> >> > }
> >> >
> >> > So, I have defined the variable name. I am unsure how else to
define
> the
> >> > variable to locate. In the NetCDF files that are used for the
> >> observations,
> >> > the variable name is "APCP". So, these two match, what might be
the
> next
> >> > thing to test?
> >> >
> >> > Thank you,
> >> > Matt
> >> > --
> >> > Matthew R. Green
> >> >
> >> > Professional Research Assistant
> >> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> >> > NOAA/NWS/Weather Prediction Center
> >> >
> >> >
> >> > On Thu, Mar 11, 2021 at 12:44 PM John Halley Gotway via RT <
> >> > met_help at ucar.edu> wrote:
> >> >
> >> > > Hi Matt,
> >> > >
> >> > > I see you have a question about interpreting the reason code
from
> the
> >> > > output of Point-Stat:
> >> > > *DEBUG 3: Rejected: obs type = 1492*
> >> > >
> >> > > By "obs type" we really mean the observation variable name.
But I
> >> > > definitely do understand why that's confusing! In fact, I see
that
> for
> >> > the
> >> > > upcoming met-10.0.0 we've changed the log message to print
> "*Rejected:
> >> > obs
> >> > > var name*" instead:
> >> > >
> >> > >
> >> >
> >>
>
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
> >> > >
> >> > > So that must have been confusing to other users as well!
> >> > >
> >> > > Please take a look in your Point-Stat config file at
"obs.field"
> >> entries.
> >> > > This log message is telling you that it can't find any point
> >> observations
> >> > > named "APCP" with an accumulation interval of 24 hours.
> >> > >
> >> > > Hope that helps clarify.
> >> > >
> >> > > Thanks,
> >> > > John
> >> > >
> >> > > On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA
Affiliate via
> >> RT <
> >> > > met_help at ucar.edu> wrote:
> >> > >
> >> > > >
> >> > > > Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
> >> > > > Transaction: Ticket created by matthew.r.green at noaa.gov
> >> > > > Queue: met_help
> >> > > > Subject: Error running PointStatConfig for QPF (APCP)
> >> > > > Owner: Nobody
> >> > > > Requestors: matthew.r.green at noaa.gov
> >> > > > Status: new
> >> > > > Ticket <URL:
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015
> >> > >
> >> > > >
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > Below is the error that we are getting and the debug line
that is
> >> our
> >> > > > concern:
> >> > > >
> >> > > > DEBUG 2: Processing APCP_24A24 versus APCP/A24, for
observation
> type
> >> > > > ADPSFC, over region FULL, for interpolation method
NEAREST(1),
> >> using 0
> >> > > > matched pairs.
> >> > > > DEBUG 3: Number of matched pairs = 0
> >> > > > DEBUG 3: Observations processed = 1492
> >> > > > DEBUG 3: Rejected: station id = 0
> >> > > >
> >> > > > *DEBUG 3: Rejected: obs type = 1492*DEBUG 3:
Rejected:
> valid
> >> > time
> >> > > > = 0
> >> > > > DEBUG 3: Rejected: bad obs value = 0
> >> > > > DEBUG 3: Rejected: off the grid = 0
> >> > > > DEBUG 3: Rejected: topography = 0
> >> > > > DEBUG 3: Rejected: level mismatch = 0
> >> > > > DEBUG 3: Rejected: quality marker = 0
> >> > > > DEBUG 3: Rejected: message type = 0
> >> > > > DEBUG 3: Rejected: masking region = 0
> >> > > > DEBUG 3: Rejected: bad fcst value = 0
> >> > > > DEBUG 3: Rejected: bad climo mean = 0
> >> > > > DEBUG 3: Rejected: bad climo stdev = 0
> >> > > > DEBUG 3: Rejected: duplicates = 0
> >> > > >
> >> > > > When looking at reference material, we do not understand
where to
> >> > > identify
> >> > > > this "obs type" within the PointStatConfig. Can you provide
> >> information
> >> > > on
> >> > > > where we might address this issue within this file? The
netCDF
> file
> >> > > > obtained from running ascii2nc does not appear to contain
anything
> >> by
> >> > the
> >> > > > name "obs type".
> >> > > >
> >> > > > Based on the debug return above, is the bolded line even
the
> issue,
> >> or
> >> > is
> >> > > > some other information included here that we are not
noticing?
> >> > > >
> >> > > > I appreciate any help you can provide.
> >> > > >
> >> > > > Best,
> >> > > > Matt
> >> > > > --
> >> > > > Matthew R. Green
> >> > > >
> >> > > > Professional Research Assistant
> >> > > > Cooperative Institute for Research in Environmental
Sciences
> (CIRES)
> >> > > > NOAA/NWS/Weather Prediction Center
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
>
>
------------------------------------------------
Subject: Error running PointStatConfig for QPF (APCP)
From: Matthew Green - NOAA Affiliate
Time: Fri Mar 12 12:19:19 2021
John,
Thank you for working through this issue for us! I will make these
changes
to the observation files and see what we get after that.
I will let you know if we still encounter issues.
Thank you,
Matt
--
Matthew R. Green
Professional Research Assistant
Cooperative Institute for Research in Environmental Sciences (CIRES)
NOAA/NWS/Weather Prediction Center
On Fri, Mar 12, 2021 at 10:59 AM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Matt,
>
> Thanks for sending the sample data. I was able to run it right out
of the
> box (using met-9.1) and get the exact same behavior you describe:
>
> DEBUG 2: Processing APCP_24A24 versus APCP/A24, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
0
> matched pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 1492
> DEBUG 3: Rejected: station id = 0
> DEBUG 3: Rejected: obs type = 1492
>
> Indeed, the issue is something "weird" related to precip. The
trouble comes
> from the following line of code:
>
>
https://github.com/dtcenter/MET/blob/8a3ee59f069bc4eff8d9d75b452a19f0a80a6c8a/met/src/libcode/vx_data2d/var_info.cc#L678
>
> I suspect this logic was intended as a way to make verifying precip
more
> convenient and intuitive, but we're now finding it more confusing!
> Basically, when you request 'name = "APCP"; level = "A24";' this
library
> code translates that into a string "APCP_24". But that string
doesn't exist
> in your obs... only "APCP" does.
>
> If you have ability to modify these point observations, you could
either
> replace "APCP" with "APCP_24" or use some other string entirely.
>
> I did that (changed APCP to APCP_24) with the sample data you sent
and was
> able to get 614 matched pairs:
>
> DEBUG 2: Processing APCP_24/A24 versus APCP_24/Z0, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
614
> matched pairs.
> DEBUG 3: Number of matched pairs = 614
> DEBUG 3: Observations processed = 1492
> DEBUG 3: Rejected: station id = 0
> DEBUG 3: Rejected: obs var name = 0
> DEBUG 3: Rejected: valid time = 878
>
> Sorry this is so confusing! We really should revisit whether or not
> automatically appending the accumulation to the variable name helps
or
> hurts. I'm sure the original motivation was avoiding confusion when
> verifying multiple precip accumulations... differentiating by
variable name
> (APCP_01, APCP_06, APCP_24) is more clear than them all being named
APCP
> with level = A1, A6, or A24.
>
> Please give that a try and let me know if you're still stuck.
>
> Thanks,
> John
>
> On Thu, Mar 11, 2021 at 3:27 PM Matthew Green - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015 >
> >
> > For some reason, I have been struggling with the ftp. I think I
managed
> to
> > upload to the forecast file and the observation file. The point
stat
> config
> > file is attached, because I was not able to upload it properly.
> >
> > - Matt
> > --
> > Matthew R. Green
> >
> > Professional Research Assistant
> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > NOAA/NWS/Weather Prediction Center
> >
> >
> > On Thu, Mar 11, 2021 at 2:15 PM Matthew Green - NOAA Affiliate <
> > matthew.r.green at noaa.gov> wrote:
> >
> > > John,
> > >
> > > I think the forecast file is just too big (34 MB), so I will try
to
> > > upload them to the ftp site. I will email you again when I have
done
> > this.
> > >
> > > Matt
> > > --
> > > Matthew R. Green
> > >
> > > Professional Research Assistant
> > > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > > NOAA/NWS/Weather Prediction Center
> > >
> > >
> > > On Thu, Mar 11, 2021 at 1:58 PM John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> There might be something tricky going on here with accumulated
precip.
> > Are
> > >> you running on a shared NOAA machine, like hera, jet, or wcoss.
If
> so, I
> > >> could log on and take a closer look.
> > >>
> > >> If not, could you send me files I could use to run point-stat
locally?
> > >> That'd be the forecast file, the NetCDF point observation file,
and
> your
> > >> Point-Stat config file.
> > >>
> > >> If the data is too big, you could post to our anonymous ftp
site:
> > >>
> > >>
> >
> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
> > >>
> > >> John
> > >>
> > >> On Thu, Mar 11, 2021 at 1:54 PM Matthew Green - NOAA Affiliate
via RT
> <
> > >> met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015
>
> > >> >
> > >> > Hi John,
> > >> >
> > >> > Thank you for your prompt reply.
> > >> >
> > >> > In the config file I have the following code:
> > >> >
> > >> > obs = {
> > >> >
> > >> >
> > >> > field = [
> > >> > {
> > >> > message_type = ["ADPSFC"];
> > >> > name = "APCP";
> > >> > level = [ "A24" ];
> > >> > cat_thresh = [ >=0.254, >=2.54, >=6.35, >=12.7,
>=25.4,
> > >=38.1,
> > >> > >=50.8, >=76.2, >=101.6, >=127.0, >=152.4 ];
> > >> > }
> > >> >
> > >> > So, I have defined the variable name. I am unsure how else to
define
> > the
> > >> > variable to locate. In the NetCDF files that are used for the
> > >> observations,
> > >> > the variable name is "APCP". So, these two match, what might
be the
> > next
> > >> > thing to test?
> > >> >
> > >> > Thank you,
> > >> > Matt
> > >> > --
> > >> > Matthew R. Green
> > >> >
> > >> > Professional Research Assistant
> > >> > Cooperative Institute for Research in Environmental Sciences
(CIRES)
> > >> > NOAA/NWS/Weather Prediction Center
> > >> >
> > >> >
> > >> > On Thu, Mar 11, 2021 at 12:44 PM John Halley Gotway via RT <
> > >> > met_help at ucar.edu> wrote:
> > >> >
> > >> > > Hi Matt,
> > >> > >
> > >> > > I see you have a question about interpreting the reason
code from
> > the
> > >> > > output of Point-Stat:
> > >> > > *DEBUG 3: Rejected: obs type = 1492*
> > >> > >
> > >> > > By "obs type" we really mean the observation variable name.
But I
> > >> > > definitely do understand why that's confusing! In fact, I
see that
> > for
> > >> > the
> > >> > > upcoming met-10.0.0 we've changed the log message to print
> > "*Rejected:
> > >> > obs
> > >> > > var name*" instead:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
>
https://github.com/dtcenter/MET/blob/2b5e37fa69712681b4e0e25fd6b753bc5d638cdb/met/src/tools/core/point_stat/point_stat.cc#L1007
> > >> > >
> > >> > > So that must have been confusing to other users as well!
> > >> > >
> > >> > > Please take a look in your Point-Stat config file at
"obs.field"
> > >> entries.
> > >> > > This log message is telling you that it can't find any
point
> > >> observations
> > >> > > named "APCP" with an accumulation interval of 24 hours.
> > >> > >
> > >> > > Hope that helps clarify.
> > >> > >
> > >> > > Thanks,
> > >> > > John
> > >> > >
> > >> > > On Thu, Mar 11, 2021 at 11:42 AM Matthew Green - NOAA
Affiliate
> via
> > >> RT <
> > >> > > met_help at ucar.edu> wrote:
> > >> > >
> > >> > > >
> > >> > > > Thu Mar 11 11:41:30 2021: Request 99015 was acted upon.
> > >> > > > Transaction: Ticket created by matthew.r.green at noaa.gov
> > >> > > > Queue: met_help
> > >> > > > Subject: Error running PointStatConfig for QPF
(APCP)
> > >> > > > Owner: Nobody
> > >> > > > Requestors: matthew.r.green at noaa.gov
> > >> > > > Status: new
> > >> > > > Ticket <URL:
> > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=99015
> > >> > >
> > >> > > >
> > >> > > >
> > >> > > > Hi,
> > >> > > >
> > >> > > > Below is the error that we are getting and the debug line
that
> is
> > >> our
> > >> > > > concern:
> > >> > > >
> > >> > > > DEBUG 2: Processing APCP_24A24 versus APCP/A24, for
observation
> > type
> > >> > > > ADPSFC, over region FULL, for interpolation method
NEAREST(1),
> > >> using 0
> > >> > > > matched pairs.
> > >> > > > DEBUG 3: Number of matched pairs = 0
> > >> > > > DEBUG 3: Observations processed = 1492
> > >> > > > DEBUG 3: Rejected: station id = 0
> > >> > > >
> > >> > > > *DEBUG 3: Rejected: obs type = 1492*DEBUG 3:
Rejected:
> > valid
> > >> > time
> > >> > > > = 0
> > >> > > > DEBUG 3: Rejected: bad obs value = 0
> > >> > > > DEBUG 3: Rejected: off the grid = 0
> > >> > > > DEBUG 3: Rejected: topography = 0
> > >> > > > DEBUG 3: Rejected: level mismatch = 0
> > >> > > > DEBUG 3: Rejected: quality marker = 0
> > >> > > > DEBUG 3: Rejected: message type = 0
> > >> > > > DEBUG 3: Rejected: masking region = 0
> > >> > > > DEBUG 3: Rejected: bad fcst value = 0
> > >> > > > DEBUG 3: Rejected: bad climo mean = 0
> > >> > > > DEBUG 3: Rejected: bad climo stdev = 0
> > >> > > > DEBUG 3: Rejected: duplicates = 0
> > >> > > >
> > >> > > > When looking at reference material, we do not understand
where
> to
> > >> > > identify
> > >> > > > this "obs type" within the PointStatConfig. Can you
provide
> > >> information
> > >> > > on
> > >> > > > where we might address this issue within this file? The
netCDF
> > file
> > >> > > > obtained from running ascii2nc does not appear to contain
> anything
> > >> by
> > >> > the
> > >> > > > name "obs type".
> > >> > > >
> > >> > > > Based on the debug return above, is the bolded line even
the
> > issue,
> > >> or
> > >> > is
> > >> > > > some other information included here that we are not
noticing?
> > >> > > >
> > >> > > > I appreciate any help you can provide.
> > >> > > >
> > >> > > > Best,
> > >> > > > Matt
> > >> > > > --
> > >> > > > Matthew R. Green
> > >> > > >
> > >> > > > Professional Research Assistant
> > >> > > > Cooperative Institute for Research in Environmental
Sciences
> > (CIRES)
> > >> > > > NOAA/NWS/Weather Prediction Center
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >>
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list