[Met_help] [rt.rap.ucar.edu #90917] History for Point_stat and unmatched pairs
John Halley Gotway via RT
met_help at ucar.edu
Mon Jul 8 12:35:32 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I am currently using *point_stat* in attempt to verify a 1-hour
precipitation forecast from the experimental High Resolution Rapid Refresh
(HRRR) model with a network of surface rain gauge observations in the New
York City metro area. The observations cover a domain of roughly 50km x
50km and is near the North Atlantic coastline. The forecast initialization
time is 20180416_0200, where the forecast validation time is 20180416_0300.
The issue I have is when running *point_stat* no matching pairs are found.
At a higher verbosity level I see the following, which tells me there are
no matched pairs:
DEBUG 2: Searching 8 observations from 8 messages.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 4: set FCST_UNITS:kg/m^2
DEBUG 4: set OBS_UNITS:NA
DEBUG 2: Processing APCP/A1 versus APCP/A1, for observation type ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 8
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: obs type = 0
DEBUG 3: Rejected: valid time = 8
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: duplicates = 0
In addition, I have made changes to the following dictionaries in my own
configuration file from the default PointStatConfig file:
- fcst
- obs
- obs_window
- mask
- output_flag
I am not sure how to send you some test data through your ftp site, so you
may re-create the issue. When typing in the password for "anonymous", it
does not recognize my email.
Any assistance will be greatly appreciated. Please let me know what else
you may need from me. Thank you.
--
*Adrian Pena*
*NERTO Intern with HMA*
*NOAA EPP/MSI Graduate Scholar at CESSRST CSC*
*MS Candidate, Earth Systems Science & Environmental Engineering*
*The City College of New York at CUNY*
*adrian.pena at noaa.gov <adrian.pena at noaa.gov>*
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Point_stat and unmatched pairs
From: John Halley Gotway
Time: Mon Jul 08 11:35:55 2019
Adrian,
I see you have a question about 0 matched pairs from Point-Stat. I'm
glad
to see that you've run at verbosity level 3 to print out the counts of
reason codes. Looks like all 8 of your observations were skipped due
to
the valid time window:
*DEBUG 3: Rejected: valid time = 8*
Here's how the time window logic works. You pass forecast data to
Point-Stat on the command line. It reads the forecast valid time from
the
metadata, which according to your email, should be 20180416_030000.
It
reads the "obs_window" setting from the Point-Stat config file and
defines
the matching time window from (valid time + obs_window.beg) to (valid
time
+ obs_window.end). The "beg" and "end" values are specified in
seconds.
The default setting of +/- 5400 seconds is +/- 1.5 hours:
*obs_window = { beg = -5400; end = 5400;}*
The debug level 3 output indicates that none of the 8 observations
fell in
that time window of 20180416_013000 and 20180416_043000. So you just
need
to check the timestamps of your data and make sure you're comparing
the
correct observations to your forecast data.
One way of doing that would be to open up the matching time window A
LOT to
get those 8 obs to match:
*obs_window = { beg = -54000000; end = 54000000;}*
That would be a window of like +/- 1.7 years! And then turn on the
MPR
output line type:
* mpr = BOTH;*
Then look in the MPR output file at the timestamps of the data listed
in
the header columns. That should tell you what the actual difference
is.
Hope that helps get you going.
Thanks,
John Halley Gotway
On Fri, Jul 5, 2019 at 4:39 PM Adrian Pena - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> Fri Jul 05 16:39:53 2019: Request 90917 was acted upon.
> Transaction: Ticket created by adrian.pena at noaa.gov
> Queue: met_help
> Subject: Point_stat and unmatched pairs
> Owner: Nobody
> Requestors: adrian.pena at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90917 >
>
>
> Hello,
> I am currently using *point_stat* in attempt to verify a 1-hour
> precipitation forecast from the experimental High Resolution Rapid
Refresh
> (HRRR) model with a network of surface rain gauge observations in
the New
> York City metro area. The observations cover a domain of roughly
50km x
> 50km and is near the North Atlantic coastline. The forecast
initialization
> time is 20180416_0200, where the forecast validation time is
20180416_0300.
> The issue I have is when running *point_stat* no matching pairs are
found.
> At a higher verbosity level I see the following, which tells me
there are
> no matched pairs:
>
> DEBUG 2: Searching 8 observations from 8 messages.
> DEBUG 2:
> DEBUG 2:
>
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 4: set FCST_UNITS:kg/m^2
> DEBUG 4: set OBS_UNITS:NA
> DEBUG 2: Processing APCP/A1 versus APCP/A1, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 0
pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 8
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: obs type = 0
> DEBUG 3: Rejected: valid time = 8
> 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: duplicates = 0
>
> In addition, I have made changes to the following dictionaries in my
own
> configuration file from the default PointStatConfig file:
> - fcst
> - obs
> - obs_window
> - mask
> - output_flag
>
> I am not sure how to send you some test data through your ftp site,
so you
> may re-create the issue. When typing in the password for
"anonymous", it
> does not recognize my email.
>
> Any assistance will be greatly appreciated. Please let me know what
else
> you may need from me. Thank you.
> --
> *Adrian Pena*
>
> *NERTO Intern with HMA*
> *NOAA EPP/MSI Graduate Scholar at CESSRST CSC*
> *MS Candidate, Earth Systems Science & Environmental Engineering*
> *The City College of New York at CUNY*
> *adrian.pena at noaa.gov <adrian.pena at noaa.gov>*
>
>
------------------------------------------------
Subject: Point_stat and unmatched pairs
From: Adrian Pena - NOAA Affiliate
Time: Mon Jul 08 11:48:45 2019
Hi John,
Thank you for getting back to me so quickly. Your explanation of
obs_window
was quite clear and will definitely help in the future. For now I have
corrected the observation times and point_stat ran without issue.
Thanks
again for your help.
Best regards,
Adrian
On Mon, Jul 8, 2019 at 11:35 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Adrian,
>
> I see you have a question about 0 matched pairs from Point-Stat.
I'm glad
> to see that you've run at verbosity level 3 to print out the counts
of
> reason codes. Looks like all 8 of your observations were skipped
due to
> the valid time window:
> *DEBUG 3: Rejected: valid time = 8*
>
> Here's how the time window logic works. You pass forecast data to
> Point-Stat on the command line. It reads the forecast valid time
from the
> metadata, which according to your email, should be 20180416_030000.
It
> reads the "obs_window" setting from the Point-Stat config file and
defines
> the matching time window from (valid time + obs_window.beg) to
(valid time
> + obs_window.end). The "beg" and "end" values are specified in
seconds.
> The default setting of +/- 5400 seconds is +/- 1.5 hours:
>
>
>
> *obs_window = { beg = -5400; end = 5400;}*
>
> The debug level 3 output indicates that none of the 8 observations
fell in
> that time window of 20180416_013000 and 20180416_043000. So you
just need
> to check the timestamps of your data and make sure you're comparing
the
> correct observations to your forecast data.
>
> One way of doing that would be to open up the matching time window A
LOT to
> get those 8 obs to match:
>
>
>
> *obs_window = { beg = -54000000; end = 54000000;}*
>
> That would be a window of like +/- 1.7 years! And then turn on the
MPR
> output line type:
> * mpr = BOTH;*
>
> Then look in the MPR output file at the timestamps of the data
listed in
> the header columns. That should tell you what the actual difference
is.
>
> Hope that helps get you going.
>
> Thanks,
> John Halley Gotway
>
> On Fri, Jul 5, 2019 at 4:39 PM Adrian Pena - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jul 05 16:39:53 2019: Request 90917 was acted upon.
> > Transaction: Ticket created by adrian.pena at noaa.gov
> > Queue: met_help
> > Subject: Point_stat and unmatched pairs
> > Owner: Nobody
> > Requestors: adrian.pena at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90917 >
> >
> >
> > Hello,
> > I am currently using *point_stat* in attempt to verify a 1-hour
> > precipitation forecast from the experimental High Resolution Rapid
> Refresh
> > (HRRR) model with a network of surface rain gauge observations in
the New
> > York City metro area. The observations cover a domain of roughly
50km x
> > 50km and is near the North Atlantic coastline. The forecast
> initialization
> > time is 20180416_0200, where the forecast validation time is
> 20180416_0300.
> > The issue I have is when running *point_stat* no matching pairs
are
> found.
> > At a higher verbosity level I see the following, which tells me
there are
> > no matched pairs:
> >
> > DEBUG 2: Searching 8 observations from 8 messages.
> > DEBUG 2:
> > DEBUG 2:
> >
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 4: set FCST_UNITS:kg/m^2
> > DEBUG 4: set OBS_UNITS:NA
> > DEBUG 2: Processing APCP/A1 versus APCP/A1, for observation type
> ADPSFC,
> > over region FULL, for interpolation method NEAREST(1), using 0
pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 8
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: obs type = 0
> > DEBUG 3: Rejected: valid time = 8
> > 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: duplicates = 0
> >
> > In addition, I have made changes to the following dictionaries in
my own
> > configuration file from the default PointStatConfig file:
> > - fcst
> > - obs
> > - obs_window
> > - mask
> > - output_flag
> >
> > I am not sure how to send you some test data through your ftp
site, so
> you
> > may re-create the issue. When typing in the password for
"anonymous", it
> > does not recognize my email.
> >
> > Any assistance will be greatly appreciated. Please let me know
what else
> > you may need from me. Thank you.
> > --
> > *Adrian Pena*
> >
> > *NERTO Intern with HMA*
> > *NOAA EPP/MSI Graduate Scholar at CESSRST CSC*
> > *MS Candidate, Earth Systems Science & Environmental Engineering*
> > *The City College of New York at CUNY*
> > *adrian.pena at noaa.gov <adrian.pena at noaa.gov>*
> >
> >
>
>
--
*Adrian Pena*
*NERTO Intern with HMA*
*NOAA EPP/MSI Graduate Scholar at CESSRST CSC*
*MS Candidate, Earth Systems Science & Environmental Engineering*
*The City College of New York at CUNY*
*adrian.pena at noaa.gov <adrian.pena at noaa.gov>*
------------------------------------------------
More information about the Met_help
mailing list