[Met_help] [rt.rap.ucar.edu #80360] History for questions with using point data and the nearest neighbor setting
Tara Jensen via RT
met_help at ucar.edu
Thu May 4 14:52:47 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I'm trying to do a verification between ASCAT satellite point data of 10m
winds (u and v), in a swath, against 10m u and v winds from the
gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from prepbufr data to
netCDF format, and verified that the data is in the file, both through
plotting and through ncdump. I don't want to regrid my winds. I want to
keep them as point data, and compare them to the closest GFS grid point.
So, I'm trying to use the Point-Stat tool, with the nearest neighbor
setting. I've used these settings:
model = "GFS";
regrid = {
to_grid = NONE;
method = NEAREST;
width = 1;
vld_thresh = 0.5;
}
wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
fcst = {
field = [
{
name = "UGRD";
level = "Z10";
cat_thresh = [ >=5.0 ];
},
{
name = "VGRD";
level = "Z10";
cat_thresh = [ >=5.0 ];
}
];
}
obs = fcst;
message_type = [ "ASCATW" ];
// Verification masking regions
//
mask = {
grid = [ "FULL" ];
// Interpolation methods
//
interp = {
vld_thresh = 1.0;
type = [
{
method = NEAREST;
width = 1;
}
];
}
//////
and the rest of the settings remained as I found them when I copied the
PointStatConfig_tutorial from the default config file.
So, this runs correctly, and produces all the necessary files that I asked
for, but, there is nothing in the files, because there are no matches.
That's hard for me to believe that there aren't any matches, so, I know
that I have something set wrong. My guess is that either the name =
"UGRD"; and level = "Z10"; is incorrect for 10m winds, or the method =
NEAREST; width = 1; is wrong.
How would I check on the name and level? And, is there a better setting I
should use for width? Or, is there something else I need to set?
Thanks in advance!
Roz
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: John Halley Gotway
Time: Thu May 04 11:24:11 2017
Hi Roz,
I see that you ran Point-Stat and got 0 matched pairs. Please rerun
your
Point-Stat command using verbosity level 3 (-v 3) and write the output
to a
log file (-log point_stat.log). Then inspect that logging output
closely,
and you'll see sections that look something like this:
DEBUG 3: Number of matched pairs = 334
DEBUG 3: Observations processed = 89893
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 79360
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 5
DEBUG 3: Rejected: level mismatch = 9607
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 344
DEBUG 3: Rejected: masking region = 243
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
With you data, you'll see that the number of matched pairs is 0. The
rejection counts are listed in the same order that Point-Stat uses
when
filtering the observations. This should tell you why you're getting 0
matched pairs. Perhaps there's a spatial offset between your forecast
and
obs, or a time offset, or a level offset?
Please take a look at that and let us know if you need help
deciphering the
output.
Thanks,
John Halley Gotway
On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> Queue: met_help
> Subject: questions with using point data and the nearest
neighbor
> setting
> Owner: Nobody
> Requestors: rosalyn.maccracken at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
>
>
> Hi,
>
> I'm trying to do a verification between ASCAT satellite point data
of 10m
> winds (u and v), in a swath, against 10m u and v winds from the
> gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from prepbufr
data to
> netCDF format, and verified that the data is in the file, both
through
> plotting and through ncdump. I don't want to regrid my winds. I
want to
> keep them as point data, and compare them to the closest GFS grid
point.
>
> So, I'm trying to use the Point-Stat tool, with the nearest neighbor
> setting. I've used these settings:
> model = "GFS";
>
> regrid = {
> to_grid = NONE;
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> }
>
> wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
>
> fcst = {
> field = [
> {
> name = "UGRD";
> level = "Z10";
> cat_thresh = [ >=5.0 ];
> },
>
> {
> name = "VGRD";
> level = "Z10";
> cat_thresh = [ >=5.0 ];
> }
> ];
>
> }
> obs = fcst;
>
> message_type = [ "ASCATW" ];
> // Verification masking regions
> //
> mask = {
> grid = [ "FULL" ];
>
> // Interpolation methods
> //
> interp = {
> vld_thresh = 1.0;
>
> type = [
> {
> method = NEAREST;
> width = 1;
> }
> ];
> }
>
> //////
>
> and the rest of the settings remained as I found them when I copied
the
> PointStatConfig_tutorial from the default config file.
>
> So, this runs correctly, and produces all the necessary files that I
asked
> for, but, there is nothing in the files, because there are no
matches.
> That's hard for me to believe that there aren't any matches, so, I
know
> that I have something set wrong. My guess is that either the name
=
> "UGRD"; and level = "Z10"; is incorrect for 10m winds, or the method
=
> NEAREST; width = 1; is wrong.
>
> How would I check on the name and level? And, is there a better
setting I
> should use for width? Or, is there something else I need to set?
>
> Thanks in advance!
>
> Roz
>
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 11:30:36 2017
Hi John,
Thanks for the clarification. I'll try running the code with the
verbosity
level turned up and see what happens. I'm sure I'll be back in touch
to
help deciper the output.
So, just thinking, it could be the spatial offset. The GFS is a 1 deg
grid, and the swath data is spaced every 25km. So, what happens then?
Is
there a way to fix this without interpolating the data?
Roz
On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Hi Roz,
>
> I see that you ran Point-Stat and got 0 matched pairs. Please rerun
your
> Point-Stat command using verbosity level 3 (-v 3) and write the
output to a
> log file (-log point_stat.log). Then inspect that logging output
closely,
> and you'll see sections that look something like this:
>
> DEBUG 3: Number of matched pairs = 334
>
> DEBUG 3: Observations processed = 89893
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: GRIB code = 79360
>
> DEBUG 3: Rejected: valid time = 0
>
> DEBUG 3: Rejected: bad obs value = 0
>
> DEBUG 3: Rejected: off the grid = 5
>
> DEBUG 3: Rejected: level mismatch = 9607
>
> DEBUG 3: Rejected: quality marker = 0
>
> DEBUG 3: Rejected: message type = 344
>
> DEBUG 3: Rejected: masking region = 243
>
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> With you data, you'll see that the number of matched pairs is 0.
The
> rejection counts are listed in the same order that Point-Stat uses
when
> filtering the observations. This should tell you why you're getting
0
> matched pairs. Perhaps there's a spatial offset between your
forecast and
> obs, or a time offset, or a level offset?
>
> Please take a look at that and let us know if you need help
deciphering the
> output.
>
> Thanks,
> John Halley Gotway
>
>
> On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > Queue: met_help
> > Subject: questions with using point data and the nearest
neighbor
> > setting
> > Owner: Nobody
> > Requestors: rosalyn.maccracken at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >
> >
> > Hi,
> >
> > I'm trying to do a verification between ASCAT satellite point data
of 10m
> > winds (u and v), in a swath, against 10m u and v winds from the
> > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from
prepbufr data
> to
> > netCDF format, and verified that the data is in the file, both
through
> > plotting and through ncdump. I don't want to regrid my winds. I
want to
> > keep them as point data, and compare them to the closest GFS grid
point.
> >
> > So, I'm trying to use the Point-Stat tool, with the nearest
neighbor
> > setting. I've used these settings:
> > model = "GFS";
> >
> > regrid = {
> > to_grid = NONE;
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > }
> >
> > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> >
> > fcst = {
> > field = [
> > {
> > name = "UGRD";
> > level = "Z10";
> > cat_thresh = [ >=5.0 ];
> > },
> >
> > {
> > name = "VGRD";
> > level = "Z10";
> > cat_thresh = [ >=5.0 ];
> > }
> > ];
> >
> > }
> > obs = fcst;
> >
> > message_type = [ "ASCATW" ];
> > // Verification masking regions
> > //
> > mask = {
> > grid = [ "FULL" ];
> >
> > // Interpolation methods
> > //
> > interp = {
> > vld_thresh = 1.0;
> >
> > type = [
> > {
> > method = NEAREST;
> > width = 1;
> > }
> > ];
> > }
> >
> > //////
> >
> > and the rest of the settings remained as I found them when I
copied the
> > PointStatConfig_tutorial from the default config file.
> >
> > So, this runs correctly, and produces all the necessary files that
I
> asked
> > for, but, there is nothing in the files, because there are no
matches.
> > That's hard for me to believe that there aren't any matches, so, I
know
> > that I have something set wrong. My guess is that either the name
=
> > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or the
method =
> > NEAREST; width = 1; is wrong.
> >
> > How would I check on the name and level? And, is there a better
setting
> I
> > should use for width? Or, is there something else I need to set?
> >
> > Thanks in advance!
> >
> > Roz
> >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 11:57:03 2017
Hi John,
So, I reran point-stat, and wrote it to a log file. The output for
UGRD is
below. VGRD is the same. So, I'm not sure what all this means, but,
I
have a hunch I might know what it is, and I have no idea if this is
something that can be fixed, or a work around can be found.
So, last night I was looking through the netCDF file to make sure the
data
was all there. I have a few variables, but, I really just wanted to
make
sure that lat, lon, height and values were there. The 2 variables I'm
looking at are:
obs_arr:columns = "hdr_id gc lvl hgt ob" ;
hdr_arr:columns = "lat lon elv" ;
Two lines (u and v) in the obs_arr looks like:
128947, 33, 1013, _, -8.6,
128947, 34, 1013, _, -7.2 ;
And, one line for the hdr_arr looks like this (10 is for 10m winds):
-67.92, 167.25, 10 ;
So, a couple of things come to mind, and I don't know how to fix
either.
First, in the obs_arr, the only "height" variable is the pressure
level,
1013 mb. So, is that a problem that there's no height associated with
obs_arr, only pressure? Because, I can get height from the hdr_arr.
The other thing that comes to mind is that maybe the lons in one file
go
from -180 to 180, and the other is from 0 to 360. So, could that be
the
issue?
Any thoughts?
Roz
___________
Output from logfile:
DEBUG 2: Reading data for UGRD/Z10.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
t12z.pgrbf00".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
matching VarInfo "UGRD/Z10" in GRIB file
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
0".
DEBUG 3: Use the matching forecast and observation grids.
DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181 lat_ll:
-90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
DEBUG 2: Processing masking regions.
DEBUG 3: Processing grid mask: FULL
DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2: Searching 257896 observations from 128948 messages.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for observation type
ASCATW,
over region FULL, for interpolation method NEAREST(25), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 257896
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 128948
DEBUG 3: Rejected: valid time = 71
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 76
DEBUG 3: Rejected: level mismatch = 128801
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
On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Hi Roz,
>
> I see that you ran Point-Stat and got 0 matched pairs. Please rerun
your
> Point-Stat command using verbosity level 3 (-v 3) and write the
output to a
> log file (-log point_stat.log). Then inspect that logging output
closely,
> and you'll see sections that look something like this:
>
> DEBUG 3: Number of matched pairs = 334
>
> DEBUG 3: Observations processed = 89893
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: GRIB code = 79360
>
> DEBUG 3: Rejected: valid time = 0
>
> DEBUG 3: Rejected: bad obs value = 0
>
> DEBUG 3: Rejected: off the grid = 5
>
> DEBUG 3: Rejected: level mismatch = 9607
>
> DEBUG 3: Rejected: quality marker = 0
>
> DEBUG 3: Rejected: message type = 344
>
> DEBUG 3: Rejected: masking region = 243
>
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> With you data, you'll see that the number of matched pairs is 0.
The
> rejection counts are listed in the same order that Point-Stat uses
when
> filtering the observations. This should tell you why you're getting
0
> matched pairs. Perhaps there's a spatial offset between your
forecast and
> obs, or a time offset, or a level offset?
>
> Please take a look at that and let us know if you need help
deciphering the
> output.
>
> Thanks,
> John Halley Gotway
>
>
> On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > Queue: met_help
> > Subject: questions with using point data and the nearest
neighbor
> > setting
> > Owner: Nobody
> > Requestors: rosalyn.maccracken at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >
> >
> > Hi,
> >
> > I'm trying to do a verification between ASCAT satellite point data
of 10m
> > winds (u and v), in a swath, against 10m u and v winds from the
> > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from
prepbufr data
> to
> > netCDF format, and verified that the data is in the file, both
through
> > plotting and through ncdump. I don't want to regrid my winds. I
want to
> > keep them as point data, and compare them to the closest GFS grid
point.
> >
> > So, I'm trying to use the Point-Stat tool, with the nearest
neighbor
> > setting. I've used these settings:
> > model = "GFS";
> >
> > regrid = {
> > to_grid = NONE;
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > }
> >
> > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> >
> > fcst = {
> > field = [
> > {
> > name = "UGRD";
> > level = "Z10";
> > cat_thresh = [ >=5.0 ];
> > },
> >
> > {
> > name = "VGRD";
> > level = "Z10";
> > cat_thresh = [ >=5.0 ];
> > }
> > ];
> >
> > }
> > obs = fcst;
> >
> > message_type = [ "ASCATW" ];
> > // Verification masking regions
> > //
> > mask = {
> > grid = [ "FULL" ];
> >
> > // Interpolation methods
> > //
> > interp = {
> > vld_thresh = 1.0;
> >
> > type = [
> > {
> > method = NEAREST;
> > width = 1;
> > }
> > ];
> > }
> >
> > //////
> >
> > and the rest of the settings remained as I found them when I
copied the
> > PointStatConfig_tutorial from the default config file.
> >
> > So, this runs correctly, and produces all the necessary files that
I
> asked
> > for, but, there is nothing in the files, because there are no
matches.
> > That's hard for me to believe that there aren't any matches, so, I
know
> > that I have something set wrong. My guess is that either the name
=
> > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or the
method =
> > NEAREST; width = 1; is wrong.
> >
> > How would I check on the name and level? And, is there a better
setting
> I
> > should use for width? Or, is there something else I need to set?
> >
> > Thanks in advance!
> >
> > Roz
> >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Tara Jensen
Time: Thu May 04 12:16:09 2017
Roz,
I'll jump in here as John is busy at the moment. It looks like
there's a
level mis-match occurring. As you pointed out the forecast field is
UGRD/Z10 and VGRD/Z10 and the observed field is at the surface and
mapped
to 1013 mb. Try setting the "obs dictionary" in the config to be:
obs = {
field = [
{
message_type = [ "ASCATW"];
name = "UGRD";
level = [ "P1013" ];
}
];
}
Cheers, Tara
On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA Affiliate
via RT
<met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
>
> Hi John,
>
> So, I reran point-stat, and wrote it to a log file. The output for
UGRD is
> below. VGRD is the same. So, I'm not sure what all this means,
but, I
> have a hunch I might know what it is, and I have no idea if this is
> something that can be fixed, or a work around can be found.
>
> So, last night I was looking through the netCDF file to make sure
the data
> was all there. I have a few variables, but, I really just wanted to
make
> sure that lat, lon, height and values were there. The 2 variables
I'm
> looking at are:
> obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> hdr_arr:columns = "lat lon elv" ;
>
> Two lines (u and v) in the obs_arr looks like:
> 128947, 33, 1013, _, -8.6,
> 128947, 34, 1013, _, -7.2 ;
> And, one line for the hdr_arr looks like this (10 is for 10m winds):
> -67.92, 167.25, 10 ;
>
> So, a couple of things come to mind, and I don't know how to fix
either.
> First, in the obs_arr, the only "height" variable is the pressure
level,
> 1013 mb. So, is that a problem that there's no height associated
with
> obs_arr, only pressure? Because, I can get height from the hdr_arr.
>
> The other thing that comes to mind is that maybe the lons in one
file go
> from -180 to 180, and the other is from 0 to 360. So, could that be
the
> issue?
>
> Any thoughts?
>
> Roz
> ___________
> Output from logfile:
>
> DEBUG 2: Reading data for UGRD/Z10.
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> t12z.pgrbf00".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> matching VarInfo "UGRD/Z10" in GRIB file
> "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
> 0".
> DEBUG 3: Use the matching forecast and observation grids.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0 climatology
levels.
> DEBUG 2:
> DEBUG 2:
> ------------------------------------------------------------
> --------------------
>
> DEBUG 2: Searching 257896 observations from 128948 messages.
> DEBUG 2:
> DEBUG 2:
> ------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for observation type
ASCATW,
> over region FULL, for interpolation method NEAREST(25), using 0
pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 257896
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 128948
> DEBUG 3: Rejected: valid time = 71
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 76
> DEBUG 3: Rejected: level mismatch = 128801
> 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
>
> On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> > wrote:
>
> > Hi Roz,
> >
> > I see that you ran Point-Stat and got 0 matched pairs. Please
rerun your
> > Point-Stat command using verbosity level 3 (-v 3) and write the
output
> to a
> > log file (-log point_stat.log). Then inspect that logging output
> closely,
> > and you'll see sections that look something like this:
> >
> > DEBUG 3: Number of matched pairs = 334
> >
> > DEBUG 3: Observations processed = 89893
> >
> > DEBUG 3: Rejected: SID exclusion = 0
> >
> > DEBUG 3: Rejected: GRIB code = 79360
> >
> > DEBUG 3: Rejected: valid time = 0
> >
> > DEBUG 3: Rejected: bad obs value = 0
> >
> > DEBUG 3: Rejected: off the grid = 5
> >
> > DEBUG 3: Rejected: level mismatch = 9607
> >
> > DEBUG 3: Rejected: quality marker = 0
> >
> > DEBUG 3: Rejected: message type = 344
> >
> > DEBUG 3: Rejected: masking region = 243
> >
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> >
> > With you data, you'll see that the number of matched pairs is 0.
The
> > rejection counts are listed in the same order that Point-Stat uses
when
> > filtering the observations. This should tell you why you're
getting 0
> > matched pairs. Perhaps there's a spatial offset between your
forecast
> and
> > obs, or a time offset, or a level offset?
> >
> > Please take a look at that and let us know if you need help
deciphering
> the
> > output.
> >
> > Thanks,
> > John Halley Gotway
> >
> >
> > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > Queue: met_help
> > > Subject: questions with using point data and the nearest
neighbor
> > > setting
> > > Owner: Nobody
> > > Requestors: rosalyn.maccracken at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360
> >
> > >
> > >
> > > Hi,
> > >
> > > I'm trying to do a verification between ASCAT satellite point
data of
> 10m
> > > winds (u and v), in a swath, against 10m u and v winds from the
> > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from
prepbufr
> data
> > to
> > > netCDF format, and verified that the data is in the file, both
through
> > > plotting and through ncdump. I don't want to regrid my winds.
I want
> to
> > > keep them as point data, and compare them to the closest GFS
grid
> point.
> > >
> > > So, I'm trying to use the Point-Stat tool, with the nearest
neighbor
> > > setting. I've used these settings:
> > > model = "GFS";
> > >
> > > regrid = {
> > > to_grid = NONE;
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > }
> > >
> > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > >
> > > fcst = {
> > > field = [
> > > {
> > > name = "UGRD";
> > > level = "Z10";
> > > cat_thresh = [ >=5.0 ];
> > > },
> > >
> > > {
> > > name = "VGRD";
> > > level = "Z10";
> > > cat_thresh = [ >=5.0 ];
> > > }
> > > ];
> > >
> > > }
> > > obs = fcst;
> > >
> > > message_type = [ "ASCATW" ];
> > > // Verification masking regions
> > > //
> > > mask = {
> > > grid = [ "FULL" ];
> > >
> > > // Interpolation methods
> > > //
> > > interp = {
> > > vld_thresh = 1.0;
> > >
> > > type = [
> > > {
> > > method = NEAREST;
> > > width = 1;
> > > }
> > > ];
> > > }
> > >
> > > //////
> > >
> > > and the rest of the settings remained as I found them when I
copied the
> > > PointStatConfig_tutorial from the default config file.
> > >
> > > So, this runs correctly, and produces all the necessary files
that I
> > asked
> > > for, but, there is nothing in the files, because there are no
matches.
> > > That's hard for me to believe that there aren't any matches, so,
I know
> > > that I have something set wrong. My guess is that either the
name =
> > > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or the
method =
> > > NEAREST; width = 1; is wrong.
> > >
> > > How would I check on the name and level? And, is there a better
> setting
> > I
> > > should use for width? Or, is there something else I need to
set?
> > >
> > > Thanks in advance!
> > >
> > > Roz
> > >
> > >
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
--
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 12:23:05 2017
Where is that obs dictionary? Is this in the PB2NCConfig_tutorial or
in
the PointStatConfig_tutorial? I don't see it in either. Or do I just
stick this in somewhere?
Or, is that in place of:
// Forecast and observation fields to be verified
//
fcst = {
field = [
{
name = "UGRD";
level = "Z10";
cat_thresh = [ >=1.0 ];
},
{
name = "VGRD";
level = "Z10";
cat_thresh = [ >=1.0 ];
}
];
}
obs = fcst;
Roz
On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT <met_help at ucar.edu>
wrote:
> Roz,
>
> I'll jump in here as John is busy at the moment. It looks like
there's a
> level mis-match occurring. As you pointed out the forecast field is
> UGRD/Z10 and VGRD/Z10 and the observed field is at the surface and
mapped
> to 1013 mb. Try setting the "obs dictionary" in the config to be:
>
> obs = {
> field = [
> {
> message_type = [ "ASCATW"];
> name = "UGRD";
> level = [ "P1013" ];
> }
> ];
> }
>
> Cheers, Tara
>
>
> On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >
> > Hi John,
> >
> > So, I reran point-stat, and wrote it to a log file. The output
for UGRD
> is
> > below. VGRD is the same. So, I'm not sure what all this means,
but, I
> > have a hunch I might know what it is, and I have no idea if this
is
> > something that can be fixed, or a work around can be found.
> >
> > So, last night I was looking through the netCDF file to make sure
the
> data
> > was all there. I have a few variables, but, I really just wanted
to make
> > sure that lat, lon, height and values were there. The 2 variables
I'm
> > looking at are:
> > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> > hdr_arr:columns = "lat lon elv" ;
> >
> > Two lines (u and v) in the obs_arr looks like:
> > 128947, 33, 1013, _, -8.6,
> > 128947, 34, 1013, _, -7.2 ;
> > And, one line for the hdr_arr looks like this (10 is for 10m
winds):
> > -67.92, 167.25, 10 ;
> >
> > So, a couple of things come to mind, and I don't know how to fix
either.
> > First, in the obs_arr, the only "height" variable is the pressure
level,
> > 1013 mb. So, is that a problem that there's no height associated
with
> > obs_arr, only pressure? Because, I can get height from the
hdr_arr.
> >
> > The other thing that comes to mind is that maybe the lons in one
file go
> > from -180 to 180, and the other is from 0 to 360. So, could that
be the
> > issue?
> >
> > Any thoughts?
> >
> > Roz
> > ___________
> > Output from logfile:
> >
> > DEBUG 2: Reading data for UGRD/Z10.
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> > t12z.pgrbf00".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> > matching VarInfo "UGRD/Z10" in GRIB file
> > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
> > 0".
> > DEBUG 3: Use the matching forecast and observation grids.
> > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0 climatology
levels.
> > DEBUG 2:
> > DEBUG 2:
> > ------------------------------------------------------------
> > --------------------
> >
> > DEBUG 2: Searching 257896 observations from 128948 messages.
> > DEBUG 2:
> > DEBUG 2:
> > ------------------------------------------------------------
> > --------------------
> > DEBUG 2:
> > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for observation type
> ASCATW,
> > over region FULL, for interpolation method NEAREST(25), using 0
pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 257896
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: GRIB code = 128948
> > DEBUG 3: Rejected: valid time = 71
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 76
> > DEBUG 3: Rejected: level mismatch = 128801
> > 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
> >
> > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > > Hi Roz,
> > >
> > > I see that you ran Point-Stat and got 0 matched pairs. Please
rerun
> your
> > > Point-Stat command using verbosity level 3 (-v 3) and write the
output
> > to a
> > > log file (-log point_stat.log). Then inspect that logging
output
> > closely,
> > > and you'll see sections that look something like this:
> > >
> > > DEBUG 3: Number of matched pairs = 334
> > >
> > > DEBUG 3: Observations processed = 89893
> > >
> > > DEBUG 3: Rejected: SID exclusion = 0
> > >
> > > DEBUG 3: Rejected: GRIB code = 79360
> > >
> > > DEBUG 3: Rejected: valid time = 0
> > >
> > > DEBUG 3: Rejected: bad obs value = 0
> > >
> > > DEBUG 3: Rejected: off the grid = 5
> > >
> > > DEBUG 3: Rejected: level mismatch = 9607
> > >
> > > DEBUG 3: Rejected: quality marker = 0
> > >
> > > DEBUG 3: Rejected: message type = 344
> > >
> > > DEBUG 3: Rejected: masking region = 243
> > >
> > > DEBUG 3: Rejected: bad fcst value = 0
> > > DEBUG 3: Rejected: duplicates = 0
> > >
> > > With you data, you'll see that the number of matched pairs is 0.
The
> > > rejection counts are listed in the same order that Point-Stat
uses when
> > > filtering the observations. This should tell you why you're
getting 0
> > > matched pairs. Perhaps there's a spatial offset between your
forecast
> > and
> > > obs, or a time offset, or a level offset?
> > >
> > > Please take a look at that and let us know if you need help
deciphering
> > the
> > > output.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > >
> > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA
Affiliate via
> > RT
> > > <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > Queue: met_help
> > > > Subject: questions with using point data and the nearest
> neighbor
> > > > setting
> > > > Owner: Nobody
> > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=80360
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm trying to do a verification between ASCAT satellite point
data of
> > 10m
> > > > winds (u and v), in a swath, against 10m u and v winds from
the
> > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from
prepbufr
> > data
> > > to
> > > > netCDF format, and verified that the data is in the file, both
> through
> > > > plotting and through ncdump. I don't want to regrid my winds.
I
> want
> > to
> > > > keep them as point data, and compare them to the closest GFS
grid
> > point.
> > > >
> > > > So, I'm trying to use the Point-Stat tool, with the nearest
neighbor
> > > > setting. I've used these settings:
> > > > model = "GFS";
> > > >
> > > > regrid = {
> > > > to_grid = NONE;
> > > > method = NEAREST;
> > > > width = 1;
> > > > vld_thresh = 0.5;
> > > > }
> > > >
> > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > > >
> > > > fcst = {
> > > > field = [
> > > > {
> > > > name = "UGRD";
> > > > level = "Z10";
> > > > cat_thresh = [ >=5.0 ];
> > > > },
> > > >
> > > > {
> > > > name = "VGRD";
> > > > level = "Z10";
> > > > cat_thresh = [ >=5.0 ];
> > > > }
> > > > ];
> > > >
> > > > }
> > > > obs = fcst;
> > > >
> > > > message_type = [ "ASCATW" ];
> > > > // Verification masking regions
> > > > //
> > > > mask = {
> > > > grid = [ "FULL" ];
> > > >
> > > > // Interpolation methods
> > > > //
> > > > interp = {
> > > > vld_thresh = 1.0;
> > > >
> > > > type = [
> > > > {
> > > > method = NEAREST;
> > > > width = 1;
> > > > }
> > > > ];
> > > > }
> > > >
> > > > //////
> > > >
> > > > and the rest of the settings remained as I found them when I
copied
> the
> > > > PointStatConfig_tutorial from the default config file.
> > > >
> > > > So, this runs correctly, and produces all the necessary files
that I
> > > asked
> > > > for, but, there is nothing in the files, because there are no
> matches.
> > > > That's hard for me to believe that there aren't any matches,
so, I
> know
> > > > that I have something set wrong. My guess is that either the
name =
> > > > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or the
method
> =
> > > > NEAREST; width = 1; is wrong.
> > > >
> > > > How would I check on the name and level? And, is there a
better
> > setting
> > > I
> > > > should use for width? Or, is there something else I need to
set?
> > > >
> > > > Thanks in advance!
> > > >
> > > > Roz
> > > >
> > > >
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
> --
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Tara Jensen
Time: Thu May 04 12:29:48 2017
Roz,
Sorry I didn't make it clear. Replace obs=fcst; with
obs = {
field = [
{
message_type = [ "ASCATW"];
name = "UGRD";
level = [ "P1013" ];
cat_thresh = [ >=5.0 ]; }
];
}
NOTE: I notice I missed that you have a cat_thresh listed in the
"forecast
dictionary" so added it to the recommended obs dictionary.
Tara
On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA Affiliate
via RT
<met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
>
> Where is that obs dictionary? Is this in the PB2NCConfig_tutorial
or in
> the PointStatConfig_tutorial? I don't see it in either. Or do I
just
> stick this in somewhere?
>
> Or, is that in place of:
> // Forecast and observation fields to be verified
> //
> fcst = {
> field = [
> {
> name = "UGRD";
> level = "Z10";
> cat_thresh = [ >=1.0 ];
> },
>
> {
> name = "VGRD";
> level = "Z10";
> cat_thresh = [ >=1.0 ];
> }
> ];
>
> }
> obs = fcst;
>
> Roz
>
> On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT
<met_help at ucar.edu>
> wrote:
>
> > Roz,
> >
> > I'll jump in here as John is busy at the moment. It looks like
there's a
> > level mis-match occurring. As you pointed out the forecast field
is
> > UGRD/Z10 and VGRD/Z10 and the observed field is at the surface and
mapped
> > to 1013 mb. Try setting the "obs dictionary" in the config to be:
> >
> > obs = {
> > field = [
> > {
> > message_type = [ "ASCATW"];
> > name = "UGRD";
> > level = [ "P1013" ];
> > }
> > ];
> > }
> >
> > Cheers, Tara
> >
> >
> > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> > >
> > > Hi John,
> > >
> > > So, I reran point-stat, and wrote it to a log file. The output
for
> UGRD
> > is
> > > below. VGRD is the same. So, I'm not sure what all this means,
but, I
> > > have a hunch I might know what it is, and I have no idea if this
is
> > > something that can be fixed, or a work around can be found.
> > >
> > > So, last night I was looking through the netCDF file to make
sure the
> > data
> > > was all there. I have a few variables, but, I really just
wanted to
> make
> > > sure that lat, lon, height and values were there. The 2
variables I'm
> > > looking at are:
> > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> > > hdr_arr:columns = "lat lon elv" ;
> > >
> > > Two lines (u and v) in the obs_arr looks like:
> > > 128947, 33, 1013, _, -8.6,
> > > 128947, 34, 1013, _, -7.2 ;
> > > And, one line for the hdr_arr looks like this (10 is for 10m
winds):
> > > -67.92, 167.25, 10 ;
> > >
> > > So, a couple of things come to mind, and I don't know how to fix
> either.
> > > First, in the obs_arr, the only "height" variable is the
pressure
> level,
> > > 1013 mb. So, is that a problem that there's no height
associated with
> > > obs_arr, only pressure? Because, I can get height from the
hdr_arr.
> > >
> > > The other thing that comes to mind is that maybe the lons in one
file
> go
> > > from -180 to 180, and the other is from 0 to 360. So, could
that be
> the
> > > issue?
> > >
> > > Any thoughts?
> > >
> > > Roz
> > > ___________
> > > Output from logfile:
> > >
> > > DEBUG 2: Reading data for UGRD/Z10.
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match for
> > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> > > t12z.pgrbf00".
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> > > matching VarInfo "UGRD/Z10" in GRIB file
> > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
> > > 0".
> > > DEBUG 3: Use the matching forecast and observation grids.
> > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> > > DEBUG 2: Processing masking regions.
> > > DEBUG 3: Processing grid mask: FULL
> > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0 climatology
levels.
> > > DEBUG 2:
> > > DEBUG 2:
> > > ------------------------------------------------------------
> > > --------------------
> > >
> > > DEBUG 2: Searching 257896 observations from 128948 messages.
> > > DEBUG 2:
> > > DEBUG 2:
> > > ------------------------------------------------------------
> > > --------------------
> > > DEBUG 2:
> > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for observation
type
> > ASCATW,
> > > over region FULL, for interpolation method NEAREST(25), using 0
pairs.
> > > DEBUG 3: Number of matched pairs = 0
> > > DEBUG 3: Observations processed = 257896
> > > DEBUG 3: Rejected: SID exclusion = 0
> > > DEBUG 3: Rejected: GRIB code = 128948
> > > DEBUG 3: Rejected: valid time = 71
> > > DEBUG 3: Rejected: bad obs value = 0
> > > DEBUG 3: Rejected: off the grid = 76
> > > DEBUG 3: Rejected: level mismatch = 128801
> > > 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
> > >
> > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu
> > > > wrote:
> > >
> > > > Hi Roz,
> > > >
> > > > I see that you ran Point-Stat and got 0 matched pairs. Please
rerun
> > your
> > > > Point-Stat command using verbosity level 3 (-v 3) and write
the
> output
> > > to a
> > > > log file (-log point_stat.log). Then inspect that logging
output
> > > closely,
> > > > and you'll see sections that look something like this:
> > > >
> > > > DEBUG 3: Number of matched pairs = 334
> > > >
> > > > DEBUG 3: Observations processed = 89893
> > > >
> > > > DEBUG 3: Rejected: SID exclusion = 0
> > > >
> > > > DEBUG 3: Rejected: GRIB code = 79360
> > > >
> > > > DEBUG 3: Rejected: valid time = 0
> > > >
> > > > DEBUG 3: Rejected: bad obs value = 0
> > > >
> > > > DEBUG 3: Rejected: off the grid = 5
> > > >
> > > > DEBUG 3: Rejected: level mismatch = 9607
> > > >
> > > > DEBUG 3: Rejected: quality marker = 0
> > > >
> > > > DEBUG 3: Rejected: message type = 344
> > > >
> > > > DEBUG 3: Rejected: masking region = 243
> > > >
> > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > DEBUG 3: Rejected: duplicates = 0
> > > >
> > > > With you data, you'll see that the number of matched pairs is
0. The
> > > > rejection counts are listed in the same order that Point-Stat
uses
> when
> > > > filtering the observations. This should tell you why you're
getting
> 0
> > > > matched pairs. Perhaps there's a spatial offset between your
> forecast
> > > and
> > > > obs, or a time offset, or a level offset?
> > > >
> > > > Please take a look at that and let us know if you need help
> deciphering
> > > the
> > > > output.
> > > >
> > > > Thanks,
> > > > John Halley Gotway
> > > >
> > > >
> > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA
Affiliate
> via
> > > RT
> > > > <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> > > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: questions with using point data and the
nearest
> > neighbor
> > > > > setting
> > > > > Owner: Nobody
> > > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=80360
> > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm trying to do a verification between ASCAT satellite
point data
> of
> > > 10m
> > > > > winds (u and v), in a swath, against 10m u and v winds from
the
> > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from
prepbufr
> > > data
> > > > to
> > > > > netCDF format, and verified that the data is in the file,
both
> > through
> > > > > plotting and through ncdump. I don't want to regrid my
winds. I
> > want
> > > to
> > > > > keep them as point data, and compare them to the closest GFS
grid
> > > point.
> > > > >
> > > > > So, I'm trying to use the Point-Stat tool, with the nearest
> neighbor
> > > > > setting. I've used these settings:
> > > > > model = "GFS";
> > > > >
> > > > > regrid = {
> > > > > to_grid = NONE;
> > > > > method = NEAREST;
> > > > > width = 1;
> > > > > vld_thresh = 0.5;
> > > > > }
> > > > >
> > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > > > >
> > > > > fcst = {
> > > > > field = [
> > > > > {
> > > > > name = "UGRD";
> > > > > level = "Z10";
> > > > > cat_thresh = [ >=5.0 ];
> > > > > },
> > > > >
> > > > > {
> > > > > name = "VGRD";
> > > > > level = "Z10";
> > > > > cat_thresh = [ >=5.0 ];
> > > > > }
> > > > > ];
> > > > >
> > > > > }
> > > > > obs = fcst;
> > > > >
> > > > > message_type = [ "ASCATW" ];
> > > > > // Verification masking regions
> > > > > //
> > > > > mask = {
> > > > > grid = [ "FULL" ];
> > > > >
> > > > > // Interpolation methods
> > > > > //
> > > > > interp = {
> > > > > vld_thresh = 1.0;
> > > > >
> > > > > type = [
> > > > > {
> > > > > method = NEAREST;
> > > > > width = 1;
> > > > > }
> > > > > ];
> > > > > }
> > > > >
> > > > > //////
> > > > >
> > > > > and the rest of the settings remained as I found them when I
copied
> > the
> > > > > PointStatConfig_tutorial from the default config file.
> > > > >
> > > > > So, this runs correctly, and produces all the necessary
files that
> I
> > > > asked
> > > > > for, but, there is nothing in the files, because there are
no
> > matches.
> > > > > That's hard for me to believe that there aren't any matches,
so, I
> > know
> > > > > that I have something set wrong. My guess is that either
the
> name =
> > > > > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or
the
> method
> > =
> > > > > NEAREST; width = 1; is wrong.
> > > > >
> > > > > How would I check on the name and level? And, is there a
better
> > > setting
> > > > I
> > > > > should use for width? Or, is there something else I need to
set?
> > > > >
> > > > > Thanks in advance!
> > > > >
> > > > > Roz
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Rosalyn MacCracken
> > > > > Support Scientist
> > > > >
> > > > > Ocean Applilcations Branch
> > > > > NOAA/NWS Ocean Prediction Center
> > > > > NCWCP
> > > > > 5830 University Research Ct
> > > > > College Park, MD 20740-3818
> > > > >
> > > > > (p) 301-683-1551
> > > > > rosalyn.maccracken at noaa.gov
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
> > --
> >
> >
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tara Jensen
Project Manager II
NCAR RAL and DTC
PO Box 3000, Boulder, Colorado 80307 USA
+1 303-497-8479 jensen at ucar.edu
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 12:32:01 2017
Ok, got it. I'll try that and let you know how things worked.
Thanks for the help!
Roz
On Thu, May 4, 2017 at 2:29 PM, Tara Jensen via RT <met_help at ucar.edu>
wrote:
> Roz,
>
> Sorry I didn't make it clear. Replace obs=fcst; with
>
> obs = {
> field = [
> {
> message_type = [ "ASCATW"];
> name = "UGRD";
> level = [ "P1013" ];
> cat_thresh = [ >=5.0 ]; }
> ];
> }
>
> NOTE: I notice I missed that you have a cat_thresh listed in the
"forecast
> dictionary" so added it to the recommended obs dictionary.
>
> Tara
>
>
> On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >
> > Where is that obs dictionary? Is this in the PB2NCConfig_tutorial
or in
> > the PointStatConfig_tutorial? I don't see it in either. Or do I
just
> > stick this in somewhere?
> >
> > Or, is that in place of:
> > // Forecast and observation fields to be verified
> > //
> > fcst = {
> > field = [
> > {
> > name = "UGRD";
> > level = "Z10";
> > cat_thresh = [ >=1.0 ];
> > },
> >
> > {
> > name = "VGRD";
> > level = "Z10";
> > cat_thresh = [ >=1.0 ];
> > }
> > ];
> >
> > }
> > obs = fcst;
> >
> > Roz
> >
> > On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Roz,
> > >
> > > I'll jump in here as John is busy at the moment. It looks like
> there's a
> > > level mis-match occurring. As you pointed out the forecast
field is
> > > UGRD/Z10 and VGRD/Z10 and the observed field is at the surface
and
> mapped
> > > to 1013 mb. Try setting the "obs dictionary" in the config to
be:
> > >
> > > obs = {
> > > field = [
> > > {
> > > message_type = [ "ASCATW"];
> > > name = "UGRD";
> > > level = [ "P1013" ];
> > > }
> > > ];
> > > }
> > >
> > > Cheers, Tara
> > >
> > >
> > > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA
Affiliate
> via
> > RT
> > > <met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360
>
> > > >
> > > > Hi John,
> > > >
> > > > So, I reran point-stat, and wrote it to a log file. The
output for
> > UGRD
> > > is
> > > > below. VGRD is the same. So, I'm not sure what all this
means,
> but, I
> > > > have a hunch I might know what it is, and I have no idea if
this is
> > > > something that can be fixed, or a work around can be found.
> > > >
> > > > So, last night I was looking through the netCDF file to make
sure the
> > > data
> > > > was all there. I have a few variables, but, I really just
wanted to
> > make
> > > > sure that lat, lon, height and values were there. The 2
variables
> I'm
> > > > looking at are:
> > > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> > > > hdr_arr:columns = "lat lon elv" ;
> > > >
> > > > Two lines (u and v) in the obs_arr looks like:
> > > > 128947, 33, 1013, _, -8.6,
> > > > 128947, 34, 1013, _, -7.2 ;
> > > > And, one line for the hdr_arr looks like this (10 is for 10m
winds):
> > > > -67.92, 167.25, 10 ;
> > > >
> > > > So, a couple of things come to mind, and I don't know how to
fix
> > either.
> > > > First, in the obs_arr, the only "height" variable is the
pressure
> > level,
> > > > 1013 mb. So, is that a problem that there's no height
associated
> with
> > > > obs_arr, only pressure? Because, I can get height from the
hdr_arr.
> > > >
> > > > The other thing that comes to mind is that maybe the lons in
one file
> > go
> > > > from -180 to 180, and the other is from 0 to 360. So, could
that be
> > the
> > > > issue?
> > > >
> > > > Any thoughts?
> > > >
> > > > Roz
> > > > ___________
> > > > Output from logfile:
> > > >
> > > > DEBUG 2: Reading data for UGRD/Z10.
> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
> for
> > > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> > > > t12z.pgrbf00".
> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
> records
> > > > matching VarInfo "UGRD/Z10" in GRIB file
> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
> > > > 0".
> > > > DEBUG 3: Use the matching forecast and observation grids.
> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> > > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> > > > DEBUG 2: Processing masking regions.
> > > > DEBUG 3: Processing grid mask: FULL
> > > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0
climatology
> levels.
> > > > DEBUG 2:
> > > > DEBUG 2:
> > > > ------------------------------------------------------------
> > > > --------------------
> > > >
> > > > DEBUG 2: Searching 257896 observations from 128948 messages.
> > > > DEBUG 2:
> > > > DEBUG 2:
> > > > ------------------------------------------------------------
> > > > --------------------
> > > > DEBUG 2:
> > > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for observation
type
> > > ASCATW,
> > > > over region FULL, for interpolation method NEAREST(25), using
0
> pairs.
> > > > DEBUG 3: Number of matched pairs = 0
> > > > DEBUG 3: Observations processed = 257896
> > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > DEBUG 3: Rejected: GRIB code = 128948
> > > > DEBUG 3: Rejected: valid time = 71
> > > > DEBUG 3: Rejected: bad obs value = 0
> > > > DEBUG 3: Rejected: off the grid = 76
> > > > DEBUG 3: Rejected: level mismatch = 128801
> > > > 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
> > > >
> > > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT <
> > > > met_help at ucar.edu
> > > > > wrote:
> > > >
> > > > > Hi Roz,
> > > > >
> > > > > I see that you ran Point-Stat and got 0 matched pairs.
Please
> rerun
> > > your
> > > > > Point-Stat command using verbosity level 3 (-v 3) and write
the
> > output
> > > > to a
> > > > > log file (-log point_stat.log). Then inspect that logging
output
> > > > closely,
> > > > > and you'll see sections that look something like this:
> > > > >
> > > > > DEBUG 3: Number of matched pairs = 334
> > > > >
> > > > > DEBUG 3: Observations processed = 89893
> > > > >
> > > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > >
> > > > > DEBUG 3: Rejected: GRIB code = 79360
> > > > >
> > > > > DEBUG 3: Rejected: valid time = 0
> > > > >
> > > > > DEBUG 3: Rejected: bad obs value = 0
> > > > >
> > > > > DEBUG 3: Rejected: off the grid = 5
> > > > >
> > > > > DEBUG 3: Rejected: level mismatch = 9607
> > > > >
> > > > > DEBUG 3: Rejected: quality marker = 0
> > > > >
> > > > > DEBUG 3: Rejected: message type = 344
> > > > >
> > > > > DEBUG 3: Rejected: masking region = 243
> > > > >
> > > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > > DEBUG 3: Rejected: duplicates = 0
> > > > >
> > > > > With you data, you'll see that the number of matched pairs
is 0.
> The
> > > > > rejection counts are listed in the same order that Point-
Stat uses
> > when
> > > > > filtering the observations. This should tell you why you're
> getting
> > 0
> > > > > matched pairs. Perhaps there's a spatial offset between
your
> > forecast
> > > > and
> > > > > obs, or a time offset, or a level offset?
> > > > >
> > > > > Please take a look at that and let us know if you need help
> > deciphering
> > > > the
> > > > > output.
> > > > >
> > > > > Thanks,
> > > > > John Halley Gotway
> > > > >
> > > > >
> > > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA
Affiliate
> > via
> > > > RT
> > > > > <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> > > > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > > > Queue: met_help
> > > > > > Subject: questions with using point data and the
nearest
> > > neighbor
> > > > > > setting
> > > > > > Owner: Nobody
> > > > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > > > Status: new
> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=80360
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm trying to do a verification between ASCAT satellite
point
> data
> > of
> > > > 10m
> > > > > > winds (u and v), in a swath, against 10m u and v winds
from the
> > > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data from
> prepbufr
> > > > data
> > > > > to
> > > > > > netCDF format, and verified that the data is in the file,
both
> > > through
> > > > > > plotting and through ncdump. I don't want to regrid my
winds. I
> > > want
> > > > to
> > > > > > keep them as point data, and compare them to the closest
GFS grid
> > > > point.
> > > > > >
> > > > > > So, I'm trying to use the Point-Stat tool, with the
nearest
> > neighbor
> > > > > > setting. I've used these settings:
> > > > > > model = "GFS";
> > > > > >
> > > > > > regrid = {
> > > > > > to_grid = NONE;
> > > > > > method = NEAREST;
> > > > > > width = 1;
> > > > > > vld_thresh = 0.5;
> > > > > > }
> > > > > >
> > > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > > > > >
> > > > > > fcst = {
> > > > > > field = [
> > > > > > {
> > > > > > name = "UGRD";
> > > > > > level = "Z10";
> > > > > > cat_thresh = [ >=5.0 ];
> > > > > > },
> > > > > >
> > > > > > {
> > > > > > name = "VGRD";
> > > > > > level = "Z10";
> > > > > > cat_thresh = [ >=5.0 ];
> > > > > > }
> > > > > > ];
> > > > > >
> > > > > > }
> > > > > > obs = fcst;
> > > > > >
> > > > > > message_type = [ "ASCATW" ];
> > > > > > // Verification masking regions
> > > > > > //
> > > > > > mask = {
> > > > > > grid = [ "FULL" ];
> > > > > >
> > > > > > // Interpolation methods
> > > > > > //
> > > > > > interp = {
> > > > > > vld_thresh = 1.0;
> > > > > >
> > > > > > type = [
> > > > > > {
> > > > > > method = NEAREST;
> > > > > > width = 1;
> > > > > > }
> > > > > > ];
> > > > > > }
> > > > > >
> > > > > > //////
> > > > > >
> > > > > > and the rest of the settings remained as I found them when
I
> copied
> > > the
> > > > > > PointStatConfig_tutorial from the default config file.
> > > > > >
> > > > > > So, this runs correctly, and produces all the necessary
files
> that
> > I
> > > > > asked
> > > > > > for, but, there is nothing in the files, because there are
no
> > > matches.
> > > > > > That's hard for me to believe that there aren't any
matches, so,
> I
> > > know
> > > > > > that I have something set wrong. My guess is that either
the
> > name =
> > > > > > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or
the
> > method
> > > =
> > > > > > NEAREST; width = 1; is wrong.
> > > > > >
> > > > > > How would I check on the name and level? And, is there a
better
> > > > setting
> > > > > I
> > > > > > should use for width? Or, is there something else I need
to set?
> > > > > >
> > > > > > Thanks in advance!
> > > > > >
> > > > > > Roz
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Rosalyn MacCracken
> > > > > > Support Scientist
> > > > > >
> > > > > > Ocean Applilcations Branch
> > > > > > NOAA/NWS Ocean Prediction Center
> > > > > > NCWCP
> > > > > > 5830 University Research Ct
> > > > > > College Park, MD 20740-3818
> > > > > >
> > > > > > (p) 301-683-1551
> > > > > > rosalyn.maccracken at noaa.gov
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tara Jensen
> Project Manager II
> NCAR RAL and DTC
> PO Box 3000, Boulder, Colorado 80307 USA
> +1 303-497-8479 jensen at ucar.edu
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 12:39:28 2017
Oh, grrrr...I got the error:
ERROR : PointStatConfInfo::process_config() -> The number of
verification
tasks in "obs.field" must be non-zero and match the number in
"fcst.field".
Any ideas?
roz
On Thu, May 4, 2017 at 2:31 PM, Rosalyn MacCracken - NOAA Affiliate <
rosalyn.maccracken at noaa.gov> wrote:
> Ok, got it. I'll try that and let you know how things worked.
>
> Thanks for the help!
>
> Roz
>
> On Thu, May 4, 2017 at 2:29 PM, Tara Jensen via RT
<met_help at ucar.edu>
> wrote:
>
>> Roz,
>>
>> Sorry I didn't make it clear. Replace obs=fcst; with
>>
>> obs = {
>> field = [
>> {
>> message_type = [ "ASCATW"];
>> name = "UGRD";
>> level = [ "P1013" ];
>> cat_thresh = [ >=5.0 ]; }
>> ];
>> }
>>
>> NOTE: I notice I missed that you have a cat_thresh listed in the
>> "forecast
>> dictionary" so added it to the recommended obs dictionary.
>>
>> Tara
>>
>>
>> On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA
Affiliate via
>> RT
>> <met_help at ucar.edu> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
>> >
>> > Where is that obs dictionary? Is this in the
PB2NCConfig_tutorial or
>> in
>> > the PointStatConfig_tutorial? I don't see it in either. Or do I
just
>> > stick this in somewhere?
>> >
>> > Or, is that in place of:
>> > // Forecast and observation fields to be verified
>> > //
>> > fcst = {
>> > field = [
>> > {
>> > name = "UGRD";
>> > level = "Z10";
>> > cat_thresh = [ >=1.0 ];
>> > },
>> >
>> > {
>> > name = "VGRD";
>> > level = "Z10";
>> > cat_thresh = [ >=1.0 ];
>> > }
>> > ];
>> >
>> > }
>> > obs = fcst;
>> >
>> > Roz
>> >
>> > On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT
<met_help at ucar.edu>
>> > wrote:
>> >
>> > > Roz,
>> > >
>> > > I'll jump in here as John is busy at the moment. It looks like
>> there's a
>> > > level mis-match occurring. As you pointed out the forecast
field is
>> > > UGRD/Z10 and VGRD/Z10 and the observed field is at the surface
and
>> mapped
>> > > to 1013 mb. Try setting the "obs dictionary" in the config to
be:
>> > >
>> > > obs = {
>> > > field = [
>> > > {
>> > > message_type = [ "ASCATW"];
>> > > name = "UGRD";
>> > > level = [ "P1013" ];
>> > > }
>> > > ];
>> > > }
>> > >
>> > > Cheers, Tara
>> > >
>> > >
>> > > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA
Affiliate
>> via
>> > RT
>> > > <met_help at ucar.edu> wrote:
>> > >
>> > > >
>> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360
>
>> > > >
>> > > > Hi John,
>> > > >
>> > > > So, I reran point-stat, and wrote it to a log file. The
output for
>> > UGRD
>> > > is
>> > > > below. VGRD is the same. So, I'm not sure what all this
means,
>> but, I
>> > > > have a hunch I might know what it is, and I have no idea if
this is
>> > > > something that can be fixed, or a work around can be found.
>> > > >
>> > > > So, last night I was looking through the netCDF file to make
sure
>> the
>> > > data
>> > > > was all there. I have a few variables, but, I really just
wanted to
>> > make
>> > > > sure that lat, lon, height and values were there. The 2
variables
>> I'm
>> > > > looking at are:
>> > > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
>> > > > hdr_arr:columns = "lat lon elv" ;
>> > > >
>> > > > Two lines (u and v) in the obs_arr looks like:
>> > > > 128947, 33, 1013, _, -8.6,
>> > > > 128947, 34, 1013, _, -7.2 ;
>> > > > And, one line for the hdr_arr looks like this (10 is for 10m
winds):
>> > > > -67.92, 167.25, 10 ;
>> > > >
>> > > > So, a couple of things come to mind, and I don't know how to
fix
>> > either.
>> > > > First, in the obs_arr, the only "height" variable is the
pressure
>> > level,
>> > > > 1013 mb. So, is that a problem that there's no height
associated
>> with
>> > > > obs_arr, only pressure? Because, I can get height from the
hdr_arr.
>> > > >
>> > > > The other thing that comes to mind is that maybe the lons in
one
>> file
>> > go
>> > > > from -180 to 180, and the other is from 0 to 360. So, could
that be
>> > the
>> > > > issue?
>> > > >
>> > > > Any thoughts?
>> > > >
>> > > > Roz
>> > > > ___________
>> > > > Output from logfile:
>> > > >
>> > > > DEBUG 2: Reading data for UGRD/Z10.
>> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
>> for
>> > > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
>> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
>> > > > t12z.pgrbf00".
>> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
>> records
>> > > > matching VarInfo "UGRD/Z10" in GRIB file
>> > > >
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
>> > > > 0".
>> > > > DEBUG 3: Use the matching forecast and observation grids.
>> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
>> lat_ll:
>> > > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
>> > > > DEBUG 2: Processing masking regions.
>> > > > DEBUG 3: Processing grid mask: FULL
>> > > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0
climatology
>> levels.
>> > > > DEBUG 2:
>> > > > DEBUG 2:
>> > > > ------------------------------------------------------------
>> > > > --------------------
>> > > >
>> > > > DEBUG 2: Searching 257896 observations from 128948 messages.
>> > > > DEBUG 2:
>> > > > DEBUG 2:
>> > > > ------------------------------------------------------------
>> > > > --------------------
>> > > > DEBUG 2:
>> > > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for observation
type
>> > > ASCATW,
>> > > > over region FULL, for interpolation method NEAREST(25), using
0
>> pairs.
>> > > > DEBUG 3: Number of matched pairs = 0
>> > > > DEBUG 3: Observations processed = 257896
>> > > > DEBUG 3: Rejected: SID exclusion = 0
>> > > > DEBUG 3: Rejected: GRIB code = 128948
>> > > > DEBUG 3: Rejected: valid time = 71
>> > > > DEBUG 3: Rejected: bad obs value = 0
>> > > > DEBUG 3: Rejected: off the grid = 76
>> > > > DEBUG 3: Rejected: level mismatch = 128801
>> > > > 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
>> > > >
>> > > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT <
>> > > > met_help at ucar.edu
>> > > > > wrote:
>> > > >
>> > > > > Hi Roz,
>> > > > >
>> > > > > I see that you ran Point-Stat and got 0 matched pairs.
Please
>> rerun
>> > > your
>> > > > > Point-Stat command using verbosity level 3 (-v 3) and write
the
>> > output
>> > > > to a
>> > > > > log file (-log point_stat.log). Then inspect that logging
output
>> > > > closely,
>> > > > > and you'll see sections that look something like this:
>> > > > >
>> > > > > DEBUG 3: Number of matched pairs = 334
>> > > > >
>> > > > > DEBUG 3: Observations processed = 89893
>> > > > >
>> > > > > DEBUG 3: Rejected: SID exclusion = 0
>> > > > >
>> > > > > DEBUG 3: Rejected: GRIB code = 79360
>> > > > >
>> > > > > DEBUG 3: Rejected: valid time = 0
>> > > > >
>> > > > > DEBUG 3: Rejected: bad obs value = 0
>> > > > >
>> > > > > DEBUG 3: Rejected: off the grid = 5
>> > > > >
>> > > > > DEBUG 3: Rejected: level mismatch = 9607
>> > > > >
>> > > > > DEBUG 3: Rejected: quality marker = 0
>> > > > >
>> > > > > DEBUG 3: Rejected: message type = 344
>> > > > >
>> > > > > DEBUG 3: Rejected: masking region = 243
>> > > > >
>> > > > > DEBUG 3: Rejected: bad fcst value = 0
>> > > > > DEBUG 3: Rejected: duplicates = 0
>> > > > >
>> > > > > With you data, you'll see that the number of matched pairs
is 0.
>> The
>> > > > > rejection counts are listed in the same order that Point-
Stat uses
>> > when
>> > > > > filtering the observations. This should tell you why
you're
>> getting
>> > 0
>> > > > > matched pairs. Perhaps there's a spatial offset between
your
>> > forecast
>> > > > and
>> > > > > obs, or a time offset, or a level offset?
>> > > > >
>> > > > > Please take a look at that and let us know if you need help
>> > deciphering
>> > > > the
>> > > > > output.
>> > > > >
>> > > > > Thanks,
>> > > > > John Halley Gotway
>> > > > >
>> > > > >
>> > > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA
>> Affiliate
>> > via
>> > > > RT
>> > > > > <
>> > > > > met_help at ucar.edu> wrote:
>> > > > >
>> > > > > >
>> > > > > > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
>> > > > > > Transaction: Ticket created by
rosalyn.maccracken at noaa.gov
>> > > > > > Queue: met_help
>> > > > > > Subject: questions with using point data and the
nearest
>> > > neighbor
>> > > > > > setting
>> > > > > > Owner: Nobody
>> > > > > > Requestors: rosalyn.maccracken at noaa.gov
>> > > > > > Status: new
>> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
>> > > Ticket/Display.html?id=80360
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > I'm trying to do a verification between ASCAT satellite
point
>> data
>> > of
>> > > > 10m
>> > > > > > winds (u and v), in a swath, against 10m u and v winds
from the
>> > > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data
from
>> prepbufr
>> > > > data
>> > > > > to
>> > > > > > netCDF format, and verified that the data is in the file,
both
>> > > through
>> > > > > > plotting and through ncdump. I don't want to regrid my
winds.
>> I
>> > > want
>> > > > to
>> > > > > > keep them as point data, and compare them to the closest
GFS
>> grid
>> > > > point.
>> > > > > >
>> > > > > > So, I'm trying to use the Point-Stat tool, with the
nearest
>> > neighbor
>> > > > > > setting. I've used these settings:
>> > > > > > model = "GFS";
>> > > > > >
>> > > > > > regrid = {
>> > > > > > to_grid = NONE;
>> > > > > > method = NEAREST;
>> > > > > > width = 1;
>> > > > > > vld_thresh = 0.5;
>> > > > > > }
>> > > > > >
>> > > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
>> > > > > >
>> > > > > > fcst = {
>> > > > > > field = [
>> > > > > > {
>> > > > > > name = "UGRD";
>> > > > > > level = "Z10";
>> > > > > > cat_thresh = [ >=5.0 ];
>> > > > > > },
>> > > > > >
>> > > > > > {
>> > > > > > name = "VGRD";
>> > > > > > level = "Z10";
>> > > > > > cat_thresh = [ >=5.0 ];
>> > > > > > }
>> > > > > > ];
>> > > > > >
>> > > > > > }
>> > > > > > obs = fcst;
>> > > > > >
>> > > > > > message_type = [ "ASCATW" ];
>> > > > > > // Verification masking regions
>> > > > > > //
>> > > > > > mask = {
>> > > > > > grid = [ "FULL" ];
>> > > > > >
>> > > > > > // Interpolation methods
>> > > > > > //
>> > > > > > interp = {
>> > > > > > vld_thresh = 1.0;
>> > > > > >
>> > > > > > type = [
>> > > > > > {
>> > > > > > method = NEAREST;
>> > > > > > width = 1;
>> > > > > > }
>> > > > > > ];
>> > > > > > }
>> > > > > >
>> > > > > > //////
>> > > > > >
>> > > > > > and the rest of the settings remained as I found them
when I
>> copied
>> > > the
>> > > > > > PointStatConfig_tutorial from the default config file.
>> > > > > >
>> > > > > > So, this runs correctly, and produces all the necessary
files
>> that
>> > I
>> > > > > asked
>> > > > > > for, but, there is nothing in the files, because there
are no
>> > > matches.
>> > > > > > That's hard for me to believe that there aren't any
matches,
>> so, I
>> > > know
>> > > > > > that I have something set wrong. My guess is that either
the
>> > name =
>> > > > > > "UGRD"; and level = "Z10"; is incorrect for 10m winds, or
the
>> > method
>> > > =
>> > > > > > NEAREST; width = 1; is wrong.
>> > > > > >
>> > > > > > How would I check on the name and level? And, is there a
better
>> > > > setting
>> > > > > I
>> > > > > > should use for width? Or, is there something else I need
to
>> set?
>> > > > > >
>> > > > > > Thanks in advance!
>> > > > > >
>> > > > > > Roz
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Rosalyn MacCracken
>> > > > > > Support Scientist
>> > > > > >
>> > > > > > Ocean Applilcations Branch
>> > > > > > NOAA/NWS Ocean Prediction Center
>> > > > > > NCWCP
>> > > > > > 5830 University Research Ct
>> > > > > > College Park, MD 20740-3818
>> > > > > >
>> > > > > > (p) 301-683-1551 <(301)%20683-1551>
>> > > > > > rosalyn.maccracken at noaa.gov
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > Rosalyn MacCracken
>> > > > Support Scientist
>> > > >
>> > > > Ocean Applilcations Branch
>> > > > NOAA/NWS Ocean Prediction Center
>> > > > NCWCP
>> > > > 5830 University Research Ct
>> > > > College Park, MD 20740-3818
>> > > >
>> > > > (p) 301-683-1551
>> > > > rosalyn.maccracken at noaa.gov
>> > > >
>> > > >
>> > >
>> > >
>> > > --
>> > >
>> > >
>> >
>> >
>> > --
>> > Rosalyn MacCracken
>> > Support Scientist
>> >
>> > Ocean Applilcations Branch
>> > NOAA/NWS Ocean Prediction Center
>> > NCWCP
>> > 5830 University Research Ct
>> > College Park, MD 20740-3818
>> >
>> > (p) 301-683-1551
>> > rosalyn.maccracken at noaa.gov
>> >
>> >
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Tara Jensen
>> Project Manager II
>> NCAR RAL and DTC
>> PO Box 3000, Boulder, Colorado 80307 USA
>> +1 303-497-8479 jensen at ucar.edu
>>
>>
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551 <(301)%20683-1551>
> rosalyn.maccracken at noaa.gov
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Tara Jensen
Time: Thu May 04 12:46:18 2017
Roz,
Once again... my oversight. I don't usually handle helpdesk so I'm a
little rusty. It error-ed out because you only have the UGRD defined
in
the obs dictionary I suggested and don't have the VGRD. The number of
fields in the forecast dictionary is 2, the number in the obs
dictionary is
1. Try this:
obs = {
field = [
{
message_type = [ "ASCATW"];
name = "UGRD";
level = [ "P1013" ];
cat_thresh = [ >=5.0 ];
}
{
message_type = [ "ASCATW"];
name = "VGRD";
level = [ "P1013" ];
cat_thresh = [ >=5.0 ];
}
];
}
Tara
On Thu, May 4, 2017 at 12:39 PM, Rosalyn MacCracken - NOAA Affiliate
via RT
<met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
>
> Oh, grrrr...I got the error:
> ERROR : PointStatConfInfo::process_config() -> The number of
verification
> tasks in "obs.field" must be non-zero and match the number in
"fcst.field".
>
> Any ideas?
>
> roz
>
> On Thu, May 4, 2017 at 2:31 PM, Rosalyn MacCracken - NOAA Affiliate
<
> rosalyn.maccracken at noaa.gov> wrote:
>
> > Ok, got it. I'll try that and let you know how things worked.
> >
> > Thanks for the help!
> >
> > Roz
> >
> > On Thu, May 4, 2017 at 2:29 PM, Tara Jensen via RT
<met_help at ucar.edu>
> > wrote:
> >
> >> Roz,
> >>
> >> Sorry I didn't make it clear. Replace obs=fcst; with
> >>
> >> obs = {
> >> field = [
> >> {
> >> message_type = [ "ASCATW"];
> >> name = "UGRD";
> >> level = [ "P1013" ];
> >> cat_thresh = [ >=5.0 ]; }
> >> ];
> >> }
> >>
> >> NOTE: I notice I missed that you have a cat_thresh listed in the
> >> "forecast
> >> dictionary" so added it to the recommended obs dictionary.
> >>
> >> Tara
> >>
> >>
> >> On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA
Affiliate via
> >> RT
> >> <met_help at ucar.edu> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >> >
> >> > Where is that obs dictionary? Is this in the
PB2NCConfig_tutorial or
> >> in
> >> > the PointStatConfig_tutorial? I don't see it in either. Or do
I just
> >> > stick this in somewhere?
> >> >
> >> > Or, is that in place of:
> >> > // Forecast and observation fields to be verified
> >> > //
> >> > fcst = {
> >> > field = [
> >> > {
> >> > name = "UGRD";
> >> > level = "Z10";
> >> > cat_thresh = [ >=1.0 ];
> >> > },
> >> >
> >> > {
> >> > name = "VGRD";
> >> > level = "Z10";
> >> > cat_thresh = [ >=1.0 ];
> >> > }
> >> > ];
> >> >
> >> > }
> >> > obs = fcst;
> >> >
> >> > Roz
> >> >
> >> > On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT
<met_help at ucar.edu
> >
> >> > wrote:
> >> >
> >> > > Roz,
> >> > >
> >> > > I'll jump in here as John is busy at the moment. It looks
like
> >> there's a
> >> > > level mis-match occurring. As you pointed out the forecast
field is
> >> > > UGRD/Z10 and VGRD/Z10 and the observed field is at the
surface and
> >> mapped
> >> > > to 1013 mb. Try setting the "obs dictionary" in the config
to be:
> >> > >
> >> > > obs = {
> >> > > field = [
> >> > > {
> >> > > message_type = [ "ASCATW"];
> >> > > name = "UGRD";
> >> > > level = [ "P1013" ];
> >> > > }
> >> > > ];
> >> > > }
> >> > >
> >> > > Cheers, Tara
> >> > >
> >> > >
> >> > > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA
Affiliate
> >> via
> >> > RT
> >> > > <met_help at ucar.edu> wrote:
> >> > >
> >> > > >
> >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >> > > >
> >> > > > Hi John,
> >> > > >
> >> > > > So, I reran point-stat, and wrote it to a log file. The
output
> for
> >> > UGRD
> >> > > is
> >> > > > below. VGRD is the same. So, I'm not sure what all this
means,
> >> but, I
> >> > > > have a hunch I might know what it is, and I have no idea if
this
> is
> >> > > > something that can be fixed, or a work around can be found.
> >> > > >
> >> > > > So, last night I was looking through the netCDF file to
make sure
> >> the
> >> > > data
> >> > > > was all there. I have a few variables, but, I really just
wanted
> to
> >> > make
> >> > > > sure that lat, lon, height and values were there. The 2
variables
> >> I'm
> >> > > > looking at are:
> >> > > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> >> > > > hdr_arr:columns = "lat lon elv" ;
> >> > > >
> >> > > > Two lines (u and v) in the obs_arr looks like:
> >> > > > 128947, 33, 1013, _, -8.6,
> >> > > > 128947, 34, 1013, _, -7.2 ;
> >> > > > And, one line for the hdr_arr looks like this (10 is for
10m
> winds):
> >> > > > -67.92, 167.25, 10 ;
> >> > > >
> >> > > > So, a couple of things come to mind, and I don't know how
to fix
> >> > either.
> >> > > > First, in the obs_arr, the only "height" variable is the
pressure
> >> > level,
> >> > > > 1013 mb. So, is that a problem that there's no height
associated
> >> with
> >> > > > obs_arr, only pressure? Because, I can get height from the
> hdr_arr.
> >> > > >
> >> > > > The other thing that comes to mind is that maybe the lons
in one
> >> file
> >> > go
> >> > > > from -180 to 180, and the other is from 0 to 360. So,
could that
> be
> >> > the
> >> > > > issue?
> >> > > >
> >> > > > Any thoughts?
> >> > > >
> >> > > > Roz
> >> > > > ___________
> >> > > > Output from logfile:
> >> > > >
> >> > > > DEBUG 2: Reading data for UGRD/Z10.
> >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
> match
> >> for
> >> > > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> >> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> >> > > > t12z.pgrbf00".
> >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1
GRIB
> >> records
> >> > > > matching VarInfo "UGRD/Z10" in GRIB file
> >> > > >
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
> >> > > > 0".
> >> > > > DEBUG 3: Use the matching forecast and observation grids.
> >> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny:
181
> >> lat_ll:
> >> > > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> >> > > > DEBUG 2: Processing masking regions.
> >> > > > DEBUG 3: Processing grid mask: FULL
> >> > > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0
climatology
> >> levels.
> >> > > > DEBUG 2:
> >> > > > DEBUG 2:
> >> > > >
------------------------------------------------------------
> >> > > > --------------------
> >> > > >
> >> > > > DEBUG 2: Searching 257896 observations from 128948
messages.
> >> > > > DEBUG 2:
> >> > > > DEBUG 2:
> >> > > >
------------------------------------------------------------
> >> > > > --------------------
> >> > > > DEBUG 2:
> >> > > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for
observation type
> >> > > ASCATW,
> >> > > > over region FULL, for interpolation method NEAREST(25),
using 0
> >> pairs.
> >> > > > DEBUG 3: Number of matched pairs = 0
> >> > > > DEBUG 3: Observations processed = 257896
> >> > > > DEBUG 3: Rejected: SID exclusion = 0
> >> > > > DEBUG 3: Rejected: GRIB code = 128948
> >> > > > DEBUG 3: Rejected: valid time = 71
> >> > > > DEBUG 3: Rejected: bad obs value = 0
> >> > > > DEBUG 3: Rejected: off the grid = 76
> >> > > > DEBUG 3: Rejected: level mismatch = 128801
> >> > > > 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
> >> > > >
> >> > > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT <
> >> > > > met_help at ucar.edu
> >> > > > > wrote:
> >> > > >
> >> > > > > Hi Roz,
> >> > > > >
> >> > > > > I see that you ran Point-Stat and got 0 matched pairs.
Please
> >> rerun
> >> > > your
> >> > > > > Point-Stat command using verbosity level 3 (-v 3) and
write the
> >> > output
> >> > > > to a
> >> > > > > log file (-log point_stat.log). Then inspect that
logging
> output
> >> > > > closely,
> >> > > > > and you'll see sections that look something like this:
> >> > > > >
> >> > > > > DEBUG 3: Number of matched pairs = 334
> >> > > > >
> >> > > > > DEBUG 3: Observations processed = 89893
> >> > > > >
> >> > > > > DEBUG 3: Rejected: SID exclusion = 0
> >> > > > >
> >> > > > > DEBUG 3: Rejected: GRIB code = 79360
> >> > > > >
> >> > > > > DEBUG 3: Rejected: valid time = 0
> >> > > > >
> >> > > > > DEBUG 3: Rejected: bad obs value = 0
> >> > > > >
> >> > > > > DEBUG 3: Rejected: off the grid = 5
> >> > > > >
> >> > > > > DEBUG 3: Rejected: level mismatch = 9607
> >> > > > >
> >> > > > > DEBUG 3: Rejected: quality marker = 0
> >> > > > >
> >> > > > > DEBUG 3: Rejected: message type = 344
> >> > > > >
> >> > > > > DEBUG 3: Rejected: masking region = 243
> >> > > > >
> >> > > > > DEBUG 3: Rejected: bad fcst value = 0
> >> > > > > DEBUG 3: Rejected: duplicates = 0
> >> > > > >
> >> > > > > With you data, you'll see that the number of matched
pairs is 0.
> >> The
> >> > > > > rejection counts are listed in the same order that Point-
Stat
> uses
> >> > when
> >> > > > > filtering the observations. This should tell you why
you're
> >> getting
> >> > 0
> >> > > > > matched pairs. Perhaps there's a spatial offset between
your
> >> > forecast
> >> > > > and
> >> > > > > obs, or a time offset, or a level offset?
> >> > > > >
> >> > > > > Please take a look at that and let us know if you need
help
> >> > deciphering
> >> > > > the
> >> > > > > output.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > John Halley Gotway
> >> > > > >
> >> > > > >
> >> > > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken - NOAA
> >> Affiliate
> >> > via
> >> > > > RT
> >> > > > > <
> >> > > > > met_help at ucar.edu> wrote:
> >> > > > >
> >> > > > > >
> >> > > > > > Thu May 04 07:45:40 2017: Request 80360 was acted upon.
> >> > > > > > Transaction: Ticket created by
rosalyn.maccracken at noaa.gov
> >> > > > > > Queue: met_help
> >> > > > > > Subject: questions with using point data and the
nearest
> >> > > neighbor
> >> > > > > > setting
> >> > > > > > Owner: Nobody
> >> > > > > > Requestors: rosalyn.maccracken at noaa.gov
> >> > > > > > Status: new
> >> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> >> > > Ticket/Display.html?id=80360
> >> > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > I'm trying to do a verification between ASCAT satellite
point
> >> data
> >> > of
> >> > > > 10m
> >> > > > > > winds (u and v), in a swath, against 10m u and v winds
from
> the
> >> > > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data
from
> >> prepbufr
> >> > > > data
> >> > > > > to
> >> > > > > > netCDF format, and verified that the data is in the
file, both
> >> > > through
> >> > > > > > plotting and through ncdump. I don't want to regrid my
winds.
> >> I
> >> > > want
> >> > > > to
> >> > > > > > keep them as point data, and compare them to the
closest GFS
> >> grid
> >> > > > point.
> >> > > > > >
> >> > > > > > So, I'm trying to use the Point-Stat tool, with the
nearest
> >> > neighbor
> >> > > > > > setting. I've used these settings:
> >> > > > > > model = "GFS";
> >> > > > > >
> >> > > > > > regrid = {
> >> > > > > > to_grid = NONE;
> >> > > > > > method = NEAREST;
> >> > > > > > width = 1;
> >> > > > > > vld_thresh = 0.5;
> >> > > > > > }
> >> > > > > >
> >> > > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> >> > > > > >
> >> > > > > > fcst = {
> >> > > > > > field = [
> >> > > > > > {
> >> > > > > > name = "UGRD";
> >> > > > > > level = "Z10";
> >> > > > > > cat_thresh = [ >=5.0 ];
> >> > > > > > },
> >> > > > > >
> >> > > > > > {
> >> > > > > > name = "VGRD";
> >> > > > > > level = "Z10";
> >> > > > > > cat_thresh = [ >=5.0 ];
> >> > > > > > }
> >> > > > > > ];
> >> > > > > >
> >> > > > > > }
> >> > > > > > obs = fcst;
> >> > > > > >
> >> > > > > > message_type = [ "ASCATW" ];
> >> > > > > > // Verification masking regions
> >> > > > > > //
> >> > > > > > mask = {
> >> > > > > > grid = [ "FULL" ];
> >> > > > > >
> >> > > > > > // Interpolation methods
> >> > > > > > //
> >> > > > > > interp = {
> >> > > > > > vld_thresh = 1.0;
> >> > > > > >
> >> > > > > > type = [
> >> > > > > > {
> >> > > > > > method = NEAREST;
> >> > > > > > width = 1;
> >> > > > > > }
> >> > > > > > ];
> >> > > > > > }
> >> > > > > >
> >> > > > > > //////
> >> > > > > >
> >> > > > > > and the rest of the settings remained as I found them
when I
> >> copied
> >> > > the
> >> > > > > > PointStatConfig_tutorial from the default config file.
> >> > > > > >
> >> > > > > > So, this runs correctly, and produces all the necessary
files
> >> that
> >> > I
> >> > > > > asked
> >> > > > > > for, but, there is nothing in the files, because there
are no
> >> > > matches.
> >> > > > > > That's hard for me to believe that there aren't any
matches,
> >> so, I
> >> > > know
> >> > > > > > that I have something set wrong. My guess is that
either the
> >> > name =
> >> > > > > > "UGRD"; and level = "Z10"; is incorrect for 10m winds,
or the
> >> > method
> >> > > =
> >> > > > > > NEAREST; width = 1; is wrong.
> >> > > > > >
> >> > > > > > How would I check on the name and level? And, is there
a
> better
> >> > > > setting
> >> > > > > I
> >> > > > > > should use for width? Or, is there something else I
need to
> >> set?
> >> > > > > >
> >> > > > > > Thanks in advance!
> >> > > > > >
> >> > > > > > Roz
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > Rosalyn MacCracken
> >> > > > > > Support Scientist
> >> > > > > >
> >> > > > > > Ocean Applilcations Branch
> >> > > > > > NOAA/NWS Ocean Prediction Center
> >> > > > > > NCWCP
> >> > > > > > 5830 University Research Ct
> >> > > > > > College Park, MD 20740-3818
> >> > > > > >
> >> > > > > > (p) 301-683-1551 <(301)%20683-1551>
> >> > > > > > rosalyn.maccracken at noaa.gov
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Rosalyn MacCracken
> >> > > > Support Scientist
> >> > > >
> >> > > > Ocean Applilcations Branch
> >> > > > NOAA/NWS Ocean Prediction Center
> >> > > > NCWCP
> >> > > > 5830 University Research Ct
> >> > > > College Park, MD 20740-3818
> >> > > >
> >> > > > (p) 301-683-1551
> >> > > > rosalyn.maccracken at noaa.gov
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> > > --
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > Rosalyn MacCracken
> >> > Support Scientist
> >> >
> >> > Ocean Applilcations Branch
> >> > NOAA/NWS Ocean Prediction Center
> >> > NCWCP
> >> > 5830 University Research Ct
> >> > College Park, MD 20740-3818
> >> >
> >> > (p) 301-683-1551
> >> > rosalyn.maccracken at noaa.gov
> >> >
> >> >
> >>
> >>
> >> --
> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> Tara Jensen
> >> Project Manager II
> >> NCAR RAL and DTC
> >> PO Box 3000, Boulder, Colorado 80307 USA
> >> +1 303-497-8479 jensen at ucar.edu
> >>
> >>
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551 <(301)%20683-1551>
> > rosalyn.maccracken at noaa.gov
> >
>
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tara Jensen
Project Manager II
NCAR RAL and DTC
PO Box 3000, Boulder, Colorado 80307 USA
+1 303-497-8479 jensen at ucar.edu
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 13:04:53 2017
Oooh, nifty! That worked! Actually, there was a comma left out
between
the ugrd and vgrd. I added that and it worked like a charm!
Ok, so, I have my width for Nearest Neighbor set to 5. What would you
suggest I set that to, to still be able to capture matches?
Then, now that I have that working, what else can I do with point
data?
I'd like to be able to capture closed circulations (extra-tropical and
tropical). Can I do that with point data? You know, you have alot of
cool
tools to use. I'd just like to be able to use as many as I can. :-)
Thanks again for all your help!
Roz
On Thu, May 4, 2017 at 2:46 PM, Tara Jensen via RT <met_help at ucar.edu>
wrote:
> Roz,
>
> Once again... my oversight. I don't usually handle helpdesk so I'm
a
> little rusty. It error-ed out because you only have the UGRD
defined in
> the obs dictionary I suggested and don't have the VGRD. The number
of
> fields in the forecast dictionary is 2, the number in the obs
dictionary is
> 1. Try this:
>
> obs = {
> field = [
> {
> message_type = [ "ASCATW"];
> name = "UGRD";
> level = [ "P1013" ];
> cat_thresh = [ >=5.0 ];
> }
> {
> message_type = [ "ASCATW"];
> name = "VGRD";
> level = [ "P1013" ];
> cat_thresh = [ >=5.0 ];
> }
> ];
> }
>
> Tara
>
> On Thu, May 4, 2017 at 12:39 PM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >
> > Oh, grrrr...I got the error:
> > ERROR : PointStatConfInfo::process_config() -> The number of
> verification
> > tasks in "obs.field" must be non-zero and match the number in
> "fcst.field".
> >
> > Any ideas?
> >
> > roz
> >
> > On Thu, May 4, 2017 at 2:31 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > rosalyn.maccracken at noaa.gov> wrote:
> >
> > > Ok, got it. I'll try that and let you know how things worked.
> > >
> > > Thanks for the help!
> > >
> > > Roz
> > >
> > > On Thu, May 4, 2017 at 2:29 PM, Tara Jensen via RT
<met_help at ucar.edu>
> > > wrote:
> > >
> > >> Roz,
> > >>
> > >> Sorry I didn't make it clear. Replace obs=fcst; with
> > >>
> > >> obs = {
> > >> field = [
> > >> {
> > >> message_type = [ "ASCATW"];
> > >> name = "UGRD";
> > >> level = [ "P1013" ];
> > >> cat_thresh = [ >=5.0 ]; }
> > >> ];
> > >> }
> > >>
> > >> NOTE: I notice I missed that you have a cat_thresh listed in
the
> > >> "forecast
> > >> dictionary" so added it to the recommended obs dictionary.
> > >>
> > >> Tara
> > >>
> > >>
> > >> On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA
Affiliate
> via
> > >> RT
> > >> <met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360
>
> > >> >
> > >> > Where is that obs dictionary? Is this in the
PB2NCConfig_tutorial
> or
> > >> in
> > >> > the PointStatConfig_tutorial? I don't see it in either. Or
do I
> just
> > >> > stick this in somewhere?
> > >> >
> > >> > Or, is that in place of:
> > >> > // Forecast and observation fields to be verified
> > >> > //
> > >> > fcst = {
> > >> > field = [
> > >> > {
> > >> > name = "UGRD";
> > >> > level = "Z10";
> > >> > cat_thresh = [ >=1.0 ];
> > >> > },
> > >> >
> > >> > {
> > >> > name = "VGRD";
> > >> > level = "Z10";
> > >> > cat_thresh = [ >=1.0 ];
> > >> > }
> > >> > ];
> > >> >
> > >> > }
> > >> > obs = fcst;
> > >> >
> > >> > Roz
> > >> >
> > >> > On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT <
> met_help at ucar.edu
> > >
> > >> > wrote:
> > >> >
> > >> > > Roz,
> > >> > >
> > >> > > I'll jump in here as John is busy at the moment. It looks
like
> > >> there's a
> > >> > > level mis-match occurring. As you pointed out the forecast
field
> is
> > >> > > UGRD/Z10 and VGRD/Z10 and the observed field is at the
surface and
> > >> mapped
> > >> > > to 1013 mb. Try setting the "obs dictionary" in the config
to be:
> > >> > >
> > >> > > obs = {
> > >> > > field = [
> > >> > > {
> > >> > > message_type = [ "ASCATW"];
> > >> > > name = "UGRD";
> > >> > > level = [ "P1013" ];
> > >> > > }
> > >> > > ];
> > >> > > }
> > >> > >
> > >> > > Cheers, Tara
> > >> > >
> > >> > >
> > >> > > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken - NOAA
> Affiliate
> > >> via
> > >> > RT
> > >> > > <met_help at ucar.edu> wrote:
> > >> > >
> > >> > > >
> > >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> > >> > > >
> > >> > > > Hi John,
> > >> > > >
> > >> > > > So, I reran point-stat, and wrote it to a log file. The
output
> > for
> > >> > UGRD
> > >> > > is
> > >> > > > below. VGRD is the same. So, I'm not sure what all this
means,
> > >> but, I
> > >> > > > have a hunch I might know what it is, and I have no idea
if this
> > is
> > >> > > > something that can be fixed, or a work around can be
found.
> > >> > > >
> > >> > > > So, last night I was looking through the netCDF file to
make
> sure
> > >> the
> > >> > > data
> > >> > > > was all there. I have a few variables, but, I really
just
> wanted
> > to
> > >> > make
> > >> > > > sure that lat, lon, height and values were there. The 2
> variables
> > >> I'm
> > >> > > > looking at are:
> > >> > > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> > >> > > > hdr_arr:columns = "lat lon elv" ;
> > >> > > >
> > >> > > > Two lines (u and v) in the obs_arr looks like:
> > >> > > > 128947, 33, 1013, _, -8.6,
> > >> > > > 128947, 34, 1013, _, -7.2 ;
> > >> > > > And, one line for the hdr_arr looks like this (10 is for
10m
> > winds):
> > >> > > > -67.92, 167.25, 10 ;
> > >> > > >
> > >> > > > So, a couple of things come to mind, and I don't know how
to fix
> > >> > either.
> > >> > > > First, in the obs_arr, the only "height" variable is the
> pressure
> > >> > level,
> > >> > > > 1013 mb. So, is that a problem that there's no height
> associated
> > >> with
> > >> > > > obs_arr, only pressure? Because, I can get height from
the
> > hdr_arr.
> > >> > > >
> > >> > > > The other thing that comes to mind is that maybe the lons
in one
> > >> file
> > >> > go
> > >> > > > from -180 to 180, and the other is from 0 to 360. So,
could
> that
> > be
> > >> > the
> > >> > > > issue?
> > >> > > >
> > >> > > > Any thoughts?
> > >> > > >
> > >> > > > Roz
> > >> > > > ___________
> > >> > > > Output from logfile:
> > >> > > >
> > >> > > > DEBUG 2: Reading data for UGRD/Z10.
> > >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
> > match
> > >> for
> > >> > > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> > >> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> > >> > > > t12z.pgrbf00".
> > >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1
GRIB
> > >> records
> > >> > > > matching VarInfo "UGRD/Z10" in GRIB file
> > >> > > >
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.pgrbf0
> > >> > > > 0".
> > >> > > > DEBUG 3: Use the matching forecast and observation grids.
> > >> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny:
181
> > >> lat_ll:
> > >> > > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> > >> > > > DEBUG 2: Processing masking regions.
> > >> > > > DEBUG 3: Processing grid mask: FULL
> > >> > > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0
climatology
> > >> levels.
> > >> > > > DEBUG 2:
> > >> > > > DEBUG 2:
> > >> > > >
------------------------------------------------------------
> > >> > > > --------------------
> > >> > > >
> > >> > > > DEBUG 2: Searching 257896 observations from 128948
messages.
> > >> > > > DEBUG 2:
> > >> > > > DEBUG 2:
> > >> > > >
------------------------------------------------------------
> > >> > > > --------------------
> > >> > > > DEBUG 2:
> > >> > > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for
observation
> type
> > >> > > ASCATW,
> > >> > > > over region FULL, for interpolation method NEAREST(25),
using 0
> > >> pairs.
> > >> > > > DEBUG 3: Number of matched pairs = 0
> > >> > > > DEBUG 3: Observations processed = 257896
> > >> > > > DEBUG 3: Rejected: SID exclusion = 0
> > >> > > > DEBUG 3: Rejected: GRIB code = 128948
> > >> > > > DEBUG 3: Rejected: valid time = 71
> > >> > > > DEBUG 3: Rejected: bad obs value = 0
> > >> > > > DEBUG 3: Rejected: off the grid = 76
> > >> > > > DEBUG 3: Rejected: level mismatch = 128801
> > >> > > > 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
> > >> > > >
> > >> > > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via RT
<
> > >> > > > met_help at ucar.edu
> > >> > > > > wrote:
> > >> > > >
> > >> > > > > Hi Roz,
> > >> > > > >
> > >> > > > > I see that you ran Point-Stat and got 0 matched pairs.
Please
> > >> rerun
> > >> > > your
> > >> > > > > Point-Stat command using verbosity level 3 (-v 3) and
write
> the
> > >> > output
> > >> > > > to a
> > >> > > > > log file (-log point_stat.log). Then inspect that
logging
> > output
> > >> > > > closely,
> > >> > > > > and you'll see sections that look something like this:
> > >> > > > >
> > >> > > > > DEBUG 3: Number of matched pairs = 334
> > >> > > > >
> > >> > > > > DEBUG 3: Observations processed = 89893
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: SID exclusion = 0
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: GRIB code = 79360
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: valid time = 0
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: bad obs value = 0
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: off the grid = 5
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: level mismatch = 9607
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: quality marker = 0
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: message type = 344
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: masking region = 243
> > >> > > > >
> > >> > > > > DEBUG 3: Rejected: bad fcst value = 0
> > >> > > > > DEBUG 3: Rejected: duplicates = 0
> > >> > > > >
> > >> > > > > With you data, you'll see that the number of matched
pairs is
> 0.
> > >> The
> > >> > > > > rejection counts are listed in the same order that
Point-Stat
> > uses
> > >> > when
> > >> > > > > filtering the observations. This should tell you why
you're
> > >> getting
> > >> > 0
> > >> > > > > matched pairs. Perhaps there's a spatial offset
between your
> > >> > forecast
> > >> > > > and
> > >> > > > > obs, or a time offset, or a level offset?
> > >> > > > >
> > >> > > > > Please take a look at that and let us know if you need
help
> > >> > deciphering
> > >> > > > the
> > >> > > > > output.
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > > John Halley Gotway
> > >> > > > >
> > >> > > > >
> > >> > > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken -
NOAA
> > >> Affiliate
> > >> > via
> > >> > > > RT
> > >> > > > > <
> > >> > > > > met_help at ucar.edu> wrote:
> > >> > > > >
> > >> > > > > >
> > >> > > > > > Thu May 04 07:45:40 2017: Request 80360 was acted
upon.
> > >> > > > > > Transaction: Ticket created by
rosalyn.maccracken at noaa.gov
> > >> > > > > > Queue: met_help
> > >> > > > > > Subject: questions with using point data and the
> nearest
> > >> > > neighbor
> > >> > > > > > setting
> > >> > > > > > Owner: Nobody
> > >> > > > > > Requestors: rosalyn.maccracken at noaa.gov
> > >> > > > > > Status: new
> > >> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > >> > > Ticket/Display.html?id=80360
> > >> > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > Hi,
> > >> > > > > >
> > >> > > > > > I'm trying to do a verification between ASCAT
satellite
> point
> > >> data
> > >> > of
> > >> > > > 10m
> > >> > > > > > winds (u and v), in a swath, against 10m u and v
winds from
> > the
> > >> > > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT data
from
> > >> prepbufr
> > >> > > > data
> > >> > > > > to
> > >> > > > > > netCDF format, and verified that the data is in the
file,
> both
> > >> > > through
> > >> > > > > > plotting and through ncdump. I don't want to regrid
my
> winds.
> > >> I
> > >> > > want
> > >> > > > to
> > >> > > > > > keep them as point data, and compare them to the
closest GFS
> > >> grid
> > >> > > > point.
> > >> > > > > >
> > >> > > > > > So, I'm trying to use the Point-Stat tool, with the
nearest
> > >> > neighbor
> > >> > > > > > setting. I've used these settings:
> > >> > > > > > model = "GFS";
> > >> > > > > >
> > >> > > > > > regrid = {
> > >> > > > > > to_grid = NONE;
> > >> > > > > > method = NEAREST;
> > >> > > > > > width = 1;
> > >> > > > > > vld_thresh = 0.5;
> > >> > > > > > }
> > >> > > > > >
> > >> > > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > >> > > > > >
> > >> > > > > > fcst = {
> > >> > > > > > field = [
> > >> > > > > > {
> > >> > > > > > name = "UGRD";
> > >> > > > > > level = "Z10";
> > >> > > > > > cat_thresh = [ >=5.0 ];
> > >> > > > > > },
> > >> > > > > >
> > >> > > > > > {
> > >> > > > > > name = "VGRD";
> > >> > > > > > level = "Z10";
> > >> > > > > > cat_thresh = [ >=5.0 ];
> > >> > > > > > }
> > >> > > > > > ];
> > >> > > > > >
> > >> > > > > > }
> > >> > > > > > obs = fcst;
> > >> > > > > >
> > >> > > > > > message_type = [ "ASCATW" ];
> > >> > > > > > // Verification masking regions
> > >> > > > > > //
> > >> > > > > > mask = {
> > >> > > > > > grid = [ "FULL" ];
> > >> > > > > >
> > >> > > > > > // Interpolation methods
> > >> > > > > > //
> > >> > > > > > interp = {
> > >> > > > > > vld_thresh = 1.0;
> > >> > > > > >
> > >> > > > > > type = [
> > >> > > > > > {
> > >> > > > > > method = NEAREST;
> > >> > > > > > width = 1;
> > >> > > > > > }
> > >> > > > > > ];
> > >> > > > > > }
> > >> > > > > >
> > >> > > > > > //////
> > >> > > > > >
> > >> > > > > > and the rest of the settings remained as I found them
when I
> > >> copied
> > >> > > the
> > >> > > > > > PointStatConfig_tutorial from the default config
file.
> > >> > > > > >
> > >> > > > > > So, this runs correctly, and produces all the
necessary
> files
> > >> that
> > >> > I
> > >> > > > > asked
> > >> > > > > > for, but, there is nothing in the files, because
there are
> no
> > >> > > matches.
> > >> > > > > > That's hard for me to believe that there aren't any
matches,
> > >> so, I
> > >> > > know
> > >> > > > > > that I have something set wrong. My guess is that
either
> the
> > >> > name =
> > >> > > > > > "UGRD"; and level = "Z10"; is incorrect for 10m
winds, or
> the
> > >> > method
> > >> > > =
> > >> > > > > > NEAREST; width = 1; is wrong.
> > >> > > > > >
> > >> > > > > > How would I check on the name and level? And, is
there a
> > better
> > >> > > > setting
> > >> > > > > I
> > >> > > > > > should use for width? Or, is there something else I
need to
> > >> set?
> > >> > > > > >
> > >> > > > > > Thanks in advance!
> > >> > > > > >
> > >> > > > > > Roz
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Rosalyn MacCracken
> > >> > > > > > Support Scientist
> > >> > > > > >
> > >> > > > > > Ocean Applilcations Branch
> > >> > > > > > NOAA/NWS Ocean Prediction Center
> > >> > > > > > NCWCP
> > >> > > > > > 5830 University Research Ct
> > >> > > > > > College Park, MD 20740-3818
> > >> > > > > >
> > >> > > > > > (p) 301-683-1551 <(301)%20683-1551>
> > >> > > > > > rosalyn.maccracken at noaa.gov
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Rosalyn MacCracken
> > >> > > > Support Scientist
> > >> > > >
> > >> > > > Ocean Applilcations Branch
> > >> > > > NOAA/NWS Ocean Prediction Center
> > >> > > > NCWCP
> > >> > > > 5830 University Research Ct
> > >> > > > College Park, MD 20740-3818
> > >> > > >
> > >> > > > (p) 301-683-1551
> > >> > > > rosalyn.maccracken at noaa.gov
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >> > --
> > >> > Rosalyn MacCracken
> > >> > Support Scientist
> > >> >
> > >> > Ocean Applilcations Branch
> > >> > NOAA/NWS Ocean Prediction Center
> > >> > NCWCP
> > >> > 5830 University Research Ct
> > >> > College Park, MD 20740-3818
> > >> >
> > >> > (p) 301-683-1551
> > >> > rosalyn.maccracken at noaa.gov
> > >> >
> > >> >
> > >>
> > >>
> > >> --
> > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > >> Tara Jensen
> > >> Project Manager II
> > >> NCAR RAL and DTC
> > >> PO Box 3000, Boulder, Colorado 80307 USA
> > >> +1 303-497-8479 jensen at ucar.edu
> > >>
> > >>
> > >
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551 <(301)%20683-1551>
> > > rosalyn.maccracken at noaa.gov
> > >
> >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tara Jensen
> Project Manager II
> NCAR RAL and DTC
> PO Box 3000, Boulder, Colorado 80307 USA
> +1 303-497-8479 jensen at ucar.edu
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Tara Jensen
Time: Thu May 04 13:26:47 2017
Roz,
I see you set your neighborhood to 5 for Nearest Neighbor. By
definition,
Nearest Neighbor assumes a width of 1 so setting it to 5 will not
impact
the matching of forecast and observed points. Based on our earlier
discussion, Nearest Neighbor does make sense, so you might as well set
the
width back to 1.
As for other things you can do with point data: Unfortunately many of
our
"cool tools" are more focused on gridded data. However, you might be
able
to evaluate the model using point observations within a certain radii
of
the tropical or extra-tropical center. It won't define the closed
circulation, but it would allow you to look within a distance from the
core
that are important to your users. To do this, you would need to find
a
source of track data.
NHC has tropical cyclones and
EMC's Guang Ping Lou for extra-tropical (
http://www.emc.ncep.noaa.gov/mmb/gplou/emchurr/glblgen/)
You could then use the Gen_Vx_Mask and the track option to generate
the
verificaiton masking regions.
Finally, there may be a way to use Stat_Analysis -by {case} capability
to
aggregate scores over time and then plot spatially. If you'd like to
discuss this further, I'd suggest placing some output from PB2NC on
our FTP
site and we can do some brainstorming with you. Instructions for how
to
provide us with sample data may be found near the bottom of the page
at:
http://www.dtcenter.org/met/users/support/met_help.php
May I close this ticket and you can open a new one as other issues
arise?
Thanks, Tara
On Thu, May 4, 2017 at 1:04 PM, Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
>
> Oooh, nifty! That worked! Actually, there was a comma left out
between
> the ugrd and vgrd. I added that and it worked like a charm!
>
> Ok, so, I have my width for Nearest Neighbor set to 5. What would
you
> suggest I set that to, to still be able to capture matches?
>
> Then, now that I have that working, what else can I do with point
data?
> I'd like to be able to capture closed circulations (extra-tropical
and
> tropical). Can I do that with point data? You know, you have alot
of cool
> tools to use. I'd just like to be able to use as many as I can. :-
)
>
> Thanks again for all your help!
>
> Roz
>
> On Thu, May 4, 2017 at 2:46 PM, Tara Jensen via RT
<met_help at ucar.edu>
> wrote:
>
> > Roz,
> >
> > Once again... my oversight. I don't usually handle helpdesk so
I'm a
> > little rusty. It error-ed out because you only have the UGRD
defined in
> > the obs dictionary I suggested and don't have the VGRD. The
number of
> > fields in the forecast dictionary is 2, the number in the obs
dictionary
> is
> > 1. Try this:
> >
> > obs = {
> > field = [
> > {
> > message_type = [ "ASCATW"];
> > name = "UGRD";
> > level = [ "P1013" ];
> > cat_thresh = [ >=5.0 ];
> > }
> > {
> > message_type = [ "ASCATW"];
> > name = "VGRD";
> > level = [ "P1013" ];
> > cat_thresh = [ >=5.0 ];
> > }
> > ];
> > }
> >
> > Tara
> >
> > On Thu, May 4, 2017 at 12:39 PM, Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> > >
> > > Oh, grrrr...I got the error:
> > > ERROR : PointStatConfInfo::process_config() -> The number of
> > verification
> > > tasks in "obs.field" must be non-zero and match the number in
> > "fcst.field".
> > >
> > > Any ideas?
> > >
> > > roz
> > >
> > > On Thu, May 4, 2017 at 2:31 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > > rosalyn.maccracken at noaa.gov> wrote:
> > >
> > > > Ok, got it. I'll try that and let you know how things worked.
> > > >
> > > > Thanks for the help!
> > > >
> > > > Roz
> > > >
> > > > On Thu, May 4, 2017 at 2:29 PM, Tara Jensen via RT <
> met_help at ucar.edu>
> > > > wrote:
> > > >
> > > >> Roz,
> > > >>
> > > >> Sorry I didn't make it clear. Replace obs=fcst; with
> > > >>
> > > >> obs = {
> > > >> field = [
> > > >> {
> > > >> message_type = [ "ASCATW"];
> > > >> name = "UGRD";
> > > >> level = [ "P1013" ];
> > > >> cat_thresh = [ >=5.0 ]; }
> > > >> ];
> > > >> }
> > > >>
> > > >> NOTE: I notice I missed that you have a cat_thresh listed in
the
> > > >> "forecast
> > > >> dictionary" so added it to the recommended obs dictionary.
> > > >>
> > > >> Tara
> > > >>
> > > >>
> > > >> On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA
Affiliate
> > via
> > > >> RT
> > > >> <met_help at ucar.edu> wrote:
> > > >>
> > > >> >
> > > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> > > >> >
> > > >> > Where is that obs dictionary? Is this in the
PB2NCConfig_tutorial
> > or
> > > >> in
> > > >> > the PointStatConfig_tutorial? I don't see it in either.
Or do I
> > just
> > > >> > stick this in somewhere?
> > > >> >
> > > >> > Or, is that in place of:
> > > >> > // Forecast and observation fields to be verified
> > > >> > //
> > > >> > fcst = {
> > > >> > field = [
> > > >> > {
> > > >> > name = "UGRD";
> > > >> > level = "Z10";
> > > >> > cat_thresh = [ >=1.0 ];
> > > >> > },
> > > >> >
> > > >> > {
> > > >> > name = "VGRD";
> > > >> > level = "Z10";
> > > >> > cat_thresh = [ >=1.0 ];
> > > >> > }
> > > >> > ];
> > > >> >
> > > >> > }
> > > >> > obs = fcst;
> > > >> >
> > > >> > Roz
> > > >> >
> > > >> > On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT <
> > met_help at ucar.edu
> > > >
> > > >> > wrote:
> > > >> >
> > > >> > > Roz,
> > > >> > >
> > > >> > > I'll jump in here as John is busy at the moment. It
looks like
> > > >> there's a
> > > >> > > level mis-match occurring. As you pointed out the
forecast
> field
> > is
> > > >> > > UGRD/Z10 and VGRD/Z10 and the observed field is at the
surface
> and
> > > >> mapped
> > > >> > > to 1013 mb. Try setting the "obs dictionary" in the
config to
> be:
> > > >> > >
> > > >> > > obs = {
> > > >> > > field = [
> > > >> > > {
> > > >> > > message_type = [ "ASCATW"];
> > > >> > > name = "UGRD";
> > > >> > > level = [ "P1013" ];
> > > >> > > }
> > > >> > > ];
> > > >> > > }
> > > >> > >
> > > >> > > Cheers, Tara
> > > >> > >
> > > >> > >
> > > >> > > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken -
NOAA
> > Affiliate
> > > >> via
> > > >> > RT
> > > >> > > <met_help at ucar.edu> wrote:
> > > >> > >
> > > >> > > >
> > > >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360
> >
> > > >> > > >
> > > >> > > > Hi John,
> > > >> > > >
> > > >> > > > So, I reran point-stat, and wrote it to a log file.
The
> output
> > > for
> > > >> > UGRD
> > > >> > > is
> > > >> > > > below. VGRD is the same. So, I'm not sure what all
this
> means,
> > > >> but, I
> > > >> > > > have a hunch I might know what it is, and I have no
idea if
> this
> > > is
> > > >> > > > something that can be fixed, or a work around can be
found.
> > > >> > > >
> > > >> > > > So, last night I was looking through the netCDF file to
make
> > sure
> > > >> the
> > > >> > > data
> > > >> > > > was all there. I have a few variables, but, I really
just
> > wanted
> > > to
> > > >> > make
> > > >> > > > sure that lat, lon, height and values were there. The
2
> > variables
> > > >> I'm
> > > >> > > > looking at are:
> > > >> > > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> > > >> > > > hdr_arr:columns = "lat lon elv" ;
> > > >> > > >
> > > >> > > > Two lines (u and v) in the obs_arr looks like:
> > > >> > > > 128947, 33, 1013, _, -8.6,
> > > >> > > > 128947, 34, 1013, _, -7.2 ;
> > > >> > > > And, one line for the hdr_arr looks like this (10 is
for 10m
> > > winds):
> > > >> > > > -67.92, 167.25, 10 ;
> > > >> > > >
> > > >> > > > So, a couple of things come to mind, and I don't know
how to
> fix
> > > >> > either.
> > > >> > > > First, in the obs_arr, the only "height" variable is
the
> > pressure
> > > >> > level,
> > > >> > > > 1013 mb. So, is that a problem that there's no height
> > associated
> > > >> with
> > > >> > > > obs_arr, only pressure? Because, I can get height from
the
> > > hdr_arr.
> > > >> > > >
> > > >> > > > The other thing that comes to mind is that maybe the
lons in
> one
> > > >> file
> > > >> > go
> > > >> > > > from -180 to 180, and the other is from 0 to 360. So,
could
> > that
> > > be
> > > >> > the
> > > >> > > > issue?
> > > >> > > >
> > > >> > > > Any thoughts?
> > > >> > > >
> > > >> > > > Roz
> > > >> > > > ___________
> > > >> > > > Output from logfile:
> > > >> > > >
> > > >> > > > DEBUG 2: Reading data for UGRD/Z10.
> > > >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
> > > match
> > > >> for
> > > >> > > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> > > >> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> > > >> > > > t12z.pgrbf00".
> > > >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
1 GRIB
> > > >> records
> > > >> > > > matching VarInfo "UGRD/Z10" in GRIB file
> > > >> > > >
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.
> pgrbf0
> > > >> > > > 0".
> > > >> > > > DEBUG 3: Use the matching forecast and observation
grids.
> > > >> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360
Ny: 181
> > > >> lat_ll:
> > > >> > > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon:
1.000
> > > >> > > > DEBUG 2: Processing masking regions.
> > > >> > > > DEBUG 3: Processing grid mask: FULL
> > > >> > > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0
> climatology
> > > >> levels.
> > > >> > > > DEBUG 2:
> > > >> > > > DEBUG 2:
> > > >> > > >
------------------------------------------------------------
> > > >> > > > --------------------
> > > >> > > >
> > > >> > > > DEBUG 2: Searching 257896 observations from 128948
messages.
> > > >> > > > DEBUG 2:
> > > >> > > > DEBUG 2:
> > > >> > > >
------------------------------------------------------------
> > > >> > > > --------------------
> > > >> > > > DEBUG 2:
> > > >> > > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for
observation
> > type
> > > >> > > ASCATW,
> > > >> > > > over region FULL, for interpolation method NEAREST(25),
using
> 0
> > > >> pairs.
> > > >> > > > DEBUG 3: Number of matched pairs = 0
> > > >> > > > DEBUG 3: Observations processed = 257896
> > > >> > > > DEBUG 3: Rejected: SID exclusion = 0
> > > >> > > > DEBUG 3: Rejected: GRIB code = 128948
> > > >> > > > DEBUG 3: Rejected: valid time = 71
> > > >> > > > DEBUG 3: Rejected: bad obs value = 0
> > > >> > > > DEBUG 3: Rejected: off the grid = 76
> > > >> > > > DEBUG 3: Rejected: level mismatch = 128801
> > > >> > > > 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
> > > >> > > >
> > > >> > > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway via
RT <
> > > >> > > > met_help at ucar.edu
> > > >> > > > > wrote:
> > > >> > > >
> > > >> > > > > Hi Roz,
> > > >> > > > >
> > > >> > > > > I see that you ran Point-Stat and got 0 matched
pairs.
> Please
> > > >> rerun
> > > >> > > your
> > > >> > > > > Point-Stat command using verbosity level 3 (-v 3) and
write
> > the
> > > >> > output
> > > >> > > > to a
> > > >> > > > > log file (-log point_stat.log). Then inspect that
logging
> > > output
> > > >> > > > closely,
> > > >> > > > > and you'll see sections that look something like
this:
> > > >> > > > >
> > > >> > > > > DEBUG 3: Number of matched pairs = 334
> > > >> > > > >
> > > >> > > > > DEBUG 3: Observations processed = 89893
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: SID exclusion = 0
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: GRIB code = 79360
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: valid time = 0
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: bad obs value = 0
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: off the grid = 5
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: level mismatch = 9607
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: quality marker = 0
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: message type = 344
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: masking region = 243
> > > >> > > > >
> > > >> > > > > DEBUG 3: Rejected: bad fcst value = 0
> > > >> > > > > DEBUG 3: Rejected: duplicates = 0
> > > >> > > > >
> > > >> > > > > With you data, you'll see that the number of matched
pairs
> is
> > 0.
> > > >> The
> > > >> > > > > rejection counts are listed in the same order that
> Point-Stat
> > > uses
> > > >> > when
> > > >> > > > > filtering the observations. This should tell you why
you're
> > > >> getting
> > > >> > 0
> > > >> > > > > matched pairs. Perhaps there's a spatial offset
between
> your
> > > >> > forecast
> > > >> > > > and
> > > >> > > > > obs, or a time offset, or a level offset?
> > > >> > > > >
> > > >> > > > > Please take a look at that and let us know if you
need help
> > > >> > deciphering
> > > >> > > > the
> > > >> > > > > output.
> > > >> > > > >
> > > >> > > > > Thanks,
> > > >> > > > > John Halley Gotway
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken -
NOAA
> > > >> Affiliate
> > > >> > via
> > > >> > > > RT
> > > >> > > > > <
> > > >> > > > > met_help at ucar.edu> wrote:
> > > >> > > > >
> > > >> > > > > >
> > > >> > > > > > Thu May 04 07:45:40 2017: Request 80360 was acted
upon.
> > > >> > > > > > Transaction: Ticket created by
> rosalyn.maccracken at noaa.gov
> > > >> > > > > > Queue: met_help
> > > >> > > > > > Subject: questions with using point data and
the
> > nearest
> > > >> > > neighbor
> > > >> > > > > > setting
> > > >> > > > > > Owner: Nobody
> > > >> > > > > > Requestors: rosalyn.maccracken at noaa.gov
> > > >> > > > > > Status: new
> > > >> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > >> > > Ticket/Display.html?id=80360
> > > >> > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > Hi,
> > > >> > > > > >
> > > >> > > > > > I'm trying to do a verification between ASCAT
satellite
> > point
> > > >> data
> > > >> > of
> > > >> > > > 10m
> > > >> > > > > > winds (u and v), in a swath, against 10m u and v
winds
> from
> > > the
> > > >> > > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT
data from
> > > >> prepbufr
> > > >> > > > data
> > > >> > > > > to
> > > >> > > > > > netCDF format, and verified that the data is in the
file,
> > both
> > > >> > > through
> > > >> > > > > > plotting and through ncdump. I don't want to
regrid my
> > winds.
> > > >> I
> > > >> > > want
> > > >> > > > to
> > > >> > > > > > keep them as point data, and compare them to the
closest
> GFS
> > > >> grid
> > > >> > > > point.
> > > >> > > > > >
> > > >> > > > > > So, I'm trying to use the Point-Stat tool, with the
> nearest
> > > >> > neighbor
> > > >> > > > > > setting. I've used these settings:
> > > >> > > > > > model = "GFS";
> > > >> > > > > >
> > > >> > > > > > regrid = {
> > > >> > > > > > to_grid = NONE;
> > > >> > > > > > method = NEAREST;
> > > >> > > > > > width = 1;
> > > >> > > > > > vld_thresh = 0.5;
> > > >> > > > > > }
> > > >> > > > > >
> > > >> > > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > > >> > > > > >
> > > >> > > > > > fcst = {
> > > >> > > > > > field = [
> > > >> > > > > > {
> > > >> > > > > > name = "UGRD";
> > > >> > > > > > level = "Z10";
> > > >> > > > > > cat_thresh = [ >=5.0 ];
> > > >> > > > > > },
> > > >> > > > > >
> > > >> > > > > > {
> > > >> > > > > > name = "VGRD";
> > > >> > > > > > level = "Z10";
> > > >> > > > > > cat_thresh = [ >=5.0 ];
> > > >> > > > > > }
> > > >> > > > > > ];
> > > >> > > > > >
> > > >> > > > > > }
> > > >> > > > > > obs = fcst;
> > > >> > > > > >
> > > >> > > > > > message_type = [ "ASCATW" ];
> > > >> > > > > > // Verification masking regions
> > > >> > > > > > //
> > > >> > > > > > mask = {
> > > >> > > > > > grid = [ "FULL" ];
> > > >> > > > > >
> > > >> > > > > > // Interpolation methods
> > > >> > > > > > //
> > > >> > > > > > interp = {
> > > >> > > > > > vld_thresh = 1.0;
> > > >> > > > > >
> > > >> > > > > > type = [
> > > >> > > > > > {
> > > >> > > > > > method = NEAREST;
> > > >> > > > > > width = 1;
> > > >> > > > > > }
> > > >> > > > > > ];
> > > >> > > > > > }
> > > >> > > > > >
> > > >> > > > > > //////
> > > >> > > > > >
> > > >> > > > > > and the rest of the settings remained as I found
them
> when I
> > > >> copied
> > > >> > > the
> > > >> > > > > > PointStatConfig_tutorial from the default config
file.
> > > >> > > > > >
> > > >> > > > > > So, this runs correctly, and produces all the
necessary
> > files
> > > >> that
> > > >> > I
> > > >> > > > > asked
> > > >> > > > > > for, but, there is nothing in the files, because
there are
> > no
> > > >> > > matches.
> > > >> > > > > > That's hard for me to believe that there aren't any
> matches,
> > > >> so, I
> > > >> > > know
> > > >> > > > > > that I have something set wrong. My guess is that
either
> > the
> > > >> > name =
> > > >> > > > > > "UGRD"; and level = "Z10"; is incorrect for 10m
winds, or
> > the
> > > >> > method
> > > >> > > =
> > > >> > > > > > NEAREST; width = 1; is wrong.
> > > >> > > > > >
> > > >> > > > > > How would I check on the name and level? And, is
there a
> > > better
> > > >> > > > setting
> > > >> > > > > I
> > > >> > > > > > should use for width? Or, is there something else
I need
> to
> > > >> set?
> > > >> > > > > >
> > > >> > > > > > Thanks in advance!
> > > >> > > > > >
> > > >> > > > > > Roz
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > --
> > > >> > > > > > Rosalyn MacCracken
> > > >> > > > > > Support Scientist
> > > >> > > > > >
> > > >> > > > > > Ocean Applilcations Branch
> > > >> > > > > > NOAA/NWS Ocean Prediction Center
> > > >> > > > > > NCWCP
> > > >> > > > > > 5830 University Research Ct
> > > >> > > > > > College Park, MD 20740-3818
> > > >> > > > > >
> > > >> > > > > > (p) 301-683-1551 <(301)%20683-1551>
> > > >> > > > > > rosalyn.maccracken at noaa.gov
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > > Rosalyn MacCracken
> > > >> > > > Support Scientist
> > > >> > > >
> > > >> > > > Ocean Applilcations Branch
> > > >> > > > NOAA/NWS Ocean Prediction Center
> > > >> > > > NCWCP
> > > >> > > > 5830 University Research Ct
> > > >> > > > College Park, MD 20740-3818
> > > >> > > >
> > > >> > > > (p) 301-683-1551
> > > >> > > > rosalyn.maccracken at noaa.gov
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Rosalyn MacCracken
> > > >> > Support Scientist
> > > >> >
> > > >> > Ocean Applilcations Branch
> > > >> > NOAA/NWS Ocean Prediction Center
> > > >> > NCWCP
> > > >> > 5830 University Research Ct
> > > >> > College Park, MD 20740-3818
> > > >> >
> > > >> > (p) 301-683-1551
> > > >> > rosalyn.maccracken at noaa.gov
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > >> Tara Jensen
> > > >> Project Manager II
> > > >> NCAR RAL and DTC
> > > >> PO Box 3000, Boulder, Colorado 80307 USA
> > > >> +1 303-497-8479 jensen at ucar.edu
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551 <(301)%20683-1551>
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > >
> > >
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
> > --
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Tara Jensen
> > Project Manager II
> > NCAR RAL and DTC
> > PO Box 3000, Boulder, Colorado 80307 USA
> > +1 303-497-8479 jensen at ucar.edu
> >
> >
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tara Jensen
Project Manager II
NCAR RAL and DTC
PO Box 3000, Boulder, Colorado 80307 USA
+1 303-497-8479 jensen at ucar.edu
------------------------------------------------
Subject: questions with using point data and the nearest neighbor setting
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu May 04 13:38:46 2017
Hi Tara,
Yes, you can close the ticket. I'll definitely look in to all the
suggestions you gave me, and when I get to the Stat_Analysis point,
I'll be
back in touch.
I think this will definitely get me started!
Thanks again!
Roz
On Thu, May 4, 2017 at 3:26 PM, Tara Jensen via RT <met_help at ucar.edu>
wrote:
> Roz,
>
> I see you set your neighborhood to 5 for Nearest Neighbor. By
definition,
> Nearest Neighbor assumes a width of 1 so setting it to 5 will not
impact
> the matching of forecast and observed points. Based on our earlier
> discussion, Nearest Neighbor does make sense, so you might as well
set the
> width back to 1.
>
> As for other things you can do with point data: Unfortunately many
of our
> "cool tools" are more focused on gridded data. However, you might
be able
> to evaluate the model using point observations within a certain
radii of
> the tropical or extra-tropical center. It won't define the closed
> circulation, but it would allow you to look within a distance from
the core
> that are important to your users. To do this, you would need to
find a
> source of track data.
>
> NHC has tropical cyclones and
> EMC's Guang Ping Lou for extra-tropical (
> http://www.emc.ncep.noaa.gov/mmb/gplou/emchurr/glblgen/)
>
> You could then use the Gen_Vx_Mask and the track option to generate
the
> verificaiton masking regions.
>
> Finally, there may be a way to use Stat_Analysis -by {case}
capability to
> aggregate scores over time and then plot spatially. If you'd like
to
> discuss this further, I'd suggest placing some output from PB2NC on
our FTP
> site and we can do some brainstorming with you. Instructions for
how to
> provide us with sample data may be found near the bottom of the page
at:
>
> http://www.dtcenter.org/met/users/support/met_help.php
>
> May I close this ticket and you can open a new one as other issues
arise?
> Thanks, Tara
>
> On Thu, May 4, 2017 at 1:04 PM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> >
> > Oooh, nifty! That worked! Actually, there was a comma left out
between
> > the ugrd and vgrd. I added that and it worked like a charm!
> >
> > Ok, so, I have my width for Nearest Neighbor set to 5. What would
you
> > suggest I set that to, to still be able to capture matches?
> >
> > Then, now that I have that working, what else can I do with point
data?
> > I'd like to be able to capture closed circulations (extra-tropical
and
> > tropical). Can I do that with point data? You know, you have
alot of
> cool
> > tools to use. I'd just like to be able to use as many as I can.
:-)
> >
> > Thanks again for all your help!
> >
> > Roz
> >
> > On Thu, May 4, 2017 at 2:46 PM, Tara Jensen via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Roz,
> > >
> > > Once again... my oversight. I don't usually handle helpdesk so
I'm a
> > > little rusty. It error-ed out because you only have the UGRD
defined
> in
> > > the obs dictionary I suggested and don't have the VGRD. The
number of
> > > fields in the forecast dictionary is 2, the number in the obs
> dictionary
> > is
> > > 1. Try this:
> > >
> > > obs = {
> > > field = [
> > > {
> > > message_type = [ "ASCATW"];
> > > name = "UGRD";
> > > level = [ "P1013" ];
> > > cat_thresh = [ >=5.0 ];
> > > }
> > > {
> > > message_type = [ "ASCATW"];
> > > name = "VGRD";
> > > level = [ "P1013" ];
> > > cat_thresh = [ >=5.0 ];
> > > }
> > > ];
> > > }
> > >
> > > Tara
> > >
> > > On Thu, May 4, 2017 at 12:39 PM, Rosalyn MacCracken - NOAA
Affiliate
> via
> > RT
> > > <met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360
>
> > > >
> > > > Oh, grrrr...I got the error:
> > > > ERROR : PointStatConfInfo::process_config() -> The number of
> > > verification
> > > > tasks in "obs.field" must be non-zero and match the number in
> > > "fcst.field".
> > > >
> > > > Any ideas?
> > > >
> > > > roz
> > > >
> > > > On Thu, May 4, 2017 at 2:31 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > > > rosalyn.maccracken at noaa.gov> wrote:
> > > >
> > > > > Ok, got it. I'll try that and let you know how things
worked.
> > > > >
> > > > > Thanks for the help!
> > > > >
> > > > > Roz
> > > > >
> > > > > On Thu, May 4, 2017 at 2:29 PM, Tara Jensen via RT <
> > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > >> Roz,
> > > > >>
> > > > >> Sorry I didn't make it clear. Replace obs=fcst; with
> > > > >>
> > > > >> obs = {
> > > > >> field = [
> > > > >> {
> > > > >> message_type = [ "ASCATW"];
> > > > >> name = "UGRD";
> > > > >> level = [ "P1013" ];
> > > > >> cat_thresh = [ >=5.0 ]; }
> > > > >> ];
> > > > >> }
> > > > >>
> > > > >> NOTE: I notice I missed that you have a cat_thresh listed
in the
> > > > >> "forecast
> > > > >> dictionary" so added it to the recommended obs dictionary.
> > > > >>
> > > > >> Tara
> > > > >>
> > > > >>
> > > > >> On Thu, May 4, 2017 at 12:23 PM, Rosalyn MacCracken - NOAA
> Affiliate
> > > via
> > > > >> RT
> > > > >> <met_help at ucar.edu> wrote:
> > > > >>
> > > > >> >
> > > > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80360 >
> > > > >> >
> > > > >> > Where is that obs dictionary? Is this in the
> PB2NCConfig_tutorial
> > > or
> > > > >> in
> > > > >> > the PointStatConfig_tutorial? I don't see it in either.
Or do
> I
> > > just
> > > > >> > stick this in somewhere?
> > > > >> >
> > > > >> > Or, is that in place of:
> > > > >> > // Forecast and observation fields to be verified
> > > > >> > //
> > > > >> > fcst = {
> > > > >> > field = [
> > > > >> > {
> > > > >> > name = "UGRD";
> > > > >> > level = "Z10";
> > > > >> > cat_thresh = [ >=1.0 ];
> > > > >> > },
> > > > >> >
> > > > >> > {
> > > > >> > name = "VGRD";
> > > > >> > level = "Z10";
> > > > >> > cat_thresh = [ >=1.0 ];
> > > > >> > }
> > > > >> > ];
> > > > >> >
> > > > >> > }
> > > > >> > obs = fcst;
> > > > >> >
> > > > >> > Roz
> > > > >> >
> > > > >> > On Thu, May 4, 2017 at 2:16 PM, Tara Jensen via RT <
> > > met_help at ucar.edu
> > > > >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Roz,
> > > > >> > >
> > > > >> > > I'll jump in here as John is busy at the moment. It
looks
> like
> > > > >> there's a
> > > > >> > > level mis-match occurring. As you pointed out the
forecast
> > field
> > > is
> > > > >> > > UGRD/Z10 and VGRD/Z10 and the observed field is at the
surface
> > and
> > > > >> mapped
> > > > >> > > to 1013 mb. Try setting the "obs dictionary" in the
config to
> > be:
> > > > >> > >
> > > > >> > > obs = {
> > > > >> > > field = [
> > > > >> > > {
> > > > >> > > message_type = [ "ASCATW"];
> > > > >> > > name = "UGRD";
> > > > >> > > level = [ "P1013" ];
> > > > >> > > }
> > > > >> > > ];
> > > > >> > > }
> > > > >> > >
> > > > >> > > Cheers, Tara
> > > > >> > >
> > > > >> > >
> > > > >> > > On Thu, May 4, 2017 at 11:57 AM, Rosalyn MacCracken -
NOAA
> > > Affiliate
> > > > >> via
> > > > >> > RT
> > > > >> > > <met_help at ucar.edu> wrote:
> > > > >> > >
> > > > >> > > >
> > > > >> > > > <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=80360
> > >
> > > > >> > > >
> > > > >> > > > Hi John,
> > > > >> > > >
> > > > >> > > > So, I reran point-stat, and wrote it to a log file.
The
> > output
> > > > for
> > > > >> > UGRD
> > > > >> > > is
> > > > >> > > > below. VGRD is the same. So, I'm not sure what all
this
> > means,
> > > > >> but, I
> > > > >> > > > have a hunch I might know what it is, and I have no
idea if
> > this
> > > > is
> > > > >> > > > something that can be fixed, or a work around can be
found.
> > > > >> > > >
> > > > >> > > > So, last night I was looking through the netCDF file
to make
> > > sure
> > > > >> the
> > > > >> > > data
> > > > >> > > > was all there. I have a few variables, but, I really
just
> > > wanted
> > > > to
> > > > >> > make
> > > > >> > > > sure that lat, lon, height and values were there.
The 2
> > > variables
> > > > >> I'm
> > > > >> > > > looking at are:
> > > > >> > > > obs_arr:columns = "hdr_id gc lvl hgt ob" ;
> > > > >> > > > hdr_arr:columns = "lat lon elv" ;
> > > > >> > > >
> > > > >> > > > Two lines (u and v) in the obs_arr looks like:
> > > > >> > > > 128947, 33, 1013, _, -8.6,
> > > > >> > > > 128947, 34, 1013, _, -7.2 ;
> > > > >> > > > And, one line for the hdr_arr looks like this (10 is
for 10m
> > > > winds):
> > > > >> > > > -67.92, 167.25, 10 ;
> > > > >> > > >
> > > > >> > > > So, a couple of things come to mind, and I don't know
how to
> > fix
> > > > >> > either.
> > > > >> > > > First, in the obs_arr, the only "height" variable is
the
> > > pressure
> > > > >> > level,
> > > > >> > > > 1013 mb. So, is that a problem that there's no
height
> > > associated
> > > > >> with
> > > > >> > > > obs_arr, only pressure? Because, I can get height
from the
> > > > hdr_arr.
> > > > >> > > >
> > > > >> > > > The other thing that comes to mind is that maybe the
lons in
> > one
> > > > >> file
> > > > >> > go
> > > > >> > > > from -180 to 180, and the other is from 0 to 360.
So, could
> > > that
> > > > be
> > > > >> > the
> > > > >> > > > issue?
> > > > >> > > >
> > > > >> > > > Any thoughts?
> > > > >> > > >
> > > > >> > > > Roz
> > > > >> > > > ___________
> > > > >> > > > Output from logfile:
> > > > >> > > >
> > > > >> > > > DEBUG 2: Reading data for UGRD/Z10.
> > > > >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() ->
Found
> range
> > > > match
> > > > >> for
> > > > >> > > > VarInfo "UGRD/Z10" in GRIB record 265 of GRIB file
> > > > >> > > > "/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.
> > > > >> > > > t12z.pgrbf00".
> > > > >> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() ->
Found 1
> GRIB
> > > > >> records
> > > > >> > > > matching VarInfo "UGRD/Z10" in GRIB file
> > > > >> > > >
"/ptmpp1/Rosalyn.MacCracken/proc/data/20170501/gfs.t12z.
> > pgrbf0
> > > > >> > > > 0".
> > > > >> > > > DEBUG 3: Use the matching forecast and observation
grids.
> > > > >> > > > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360
Ny:
> 181
> > > > >> lat_ll:
> > > > >> > > > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon:
1.000
> > > > >> > > > DEBUG 2: Processing masking regions.
> > > > >> > > > DEBUG 3: Processing grid mask: FULL
> > > > >> > > > DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0
> > climatology
> > > > >> levels.
> > > > >> > > > DEBUG 2:
> > > > >> > > > DEBUG 2:
> > > > >> > > > ------------------------------
> ------------------------------
> > > > >> > > > --------------------
> > > > >> > > >
> > > > >> > > > DEBUG 2: Searching 257896 observations from 128948
messages.
> > > > >> > > > DEBUG 2:
> > > > >> > > > DEBUG 2:
> > > > >> > > > ------------------------------
> ------------------------------
> > > > >> > > > --------------------
> > > > >> > > > DEBUG 2:
> > > > >> > > > DEBUG 2: Processing UGRD/Z10 versus UGRD/Z10, for
> observation
> > > type
> > > > >> > > ASCATW,
> > > > >> > > > over region FULL, for interpolation method
NEAREST(25),
> using
> > 0
> > > > >> pairs.
> > > > >> > > > DEBUG 3: Number of matched pairs = 0
> > > > >> > > > DEBUG 3: Observations processed = 257896
> > > > >> > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > >> > > > DEBUG 3: Rejected: GRIB code = 128948
> > > > >> > > > DEBUG 3: Rejected: valid time = 71
> > > > >> > > > DEBUG 3: Rejected: bad obs value = 0
> > > > >> > > > DEBUG 3: Rejected: off the grid = 76
> > > > >> > > > DEBUG 3: Rejected: level mismatch = 128801
> > > > >> > > > 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
> > > > >> > > >
> > > > >> > > > On Thu, May 4, 2017 at 1:24 PM, John Halley Gotway
via RT <
> > > > >> > > > met_help at ucar.edu
> > > > >> > > > > wrote:
> > > > >> > > >
> > > > >> > > > > Hi Roz,
> > > > >> > > > >
> > > > >> > > > > I see that you ran Point-Stat and got 0 matched
pairs.
> > Please
> > > > >> rerun
> > > > >> > > your
> > > > >> > > > > Point-Stat command using verbosity level 3 (-v 3)
and
> write
> > > the
> > > > >> > output
> > > > >> > > > to a
> > > > >> > > > > log file (-log point_stat.log). Then inspect that
logging
> > > > output
> > > > >> > > > closely,
> > > > >> > > > > and you'll see sections that look something like
this:
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Number of matched pairs = 334
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Observations processed = 89893
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: SID exclusion = 0
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: GRIB code = 79360
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: valid time = 0
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: bad obs value = 0
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: off the grid = 5
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: level mismatch = 9607
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: quality marker = 0
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: message type = 344
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: masking region = 243
> > > > >> > > > >
> > > > >> > > > > DEBUG 3: Rejected: bad fcst value = 0
> > > > >> > > > > DEBUG 3: Rejected: duplicates = 0
> > > > >> > > > >
> > > > >> > > > > With you data, you'll see that the number of
matched pairs
> > is
> > > 0.
> > > > >> The
> > > > >> > > > > rejection counts are listed in the same order that
> > Point-Stat
> > > > uses
> > > > >> > when
> > > > >> > > > > filtering the observations. This should tell you
why
> you're
> > > > >> getting
> > > > >> > 0
> > > > >> > > > > matched pairs. Perhaps there's a spatial offset
between
> > your
> > > > >> > forecast
> > > > >> > > > and
> > > > >> > > > > obs, or a time offset, or a level offset?
> > > > >> > > > >
> > > > >> > > > > Please take a look at that and let us know if you
need
> help
> > > > >> > deciphering
> > > > >> > > > the
> > > > >> > > > > output.
> > > > >> > > > >
> > > > >> > > > > Thanks,
> > > > >> > > > > John Halley Gotway
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > On Thu, May 4, 2017 at 7:45 AM, Rosalyn MacCracken
- NOAA
> > > > >> Affiliate
> > > > >> > via
> > > > >> > > > RT
> > > > >> > > > > <
> > > > >> > > > > met_help at ucar.edu> wrote:
> > > > >> > > > >
> > > > >> > > > > >
> > > > >> > > > > > Thu May 04 07:45:40 2017: Request 80360 was acted
upon.
> > > > >> > > > > > Transaction: Ticket created by
> > rosalyn.maccracken at noaa.gov
> > > > >> > > > > > Queue: met_help
> > > > >> > > > > > Subject: questions with using point data and
the
> > > nearest
> > > > >> > > neighbor
> > > > >> > > > > > setting
> > > > >> > > > > > Owner: Nobody
> > > > >> > > > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > >> > > > > > Status: new
> > > > >> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > > >> > > Ticket/Display.html?id=80360
> > > > >> > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > Hi,
> > > > >> > > > > >
> > > > >> > > > > > I'm trying to do a verification between ASCAT
satellite
> > > point
> > > > >> data
> > > > >> > of
> > > > >> > > > 10m
> > > > >> > > > > > winds (u and v), in a swath, against 10m u and v
winds
> > from
> > > > the
> > > > >> > > > > > gfs.tHHz.pgrbf00 file. I've converted the ASCAT
data
> from
> > > > >> prepbufr
> > > > >> > > > data
> > > > >> > > > > to
> > > > >> > > > > > netCDF format, and verified that the data is in
the
> file,
> > > both
> > > > >> > > through
> > > > >> > > > > > plotting and through ncdump. I don't want to
regrid my
> > > winds.
> > > > >> I
> > > > >> > > want
> > > > >> > > > to
> > > > >> > > > > > keep them as point data, and compare them to the
closest
> > GFS
> > > > >> grid
> > > > >> > > > point.
> > > > >> > > > > >
> > > > >> > > > > > So, I'm trying to use the Point-Stat tool, with
the
> > nearest
> > > > >> > neighbor
> > > > >> > > > > > setting. I've used these settings:
> > > > >> > > > > > model = "GFS";
> > > > >> > > > > >
> > > > >> > > > > > regrid = {
> > > > >> > > > > > to_grid = NONE;
> > > > >> > > > > > method = NEAREST;
> > > > >> > > > > > width = 1;
> > > > >> > > > > > vld_thresh = 0.5;
> > > > >> > > > > > }
> > > > >> > > > > >
> > > > >> > > > > > wind_thresh = [ >0.0, >=1.0, >=5.0, >=8.0 ];
> > > > >> > > > > >
> > > > >> > > > > > fcst = {
> > > > >> > > > > > field = [
> > > > >> > > > > > {
> > > > >> > > > > > name = "UGRD";
> > > > >> > > > > > level = "Z10";
> > > > >> > > > > > cat_thresh = [ >=5.0 ];
> > > > >> > > > > > },
> > > > >> > > > > >
> > > > >> > > > > > {
> > > > >> > > > > > name = "VGRD";
> > > > >> > > > > > level = "Z10";
> > > > >> > > > > > cat_thresh = [ >=5.0 ];
> > > > >> > > > > > }
> > > > >> > > > > > ];
> > > > >> > > > > >
> > > > >> > > > > > }
> > > > >> > > > > > obs = fcst;
> > > > >> > > > > >
> > > > >> > > > > > message_type = [ "ASCATW" ];
> > > > >> > > > > > // Verification masking regions
> > > > >> > > > > > //
> > > > >> > > > > > mask = {
> > > > >> > > > > > grid = [ "FULL" ];
> > > > >> > > > > >
> > > > >> > > > > > // Interpolation methods
> > > > >> > > > > > //
> > > > >> > > > > > interp = {
> > > > >> > > > > > vld_thresh = 1.0;
> > > > >> > > > > >
> > > > >> > > > > > type = [
> > > > >> > > > > > {
> > > > >> > > > > > method = NEAREST;
> > > > >> > > > > > width = 1;
> > > > >> > > > > > }
> > > > >> > > > > > ];
> > > > >> > > > > > }
> > > > >> > > > > >
> > > > >> > > > > > //////
> > > > >> > > > > >
> > > > >> > > > > > and the rest of the settings remained as I found
them
> > when I
> > > > >> copied
> > > > >> > > the
> > > > >> > > > > > PointStatConfig_tutorial from the default config
file.
> > > > >> > > > > >
> > > > >> > > > > > So, this runs correctly, and produces all the
necessary
> > > files
> > > > >> that
> > > > >> > I
> > > > >> > > > > asked
> > > > >> > > > > > for, but, there is nothing in the files, because
there
> are
> > > no
> > > > >> > > matches.
> > > > >> > > > > > That's hard for me to believe that there aren't
any
> > matches,
> > > > >> so, I
> > > > >> > > know
> > > > >> > > > > > that I have something set wrong. My guess is
that
> either
> > > the
> > > > >> > name =
> > > > >> > > > > > "UGRD"; and level = "Z10"; is incorrect for 10m
winds,
> or
> > > the
> > > > >> > method
> > > > >> > > =
> > > > >> > > > > > NEAREST; width = 1; is wrong.
> > > > >> > > > > >
> > > > >> > > > > > How would I check on the name and level? And, is
there
> a
> > > > better
> > > > >> > > > setting
> > > > >> > > > > I
> > > > >> > > > > > should use for width? Or, is there something
else I
> need
> > to
> > > > >> set?
> > > > >> > > > > >
> > > > >> > > > > > Thanks in advance!
> > > > >> > > > > >
> > > > >> > > > > > Roz
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > --
> > > > >> > > > > > Rosalyn MacCracken
> > > > >> > > > > > Support Scientist
> > > > >> > > > > >
> > > > >> > > > > > Ocean Applilcations Branch
> > > > >> > > > > > NOAA/NWS Ocean Prediction Center
> > > > >> > > > > > NCWCP
> > > > >> > > > > > 5830 University Research Ct
> > > > >> > > > > > College Park, MD 20740-3818
> > > > >> > > > > >
> > > > >> > > > > > (p) 301-683-1551 <(301)%20683-1551>
> > > > >> > > > > > rosalyn.maccracken at noaa.gov
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > --
> > > > >> > > > Rosalyn MacCracken
> > > > >> > > > Support Scientist
> > > > >> > > >
> > > > >> > > > Ocean Applilcations Branch
> > > > >> > > > NOAA/NWS Ocean Prediction Center
> > > > >> > > > NCWCP
> > > > >> > > > 5830 University Research Ct
> > > > >> > > > College Park, MD 20740-3818
> > > > >> > > >
> > > > >> > > > (p) 301-683-1551
> > > > >> > > > rosalyn.maccracken at noaa.gov
> > > > >> > > >
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Rosalyn MacCracken
> > > > >> > Support Scientist
> > > > >> >
> > > > >> > Ocean Applilcations Branch
> > > > >> > NOAA/NWS Ocean Prediction Center
> > > > >> > NCWCP
> > > > >> > 5830 University Research Ct
> > > > >> > College Park, MD 20740-3818
> > > > >> >
> > > > >> > (p) 301-683-1551
> > > > >> > rosalyn.maccracken at noaa.gov
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > > >> Tara Jensen
> > > > >> Project Manager II
> > > > >> NCAR RAL and DTC
> > > > >> PO Box 3000, Boulder, Colorado 80307 USA
> > > > >> +1 303-497-8479 jensen at ucar.edu
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Rosalyn MacCracken
> > > > > Support Scientist
> > > > >
> > > > > Ocean Applilcations Branch
> > > > > NOAA/NWS Ocean Prediction Center
> > > > > NCWCP
> > > > > 5830 University Research Ct
> > > > > College Park, MD 20740-3818
> > > > >
> > > > > (p) 301-683-1551 <(301)%20683-1551>
> > > > > rosalyn.maccracken at noaa.gov
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
> > > --
> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > Tara Jensen
> > > Project Manager II
> > > NCAR RAL and DTC
> > > PO Box 3000, Boulder, Colorado 80307 USA
> > > +1 303-497-8479 jensen at ucar.edu
> > >
> > >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tara Jensen
> Project Manager II
> NCAR RAL and DTC
> PO Box 3000, Boulder, Colorado 80307 USA
> +1 303-497-8479 jensen at ucar.edu
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
More information about the Met_help
mailing list