[Met_help] [rt.rap.ucar.edu #86091] History for masking land features questions
John Halley Gotway via RT
met_help at ucar.edu
Mon Jul 16 14:58:44 MDT 2018
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I'm using ASCAT data to verify the GFS. I only want to verify points over
the ocean, and not over any inland lakes. I noticed that I was getting
matched points over land (mostly Africa). I'm dumping out the MGDRlite
file to an ascii file, which I use ASCII2NC to create the netCDF file, and
then go on to use Point_stat to create statistics for the matched points.
How do I mask out points over land before it gets to the Point_stat step?
Is there something in the ASCII2NC processing that I can add, so I don't
get these matched points?
Thanks in advance!
Roz
--
Rosalyn MacCracken
Support Scientist
Ocean Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 09 09:46:06 2018
Hi Roz,
I see you're wondering how to only use point observations over water
and
discard the ones over land. You're running ASCII2NC followed by
Point-Stat
and want to know where/how to define that masking.
The ASCII2NC tool supports 3 command line options for filtering point
observations spatially: -mask_grid, -mask_poly, and -mask_sid, for
grid,
polyline, and station ID masking, respectively. But that's not really
what
you want. You want to do "data masking" where you read in a land/sea
mask
and only use the points over water.
I'd recommend running the Gen-Vx-Mask tool to create the desired
masking
region, and then reference that in the Point-Stat config file.
To illustrate, I pulled a sample GFS file:
> wget
https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_4_20180702_0000_012.grb2
Run wgrib2 and look for a LAND/SEA mask:
> wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
400:65422867:d=2018070200:LAND:surface:12 hour fcst:
Run plot_data_plane to see it (see attached image):
> met-7.0/bin/plot_data_plane gfs_4_20180702_0000_012.grb2
gfs_4_LAND.ps
'name="LAND"; level="L0";'
Run gen_vx_mask to create a mask for your verification domain. If
you're
actually verifying on the GFS domain, the command looks a little
redundant:
> /usr/local/met-7.0/bin/gen_vx_mask \
gfs_4_20180702_0000_012.grb2 \
gfs_4_20180702_0000_012.grb2 \
gfs_4_WATER_mask.nc \
-type data \
-mask_field 'name="LAND"; level="L0";' \
-thresh ==0 \
-name WATER
I defined the threshold as "==0" because we want the WATER points, not
the
LAND points. And I used the "-name WATER" command line option to name
the
output NetCDF variable. This will show up in the VX_MASK output
column of
Point-Stat.
Lastly, setup your Point-Stat config file like this:
mask = {
grid = [];
poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
sid = [];
}
Hope that helps clarify.
Thanks,
John
On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
> Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> Queue: met_help
> Subject: masking land features questions
> Owner: Nobody
> Requestors: rosalyn.maccracken at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
>
> Hi,
>
> I'm using ASCAT data to verify the GFS. I only want to verify
points over
> the ocean, and not over any inland lakes. I noticed that I was
getting
> matched points over land (mostly Africa). I'm dumping out the
MGDRlite
> file to an ascii file, which I use ASCII2NC to create the netCDF
file, and
> then go on to use Point_stat to create statistics for the matched
points.
>
> How do I mask out points over land before it gets to the Point_stat
step?
> Is there something in the ASCII2NC processing that I can add, so I
don't
> get these matched points?
>
> Thanks in advance!
>
> Roz
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Mon Jul 09 09:56:38 2018
Hi John,
I get the general idea and it looks pretty straight forward. I'm
still
running MET6.0, since we had some installation issues, but, I should
be
able to generate the mask with that pretty easily, correct?
So, if this works, I'll need to rerun all my data from Mar 2018 -
present,
using that method that we worked out earlier with the *.stat files,
correct? Actually, I don't need to do that...I can start from the
ASCII
files I've already generated, and then just rerun POINT_STAT with the
mask. Ok, that will save some steps.
Alright, I'll try making the mask and do a test run after lunch, and
get
back to you when it works.
Thanks!
Roz
On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Hi Roz,
>
> I see you're wondering how to only use point observations over water
and
> discard the ones over land. You're running ASCII2NC followed by
Point-Stat
> and want to know where/how to define that masking.
>
> The ASCII2NC tool supports 3 command line options for filtering
point
> observations spatially: -mask_grid, -mask_poly, and -mask_sid, for
grid,
> polyline, and station ID masking, respectively. But that's not
really what
> you want. You want to do "data masking" where you read in a
land/sea mask
> and only use the points over water.
>
> I'd recommend running the Gen-Vx-Mask tool to create the desired
masking
> region, and then reference that in the Point-Stat config file.
>
> To illustrate, I pulled a sample GFS file:
> > wget
> https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> 4_20180702_0000_012.grb2
>
> Run wgrib2 and look for a LAND/SEA mask:
> > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
> 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
>
> Run plot_data_plane to see it (see attached image):
> > met-7.0/bin/plot_data_plane gfs_4_20180702_0000_012.grb2
gfs_4_LAND.ps
> 'name="LAND"; level="L0";'
>
> Run gen_vx_mask to create a mask for your verification domain. If
you're
> actually verifying on the GFS domain, the command looks a little
redundant:
>
> > /usr/local/met-7.0/bin/gen_vx_mask \
> gfs_4_20180702_0000_012.grb2 \
> gfs_4_20180702_0000_012.grb2 \
> gfs_4_WATER_mask.nc \
> -type data \
> -mask_field 'name="LAND"; level="L0";' \
> -thresh ==0 \
> -name WATER
>
> I defined the threshold as "==0" because we want the WATER points,
not the
> LAND points. And I used the "-name WATER" command line option to
name the
> output NetCDF variable. This will show up in the VX_MASK output
column of
> Point-Stat.
>
> Lastly, setup your Point-Stat config file like this:
>
> mask = {
> grid = [];
> poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> sid = [];
> }
>
> Hope that helps clarify.
>
> Thanks,
> John
>
>
> On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
> > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > Queue: met_help
> > Subject: masking land features questions
> > Owner: Nobody
> > Requestors: rosalyn.maccracken at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >
> >
> > Hi,
> >
> > I'm using ASCAT data to verify the GFS. I only want to verify
points
> over
> > the ocean, and not over any inland lakes. I noticed that I was
getting
> > matched points over land (mostly Africa). I'm dumping out the
MGDRlite
> > file to an ascii file, which I use ASCII2NC to create the netCDF
file,
> and
> > then go on to use Point_stat to create statistics for the matched
points.
> >
> > How do I mask out points over land before it gets to the
Point_stat step?
> > Is there something in the ASCII2NC processing that I can add, so I
don't
> > get these matched points?
> >
> > Thanks in advance!
> >
> > Roz
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 09 10:26:54 2018
Roz,
Yes, I expect that using met-6.0 would work fine. Hope it goes
smoothly.
Thanks,
John
On Mon, Jul 9, 2018 at 9: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=86091 >
>
> Hi John,
>
> I get the general idea and it looks pretty straight forward. I'm
still
> running MET6.0, since we had some installation issues, but, I should
be
> able to generate the mask with that pretty easily, correct?
>
> So, if this works, I'll need to rerun all my data from Mar 2018 -
present,
> using that method that we worked out earlier with the *.stat files,
> correct? Actually, I don't need to do that...I can start from the
ASCII
> files I've already generated, and then just rerun POINT_STAT with
the
> mask. Ok, that will save some steps.
>
> Alright, I'll try making the mask and do a test run after lunch, and
get
> back to you when it works.
>
> Thanks!
>
> Roz
>
> On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> > wrote:
>
> > Hi Roz,
> >
> > I see you're wondering how to only use point observations over
water and
> > discard the ones over land. You're running ASCII2NC followed by
> Point-Stat
> > and want to know where/how to define that masking.
> >
> > The ASCII2NC tool supports 3 command line options for filtering
point
> > observations spatially: -mask_grid, -mask_poly, and -mask_sid, for
grid,
> > polyline, and station ID masking, respectively. But that's not
really
> what
> > you want. You want to do "data masking" where you read in a
land/sea
> mask
> > and only use the points over water.
> >
> > I'd recommend running the Gen-Vx-Mask tool to create the desired
masking
> > region, and then reference that in the Point-Stat config file.
> >
> > To illustrate, I pulled a sample GFS file:
> > > wget
> > https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> > 4_20180702_0000_012.grb2
> >
> > Run wgrib2 and look for a LAND/SEA mask:
> > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
> > 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
> >
> > Run plot_data_plane to see it (see attached image):
> > > met-7.0/bin/plot_data_plane gfs_4_20180702_0000_012.grb2
> gfs_4_LAND.ps
> > 'name="LAND"; level="L0";'
> >
> > Run gen_vx_mask to create a mask for your verification domain. If
you're
> > actually verifying on the GFS domain, the command looks a little
> redundant:
> >
> > > /usr/local/met-7.0/bin/gen_vx_mask \
> > gfs_4_20180702_0000_012.grb2 \
> > gfs_4_20180702_0000_012.grb2 \
> > gfs_4_WATER_mask.nc \
> > -type data \
> > -mask_field 'name="LAND"; level="L0";' \
> > -thresh ==0 \
> > -name WATER
> >
> > I defined the threshold as "==0" because we want the WATER points,
not
> the
> > LAND points. And I used the "-name WATER" command line option to
name
> the
> > output NetCDF variable. This will show up in the VX_MASK output
column
> of
> > Point-Stat.
> >
> > Lastly, setup your Point-Stat config file like this:
> >
> > mask = {
> > grid = [];
> > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> > sid = [];
> > }
> >
> > Hope that helps clarify.
> >
> > Thanks,
> > John
> >
> >
> > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA Affiliate
via
> RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
> > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > Queue: met_help
> > > Subject: masking land features questions
> > > Owner: Nobody
> > > Requestors: rosalyn.maccracken at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> >
> > >
> > >
> > > Hi,
> > >
> > > I'm using ASCAT data to verify the GFS. I only want to verify
points
> > over
> > > the ocean, and not over any inland lakes. I noticed that I was
getting
> > > matched points over land (mostly Africa). I'm dumping out the
MGDRlite
> > > file to an ascii file, which I use ASCII2NC to create the netCDF
file,
> > and
> > > then go on to use Point_stat to create statistics for the
matched
> points.
> > >
> > > How do I mask out points over land before it gets to the
Point_stat
> step?
> > > Is there something in the ASCII2NC processing that I can add, so
I
> don't
> > > get these matched points?
> > >
> > > Thanks in advance!
> > >
> > > Roz
> > >
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Mon Jul 09 11:04:36 2018
Ok, I'll let you know if I can get the mask to work. This seems easy
enough, and pretty straight forward.
Thanks for the help!
Roz
On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Roz,
>
> Yes, I expect that using met-6.0 would work fine. Hope it goes
smoothly.
>
> Thanks,
> John
>
> On Mon, Jul 9, 2018 at 9: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=86091 >
> >
> > Hi John,
> >
> > I get the general idea and it looks pretty straight forward. I'm
still
> > running MET6.0, since we had some installation issues, but, I
should be
> > able to generate the mask with that pretty easily, correct?
> >
> > So, if this works, I'll need to rerun all my data from Mar 2018 -
> present,
> > using that method that we worked out earlier with the *.stat
files,
> > correct? Actually, I don't need to do that...I can start from the
ASCII
> > files I've already generated, and then just rerun POINT_STAT with
the
> > mask. Ok, that will save some steps.
> >
> > Alright, I'll try making the mask and do a test run after lunch,
and get
> > back to you when it works.
> >
> > Thanks!
> >
> > Roz
> >
> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > > Hi Roz,
> > >
> > > I see you're wondering how to only use point observations over
water
> and
> > > discard the ones over land. You're running ASCII2NC followed by
> > Point-Stat
> > > and want to know where/how to define that masking.
> > >
> > > The ASCII2NC tool supports 3 command line options for filtering
point
> > > observations spatially: -mask_grid, -mask_poly, and -mask_sid,
for
> grid,
> > > polyline, and station ID masking, respectively. But that's not
really
> > what
> > > you want. You want to do "data masking" where you read in a
land/sea
> > mask
> > > and only use the points over water.
> > >
> > > I'd recommend running the Gen-Vx-Mask tool to create the desired
> masking
> > > region, and then reference that in the Point-Stat config file.
> > >
> > > To illustrate, I pulled a sample GFS file:
> > > > wget
> > > https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> > > 4_20180702_0000_012.grb2
> > >
> > > Run wgrib2 and look for a LAND/SEA mask:
> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
> > > 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
> > >
> > > Run plot_data_plane to see it (see attached image):
> > > > met-7.0/bin/plot_data_plane gfs_4_20180702_0000_012.grb2
> > gfs_4_LAND.ps
> > > 'name="LAND"; level="L0";'
> > >
> > > Run gen_vx_mask to create a mask for your verification domain.
If
> you're
> > > actually verifying on the GFS domain, the command looks a little
> > redundant:
> > >
> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> > > gfs_4_20180702_0000_012.grb2 \
> > > gfs_4_20180702_0000_012.grb2 \
> > > gfs_4_WATER_mask.nc \
> > > -type data \
> > > -mask_field 'name="LAND"; level="L0";' \
> > > -thresh ==0 \
> > > -name WATER
> > >
> > > I defined the threshold as "==0" because we want the WATER
points, not
> > the
> > > LAND points. And I used the "-name WATER" command line option
to name
> > the
> > > output NetCDF variable. This will show up in the VX_MASK output
column
> > of
> > > Point-Stat.
> > >
> > > Lastly, setup your Point-Stat config file like this:
> > >
> > > mask = {
> > > grid = [];
> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> > > sid = [];
> > > }
> > >
> > > Hope that helps clarify.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA
Affiliate via
> > RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > Queue: met_help
> > > > Subject: masking land features questions
> > > > Owner: Nobody
> > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=86091
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm using ASCAT data to verify the GFS. I only want to verify
points
> > > over
> > > > the ocean, and not over any inland lakes. I noticed that I
was
> getting
> > > > matched points over land (mostly Africa). I'm dumping out the
> MGDRlite
> > > > file to an ascii file, which I use ASCII2NC to create the
netCDF
> file,
> > > and
> > > > then go on to use Point_stat to create statistics for the
matched
> > points.
> > > >
> > > > How do I mask out points over land before it gets to the
Point_stat
> > step?
> > > > Is there something in the ASCII2NC processing that I can add,
so I
> > don't
> > > > get these matched points?
> > > >
> > > > Thanks in advance!
> > > >
> > > > Roz
> > > >
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Mon Jul 09 11:47:44 2018
Hey John,
I have 2 problems. First, I'm able to use plot_data_plane, but, when
I use
the command for gen_vx_mask, I get this:
/opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data -mask_field
'name="LAND"; level="L0";' -thresh ==0 -name WATER
/opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
libraries:
libgsl.so.0: cannot open shared object file: No such file or directory
Now, they are both in the same directory, and I know that I've used
gen_vx_mask before, so, I have no idea why I would be getting that
error
message. Any ideas?
Then, I was able to generate a *.ps file, which looks exactly like
yours,
but, there is still the same problem. If you look closely are your
map,
you'll see these little white dots over land. Those are lakes, and
that's
what is giving me a fit, because I have ASCAT observations over those
white
dots. You know, I'm using 0.25 deg GFS data with 12 km ASCAT
data...so,
very sensitive. Anyway, do you have any idea how to get rid of those
points? Perhaps a different file with the same domain?
Roz
On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA Affiliate <
rosalyn.maccracken at noaa.gov> wrote:
> Ok, I'll let you know if I can get the mask to work. This seems
easy
> enough, and pretty straight forward.
>
> Thanks for the help!
>
> Roz
>
> On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Roz,
>>
>> Yes, I expect that using met-6.0 would work fine. Hope it goes
smoothly.
>>
>> Thanks,
>> John
>>
>> On Mon, Jul 9, 2018 at 9: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=86091 >
>> >
>> > Hi John,
>> >
>> > I get the general idea and it looks pretty straight forward. I'm
still
>> > running MET6.0, since we had some installation issues, but, I
should be
>> > able to generate the mask with that pretty easily, correct?
>> >
>> > So, if this works, I'll need to rerun all my data from Mar 2018 -
>> present,
>> > using that method that we worked out earlier with the *.stat
files,
>> > correct? Actually, I don't need to do that...I can start from
the ASCII
>> > files I've already generated, and then just rerun POINT_STAT with
the
>> > mask. Ok, that will save some steps.
>> >
>> > Alright, I'll try making the mask and do a test run after lunch,
and get
>> > back to you when it works.
>> >
>> > Thanks!
>> >
>> > Roz
>> >
>> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
>> > met_help at ucar.edu
>> > > wrote:
>> >
>> > > Hi Roz,
>> > >
>> > > I see you're wondering how to only use point observations over
water
>> and
>> > > discard the ones over land. You're running ASCII2NC followed
by
>> > Point-Stat
>> > > and want to know where/how to define that masking.
>> > >
>> > > The ASCII2NC tool supports 3 command line options for filtering
point
>> > > observations spatially: -mask_grid, -mask_poly, and -mask_sid,
for
>> grid,
>> > > polyline, and station ID masking, respectively. But that's not
really
>> > what
>> > > you want. You want to do "data masking" where you read in a
land/sea
>> > mask
>> > > and only use the points over water.
>> > >
>> > > I'd recommend running the Gen-Vx-Mask tool to create the
desired
>> masking
>> > > region, and then reference that in the Point-Stat config file.
>> > >
>> > > To illustrate, I pulled a sample GFS file:
>> > > > wget
>> > > https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
>> > > 4_20180702_0000_012.grb2
>> > >
>> > > Run wgrib2 and look for a LAND/SEA mask:
>> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
>> > > 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
>> > >
>> > > Run plot_data_plane to see it (see attached image):
>> > > > met-7.0/bin/plot_data_plane gfs_4_20180702_0000_012.grb2
>> > gfs_4_LAND.ps
>> > > 'name="LAND"; level="L0";'
>> > >
>> > > Run gen_vx_mask to create a mask for your verification domain.
If
>> you're
>> > > actually verifying on the GFS domain, the command looks a
little
>> > redundant:
>> > >
>> > > > /usr/local/met-7.0/bin/gen_vx_mask \
>> > > gfs_4_20180702_0000_012.grb2 \
>> > > gfs_4_20180702_0000_012.grb2 \
>> > > gfs_4_WATER_mask.nc \
>> > > -type data \
>> > > -mask_field 'name="LAND"; level="L0";' \
>> > > -thresh ==0 \
>> > > -name WATER
>> > >
>> > > I defined the threshold as "==0" because we want the WATER
points, not
>> > the
>> > > LAND points. And I used the "-name WATER" command line option
to name
>> > the
>> > > output NetCDF variable. This will show up in the VX_MASK
output
>> column
>> > of
>> > > Point-Stat.
>> > >
>> > > Lastly, setup your Point-Stat config file like this:
>> > >
>> > > mask = {
>> > > grid = [];
>> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
>> > > sid = [];
>> > > }
>> > >
>> > > Hope that helps clarify.
>> > >
>> > > Thanks,
>> > > John
>> > >
>> > >
>> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA
Affiliate via
>> > RT <
>> > > met_help at ucar.edu> wrote:
>> > >
>> > > >
>> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
>> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
>> > > > Queue: met_help
>> > > > Subject: masking land features questions
>> > > > Owner: Nobody
>> > > > Requestors: rosalyn.maccracken at noaa.gov
>> > > > Status: new
>> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
>> ket/Display.html?id=86091
>> > >
>> > > >
>> > > >
>> > > > Hi,
>> > > >
>> > > > I'm using ASCAT data to verify the GFS. I only want to
verify
>> points
>> > > over
>> > > > the ocean, and not over any inland lakes. I noticed that I
was
>> getting
>> > > > matched points over land (mostly Africa). I'm dumping out
the
>> MGDRlite
>> > > > file to an ascii file, which I use ASCII2NC to create the
netCDF
>> file,
>> > > and
>> > > > then go on to use Point_stat to create statistics for the
matched
>> > points.
>> > > >
>> > > > How do I mask out points over land before it gets to the
Point_stat
>> > step?
>> > > > Is there something in the ASCII2NC processing that I can add,
so I
>> > don't
>> > > > get these matched points?
>> > > >
>> > > > Thanks in advance!
>> > > >
>> > > > Roz
>> > > >
>> > > > --
>> > > > Rosalyn MacCracken
>> > > > Support Scientist
>> > > >
>> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 09 14:44:28 2018
Roz,
Whenever you see that error about loading shared libraries, it means
that
there's a problem in how your LD_LIBRARY_PATH environment variable is
set.
That environment variable tells the linker where to look for shared
libraries at runtime... one of those shared libraries is GSL (GNU
Scientific Library). You'd "fix" this issue by modifying how
LD_LIBRARY_PATH is set:
echo $LD_LIBRARY_PATH
Take a look in your ~/.cshrc file for c-shell or ~/.bashrc for bash to
see
how its set.
As for the LAND/SEA mask, I was wondering if those lakes would be a
problem. Using the model's LAND/SEA mask is the easiest, but doesn't
provide an easy way of selecting out oceans. My next thought was to
use
GIS Shapefiles to define only the ocean area. That will be available
in
the next version of MET, version 7.1. I tried using a beta release
for
met-7.1, but ran into problems when applying large polylines to global
grids.
I'll keep thinking about that one.
Thanks,
John
On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
> Hey John,
>
> I have 2 problems. First, I'm able to use plot_data_plane, but,
when I use
> the command for gen_vx_mask, I get this:
> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data -mask_field
> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
libraries:
> libgsl.so.0: cannot open shared object file: No such file or
directory
>
> Now, they are both in the same directory, and I know that I've used
> gen_vx_mask before, so, I have no idea why I would be getting that
error
> message. Any ideas?
>
> Then, I was able to generate a *.ps file, which looks exactly like
yours,
> but, there is still the same problem. If you look closely are your
map,
> you'll see these little white dots over land. Those are lakes, and
that's
> what is giving me a fit, because I have ASCAT observations over
those white
> dots. You know, I'm using 0.25 deg GFS data with 12 km ASCAT
data...so,
> very sensitive. Anyway, do you have any idea how to get rid of
those
> points? Perhaps a different file with the same domain?
>
> Roz
>
> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA Affiliate
<
> rosalyn.maccracken at noaa.gov> wrote:
>
> > Ok, I'll let you know if I can get the mask to work. This seems
easy
> > enough, and pretty straight forward.
> >
> > Thanks for the help!
> >
> > Roz
> >
> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Roz,
> >>
> >> Yes, I expect that using met-6.0 would work fine. Hope it goes
> smoothly.
> >>
> >> Thanks,
> >> John
> >>
> >> On Mon, Jul 9, 2018 at 9: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=86091 >
> >> >
> >> > Hi John,
> >> >
> >> > I get the general idea and it looks pretty straight forward.
I'm
> still
> >> > running MET6.0, since we had some installation issues, but, I
should
> be
> >> > able to generate the mask with that pretty easily, correct?
> >> >
> >> > So, if this works, I'll need to rerun all my data from Mar 2018
-
> >> present,
> >> > using that method that we worked out earlier with the *.stat
files,
> >> > correct? Actually, I don't need to do that...I can start from
the
> ASCII
> >> > files I've already generated, and then just rerun POINT_STAT
with the
> >> > mask. Ok, that will save some steps.
> >> >
> >> > Alright, I'll try making the mask and do a test run after
lunch, and
> get
> >> > back to you when it works.
> >> >
> >> > Thanks!
> >> >
> >> > Roz
> >> >
> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
> >> > met_help at ucar.edu
> >> > > wrote:
> >> >
> >> > > Hi Roz,
> >> > >
> >> > > I see you're wondering how to only use point observations
over water
> >> and
> >> > > discard the ones over land. You're running ASCII2NC followed
by
> >> > Point-Stat
> >> > > and want to know where/how to define that masking.
> >> > >
> >> > > The ASCII2NC tool supports 3 command line options for
filtering
> point
> >> > > observations spatially: -mask_grid, -mask_poly, and
-mask_sid, for
> >> grid,
> >> > > polyline, and station ID masking, respectively. But that's
not
> really
> >> > what
> >> > > you want. You want to do "data masking" where you read in a
> land/sea
> >> > mask
> >> > > and only use the points over water.
> >> > >
> >> > > I'd recommend running the Gen-Vx-Mask tool to create the
desired
> >> masking
> >> > > region, and then reference that in the Point-Stat config
file.
> >> > >
> >> > > To illustrate, I pulled a sample GFS file:
> >> > > > wget
> >> > > https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> >> > > 4_20180702_0000_012.grb2
> >> > >
> >> > > Run wgrib2 and look for a LAND/SEA mask:
> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
> >> > >
> >> > > Run plot_data_plane to see it (see attached image):
> >> > > > met-7.0/bin/plot_data_plane gfs_4_20180702_0000_012.grb2
> >> > gfs_4_LAND.ps
> >> > > 'name="LAND"; level="L0";'
> >> > >
> >> > > Run gen_vx_mask to create a mask for your verification
domain. If
> >> you're
> >> > > actually verifying on the GFS domain, the command looks a
little
> >> > redundant:
> >> > >
> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > > gfs_4_WATER_mask.nc \
> >> > > -type data \
> >> > > -mask_field 'name="LAND"; level="L0";' \
> >> > > -thresh ==0 \
> >> > > -name WATER
> >> > >
> >> > > I defined the threshold as "==0" because we want the WATER
points,
> not
> >> > the
> >> > > LAND points. And I used the "-name WATER" command line
option to
> name
> >> > the
> >> > > output NetCDF variable. This will show up in the VX_MASK
output
> >> column
> >> > of
> >> > > Point-Stat.
> >> > >
> >> > > Lastly, setup your Point-Stat config file like this:
> >> > >
> >> > > mask = {
> >> > > grid = [];
> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> >> > > sid = [];
> >> > > }
> >> > >
> >> > > Hope that helps clarify.
> >> > >
> >> > > Thanks,
> >> > > John
> >> > >
> >> > >
> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA
Affiliate
> via
> >> > RT <
> >> > > met_help at ucar.edu> wrote:
> >> > >
> >> > > >
> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
> >> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> >> > > > Queue: met_help
> >> > > > Subject: masking land features questions
> >> > > > Owner: Nobody
> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> >> > > > Status: new
> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> >> ket/Display.html?id=86091
> >> > >
> >> > > >
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > I'm using ASCAT data to verify the GFS. I only want to
verify
> >> points
> >> > > over
> >> > > > the ocean, and not over any inland lakes. I noticed that I
was
> >> getting
> >> > > > matched points over land (mostly Africa). I'm dumping out
the
> >> MGDRlite
> >> > > > file to an ascii file, which I use ASCII2NC to create the
netCDF
> >> file,
> >> > > and
> >> > > > then go on to use Point_stat to create statistics for the
matched
> >> > points.
> >> > > >
> >> > > > How do I mask out points over land before it gets to the
> Point_stat
> >> > step?
> >> > > > Is there something in the ASCII2NC processing that I can
add, so I
> >> > don't
> >> > > > get these matched points?
> >> > > >
> >> > > > Thanks in advance!
> >> > > >
> >> > > > Roz
> >> > > >
> >> > > > --
> >> > > > Rosalyn MacCracken
> >> > > > Support Scientist
> >> > > >
> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 09 15:04:14 2018
Roz,
I talked to some folks and have one suggestion that *might* work. The
WRF
Pre-processing system is named WPS. The geogrid program within WPS is
used
to initialize your domain and handles land use information. By
default,
lakes and oceans are treated the same way. However, apparently there
is an
option to distinguish between them. Take a look here:
http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/users_guide_chap3.htm#_Description_of_the_1
And search for "Alternative Initialization of Lake SSTs".
So you'd...
(1) download the MODIS SST data
(2) configure geogrid for the 0.25 degree GFS grid
(3) configure geogrid to distinguish between lakes and oceans
(4) run geogrid
(5) run the output through the MET gen_vx_mask tool to use ocean
values and
skip the lake values
Thanks,
John
On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Roz,
>
> Whenever you see that error about loading shared libraries, it means
that
> there's a problem in how your LD_LIBRARY_PATH environment variable
is set.
> That environment variable tells the linker where to look for shared
> libraries at runtime... one of those shared libraries is GSL (GNU
> Scientific Library). You'd "fix" this issue by modifying how
> LD_LIBRARY_PATH is set:
> echo $LD_LIBRARY_PATH
>
> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc for bash
to see
> how its set.
>
> As for the LAND/SEA mask, I was wondering if those lakes would be a
> problem. Using the model's LAND/SEA mask is the easiest, but
doesn't
> provide an easy way of selecting out oceans. My next thought was to
use
> GIS Shapefiles to define only the ocean area. That will be
available in
> the next version of MET, version 7.1. I tried using a beta release
for
> met-7.1, but ran into problems when applying large polylines to
global
> grids.
>
> I'll keep thinking about that one.
>
> Thanks,
> John
>
> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA Affiliate
via RT
> <met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>>
>> Hey John,
>>
>> I have 2 problems. First, I'm able to use plot_data_plane, but,
when I
>> use
>> the command for gen_vx_mask, I get this:
>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data -mask_field
>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
libraries:
>> libgsl.so.0: cannot open shared object file: No such file or
directory
>>
>> Now, they are both in the same directory, and I know that I've used
>> gen_vx_mask before, so, I have no idea why I would be getting that
error
>> message. Any ideas?
>>
>> Then, I was able to generate a *.ps file, which looks exactly like
yours,
>> but, there is still the same problem. If you look closely are your
map,
>> you'll see these little white dots over land. Those are lakes, and
that's
>> what is giving me a fit, because I have ASCAT observations over
those
>> white
>> dots. You know, I'm using 0.25 deg GFS data with 12 km ASCAT
data...so,
>> very sensitive. Anyway, do you have any idea how to get rid of
those
>> points? Perhaps a different file with the same domain?
>>
>> Roz
>>
>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA Affiliate
<
>> rosalyn.maccracken at noaa.gov> wrote:
>>
>> > Ok, I'll let you know if I can get the mask to work. This seems
easy
>> > enough, and pretty straight forward.
>> >
>> > Thanks for the help!
>> >
>> > Roz
>> >
>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT <
>> > met_help at ucar.edu> wrote:
>> >
>> >> Roz,
>> >>
>> >> Yes, I expect that using met-6.0 would work fine. Hope it goes
>> smoothly.
>> >>
>> >> Thanks,
>> >> John
>> >>
>> >> On Mon, Jul 9, 2018 at 9: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=86091
>
>> >> >
>> >> > Hi John,
>> >> >
>> >> > I get the general idea and it looks pretty straight forward.
I'm
>> still
>> >> > running MET6.0, since we had some installation issues, but, I
should
>> be
>> >> > able to generate the mask with that pretty easily, correct?
>> >> >
>> >> > So, if this works, I'll need to rerun all my data from Mar
2018 -
>> >> present,
>> >> > using that method that we worked out earlier with the *.stat
files,
>> >> > correct? Actually, I don't need to do that...I can start from
the
>> ASCII
>> >> > files I've already generated, and then just rerun POINT_STAT
with the
>> >> > mask. Ok, that will save some steps.
>> >> >
>> >> > Alright, I'll try making the mask and do a test run after
lunch, and
>> get
>> >> > back to you when it works.
>> >> >
>> >> > Thanks!
>> >> >
>> >> > Roz
>> >> >
>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
>> >> > met_help at ucar.edu
>> >> > > wrote:
>> >> >
>> >> > > Hi Roz,
>> >> > >
>> >> > > I see you're wondering how to only use point observations
over
>> water
>> >> and
>> >> > > discard the ones over land. You're running ASCII2NC
followed by
>> >> > Point-Stat
>> >> > > and want to know where/how to define that masking.
>> >> > >
>> >> > > The ASCII2NC tool supports 3 command line options for
filtering
>> point
>> >> > > observations spatially: -mask_grid, -mask_poly, and
-mask_sid, for
>> >> grid,
>> >> > > polyline, and station ID masking, respectively. But that's
not
>> really
>> >> > what
>> >> > > you want. You want to do "data masking" where you read in a
>> land/sea
>> >> > mask
>> >> > > and only use the points over water.
>> >> > >
>> >> > > I'd recommend running the Gen-Vx-Mask tool to create the
desired
>> >> masking
>> >> > > region, and then reference that in the Point-Stat config
file.
>> >> > >
>> >> > > To illustrate, I pulled a sample GFS file:
>> >> > > > wget
>> >> > > https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
>> >> > > 4_20180702_0000_012.grb2
>> >> > >
>> >> > > Run wgrib2 and look for a LAND/SEA mask:
>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
>> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
>> >> > >
>> >> > > Run plot_data_plane to see it (see attached image):
>> >> > > > met-7.0/bin/plot_data_plane
gfs_4_20180702_0000_012.grb2
>> >> > gfs_4_LAND.ps
>> >> > > 'name="LAND"; level="L0";'
>> >> > >
>> >> > > Run gen_vx_mask to create a mask for your verification
domain. If
>> >> you're
>> >> > > actually verifying on the GFS domain, the command looks a
little
>> >> > redundant:
>> >> > >
>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
>> >> > > gfs_4_20180702_0000_012.grb2 \
>> >> > > gfs_4_20180702_0000_012.grb2 \
>> >> > > gfs_4_WATER_mask.nc \
>> >> > > -type data \
>> >> > > -mask_field 'name="LAND"; level="L0";' \
>> >> > > -thresh ==0 \
>> >> > > -name WATER
>> >> > >
>> >> > > I defined the threshold as "==0" because we want the WATER
points,
>> not
>> >> > the
>> >> > > LAND points. And I used the "-name WATER" command line
option to
>> name
>> >> > the
>> >> > > output NetCDF variable. This will show up in the VX_MASK
output
>> >> column
>> >> > of
>> >> > > Point-Stat.
>> >> > >
>> >> > > Lastly, setup your Point-Stat config file like this:
>> >> > >
>> >> > > mask = {
>> >> > > grid = [];
>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
>> >> > > sid = [];
>> >> > > }
>> >> > >
>> >> > > Hope that helps clarify.
>> >> > >
>> >> > > Thanks,
>> >> > > John
>> >> > >
>> >> > >
>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA
Affiliate
>> via
>> >> > RT <
>> >> > > met_help at ucar.edu> wrote:
>> >> > >
>> >> > > >
>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
>> >> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
>> >> > > > Queue: met_help
>> >> > > > Subject: masking land features questions
>> >> > > > Owner: Nobody
>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
>> >> > > > Status: new
>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
>> >> ket/Display.html?id=86091
>> >> > >
>> >> > > >
>> >> > > >
>> >> > > > Hi,
>> >> > > >
>> >> > > > I'm using ASCAT data to verify the GFS. I only want to
verify
>> >> points
>> >> > > over
>> >> > > > the ocean, and not over any inland lakes. I noticed that
I was
>> >> getting
>> >> > > > matched points over land (mostly Africa). I'm dumping out
the
>> >> MGDRlite
>> >> > > > file to an ascii file, which I use ASCII2NC to create the
netCDF
>> >> file,
>> >> > > and
>> >> > > > then go on to use Point_stat to create statistics for the
matched
>> >> > points.
>> >> > > >
>> >> > > > How do I mask out points over land before it gets to the
>> Point_stat
>> >> > step?
>> >> > > > Is there something in the ASCII2NC processing that I can
add, so
>> I
>> >> > don't
>> >> > > > get these matched points?
>> >> > > >
>> >> > > > Thanks in advance!
>> >> > > >
>> >> > > > Roz
>> >> > > >
>> >> > > > --
>> >> > > > Rosalyn MacCracken
>> >> > > > Support Scientist
>> >> > > >
>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 09 15:39:42 2018
Roz,
OK, one other possible option to consider. I figured that there's
plenty
of "ocean" products out there. So I found a NOAA WAVEWATCH one:
(1) Download sample wavewatch file:
wget
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/gwes.20180708/gwes01.glo_30m.t00z.grib2
(2) Run regrid_data_plane to put some surface wind speed data on the
1/4
GFS grid:
regrid_data_plane gwes01.glo_30m.t00z.grib2 G193 ocean_data.nc
-field
'name="WIND"; level="L0";'
(3) Run gen_vx_mask to select points that contain valid data:
gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc -type data
-mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999 -name OCEAN
(4) Run plot_data_plane to see the result:
plot_data_plane ocean_mask.nc ocean_mask.ps 'name="OCEAN";
level="(*,*)";'
As you can see, the result gets rid of the lakes problem. But
wavewatch is
only run to +/- 80 degrees, so we're not including points near the
poles.
Figured this would be a lot easier than running WPS yourself.
Thanks,
John
On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Roz,
>
> I talked to some folks and have one suggestion that *might* work.
The WRF
> Pre-processing system is named WPS. The geogrid program within WPS
is used
> to initialize your domain and handles land use information. By
default,
> lakes and oceans are treated the same way. However, apparently
there is an
> option to distinguish between them. Take a look here:
>
>
http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/users_guide_chap3.htm#_Description_of_the_1
>
> And search for "Alternative Initialization of Lake SSTs".
>
> So you'd...
> (1) download the MODIS SST data
> (2) configure geogrid for the 0.25 degree GFS grid
> (3) configure geogrid to distinguish between lakes and oceans
> (4) run geogrid
> (5) run the output through the MET gen_vx_mask tool to use ocean
values
> and skip the lake values
>
> Thanks,
> John
>
> On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
>
>> Roz,
>>
>> Whenever you see that error about loading shared libraries, it
means that
>> there's a problem in how your LD_LIBRARY_PATH environment variable
is set.
>> That environment variable tells the linker where to look for shared
>> libraries at runtime... one of those shared libraries is GSL (GNU
>> Scientific Library). You'd "fix" this issue by modifying how
>> LD_LIBRARY_PATH is set:
>> echo $LD_LIBRARY_PATH
>>
>> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc for bash
to
>> see how its set.
>>
>> As for the LAND/SEA mask, I was wondering if those lakes would be a
>> problem. Using the model's LAND/SEA mask is the easiest, but
doesn't
>> provide an easy way of selecting out oceans. My next thought was
to use
>> GIS Shapefiles to define only the ocean area. That will be
available in
>> the next version of MET, version 7.1. I tried using a beta release
for
>> met-7.1, but ran into problems when applying large polylines to
global
>> grids.
>>
>> I'll keep thinking about that one.
>>
>> Thanks,
>> John
>>
>> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA Affiliate
via
>> RT <met_help at ucar.edu> wrote:
>>
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>>>
>>> Hey John,
>>>
>>> I have 2 problems. First, I'm able to use plot_data_plane, but,
when I
>>> use
>>> the command for gen_vx_mask, I get this:
>>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
>>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
-mask_field
>>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
>>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
libraries:
>>> libgsl.so.0: cannot open shared object file: No such file or
directory
>>>
>>> Now, they are both in the same directory, and I know that I've
used
>>> gen_vx_mask before, so, I have no idea why I would be getting that
error
>>> message. Any ideas?
>>>
>>> Then, I was able to generate a *.ps file, which looks exactly like
yours,
>>> but, there is still the same problem. If you look closely are
your map,
>>> you'll see these little white dots over land. Those are lakes,
and
>>> that's
>>> what is giving me a fit, because I have ASCAT observations over
those
>>> white
>>> dots. You know, I'm using 0.25 deg GFS data with 12 km ASCAT
data...so,
>>> very sensitive. Anyway, do you have any idea how to get rid of
those
>>> points? Perhaps a different file with the same domain?
>>>
>>> Roz
>>>
>>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA
Affiliate <
>>> rosalyn.maccracken at noaa.gov> wrote:
>>>
>>> > Ok, I'll let you know if I can get the mask to work. This seems
easy
>>> > enough, and pretty straight forward.
>>> >
>>> > Thanks for the help!
>>> >
>>> > Roz
>>> >
>>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT <
>>> > met_help at ucar.edu> wrote:
>>> >
>>> >> Roz,
>>> >>
>>> >> Yes, I expect that using met-6.0 would work fine. Hope it goes
>>> smoothly.
>>> >>
>>> >> Thanks,
>>> >> John
>>> >>
>>> >> On Mon, Jul 9, 2018 at 9: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=86091
>
>>> >> >
>>> >> > Hi John,
>>> >> >
>>> >> > I get the general idea and it looks pretty straight forward.
I'm
>>> still
>>> >> > running MET6.0, since we had some installation issues, but, I
>>> should be
>>> >> > able to generate the mask with that pretty easily, correct?
>>> >> >
>>> >> > So, if this works, I'll need to rerun all my data from Mar
2018 -
>>> >> present,
>>> >> > using that method that we worked out earlier with the *.stat
files,
>>> >> > correct? Actually, I don't need to do that...I can start
from the
>>> ASCII
>>> >> > files I've already generated, and then just rerun POINT_STAT
with
>>> the
>>> >> > mask. Ok, that will save some steps.
>>> >> >
>>> >> > Alright, I'll try making the mask and do a test run after
lunch,
>>> and get
>>> >> > back to you when it works.
>>> >> >
>>> >> > Thanks!
>>> >> >
>>> >> > Roz
>>> >> >
>>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
>>> >> > met_help at ucar.edu
>>> >> > > wrote:
>>> >> >
>>> >> > > Hi Roz,
>>> >> > >
>>> >> > > I see you're wondering how to only use point observations
over
>>> water
>>> >> and
>>> >> > > discard the ones over land. You're running ASCII2NC
followed by
>>> >> > Point-Stat
>>> >> > > and want to know where/how to define that masking.
>>> >> > >
>>> >> > > The ASCII2NC tool supports 3 command line options for
filtering
>>> point
>>> >> > > observations spatially: -mask_grid, -mask_poly, and
-mask_sid, for
>>> >> grid,
>>> >> > > polyline, and station ID masking, respectively. But that's
not
>>> really
>>> >> > what
>>> >> > > you want. You want to do "data masking" where you read in
a
>>> land/sea
>>> >> > mask
>>> >> > > and only use the points over water.
>>> >> > >
>>> >> > > I'd recommend running the Gen-Vx-Mask tool to create the
desired
>>> >> masking
>>> >> > > region, and then reference that in the Point-Stat config
file.
>>> >> > >
>>> >> > > To illustrate, I pulled a sample GFS file:
>>> >> > > > wget
>>> >> > > https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
>>> >> > > 4_20180702_0000_012.grb2
>>> >> > >
>>> >> > > Run wgrib2 and look for a LAND/SEA mask:
>>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
>>> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour fcst:
>>> >> > >
>>> >> > > Run plot_data_plane to see it (see attached image):
>>> >> > > > met-7.0/bin/plot_data_plane
gfs_4_20180702_0000_012.grb2
>>> >> > gfs_4_LAND.ps
>>> >> > > 'name="LAND"; level="L0";'
>>> >> > >
>>> >> > > Run gen_vx_mask to create a mask for your verification
domain. If
>>> >> you're
>>> >> > > actually verifying on the GFS domain, the command looks a
little
>>> >> > redundant:
>>> >> > >
>>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
>>> >> > > gfs_4_20180702_0000_012.grb2 \
>>> >> > > gfs_4_20180702_0000_012.grb2 \
>>> >> > > gfs_4_WATER_mask.nc \
>>> >> > > -type data \
>>> >> > > -mask_field 'name="LAND"; level="L0";' \
>>> >> > > -thresh ==0 \
>>> >> > > -name WATER
>>> >> > >
>>> >> > > I defined the threshold as "==0" because we want the WATER
>>> points, not
>>> >> > the
>>> >> > > LAND points. And I used the "-name WATER" command line
option to
>>> name
>>> >> > the
>>> >> > > output NetCDF variable. This will show up in the VX_MASK
output
>>> >> column
>>> >> > of
>>> >> > > Point-Stat.
>>> >> > >
>>> >> > > Lastly, setup your Point-Stat config file like this:
>>> >> > >
>>> >> > > mask = {
>>> >> > > grid = [];
>>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
>>> >> > > sid = [];
>>> >> > > }
>>> >> > >
>>> >> > > Hope that helps clarify.
>>> >> > >
>>> >> > > Thanks,
>>> >> > > John
>>> >> > >
>>> >> > >
>>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA
>>> Affiliate via
>>> >> > RT <
>>> >> > > met_help at ucar.edu> wrote:
>>> >> > >
>>> >> > > >
>>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
>>> >> > > > Transaction: Ticket created by
rosalyn.maccracken at noaa.gov
>>> >> > > > Queue: met_help
>>> >> > > > Subject: masking land features questions
>>> >> > > > Owner: Nobody
>>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
>>> >> > > > Status: new
>>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
>>> >> ket/Display.html?id=86091
>>> >> > >
>>> >> > > >
>>> >> > > >
>>> >> > > > Hi,
>>> >> > > >
>>> >> > > > I'm using ASCAT data to verify the GFS. I only want to
verify
>>> >> points
>>> >> > > over
>>> >> > > > the ocean, and not over any inland lakes. I noticed that
I was
>>> >> getting
>>> >> > > > matched points over land (mostly Africa). I'm dumping
out the
>>> >> MGDRlite
>>> >> > > > file to an ascii file, which I use ASCII2NC to create the
netCDF
>>> >> file,
>>> >> > > and
>>> >> > > > then go on to use Point_stat to create statistics for the
>>> matched
>>> >> > points.
>>> >> > > >
>>> >> > > > How do I mask out points over land before it gets to the
>>> Point_stat
>>> >> > step?
>>> >> > > > Is there something in the ASCII2NC processing that I can
add,
>>> so I
>>> >> > don't
>>> >> > > > get these matched points?
>>> >> > > >
>>> >> > > > Thanks in advance!
>>> >> > > >
>>> >> > > > Roz
>>> >> > > >
>>> >> > > > --
>>> >> > > > Rosalyn MacCracken
>>> >> > > > Support Scientist
>>> >> > > >
>>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Tue Jul 10 09:58:04 2018
Hi John,
I'm really not having much luck today with this. Maybe I should have
stayed in bed (haha).
So, the first thing I did was check the LD_LIBRARY_PATH, and it's
pointing
to the MET7 directories. Ok, that could be most of the problem. MET7
seems
to be having some issue, and the guy here at OPC that helps me with
that
stuff (Chris Juckins) is out on leave until tomorrow. Anyway, MET7 is
not
running any of my verification programs, and giving out some errors,
so,
I'll have to get with him tomorrow to fix that.
So, in the mean time, I don't think that any kind of land mask
creation
that I'm doing today will work because it's not pointing at the right
directories.
But, when I do get this to work, I tried this and got this error:
/opt/MET6/met6.0/bin/regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
ocean_data.nc -field 'name="WIND"; level="L0";'
DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321 lat_ll:
-80.000
lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
ERROR :
ERROR : grd_file_type() -> file does not exist "G193"
ERROR :
I'm wondering if that's all related to MET7.
So, I think I need to fix the MET7 issue before moving on with this,
don't
you?
Roz
On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Roz,
>
> OK, one other possible option to consider. I figured that there's
plenty
> of "ocean" products out there. So I found a NOAA WAVEWATCH one:
>
> (1) Download sample wavewatch file:
> wget
> ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> gwes.20180708/gwes01.glo_30m.t00z.grib2
>
> (2) Run regrid_data_plane to put some surface wind speed data on the
1/4
> GFS grid:
> regrid_data_plane gwes01.glo_30m.t00z.grib2 G193 ocean_data.nc
-field
> 'name="WIND"; level="L0";'
>
> (3) Run gen_vx_mask to select points that contain valid data:
> gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc -type data
> -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999 -name
OCEAN
>
> (4) Run plot_data_plane to see the result:
> plot_data_plane ocean_mask.nc ocean_mask.ps 'name="OCEAN";
> level="(*,*)";'
>
> As you can see, the result gets rid of the lakes problem. But
wavewatch is
> only run to +/- 80 degrees, so we're not including points near the
poles.
>
> Figured this would be a lot easier than running WPS yourself.
>
> Thanks,
> John
>
>
> On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
>
> > Roz,
> >
> > I talked to some folks and have one suggestion that *might* work.
The
> WRF
> > Pre-processing system is named WPS. The geogrid program within
WPS is
> used
> > to initialize your domain and handles land use information. By
default,
> > lakes and oceans are treated the same way. However, apparently
there is
> an
> > option to distinguish between them. Take a look here:
> >
> > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> users_guide_chap3.htm#_Description_of_the_1
> >
> > And search for "Alternative Initialization of Lake SSTs".
> >
> > So you'd...
> > (1) download the MODIS SST data
> > (2) configure geogrid for the 0.25 degree GFS grid
> > (3) configure geogrid to distinguish between lakes and oceans
> > (4) run geogrid
> > (5) run the output through the MET gen_vx_mask tool to use ocean
values
> > and skip the lake values
> >
> > Thanks,
> > John
> >
> > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway
<johnhg at ucar.edu>
> wrote:
> >
> >> Roz,
> >>
> >> Whenever you see that error about loading shared libraries, it
means
> that
> >> there's a problem in how your LD_LIBRARY_PATH environment
variable is
> set.
> >> That environment variable tells the linker where to look for
shared
> >> libraries at runtime... one of those shared libraries is GSL (GNU
> >> Scientific Library). You'd "fix" this issue by modifying how
> >> LD_LIBRARY_PATH is set:
> >> echo $LD_LIBRARY_PATH
> >>
> >> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc for
bash to
> >> see how its set.
> >>
> >> As for the LAND/SEA mask, I was wondering if those lakes would be
a
> >> problem. Using the model's LAND/SEA mask is the easiest, but
doesn't
> >> provide an easy way of selecting out oceans. My next thought was
to use
> >> GIS Shapefiles to define only the ocean area. That will be
available in
> >> the next version of MET, version 7.1. I tried using a beta
release for
> >> met-7.1, but ran into problems when applying large polylines to
global
> >> grids.
> >>
> >> I'll keep thinking about that one.
> >>
> >> Thanks,
> >> John
> >>
> >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA
Affiliate via
> >> RT <met_help at ucar.edu> wrote:
> >>
> >>>
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >>>
> >>> Hey John,
> >>>
> >>> I have 2 problems. First, I'm able to use plot_data_plane, but,
when I
> >>> use
> >>> the command for gen_vx_mask, I get this:
> >>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
> >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
-mask_field
> >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
> libraries:
> >>> libgsl.so.0: cannot open shared object file: No such file or
directory
> >>>
> >>> Now, they are both in the same directory, and I know that I've
used
> >>> gen_vx_mask before, so, I have no idea why I would be getting
that
> error
> >>> message. Any ideas?
> >>>
> >>> Then, I was able to generate a *.ps file, which looks exactly
like
> yours,
> >>> but, there is still the same problem. If you look closely are
your
> map,
> >>> you'll see these little white dots over land. Those are lakes,
and
> >>> that's
> >>> what is giving me a fit, because I have ASCAT observations over
those
> >>> white
> >>> dots. You know, I'm using 0.25 deg GFS data with 12 km ASCAT
> data...so,
> >>> very sensitive. Anyway, do you have any idea how to get rid of
those
> >>> points? Perhaps a different file with the same domain?
> >>>
> >>> Roz
> >>>
> >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA
Affiliate <
> >>> rosalyn.maccracken at noaa.gov> wrote:
> >>>
> >>> > Ok, I'll let you know if I can get the mask to work. This
seems easy
> >>> > enough, and pretty straight forward.
> >>> >
> >>> > Thanks for the help!
> >>> >
> >>> > Roz
> >>> >
> >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT <
> >>> > met_help at ucar.edu> wrote:
> >>> >
> >>> >> Roz,
> >>> >>
> >>> >> Yes, I expect that using met-6.0 would work fine. Hope it
goes
> >>> smoothly.
> >>> >>
> >>> >> Thanks,
> >>> >> John
> >>> >>
> >>> >> On Mon, Jul 9, 2018 at 9: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=86091 >
> >>> >> >
> >>> >> > Hi John,
> >>> >> >
> >>> >> > I get the general idea and it looks pretty straight
forward. I'm
> >>> still
> >>> >> > running MET6.0, since we had some installation issues, but,
I
> >>> should be
> >>> >> > able to generate the mask with that pretty easily, correct?
> >>> >> >
> >>> >> > So, if this works, I'll need to rerun all my data from Mar
2018 -
> >>> >> present,
> >>> >> > using that method that we worked out earlier with the
*.stat
> files,
> >>> >> > correct? Actually, I don't need to do that...I can start
from the
> >>> ASCII
> >>> >> > files I've already generated, and then just rerun
POINT_STAT with
> >>> the
> >>> >> > mask. Ok, that will save some steps.
> >>> >> >
> >>> >> > Alright, I'll try making the mask and do a test run after
lunch,
> >>> and get
> >>> >> > back to you when it works.
> >>> >> >
> >>> >> > Thanks!
> >>> >> >
> >>> >> > Roz
> >>> >> >
> >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT <
> >>> >> > met_help at ucar.edu
> >>> >> > > wrote:
> >>> >> >
> >>> >> > > Hi Roz,
> >>> >> > >
> >>> >> > > I see you're wondering how to only use point observations
over
> >>> water
> >>> >> and
> >>> >> > > discard the ones over land. You're running ASCII2NC
followed by
> >>> >> > Point-Stat
> >>> >> > > and want to know where/how to define that masking.
> >>> >> > >
> >>> >> > > The ASCII2NC tool supports 3 command line options for
filtering
> >>> point
> >>> >> > > observations spatially: -mask_grid, -mask_poly, and
-mask_sid,
> for
> >>> >> grid,
> >>> >> > > polyline, and station ID masking, respectively. But
that's not
> >>> really
> >>> >> > what
> >>> >> > > you want. You want to do "data masking" where you read
in a
> >>> land/sea
> >>> >> > mask
> >>> >> > > and only use the points over water.
> >>> >> > >
> >>> >> > > I'd recommend running the Gen-Vx-Mask tool to create the
desired
> >>> >> masking
> >>> >> > > region, and then reference that in the Point-Stat config
file.
> >>> >> > >
> >>> >> > > To illustrate, I pulled a sample GFS file:
> >>> >> > > > wget
> >>> >> > >
https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> >>> >> > > 4_20180702_0000_012.grb2
> >>> >> > >
> >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
> >>> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour
fcst:
> >>> >> > >
> >>> >> > > Run plot_data_plane to see it (see attached image):
> >>> >> > > > met-7.0/bin/plot_data_plane
gfs_4_20180702_0000_012.grb2
> >>> >> > gfs_4_LAND.ps
> >>> >> > > 'name="LAND"; level="L0";'
> >>> >> > >
> >>> >> > > Run gen_vx_mask to create a mask for your verification
domain.
> If
> >>> >> you're
> >>> >> > > actually verifying on the GFS domain, the command looks a
little
> >>> >> > redundant:
> >>> >> > >
> >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >>> >> > > gfs_4_WATER_mask.nc \
> >>> >> > > -type data \
> >>> >> > > -mask_field 'name="LAND"; level="L0";' \
> >>> >> > > -thresh ==0 \
> >>> >> > > -name WATER
> >>> >> > >
> >>> >> > > I defined the threshold as "==0" because we want the
WATER
> >>> points, not
> >>> >> > the
> >>> >> > > LAND points. And I used the "-name WATER" command line
option
> to
> >>> name
> >>> >> > the
> >>> >> > > output NetCDF variable. This will show up in the VX_MASK
output
> >>> >> column
> >>> >> > of
> >>> >> > > Point-Stat.
> >>> >> > >
> >>> >> > > Lastly, setup your Point-Stat config file like this:
> >>> >> > >
> >>> >> > > mask = {
> >>> >> > > grid = [];
> >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> >>> >> > > sid = [];
> >>> >> > > }
> >>> >> > >
> >>> >> > > Hope that helps clarify.
> >>> >> > >
> >>> >> > > Thanks,
> >>> >> > > John
> >>> >> > >
> >>> >> > >
> >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken - NOAA
> >>> Affiliate via
> >>> >> > RT <
> >>> >> > > met_help at ucar.edu> wrote:
> >>> >> > >
> >>> >> > > >
> >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted upon.
> >>> >> > > > Transaction: Ticket created by
rosalyn.maccracken at noaa.gov
> >>> >> > > > Queue: met_help
> >>> >> > > > Subject: masking land features questions
> >>> >> > > > Owner: Nobody
> >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> >>> >> > > > Status: new
> >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> >>> >> ket/Display.html?id=86091
> >>> >> > >
> >>> >> > > >
> >>> >> > > >
> >>> >> > > > Hi,
> >>> >> > > >
> >>> >> > > > I'm using ASCAT data to verify the GFS. I only want to
verify
> >>> >> points
> >>> >> > > over
> >>> >> > > > the ocean, and not over any inland lakes. I noticed
that I
> was
> >>> >> getting
> >>> >> > > > matched points over land (mostly Africa). I'm dumping
out the
> >>> >> MGDRlite
> >>> >> > > > file to an ascii file, which I use ASCII2NC to create
the
> netCDF
> >>> >> file,
> >>> >> > > and
> >>> >> > > > then go on to use Point_stat to create statistics for
the
> >>> matched
> >>> >> > points.
> >>> >> > > >
> >>> >> > > > How do I mask out points over land before it gets to
the
> >>> Point_stat
> >>> >> > step?
> >>> >> > > > Is there something in the ASCII2NC processing that I
can add,
> >>> so I
> >>> >> > don't
> >>> >> > > > get these matched points?
> >>> >> > > >
> >>> >> > > > Thanks in advance!
> >>> >> > > >
> >>> >> > > > Roz
> >>> >> > > >
> >>> >> > > > --
> >>> >> > > > Rosalyn MacCracken
> >>> >> > > > Support Scientist
> >>> >> > > >
> >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Tue Jul 10 11:43:50 2018
Roz,
Sorry you're having a rough day. No worries though, this issue is
easy to
overcome. Here's a list of pre-defined NCEP grids:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
The intention in MET is to support them using the naming convention
G###
where ### is the 3 digit grid number. But if you look closely on that
website, you'll see that grid 193 is a relatively new one and is
listed in
red. That definition just doesn't exist in MET version 6.0.
The easy fix is this.... just replace "G193" on the command line with
the
path to a 1/4 degree GFS GRIB2 file. Here's a selection from the
usage
statement for regrid_data_plane:
Usage: regrid_data_plane
input_filename
to_grid
output_filename
"to_grid" defines the output grid as a named grid, the
path
to a gridded data file, or an explicit grid specification string
(required).
When you set "to_grid" equal to a gridded data file, MET reads the
grid
definition from the first record of that file and uses it.
That should do it.
Thanks,
John
On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
> Hi John,
>
> I'm really not having much luck today with this. Maybe I should
have
> stayed in bed (haha).
>
> So, the first thing I did was check the LD_LIBRARY_PATH, and it's
pointing
> to the MET7 directories. Ok, that could be most of the problem.
MET7 seems
> to be having some issue, and the guy here at OPC that helps me with
that
> stuff (Chris Juckins) is out on leave until tomorrow. Anyway, MET7
is not
> running any of my verification programs, and giving out some errors,
so,
> I'll have to get with him tomorrow to fix that.
>
> So, in the mean time, I don't think that any kind of land mask
creation
> that I'm doing today will work because it's not pointing at the
right
> directories.
>
> But, when I do get this to work, I tried this and got this error:
> /opt/MET6/met6.0/bin/regrid_data_plane gwes01.glo_30m.t00z.grib2
G193
> ocean_data.nc -field 'name="WIND"; level="L0";'
> DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321 lat_ll:
-80.000
> lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> ERROR :
> ERROR : grd_file_type() -> file does not exist "G193"
> ERROR :
>
> I'm wondering if that's all related to MET7.
>
> So, I think I need to fix the MET7 issue before moving on with this,
don't
> you?
>
> Roz
>
> On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> > wrote:
>
> > Roz,
> >
> > OK, one other possible option to consider. I figured that there's
plenty
> > of "ocean" products out there. So I found a NOAA WAVEWATCH one:
> >
> > (1) Download sample wavewatch file:
> > wget
> > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > gwes.20180708/gwes01.glo_30m.t00z.grib2
> >
> > (2) Run regrid_data_plane to put some surface wind speed data on
the 1/4
> > GFS grid:
> > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193 ocean_data.nc
-field
> > 'name="WIND"; level="L0";'
> >
> > (3) Run gen_vx_mask to select points that contain valid data:
> > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc -type
data
> > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999 -name
OCEAN
> >
> > (4) Run plot_data_plane to see the result:
> > plot_data_plane ocean_mask.nc ocean_mask.ps 'name="OCEAN";
> > level="(*,*)";'
> >
> > As you can see, the result gets rid of the lakes problem. But
wavewatch
> is
> > only run to +/- 80 degrees, so we're not including points near the
poles.
> >
> > Figured this would be a lot easier than running WPS yourself.
> >
> > Thanks,
> > John
> >
> >
> > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway
<johnhg at ucar.edu>
> wrote:
> >
> > > Roz,
> > >
> > > I talked to some folks and have one suggestion that *might*
work. The
> > WRF
> > > Pre-processing system is named WPS. The geogrid program within
WPS is
> > used
> > > to initialize your domain and handles land use information. By
> default,
> > > lakes and oceans are treated the same way. However, apparently
there
> is
> > an
> > > option to distinguish between them. Take a look here:
> > >
> > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> > users_guide_chap3.htm#_Description_of_the_1
> > >
> > > And search for "Alternative Initialization of Lake SSTs".
> > >
> > > So you'd...
> > > (1) download the MODIS SST data
> > > (2) configure geogrid for the 0.25 degree GFS grid
> > > (3) configure geogrid to distinguish between lakes and oceans
> > > (4) run geogrid
> > > (5) run the output through the MET gen_vx_mask tool to use ocean
values
> > > and skip the lake values
> > >
> > > Thanks,
> > > John
> > >
> > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway
<johnhg at ucar.edu>
> > wrote:
> > >
> > >> Roz,
> > >>
> > >> Whenever you see that error about loading shared libraries, it
means
> > that
> > >> there's a problem in how your LD_LIBRARY_PATH environment
variable is
> > set.
> > >> That environment variable tells the linker where to look for
shared
> > >> libraries at runtime... one of those shared libraries is GSL
(GNU
> > >> Scientific Library). You'd "fix" this issue by modifying how
> > >> LD_LIBRARY_PATH is set:
> > >> echo $LD_LIBRARY_PATH
> > >>
> > >> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc for
bash to
> > >> see how its set.
> > >>
> > >> As for the LAND/SEA mask, I was wondering if those lakes would
be a
> > >> problem. Using the model's LAND/SEA mask is the easiest, but
doesn't
> > >> provide an easy way of selecting out oceans. My next thought
was to
> use
> > >> GIS Shapefiles to define only the ocean area. That will be
available
> in
> > >> the next version of MET, version 7.1. I tried using a beta
release
> for
> > >> met-7.1, but ran into problems when applying large polylines to
global
> > >> grids.
> > >>
> > >> I'll keep thinking about that one.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA
Affiliate
> via
> > >> RT <met_help at ucar.edu> wrote:
> > >>
> > >>>
> > >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
>
> > >>>
> > >>> Hey John,
> > >>>
> > >>> I have 2 problems. First, I'm able to use plot_data_plane,
but,
> when I
> > >>> use
> > >>> the command for gen_vx_mask, I get this:
> > >>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
> > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
-mask_field
> > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
> > libraries:
> > >>> libgsl.so.0: cannot open shared object file: No such file or
> directory
> > >>>
> > >>> Now, they are both in the same directory, and I know that I've
used
> > >>> gen_vx_mask before, so, I have no idea why I would be getting
that
> > error
> > >>> message. Any ideas?
> > >>>
> > >>> Then, I was able to generate a *.ps file, which looks exactly
like
> > yours,
> > >>> but, there is still the same problem. If you look closely are
your
> > map,
> > >>> you'll see these little white dots over land. Those are
lakes, and
> > >>> that's
> > >>> what is giving me a fit, because I have ASCAT observations
over those
> > >>> white
> > >>> dots. You know, I'm using 0.25 deg GFS data with 12 km ASCAT
> > data...so,
> > >>> very sensitive. Anyway, do you have any idea how to get rid
of those
> > >>> points? Perhaps a different file with the same domain?
> > >>>
> > >>> Roz
> > >>>
> > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > >>> rosalyn.maccracken at noaa.gov> wrote:
> > >>>
> > >>> > Ok, I'll let you know if I can get the mask to work. This
seems
> easy
> > >>> > enough, and pretty straight forward.
> > >>> >
> > >>> > Thanks for the help!
> > >>> >
> > >>> > Roz
> > >>> >
> > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT <
> > >>> > met_help at ucar.edu> wrote:
> > >>> >
> > >>> >> Roz,
> > >>> >>
> > >>> >> Yes, I expect that using met-6.0 would work fine. Hope it
goes
> > >>> smoothly.
> > >>> >>
> > >>> >> Thanks,
> > >>> >> John
> > >>> >>
> > >>> >> On Mon, Jul 9, 2018 at 9: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=86091 >
> > >>> >> >
> > >>> >> > Hi John,
> > >>> >> >
> > >>> >> > I get the general idea and it looks pretty straight
forward.
> I'm
> > >>> still
> > >>> >> > running MET6.0, since we had some installation issues,
but, I
> > >>> should be
> > >>> >> > able to generate the mask with that pretty easily,
correct?
> > >>> >> >
> > >>> >> > So, if this works, I'll need to rerun all my data from
Mar 2018
> -
> > >>> >> present,
> > >>> >> > using that method that we worked out earlier with the
*.stat
> > files,
> > >>> >> > correct? Actually, I don't need to do that...I can start
from
> the
> > >>> ASCII
> > >>> >> > files I've already generated, and then just rerun
POINT_STAT
> with
> > >>> the
> > >>> >> > mask. Ok, that will save some steps.
> > >>> >> >
> > >>> >> > Alright, I'll try making the mask and do a test run after
lunch,
> > >>> and get
> > >>> >> > back to you when it works.
> > >>> >> >
> > >>> >> > Thanks!
> > >>> >> >
> > >>> >> > Roz
> > >>> >> >
> > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via RT
<
> > >>> >> > met_help at ucar.edu
> > >>> >> > > wrote:
> > >>> >> >
> > >>> >> > > Hi Roz,
> > >>> >> > >
> > >>> >> > > I see you're wondering how to only use point
observations over
> > >>> water
> > >>> >> and
> > >>> >> > > discard the ones over land. You're running ASCII2NC
followed
> by
> > >>> >> > Point-Stat
> > >>> >> > > and want to know where/how to define that masking.
> > >>> >> > >
> > >>> >> > > The ASCII2NC tool supports 3 command line options for
> filtering
> > >>> point
> > >>> >> > > observations spatially: -mask_grid, -mask_poly, and
-mask_sid,
> > for
> > >>> >> grid,
> > >>> >> > > polyline, and station ID masking, respectively. But
that's
> not
> > >>> really
> > >>> >> > what
> > >>> >> > > you want. You want to do "data masking" where you read
in a
> > >>> land/sea
> > >>> >> > mask
> > >>> >> > > and only use the points over water.
> > >>> >> > >
> > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to create
the
> desired
> > >>> >> masking
> > >>> >> > > region, and then reference that in the Point-Stat
config file.
> > >>> >> > >
> > >>> >> > > To illustrate, I pulled a sample GFS file:
> > >>> >> > > > wget
> > >>> >> > >
https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> > >>> >> > > 4_20180702_0000_012.grb2
> > >>> >> > >
> > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i LAND
> > >>> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour
fcst:
> > >>> >> > >
> > >>> >> > > Run plot_data_plane to see it (see attached image):
> > >>> >> > > > met-7.0/bin/plot_data_plane
gfs_4_20180702_0000_012.grb2
> > >>> >> > gfs_4_LAND.ps
> > >>> >> > > 'name="LAND"; level="L0";'
> > >>> >> > >
> > >>> >> > > Run gen_vx_mask to create a mask for your verification
domain.
> > If
> > >>> >> you're
> > >>> >> > > actually verifying on the GFS domain, the command looks
a
> little
> > >>> >> > redundant:
> > >>> >> > >
> > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >>> >> > > gfs_4_WATER_mask.nc \
> > >>> >> > > -type data \
> > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
> > >>> >> > > -thresh ==0 \
> > >>> >> > > -name WATER
> > >>> >> > >
> > >>> >> > > I defined the threshold as "==0" because we want the
WATER
> > >>> points, not
> > >>> >> > the
> > >>> >> > > LAND points. And I used the "-name WATER" command line
option
> > to
> > >>> name
> > >>> >> > the
> > >>> >> > > output NetCDF variable. This will show up in the
VX_MASK
> output
> > >>> >> column
> > >>> >> > of
> > >>> >> > > Point-Stat.
> > >>> >> > >
> > >>> >> > > Lastly, setup your Point-Stat config file like this:
> > >>> >> > >
> > >>> >> > > mask = {
> > >>> >> > > grid = [];
> > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> > >>> >> > > sid = [];
> > >>> >> > > }
> > >>> >> > >
> > >>> >> > > Hope that helps clarify.
> > >>> >> > >
> > >>> >> > > Thanks,
> > >>> >> > > John
> > >>> >> > >
> > >>> >> > >
> > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken -
NOAA
> > >>> Affiliate via
> > >>> >> > RT <
> > >>> >> > > met_help at ucar.edu> wrote:
> > >>> >> > >
> > >>> >> > > >
> > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted
upon.
> > >>> >> > > > Transaction: Ticket created by
rosalyn.maccracken at noaa.gov
> > >>> >> > > > Queue: met_help
> > >>> >> > > > Subject: masking land features questions
> > >>> >> > > > Owner: Nobody
> > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> > >>> >> > > > Status: new
> > >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> > >>> >> ket/Display.html?id=86091
> > >>> >> > >
> > >>> >> > > >
> > >>> >> > > >
> > >>> >> > > > Hi,
> > >>> >> > > >
> > >>> >> > > > I'm using ASCAT data to verify the GFS. I only want
to
> verify
> > >>> >> points
> > >>> >> > > over
> > >>> >> > > > the ocean, and not over any inland lakes. I noticed
that I
> > was
> > >>> >> getting
> > >>> >> > > > matched points over land (mostly Africa). I'm
dumping out
> the
> > >>> >> MGDRlite
> > >>> >> > > > file to an ascii file, which I use ASCII2NC to create
the
> > netCDF
> > >>> >> file,
> > >>> >> > > and
> > >>> >> > > > then go on to use Point_stat to create statistics for
the
> > >>> matched
> > >>> >> > points.
> > >>> >> > > >
> > >>> >> > > > How do I mask out points over land before it gets to
the
> > >>> Point_stat
> > >>> >> > step?
> > >>> >> > > > Is there something in the ASCII2NC processing that I
can
> add,
> > >>> so I
> > >>> >> > don't
> > >>> >> > > > get these matched points?
> > >>> >> > > >
> > >>> >> > > > Thanks in advance!
> > >>> >> > > >
> > >>> >> > > > Roz
> > >>> >> > > >
> > >>> >> > > > --
> > >>> >> > > > Rosalyn MacCracken
> > >>> >> > > > Support Scientist
> > >>> >> > > >
> > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Tue Jul 10 12:35:44 2018
Oh, yeah, nothing seems to be going smoothly today...anyway, I think I
need
to wait until Chris and Fran come in tomorrow to set our directories
correctly to point at MET, and get it running again before I do
anything
else.
I'll try this again tomorrow and let you know how I do.
Thanks for your help!
Roz
On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> Sorry you're having a rough day. No worries though, this issue is
easy to
> overcome. Here's a list of pre-defined NCEP grids:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
>
> The intention in MET is to support them using the naming convention
G###
> where ### is the 3 digit grid number. But if you look closely on
that
> website, you'll see that grid 193 is a relatively new one and is
listed in
> red. That definition just doesn't exist in MET version 6.0.
>
> The easy fix is this.... just replace "G193" on the command line
with the
> path to a 1/4 degree GFS GRIB2 file. Here's a selection from the
usage
> statement for regrid_data_plane:
>
> Usage: regrid_data_plane
> input_filename
> to_grid
> output_filename
> "to_grid" defines the output grid as a named grid,
the path
> to a gridded data file, or an explicit grid specification string
> (required).
>
> When you set "to_grid" equal to a gridded data file, MET reads the
grid
> definition from the first record of that file and uses it.
>
> That should do it.
>
> Thanks,
> John
>
> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >
> > Hi John,
> >
> > I'm really not having much luck today with this. Maybe I should
have
> > stayed in bed (haha).
> >
> > So, the first thing I did was check the LD_LIBRARY_PATH, and it's
> pointing
> > to the MET7 directories. Ok, that could be most of the problem.
MET7
> seems
> > to be having some issue, and the guy here at OPC that helps me
with that
> > stuff (Chris Juckins) is out on leave until tomorrow. Anyway,
MET7 is
> not
> > running any of my verification programs, and giving out some
errors, so,
> > I'll have to get with him tomorrow to fix that.
> >
> > So, in the mean time, I don't think that any kind of land mask
creation
> > that I'm doing today will work because it's not pointing at the
right
> > directories.
> >
> > But, when I do get this to work, I tried this and got this error:
> > /opt/MET6/met6.0/bin/regrid_data_plane gwes01.glo_30m.t00z.grib2
G193
> > ocean_data.nc -field 'name="WIND"; level="L0";'
> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321 lat_ll:
-80.000
> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> > ERROR :
> > ERROR : grd_file_type() -> file does not exist "G193"
> > ERROR :
> >
> > I'm wondering if that's all related to MET7.
> >
> > So, I think I need to fix the MET7 issue before moving on with
this,
> don't
> > you?
> >
> > Roz
> >
> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > > Roz,
> > >
> > > OK, one other possible option to consider. I figured that
there's
> plenty
> > > of "ocean" products out there. So I found a NOAA WAVEWATCH one:
> > >
> > > (1) Download sample wavewatch file:
> > > wget
> > > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> > >
> > > (2) Run regrid_data_plane to put some surface wind speed data on
the
> 1/4
> > > GFS grid:
> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
ocean_data.nc
> -field
> > > 'name="WIND"; level="L0";'
> > >
> > > (3) Run gen_vx_mask to select points that contain valid data:
> > > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc -type
data
> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999 -name
OCEAN
> > >
> > > (4) Run plot_data_plane to see the result:
> > > plot_data_plane ocean_mask.nc ocean_mask.ps 'name="OCEAN";
> > > level="(*,*)";'
> > >
> > > As you can see, the result gets rid of the lakes problem. But
> wavewatch
> > is
> > > only run to +/- 80 degrees, so we're not including points near
the
> poles.
> > >
> > > Figured this would be a lot easier than running WPS yourself.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway
<johnhg at ucar.edu>
> > wrote:
> > >
> > > > Roz,
> > > >
> > > > I talked to some folks and have one suggestion that *might*
work.
> The
> > > WRF
> > > > Pre-processing system is named WPS. The geogrid program
within WPS
> is
> > > used
> > > > to initialize your domain and handles land use information.
By
> > default,
> > > > lakes and oceans are treated the same way. However,
apparently there
> > is
> > > an
> > > > option to distinguish between them. Take a look here:
> > > >
> > > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> > > users_guide_chap3.htm#_Description_of_the_1
> > > >
> > > > And search for "Alternative Initialization of Lake SSTs".
> > > >
> > > > So you'd...
> > > > (1) download the MODIS SST data
> > > > (2) configure geogrid for the 0.25 degree GFS grid
> > > > (3) configure geogrid to distinguish between lakes and oceans
> > > > (4) run geogrid
> > > > (5) run the output through the MET gen_vx_mask tool to use
ocean
> values
> > > > and skip the lake values
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway
<johnhg at ucar.edu>
> > > wrote:
> > > >
> > > >> Roz,
> > > >>
> > > >> Whenever you see that error about loading shared libraries,
it means
> > > that
> > > >> there's a problem in how your LD_LIBRARY_PATH environment
variable
> is
> > > set.
> > > >> That environment variable tells the linker where to look for
shared
> > > >> libraries at runtime... one of those shared libraries is GSL
(GNU
> > > >> Scientific Library). You'd "fix" this issue by modifying how
> > > >> LD_LIBRARY_PATH is set:
> > > >> echo $LD_LIBRARY_PATH
> > > >>
> > > >> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc
for bash
> to
> > > >> see how its set.
> > > >>
> > > >> As for the LAND/SEA mask, I was wondering if those lakes
would be a
> > > >> problem. Using the model's LAND/SEA mask is the easiest, but
> doesn't
> > > >> provide an easy way of selecting out oceans. My next thought
was to
> > use
> > > >> GIS Shapefiles to define only the ocean area. That will be
> available
> > in
> > > >> the next version of MET, version 7.1. I tried using a beta
release
> > for
> > > >> met-7.1, but ran into problems when applying large polylines
to
> global
> > > >> grids.
> > > >>
> > > >> I'll keep thinking about that one.
> > > >>
> > > >> Thanks,
> > > >> John
> > > >>
> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA
Affiliate
> > via
> > > >> RT <met_help at ucar.edu> wrote:
> > > >>
> > > >>>
> > > >>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> > > >>>
> > > >>> Hey John,
> > > >>>
> > > >>> I have 2 problems. First, I'm able to use plot_data_plane,
but,
> > when I
> > > >>> use
> > > >>> the command for gen_vx_mask, I get this:
> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
-mask_field
> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading shared
> > > libraries:
> > > >>> libgsl.so.0: cannot open shared object file: No such file or
> > directory
> > > >>>
> > > >>> Now, they are both in the same directory, and I know that
I've used
> > > >>> gen_vx_mask before, so, I have no idea why I would be
getting that
> > > error
> > > >>> message. Any ideas?
> > > >>>
> > > >>> Then, I was able to generate a *.ps file, which looks
exactly like
> > > yours,
> > > >>> but, there is still the same problem. If you look closely
are your
> > > map,
> > > >>> you'll see these little white dots over land. Those are
lakes, and
> > > >>> that's
> > > >>> what is giving me a fit, because I have ASCAT observations
over
> those
> > > >>> white
> > > >>> dots. You know, I'm using 0.25 deg GFS data with 12 km
ASCAT
> > > data...so,
> > > >>> very sensitive. Anyway, do you have any idea how to get rid
of
> those
> > > >>> points? Perhaps a different file with the same domain?
> > > >>>
> > > >>> Roz
> > > >>>
> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA
> Affiliate <
> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> > > >>>
> > > >>> > Ok, I'll let you know if I can get the mask to work. This
seems
> > easy
> > > >>> > enough, and pretty straight forward.
> > > >>> >
> > > >>> > Thanks for the help!
> > > >>> >
> > > >>> > Roz
> > > >>> >
> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT
<
> > > >>> > met_help at ucar.edu> wrote:
> > > >>> >
> > > >>> >> Roz,
> > > >>> >>
> > > >>> >> Yes, I expect that using met-6.0 would work fine. Hope
it goes
> > > >>> smoothly.
> > > >>> >>
> > > >>> >> Thanks,
> > > >>> >> John
> > > >>> >>
> > > >>> >> On Mon, Jul 9, 2018 at 9: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=86091
> >
> > > >>> >> >
> > > >>> >> > Hi John,
> > > >>> >> >
> > > >>> >> > I get the general idea and it looks pretty straight
forward.
> > I'm
> > > >>> still
> > > >>> >> > running MET6.0, since we had some installation issues,
but, I
> > > >>> should be
> > > >>> >> > able to generate the mask with that pretty easily,
correct?
> > > >>> >> >
> > > >>> >> > So, if this works, I'll need to rerun all my data from
Mar
> 2018
> > -
> > > >>> >> present,
> > > >>> >> > using that method that we worked out earlier with the
*.stat
> > > files,
> > > >>> >> > correct? Actually, I don't need to do that...I can
start from
> > the
> > > >>> ASCII
> > > >>> >> > files I've already generated, and then just rerun
POINT_STAT
> > with
> > > >>> the
> > > >>> >> > mask. Ok, that will save some steps.
> > > >>> >> >
> > > >>> >> > Alright, I'll try making the mask and do a test run
after
> lunch,
> > > >>> and get
> > > >>> >> > back to you when it works.
> > > >>> >> >
> > > >>> >> > Thanks!
> > > >>> >> >
> > > >>> >> > Roz
> > > >>> >> >
> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via
RT <
> > > >>> >> > met_help at ucar.edu
> > > >>> >> > > wrote:
> > > >>> >> >
> > > >>> >> > > Hi Roz,
> > > >>> >> > >
> > > >>> >> > > I see you're wondering how to only use point
observations
> over
> > > >>> water
> > > >>> >> and
> > > >>> >> > > discard the ones over land. You're running ASCII2NC
> followed
> > by
> > > >>> >> > Point-Stat
> > > >>> >> > > and want to know where/how to define that masking.
> > > >>> >> > >
> > > >>> >> > > The ASCII2NC tool supports 3 command line options for
> > filtering
> > > >>> point
> > > >>> >> > > observations spatially: -mask_grid, -mask_poly, and
> -mask_sid,
> > > for
> > > >>> >> grid,
> > > >>> >> > > polyline, and station ID masking, respectively. But
that's
> > not
> > > >>> really
> > > >>> >> > what
> > > >>> >> > > you want. You want to do "data masking" where you
read in a
> > > >>> land/sea
> > > >>> >> > mask
> > > >>> >> > > and only use the points over water.
> > > >>> >> > >
> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to create
the
> > desired
> > > >>> >> masking
> > > >>> >> > > region, and then reference that in the Point-Stat
config
> file.
> > > >>> >> > >
> > > >>> >> > > To illustrate, I pulled a sample GFS file:
> > > >>> >> > > > wget
> > > >>> >> > >
https://nomads.ncdc.noaa.gov/data/gfs4/201807/20180702/gfs_
> > > >>> >> > > 4_20180702_0000_012.grb2
> > > >>> >> > >
> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i
LAND
> > > >>> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour
fcst:
> > > >>> >> > >
> > > >>> >> > > Run plot_data_plane to see it (see attached image):
> > > >>> >> > > > met-7.0/bin/plot_data_plane
> gfs_4_20180702_0000_012.grb2
> > > >>> >> > gfs_4_LAND.ps
> > > >>> >> > > 'name="LAND"; level="L0";'
> > > >>> >> > >
> > > >>> >> > > Run gen_vx_mask to create a mask for your
verification
> domain.
> > > If
> > > >>> >> you're
> > > >>> >> > > actually verifying on the GFS domain, the command
looks a
> > little
> > > >>> >> > redundant:
> > > >>> >> > >
> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > > >>> >> > > gfs_4_WATER_mask.nc \
> > > >>> >> > > -type data \
> > > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
> > > >>> >> > > -thresh ==0 \
> > > >>> >> > > -name WATER
> > > >>> >> > >
> > > >>> >> > > I defined the threshold as "==0" because we want the
WATER
> > > >>> points, not
> > > >>> >> > the
> > > >>> >> > > LAND points. And I used the "-name WATER" command
line
> option
> > > to
> > > >>> name
> > > >>> >> > the
> > > >>> >> > > output NetCDF variable. This will show up in the
VX_MASK
> > output
> > > >>> >> column
> > > >>> >> > of
> > > >>> >> > > Point-Stat.
> > > >>> >> > >
> > > >>> >> > > Lastly, setup your Point-Stat config file like this:
> > > >>> >> > >
> > > >>> >> > > mask = {
> > > >>> >> > > grid = [];
> > > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> > > >>> >> > > sid = [];
> > > >>> >> > > }
> > > >>> >> > >
> > > >>> >> > > Hope that helps clarify.
> > > >>> >> > >
> > > >>> >> > > Thanks,
> > > >>> >> > > John
> > > >>> >> > >
> > > >>> >> > >
> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken -
NOAA
> > > >>> Affiliate via
> > > >>> >> > RT <
> > > >>> >> > > met_help at ucar.edu> wrote:
> > > >>> >> > >
> > > >>> >> > > >
> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted
upon.
> > > >>> >> > > > Transaction: Ticket created by
> rosalyn.maccracken at noaa.gov
> > > >>> >> > > > Queue: met_help
> > > >>> >> > > > Subject: masking land features questions
> > > >>> >> > > > Owner: Nobody
> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> > > >>> >> > > > Status: new
> > > >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> > > >>> >> ket/Display.html?id=86091
> > > >>> >> > >
> > > >>> >> > > >
> > > >>> >> > > >
> > > >>> >> > > > Hi,
> > > >>> >> > > >
> > > >>> >> > > > I'm using ASCAT data to verify the GFS. I only
want to
> > verify
> > > >>> >> points
> > > >>> >> > > over
> > > >>> >> > > > the ocean, and not over any inland lakes. I
noticed that
> I
> > > was
> > > >>> >> getting
> > > >>> >> > > > matched points over land (mostly Africa). I'm
dumping out
> > the
> > > >>> >> MGDRlite
> > > >>> >> > > > file to an ascii file, which I use ASCII2NC to
create the
> > > netCDF
> > > >>> >> file,
> > > >>> >> > > and
> > > >>> >> > > > then go on to use Point_stat to create statistics
for the
> > > >>> matched
> > > >>> >> > points.
> > > >>> >> > > >
> > > >>> >> > > > How do I mask out points over land before it gets
to the
> > > >>> Point_stat
> > > >>> >> > step?
> > > >>> >> > > > Is there something in the ASCII2NC processing that
I can
> > add,
> > > >>> so I
> > > >>> >> > don't
> > > >>> >> > > > get these matched points?
> > > >>> >> > > >
> > > >>> >> > > > Thanks in advance!
> > > >>> >> > > >
> > > >>> >> > > > Roz
> > > >>> >> > > >
> > > >>> >> > > > --
> > > >>> >> > > > Rosalyn MacCracken
> > > >>> >> > > > Support Scientist
> > > >>> >> > > >
> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Wed Jul 11 13:08:16 2018
Hi John,
Well, good news. We got our MET7 to work, and I was able to create my
ocean mask. It was an issue with conflicts in our libraries, and the
LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
Now, I have this ocean mask, and now I can go back and rerun my data.
So,
as usual, I had some questions.
I have a series of scripts where you helped me set up STATanalysis to
reprocess the data using the *.stat files and the -job aggregate_stat
command . Will I be able to use this method again, or, because it's
applying a mask, will I need to get the raw data (GFS and ASCAT data)?
And, I guess if I have to use the raw data, I will have to start with
ASCII2NC, etc, as if I'm processing from scratch, correct?
I just need a sense of how big of a job this is....
Thanks for your help!
Roz
On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA Affiliate <
rosalyn.maccracken at noaa.gov> wrote:
> Oh, yeah, nothing seems to be going smoothly today...anyway, I think
I
> need to wait until Chris and Fran come in tomorrow to set our
directories
> correctly to point at MET, and get it running again before I do
anything
> else.
>
> I'll try this again tomorrow and let you know how I do.
>
> Thanks for your help!
>
> Roz
>
> On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Roz,
>>
>> Sorry you're having a rough day. No worries though, this issue is
easy to
>> overcome. Here's a list of pre-defined NCEP grids:
>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
>>
>> The intention in MET is to support them using the naming convention
G###
>> where ### is the 3 digit grid number. But if you look closely on
that
>> website, you'll see that grid 193 is a relatively new one and is
listed in
>> red. That definition just doesn't exist in MET version 6.0.
>>
>> The easy fix is this.... just replace "G193" on the command line
with the
>> path to a 1/4 degree GFS GRIB2 file. Here's a selection from the
usage
>> statement for regrid_data_plane:
>>
>> Usage: regrid_data_plane
>> input_filename
>> to_grid
>> output_filename
>> "to_grid" defines the output grid as a named grid,
the
>> path
>> to a gridded data file, or an explicit grid specification string
>> (required).
>>
>> When you set "to_grid" equal to a gridded data file, MET reads the
grid
>> definition from the first record of that file and uses it.
>>
>> That should do it.
>>
>> Thanks,
>> John
>>
>> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA Affiliate
via
>> RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>> >
>> > Hi John,
>> >
>> > I'm really not having much luck today with this. Maybe I should
have
>> > stayed in bed (haha).
>> >
>> > So, the first thing I did was check the LD_LIBRARY_PATH, and it's
>> pointing
>> > to the MET7 directories. Ok, that could be most of the problem.
MET7
>> seems
>> > to be having some issue, and the guy here at OPC that helps me
with that
>> > stuff (Chris Juckins) is out on leave until tomorrow. Anyway,
MET7 is
>> not
>> > running any of my verification programs, and giving out some
errors, so,
>> > I'll have to get with him tomorrow to fix that.
>> >
>> > So, in the mean time, I don't think that any kind of land mask
creation
>> > that I'm doing today will work because it's not pointing at the
right
>> > directories.
>> >
>> > But, when I do get this to work, I tried this and got this error:
>> > /opt/MET6/met6.0/bin/regrid_data_plane gwes01.glo_30m.t00z.grib2
G193
>> > ocean_data.nc -field 'name="WIND"; level="L0";'
>> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
>> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321 lat_ll:
-80.000
>> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
>> > ERROR :
>> > ERROR : grd_file_type() -> file does not exist "G193"
>> > ERROR :
>> >
>> > I'm wondering if that's all related to MET7.
>> >
>> > So, I think I need to fix the MET7 issue before moving on with
this,
>> don't
>> > you?
>> >
>> > Roz
>> >
>> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT <
>> > met_help at ucar.edu
>> > > wrote:
>> >
>> > > Roz,
>> > >
>> > > OK, one other possible option to consider. I figured that
there's
>> plenty
>> > > of "ocean" products out there. So I found a NOAA WAVEWATCH
one:
>> > >
>> > > (1) Download sample wavewatch file:
>> > > wget
>> > > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
>> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
>> > >
>> > > (2) Run regrid_data_plane to put some surface wind speed data
on the
>> 1/4
>> > > GFS grid:
>> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
ocean_data.nc
>> -field
>> > > 'name="WIND"; level="L0";'
>> > >
>> > > (3) Run gen_vx_mask to select points that contain valid data:
>> > > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc -type
data
>> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999 -name
OCEAN
>> > >
>> > > (4) Run plot_data_plane to see the result:
>> > > plot_data_plane ocean_mask.nc ocean_mask.ps 'name="OCEAN";
>> > > level="(*,*)";'
>> > >
>> > > As you can see, the result gets rid of the lakes problem. But
>> wavewatch
>> > is
>> > > only run to +/- 80 degrees, so we're not including points near
the
>> poles.
>> > >
>> > > Figured this would be a lot easier than running WPS yourself.
>> > >
>> > > Thanks,
>> > > John
>> > >
>> > >
>> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway
<johnhg at ucar.edu>
>> > wrote:
>> > >
>> > > > Roz,
>> > > >
>> > > > I talked to some folks and have one suggestion that *might*
work.
>> The
>> > > WRF
>> > > > Pre-processing system is named WPS. The geogrid program
within WPS
>> is
>> > > used
>> > > > to initialize your domain and handles land use information.
By
>> > default,
>> > > > lakes and oceans are treated the same way. However,
apparently
>> there
>> > is
>> > > an
>> > > > option to distinguish between them. Take a look here:
>> > > >
>> > > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
>> > > users_guide_chap3.htm#_Description_of_the_1
>> > > >
>> > > > And search for "Alternative Initialization of Lake SSTs".
>> > > >
>> > > > So you'd...
>> > > > (1) download the MODIS SST data
>> > > > (2) configure geogrid for the 0.25 degree GFS grid
>> > > > (3) configure geogrid to distinguish between lakes and oceans
>> > > > (4) run geogrid
>> > > > (5) run the output through the MET gen_vx_mask tool to use
ocean
>> values
>> > > > and skip the lake values
>> > > >
>> > > > Thanks,
>> > > > John
>> > > >
>> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway
<johnhg at ucar.edu>
>> > > wrote:
>> > > >
>> > > >> Roz,
>> > > >>
>> > > >> Whenever you see that error about loading shared libraries,
it
>> means
>> > > that
>> > > >> there's a problem in how your LD_LIBRARY_PATH environment
variable
>> is
>> > > set.
>> > > >> That environment variable tells the linker where to look for
shared
>> > > >> libraries at runtime... one of those shared libraries is GSL
(GNU
>> > > >> Scientific Library). You'd "fix" this issue by modifying
how
>> > > >> LD_LIBRARY_PATH is set:
>> > > >> echo $LD_LIBRARY_PATH
>> > > >>
>> > > >> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc
for
>> bash to
>> > > >> see how its set.
>> > > >>
>> > > >> As for the LAND/SEA mask, I was wondering if those lakes
would be a
>> > > >> problem. Using the model's LAND/SEA mask is the easiest,
but
>> doesn't
>> > > >> provide an easy way of selecting out oceans. My next
thought was
>> to
>> > use
>> > > >> GIS Shapefiles to define only the ocean area. That will be
>> available
>> > in
>> > > >> the next version of MET, version 7.1. I tried using a beta
release
>> > for
>> > > >> met-7.1, but ran into problems when applying large polylines
to
>> global
>> > > >> grids.
>> > > >>
>> > > >> I'll keep thinking about that one.
>> > > >>
>> > > >> Thanks,
>> > > >> John
>> > > >>
>> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA
Affiliate
>> > via
>> > > >> RT <met_help at ucar.edu> wrote:
>> > > >>
>> > > >>>
>> > > >>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>> > > >>>
>> > > >>> Hey John,
>> > > >>>
>> > > >>> I have 2 problems. First, I'm able to use plot_data_plane,
but,
>> > when I
>> > > >>> use
>> > > >>> the command for gen_vx_mask, I get this:
>> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
>> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
>> -mask_field
>> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
>> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading
shared
>> > > libraries:
>> > > >>> libgsl.so.0: cannot open shared object file: No such file
or
>> > directory
>> > > >>>
>> > > >>> Now, they are both in the same directory, and I know that
I've
>> used
>> > > >>> gen_vx_mask before, so, I have no idea why I would be
getting that
>> > > error
>> > > >>> message. Any ideas?
>> > > >>>
>> > > >>> Then, I was able to generate a *.ps file, which looks
exactly like
>> > > yours,
>> > > >>> but, there is still the same problem. If you look closely
are
>> your
>> > > map,
>> > > >>> you'll see these little white dots over land. Those are
lakes,
>> and
>> > > >>> that's
>> > > >>> what is giving me a fit, because I have ASCAT observations
over
>> those
>> > > >>> white
>> > > >>> dots. You know, I'm using 0.25 deg GFS data with 12 km
ASCAT
>> > > data...so,
>> > > >>> very sensitive. Anyway, do you have any idea how to get
rid of
>> those
>> > > >>> points? Perhaps a different file with the same domain?
>> > > >>>
>> > > >>> Roz
>> > > >>>
>> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA
>> Affiliate <
>> > > >>> rosalyn.maccracken at noaa.gov> wrote:
>> > > >>>
>> > > >>> > Ok, I'll let you know if I can get the mask to work.
This seems
>> > easy
>> > > >>> > enough, and pretty straight forward.
>> > > >>> >
>> > > >>> > Thanks for the help!
>> > > >>> >
>> > > >>> > Roz
>> > > >>> >
>> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via RT
<
>> > > >>> > met_help at ucar.edu> wrote:
>> > > >>> >
>> > > >>> >> Roz,
>> > > >>> >>
>> > > >>> >> Yes, I expect that using met-6.0 would work fine. Hope
it goes
>> > > >>> smoothly.
>> > > >>> >>
>> > > >>> >> Thanks,
>> > > >>> >> John
>> > > >>> >>
>> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn MacCracken - NOAA
>> Affiliate
>> > > >>> via RT
>> > > >>> >> <
>> > > >>> >> met_help at ucar.edu> wrote:
>> > > >>> >>
>> > > >>> >> >
>> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
>> ket/Display.html?id=86091 >
>> > > >>> >> >
>> > > >>> >> > Hi John,
>> > > >>> >> >
>> > > >>> >> > I get the general idea and it looks pretty straight
forward.
>> > I'm
>> > > >>> still
>> > > >>> >> > running MET6.0, since we had some installation issues,
but, I
>> > > >>> should be
>> > > >>> >> > able to generate the mask with that pretty easily,
correct?
>> > > >>> >> >
>> > > >>> >> > So, if this works, I'll need to rerun all my data from
Mar
>> 2018
>> > -
>> > > >>> >> present,
>> > > >>> >> > using that method that we worked out earlier with the
*.stat
>> > > files,
>> > > >>> >> > correct? Actually, I don't need to do that...I can
start
>> from
>> > the
>> > > >>> ASCII
>> > > >>> >> > files I've already generated, and then just rerun
POINT_STAT
>> > with
>> > > >>> the
>> > > >>> >> > mask. Ok, that will save some steps.
>> > > >>> >> >
>> > > >>> >> > Alright, I'll try making the mask and do a test run
after
>> lunch,
>> > > >>> and get
>> > > >>> >> > back to you when it works.
>> > > >>> >> >
>> > > >>> >> > Thanks!
>> > > >>> >> >
>> > > >>> >> > Roz
>> > > >>> >> >
>> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway via
RT <
>> > > >>> >> > met_help at ucar.edu
>> > > >>> >> > > wrote:
>> > > >>> >> >
>> > > >>> >> > > Hi Roz,
>> > > >>> >> > >
>> > > >>> >> > > I see you're wondering how to only use point
observations
>> over
>> > > >>> water
>> > > >>> >> and
>> > > >>> >> > > discard the ones over land. You're running ASCII2NC
>> followed
>> > by
>> > > >>> >> > Point-Stat
>> > > >>> >> > > and want to know where/how to define that masking.
>> > > >>> >> > >
>> > > >>> >> > > The ASCII2NC tool supports 3 command line options
for
>> > filtering
>> > > >>> point
>> > > >>> >> > > observations spatially: -mask_grid, -mask_poly, and
>> -mask_sid,
>> > > for
>> > > >>> >> grid,
>> > > >>> >> > > polyline, and station ID masking, respectively. But
that's
>> > not
>> > > >>> really
>> > > >>> >> > what
>> > > >>> >> > > you want. You want to do "data masking" where you
read in
>> a
>> > > >>> land/sea
>> > > >>> >> > mask
>> > > >>> >> > > and only use the points over water.
>> > > >>> >> > >
>> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to create
the
>> > desired
>> > > >>> >> masking
>> > > >>> >> > > region, and then reference that in the Point-Stat
config
>> file.
>> > > >>> >> > >
>> > > >>> >> > > To illustrate, I pulled a sample GFS file:
>> > > >>> >> > > > wget
>> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
>> ata/gfs4/201807/20180702/gfs_
>> > > >>> >> > > 4_20180702_0000_012.grb2
>> > > >>> >> > >
>> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
>> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i
LAND
>> > > >>> >> > > 400:65422867:d=2018070200:LAND:surface:12 hour
fcst:
>> > > >>> >> > >
>> > > >>> >> > > Run plot_data_plane to see it (see attached image):
>> > > >>> >> > > > met-7.0/bin/plot_data_plane
>> gfs_4_20180702_0000_012.grb2
>> > > >>> >> > gfs_4_LAND.ps
>> > > >>> >> > > 'name="LAND"; level="L0";'
>> > > >>> >> > >
>> > > >>> >> > > Run gen_vx_mask to create a mask for your
verification
>> domain.
>> > > If
>> > > >>> >> you're
>> > > >>> >> > > actually verifying on the GFS domain, the command
looks a
>> > little
>> > > >>> >> > redundant:
>> > > >>> >> > >
>> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
>> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
>> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
>> > > >>> >> > > gfs_4_WATER_mask.nc \
>> > > >>> >> > > -type data \
>> > > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
>> > > >>> >> > > -thresh ==0 \
>> > > >>> >> > > -name WATER
>> > > >>> >> > >
>> > > >>> >> > > I defined the threshold as "==0" because we want the
WATER
>> > > >>> points, not
>> > > >>> >> > the
>> > > >>> >> > > LAND points. And I used the "-name WATER" command
line
>> option
>> > > to
>> > > >>> name
>> > > >>> >> > the
>> > > >>> >> > > output NetCDF variable. This will show up in the
VX_MASK
>> > output
>> > > >>> >> column
>> > > >>> >> > of
>> > > >>> >> > > Point-Stat.
>> > > >>> >> > >
>> > > >>> >> > > Lastly, setup your Point-Stat config file like this:
>> > > >>> >> > >
>> > > >>> >> > > mask = {
>> > > >>> >> > > grid = [];
>> > > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
>> > > >>> >> > > sid = [];
>> > > >>> >> > > }
>> > > >>> >> > >
>> > > >>> >> > > Hope that helps clarify.
>> > > >>> >> > >
>> > > >>> >> > > Thanks,
>> > > >>> >> > > John
>> > > >>> >> > >
>> > > >>> >> > >
>> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken -
NOAA
>> > > >>> Affiliate via
>> > > >>> >> > RT <
>> > > >>> >> > > met_help at ucar.edu> wrote:
>> > > >>> >> > >
>> > > >>> >> > > >
>> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was acted
upon.
>> > > >>> >> > > > Transaction: Ticket created by
>> rosalyn.maccracken at noaa.gov
>> > > >>> >> > > > Queue: met_help
>> > > >>> >> > > > Subject: masking land features questions
>> > > >>> >> > > > Owner: Nobody
>> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
>> > > >>> >> > > > Status: new
>> > > >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
>> > > >>> >> ket/Display.html?id=86091
>> > > >>> >> > >
>> > > >>> >> > > >
>> > > >>> >> > > >
>> > > >>> >> > > > Hi,
>> > > >>> >> > > >
>> > > >>> >> > > > I'm using ASCAT data to verify the GFS. I only
want to
>> > verify
>> > > >>> >> points
>> > > >>> >> > > over
>> > > >>> >> > > > the ocean, and not over any inland lakes. I
noticed
>> that I
>> > > was
>> > > >>> >> getting
>> > > >>> >> > > > matched points over land (mostly Africa). I'm
dumping
>> out
>> > the
>> > > >>> >> MGDRlite
>> > > >>> >> > > > file to an ascii file, which I use ASCII2NC to
create the
>> > > netCDF
>> > > >>> >> file,
>> > > >>> >> > > and
>> > > >>> >> > > > then go on to use Point_stat to create statistics
for the
>> > > >>> matched
>> > > >>> >> > points.
>> > > >>> >> > > >
>> > > >>> >> > > > How do I mask out points over land before it gets
to the
>> > > >>> Point_stat
>> > > >>> >> > step?
>> > > >>> >> > > > Is there something in the ASCII2NC processing that
I can
>> > add,
>> > > >>> so I
>> > > >>> >> > don't
>> > > >>> >> > > > get these matched points?
>> > > >>> >> > > >
>> > > >>> >> > > > Thanks in advance!
>> > > >>> >> > > >
>> > > >>> >> > > > Roz
>> > > >>> >> > > >
>> > > >>> >> > > > --
>> > > >>> >> > > > Rosalyn MacCracken
>> > > >>> >> > > > Support Scientist
>> > > >>> >> > > >
>> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Wed Jul 11 14:00:45 2018
Roz,
Bad news. I had hoped we could simply pass in the gridded mask file
you've
defined as input to STAT-Analysis using "-mask_poly" but unfortunately
that
doesn't work.
STAT-Analysis currently supports: -mask_grid, -mask_poly, and
-mask_sid to
filter MPR lines by a named grid, polyline file, or list of station id
names. The other MET tools, like Point-Stat and Grid-Stat also
support
multiple masking options.
For example, in Point-Stat:
mask = {
grid = [ "FULL" ];
poly = [];
sid = [];
}
The "mask.grid" option in Point-Stat is the same of "-mask_grid" in
STAT-Analysis. They both process named grids, like "G212" for NCEP
grid
number 212.
Likewise, the "mask.sid" option is the same as "-mask_sid". They both
define lists of station ID names to be included.
*BUT* the "mask.poly" option in Point-Stat is much more flexible than
"-mask_poly" in STAT-Analysis. In STAT-Analysis, it can only be set
to a
lat/lon polyline file. In Point-Stat, it can also be set to the
output of
gen_vx_mask or any gridded data file followed by a description of data
to
be extracted and thresholded.
We actually have a development task already defined to address this
issue
(see attached).
But that doesn't help you. So unfortunately, with met-7.0, you'd
would
need to go all the way back to generating pairs with Point-Stat.
However, if you were using a future version of MET, you could do this
all
in STAT-Analysis.
Thanks,
John
On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
> Hi John,
>
> Well, good news. We got our MET7 to work, and I was able to create
my
> ocean mask. It was an issue with conflicts in our libraries, and
the
> LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
>
> Now, I have this ocean mask, and now I can go back and rerun my
data. So,
> as usual, I had some questions.
>
> I have a series of scripts where you helped me set up STATanalysis
to
> reprocess the data using the *.stat files and the -job
aggregate_stat
> command . Will I be able to use this method again, or, because it's
> applying a mask, will I need to get the raw data (GFS and ASCAT
data)?
> And, I guess if I have to use the raw data, I will have to start
with
> ASCII2NC, etc, as if I'm processing from scratch, correct?
>
> I just need a sense of how big of a job this is....
>
> Thanks for your help!
>
> Roz
>
> On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA Affiliate
<
> rosalyn.maccracken at noaa.gov> wrote:
>
> > Oh, yeah, nothing seems to be going smoothly today...anyway, I
think I
> > need to wait until Chris and Fran come in tomorrow to set our
directories
> > correctly to point at MET, and get it running again before I do
anything
> > else.
> >
> > I'll try this again tomorrow and let you know how I do.
> >
> > Thanks for your help!
> >
> > Roz
> >
> > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Roz,
> >>
> >> Sorry you're having a rough day. No worries though, this issue
is easy
> to
> >> overcome. Here's a list of pre-defined NCEP grids:
> >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> >>
> >> The intention in MET is to support them using the naming
convention G###
> >> where ### is the 3 digit grid number. But if you look closely on
that
> >> website, you'll see that grid 193 is a relatively new one and is
listed
> in
> >> red. That definition just doesn't exist in MET version 6.0.
> >>
> >> The easy fix is this.... just replace "G193" on the command line
with
> the
> >> path to a 1/4 degree GFS GRIB2 file. Here's a selection from the
usage
> >> statement for regrid_data_plane:
> >>
> >> Usage: regrid_data_plane
> >> input_filename
> >> to_grid
> >> output_filename
> >> "to_grid" defines the output grid as a named
grid, the
> >> path
> >> to a gridded data file, or an explicit grid specification string
> >> (required).
> >>
> >> When you set "to_grid" equal to a gridded data file, MET reads
the grid
> >> definition from the first record of that file and uses it.
> >>
> >> That should do it.
> >>
> >> Thanks,
> >> John
> >>
> >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA
Affiliate via
> >> RT <
> >> met_help at ucar.edu> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >> >
> >> > Hi John,
> >> >
> >> > I'm really not having much luck today with this. Maybe I
should have
> >> > stayed in bed (haha).
> >> >
> >> > So, the first thing I did was check the LD_LIBRARY_PATH, and
it's
> >> pointing
> >> > to the MET7 directories. Ok, that could be most of the
problem. MET7
> >> seems
> >> > to be having some issue, and the guy here at OPC that helps me
with
> that
> >> > stuff (Chris Juckins) is out on leave until tomorrow. Anyway,
MET7 is
> >> not
> >> > running any of my verification programs, and giving out some
errors,
> so,
> >> > I'll have to get with him tomorrow to fix that.
> >> >
> >> > So, in the mean time, I don't think that any kind of land mask
> creation
> >> > that I'm doing today will work because it's not pointing at the
right
> >> > directories.
> >> >
> >> > But, when I do get this to work, I tried this and got this
error:
> >> > /opt/MET6/met6.0/bin/regrid_data_plane
gwes01.glo_30m.t00z.grib2 G193
> >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321
lat_ll:
> -80.000
> >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> >> > ERROR :
> >> > ERROR : grd_file_type() -> file does not exist "G193"
> >> > ERROR :
> >> >
> >> > I'm wondering if that's all related to MET7.
> >> >
> >> > So, I think I need to fix the MET7 issue before moving on with
this,
> >> don't
> >> > you?
> >> >
> >> > Roz
> >> >
> >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT <
> >> > met_help at ucar.edu
> >> > > wrote:
> >> >
> >> > > Roz,
> >> > >
> >> > > OK, one other possible option to consider. I figured that
there's
> >> plenty
> >> > > of "ocean" products out there. So I found a NOAA WAVEWATCH
one:
> >> > >
> >> > > (1) Download sample wavewatch file:
> >> > > wget
> >> > > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> >> > >
> >> > > (2) Run regrid_data_plane to put some surface wind speed data
on the
> >> 1/4
> >> > > GFS grid:
> >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
ocean_data.nc
> >> -field
> >> > > 'name="WIND"; level="L0";'
> >> > >
> >> > > (3) Run gen_vx_mask to select points that contain valid data:
> >> > > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc
-type data
> >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999
-name
> OCEAN
> >> > >
> >> > > (4) Run plot_data_plane to see the result:
> >> > > plot_data_plane ocean_mask.nc ocean_mask.ps 'name="OCEAN";
> >> > > level="(*,*)";'
> >> > >
> >> > > As you can see, the result gets rid of the lakes problem.
But
> >> wavewatch
> >> > is
> >> > > only run to +/- 80 degrees, so we're not including points
near the
> >> poles.
> >> > >
> >> > > Figured this would be a lot easier than running WPS yourself.
> >> > >
> >> > > Thanks,
> >> > > John
> >> > >
> >> > >
> >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway
<johnhg at ucar.edu>
> >> > wrote:
> >> > >
> >> > > > Roz,
> >> > > >
> >> > > > I talked to some folks and have one suggestion that *might*
work.
> >> The
> >> > > WRF
> >> > > > Pre-processing system is named WPS. The geogrid program
within
> WPS
> >> is
> >> > > used
> >> > > > to initialize your domain and handles land use information.
By
> >> > default,
> >> > > > lakes and oceans are treated the same way. However,
apparently
> >> there
> >> > is
> >> > > an
> >> > > > option to distinguish between them. Take a look here:
> >> > > >
> >> > > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> >> > > users_guide_chap3.htm#_Description_of_the_1
> >> > > >
> >> > > > And search for "Alternative Initialization of Lake SSTs".
> >> > > >
> >> > > > So you'd...
> >> > > > (1) download the MODIS SST data
> >> > > > (2) configure geogrid for the 0.25 degree GFS grid
> >> > > > (3) configure geogrid to distinguish between lakes and
oceans
> >> > > > (4) run geogrid
> >> > > > (5) run the output through the MET gen_vx_mask tool to use
ocean
> >> values
> >> > > > and skip the lake values
> >> > > >
> >> > > > Thanks,
> >> > > > John
> >> > > >
> >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <
> johnhg at ucar.edu>
> >> > > wrote:
> >> > > >
> >> > > >> Roz,
> >> > > >>
> >> > > >> Whenever you see that error about loading shared
libraries, it
> >> means
> >> > > that
> >> > > >> there's a problem in how your LD_LIBRARY_PATH environment
> variable
> >> is
> >> > > set.
> >> > > >> That environment variable tells the linker where to look
for
> shared
> >> > > >> libraries at runtime... one of those shared libraries is
GSL (GNU
> >> > > >> Scientific Library). You'd "fix" this issue by modifying
how
> >> > > >> LD_LIBRARY_PATH is set:
> >> > > >> echo $LD_LIBRARY_PATH
> >> > > >>
> >> > > >> Take a look in your ~/.cshrc file for c-shell or ~/.bashrc
for
> >> bash to
> >> > > >> see how its set.
> >> > > >>
> >> > > >> As for the LAND/SEA mask, I was wondering if those lakes
would
> be a
> >> > > >> problem. Using the model's LAND/SEA mask is the easiest,
but
> >> doesn't
> >> > > >> provide an easy way of selecting out oceans. My next
thought was
> >> to
> >> > use
> >> > > >> GIS Shapefiles to define only the ocean area. That will
be
> >> available
> >> > in
> >> > > >> the next version of MET, version 7.1. I tried using a
beta
> release
> >> > for
> >> > > >> met-7.1, but ran into problems when applying large
polylines to
> >> global
> >> > > >> grids.
> >> > > >>
> >> > > >> I'll keep thinking about that one.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> John
> >> > > >>
> >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken - NOAA
> Affiliate
> >> > via
> >> > > >> RT <met_help at ucar.edu> wrote:
> >> > > >>
> >> > > >>>
> >> > > >>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >> > > >>>
> >> > > >>> Hey John,
> >> > > >>>
> >> > > >>> I have 2 problems. First, I'm able to use
plot_data_plane, but,
> >> > when I
> >> > > >>> use
> >> > > >>> the command for gen_vx_mask, I get this:
> >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask gfs.t00z.pgrb2.0p25.f000
> >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
> >> -mask_field
> >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading
shared
> >> > > libraries:
> >> > > >>> libgsl.so.0: cannot open shared object file: No such file
or
> >> > directory
> >> > > >>>
> >> > > >>> Now, they are both in the same directory, and I know that
I've
> >> used
> >> > > >>> gen_vx_mask before, so, I have no idea why I would be
getting
> that
> >> > > error
> >> > > >>> message. Any ideas?
> >> > > >>>
> >> > > >>> Then, I was able to generate a *.ps file, which looks
exactly
> like
> >> > > yours,
> >> > > >>> but, there is still the same problem. If you look
closely are
> >> your
> >> > > map,
> >> > > >>> you'll see these little white dots over land. Those are
lakes,
> >> and
> >> > > >>> that's
> >> > > >>> what is giving me a fit, because I have ASCAT
observations over
> >> those
> >> > > >>> white
> >> > > >>> dots. You know, I'm using 0.25 deg GFS data with 12 km
ASCAT
> >> > > data...so,
> >> > > >>> very sensitive. Anyway, do you have any idea how to get
rid of
> >> those
> >> > > >>> points? Perhaps a different file with the same domain?
> >> > > >>>
> >> > > >>> Roz
> >> > > >>>
> >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken - NOAA
> >> Affiliate <
> >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> >> > > >>>
> >> > > >>> > Ok, I'll let you know if I can get the mask to work.
This
> seems
> >> > easy
> >> > > >>> > enough, and pretty straight forward.
> >> > > >>> >
> >> > > >>> > Thanks for the help!
> >> > > >>> >
> >> > > >>> > Roz
> >> > > >>> >
> >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway via
RT <
> >> > > >>> > met_help at ucar.edu> wrote:
> >> > > >>> >
> >> > > >>> >> Roz,
> >> > > >>> >>
> >> > > >>> >> Yes, I expect that using met-6.0 would work fine.
Hope it
> goes
> >> > > >>> smoothly.
> >> > > >>> >>
> >> > > >>> >> Thanks,
> >> > > >>> >> John
> >> > > >>> >>
> >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn MacCracken -
NOAA
> >> Affiliate
> >> > > >>> via RT
> >> > > >>> >> <
> >> > > >>> >> met_help at ucar.edu> wrote:
> >> > > >>> >>
> >> > > >>> >> >
> >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> >> ket/Display.html?id=86091 >
> >> > > >>> >> >
> >> > > >>> >> > Hi John,
> >> > > >>> >> >
> >> > > >>> >> > I get the general idea and it looks pretty straight
> forward.
> >> > I'm
> >> > > >>> still
> >> > > >>> >> > running MET6.0, since we had some installation
issues,
> but, I
> >> > > >>> should be
> >> > > >>> >> > able to generate the mask with that pretty easily,
correct?
> >> > > >>> >> >
> >> > > >>> >> > So, if this works, I'll need to rerun all my data
from Mar
> >> 2018
> >> > -
> >> > > >>> >> present,
> >> > > >>> >> > using that method that we worked out earlier with
the
> *.stat
> >> > > files,
> >> > > >>> >> > correct? Actually, I don't need to do that...I can
start
> >> from
> >> > the
> >> > > >>> ASCII
> >> > > >>> >> > files I've already generated, and then just rerun
> POINT_STAT
> >> > with
> >> > > >>> the
> >> > > >>> >> > mask. Ok, that will save some steps.
> >> > > >>> >> >
> >> > > >>> >> > Alright, I'll try making the mask and do a test run
after
> >> lunch,
> >> > > >>> and get
> >> > > >>> >> > back to you when it works.
> >> > > >>> >> >
> >> > > >>> >> > Thanks!
> >> > > >>> >> >
> >> > > >>> >> > Roz
> >> > > >>> >> >
> >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway
via RT <
> >> > > >>> >> > met_help at ucar.edu
> >> > > >>> >> > > wrote:
> >> > > >>> >> >
> >> > > >>> >> > > Hi Roz,
> >> > > >>> >> > >
> >> > > >>> >> > > I see you're wondering how to only use point
observations
> >> over
> >> > > >>> water
> >> > > >>> >> and
> >> > > >>> >> > > discard the ones over land. You're running
ASCII2NC
> >> followed
> >> > by
> >> > > >>> >> > Point-Stat
> >> > > >>> >> > > and want to know where/how to define that masking.
> >> > > >>> >> > >
> >> > > >>> >> > > The ASCII2NC tool supports 3 command line options
for
> >> > filtering
> >> > > >>> point
> >> > > >>> >> > > observations spatially: -mask_grid, -mask_poly,
and
> >> -mask_sid,
> >> > > for
> >> > > >>> >> grid,
> >> > > >>> >> > > polyline, and station ID masking, respectively.
But
> that's
> >> > not
> >> > > >>> really
> >> > > >>> >> > what
> >> > > >>> >> > > you want. You want to do "data masking" where you
read
> in
> >> a
> >> > > >>> land/sea
> >> > > >>> >> > mask
> >> > > >>> >> > > and only use the points over water.
> >> > > >>> >> > >
> >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to
create the
> >> > desired
> >> > > >>> >> masking
> >> > > >>> >> > > region, and then reference that in the Point-Stat
config
> >> file.
> >> > > >>> >> > >
> >> > > >>> >> > > To illustrate, I pulled a sample GFS file:
> >> > > >>> >> > > > wget
> >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> >> ata/gfs4/201807/20180702/gfs_
> >> > > >>> >> > > 4_20180702_0000_012.grb2
> >> > > >>> >> > >
> >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep -i
LAND
> >> > > >>> >> > > 400:65422867:d=2018070200:LAND:surface:12
hour
> fcst:
> >> > > >>> >> > >
> >> > > >>> >> > > Run plot_data_plane to see it (see attached
image):
> >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> >> gfs_4_20180702_0000_012.grb2
> >> > > >>> >> > gfs_4_LAND.ps
> >> > > >>> >> > > 'name="LAND"; level="L0";'
> >> > > >>> >> > >
> >> > > >>> >> > > Run gen_vx_mask to create a mask for your
verification
> >> domain.
> >> > > If
> >> > > >>> >> you're
> >> > > >>> >> > > actually verifying on the GFS domain, the command
looks a
> >> > little
> >> > > >>> >> > redundant:
> >> > > >>> >> > >
> >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > > >>> >> > > gfs_4_WATER_mask.nc \
> >> > > >>> >> > > -type data \
> >> > > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
> >> > > >>> >> > > -thresh ==0 \
> >> > > >>> >> > > -name WATER
> >> > > >>> >> > >
> >> > > >>> >> > > I defined the threshold as "==0" because we want
the
> WATER
> >> > > >>> points, not
> >> > > >>> >> > the
> >> > > >>> >> > > LAND points. And I used the "-name WATER" command
line
> >> option
> >> > > to
> >> > > >>> name
> >> > > >>> >> > the
> >> > > >>> >> > > output NetCDF variable. This will show up in the
VX_MASK
> >> > output
> >> > > >>> >> column
> >> > > >>> >> > of
> >> > > >>> >> > > Point-Stat.
> >> > > >>> >> > >
> >> > > >>> >> > > Lastly, setup your Point-Stat config file like
this:
> >> > > >>> >> > >
> >> > > >>> >> > > mask = {
> >> > > >>> >> > > grid = [];
> >> > > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> >> > > >>> >> > > sid = [];
> >> > > >>> >> > > }
> >> > > >>> >> > >
> >> > > >>> >> > > Hope that helps clarify.
> >> > > >>> >> > >
> >> > > >>> >> > > Thanks,
> >> > > >>> >> > > John
> >> > > >>> >> > >
> >> > > >>> >> > >
> >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn MacCracken
- NOAA
> >> > > >>> Affiliate via
> >> > > >>> >> > RT <
> >> > > >>> >> > > met_help at ucar.edu> wrote:
> >> > > >>> >> > >
> >> > > >>> >> > > >
> >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was
acted upon.
> >> > > >>> >> > > > Transaction: Ticket created by
> >> rosalyn.maccracken at noaa.gov
> >> > > >>> >> > > > Queue: met_help
> >> > > >>> >> > > > Subject: masking land features questions
> >> > > >>> >> > > > Owner: Nobody
> >> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> >> > > >>> >> > > > Status: new
> >> > > >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> >> > > >>> >> ket/Display.html?id=86091
> >> > > >>> >> > >
> >> > > >>> >> > > >
> >> > > >>> >> > > >
> >> > > >>> >> > > > Hi,
> >> > > >>> >> > > >
> >> > > >>> >> > > > I'm using ASCAT data to verify the GFS. I only
want to
> >> > verify
> >> > > >>> >> points
> >> > > >>> >> > > over
> >> > > >>> >> > > > the ocean, and not over any inland lakes. I
noticed
> >> that I
> >> > > was
> >> > > >>> >> getting
> >> > > >>> >> > > > matched points over land (mostly Africa). I'm
dumping
> >> out
> >> > the
> >> > > >>> >> MGDRlite
> >> > > >>> >> > > > file to an ascii file, which I use ASCII2NC to
create
> the
> >> > > netCDF
> >> > > >>> >> file,
> >> > > >>> >> > > and
> >> > > >>> >> > > > then go on to use Point_stat to create
statistics for
> the
> >> > > >>> matched
> >> > > >>> >> > points.
> >> > > >>> >> > > >
> >> > > >>> >> > > > How do I mask out points over land before it
gets to
> the
> >> > > >>> Point_stat
> >> > > >>> >> > step?
> >> > > >>> >> > > > Is there something in the ASCII2NC processing
that I
> can
> >> > add,
> >> > > >>> so I
> >> > > >>> >> > don't
> >> > > >>> >> > > > get these matched points?
> >> > > >>> >> > > >
> >> > > >>> >> > > > Thanks in advance!
> >> > > >>> >> > > >
> >> > > >>> >> > > > Roz
> >> > > >>> >> > > >
> >> > > >>> >> > > > --
> >> > > >>> >> > > > Rosalyn MacCracken
> >> > > >>> >> > > > Support Scientist
> >> > > >>> >> > > >
> >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu Jul 12 07:09:52 2018
Hi John,
There's got to be a way around this...I'm sure there is a work around
so
that I don't have to go back an get all of the GFS files. And, I know
that
I want to use STAT-Analysis, since I already have all that in place to
regenerate data.
So, you said I can use a lat/lon polyline file with STAT-Analysis. Of
course, I already use that with my North Atlantic or North Pacific
masks.
So, my first option might be, make my North Atlantic mask smaller, not
to
include West Africa, where the bad observations are located, and don't
use
the global file that is generated (if there a way not to make that
file,
and only re-generate files for the North Atlantic?). Ok...that's one
option, and that's probably what I will have to do.
Here's the question. So, let's say there was a way for us to go back
through our ASCAT data, and identify lat/lons of observations that
were
flagged not to use, or over land, is there a way to have STAT-Analysis
discard matched pairs associated with those lat/lons? Maybe, that's
like
using the lat/lon ployline file in reverse? Here's the mask, use all
observations except if it falls inside this masked domain? Can we do
that?
Roz
On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> Bad news. I had hoped we could simply pass in the gridded mask file
you've
> defined as input to STAT-Analysis using "-mask_poly" but
unfortunately that
> doesn't work.
>
> STAT-Analysis currently supports: -mask_grid, -mask_poly, and
-mask_sid to
> filter MPR lines by a named grid, polyline file, or list of station
id
> names. The other MET tools, like Point-Stat and Grid-Stat also
support
> multiple masking options.
>
> For example, in Point-Stat:
> mask = {
> grid = [ "FULL" ];
> poly = [];
> sid = [];
> }
>
> The "mask.grid" option in Point-Stat is the same of "-mask_grid" in
> STAT-Analysis. They both process named grids, like "G212" for NCEP
grid
> number 212.
>
> Likewise, the "mask.sid" option is the same as "-mask_sid". They
both
> define lists of station ID names to be included.
>
> *BUT* the "mask.poly" option in Point-Stat is much more flexible
than
> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can only be set
to a
> lat/lon polyline file. In Point-Stat, it can also be set to the
output of
> gen_vx_mask or any gridded data file followed by a description of
data to
> be extracted and thresholded.
>
> We actually have a development task already defined to address this
issue
> (see attached).
>
> But that doesn't help you. So unfortunately, with met-7.0, you'd
would
> need to go all the way back to generating pairs with Point-Stat.
>
> However, if you were using a future version of MET, you could do
this all
> in STAT-Analysis.
>
> Thanks,
> John
>
> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >
> > Hi John,
> >
> > Well, good news. We got our MET7 to work, and I was able to
create my
> > ocean mask. It was an issue with conflicts in our libraries, and
the
> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> >
> > Now, I have this ocean mask, and now I can go back and rerun my
data.
> So,
> > as usual, I had some questions.
> >
> > I have a series of scripts where you helped me set up STATanalysis
to
> > reprocess the data using the *.stat files and the -job
aggregate_stat
> > command . Will I be able to use this method again, or, because
it's
> > applying a mask, will I need to get the raw data (GFS and ASCAT
data)?
> > And, I guess if I have to use the raw data, I will have to start
with
> > ASCII2NC, etc, as if I'm processing from scratch, correct?
> >
> > I just need a sense of how big of a job this is....
> >
> > Thanks for your help!
> >
> > Roz
> >
> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > rosalyn.maccracken at noaa.gov> wrote:
> >
> > > Oh, yeah, nothing seems to be going smoothly today...anyway, I
think I
> > > need to wait until Chris and Fran come in tomorrow to set our
> directories
> > > correctly to point at MET, and get it running again before I do
> anything
> > > else.
> > >
> > > I'll try this again tomorrow and let you know how I do.
> > >
> > > Thanks for your help!
> > >
> > > Roz
> > >
> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> Roz,
> > >>
> > >> Sorry you're having a rough day. No worries though, this issue
is
> easy
> > to
> > >> overcome. Here's a list of pre-defined NCEP grids:
> > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> > >>
> > >> The intention in MET is to support them using the naming
convention
> G###
> > >> where ### is the 3 digit grid number. But if you look closely
on that
> > >> website, you'll see that grid 193 is a relatively new one and
is
> listed
> > in
> > >> red. That definition just doesn't exist in MET version 6.0.
> > >>
> > >> The easy fix is this.... just replace "G193" on the command
line with
> > the
> > >> path to a 1/4 degree GFS GRIB2 file. Here's a selection from
the
> usage
> > >> statement for regrid_data_plane:
> > >>
> > >> Usage: regrid_data_plane
> > >> input_filename
> > >> to_grid
> > >> output_filename
> > >> "to_grid" defines the output grid as a named
grid, the
> > >> path
> > >> to a gridded data file, or an explicit grid specification
string
> > >> (required).
> > >>
> > >> When you set "to_grid" equal to a gridded data file, MET reads
the
> grid
> > >> definition from the first record of that file and uses it.
> > >>
> > >> That should do it.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA
Affiliate
> via
> > >> RT <
> > >> met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
>
> > >> >
> > >> > Hi John,
> > >> >
> > >> > I'm really not having much luck today with this. Maybe I
should
> have
> > >> > stayed in bed (haha).
> > >> >
> > >> > So, the first thing I did was check the LD_LIBRARY_PATH, and
it's
> > >> pointing
> > >> > to the MET7 directories. Ok, that could be most of the
problem.
> MET7
> > >> seems
> > >> > to be having some issue, and the guy here at OPC that helps
me with
> > that
> > >> > stuff (Chris Juckins) is out on leave until tomorrow.
Anyway, MET7
> is
> > >> not
> > >> > running any of my verification programs, and giving out some
errors,
> > so,
> > >> > I'll have to get with him tomorrow to fix that.
> > >> >
> > >> > So, in the mean time, I don't think that any kind of land
mask
> > creation
> > >> > that I'm doing today will work because it's not pointing at
the
> right
> > >> > directories.
> > >> >
> > >> > But, when I do get this to work, I tried this and got this
error:
> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
gwes01.glo_30m.t00z.grib2
> G193
> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> > >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321
lat_ll:
> > -80.000
> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> > >> > ERROR :
> > >> > ERROR : grd_file_type() -> file does not exist "G193"
> > >> > ERROR :
> > >> >
> > >> > I'm wondering if that's all related to MET7.
> > >> >
> > >> > So, I think I need to fix the MET7 issue before moving on
with this,
> > >> don't
> > >> > you?
> > >> >
> > >> > Roz
> > >> >
> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT <
> > >> > met_help at ucar.edu
> > >> > > wrote:
> > >> >
> > >> > > Roz,
> > >> > >
> > >> > > OK, one other possible option to consider. I figured that
there's
> > >> plenty
> > >> > > of "ocean" products out there. So I found a NOAA WAVEWATCH
one:
> > >> > >
> > >> > > (1) Download sample wavewatch file:
> > >> > > wget
> > >> > > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> > >> > >
> > >> > > (2) Run regrid_data_plane to put some surface wind speed
data on
> the
> > >> 1/4
> > >> > > GFS grid:
> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
ocean_data.nc
> > >> -field
> > >> > > 'name="WIND"; level="L0";'
> > >> > >
> > >> > > (3) Run gen_vx_mask to select points that contain valid
data:
> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc
-type
> data
> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999
-name
> > OCEAN
> > >> > >
> > >> > > (4) Run plot_data_plane to see the result:
> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
'name="OCEAN";
> > >> > > level="(*,*)";'
> > >> > >
> > >> > > As you can see, the result gets rid of the lakes problem.
But
> > >> wavewatch
> > >> > is
> > >> > > only run to +/- 80 degrees, so we're not including points
near the
> > >> poles.
> > >> > >
> > >> > > Figured this would be a lot easier than running WPS
yourself.
> > >> > >
> > >> > > Thanks,
> > >> > > John
> > >> > >
> > >> > >
> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <
> johnhg at ucar.edu>
> > >> > wrote:
> > >> > >
> > >> > > > Roz,
> > >> > > >
> > >> > > > I talked to some folks and have one suggestion that
*might*
> work.
> > >> The
> > >> > > WRF
> > >> > > > Pre-processing system is named WPS. The geogrid program
within
> > WPS
> > >> is
> > >> > > used
> > >> > > > to initialize your domain and handles land use
information. By
> > >> > default,
> > >> > > > lakes and oceans are treated the same way. However,
apparently
> > >> there
> > >> > is
> > >> > > an
> > >> > > > option to distinguish between them. Take a look here:
> > >> > > >
> > >> > > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> > >> > > users_guide_chap3.htm#_Description_of_the_1
> > >> > > >
> > >> > > > And search for "Alternative Initialization of Lake SSTs".
> > >> > > >
> > >> > > > So you'd...
> > >> > > > (1) download the MODIS SST data
> > >> > > > (2) configure geogrid for the 0.25 degree GFS grid
> > >> > > > (3) configure geogrid to distinguish between lakes and
oceans
> > >> > > > (4) run geogrid
> > >> > > > (5) run the output through the MET gen_vx_mask tool to
use ocean
> > >> values
> > >> > > > and skip the lake values
> > >> > > >
> > >> > > > Thanks,
> > >> > > > John
> > >> > > >
> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <
> > johnhg at ucar.edu>
> > >> > > wrote:
> > >> > > >
> > >> > > >> Roz,
> > >> > > >>
> > >> > > >> Whenever you see that error about loading shared
libraries, it
> > >> means
> > >> > > that
> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
environment
> > variable
> > >> is
> > >> > > set.
> > >> > > >> That environment variable tells the linker where to look
for
> > shared
> > >> > > >> libraries at runtime... one of those shared libraries is
GSL
> (GNU
> > >> > > >> Scientific Library). You'd "fix" this issue by
modifying how
> > >> > > >> LD_LIBRARY_PATH is set:
> > >> > > >> echo $LD_LIBRARY_PATH
> > >> > > >>
> > >> > > >> Take a look in your ~/.cshrc file for c-shell or
~/.bashrc for
> > >> bash to
> > >> > > >> see how its set.
> > >> > > >>
> > >> > > >> As for the LAND/SEA mask, I was wondering if those lakes
would
> > be a
> > >> > > >> problem. Using the model's LAND/SEA mask is the
easiest, but
> > >> doesn't
> > >> > > >> provide an easy way of selecting out oceans. My next
thought
> was
> > >> to
> > >> > use
> > >> > > >> GIS Shapefiles to define only the ocean area. That will
be
> > >> available
> > >> > in
> > >> > > >> the next version of MET, version 7.1. I tried using a
beta
> > release
> > >> > for
> > >> > > >> met-7.1, but ran into problems when applying large
polylines to
> > >> global
> > >> > > >> grids.
> > >> > > >>
> > >> > > >> I'll keep thinking about that one.
> > >> > > >>
> > >> > > >> Thanks,
> > >> > > >> John
> > >> > > >>
> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken -
NOAA
> > Affiliate
> > >> > via
> > >> > > >> RT <met_help at ucar.edu> wrote:
> > >> > > >>
> > >> > > >>>
> > >> > > >>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> >
> > >> > > >>>
> > >> > > >>> Hey John,
> > >> > > >>>
> > >> > > >>> I have 2 problems. First, I'm able to use
plot_data_plane,
> but,
> > >> > when I
> > >> > > >>> use
> > >> > > >>> the command for gen_vx_mask, I get this:
> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
gfs.t00z.pgrb2.0p25.f000
> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type data
> > >> -mask_field
> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading
shared
> > >> > > libraries:
> > >> > > >>> libgsl.so.0: cannot open shared object file: No such
file or
> > >> > directory
> > >> > > >>>
> > >> > > >>> Now, they are both in the same directory, and I know
that I've
> > >> used
> > >> > > >>> gen_vx_mask before, so, I have no idea why I would be
getting
> > that
> > >> > > error
> > >> > > >>> message. Any ideas?
> > >> > > >>>
> > >> > > >>> Then, I was able to generate a *.ps file, which looks
exactly
> > like
> > >> > > yours,
> > >> > > >>> but, there is still the same problem. If you look
closely are
> > >> your
> > >> > > map,
> > >> > > >>> you'll see these little white dots over land. Those
are
> lakes,
> > >> and
> > >> > > >>> that's
> > >> > > >>> what is giving me a fit, because I have ASCAT
observations
> over
> > >> those
> > >> > > >>> white
> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data with 12 km
ASCAT
> > >> > > data...so,
> > >> > > >>> very sensitive. Anyway, do you have any idea how to
get rid
> of
> > >> those
> > >> > > >>> points? Perhaps a different file with the same domain?
> > >> > > >>>
> > >> > > >>> Roz
> > >> > > >>>
> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken -
NOAA
> > >> Affiliate <
> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> > >> > > >>>
> > >> > > >>> > Ok, I'll let you know if I can get the mask to work.
This
> > seems
> > >> > easy
> > >> > > >>> > enough, and pretty straight forward.
> > >> > > >>> >
> > >> > > >>> > Thanks for the help!
> > >> > > >>> >
> > >> > > >>> > Roz
> > >> > > >>> >
> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway
via RT <
> > >> > > >>> > met_help at ucar.edu> wrote:
> > >> > > >>> >
> > >> > > >>> >> Roz,
> > >> > > >>> >>
> > >> > > >>> >> Yes, I expect that using met-6.0 would work fine.
Hope it
> > goes
> > >> > > >>> smoothly.
> > >> > > >>> >>
> > >> > > >>> >> Thanks,
> > >> > > >>> >> John
> > >> > > >>> >>
> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn MacCracken -
NOAA
> > >> Affiliate
> > >> > > >>> via RT
> > >> > > >>> >> <
> > >> > > >>> >> met_help at ucar.edu> wrote:
> > >> > > >>> >>
> > >> > > >>> >> >
> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> > >> ket/Display.html?id=86091 >
> > >> > > >>> >> >
> > >> > > >>> >> > Hi John,
> > >> > > >>> >> >
> > >> > > >>> >> > I get the general idea and it looks pretty
straight
> > forward.
> > >> > I'm
> > >> > > >>> still
> > >> > > >>> >> > running MET6.0, since we had some installation
issues,
> > but, I
> > >> > > >>> should be
> > >> > > >>> >> > able to generate the mask with that pretty easily,
> correct?
> > >> > > >>> >> >
> > >> > > >>> >> > So, if this works, I'll need to rerun all my data
from
> Mar
> > >> 2018
> > >> > -
> > >> > > >>> >> present,
> > >> > > >>> >> > using that method that we worked out earlier with
the
> > *.stat
> > >> > > files,
> > >> > > >>> >> > correct? Actually, I don't need to do that...I
can start
> > >> from
> > >> > the
> > >> > > >>> ASCII
> > >> > > >>> >> > files I've already generated, and then just rerun
> > POINT_STAT
> > >> > with
> > >> > > >>> the
> > >> > > >>> >> > mask. Ok, that will save some steps.
> > >> > > >>> >> >
> > >> > > >>> >> > Alright, I'll try making the mask and do a test
run after
> > >> lunch,
> > >> > > >>> and get
> > >> > > >>> >> > back to you when it works.
> > >> > > >>> >> >
> > >> > > >>> >> > Thanks!
> > >> > > >>> >> >
> > >> > > >>> >> > Roz
> > >> > > >>> >> >
> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley Gotway
via
> RT <
> > >> > > >>> >> > met_help at ucar.edu
> > >> > > >>> >> > > wrote:
> > >> > > >>> >> >
> > >> > > >>> >> > > Hi Roz,
> > >> > > >>> >> > >
> > >> > > >>> >> > > I see you're wondering how to only use point
> observations
> > >> over
> > >> > > >>> water
> > >> > > >>> >> and
> > >> > > >>> >> > > discard the ones over land. You're running
ASCII2NC
> > >> followed
> > >> > by
> > >> > > >>> >> > Point-Stat
> > >> > > >>> >> > > and want to know where/how to define that
masking.
> > >> > > >>> >> > >
> > >> > > >>> >> > > The ASCII2NC tool supports 3 command line
options for
> > >> > filtering
> > >> > > >>> point
> > >> > > >>> >> > > observations spatially: -mask_grid, -mask_poly,
and
> > >> -mask_sid,
> > >> > > for
> > >> > > >>> >> grid,
> > >> > > >>> >> > > polyline, and station ID masking, respectively.
But
> > that's
> > >> > not
> > >> > > >>> really
> > >> > > >>> >> > what
> > >> > > >>> >> > > you want. You want to do "data masking" where
you read
> > in
> > >> a
> > >> > > >>> land/sea
> > >> > > >>> >> > mask
> > >> > > >>> >> > > and only use the points over water.
> > >> > > >>> >> > >
> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to
create
> the
> > >> > desired
> > >> > > >>> >> masking
> > >> > > >>> >> > > region, and then reference that in the Point-
Stat
> config
> > >> file.
> > >> > > >>> >> > >
> > >> > > >>> >> > > To illustrate, I pulled a sample GFS file:
> > >> > > >>> >> > > > wget
> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> > >> ata/gfs4/201807/20180702/gfs_
> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> > >> > > >>> >> > >
> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> > >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep
-i LAND
> > >> > > >>> >> > > 400:65422867:d=2018070200:LAND:surface:12
hour
> > fcst:
> > >> > > >>> >> > >
> > >> > > >>> >> > > Run plot_data_plane to see it (see attached
image):
> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> > >> gfs_4_20180702_0000_012.grb2
> > >> > > >>> >> > gfs_4_LAND.ps
> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> > >> > > >>> >> > >
> > >> > > >>> >> > > Run gen_vx_mask to create a mask for your
verification
> > >> domain.
> > >> > > If
> > >> > > >>> >> you're
> > >> > > >>> >> > > actually verifying on the GFS domain, the
command
> looks a
> > >> > little
> > >> > > >>> >> > redundant:
> > >> > > >>> >> > >
> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> > >> > > >>> >> > > -type data \
> > >> > > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
> > >> > > >>> >> > > -thresh ==0 \
> > >> > > >>> >> > > -name WATER
> > >> > > >>> >> > >
> > >> > > >>> >> > > I defined the threshold as "==0" because we want
the
> > WATER
> > >> > > >>> points, not
> > >> > > >>> >> > the
> > >> > > >>> >> > > LAND points. And I used the "-name WATER"
command line
> > >> option
> > >> > > to
> > >> > > >>> name
> > >> > > >>> >> > the
> > >> > > >>> >> > > output NetCDF variable. This will show up in
the
> VX_MASK
> > >> > output
> > >> > > >>> >> column
> > >> > > >>> >> > of
> > >> > > >>> >> > > Point-Stat.
> > >> > > >>> >> > >
> > >> > > >>> >> > > Lastly, setup your Point-Stat config file like
this:
> > >> > > >>> >> > >
> > >> > > >>> >> > > mask = {
> > >> > > >>> >> > > grid = [];
> > >> > > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc" ];
> > >> > > >>> >> > > sid = [];
> > >> > > >>> >> > > }
> > >> > > >>> >> > >
> > >> > > >>> >> > > Hope that helps clarify.
> > >> > > >>> >> > >
> > >> > > >>> >> > > Thanks,
> > >> > > >>> >> > > John
> > >> > > >>> >> > >
> > >> > > >>> >> > >
> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
MacCracken -
> NOAA
> > >> > > >>> Affiliate via
> > >> > > >>> >> > RT <
> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> > >> > > >>> >> > >
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was
acted
> upon.
> > >> > > >>> >> > > > Transaction: Ticket created by
> > >> rosalyn.maccracken at noaa.gov
> > >> > > >>> >> > > > Queue: met_help
> > >> > > >>> >> > > > Subject: masking land features questions
> > >> > > >>> >> > > > Owner: Nobody
> > >> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> > >> > > >>> >> > > > Status: new
> > >> > > >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> > >> > > >>> >> ket/Display.html?id=86091
> > >> > > >>> >> > >
> > >> > > >>> >> > > >
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > Hi,
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > I'm using ASCAT data to verify the GFS. I
only want
> to
> > >> > verify
> > >> > > >>> >> points
> > >> > > >>> >> > > over
> > >> > > >>> >> > > > the ocean, and not over any inland lakes. I
noticed
> > >> that I
> > >> > > was
> > >> > > >>> >> getting
> > >> > > >>> >> > > > matched points over land (mostly Africa). I'm
> dumping
> > >> out
> > >> > the
> > >> > > >>> >> MGDRlite
> > >> > > >>> >> > > > file to an ascii file, which I use ASCII2NC to
create
> > the
> > >> > > netCDF
> > >> > > >>> >> file,
> > >> > > >>> >> > > and
> > >> > > >>> >> > > > then go on to use Point_stat to create
statistics for
> > the
> > >> > > >>> matched
> > >> > > >>> >> > points.
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > How do I mask out points over land before it
gets to
> > the
> > >> > > >>> Point_stat
> > >> > > >>> >> > step?
> > >> > > >>> >> > > > Is there something in the ASCII2NC processing
that I
> > can
> > >> > add,
> > >> > > >>> so I
> > >> > > >>> >> > don't
> > >> > > >>> >> > > > get these matched points?
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > Thanks in advance!
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > Roz
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > --
> > >> > > >>> >> > > > Rosalyn MacCracken
> > >> > > >>> >> > > > Support Scientist
> > >> > > >>> >> > > >
> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu Jul 12 07:43:16 2018
Oh, but, I can incorporate this new land mask from here on out, right?
And,
I would add that to my Point-stat config file, like you showed me to
do in
the previous email, correct?
Roz
On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA Affiliate <
rosalyn.maccracken at noaa.gov> wrote:
> Hi John,
>
> There's got to be a way around this...I'm sure there is a work
around so
> that I don't have to go back an get all of the GFS files. And, I
know that
> I want to use STAT-Analysis, since I already have all that in place
to
> regenerate data.
>
> So, you said I can use a lat/lon polyline file with STAT-Analysis.
Of
> course, I already use that with my North Atlantic or North Pacific
masks.
> So, my first option might be, make my North Atlantic mask smaller,
not to
> include West Africa, where the bad observations are located, and
don't use
> the global file that is generated (if there a way not to make that
file,
> and only re-generate files for the North Atlantic?). Ok...that's
one
> option, and that's probably what I will have to do.
>
> Here's the question. So, let's say there was a way for us to go
back
> through our ASCAT data, and identify lat/lons of observations that
were
> flagged not to use, or over land, is there a way to have STAT-
Analysis
> discard matched pairs associated with those lat/lons? Maybe, that's
like
> using the lat/lon ployline file in reverse? Here's the mask, use
all
> observations except if it falls inside this masked domain? Can we
do that?
>
> Roz
>
>
>
> On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Roz,
>>
>> Bad news. I had hoped we could simply pass in the gridded mask
file
>> you've
>> defined as input to STAT-Analysis using "-mask_poly" but
unfortunately
>> that
>> doesn't work.
>>
>> STAT-Analysis currently supports: -mask_grid, -mask_poly, and
-mask_sid to
>> filter MPR lines by a named grid, polyline file, or list of station
id
>> names. The other MET tools, like Point-Stat and Grid-Stat also
support
>> multiple masking options.
>>
>> For example, in Point-Stat:
>> mask = {
>> grid = [ "FULL" ];
>> poly = [];
>> sid = [];
>> }
>>
>> The "mask.grid" option in Point-Stat is the same of "-mask_grid" in
>> STAT-Analysis. They both process named grids, like "G212" for NCEP
grid
>> number 212.
>>
>> Likewise, the "mask.sid" option is the same as "-mask_sid". They
both
>> define lists of station ID names to be included.
>>
>> *BUT* the "mask.poly" option in Point-Stat is much more flexible
than
>> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can only be
set to a
>> lat/lon polyline file. In Point-Stat, it can also be set to the
output of
>> gen_vx_mask or any gridded data file followed by a description of
data to
>> be extracted and thresholded.
>>
>> We actually have a development task already defined to address this
issue
>> (see attached).
>>
>> But that doesn't help you. So unfortunately, with met-7.0, you'd
would
>> need to go all the way back to generating pairs with Point-Stat.
>>
>> However, if you were using a future version of MET, you could do
this all
>> in STAT-Analysis.
>>
>> Thanks,
>> John
>>
>> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA Affiliate
via
>> RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>> >
>> > Hi John,
>> >
>> > Well, good news. We got our MET7 to work, and I was able to
create my
>> > ocean mask. It was an issue with conflicts in our libraries, and
the
>> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
>> >
>> > Now, I have this ocean mask, and now I can go back and rerun my
data.
>> So,
>> > as usual, I had some questions.
>> >
>> > I have a series of scripts where you helped me set up
STATanalysis to
>> > reprocess the data using the *.stat files and the -job
aggregate_stat
>> > command . Will I be able to use this method again, or, because
it's
>> > applying a mask, will I need to get the raw data (GFS and ASCAT
data)?
>> > And, I guess if I have to use the raw data, I will have to start
with
>> > ASCII2NC, etc, as if I'm processing from scratch, correct?
>> >
>> > I just need a sense of how big of a job this is....
>> >
>> > Thanks for your help!
>> >
>> > Roz
>> >
>> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA
Affiliate <
>> > rosalyn.maccracken at noaa.gov> wrote:
>> >
>> > > Oh, yeah, nothing seems to be going smoothly today...anyway, I
think I
>> > > need to wait until Chris and Fran come in tomorrow to set our
>> directories
>> > > correctly to point at MET, and get it running again before I do
>> anything
>> > > else.
>> > >
>> > > I'll try this again tomorrow and let you know how I do.
>> > >
>> > > Thanks for your help!
>> > >
>> > > Roz
>> > >
>> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT <
>> > > met_help at ucar.edu> wrote:
>> > >
>> > >> Roz,
>> > >>
>> > >> Sorry you're having a rough day. No worries though, this
issue is
>> easy
>> > to
>> > >> overcome. Here's a list of pre-defined NCEP grids:
>> > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
>> > >>
>> > >> The intention in MET is to support them using the naming
convention
>> G###
>> > >> where ### is the 3 digit grid number. But if you look closely
on
>> that
>> > >> website, you'll see that grid 193 is a relatively new one and
is
>> listed
>> > in
>> > >> red. That definition just doesn't exist in MET version 6.0.
>> > >>
>> > >> The easy fix is this.... just replace "G193" on the command
line with
>> > the
>> > >> path to a 1/4 degree GFS GRIB2 file. Here's a selection from
the
>> usage
>> > >> statement for regrid_data_plane:
>> > >>
>> > >> Usage: regrid_data_plane
>> > >> input_filename
>> > >> to_grid
>> > >> output_filename
>> > >> "to_grid" defines the output grid as a named
grid,
>> the
>> > >> path
>> > >> to a gridded data file, or an explicit grid specification
string
>> > >> (required).
>> > >>
>> > >> When you set "to_grid" equal to a gridded data file, MET reads
the
>> grid
>> > >> definition from the first record of that file and uses it.
>> > >>
>> > >> That should do it.
>> > >>
>> > >> Thanks,
>> > >> John
>> > >>
>> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA
Affiliate
>> via
>> > >> RT <
>> > >> met_help at ucar.edu> wrote:
>> > >>
>> > >> >
>> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>> > >> >
>> > >> > Hi John,
>> > >> >
>> > >> > I'm really not having much luck today with this. Maybe I
should
>> have
>> > >> > stayed in bed (haha).
>> > >> >
>> > >> > So, the first thing I did was check the LD_LIBRARY_PATH, and
it's
>> > >> pointing
>> > >> > to the MET7 directories. Ok, that could be most of the
problem.
>> MET7
>> > >> seems
>> > >> > to be having some issue, and the guy here at OPC that helps
me with
>> > that
>> > >> > stuff (Chris Juckins) is out on leave until tomorrow.
Anyway,
>> MET7 is
>> > >> not
>> > >> > running any of my verification programs, and giving out some
>> errors,
>> > so,
>> > >> > I'll have to get with him tomorrow to fix that.
>> > >> >
>> > >> > So, in the mean time, I don't think that any kind of land
mask
>> > creation
>> > >> > that I'm doing today will work because it's not pointing at
the
>> right
>> > >> > directories.
>> > >> >
>> > >> > But, when I do get this to work, I tried this and got this
error:
>> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
gwes01.glo_30m.t00z.grib2
>> G193
>> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
>> > >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
>> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321
lat_ll:
>> > -80.000
>> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
>> > >> > ERROR :
>> > >> > ERROR : grd_file_type() -> file does not exist "G193"
>> > >> > ERROR :
>> > >> >
>> > >> > I'm wondering if that's all related to MET7.
>> > >> >
>> > >> > So, I think I need to fix the MET7 issue before moving on
with
>> this,
>> > >> don't
>> > >> > you?
>> > >> >
>> > >> > Roz
>> > >> >
>> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT <
>> > >> > met_help at ucar.edu
>> > >> > > wrote:
>> > >> >
>> > >> > > Roz,
>> > >> > >
>> > >> > > OK, one other possible option to consider. I figured that
>> there's
>> > >> plenty
>> > >> > > of "ocean" products out there. So I found a NOAA
WAVEWATCH one:
>> > >> > >
>> > >> > > (1) Download sample wavewatch file:
>> > >> > > wget
>> > >> > > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
>> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
>> > >> > >
>> > >> > > (2) Run regrid_data_plane to put some surface wind speed
data on
>> the
>> > >> 1/4
>> > >> > > GFS grid:
>> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
>> ocean_data.nc
>> > >> -field
>> > >> > > 'name="WIND"; level="L0";'
>> > >> > >
>> > >> > > (3) Run gen_vx_mask to select points that contain valid
data:
>> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc
-type
>> data
>> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-9999
-name
>> > OCEAN
>> > >> > >
>> > >> > > (4) Run plot_data_plane to see the result:
>> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
'name="OCEAN";
>> > >> > > level="(*,*)";'
>> > >> > >
>> > >> > > As you can see, the result gets rid of the lakes problem.
But
>> > >> wavewatch
>> > >> > is
>> > >> > > only run to +/- 80 degrees, so we're not including points
near
>> the
>> > >> poles.
>> > >> > >
>> > >> > > Figured this would be a lot easier than running WPS
yourself.
>> > >> > >
>> > >> > > Thanks,
>> > >> > > John
>> > >> > >
>> > >> > >
>> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <
>> johnhg at ucar.edu>
>> > >> > wrote:
>> > >> > >
>> > >> > > > Roz,
>> > >> > > >
>> > >> > > > I talked to some folks and have one suggestion that
*might*
>> work.
>> > >> The
>> > >> > > WRF
>> > >> > > > Pre-processing system is named WPS. The geogrid program
within
>> > WPS
>> > >> is
>> > >> > > used
>> > >> > > > to initialize your domain and handles land use
information. By
>> > >> > default,
>> > >> > > > lakes and oceans are treated the same way. However,
apparently
>> > >> there
>> > >> > is
>> > >> > > an
>> > >> > > > option to distinguish between them. Take a look here:
>> > >> > > >
>> > >> > > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
>> > >> > > users_guide_chap3.htm#_Description_of_the_1
>> > >> > > >
>> > >> > > > And search for "Alternative Initialization of Lake
SSTs".
>> > >> > > >
>> > >> > > > So you'd...
>> > >> > > > (1) download the MODIS SST data
>> > >> > > > (2) configure geogrid for the 0.25 degree GFS grid
>> > >> > > > (3) configure geogrid to distinguish between lakes and
oceans
>> > >> > > > (4) run geogrid
>> > >> > > > (5) run the output through the MET gen_vx_mask tool to
use
>> ocean
>> > >> values
>> > >> > > > and skip the lake values
>> > >> > > >
>> > >> > > > Thanks,
>> > >> > > > John
>> > >> > > >
>> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <
>> > johnhg at ucar.edu>
>> > >> > > wrote:
>> > >> > > >
>> > >> > > >> Roz,
>> > >> > > >>
>> > >> > > >> Whenever you see that error about loading shared
libraries, it
>> > >> means
>> > >> > > that
>> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
environment
>> > variable
>> > >> is
>> > >> > > set.
>> > >> > > >> That environment variable tells the linker where to
look for
>> > shared
>> > >> > > >> libraries at runtime... one of those shared libraries
is GSL
>> (GNU
>> > >> > > >> Scientific Library). You'd "fix" this issue by
modifying how
>> > >> > > >> LD_LIBRARY_PATH is set:
>> > >> > > >> echo $LD_LIBRARY_PATH
>> > >> > > >>
>> > >> > > >> Take a look in your ~/.cshrc file for c-shell or
~/.bashrc for
>> > >> bash to
>> > >> > > >> see how its set.
>> > >> > > >>
>> > >> > > >> As for the LAND/SEA mask, I was wondering if those
lakes would
>> > be a
>> > >> > > >> problem. Using the model's LAND/SEA mask is the
easiest, but
>> > >> doesn't
>> > >> > > >> provide an easy way of selecting out oceans. My next
thought
>> was
>> > >> to
>> > >> > use
>> > >> > > >> GIS Shapefiles to define only the ocean area. That
will be
>> > >> available
>> > >> > in
>> > >> > > >> the next version of MET, version 7.1. I tried using a
beta
>> > release
>> > >> > for
>> > >> > > >> met-7.1, but ran into problems when applying large
polylines
>> to
>> > >> global
>> > >> > > >> grids.
>> > >> > > >>
>> > >> > > >> I'll keep thinking about that one.
>> > >> > > >>
>> > >> > > >> Thanks,
>> > >> > > >> John
>> > >> > > >>
>> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken -
NOAA
>> > Affiliate
>> > >> > via
>> > >> > > >> RT <met_help at ucar.edu> wrote:
>> > >> > > >>
>> > >> > > >>>
>> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
>> ket/Display.html?id=86091 >
>> > >> > > >>>
>> > >> > > >>> Hey John,
>> > >> > > >>>
>> > >> > > >>> I have 2 problems. First, I'm able to use
plot_data_plane,
>> but,
>> > >> > when I
>> > >> > > >>> use
>> > >> > > >>> the command for gen_vx_mask, I get this:
>> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
gfs.t00z.pgrb2.0p25.f000
>> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type
data
>> > >> -mask_field
>> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
>> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while loading
shared
>> > >> > > libraries:
>> > >> > > >>> libgsl.so.0: cannot open shared object file: No such
file or
>> > >> > directory
>> > >> > > >>>
>> > >> > > >>> Now, they are both in the same directory, and I know
that
>> I've
>> > >> used
>> > >> > > >>> gen_vx_mask before, so, I have no idea why I would be
getting
>> > that
>> > >> > > error
>> > >> > > >>> message. Any ideas?
>> > >> > > >>>
>> > >> > > >>> Then, I was able to generate a *.ps file, which looks
exactly
>> > like
>> > >> > > yours,
>> > >> > > >>> but, there is still the same problem. If you look
closely
>> are
>> > >> your
>> > >> > > map,
>> > >> > > >>> you'll see these little white dots over land. Those
are
>> lakes,
>> > >> and
>> > >> > > >>> that's
>> > >> > > >>> what is giving me a fit, because I have ASCAT
observations
>> over
>> > >> those
>> > >> > > >>> white
>> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data with 12
km ASCAT
>> > >> > > data...so,
>> > >> > > >>> very sensitive. Anyway, do you have any idea how to
get rid
>> of
>> > >> those
>> > >> > > >>> points? Perhaps a different file with the same
domain?
>> > >> > > >>>
>> > >> > > >>> Roz
>> > >> > > >>>
>> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken -
NOAA
>> > >> Affiliate <
>> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
>> > >> > > >>>
>> > >> > > >>> > Ok, I'll let you know if I can get the mask to work.
This
>> > seems
>> > >> > easy
>> > >> > > >>> > enough, and pretty straight forward.
>> > >> > > >>> >
>> > >> > > >>> > Thanks for the help!
>> > >> > > >>> >
>> > >> > > >>> > Roz
>> > >> > > >>> >
>> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway
via RT <
>> > >> > > >>> > met_help at ucar.edu> wrote:
>> > >> > > >>> >
>> > >> > > >>> >> Roz,
>> > >> > > >>> >>
>> > >> > > >>> >> Yes, I expect that using met-6.0 would work fine.
Hope it
>> > goes
>> > >> > > >>> smoothly.
>> > >> > > >>> >>
>> > >> > > >>> >> Thanks,
>> > >> > > >>> >> John
>> > >> > > >>> >>
>> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn MacCracken -
NOAA
>> > >> Affiliate
>> > >> > > >>> via RT
>> > >> > > >>> >> <
>> > >> > > >>> >> met_help at ucar.edu> wrote:
>> > >> > > >>> >>
>> > >> > > >>> >> >
>> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
>> > >> ket/Display.html?id=86091 >
>> > >> > > >>> >> >
>> > >> > > >>> >> > Hi John,
>> > >> > > >>> >> >
>> > >> > > >>> >> > I get the general idea and it looks pretty
straight
>> > forward.
>> > >> > I'm
>> > >> > > >>> still
>> > >> > > >>> >> > running MET6.0, since we had some installation
issues,
>> > but, I
>> > >> > > >>> should be
>> > >> > > >>> >> > able to generate the mask with that pretty
easily,
>> correct?
>> > >> > > >>> >> >
>> > >> > > >>> >> > So, if this works, I'll need to rerun all my data
from
>> Mar
>> > >> 2018
>> > >> > -
>> > >> > > >>> >> present,
>> > >> > > >>> >> > using that method that we worked out earlier with
the
>> > *.stat
>> > >> > > files,
>> > >> > > >>> >> > correct? Actually, I don't need to do that...I
can
>> start
>> > >> from
>> > >> > the
>> > >> > > >>> ASCII
>> > >> > > >>> >> > files I've already generated, and then just rerun
>> > POINT_STAT
>> > >> > with
>> > >> > > >>> the
>> > >> > > >>> >> > mask. Ok, that will save some steps.
>> > >> > > >>> >> >
>> > >> > > >>> >> > Alright, I'll try making the mask and do a test
run
>> after
>> > >> lunch,
>> > >> > > >>> and get
>> > >> > > >>> >> > back to you when it works.
>> > >> > > >>> >> >
>> > >> > > >>> >> > Thanks!
>> > >> > > >>> >> >
>> > >> > > >>> >> > Roz
>> > >> > > >>> >> >
>> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley
Gotway via
>> RT <
>> > >> > > >>> >> > met_help at ucar.edu
>> > >> > > >>> >> > > wrote:
>> > >> > > >>> >> >
>> > >> > > >>> >> > > Hi Roz,
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > I see you're wondering how to only use point
>> observations
>> > >> over
>> > >> > > >>> water
>> > >> > > >>> >> and
>> > >> > > >>> >> > > discard the ones over land. You're running
ASCII2NC
>> > >> followed
>> > >> > by
>> > >> > > >>> >> > Point-Stat
>> > >> > > >>> >> > > and want to know where/how to define that
masking.
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > The ASCII2NC tool supports 3 command line
options for
>> > >> > filtering
>> > >> > > >>> point
>> > >> > > >>> >> > > observations spatially: -mask_grid, -mask_poly,
and
>> > >> -mask_sid,
>> > >> > > for
>> > >> > > >>> >> grid,
>> > >> > > >>> >> > > polyline, and station ID masking, respectively.
But
>> > that's
>> > >> > not
>> > >> > > >>> really
>> > >> > > >>> >> > what
>> > >> > > >>> >> > > you want. You want to do "data masking" where
you
>> read
>> > in
>> > >> a
>> > >> > > >>> land/sea
>> > >> > > >>> >> > mask
>> > >> > > >>> >> > > and only use the points over water.
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to
create
>> the
>> > >> > desired
>> > >> > > >>> >> masking
>> > >> > > >>> >> > > region, and then reference that in the Point-
Stat
>> config
>> > >> file.
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > To illustrate, I pulled a sample GFS file:
>> > >> > > >>> >> > > > wget
>> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
>> > >> ata/gfs4/201807/20180702/gfs_
>> > >> > > >>> >> > > 4_20180702_0000_012.grb2
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
>> > >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 | egrep
-i
>> LAND
>> > >> > > >>> >> > > 400:65422867:d=2018070200:LAND:surface:12
hour
>> > fcst:
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > Run plot_data_plane to see it (see attached
image):
>> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
>> > >> gfs_4_20180702_0000_012.grb2
>> > >> > > >>> >> > gfs_4_LAND.ps
>> > >> > > >>> >> > > 'name="LAND"; level="L0";'
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > Run gen_vx_mask to create a mask for your
verification
>> > >> domain.
>> > >> > > If
>> > >> > > >>> >> you're
>> > >> > > >>> >> > > actually verifying on the GFS domain, the
command
>> looks a
>> > >> > little
>> > >> > > >>> >> > redundant:
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
>> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
>> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
>> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
>> > >> > > >>> >> > > -type data \
>> > >> > > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
>> > >> > > >>> >> > > -thresh ==0 \
>> > >> > > >>> >> > > -name WATER
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > I defined the threshold as "==0" because we
want the
>> > WATER
>> > >> > > >>> points, not
>> > >> > > >>> >> > the
>> > >> > > >>> >> > > LAND points. And I used the "-name WATER"
command
>> line
>> > >> option
>> > >> > > to
>> > >> > > >>> name
>> > >> > > >>> >> > the
>> > >> > > >>> >> > > output NetCDF variable. This will show up in
the
>> VX_MASK
>> > >> > output
>> > >> > > >>> >> column
>> > >> > > >>> >> > of
>> > >> > > >>> >> > > Point-Stat.
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > Lastly, setup your Point-Stat config file like
this:
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > mask = {
>> > >> > > >>> >> > > grid = [];
>> > >> > > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc"
];
>> > >> > > >>> >> > > sid = [];
>> > >> > > >>> >> > > }
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > Hope that helps clarify.
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > Thanks,
>> > >> > > >>> >> > > John
>> > >> > > >>> >> > >
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
MacCracken -
>> NOAA
>> > >> > > >>> Affiliate via
>> > >> > > >>> >> > RT <
>> > >> > > >>> >> > > met_help at ucar.edu> wrote:
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was
acted
>> upon.
>> > >> > > >>> >> > > > Transaction: Ticket created by
>> > >> rosalyn.maccracken at noaa.gov
>> > >> > > >>> >> > > > Queue: met_help
>> > >> > > >>> >> > > > Subject: masking land features questions
>> > >> > > >>> >> > > > Owner: Nobody
>> > >> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
>> > >> > > >>> >> > > > Status: new
>> > >> > > >>> >> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
>> > >> > > >>> >> ket/Display.html?id=86091
>> > >> > > >>> >> > >
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > Hi,
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > I'm using ASCAT data to verify the GFS. I
only
>> want to
>> > >> > verify
>> > >> > > >>> >> points
>> > >> > > >>> >> > > over
>> > >> > > >>> >> > > > the ocean, and not over any inland lakes. I
noticed
>> > >> that I
>> > >> > > was
>> > >> > > >>> >> getting
>> > >> > > >>> >> > > > matched points over land (mostly Africa).
I'm
>> dumping
>> > >> out
>> > >> > the
>> > >> > > >>> >> MGDRlite
>> > >> > > >>> >> > > > file to an ascii file, which I use ASCII2NC
to
>> create
>> > the
>> > >> > > netCDF
>> > >> > > >>> >> file,
>> > >> > > >>> >> > > and
>> > >> > > >>> >> > > > then go on to use Point_stat to create
statistics
>> for
>> > the
>> > >> > > >>> matched
>> > >> > > >>> >> > points.
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > How do I mask out points over land before it
gets to
>> > the
>> > >> > > >>> Point_stat
>> > >> > > >>> >> > step?
>> > >> > > >>> >> > > > Is there something in the ASCII2NC processing
that I
>> > can
>> > >> > add,
>> > >> > > >>> so I
>> > >> > > >>> >> > don't
>> > >> > > >>> >> > > > get these matched points?
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > Thanks in advance!
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > Roz
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > --
>> > >> > > >>> >> > > > Rosalyn MacCracken
>> > >> > > >>> >> > > > Support Scientist
>> > >> > > >>> >> > > >
>> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Thu Jul 12 12:55:54 2018
Roz,
Yes, that's correct. You'd list that new land mask in the Point-Stat
config file to control which points are included.
If I remember correctly, you're running some STAT-Analysis jobs to
aggregate MPR lines from previous runs of Point-Stat. And that's the
problem, that STAT-Analysis cannot use the output of gen_vx_mask to
control
which MPR lines should be included. Here are two possibilities for
solving
this problem:
(1) The MPR line contains a column named OBS_SID which is the name of
the
station. If you can, through some means, identify the names of the
stations that you *DO* want to use, you could write them out to an
ASCII
file. Then when you run STAT-Analysis jobs, you could use the "-
mask_sid"
option to tell it the names of the stations to be included. I haven't
done
this for large numbers of stations. In principle, the logic should
work.
In practice, it may be a little slow, checking that long list of
stations
many times.
(2) We have been doing active development for the next MET release.
As we
add new features, we've been building beta releases and building them
on
NOAA machines (theia, jet, wcoss) for NOAA folks to test out. The
current
development version is named met-7.1_beta6. I could elevate the
priority
of that development ticket I sent to you, and enhance stat-analysis to
define masking regions using the output of gen_vx_mask. And then I
could
include it in the next beta release for you to test out. That would
certainly be easier for you than generating a list of stations to use.
But
it would take a week or two to get you a new beta release to test out.
If you decided to go with (1), let me know. I have a suggestion for
how
you might generate that list of stations to include.
Thanks,
John
On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
> Oh, but, I can incorporate this new land mask from here on out,
right? And,
> I would add that to my Point-stat config file, like you showed me to
do in
> the previous email, correct?
>
> Roz
>
> On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA Affiliate
<
> rosalyn.maccracken at noaa.gov> wrote:
>
> > Hi John,
> >
> > There's got to be a way around this...I'm sure there is a work
around so
> > that I don't have to go back an get all of the GFS files. And, I
know
> that
> > I want to use STAT-Analysis, since I already have all that in
place to
> > regenerate data.
> >
> > So, you said I can use a lat/lon polyline file with STAT-Analysis.
Of
> > course, I already use that with my North Atlantic or North Pacific
masks.
> > So, my first option might be, make my North Atlantic mask smaller,
not to
> > include West Africa, where the bad observations are located, and
don't
> use
> > the global file that is generated (if there a way not to make that
file,
> > and only re-generate files for the North Atlantic?). Ok...that's
one
> > option, and that's probably what I will have to do.
> >
> > Here's the question. So, let's say there was a way for us to go
back
> > through our ASCAT data, and identify lat/lons of observations that
were
> > flagged not to use, or over land, is there a way to have STAT-
Analysis
> > discard matched pairs associated with those lat/lons? Maybe,
that's like
> > using the lat/lon ployline file in reverse? Here's the mask, use
all
> > observations except if it falls inside this masked domain? Can we
do
> that?
> >
> > Roz
> >
> >
> >
> > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Roz,
> >>
> >> Bad news. I had hoped we could simply pass in the gridded mask
file
> >> you've
> >> defined as input to STAT-Analysis using "-mask_poly" but
unfortunately
> >> that
> >> doesn't work.
> >>
> >> STAT-Analysis currently supports: -mask_grid, -mask_poly, and
-mask_sid
> to
> >> filter MPR lines by a named grid, polyline file, or list of
station id
> >> names. The other MET tools, like Point-Stat and Grid-Stat also
support
> >> multiple masking options.
> >>
> >> For example, in Point-Stat:
> >> mask = {
> >> grid = [ "FULL" ];
> >> poly = [];
> >> sid = [];
> >> }
> >>
> >> The "mask.grid" option in Point-Stat is the same of "-mask_grid"
in
> >> STAT-Analysis. They both process named grids, like "G212" for
NCEP grid
> >> number 212.
> >>
> >> Likewise, the "mask.sid" option is the same as "-mask_sid". They
both
> >> define lists of station ID names to be included.
> >>
> >> *BUT* the "mask.poly" option in Point-Stat is much more flexible
than
> >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can only be
set to
> a
> >> lat/lon polyline file. In Point-Stat, it can also be set to the
output
> of
> >> gen_vx_mask or any gridded data file followed by a description of
data
> to
> >> be extracted and thresholded.
> >>
> >> We actually have a development task already defined to address
this
> issue
> >> (see attached).
> >>
> >> But that doesn't help you. So unfortunately, with met-7.0, you'd
would
> >> need to go all the way back to generating pairs with Point-Stat.
> >>
> >> However, if you were using a future version of MET, you could do
this
> all
> >> in STAT-Analysis.
> >>
> >> Thanks,
> >> John
> >>
> >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA
Affiliate via
> >> RT <
> >> met_help at ucar.edu> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >> >
> >> > Hi John,
> >> >
> >> > Well, good news. We got our MET7 to work, and I was able to
create my
> >> > ocean mask. It was an issue with conflicts in our libraries,
and the
> >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> >> >
> >> > Now, I have this ocean mask, and now I can go back and rerun my
data.
> >> So,
> >> > as usual, I had some questions.
> >> >
> >> > I have a series of scripts where you helped me set up
STATanalysis to
> >> > reprocess the data using the *.stat files and the -job
aggregate_stat
> >> > command . Will I be able to use this method again, or, because
it's
> >> > applying a mask, will I need to get the raw data (GFS and ASCAT
data)?
> >> > And, I guess if I have to use the raw data, I will have to
start with
> >> > ASCII2NC, etc, as if I'm processing from scratch, correct?
> >> >
> >> > I just need a sense of how big of a job this is....
> >> >
> >> > Thanks for your help!
> >> >
> >> > Roz
> >> >
> >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA
Affiliate <
> >> > rosalyn.maccracken at noaa.gov> wrote:
> >> >
> >> > > Oh, yeah, nothing seems to be going smoothly today...anyway,
I
> think I
> >> > > need to wait until Chris and Fran come in tomorrow to set our
> >> directories
> >> > > correctly to point at MET, and get it running again before I
do
> >> anything
> >> > > else.
> >> > >
> >> > > I'll try this again tomorrow and let you know how I do.
> >> > >
> >> > > Thanks for your help!
> >> > >
> >> > > Roz
> >> > >
> >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT <
> >> > > met_help at ucar.edu> wrote:
> >> > >
> >> > >> Roz,
> >> > >>
> >> > >> Sorry you're having a rough day. No worries though, this
issue is
> >> easy
> >> > to
> >> > >> overcome. Here's a list of pre-defined NCEP grids:
> >> > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> >> > >>
> >> > >> The intention in MET is to support them using the naming
convention
> >> G###
> >> > >> where ### is the 3 digit grid number. But if you look
closely on
> >> that
> >> > >> website, you'll see that grid 193 is a relatively new one
and is
> >> listed
> >> > in
> >> > >> red. That definition just doesn't exist in MET version 6.0.
> >> > >>
> >> > >> The easy fix is this.... just replace "G193" on the command
line
> with
> >> > the
> >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a selection
from the
> >> usage
> >> > >> statement for regrid_data_plane:
> >> > >>
> >> > >> Usage: regrid_data_plane
> >> > >> input_filename
> >> > >> to_grid
> >> > >> output_filename
> >> > >> "to_grid" defines the output grid as a named
grid,
> >> the
> >> > >> path
> >> > >> to a gridded data file, or an explicit grid specification
string
> >> > >> (required).
> >> > >>
> >> > >> When you set "to_grid" equal to a gridded data file, MET
reads the
> >> grid
> >> > >> definition from the first record of that file and uses it.
> >> > >>
> >> > >> That should do it.
> >> > >>
> >> > >> Thanks,
> >> > >> John
> >> > >>
> >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA
Affiliate
> >> via
> >> > >> RT <
> >> > >> met_help at ucar.edu> wrote:
> >> > >>
> >> > >> >
> >> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >> > >> >
> >> > >> > Hi John,
> >> > >> >
> >> > >> > I'm really not having much luck today with this. Maybe I
should
> >> have
> >> > >> > stayed in bed (haha).
> >> > >> >
> >> > >> > So, the first thing I did was check the LD_LIBRARY_PATH,
and it's
> >> > >> pointing
> >> > >> > to the MET7 directories. Ok, that could be most of the
problem.
> >> MET7
> >> > >> seems
> >> > >> > to be having some issue, and the guy here at OPC that
helps me
> with
> >> > that
> >> > >> > stuff (Chris Juckins) is out on leave until tomorrow.
Anyway,
> >> MET7 is
> >> > >> not
> >> > >> > running any of my verification programs, and giving out
some
> >> errors,
> >> > so,
> >> > >> > I'll have to get with him tomorrow to fix that.
> >> > >> >
> >> > >> > So, in the mean time, I don't think that any kind of land
mask
> >> > creation
> >> > >> > that I'm doing today will work because it's not pointing
at the
> >> right
> >> > >> > directories.
> >> > >> >
> >> > >> > But, when I do get this to work, I tried this and got this
error:
> >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
gwes01.glo_30m.t00z.grib2
> >> G193
> >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> >> > >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321
lat_ll:
> >> > -80.000
> >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> >> > >> > ERROR :
> >> > >> > ERROR : grd_file_type() -> file does not exist "G193"
> >> > >> > ERROR :
> >> > >> >
> >> > >> > I'm wondering if that's all related to MET7.
> >> > >> >
> >> > >> > So, I think I need to fix the MET7 issue before moving on
with
> >> this,
> >> > >> don't
> >> > >> > you?
> >> > >> >
> >> > >> > Roz
> >> > >> >
> >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via RT
<
> >> > >> > met_help at ucar.edu
> >> > >> > > wrote:
> >> > >> >
> >> > >> > > Roz,
> >> > >> > >
> >> > >> > > OK, one other possible option to consider. I figured
that
> >> there's
> >> > >> plenty
> >> > >> > > of "ocean" products out there. So I found a NOAA
WAVEWATCH
> one:
> >> > >> > >
> >> > >> > > (1) Download sample wavewatch file:
> >> > >> > > wget
> >> > >> > > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> >> > >> > >
> >> > >> > > (2) Run regrid_data_plane to put some surface wind speed
data
> on
> >> the
> >> > >> 1/4
> >> > >> > > GFS grid:
> >> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
> >> ocean_data.nc
> >> > >> -field
> >> > >> > > 'name="WIND"; level="L0";'
> >> > >> > >
> >> > >> > > (3) Run gen_vx_mask to select points that contain valid
data:
> >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc ocean_mask.nc
-type
> >> data
> >> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-
9999 -name
> >> > OCEAN
> >> > >> > >
> >> > >> > > (4) Run plot_data_plane to see the result:
> >> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
'name="OCEAN";
> >> > >> > > level="(*,*)";'
> >> > >> > >
> >> > >> > > As you can see, the result gets rid of the lakes
problem. But
> >> > >> wavewatch
> >> > >> > is
> >> > >> > > only run to +/- 80 degrees, so we're not including
points near
> >> the
> >> > >> poles.
> >> > >> > >
> >> > >> > > Figured this would be a lot easier than running WPS
yourself.
> >> > >> > >
> >> > >> > > Thanks,
> >> > >> > > John
> >> > >> > >
> >> > >> > >
> >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <
> >> johnhg at ucar.edu>
> >> > >> > wrote:
> >> > >> > >
> >> > >> > > > Roz,
> >> > >> > > >
> >> > >> > > > I talked to some folks and have one suggestion that
*might*
> >> work.
> >> > >> The
> >> > >> > > WRF
> >> > >> > > > Pre-processing system is named WPS. The geogrid
program
> within
> >> > WPS
> >> > >> is
> >> > >> > > used
> >> > >> > > > to initialize your domain and handles land use
information.
> By
> >> > >> > default,
> >> > >> > > > lakes and oceans are treated the same way. However,
> apparently
> >> > >> there
> >> > >> > is
> >> > >> > > an
> >> > >> > > > option to distinguish between them. Take a look here:
> >> > >> > > >
> >> > >> > > > http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> >> > >> > > users_guide_chap3.htm#_Description_of_the_1
> >> > >> > > >
> >> > >> > > > And search for "Alternative Initialization of Lake
SSTs".
> >> > >> > > >
> >> > >> > > > So you'd...
> >> > >> > > > (1) download the MODIS SST data
> >> > >> > > > (2) configure geogrid for the 0.25 degree GFS grid
> >> > >> > > > (3) configure geogrid to distinguish between lakes and
oceans
> >> > >> > > > (4) run geogrid
> >> > >> > > > (5) run the output through the MET gen_vx_mask tool to
use
> >> ocean
> >> > >> values
> >> > >> > > > and skip the lake values
> >> > >> > > >
> >> > >> > > > Thanks,
> >> > >> > > > John
> >> > >> > > >
> >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <
> >> > johnhg at ucar.edu>
> >> > >> > > wrote:
> >> > >> > > >
> >> > >> > > >> Roz,
> >> > >> > > >>
> >> > >> > > >> Whenever you see that error about loading shared
libraries,
> it
> >> > >> means
> >> > >> > > that
> >> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
environment
> >> > variable
> >> > >> is
> >> > >> > > set.
> >> > >> > > >> That environment variable tells the linker where to
look for
> >> > shared
> >> > >> > > >> libraries at runtime... one of those shared libraries
is GSL
> >> (GNU
> >> > >> > > >> Scientific Library). You'd "fix" this issue by
modifying
> how
> >> > >> > > >> LD_LIBRARY_PATH is set:
> >> > >> > > >> echo $LD_LIBRARY_PATH
> >> > >> > > >>
> >> > >> > > >> Take a look in your ~/.cshrc file for c-shell or
~/.bashrc
> for
> >> > >> bash to
> >> > >> > > >> see how its set.
> >> > >> > > >>
> >> > >> > > >> As for the LAND/SEA mask, I was wondering if those
lakes
> would
> >> > be a
> >> > >> > > >> problem. Using the model's LAND/SEA mask is the
easiest,
> but
> >> > >> doesn't
> >> > >> > > >> provide an easy way of selecting out oceans. My next
> thought
> >> was
> >> > >> to
> >> > >> > use
> >> > >> > > >> GIS Shapefiles to define only the ocean area. That
will be
> >> > >> available
> >> > >> > in
> >> > >> > > >> the next version of MET, version 7.1. I tried using
a beta
> >> > release
> >> > >> > for
> >> > >> > > >> met-7.1, but ran into problems when applying large
polylines
> >> to
> >> > >> global
> >> > >> > > >> grids.
> >> > >> > > >>
> >> > >> > > >> I'll keep thinking about that one.
> >> > >> > > >>
> >> > >> > > >> Thanks,
> >> > >> > > >> John
> >> > >> > > >>
> >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken -
NOAA
> >> > Affiliate
> >> > >> > via
> >> > >> > > >> RT <met_help at ucar.edu> wrote:
> >> > >> > > >>
> >> > >> > > >>>
> >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
> >> ket/Display.html?id=86091 >
> >> > >> > > >>>
> >> > >> > > >>> Hey John,
> >> > >> > > >>>
> >> > >> > > >>> I have 2 problems. First, I'm able to use
plot_data_plane,
> >> but,
> >> > >> > when I
> >> > >> > > >>> use
> >> > >> > > >>> the command for gen_vx_mask, I get this:
> >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
gfs.t00z.pgrb2.0p25.f000
> >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type
data
> >> > >> -mask_field
> >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while
loading
> shared
> >> > >> > > libraries:
> >> > >> > > >>> libgsl.so.0: cannot open shared object file: No such
file
> or
> >> > >> > directory
> >> > >> > > >>>
> >> > >> > > >>> Now, they are both in the same directory, and I know
that
> >> I've
> >> > >> used
> >> > >> > > >>> gen_vx_mask before, so, I have no idea why I would
be
> getting
> >> > that
> >> > >> > > error
> >> > >> > > >>> message. Any ideas?
> >> > >> > > >>>
> >> > >> > > >>> Then, I was able to generate a *.ps file, which
looks
> exactly
> >> > like
> >> > >> > > yours,
> >> > >> > > >>> but, there is still the same problem. If you look
closely
> >> are
> >> > >> your
> >> > >> > > map,
> >> > >> > > >>> you'll see these little white dots over land. Those
are
> >> lakes,
> >> > >> and
> >> > >> > > >>> that's
> >> > >> > > >>> what is giving me a fit, because I have ASCAT
observations
> >> over
> >> > >> those
> >> > >> > > >>> white
> >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data with 12
km
> ASCAT
> >> > >> > > data...so,
> >> > >> > > >>> very sensitive. Anyway, do you have any idea how to
get
> rid
> >> of
> >> > >> those
> >> > >> > > >>> points? Perhaps a different file with the same
domain?
> >> > >> > > >>>
> >> > >> > > >>> Roz
> >> > >> > > >>>
> >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken -
NOAA
> >> > >> Affiliate <
> >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> >> > >> > > >>>
> >> > >> > > >>> > Ok, I'll let you know if I can get the mask to
work.
> This
> >> > seems
> >> > >> > easy
> >> > >> > > >>> > enough, and pretty straight forward.
> >> > >> > > >>> >
> >> > >> > > >>> > Thanks for the help!
> >> > >> > > >>> >
> >> > >> > > >>> > Roz
> >> > >> > > >>> >
> >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley Gotway
via
> RT <
> >> > >> > > >>> > met_help at ucar.edu> wrote:
> >> > >> > > >>> >
> >> > >> > > >>> >> Roz,
> >> > >> > > >>> >>
> >> > >> > > >>> >> Yes, I expect that using met-6.0 would work fine.
Hope
> it
> >> > goes
> >> > >> > > >>> smoothly.
> >> > >> > > >>> >>
> >> > >> > > >>> >> Thanks,
> >> > >> > > >>> >> John
> >> > >> > > >>> >>
> >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn MacCracken
- NOAA
> >> > >> Affiliate
> >> > >> > > >>> via RT
> >> > >> > > >>> >> <
> >> > >> > > >>> >> met_help at ucar.edu> wrote:
> >> > >> > > >>> >>
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> >> > >> ket/Display.html?id=86091 >
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > Hi John,
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > I get the general idea and it looks pretty
straight
> >> > forward.
> >> > >> > I'm
> >> > >> > > >>> still
> >> > >> > > >>> >> > running MET6.0, since we had some installation
issues,
> >> > but, I
> >> > >> > > >>> should be
> >> > >> > > >>> >> > able to generate the mask with that pretty
easily,
> >> correct?
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > So, if this works, I'll need to rerun all my
data from
> >> Mar
> >> > >> 2018
> >> > >> > -
> >> > >> > > >>> >> present,
> >> > >> > > >>> >> > using that method that we worked out earlier
with the
> >> > *.stat
> >> > >> > > files,
> >> > >> > > >>> >> > correct? Actually, I don't need to do that...I
can
> >> start
> >> > >> from
> >> > >> > the
> >> > >> > > >>> ASCII
> >> > >> > > >>> >> > files I've already generated, and then just
rerun
> >> > POINT_STAT
> >> > >> > with
> >> > >> > > >>> the
> >> > >> > > >>> >> > mask. Ok, that will save some steps.
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > Alright, I'll try making the mask and do a test
run
> >> after
> >> > >> lunch,
> >> > >> > > >>> and get
> >> > >> > > >>> >> > back to you when it works.
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > Thanks!
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > Roz
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley
Gotway via
> >> RT <
> >> > >> > > >>> >> > met_help at ucar.edu
> >> > >> > > >>> >> > > wrote:
> >> > >> > > >>> >> >
> >> > >> > > >>> >> > > Hi Roz,
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > I see you're wondering how to only use point
> >> observations
> >> > >> over
> >> > >> > > >>> water
> >> > >> > > >>> >> and
> >> > >> > > >>> >> > > discard the ones over land. You're running
ASCII2NC
> >> > >> followed
> >> > >> > by
> >> > >> > > >>> >> > Point-Stat
> >> > >> > > >>> >> > > and want to know where/how to define that
masking.
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > The ASCII2NC tool supports 3 command line
options
> for
> >> > >> > filtering
> >> > >> > > >>> point
> >> > >> > > >>> >> > > observations spatially: -mask_grid,
-mask_poly, and
> >> > >> -mask_sid,
> >> > >> > > for
> >> > >> > > >>> >> grid,
> >> > >> > > >>> >> > > polyline, and station ID masking,
respectively. But
> >> > that's
> >> > >> > not
> >> > >> > > >>> really
> >> > >> > > >>> >> > what
> >> > >> > > >>> >> > > you want. You want to do "data masking"
where you
> >> read
> >> > in
> >> > >> a
> >> > >> > > >>> land/sea
> >> > >> > > >>> >> > mask
> >> > >> > > >>> >> > > and only use the points over water.
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool to
create
> >> the
> >> > >> > desired
> >> > >> > > >>> >> masking
> >> > >> > > >>> >> > > region, and then reference that in the Point-
Stat
> >> config
> >> > >> file.
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > To illustrate, I pulled a sample GFS file:
> >> > >> > > >>> >> > > > wget
> >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> >> > >> ata/gfs4/201807/20180702/gfs_
> >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> >> > >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 |
egrep -i
> >> LAND
> >> > >> > > >>> >> > >
400:65422867:d=2018070200:LAND:surface:12 hour
> >> > fcst:
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > Run plot_data_plane to see it (see attached
image):
> >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> >> > >> gfs_4_20180702_0000_012.grb2
> >> > >> > > >>> >> > gfs_4_LAND.ps
> >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > Run gen_vx_mask to create a mask for your
> verification
> >> > >> domain.
> >> > >> > > If
> >> > >> > > >>> >> you're
> >> > >> > > >>> >> > > actually verifying on the GFS domain, the
command
> >> looks a
> >> > >> > little
> >> > >> > > >>> >> > redundant:
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> >> > >> > > >>> >> > > -type data \
> >> > >> > > >>> >> > > -mask_field 'name="LAND"; level="L0";' \
> >> > >> > > >>> >> > > -thresh ==0 \
> >> > >> > > >>> >> > > -name WATER
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > I defined the threshold as "==0" because we
want the
> >> > WATER
> >> > >> > > >>> points, not
> >> > >> > > >>> >> > the
> >> > >> > > >>> >> > > LAND points. And I used the "-name WATER"
command
> >> line
> >> > >> option
> >> > >> > > to
> >> > >> > > >>> name
> >> > >> > > >>> >> > the
> >> > >> > > >>> >> > > output NetCDF variable. This will show up in
the
> >> VX_MASK
> >> > >> > output
> >> > >> > > >>> >> column
> >> > >> > > >>> >> > of
> >> > >> > > >>> >> > > Point-Stat.
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > Lastly, setup your Point-Stat config file
like this:
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > mask = {
> >> > >> > > >>> >> > > grid = [];
> >> > >> > > >>> >> > > poly = [ "/path/to/gfs_4_WATER_mask.nc"
];
> >> > >> > > >>> >> > > sid = [];
> >> > >> > > >>> >> > > }
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > Hope that helps clarify.
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > Thanks,
> >> > >> > > >>> >> > > John
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
MacCracken -
> >> NOAA
> >> > >> > > >>> Affiliate via
> >> > >> > > >>> >> > RT <
> >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091 was
acted
> >> upon.
> >> > >> > > >>> >> > > > Transaction: Ticket created by
> >> > >> rosalyn.maccracken at noaa.gov
> >> > >> > > >>> >> > > > Queue: met_help
> >> > >> > > >>> >> > > > Subject: masking land features
questions
> >> > >> > > >>> >> > > > Owner: Nobody
> >> > >> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> >> > >> > > >>> >> > > > Status: new
> >> > >> > > >>> >> > > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Tic
> >> > >> > > >>> >> ket/Display.html?id=86091
> >> > >> > > >>> >> > >
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > Hi,
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > I'm using ASCAT data to verify the GFS. I
only
> >> want to
> >> > >> > verify
> >> > >> > > >>> >> points
> >> > >> > > >>> >> > > over
> >> > >> > > >>> >> > > > the ocean, and not over any inland lakes.
I
> noticed
> >> > >> that I
> >> > >> > > was
> >> > >> > > >>> >> getting
> >> > >> > > >>> >> > > > matched points over land (mostly Africa).
I'm
> >> dumping
> >> > >> out
> >> > >> > the
> >> > >> > > >>> >> MGDRlite
> >> > >> > > >>> >> > > > file to an ascii file, which I use ASCII2NC
to
> >> create
> >> > the
> >> > >> > > netCDF
> >> > >> > > >>> >> file,
> >> > >> > > >>> >> > > and
> >> > >> > > >>> >> > > > then go on to use Point_stat to create
statistics
> >> for
> >> > the
> >> > >> > > >>> matched
> >> > >> > > >>> >> > points.
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > How do I mask out points over land before
it gets
> to
> >> > the
> >> > >> > > >>> Point_stat
> >> > >> > > >>> >> > step?
> >> > >> > > >>> >> > > > Is there something in the ASCII2NC
processing
> that I
> >> > can
> >> > >> > add,
> >> > >> > > >>> so I
> >> > >> > > >>> >> > don't
> >> > >> > > >>> >> > > > get these matched points?
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > Thanks in advance!
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > Roz
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > --
> >> > >> > > >>> >> > > > Rosalyn MacCracken
> >> > >> > > >>> >> > > > Support Scientist
> >> > >> > > >>> >> > > >
> >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Fri Jul 13 12:08:28 2018
Hi John,
Yeah, I don't know if either solution is going to work. There isn't
any
OBS_ID associated with the observation, but, more like a flag in the
original ASCAT data file. I wouldn't even begin to know how to figure
out
how to translate that into a station id.
Oh, and I can't just change the mask and rerun stat-analysis. I would
need
to rerun point-stat, and now I'm back to square one...
So, there is no way to designate a new box to input into the
stat-analysis? You know, like you can indicate the wind speed
threshold...maybe something similar with the lat/lon? Guess not...
Roz
On Thu, Jul 12, 2018 at 2:55 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> Yes, that's correct. You'd list that new land mask in the Point-
Stat
> config file to control which points are included.
>
> If I remember correctly, you're running some STAT-Analysis jobs to
> aggregate MPR lines from previous runs of Point-Stat. And that's
the
> problem, that STAT-Analysis cannot use the output of gen_vx_mask to
control
> which MPR lines should be included. Here are two possibilities for
solving
> this problem:
>
> (1) The MPR line contains a column named OBS_SID which is the name
of the
> station. If you can, through some means, identify the names of the
> stations that you *DO* want to use, you could write them out to an
ASCII
> file. Then when you run STAT-Analysis jobs, you could use the "-
mask_sid"
> option to tell it the names of the stations to be included. I
haven't done
> this for large numbers of stations. In principle, the logic should
work.
> In practice, it may be a little slow, checking that long list of
stations
> many times.
>
> (2) We have been doing active development for the next MET release.
As we
> add new features, we've been building beta releases and building
them on
> NOAA machines (theia, jet, wcoss) for NOAA folks to test out. The
current
> development version is named met-7.1_beta6. I could elevate the
priority
> of that development ticket I sent to you, and enhance stat-analysis
to
> define masking regions using the output of gen_vx_mask. And then I
could
> include it in the next beta release for you to test out. That would
> certainly be easier for you than generating a list of stations to
use. But
> it would take a week or two to get you a new beta release to test
out.
>
> If you decided to go with (1), let me know. I have a suggestion for
how
> you might generate that list of stations to include.
>
> Thanks,
> John
>
> On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >
> > Oh, but, I can incorporate this new land mask from here on out,
right?
> And,
> > I would add that to my Point-stat config file, like you showed me
to do
> in
> > the previous email, correct?
> >
> > Roz
> >
> > On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > rosalyn.maccracken at noaa.gov> wrote:
> >
> > > Hi John,
> > >
> > > There's got to be a way around this...I'm sure there is a work
around
> so
> > > that I don't have to go back an get all of the GFS files. And,
I know
> > that
> > > I want to use STAT-Analysis, since I already have all that in
place to
> > > regenerate data.
> > >
> > > So, you said I can use a lat/lon polyline file with STAT-
Analysis. Of
> > > course, I already use that with my North Atlantic or North
Pacific
> masks.
> > > So, my first option might be, make my North Atlantic mask
smaller, not
> to
> > > include West Africa, where the bad observations are located, and
don't
> > use
> > > the global file that is generated (if there a way not to make
that
> file,
> > > and only re-generate files for the North Atlantic?).
Ok...that's one
> > > option, and that's probably what I will have to do.
> > >
> > > Here's the question. So, let's say there was a way for us to go
back
> > > through our ASCAT data, and identify lat/lons of observations
that were
> > > flagged not to use, or over land, is there a way to have STAT-
Analysis
> > > discard matched pairs associated with those lat/lons? Maybe,
that's
> like
> > > using the lat/lon ployline file in reverse? Here's the mask,
use all
> > > observations except if it falls inside this masked domain? Can
we do
> > that?
> > >
> > > Roz
> > >
> > >
> > >
> > > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> Roz,
> > >>
> > >> Bad news. I had hoped we could simply pass in the gridded mask
file
> > >> you've
> > >> defined as input to STAT-Analysis using "-mask_poly" but
unfortunately
> > >> that
> > >> doesn't work.
> > >>
> > >> STAT-Analysis currently supports: -mask_grid, -mask_poly, and
> -mask_sid
> > to
> > >> filter MPR lines by a named grid, polyline file, or list of
station id
> > >> names. The other MET tools, like Point-Stat and Grid-Stat also
> support
> > >> multiple masking options.
> > >>
> > >> For example, in Point-Stat:
> > >> mask = {
> > >> grid = [ "FULL" ];
> > >> poly = [];
> > >> sid = [];
> > >> }
> > >>
> > >> The "mask.grid" option in Point-Stat is the same of "-
mask_grid" in
> > >> STAT-Analysis. They both process named grids, like "G212" for
NCEP
> grid
> > >> number 212.
> > >>
> > >> Likewise, the "mask.sid" option is the same as "-mask_sid".
They both
> > >> define lists of station ID names to be included.
> > >>
> > >> *BUT* the "mask.poly" option in Point-Stat is much more
flexible than
> > >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can only
be set
> to
> > a
> > >> lat/lon polyline file. In Point-Stat, it can also be set to
the
> output
> > of
> > >> gen_vx_mask or any gridded data file followed by a description
of data
> > to
> > >> be extracted and thresholded.
> > >>
> > >> We actually have a development task already defined to address
this
> > issue
> > >> (see attached).
> > >>
> > >> But that doesn't help you. So unfortunately, with met-7.0,
you'd
> would
> > >> need to go all the way back to generating pairs with Point-
Stat.
> > >>
> > >> However, if you were using a future version of MET, you could
do this
> > all
> > >> in STAT-Analysis.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA
Affiliate
> via
> > >> RT <
> > >> met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
>
> > >> >
> > >> > Hi John,
> > >> >
> > >> > Well, good news. We got our MET7 to work, and I was able to
create
> my
> > >> > ocean mask. It was an issue with conflicts in our libraries,
and
> the
> > >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> > >> >
> > >> > Now, I have this ocean mask, and now I can go back and rerun
my
> data.
> > >> So,
> > >> > as usual, I had some questions.
> > >> >
> > >> > I have a series of scripts where you helped me set up
STATanalysis
> to
> > >> > reprocess the data using the *.stat files and the -job
> aggregate_stat
> > >> > command . Will I be able to use this method again, or,
because it's
> > >> > applying a mask, will I need to get the raw data (GFS and
ASCAT
> data)?
> > >> > And, I guess if I have to use the raw data, I will have to
start
> with
> > >> > ASCII2NC, etc, as if I'm processing from scratch, correct?
> > >> >
> > >> > I just need a sense of how big of a job this is....
> > >> >
> > >> > Thanks for your help!
> > >> >
> > >> > Roz
> > >> >
> > >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA
> Affiliate <
> > >> > rosalyn.maccracken at noaa.gov> wrote:
> > >> >
> > >> > > Oh, yeah, nothing seems to be going smoothly
today...anyway, I
> > think I
> > >> > > need to wait until Chris and Fran come in tomorrow to set
our
> > >> directories
> > >> > > correctly to point at MET, and get it running again before
I do
> > >> anything
> > >> > > else.
> > >> > >
> > >> > > I'll try this again tomorrow and let you know how I do.
> > >> > >
> > >> > > Thanks for your help!
> > >> > >
> > >> > > Roz
> > >> > >
> > >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT
<
> > >> > > met_help at ucar.edu> wrote:
> > >> > >
> > >> > >> Roz,
> > >> > >>
> > >> > >> Sorry you're having a rough day. No worries though, this
issue
> is
> > >> easy
> > >> > to
> > >> > >> overcome. Here's a list of pre-defined NCEP grids:
> > >> > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> > >> > >>
> > >> > >> The intention in MET is to support them using the naming
> convention
> > >> G###
> > >> > >> where ### is the 3 digit grid number. But if you look
closely on
> > >> that
> > >> > >> website, you'll see that grid 193 is a relatively new one
and is
> > >> listed
> > >> > in
> > >> > >> red. That definition just doesn't exist in MET version
6.0.
> > >> > >>
> > >> > >> The easy fix is this.... just replace "G193" on the
command line
> > with
> > >> > the
> > >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a selection
from the
> > >> usage
> > >> > >> statement for regrid_data_plane:
> > >> > >>
> > >> > >> Usage: regrid_data_plane
> > >> > >> input_filename
> > >> > >> to_grid
> > >> > >> output_filename
> > >> > >> "to_grid" defines the output grid as a
named
> grid,
> > >> the
> > >> > >> path
> > >> > >> to a gridded data file, or an explicit grid specification
string
> > >> > >> (required).
> > >> > >>
> > >> > >> When you set "to_grid" equal to a gridded data file, MET
reads
> the
> > >> grid
> > >> > >> definition from the first record of that file and uses it.
> > >> > >>
> > >> > >> That should do it.
> > >> > >>
> > >> > >> Thanks,
> > >> > >> John
> > >> > >>
> > >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA
> Affiliate
> > >> via
> > >> > >> RT <
> > >> > >> met_help at ucar.edu> wrote:
> > >> > >>
> > >> > >> >
> > >> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> >
> > >> > >> >
> > >> > >> > Hi John,
> > >> > >> >
> > >> > >> > I'm really not having much luck today with this. Maybe
I
> should
> > >> have
> > >> > >> > stayed in bed (haha).
> > >> > >> >
> > >> > >> > So, the first thing I did was check the LD_LIBRARY_PATH,
and
> it's
> > >> > >> pointing
> > >> > >> > to the MET7 directories. Ok, that could be most of the
> problem.
> > >> MET7
> > >> > >> seems
> > >> > >> > to be having some issue, and the guy here at OPC that
helps me
> > with
> > >> > that
> > >> > >> > stuff (Chris Juckins) is out on leave until tomorrow.
Anyway,
> > >> MET7 is
> > >> > >> not
> > >> > >> > running any of my verification programs, and giving out
some
> > >> errors,
> > >> > so,
> > >> > >> > I'll have to get with him tomorrow to fix that.
> > >> > >> >
> > >> > >> > So, in the mean time, I don't think that any kind of
land mask
> > >> > creation
> > >> > >> > that I'm doing today will work because it's not pointing
at the
> > >> right
> > >> > >> > directories.
> > >> > >> >
> > >> > >> > But, when I do get this to work, I tried this and got
this
> error:
> > >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
> gwes01.glo_30m.t00z.grib2
> > >> G193
> > >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> > >> > >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> > >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny: 321
> lat_ll:
> > >> > -80.000
> > >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> > >> > >> > ERROR :
> > >> > >> > ERROR : grd_file_type() -> file does not exist "G193"
> > >> > >> > ERROR :
> > >> > >> >
> > >> > >> > I'm wondering if that's all related to MET7.
> > >> > >> >
> > >> > >> > So, I think I need to fix the MET7 issue before moving
on with
> > >> this,
> > >> > >> don't
> > >> > >> > you?
> > >> > >> >
> > >> > >> > Roz
> > >> > >> >
> > >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via
RT <
> > >> > >> > met_help at ucar.edu
> > >> > >> > > wrote:
> > >> > >> >
> > >> > >> > > Roz,
> > >> > >> > >
> > >> > >> > > OK, one other possible option to consider. I figured
that
> > >> there's
> > >> > >> plenty
> > >> > >> > > of "ocean" products out there. So I found a NOAA
WAVEWATCH
> > one:
> > >> > >> > >
> > >> > >> > > (1) Download sample wavewatch file:
> > >> > >> > > wget
> > >> > >> > >
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> > >> > >> > >
> > >> > >> > > (2) Run regrid_data_plane to put some surface wind
speed data
> > on
> > >> the
> > >> > >> 1/4
> > >> > >> > > GFS grid:
> > >> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
> > >> ocean_data.nc
> > >> > >> -field
> > >> > >> > > 'name="WIND"; level="L0";'
> > >> > >> > >
> > >> > >> > > (3) Run gen_vx_mask to select points that contain
valid data:
> > >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc
ocean_mask.nc
> -type
> > >> data
> > >> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-
9999
> -name
> > >> > OCEAN
> > >> > >> > >
> > >> > >> > > (4) Run plot_data_plane to see the result:
> > >> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
> 'name="OCEAN";
> > >> > >> > > level="(*,*)";'
> > >> > >> > >
> > >> > >> > > As you can see, the result gets rid of the lakes
problem.
> But
> > >> > >> wavewatch
> > >> > >> > is
> > >> > >> > > only run to +/- 80 degrees, so we're not including
points
> near
> > >> the
> > >> > >> poles.
> > >> > >> > >
> > >> > >> > > Figured this would be a lot easier than running WPS
yourself.
> > >> > >> > >
> > >> > >> > > Thanks,
> > >> > >> > > John
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <
> > >> johnhg at ucar.edu>
> > >> > >> > wrote:
> > >> > >> > >
> > >> > >> > > > Roz,
> > >> > >> > > >
> > >> > >> > > > I talked to some folks and have one suggestion that
*might*
> > >> work.
> > >> > >> The
> > >> > >> > > WRF
> > >> > >> > > > Pre-processing system is named WPS. The geogrid
program
> > within
> > >> > WPS
> > >> > >> is
> > >> > >> > > used
> > >> > >> > > > to initialize your domain and handles land use
information.
> > By
> > >> > >> > default,
> > >> > >> > > > lakes and oceans are treated the same way. However,
> > apparently
> > >> > >> there
> > >> > >> > is
> > >> > >> > > an
> > >> > >> > > > option to distinguish between them. Take a look
here:
> > >> > >> > > >
> > >> > >> > > >
http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> > >> > >> > > users_guide_chap3.htm#_Description_of_the_1
> > >> > >> > > >
> > >> > >> > > > And search for "Alternative Initialization of Lake
SSTs".
> > >> > >> > > >
> > >> > >> > > > So you'd...
> > >> > >> > > > (1) download the MODIS SST data
> > >> > >> > > > (2) configure geogrid for the 0.25 degree GFS grid
> > >> > >> > > > (3) configure geogrid to distinguish between lakes
and
> oceans
> > >> > >> > > > (4) run geogrid
> > >> > >> > > > (5) run the output through the MET gen_vx_mask tool
to use
> > >> ocean
> > >> > >> values
> > >> > >> > > > and skip the lake values
> > >> > >> > > >
> > >> > >> > > > Thanks,
> > >> > >> > > > John
> > >> > >> > > >
> > >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <
> > >> > johnhg at ucar.edu>
> > >> > >> > > wrote:
> > >> > >> > > >
> > >> > >> > > >> Roz,
> > >> > >> > > >>
> > >> > >> > > >> Whenever you see that error about loading shared
> libraries,
> > it
> > >> > >> means
> > >> > >> > > that
> > >> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
environment
> > >> > variable
> > >> > >> is
> > >> > >> > > set.
> > >> > >> > > >> That environment variable tells the linker where to
look
> for
> > >> > shared
> > >> > >> > > >> libraries at runtime... one of those shared
libraries is
> GSL
> > >> (GNU
> > >> > >> > > >> Scientific Library). You'd "fix" this issue by
modifying
> > how
> > >> > >> > > >> LD_LIBRARY_PATH is set:
> > >> > >> > > >> echo $LD_LIBRARY_PATH
> > >> > >> > > >>
> > >> > >> > > >> Take a look in your ~/.cshrc file for c-shell or
~/.bashrc
> > for
> > >> > >> bash to
> > >> > >> > > >> see how its set.
> > >> > >> > > >>
> > >> > >> > > >> As for the LAND/SEA mask, I was wondering if those
lakes
> > would
> > >> > be a
> > >> > >> > > >> problem. Using the model's LAND/SEA mask is the
easiest,
> > but
> > >> > >> doesn't
> > >> > >> > > >> provide an easy way of selecting out oceans. My
next
> > thought
> > >> was
> > >> > >> to
> > >> > >> > use
> > >> > >> > > >> GIS Shapefiles to define only the ocean area. That
will
> be
> > >> > >> available
> > >> > >> > in
> > >> > >> > > >> the next version of MET, version 7.1. I tried
using a
> beta
> > >> > release
> > >> > >> > for
> > >> > >> > > >> met-7.1, but ran into problems when applying large
> polylines
> > >> to
> > >> > >> global
> > >> > >> > > >> grids.
> > >> > >> > > >>
> > >> > >> > > >> I'll keep thinking about that one.
> > >> > >> > > >>
> > >> > >> > > >> Thanks,
> > >> > >> > > >> John
> > >> > >> > > >>
> > >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken
- NOAA
> > >> > Affiliate
> > >> > >> > via
> > >> > >> > > >> RT <met_help at ucar.edu> wrote:
> > >> > >> > > >>
> > >> > >> > > >>>
> > >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
> > >> ket/Display.html?id=86091 >
> > >> > >> > > >>>
> > >> > >> > > >>> Hey John,
> > >> > >> > > >>>
> > >> > >> > > >>> I have 2 problems. First, I'm able to use
> plot_data_plane,
> > >> but,
> > >> > >> > when I
> > >> > >> > > >>> use
> > >> > >> > > >>> the command for gen_vx_mask, I get this:
> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
> gfs.t00z.pgrb2.0p25.f000
> > >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc -type
data
> > >> > >> -mask_field
> > >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name WATER
> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while
loading
> > shared
> > >> > >> > > libraries:
> > >> > >> > > >>> libgsl.so.0: cannot open shared object file: No
such file
> > or
> > >> > >> > directory
> > >> > >> > > >>>
> > >> > >> > > >>> Now, they are both in the same directory, and I
know that
> > >> I've
> > >> > >> used
> > >> > >> > > >>> gen_vx_mask before, so, I have no idea why I would
be
> > getting
> > >> > that
> > >> > >> > > error
> > >> > >> > > >>> message. Any ideas?
> > >> > >> > > >>>
> > >> > >> > > >>> Then, I was able to generate a *.ps file, which
looks
> > exactly
> > >> > like
> > >> > >> > > yours,
> > >> > >> > > >>> but, there is still the same problem. If you look
> closely
> > >> are
> > >> > >> your
> > >> > >> > > map,
> > >> > >> > > >>> you'll see these little white dots over land.
Those are
> > >> lakes,
> > >> > >> and
> > >> > >> > > >>> that's
> > >> > >> > > >>> what is giving me a fit, because I have ASCAT
> observations
> > >> over
> > >> > >> those
> > >> > >> > > >>> white
> > >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data with
12 km
> > ASCAT
> > >> > >> > > data...so,
> > >> > >> > > >>> very sensitive. Anyway, do you have any idea how
to get
> > rid
> > >> of
> > >> > >> those
> > >> > >> > > >>> points? Perhaps a different file with the same
domain?
> > >> > >> > > >>>
> > >> > >> > > >>> Roz
> > >> > >> > > >>>
> > >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn MacCracken
- NOAA
> > >> > >> Affiliate <
> > >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> > >> > >> > > >>>
> > >> > >> > > >>> > Ok, I'll let you know if I can get the mask to
work.
> > This
> > >> > seems
> > >> > >> > easy
> > >> > >> > > >>> > enough, and pretty straight forward.
> > >> > >> > > >>> >
> > >> > >> > > >>> > Thanks for the help!
> > >> > >> > > >>> >
> > >> > >> > > >>> > Roz
> > >> > >> > > >>> >
> > >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley
Gotway via
> > RT <
> > >> > >> > > >>> > met_help at ucar.edu> wrote:
> > >> > >> > > >>> >
> > >> > >> > > >>> >> Roz,
> > >> > >> > > >>> >>
> > >> > >> > > >>> >> Yes, I expect that using met-6.0 would work
fine.
> Hope
> > it
> > >> > goes
> > >> > >> > > >>> smoothly.
> > >> > >> > > >>> >>
> > >> > >> > > >>> >> Thanks,
> > >> > >> > > >>> >> John
> > >> > >> > > >>> >>
> > >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn
MacCracken -
> NOAA
> > >> > >> Affiliate
> > >> > >> > > >>> via RT
> > >> > >> > > >>> >> <
> > >> > >> > > >>> >> met_help at ucar.edu> wrote:
> > >> > >> > > >>> >>
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> > >> > >> ket/Display.html?id=86091 >
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > Hi John,
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > I get the general idea and it looks pretty
straight
> > >> > forward.
> > >> > >> > I'm
> > >> > >> > > >>> still
> > >> > >> > > >>> >> > running MET6.0, since we had some
installation
> issues,
> > >> > but, I
> > >> > >> > > >>> should be
> > >> > >> > > >>> >> > able to generate the mask with that pretty
easily,
> > >> correct?
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > So, if this works, I'll need to rerun all my
data
> from
> > >> Mar
> > >> > >> 2018
> > >> > >> > -
> > >> > >> > > >>> >> present,
> > >> > >> > > >>> >> > using that method that we worked out earlier
with
> the
> > >> > *.stat
> > >> > >> > > files,
> > >> > >> > > >>> >> > correct? Actually, I don't need to do
that...I can
> > >> start
> > >> > >> from
> > >> > >> > the
> > >> > >> > > >>> ASCII
> > >> > >> > > >>> >> > files I've already generated, and then just
rerun
> > >> > POINT_STAT
> > >> > >> > with
> > >> > >> > > >>> the
> > >> > >> > > >>> >> > mask. Ok, that will save some steps.
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > Alright, I'll try making the mask and do a
test run
> > >> after
> > >> > >> lunch,
> > >> > >> > > >>> and get
> > >> > >> > > >>> >> > back to you when it works.
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > Thanks!
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > Roz
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley
Gotway
> via
> > >> RT <
> > >> > >> > > >>> >> > met_help at ucar.edu
> > >> > >> > > >>> >> > > wrote:
> > >> > >> > > >>> >> >
> > >> > >> > > >>> >> > > Hi Roz,
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > I see you're wondering how to only use
point
> > >> observations
> > >> > >> over
> > >> > >> > > >>> water
> > >> > >> > > >>> >> and
> > >> > >> > > >>> >> > > discard the ones over land. You're running
> ASCII2NC
> > >> > >> followed
> > >> > >> > by
> > >> > >> > > >>> >> > Point-Stat
> > >> > >> > > >>> >> > > and want to know where/how to define that
masking.
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > The ASCII2NC tool supports 3 command line
options
> > for
> > >> > >> > filtering
> > >> > >> > > >>> point
> > >> > >> > > >>> >> > > observations spatially: -mask_grid,
-mask_poly,
> and
> > >> > >> -mask_sid,
> > >> > >> > > for
> > >> > >> > > >>> >> grid,
> > >> > >> > > >>> >> > > polyline, and station ID masking,
respectively.
> But
> > >> > that's
> > >> > >> > not
> > >> > >> > > >>> really
> > >> > >> > > >>> >> > what
> > >> > >> > > >>> >> > > you want. You want to do "data masking"
where you
> > >> read
> > >> > in
> > >> > >> a
> > >> > >> > > >>> land/sea
> > >> > >> > > >>> >> > mask
> > >> > >> > > >>> >> > > and only use the points over water.
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool
to
> create
> > >> the
> > >> > >> > desired
> > >> > >> > > >>> >> masking
> > >> > >> > > >>> >> > > region, and then reference that in the
Point-Stat
> > >> config
> > >> > >> file.
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > To illustrate, I pulled a sample GFS file:
> > >> > >> > > >>> >> > > > wget
> > >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> > >> > >> ata/gfs4/201807/20180702/gfs_
> > >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> > >> > >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 |
egrep -i
> > >> LAND
> > >> > >> > > >>> >> > >
400:65422867:d=2018070200:LAND:surface:12
> hour
> > >> > fcst:
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > Run plot_data_plane to see it (see attached
> image):
> > >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> > >> > >> gfs_4_20180702_0000_012.grb2
> > >> > >> > > >>> >> > gfs_4_LAND.ps
> > >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > Run gen_vx_mask to create a mask for your
> > verification
> > >> > >> domain.
> > >> > >> > > If
> > >> > >> > > >>> >> you're
> > >> > >> > > >>> >> > > actually verifying on the GFS domain, the
command
> > >> looks a
> > >> > >> > little
> > >> > >> > > >>> >> > redundant:
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> > >> > >> > > >>> >> > > -type data \
> > >> > >> > > >>> >> > > -mask_field 'name="LAND"; level="L0";'
\
> > >> > >> > > >>> >> > > -thresh ==0 \
> > >> > >> > > >>> >> > > -name WATER
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > I defined the threshold as "==0" because we
want
> the
> > >> > WATER
> > >> > >> > > >>> points, not
> > >> > >> > > >>> >> > the
> > >> > >> > > >>> >> > > LAND points. And I used the "-name WATER"
command
> > >> line
> > >> > >> option
> > >> > >> > > to
> > >> > >> > > >>> name
> > >> > >> > > >>> >> > the
> > >> > >> > > >>> >> > > output NetCDF variable. This will show up
in the
> > >> VX_MASK
> > >> > >> > output
> > >> > >> > > >>> >> column
> > >> > >> > > >>> >> > of
> > >> > >> > > >>> >> > > Point-Stat.
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > Lastly, setup your Point-Stat config file
like
> this:
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > mask = {
> > >> > >> > > >>> >> > > grid = [];
> > >> > >> > > >>> >> > > poly = [
"/path/to/gfs_4_WATER_mask.nc" ];
> > >> > >> > > >>> >> > > sid = [];
> > >> > >> > > >>> >> > > }
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > Hope that helps clarify.
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > Thanks,
> > >> > >> > > >>> >> > > John
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
MacCracken
> -
> > >> NOAA
> > >> > >> > > >>> Affiliate via
> > >> > >> > > >>> >> > RT <
> > >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091
was
> acted
> > >> upon.
> > >> > >> > > >>> >> > > > Transaction: Ticket created by
> > >> > >> rosalyn.maccracken at noaa.gov
> > >> > >> > > >>> >> > > > Queue: met_help
> > >> > >> > > >>> >> > > > Subject: masking land features
questions
> > >> > >> > > >>> >> > > > Owner: Nobody
> > >> > >> > > >>> >> > > > Requestors: rosalyn.maccracken at noaa.gov
> > >> > >> > > >>> >> > > > Status: new
> > >> > >> > > >>> >> > > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Tic
> > >> > >> > > >>> >> ket/Display.html?id=86091
> > >> > >> > > >>> >> > >
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > Hi,
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > I'm using ASCAT data to verify the GFS.
I only
> > >> want to
> > >> > >> > verify
> > >> > >> > > >>> >> points
> > >> > >> > > >>> >> > > over
> > >> > >> > > >>> >> > > > the ocean, and not over any inland lakes.
I
> > noticed
> > >> > >> that I
> > >> > >> > > was
> > >> > >> > > >>> >> getting
> > >> > >> > > >>> >> > > > matched points over land (mostly Africa).
I'm
> > >> dumping
> > >> > >> out
> > >> > >> > the
> > >> > >> > > >>> >> MGDRlite
> > >> > >> > > >>> >> > > > file to an ascii file, which I use
ASCII2NC to
> > >> create
> > >> > the
> > >> > >> > > netCDF
> > >> > >> > > >>> >> file,
> > >> > >> > > >>> >> > > and
> > >> > >> > > >>> >> > > > then go on to use Point_stat to create
> statistics
> > >> for
> > >> > the
> > >> > >> > > >>> matched
> > >> > >> > > >>> >> > points.
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > How do I mask out points over land before
it
> gets
> > to
> > >> > the
> > >> > >> > > >>> Point_stat
> > >> > >> > > >>> >> > step?
> > >> > >> > > >>> >> > > > Is there something in the ASCII2NC
processing
> > that I
> > >> > can
> > >> > >> > add,
> > >> > >> > > >>> so I
> > >> > >> > > >>> >> > don't
> > >> > >> > > >>> >> > > > get these matched points?
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > Thanks in advance!
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > Roz
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > --
> > >> > >> > > >>> >> > > > Rosalyn MacCracken
> > >> > >> > > >>> >> > > > Support Scientist
> > >> > >> > > >>> >> > > >
> > >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Fri Jul 13 12:51:58 2018
hi John,
Maybe I didn't ask the right question. Can I use the same formatted
mask
(polyline file with lat/lon), that I used for my point-stat mask, with
stat-analysis with new lat/lon coordinates in the vx_mask option? Or
does
it have to be the same set of coordinates that I used in the original
point-stat mask file?
Roz
On Fri, Jul 13, 2018 at 2:08 PM, Rosalyn MacCracken - NOAA Affiliate <
rosalyn.maccracken at noaa.gov> wrote:
> Hi John,
>
> Yeah, I don't know if either solution is going to work. There isn't
any
> OBS_ID associated with the observation, but, more like a flag in the
> original ASCAT data file. I wouldn't even begin to know how to
figure out
> how to translate that into a station id.
>
> Oh, and I can't just change the mask and rerun stat-analysis. I
would
> need to rerun point-stat, and now I'm back to square one...
>
> So, there is no way to designate a new box to input into the
> stat-analysis? You know, like you can indicate the wind speed
> threshold...maybe something similar with the lat/lon? Guess not...
>
> Roz
>
> On Thu, Jul 12, 2018 at 2:55 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Roz,
>>
>> Yes, that's correct. You'd list that new land mask in the Point-
Stat
>> config file to control which points are included.
>>
>> If I remember correctly, you're running some STAT-Analysis jobs to
>> aggregate MPR lines from previous runs of Point-Stat. And that's
the
>> problem, that STAT-Analysis cannot use the output of gen_vx_mask to
>> control
>> which MPR lines should be included. Here are two possibilities for
>> solving
>> this problem:
>>
>> (1) The MPR line contains a column named OBS_SID which is the name
of the
>> station. If you can, through some means, identify the names of the
>> stations that you *DO* want to use, you could write them out to an
ASCII
>> file. Then when you run STAT-Analysis jobs, you could use the "-
mask_sid"
>> option to tell it the names of the stations to be included. I
haven't
>> done
>> this for large numbers of stations. In principle, the logic should
work.
>> In practice, it may be a little slow, checking that long list of
stations
>> many times.
>>
>> (2) We have been doing active development for the next MET release.
As we
>> add new features, we've been building beta releases and building
them on
>> NOAA machines (theia, jet, wcoss) for NOAA folks to test out. The
current
>> development version is named met-7.1_beta6. I could elevate the
priority
>> of that development ticket I sent to you, and enhance stat-analysis
to
>> define masking regions using the output of gen_vx_mask. And then I
could
>> include it in the next beta release for you to test out. That
would
>> certainly be easier for you than generating a list of stations to
use.
>> But
>> it would take a week or two to get you a new beta release to test
out.
>>
>> If you decided to go with (1), let me know. I have a suggestion
for how
>> you might generate that list of stations to include.
>>
>> Thanks,
>> John
>>
>> On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA Affiliate
via
>> RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>> >
>> > Oh, but, I can incorporate this new land mask from here on out,
right?
>> And,
>> > I would add that to my Point-stat config file, like you showed me
to do
>> in
>> > the previous email, correct?
>> >
>> > Roz
>> >
>> > On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA
Affiliate <
>> > rosalyn.maccracken at noaa.gov> wrote:
>> >
>> > > Hi John,
>> > >
>> > > There's got to be a way around this...I'm sure there is a work
around
>> so
>> > > that I don't have to go back an get all of the GFS files. And,
I know
>> > that
>> > > I want to use STAT-Analysis, since I already have all that in
place to
>> > > regenerate data.
>> > >
>> > > So, you said I can use a lat/lon polyline file with STAT-
Analysis. Of
>> > > course, I already use that with my North Atlantic or North
Pacific
>> masks.
>> > > So, my first option might be, make my North Atlantic mask
smaller,
>> not to
>> > > include West Africa, where the bad observations are located,
and don't
>> > use
>> > > the global file that is generated (if there a way not to make
that
>> file,
>> > > and only re-generate files for the North Atlantic?).
Ok...that's one
>> > > option, and that's probably what I will have to do.
>> > >
>> > > Here's the question. So, let's say there was a way for us to
go back
>> > > through our ASCAT data, and identify lat/lons of observations
that
>> were
>> > > flagged not to use, or over land, is there a way to have STAT-
Analysis
>> > > discard matched pairs associated with those lat/lons? Maybe,
that's
>> like
>> > > using the lat/lon ployline file in reverse? Here's the mask,
use all
>> > > observations except if it falls inside this masked domain? Can
we do
>> > that?
>> > >
>> > > Roz
>> > >
>> > >
>> > >
>> > > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT <
>> > > met_help at ucar.edu> wrote:
>> > >
>> > >> Roz,
>> > >>
>> > >> Bad news. I had hoped we could simply pass in the gridded
mask file
>> > >> you've
>> > >> defined as input to STAT-Analysis using "-mask_poly" but
>> unfortunately
>> > >> that
>> > >> doesn't work.
>> > >>
>> > >> STAT-Analysis currently supports: -mask_grid, -mask_poly, and
>> -mask_sid
>> > to
>> > >> filter MPR lines by a named grid, polyline file, or list of
station
>> id
>> > >> names. The other MET tools, like Point-Stat and Grid-Stat
also
>> support
>> > >> multiple masking options.
>> > >>
>> > >> For example, in Point-Stat:
>> > >> mask = {
>> > >> grid = [ "FULL" ];
>> > >> poly = [];
>> > >> sid = [];
>> > >> }
>> > >>
>> > >> The "mask.grid" option in Point-Stat is the same of "-
mask_grid" in
>> > >> STAT-Analysis. They both process named grids, like "G212" for
NCEP
>> grid
>> > >> number 212.
>> > >>
>> > >> Likewise, the "mask.sid" option is the same as "-mask_sid".
They
>> both
>> > >> define lists of station ID names to be included.
>> > >>
>> > >> *BUT* the "mask.poly" option in Point-Stat is much more
flexible than
>> > >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can only
be set
>> to
>> > a
>> > >> lat/lon polyline file. In Point-Stat, it can also be set to
the
>> output
>> > of
>> > >> gen_vx_mask or any gridded data file followed by a description
of
>> data
>> > to
>> > >> be extracted and thresholded.
>> > >>
>> > >> We actually have a development task already defined to address
this
>> > issue
>> > >> (see attached).
>> > >>
>> > >> But that doesn't help you. So unfortunately, with met-7.0,
you'd
>> would
>> > >> need to go all the way back to generating pairs with Point-
Stat.
>> > >>
>> > >> However, if you were using a future version of MET, you could
do this
>> > all
>> > >> in STAT-Analysis.
>> > >>
>> > >> Thanks,
>> > >> John
>> > >>
>> > >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA
Affiliate
>> via
>> > >> RT <
>> > >> met_help at ucar.edu> wrote:
>> > >>
>> > >> >
>> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>> > >> >
>> > >> > Hi John,
>> > >> >
>> > >> > Well, good news. We got our MET7 to work, and I was able to
>> create my
>> > >> > ocean mask. It was an issue with conflicts in our
libraries, and
>> the
>> > >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
>> > >> >
>> > >> > Now, I have this ocean mask, and now I can go back and rerun
my
>> data.
>> > >> So,
>> > >> > as usual, I had some questions.
>> > >> >
>> > >> > I have a series of scripts where you helped me set up
STATanalysis
>> to
>> > >> > reprocess the data using the *.stat files and the -job
>> aggregate_stat
>> > >> > command . Will I be able to use this method again, or,
because
>> it's
>> > >> > applying a mask, will I need to get the raw data (GFS and
ASCAT
>> data)?
>> > >> > And, I guess if I have to use the raw data, I will have to
start
>> with
>> > >> > ASCII2NC, etc, as if I'm processing from scratch, correct?
>> > >> >
>> > >> > I just need a sense of how big of a job this is....
>> > >> >
>> > >> > Thanks for your help!
>> > >> >
>> > >> > Roz
>> > >> >
>> > >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA
>> Affiliate <
>> > >> > rosalyn.maccracken at noaa.gov> wrote:
>> > >> >
>> > >> > > Oh, yeah, nothing seems to be going smoothly
today...anyway, I
>> > think I
>> > >> > > need to wait until Chris and Fran come in tomorrow to set
our
>> > >> directories
>> > >> > > correctly to point at MET, and get it running again before
I do
>> > >> anything
>> > >> > > else.
>> > >> > >
>> > >> > > I'll try this again tomorrow and let you know how I do.
>> > >> > >
>> > >> > > Thanks for your help!
>> > >> > >
>> > >> > > Roz
>> > >> > >
>> > >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via RT
<
>> > >> > > met_help at ucar.edu> wrote:
>> > >> > >
>> > >> > >> Roz,
>> > >> > >>
>> > >> > >> Sorry you're having a rough day. No worries though, this
issue
>> is
>> > >> easy
>> > >> > to
>> > >> > >> overcome. Here's a list of pre-defined NCEP grids:
>> > >> > >>
http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
>> > >> > >>
>> > >> > >> The intention in MET is to support them using the naming
>> convention
>> > >> G###
>> > >> > >> where ### is the 3 digit grid number. But if you look
closely
>> on
>> > >> that
>> > >> > >> website, you'll see that grid 193 is a relatively new one
and is
>> > >> listed
>> > >> > in
>> > >> > >> red. That definition just doesn't exist in MET version
6.0.
>> > >> > >>
>> > >> > >> The easy fix is this.... just replace "G193" on the
command line
>> > with
>> > >> > the
>> > >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a selection
from
>> the
>> > >> usage
>> > >> > >> statement for regrid_data_plane:
>> > >> > >>
>> > >> > >> Usage: regrid_data_plane
>> > >> > >> input_filename
>> > >> > >> to_grid
>> > >> > >> output_filename
>> > >> > >> "to_grid" defines the output grid as a
named
>> grid,
>> > >> the
>> > >> > >> path
>> > >> > >> to a gridded data file, or an explicit grid specification
string
>> > >> > >> (required).
>> > >> > >>
>> > >> > >> When you set "to_grid" equal to a gridded data file, MET
reads
>> the
>> > >> grid
>> > >> > >> definition from the first record of that file and uses
it.
>> > >> > >>
>> > >> > >> That should do it.
>> > >> > >>
>> > >> > >> Thanks,
>> > >> > >> John
>> > >> > >>
>> > >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken - NOAA
>> Affiliate
>> > >> via
>> > >> > >> RT <
>> > >> > >> met_help at ucar.edu> wrote:
>> > >> > >>
>> > >> > >> >
>> > >> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
>> >
>> > >> > >> >
>> > >> > >> > Hi John,
>> > >> > >> >
>> > >> > >> > I'm really not having much luck today with this. Maybe
I
>> should
>> > >> have
>> > >> > >> > stayed in bed (haha).
>> > >> > >> >
>> > >> > >> > So, the first thing I did was check the
LD_LIBRARY_PATH, and
>> it's
>> > >> > >> pointing
>> > >> > >> > to the MET7 directories. Ok, that could be most of the
>> problem.
>> > >> MET7
>> > >> > >> seems
>> > >> > >> > to be having some issue, and the guy here at OPC that
helps me
>> > with
>> > >> > that
>> > >> > >> > stuff (Chris Juckins) is out on leave until tomorrow.
Anyway,
>> > >> MET7 is
>> > >> > >> not
>> > >> > >> > running any of my verification programs, and giving out
some
>> > >> errors,
>> > >> > so,
>> > >> > >> > I'll have to get with him tomorrow to fix that.
>> > >> > >> >
>> > >> > >> > So, in the mean time, I don't think that any kind of
land mask
>> > >> > creation
>> > >> > >> > that I'm doing today will work because it's not
pointing at
>> the
>> > >> right
>> > >> > >> > directories.
>> > >> > >> >
>> > >> > >> > But, when I do get this to work, I tried this and got
this
>> error:
>> > >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
>> gwes01.glo_30m.t00z.grib2
>> > >> G193
>> > >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
>> > >> > >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
>> > >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny:
321
>> lat_ll:
>> > >> > -80.000
>> > >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
>> > >> > >> > ERROR :
>> > >> > >> > ERROR : grd_file_type() -> file does not exist "G193"
>> > >> > >> > ERROR :
>> > >> > >> >
>> > >> > >> > I'm wondering if that's all related to MET7.
>> > >> > >> >
>> > >> > >> > So, I think I need to fix the MET7 issue before moving
on with
>> > >> this,
>> > >> > >> don't
>> > >> > >> > you?
>> > >> > >> >
>> > >> > >> > Roz
>> > >> > >> >
>> > >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway via
RT <
>> > >> > >> > met_help at ucar.edu
>> > >> > >> > > wrote:
>> > >> > >> >
>> > >> > >> > > Roz,
>> > >> > >> > >
>> > >> > >> > > OK, one other possible option to consider. I figured
that
>> > >> there's
>> > >> > >> plenty
>> > >> > >> > > of "ocean" products out there. So I found a NOAA
WAVEWATCH
>> > one:
>> > >> > >> > >
>> > >> > >> > > (1) Download sample wavewatch file:
>> > >> > >> > > wget
>> > >> > >> > >
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
>> > >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
>> > >> > >> > >
>> > >> > >> > > (2) Run regrid_data_plane to put some surface wind
speed
>> data
>> > on
>> > >> the
>> > >> > >> 1/4
>> > >> > >> > > GFS grid:
>> > >> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
>> > >> ocean_data.nc
>> > >> > >> -field
>> > >> > >> > > 'name="WIND"; level="L0";'
>> > >> > >> > >
>> > >> > >> > > (3) Run gen_vx_mask to select points that contain
valid
>> data:
>> > >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc
ocean_mask.nc
>> -type
>> > >> data
>> > >> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh ne-
9999
>> -name
>> > >> > OCEAN
>> > >> > >> > >
>> > >> > >> > > (4) Run plot_data_plane to see the result:
>> > >> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
>> 'name="OCEAN";
>> > >> > >> > > level="(*,*)";'
>> > >> > >> > >
>> > >> > >> > > As you can see, the result gets rid of the lakes
problem.
>> But
>> > >> > >> wavewatch
>> > >> > >> > is
>> > >> > >> > > only run to +/- 80 degrees, so we're not including
points
>> near
>> > >> the
>> > >> > >> poles.
>> > >> > >> > >
>> > >> > >> > > Figured this would be a lot easier than running WPS
>> yourself.
>> > >> > >> > >
>> > >> > >> > > Thanks,
>> > >> > >> > > John
>> > >> > >> > >
>> > >> > >> > >
>> > >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <
>> > >> johnhg at ucar.edu>
>> > >> > >> > wrote:
>> > >> > >> > >
>> > >> > >> > > > Roz,
>> > >> > >> > > >
>> > >> > >> > > > I talked to some folks and have one suggestion that
>> *might*
>> > >> work.
>> > >> > >> The
>> > >> > >> > > WRF
>> > >> > >> > > > Pre-processing system is named WPS. The geogrid
program
>> > within
>> > >> > WPS
>> > >> > >> is
>> > >> > >> > > used
>> > >> > >> > > > to initialize your domain and handles land use
>> information.
>> > By
>> > >> > >> > default,
>> > >> > >> > > > lakes and oceans are treated the same way.
However,
>> > apparently
>> > >> > >> there
>> > >> > >> > is
>> > >> > >> > > an
>> > >> > >> > > > option to distinguish between them. Take a look
here:
>> > >> > >> > > >
>> > >> > >> > > >
http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
>> > >> > >> > > users_guide_chap3.htm#_Description_of_the_1
>> > >> > >> > > >
>> > >> > >> > > > And search for "Alternative Initialization of Lake
SSTs".
>> > >> > >> > > >
>> > >> > >> > > > So you'd...
>> > >> > >> > > > (1) download the MODIS SST data
>> > >> > >> > > > (2) configure geogrid for the 0.25 degree GFS grid
>> > >> > >> > > > (3) configure geogrid to distinguish between lakes
and
>> oceans
>> > >> > >> > > > (4) run geogrid
>> > >> > >> > > > (5) run the output through the MET gen_vx_mask tool
to use
>> > >> ocean
>> > >> > >> values
>> > >> > >> > > > and skip the lake values
>> > >> > >> > > >
>> > >> > >> > > > Thanks,
>> > >> > >> > > > John
>> > >> > >> > > >
>> > >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway <
>> > >> > johnhg at ucar.edu>
>> > >> > >> > > wrote:
>> > >> > >> > > >
>> > >> > >> > > >> Roz,
>> > >> > >> > > >>
>> > >> > >> > > >> Whenever you see that error about loading shared
>> libraries,
>> > it
>> > >> > >> means
>> > >> > >> > > that
>> > >> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
environment
>> > >> > variable
>> > >> > >> is
>> > >> > >> > > set.
>> > >> > >> > > >> That environment variable tells the linker where
to look
>> for
>> > >> > shared
>> > >> > >> > > >> libraries at runtime... one of those shared
libraries is
>> GSL
>> > >> (GNU
>> > >> > >> > > >> Scientific Library). You'd "fix" this issue by
modifying
>> > how
>> > >> > >> > > >> LD_LIBRARY_PATH is set:
>> > >> > >> > > >> echo $LD_LIBRARY_PATH
>> > >> > >> > > >>
>> > >> > >> > > >> Take a look in your ~/.cshrc file for c-shell or
>> ~/.bashrc
>> > for
>> > >> > >> bash to
>> > >> > >> > > >> see how its set.
>> > >> > >> > > >>
>> > >> > >> > > >> As for the LAND/SEA mask, I was wondering if those
lakes
>> > would
>> > >> > be a
>> > >> > >> > > >> problem. Using the model's LAND/SEA mask is the
easiest,
>> > but
>> > >> > >> doesn't
>> > >> > >> > > >> provide an easy way of selecting out oceans. My
next
>> > thought
>> > >> was
>> > >> > >> to
>> > >> > >> > use
>> > >> > >> > > >> GIS Shapefiles to define only the ocean area.
That will
>> be
>> > >> > >> available
>> > >> > >> > in
>> > >> > >> > > >> the next version of MET, version 7.1. I tried
using a
>> beta
>> > >> > release
>> > >> > >> > for
>> > >> > >> > > >> met-7.1, but ran into problems when applying large
>> polylines
>> > >> to
>> > >> > >> global
>> > >> > >> > > >> grids.
>> > >> > >> > > >>
>> > >> > >> > > >> I'll keep thinking about that one.
>> > >> > >> > > >>
>> > >> > >> > > >> Thanks,
>> > >> > >> > > >> John
>> > >> > >> > > >>
>> > >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn MacCracken
- NOAA
>> > >> > Affiliate
>> > >> > >> > via
>> > >> > >> > > >> RT <met_help at ucar.edu> wrote:
>> > >> > >> > > >>
>> > >> > >> > > >>>
>> > >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
>> > >> ket/Display.html?id=86091 >
>> > >> > >> > > >>>
>> > >> > >> > > >>> Hey John,
>> > >> > >> > > >>>
>> > >> > >> > > >>> I have 2 problems. First, I'm able to use
>> plot_data_plane,
>> > >> but,
>> > >> > >> > when I
>> > >> > >> > > >>> use
>> > >> > >> > > >>> the command for gen_vx_mask, I get this:
>> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
>> gfs.t00z.pgrb2.0p25.f000
>> > >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc
-type data
>> > >> > >> -mask_field
>> > >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name
WATER
>> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while
loading
>> > shared
>> > >> > >> > > libraries:
>> > >> > >> > > >>> libgsl.so.0: cannot open shared object file: No
such
>> file
>> > or
>> > >> > >> > directory
>> > >> > >> > > >>>
>> > >> > >> > > >>> Now, they are both in the same directory, and I
know
>> that
>> > >> I've
>> > >> > >> used
>> > >> > >> > > >>> gen_vx_mask before, so, I have no idea why I
would be
>> > getting
>> > >> > that
>> > >> > >> > > error
>> > >> > >> > > >>> message. Any ideas?
>> > >> > >> > > >>>
>> > >> > >> > > >>> Then, I was able to generate a *.ps file, which
looks
>> > exactly
>> > >> > like
>> > >> > >> > > yours,
>> > >> > >> > > >>> but, there is still the same problem. If you
look
>> closely
>> > >> are
>> > >> > >> your
>> > >> > >> > > map,
>> > >> > >> > > >>> you'll see these little white dots over land.
Those are
>> > >> lakes,
>> > >> > >> and
>> > >> > >> > > >>> that's
>> > >> > >> > > >>> what is giving me a fit, because I have ASCAT
>> observations
>> > >> over
>> > >> > >> those
>> > >> > >> > > >>> white
>> > >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data with
12 km
>> > ASCAT
>> > >> > >> > > data...so,
>> > >> > >> > > >>> very sensitive. Anyway, do you have any idea how
to get
>> > rid
>> > >> of
>> > >> > >> those
>> > >> > >> > > >>> points? Perhaps a different file with the same
domain?
>> > >> > >> > > >>>
>> > >> > >> > > >>> Roz
>> > >> > >> > > >>>
>> > >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn
MacCracken -
>> NOAA
>> > >> > >> Affiliate <
>> > >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
>> > >> > >> > > >>>
>> > >> > >> > > >>> > Ok, I'll let you know if I can get the mask to
work.
>> > This
>> > >> > seems
>> > >> > >> > easy
>> > >> > >> > > >>> > enough, and pretty straight forward.
>> > >> > >> > > >>> >
>> > >> > >> > > >>> > Thanks for the help!
>> > >> > >> > > >>> >
>> > >> > >> > > >>> > Roz
>> > >> > >> > > >>> >
>> > >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley
Gotway via
>> > RT <
>> > >> > >> > > >>> > met_help at ucar.edu> wrote:
>> > >> > >> > > >>> >
>> > >> > >> > > >>> >> Roz,
>> > >> > >> > > >>> >>
>> > >> > >> > > >>> >> Yes, I expect that using met-6.0 would work
fine.
>> Hope
>> > it
>> > >> > goes
>> > >> > >> > > >>> smoothly.
>> > >> > >> > > >>> >>
>> > >> > >> > > >>> >> Thanks,
>> > >> > >> > > >>> >> John
>> > >> > >> > > >>> >>
>> > >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn
MacCracken -
>> NOAA
>> > >> > >> Affiliate
>> > >> > >> > > >>> via RT
>> > >> > >> > > >>> >> <
>> > >> > >> > > >>> >> met_help at ucar.edu> wrote:
>> > >> > >> > > >>> >>
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
>> > >> > >> ket/Display.html?id=86091 >
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > Hi John,
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > I get the general idea and it looks pretty
straight
>> > >> > forward.
>> > >> > >> > I'm
>> > >> > >> > > >>> still
>> > >> > >> > > >>> >> > running MET6.0, since we had some
installation
>> issues,
>> > >> > but, I
>> > >> > >> > > >>> should be
>> > >> > >> > > >>> >> > able to generate the mask with that pretty
easily,
>> > >> correct?
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > So, if this works, I'll need to rerun all my
data
>> from
>> > >> Mar
>> > >> > >> 2018
>> > >> > >> > -
>> > >> > >> > > >>> >> present,
>> > >> > >> > > >>> >> > using that method that we worked out earlier
with
>> the
>> > >> > *.stat
>> > >> > >> > > files,
>> > >> > >> > > >>> >> > correct? Actually, I don't need to do
that...I can
>> > >> start
>> > >> > >> from
>> > >> > >> > the
>> > >> > >> > > >>> ASCII
>> > >> > >> > > >>> >> > files I've already generated, and then just
rerun
>> > >> > POINT_STAT
>> > >> > >> > with
>> > >> > >> > > >>> the
>> > >> > >> > > >>> >> > mask. Ok, that will save some steps.
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > Alright, I'll try making the mask and do a
test run
>> > >> after
>> > >> > >> lunch,
>> > >> > >> > > >>> and get
>> > >> > >> > > >>> >> > back to you when it works.
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > Thanks!
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > Roz
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John Halley
Gotway
>> via
>> > >> RT <
>> > >> > >> > > >>> >> > met_help at ucar.edu
>> > >> > >> > > >>> >> > > wrote:
>> > >> > >> > > >>> >> >
>> > >> > >> > > >>> >> > > Hi Roz,
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > I see you're wondering how to only use
point
>> > >> observations
>> > >> > >> over
>> > >> > >> > > >>> water
>> > >> > >> > > >>> >> and
>> > >> > >> > > >>> >> > > discard the ones over land. You're
running
>> ASCII2NC
>> > >> > >> followed
>> > >> > >> > by
>> > >> > >> > > >>> >> > Point-Stat
>> > >> > >> > > >>> >> > > and want to know where/how to define that
>> masking.
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > The ASCII2NC tool supports 3 command line
options
>> > for
>> > >> > >> > filtering
>> > >> > >> > > >>> point
>> > >> > >> > > >>> >> > > observations spatially: -mask_grid,
-mask_poly,
>> and
>> > >> > >> -mask_sid,
>> > >> > >> > > for
>> > >> > >> > > >>> >> grid,
>> > >> > >> > > >>> >> > > polyline, and station ID masking,
respectively.
>> But
>> > >> > that's
>> > >> > >> > not
>> > >> > >> > > >>> really
>> > >> > >> > > >>> >> > what
>> > >> > >> > > >>> >> > > you want. You want to do "data masking"
where
>> you
>> > >> read
>> > >> > in
>> > >> > >> a
>> > >> > >> > > >>> land/sea
>> > >> > >> > > >>> >> > mask
>> > >> > >> > > >>> >> > > and only use the points over water.
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask tool
to
>> create
>> > >> the
>> > >> > >> > desired
>> > >> > >> > > >>> >> masking
>> > >> > >> > > >>> >> > > region, and then reference that in the
Point-Stat
>> > >> config
>> > >> > >> file.
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > To illustrate, I pulled a sample GFS file:
>> > >> > >> > > >>> >> > > > wget
>> > >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
>> > >> > >> ata/gfs4/201807/20180702/gfs_
>> > >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
>> > >> > >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2 |
egrep
>> -i
>> > >> LAND
>> > >> > >> > > >>> >> > >
400:65422867:d=2018070200:LAND:surface:12
>> hour
>> > >> > fcst:
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > Run plot_data_plane to see it (see
attached
>> image):
>> > >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
>> > >> > >> gfs_4_20180702_0000_012.grb2
>> > >> > >> > > >>> >> > gfs_4_LAND.ps
>> > >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > Run gen_vx_mask to create a mask for your
>> > verification
>> > >> > >> domain.
>> > >> > >> > > If
>> > >> > >> > > >>> >> you're
>> > >> > >> > > >>> >> > > actually verifying on the GFS domain, the
command
>> > >> looks a
>> > >> > >> > little
>> > >> > >> > > >>> >> > redundant:
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
>> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
>> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
>> > >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
>> > >> > >> > > >>> >> > > -type data \
>> > >> > >> > > >>> >> > > -mask_field 'name="LAND";
level="L0";' \
>> > >> > >> > > >>> >> > > -thresh ==0 \
>> > >> > >> > > >>> >> > > -name WATER
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > I defined the threshold as "==0" because
we want
>> the
>> > >> > WATER
>> > >> > >> > > >>> points, not
>> > >> > >> > > >>> >> > the
>> > >> > >> > > >>> >> > > LAND points. And I used the "-name WATER"
>> command
>> > >> line
>> > >> > >> option
>> > >> > >> > > to
>> > >> > >> > > >>> name
>> > >> > >> > > >>> >> > the
>> > >> > >> > > >>> >> > > output NetCDF variable. This will show up
in the
>> > >> VX_MASK
>> > >> > >> > output
>> > >> > >> > > >>> >> column
>> > >> > >> > > >>> >> > of
>> > >> > >> > > >>> >> > > Point-Stat.
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > Lastly, setup your Point-Stat config file
like
>> this:
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > mask = {
>> > >> > >> > > >>> >> > > grid = [];
>> > >> > >> > > >>> >> > > poly = [
"/path/to/gfs_4_WATER_mask.nc" ];
>> > >> > >> > > >>> >> > > sid = [];
>> > >> > >> > > >>> >> > > }
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > Hope that helps clarify.
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > Thanks,
>> > >> > >> > > >>> >> > > John
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
>> MacCracken -
>> > >> NOAA
>> > >> > >> > > >>> Affiliate via
>> > >> > >> > > >>> >> > RT <
>> > >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request 86091
was
>> acted
>> > >> upon.
>> > >> > >> > > >>> >> > > > Transaction: Ticket created by
>> > >> > >> rosalyn.maccracken at noaa.gov
>> > >> > >> > > >>> >> > > > Queue: met_help
>> > >> > >> > > >>> >> > > > Subject: masking land features
questions
>> > >> > >> > > >>> >> > > > Owner: Nobody
>> > >> > >> > > >>> >> > > > Requestors:
rosalyn.maccracken at noaa.gov
>> > >> > >> > > >>> >> > > > Status: new
>> > >> > >> > > >>> >> > > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Tic
>> > >> > >> > > >>> >> ket/Display.html?id=86091
>> > >> > >> > > >>> >> > >
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > Hi,
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > I'm using ASCAT data to verify the GFS.
I only
>> > >> want to
>> > >> > >> > verify
>> > >> > >> > > >>> >> points
>> > >> > >> > > >>> >> > > over
>> > >> > >> > > >>> >> > > > the ocean, and not over any inland
lakes. I
>> > noticed
>> > >> > >> that I
>> > >> > >> > > was
>> > >> > >> > > >>> >> getting
>> > >> > >> > > >>> >> > > > matched points over land (mostly
Africa). I'm
>> > >> dumping
>> > >> > >> out
>> > >> > >> > the
>> > >> > >> > > >>> >> MGDRlite
>> > >> > >> > > >>> >> > > > file to an ascii file, which I use
ASCII2NC to
>> > >> create
>> > >> > the
>> > >> > >> > > netCDF
>> > >> > >> > > >>> >> file,
>> > >> > >> > > >>> >> > > and
>> > >> > >> > > >>> >> > > > then go on to use Point_stat to create
>> statistics
>> > >> for
>> > >> > the
>> > >> > >> > > >>> matched
>> > >> > >> > > >>> >> > points.
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > How do I mask out points over land
before it
>> gets
>> > to
>> > >> > the
>> > >> > >> > > >>> Point_stat
>> > >> > >> > > >>> >> > step?
>> > >> > >> > > >>> >> > > > Is there something in the ASCII2NC
processing
>> > that I
>> > >> > can
>> > >> > >> > add,
>> > >> > >> > > >>> so I
>> > >> > >> > > >>> >> > don't
>> > >> > >> > > >>> >> > > > get these matched points?
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > Thanks in advance!
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > Roz
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > --
>> > >> > >> > > >>> >> > > > Rosalyn MacCracken
>> > >> > >> > > >>> >> > > > Support Scientist
>> > >> > >> > > >>> >> > > >
>> > >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 16 09:40:50 2018
Roz,
I have 3 pieces of info for you:
(1) STAT-Analysis supports the "-mask_poly" job command option which
is
used to specify a lat/lon polyline file. Only those lat/lon's falling
inside the polyline region are used. However, defining large
polylines on
global grids has proved problematic in the past. Sometimes the logic
for
determining which lat/lon points are *inside* the polyline breaks down
for
global grids.
(2) STAT-Analysis supports the "-column_thresh" job command option as
well,
which could be used to filter lat/lon values. For example, here's how
you
could use it to define a lat/lon box: -column_thresh OBS_LAT 'ge-
30&&le30'
-column_thresh OBS_LON 'ge-150&&le-90'
(3) Really, the best solution here is to enhance STAT-Analysis to do
exactly what we want it to do... namely, be able to read the output of
Gen-Vx-Mask to define the masking region. But it comes down to
timing. We
could probably include that in the next beta release for met-7.1 and
have
it available in a week or two for you to test out.
Thanks,
John
On Fri, Jul 13, 2018 at 12:52 PM Rosalyn MacCracken - NOAA Affiliate
via RT
<met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
> hi John,
>
> Maybe I didn't ask the right question. Can I use the same formatted
mask
> (polyline file with lat/lon), that I used for my point-stat mask,
with
> stat-analysis with new lat/lon coordinates in the vx_mask option?
Or does
> it have to be the same set of coordinates that I used in the
original
> point-stat mask file?
>
> Roz
>
> On Fri, Jul 13, 2018 at 2:08 PM, Rosalyn MacCracken - NOAA Affiliate
<
> rosalyn.maccracken at noaa.gov> wrote:
>
> > Hi John,
> >
> > Yeah, I don't know if either solution is going to work. There
isn't any
> > OBS_ID associated with the observation, but, more like a flag in
the
> > original ASCAT data file. I wouldn't even begin to know how to
figure
> out
> > how to translate that into a station id.
> >
> > Oh, and I can't just change the mask and rerun stat-analysis. I
would
> > need to rerun point-stat, and now I'm back to square one...
> >
> > So, there is no way to designate a new box to input into the
> > stat-analysis? You know, like you can indicate the wind speed
> > threshold...maybe something similar with the lat/lon? Guess
not...
> >
> > Roz
> >
> > On Thu, Jul 12, 2018 at 2:55 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Roz,
> >>
> >> Yes, that's correct. You'd list that new land mask in the Point-
Stat
> >> config file to control which points are included.
> >>
> >> If I remember correctly, you're running some STAT-Analysis jobs
to
> >> aggregate MPR lines from previous runs of Point-Stat. And that's
the
> >> problem, that STAT-Analysis cannot use the output of gen_vx_mask
to
> >> control
> >> which MPR lines should be included. Here are two possibilities
for
> >> solving
> >> this problem:
> >>
> >> (1) The MPR line contains a column named OBS_SID which is the
name of
> the
> >> station. If you can, through some means, identify the names of
the
> >> stations that you *DO* want to use, you could write them out to
an ASCII
> >> file. Then when you run STAT-Analysis jobs, you could use the
> "-mask_sid"
> >> option to tell it the names of the stations to be included. I
haven't
> >> done
> >> this for large numbers of stations. In principle, the logic
should
> work.
> >> In practice, it may be a little slow, checking that long list of
> stations
> >> many times.
> >>
> >> (2) We have been doing active development for the next MET
release. As
> we
> >> add new features, we've been building beta releases and building
them on
> >> NOAA machines (theia, jet, wcoss) for NOAA folks to test out.
The
> current
> >> development version is named met-7.1_beta6. I could elevate the
> priority
> >> of that development ticket I sent to you, and enhance stat-
analysis to
> >> define masking regions using the output of gen_vx_mask. And then
I
> could
> >> include it in the next beta release for you to test out. That
would
> >> certainly be easier for you than generating a list of stations to
use.
> >> But
> >> it would take a week or two to get you a new beta release to test
out.
> >>
> >> If you decided to go with (1), let me know. I have a suggestion
for how
> >> you might generate that list of stations to include.
> >>
> >> Thanks,
> >> John
> >>
> >> On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA
Affiliate via
> >> RT <
> >> met_help at ucar.edu> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >> >
> >> > Oh, but, I can incorporate this new land mask from here on out,
right?
> >> And,
> >> > I would add that to my Point-stat config file, like you showed
me to
> do
> >> in
> >> > the previous email, correct?
> >> >
> >> > Roz
> >> >
> >> > On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA
Affiliate <
> >> > rosalyn.maccracken at noaa.gov> wrote:
> >> >
> >> > > Hi John,
> >> > >
> >> > > There's got to be a way around this...I'm sure there is a
work
> around
> >> so
> >> > > that I don't have to go back an get all of the GFS files.
And, I
> know
> >> > that
> >> > > I want to use STAT-Analysis, since I already have all that in
place
> to
> >> > > regenerate data.
> >> > >
> >> > > So, you said I can use a lat/lon polyline file with STAT-
Analysis.
> Of
> >> > > course, I already use that with my North Atlantic or North
Pacific
> >> masks.
> >> > > So, my first option might be, make my North Atlantic mask
smaller,
> >> not to
> >> > > include West Africa, where the bad observations are located,
and
> don't
> >> > use
> >> > > the global file that is generated (if there a way not to make
that
> >> file,
> >> > > and only re-generate files for the North Atlantic?).
Ok...that's
> one
> >> > > option, and that's probably what I will have to do.
> >> > >
> >> > > Here's the question. So, let's say there was a way for us to
go
> back
> >> > > through our ASCAT data, and identify lat/lons of observations
that
> >> were
> >> > > flagged not to use, or over land, is there a way to have
> STAT-Analysis
> >> > > discard matched pairs associated with those lat/lons? Maybe,
that's
> >> like
> >> > > using the lat/lon ployline file in reverse? Here's the mask,
use
> all
> >> > > observations except if it falls inside this masked domain?
Can we
> do
> >> > that?
> >> > >
> >> > > Roz
> >> > >
> >> > >
> >> > >
> >> > > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT <
> >> > > met_help at ucar.edu> wrote:
> >> > >
> >> > >> Roz,
> >> > >>
> >> > >> Bad news. I had hoped we could simply pass in the gridded
mask
> file
> >> > >> you've
> >> > >> defined as input to STAT-Analysis using "-mask_poly" but
> >> unfortunately
> >> > >> that
> >> > >> doesn't work.
> >> > >>
> >> > >> STAT-Analysis currently supports: -mask_grid, -mask_poly,
and
> >> -mask_sid
> >> > to
> >> > >> filter MPR lines by a named grid, polyline file, or list of
station
> >> id
> >> > >> names. The other MET tools, like Point-Stat and Grid-Stat
also
> >> support
> >> > >> multiple masking options.
> >> > >>
> >> > >> For example, in Point-Stat:
> >> > >> mask = {
> >> > >> grid = [ "FULL" ];
> >> > >> poly = [];
> >> > >> sid = [];
> >> > >> }
> >> > >>
> >> > >> The "mask.grid" option in Point-Stat is the same of "-
mask_grid" in
> >> > >> STAT-Analysis. They both process named grids, like "G212"
for NCEP
> >> grid
> >> > >> number 212.
> >> > >>
> >> > >> Likewise, the "mask.sid" option is the same as "-mask_sid".
They
> >> both
> >> > >> define lists of station ID names to be included.
> >> > >>
> >> > >> *BUT* the "mask.poly" option in Point-Stat is much more
flexible
> than
> >> > >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can
only be
> set
> >> to
> >> > a
> >> > >> lat/lon polyline file. In Point-Stat, it can also be set to
the
> >> output
> >> > of
> >> > >> gen_vx_mask or any gridded data file followed by a
description of
> >> data
> >> > to
> >> > >> be extracted and thresholded.
> >> > >>
> >> > >> We actually have a development task already defined to
address this
> >> > issue
> >> > >> (see attached).
> >> > >>
> >> > >> But that doesn't help you. So unfortunately, with met-7.0,
you'd
> >> would
> >> > >> need to go all the way back to generating pairs with Point-
Stat.
> >> > >>
> >> > >> However, if you were using a future version of MET, you
could do
> this
> >> > all
> >> > >> in STAT-Analysis.
> >> > >>
> >> > >> Thanks,
> >> > >> John
> >> > >>
> >> > >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA
Affiliate
> >> via
> >> > >> RT <
> >> > >> met_help at ucar.edu> wrote:
> >> > >>
> >> > >> >
> >> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >> > >> >
> >> > >> > Hi John,
> >> > >> >
> >> > >> > Well, good news. We got our MET7 to work, and I was able
to
> >> create my
> >> > >> > ocean mask. It was an issue with conflicts in our
libraries, and
> >> the
> >> > >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> >> > >> >
> >> > >> > Now, I have this ocean mask, and now I can go back and
rerun my
> >> data.
> >> > >> So,
> >> > >> > as usual, I had some questions.
> >> > >> >
> >> > >> > I have a series of scripts where you helped me set up
> STATanalysis
> >> to
> >> > >> > reprocess the data using the *.stat files and the -job
> >> aggregate_stat
> >> > >> > command . Will I be able to use this method again, or,
because
> >> it's
> >> > >> > applying a mask, will I need to get the raw data (GFS and
ASCAT
> >> data)?
> >> > >> > And, I guess if I have to use the raw data, I will have to
start
> >> with
> >> > >> > ASCII2NC, etc, as if I'm processing from scratch, correct?
> >> > >> >
> >> > >> > I just need a sense of how big of a job this is....
> >> > >> >
> >> > >> > Thanks for your help!
> >> > >> >
> >> > >> > Roz
> >> > >> >
> >> > >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken - NOAA
> >> Affiliate <
> >> > >> > rosalyn.maccracken at noaa.gov> wrote:
> >> > >> >
> >> > >> > > Oh, yeah, nothing seems to be going smoothly
today...anyway, I
> >> > think I
> >> > >> > > need to wait until Chris and Fran come in tomorrow to
set our
> >> > >> directories
> >> > >> > > correctly to point at MET, and get it running again
before I do
> >> > >> anything
> >> > >> > > else.
> >> > >> > >
> >> > >> > > I'll try this again tomorrow and let you know how I do.
> >> > >> > >
> >> > >> > > Thanks for your help!
> >> > >> > >
> >> > >> > > Roz
> >> > >> > >
> >> > >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway via
RT <
> >> > >> > > met_help at ucar.edu> wrote:
> >> > >> > >
> >> > >> > >> Roz,
> >> > >> > >>
> >> > >> > >> Sorry you're having a rough day. No worries though,
this
> issue
> >> is
> >> > >> easy
> >> > >> > to
> >> > >> > >> overcome. Here's a list of pre-defined NCEP grids:
> >> > >> > >>
http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> >> > >> > >>
> >> > >> > >> The intention in MET is to support them using the
naming
> >> convention
> >> > >> G###
> >> > >> > >> where ### is the 3 digit grid number. But if you look
closely
> >> on
> >> > >> that
> >> > >> > >> website, you'll see that grid 193 is a relatively new
one and
> is
> >> > >> listed
> >> > >> > in
> >> > >> > >> red. That definition just doesn't exist in MET version
6.0.
> >> > >> > >>
> >> > >> > >> The easy fix is this.... just replace "G193" on the
command
> line
> >> > with
> >> > >> > the
> >> > >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a
selection from
> >> the
> >> > >> usage
> >> > >> > >> statement for regrid_data_plane:
> >> > >> > >>
> >> > >> > >> Usage: regrid_data_plane
> >> > >> > >> input_filename
> >> > >> > >> to_grid
> >> > >> > >> output_filename
> >> > >> > >> "to_grid" defines the output grid as a
named
> >> grid,
> >> > >> the
> >> > >> > >> path
> >> > >> > >> to a gridded data file, or an explicit grid
specification
> string
> >> > >> > >> (required).
> >> > >> > >>
> >> > >> > >> When you set "to_grid" equal to a gridded data file,
MET reads
> >> the
> >> > >> grid
> >> > >> > >> definition from the first record of that file and uses
it.
> >> > >> > >>
> >> > >> > >> That should do it.
> >> > >> > >>
> >> > >> > >> Thanks,
> >> > >> > >> John
> >> > >> > >>
> >> > >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken -
NOAA
> >> Affiliate
> >> > >> via
> >> > >> > >> RT <
> >> > >> > >> met_help at ucar.edu> wrote:
> >> > >> > >>
> >> > >> > >> >
> >> > >> > >> > <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> >> >
> >> > >> > >> >
> >> > >> > >> > Hi John,
> >> > >> > >> >
> >> > >> > >> > I'm really not having much luck today with this.
Maybe I
> >> should
> >> > >> have
> >> > >> > >> > stayed in bed (haha).
> >> > >> > >> >
> >> > >> > >> > So, the first thing I did was check the
LD_LIBRARY_PATH, and
> >> it's
> >> > >> > >> pointing
> >> > >> > >> > to the MET7 directories. Ok, that could be most of
the
> >> problem.
> >> > >> MET7
> >> > >> > >> seems
> >> > >> > >> > to be having some issue, and the guy here at OPC that
helps
> me
> >> > with
> >> > >> > that
> >> > >> > >> > stuff (Chris Juckins) is out on leave until tomorrow.
> Anyway,
> >> > >> MET7 is
> >> > >> > >> not
> >> > >> > >> > running any of my verification programs, and giving
out some
> >> > >> errors,
> >> > >> > so,
> >> > >> > >> > I'll have to get with him tomorrow to fix that.
> >> > >> > >> >
> >> > >> > >> > So, in the mean time, I don't think that any kind of
land
> mask
> >> > >> > creation
> >> > >> > >> > that I'm doing today will work because it's not
pointing at
> >> the
> >> > >> right
> >> > >> > >> > directories.
> >> > >> > >> >
> >> > >> > >> > But, when I do get this to work, I tried this and got
this
> >> error:
> >> > >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
> >> gwes01.glo_30m.t00z.grib2
> >> > >> G193
> >> > >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> >> > >> > >> > DEBUG 1: Reading data file: gwes01.glo_30m.t00z.grib2
> >> > >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720 Ny:
321
> >> lat_ll:
> >> > >> > -80.000
> >> > >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> >> > >> > >> > ERROR :
> >> > >> > >> > ERROR : grd_file_type() -> file does not exist
"G193"
> >> > >> > >> > ERROR :
> >> > >> > >> >
> >> > >> > >> > I'm wondering if that's all related to MET7.
> >> > >> > >> >
> >> > >> > >> > So, I think I need to fix the MET7 issue before
moving on
> with
> >> > >> this,
> >> > >> > >> don't
> >> > >> > >> > you?
> >> > >> > >> >
> >> > >> > >> > Roz
> >> > >> > >> >
> >> > >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway
via RT <
> >> > >> > >> > met_help at ucar.edu
> >> > >> > >> > > wrote:
> >> > >> > >> >
> >> > >> > >> > > Roz,
> >> > >> > >> > >
> >> > >> > >> > > OK, one other possible option to consider. I
figured that
> >> > >> there's
> >> > >> > >> plenty
> >> > >> > >> > > of "ocean" products out there. So I found a NOAA
> WAVEWATCH
> >> > one:
> >> > >> > >> > >
> >> > >> > >> > > (1) Download sample wavewatch file:
> >> > >> > >> > > wget
> >> > >> > >> > >
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> >> > >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> >> > >> > >> > >
> >> > >> > >> > > (2) Run regrid_data_plane to put some surface wind
speed
> >> data
> >> > on
> >> > >> the
> >> > >> > >> 1/4
> >> > >> > >> > > GFS grid:
> >> > >> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2 G193
> >> > >> ocean_data.nc
> >> > >> > >> -field
> >> > >> > >> > > 'name="WIND"; level="L0";'
> >> > >> > >> > >
> >> > >> > >> > > (3) Run gen_vx_mask to select points that contain
valid
> >> data:
> >> > >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc
ocean_mask.nc
> >> -type
> >> > >> data
> >> > >> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh
ne-9999
> >> -name
> >> > >> > OCEAN
> >> > >> > >> > >
> >> > >> > >> > > (4) Run plot_data_plane to see the result:
> >> > >> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
> >> 'name="OCEAN";
> >> > >> > >> > > level="(*,*)";'
> >> > >> > >> > >
> >> > >> > >> > > As you can see, the result gets rid of the lakes
problem.
> >> But
> >> > >> > >> wavewatch
> >> > >> > >> > is
> >> > >> > >> > > only run to +/- 80 degrees, so we're not including
points
> >> near
> >> > >> the
> >> > >> > >> poles.
> >> > >> > >> > >
> >> > >> > >> > > Figured this would be a lot easier than running WPS
> >> yourself.
> >> > >> > >> > >
> >> > >> > >> > > Thanks,
> >> > >> > >> > > John
> >> > >> > >> > >
> >> > >> > >> > >
> >> > >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway <
> >> > >> johnhg at ucar.edu>
> >> > >> > >> > wrote:
> >> > >> > >> > >
> >> > >> > >> > > > Roz,
> >> > >> > >> > > >
> >> > >> > >> > > > I talked to some folks and have one suggestion
that
> >> *might*
> >> > >> work.
> >> > >> > >> The
> >> > >> > >> > > WRF
> >> > >> > >> > > > Pre-processing system is named WPS. The geogrid
program
> >> > within
> >> > >> > WPS
> >> > >> > >> is
> >> > >> > >> > > used
> >> > >> > >> > > > to initialize your domain and handles land use
> >> information.
> >> > By
> >> > >> > >> > default,
> >> > >> > >> > > > lakes and oceans are treated the same way.
However,
> >> > apparently
> >> > >> > >> there
> >> > >> > >> > is
> >> > >> > >> > > an
> >> > >> > >> > > > option to distinguish between them. Take a look
here:
> >> > >> > >> > > >
> >> > >> > >> > > >
http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3/
> >> > >> > >> > > users_guide_chap3.htm#_Description_of_the_1
> >> > >> > >> > > >
> >> > >> > >> > > > And search for "Alternative Initialization of
Lake
> SSTs".
> >> > >> > >> > > >
> >> > >> > >> > > > So you'd...
> >> > >> > >> > > > (1) download the MODIS SST data
> >> > >> > >> > > > (2) configure geogrid for the 0.25 degree GFS
grid
> >> > >> > >> > > > (3) configure geogrid to distinguish between
lakes and
> >> oceans
> >> > >> > >> > > > (4) run geogrid
> >> > >> > >> > > > (5) run the output through the MET gen_vx_mask
tool to
> use
> >> > >> ocean
> >> > >> > >> values
> >> > >> > >> > > > and skip the lake values
> >> > >> > >> > > >
> >> > >> > >> > > > Thanks,
> >> > >> > >> > > > John
> >> > >> > >> > > >
> >> > >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley Gotway
<
> >> > >> > johnhg at ucar.edu>
> >> > >> > >> > > wrote:
> >> > >> > >> > > >
> >> > >> > >> > > >> Roz,
> >> > >> > >> > > >>
> >> > >> > >> > > >> Whenever you see that error about loading shared
> >> libraries,
> >> > it
> >> > >> > >> means
> >> > >> > >> > > that
> >> > >> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
> environment
> >> > >> > variable
> >> > >> > >> is
> >> > >> > >> > > set.
> >> > >> > >> > > >> That environment variable tells the linker where
to
> look
> >> for
> >> > >> > shared
> >> > >> > >> > > >> libraries at runtime... one of those shared
libraries
> is
> >> GSL
> >> > >> (GNU
> >> > >> > >> > > >> Scientific Library). You'd "fix" this issue by
> modifying
> >> > how
> >> > >> > >> > > >> LD_LIBRARY_PATH is set:
> >> > >> > >> > > >> echo $LD_LIBRARY_PATH
> >> > >> > >> > > >>
> >> > >> > >> > > >> Take a look in your ~/.cshrc file for c-shell or
> >> ~/.bashrc
> >> > for
> >> > >> > >> bash to
> >> > >> > >> > > >> see how its set.
> >> > >> > >> > > >>
> >> > >> > >> > > >> As for the LAND/SEA mask, I was wondering if
those
> lakes
> >> > would
> >> > >> > be a
> >> > >> > >> > > >> problem. Using the model's LAND/SEA mask is the
> easiest,
> >> > but
> >> > >> > >> doesn't
> >> > >> > >> > > >> provide an easy way of selecting out oceans. My
next
> >> > thought
> >> > >> was
> >> > >> > >> to
> >> > >> > >> > use
> >> > >> > >> > > >> GIS Shapefiles to define only the ocean area.
That
> will
> >> be
> >> > >> > >> available
> >> > >> > >> > in
> >> > >> > >> > > >> the next version of MET, version 7.1. I tried
using a
> >> beta
> >> > >> > release
> >> > >> > >> > for
> >> > >> > >> > > >> met-7.1, but ran into problems when applying
large
> >> polylines
> >> > >> to
> >> > >> > >> global
> >> > >> > >> > > >> grids.
> >> > >> > >> > > >>
> >> > >> > >> > > >> I'll keep thinking about that one.
> >> > >> > >> > > >>
> >> > >> > >> > > >> Thanks,
> >> > >> > >> > > >> John
> >> > >> > >> > > >>
> >> > >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn
MacCracken -
> NOAA
> >> > >> > Affiliate
> >> > >> > >> > via
> >> > >> > >> > > >> RT <met_help at ucar.edu> wrote:
> >> > >> > >> > > >>
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
> >> > >> ket/Display.html?id=86091 >
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> Hey John,
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> I have 2 problems. First, I'm able to use
> >> plot_data_plane,
> >> > >> but,
> >> > >> > >> > when I
> >> > >> > >> > > >>> use
> >> > >> > >> > > >>> the command for gen_vx_mask, I get this:
> >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
> >> gfs.t00z.pgrb2.0p25.f000
> >> > >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc
-type
> data
> >> > >> > >> -mask_field
> >> > >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name
WATER
> >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while
loading
> >> > shared
> >> > >> > >> > > libraries:
> >> > >> > >> > > >>> libgsl.so.0: cannot open shared object file: No
such
> >> file
> >> > or
> >> > >> > >> > directory
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> Now, they are both in the same directory, and I
know
> >> that
> >> > >> I've
> >> > >> > >> used
> >> > >> > >> > > >>> gen_vx_mask before, so, I have no idea why I
would be
> >> > getting
> >> > >> > that
> >> > >> > >> > > error
> >> > >> > >> > > >>> message. Any ideas?
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> Then, I was able to generate a *.ps file, which
looks
> >> > exactly
> >> > >> > like
> >> > >> > >> > > yours,
> >> > >> > >> > > >>> but, there is still the same problem. If you
look
> >> closely
> >> > >> are
> >> > >> > >> your
> >> > >> > >> > > map,
> >> > >> > >> > > >>> you'll see these little white dots over land.
Those
> are
> >> > >> lakes,
> >> > >> > >> and
> >> > >> > >> > > >>> that's
> >> > >> > >> > > >>> what is giving me a fit, because I have ASCAT
> >> observations
> >> > >> over
> >> > >> > >> those
> >> > >> > >> > > >>> white
> >> > >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data
with 12
> km
> >> > ASCAT
> >> > >> > >> > > data...so,
> >> > >> > >> > > >>> very sensitive. Anyway, do you have any idea
how to
> get
> >> > rid
> >> > >> of
> >> > >> > >> those
> >> > >> > >> > > >>> points? Perhaps a different file with the same
> domain?
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> Roz
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn
MacCracken -
> >> NOAA
> >> > >> > >> Affiliate <
> >> > >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> >> > >> > >> > > >>>
> >> > >> > >> > > >>> > Ok, I'll let you know if I can get the mask
to work.
> >> > This
> >> > >> > seems
> >> > >> > >> > easy
> >> > >> > >> > > >>> > enough, and pretty straight forward.
> >> > >> > >> > > >>> >
> >> > >> > >> > > >>> > Thanks for the help!
> >> > >> > >> > > >>> >
> >> > >> > >> > > >>> > Roz
> >> > >> > >> > > >>> >
> >> > >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley
Gotway
> via
> >> > RT <
> >> > >> > >> > > >>> > met_help at ucar.edu> wrote:
> >> > >> > >> > > >>> >
> >> > >> > >> > > >>> >> Roz,
> >> > >> > >> > > >>> >>
> >> > >> > >> > > >>> >> Yes, I expect that using met-6.0 would work
fine.
> >> Hope
> >> > it
> >> > >> > goes
> >> > >> > >> > > >>> smoothly.
> >> > >> > >> > > >>> >>
> >> > >> > >> > > >>> >> Thanks,
> >> > >> > >> > > >>> >> John
> >> > >> > >> > > >>> >>
> >> > >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn
MacCracken -
> >> NOAA
> >> > >> > >> Affiliate
> >> > >> > >> > > >>> via RT
> >> > >> > >> > > >>> >> <
> >> > >> > >> > > >>> >> met_help at ucar.edu> wrote:
> >> > >> > >> > > >>> >>
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> >> > >> > >> ket/Display.html?id=86091 >
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > Hi John,
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > I get the general idea and it looks pretty
> straight
> >> > >> > forward.
> >> > >> > >> > I'm
> >> > >> > >> > > >>> still
> >> > >> > >> > > >>> >> > running MET6.0, since we had some
installation
> >> issues,
> >> > >> > but, I
> >> > >> > >> > > >>> should be
> >> > >> > >> > > >>> >> > able to generate the mask with that pretty
> easily,
> >> > >> correct?
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > So, if this works, I'll need to rerun all
my data
> >> from
> >> > >> Mar
> >> > >> > >> 2018
> >> > >> > >> > -
> >> > >> > >> > > >>> >> present,
> >> > >> > >> > > >>> >> > using that method that we worked out
earlier with
> >> the
> >> > >> > *.stat
> >> > >> > >> > > files,
> >> > >> > >> > > >>> >> > correct? Actually, I don't need to do
that...I
> can
> >> > >> start
> >> > >> > >> from
> >> > >> > >> > the
> >> > >> > >> > > >>> ASCII
> >> > >> > >> > > >>> >> > files I've already generated, and then
just rerun
> >> > >> > POINT_STAT
> >> > >> > >> > with
> >> > >> > >> > > >>> the
> >> > >> > >> > > >>> >> > mask. Ok, that will save some steps.
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > Alright, I'll try making the mask and do a
test
> run
> >> > >> after
> >> > >> > >> lunch,
> >> > >> > >> > > >>> and get
> >> > >> > >> > > >>> >> > back to you when it works.
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > Thanks!
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > Roz
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John
Halley
> Gotway
> >> via
> >> > >> RT <
> >> > >> > >> > > >>> >> > met_help at ucar.edu
> >> > >> > >> > > >>> >> > > wrote:
> >> > >> > >> > > >>> >> >
> >> > >> > >> > > >>> >> > > Hi Roz,
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > I see you're wondering how to only use
point
> >> > >> observations
> >> > >> > >> over
> >> > >> > >> > > >>> water
> >> > >> > >> > > >>> >> and
> >> > >> > >> > > >>> >> > > discard the ones over land. You're
running
> >> ASCII2NC
> >> > >> > >> followed
> >> > >> > >> > by
> >> > >> > >> > > >>> >> > Point-Stat
> >> > >> > >> > > >>> >> > > and want to know where/how to define
that
> >> masking.
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > The ASCII2NC tool supports 3 command
line
> options
> >> > for
> >> > >> > >> > filtering
> >> > >> > >> > > >>> point
> >> > >> > >> > > >>> >> > > observations spatially: -mask_grid,
-mask_poly,
> >> and
> >> > >> > >> -mask_sid,
> >> > >> > >> > > for
> >> > >> > >> > > >>> >> grid,
> >> > >> > >> > > >>> >> > > polyline, and station ID masking,
respectively.
> >> But
> >> > >> > that's
> >> > >> > >> > not
> >> > >> > >> > > >>> really
> >> > >> > >> > > >>> >> > what
> >> > >> > >> > > >>> >> > > you want. You want to do "data masking"
where
> >> you
> >> > >> read
> >> > >> > in
> >> > >> > >> a
> >> > >> > >> > > >>> land/sea
> >> > >> > >> > > >>> >> > mask
> >> > >> > >> > > >>> >> > > and only use the points over water.
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask
tool to
> >> create
> >> > >> the
> >> > >> > >> > desired
> >> > >> > >> > > >>> >> masking
> >> > >> > >> > > >>> >> > > region, and then reference that in the
> Point-Stat
> >> > >> config
> >> > >> > >> file.
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > To illustrate, I pulled a sample GFS
file:
> >> > >> > >> > > >>> >> > > > wget
> >> > >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> >> > >> > >> ata/gfs4/201807/20180702/gfs_
> >> > >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA mask:
> >> > >> > >> > > >>> >> > > > wgrib2 gfs_4_20180702_0000_012.grb2
| egrep
> >> -i
> >> > >> LAND
> >> > >> > >> > > >>> >> > >
400:65422867:d=2018070200:LAND:surface:12
> >> hour
> >> > >> > fcst:
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > Run plot_data_plane to see it (see
attached
> >> image):
> >> > >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> >> > >> > >> gfs_4_20180702_0000_012.grb2
> >> > >> > >> > > >>> >> > gfs_4_LAND.ps
> >> > >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > Run gen_vx_mask to create a mask for
your
> >> > verification
> >> > >> > >> domain.
> >> > >> > >> > > If
> >> > >> > >> > > >>> >> you're
> >> > >> > >> > > >>> >> > > actually verifying on the GFS domain,
the
> command
> >> > >> looks a
> >> > >> > >> > little
> >> > >> > >> > > >>> >> > redundant:
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask \
> >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> >> > >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> >> > >> > >> > > >>> >> > > -type data \
> >> > >> > >> > > >>> >> > > -mask_field 'name="LAND";
level="L0";' \
> >> > >> > >> > > >>> >> > > -thresh ==0 \
> >> > >> > >> > > >>> >> > > -name WATER
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > I defined the threshold as "==0" because
we
> want
> >> the
> >> > >> > WATER
> >> > >> > >> > > >>> points, not
> >> > >> > >> > > >>> >> > the
> >> > >> > >> > > >>> >> > > LAND points. And I used the "-name
WATER"
> >> command
> >> > >> line
> >> > >> > >> option
> >> > >> > >> > > to
> >> > >> > >> > > >>> name
> >> > >> > >> > > >>> >> > the
> >> > >> > >> > > >>> >> > > output NetCDF variable. This will show
up in
> the
> >> > >> VX_MASK
> >> > >> > >> > output
> >> > >> > >> > > >>> >> column
> >> > >> > >> > > >>> >> > of
> >> > >> > >> > > >>> >> > > Point-Stat.
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > Lastly, setup your Point-Stat config
file like
> >> this:
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > mask = {
> >> > >> > >> > > >>> >> > > grid = [];
> >> > >> > >> > > >>> >> > > poly = [
"/path/to/gfs_4_WATER_mask.nc"
> ];
> >> > >> > >> > > >>> >> > > sid = [];
> >> > >> > >> > > >>> >> > > }
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > Hope that helps clarify.
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > Thanks,
> >> > >> > >> > > >>> >> > > John
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
> >> MacCracken -
> >> > >> NOAA
> >> > >> > >> > > >>> Affiliate via
> >> > >> > >> > > >>> >> > RT <
> >> > >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request
86091 was
> >> acted
> >> > >> upon.
> >> > >> > >> > > >>> >> > > > Transaction: Ticket created by
> >> > >> > >> rosalyn.maccracken at noaa.gov
> >> > >> > >> > > >>> >> > > > Queue: met_help
> >> > >> > >> > > >>> >> > > > Subject: masking land features
questions
> >> > >> > >> > > >>> >> > > > Owner: Nobody
> >> > >> > >> > > >>> >> > > > Requestors:
rosalyn.maccracken at noaa.gov
> >> > >> > >> > > >>> >> > > > Status: new
> >> > >> > >> > > >>> >> > > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Tic
> >> > >> > >> > > >>> >> ket/Display.html?id=86091
> >> > >> > >> > > >>> >> > >
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > Hi,
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > I'm using ASCAT data to verify the
GFS. I
> only
> >> > >> want to
> >> > >> > >> > verify
> >> > >> > >> > > >>> >> points
> >> > >> > >> > > >>> >> > > over
> >> > >> > >> > > >>> >> > > > the ocean, and not over any inland
lakes. I
> >> > noticed
> >> > >> > >> that I
> >> > >> > >> > > was
> >> > >> > >> > > >>> >> getting
> >> > >> > >> > > >>> >> > > > matched points over land (mostly
Africa).
> I'm
> >> > >> dumping
> >> > >> > >> out
> >> > >> > >> > the
> >> > >> > >> > > >>> >> MGDRlite
> >> > >> > >> > > >>> >> > > > file to an ascii file, which I use
ASCII2NC
> to
> >> > >> create
> >> > >> > the
> >> > >> > >> > > netCDF
> >> > >> > >> > > >>> >> file,
> >> > >> > >> > > >>> >> > > and
> >> > >> > >> > > >>> >> > > > then go on to use Point_stat to create
> >> statistics
> >> > >> for
> >> > >> > the
> >> > >> > >> > > >>> matched
> >> > >> > >> > > >>> >> > points.
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > How do I mask out points over land
before it
> >> gets
> >> > to
> >> > >> > the
> >> > >> > >> > > >>> Point_stat
> >> > >> > >> > > >>> >> > step?
> >> > >> > >> > > >>> >> > > > Is there something in the ASCII2NC
processing
> >> > that I
> >> > >> > can
> >> > >> > >> > add,
> >> > >> > >> > > >>> so I
> >> > >> > >> > > >>> >> > don't
> >> > >> > >> > > >>> >> > > > get these matched points?
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > Thanks in advance!
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > Roz
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > --
> >> > >> > >> > > >>> >> > > > Rosalyn MacCracken
> >> > >> > >> > > >>> >> > > > Support Scientist
> >> > >> > >> > > >>> >> > > >
> >> > >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Mon Jul 16 14:25:03 2018
John,
I think that it would be too hard to get someone to install the beta
version to test it. It took us so long to get MET7 to work correctly,
I
doubt that anyone would want to do that.
I do like Option 2:
2) STAT-Analysis supports the "-column_thresh" job command option as
well,
which could be used to filter lat/lon values. For example, here's how
you
could use it to define a lat/lon box: -column_thresh OBS_LAT 'ge-
30&&le30'
-column_thresh OBS_LON 'ge-150&&le-90'
I can define a new lat/lon box, and just rerun everything easily using
the
*.stat files. I already have all my scripts in order to rerun my data
using stat-analysis, so, adding the -column_thresh call would be
easy...I
think.
Roz
On Mon, Jul 16, 2018 at 11:40 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> I have 3 pieces of info for you:
>
> (1) STAT-Analysis supports the "-mask_poly" job command option which
is
> used to specify a lat/lon polyline file. Only those lat/lon's
falling
> inside the polyline region are used. However, defining large
polylines on
> global grids has proved problematic in the past. Sometimes the
logic for
> determining which lat/lon points are *inside* the polyline breaks
down for
> global grids.
>
> (2) STAT-Analysis supports the "-column_thresh" job command option
as well,
> which could be used to filter lat/lon values. For example, here's
how you
> could use it to define a lat/lon box: -column_thresh OBS_LAT 'ge-
30&&le30'
> -column_thresh OBS_LON 'ge-150&&le-90'
>
> (3) Really, the best solution here is to enhance STAT-Analysis to do
> exactly what we want it to do... namely, be able to read the output
of
> Gen-Vx-Mask to define the masking region. But it comes down to
timing. We
> could probably include that in the next beta release for met-7.1 and
have
> it available in a week or two for you to test out.
>
> Thanks,
> John
>
> On Fri, Jul 13, 2018 at 12:52 PM Rosalyn MacCracken - NOAA Affiliate
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >
> > hi John,
> >
> > Maybe I didn't ask the right question. Can I use the same
formatted mask
> > (polyline file with lat/lon), that I used for my point-stat mask,
with
> > stat-analysis with new lat/lon coordinates in the vx_mask option?
Or
> does
> > it have to be the same set of coordinates that I used in the
original
> > point-stat mask file?
> >
> > Roz
> >
> > On Fri, Jul 13, 2018 at 2:08 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > rosalyn.maccracken at noaa.gov> wrote:
> >
> > > Hi John,
> > >
> > > Yeah, I don't know if either solution is going to work. There
isn't
> any
> > > OBS_ID associated with the observation, but, more like a flag in
the
> > > original ASCAT data file. I wouldn't even begin to know how to
figure
> > out
> > > how to translate that into a station id.
> > >
> > > Oh, and I can't just change the mask and rerun stat-analysis. I
would
> > > need to rerun point-stat, and now I'm back to square one...
> > >
> > > So, there is no way to designate a new box to input into the
> > > stat-analysis? You know, like you can indicate the wind speed
> > > threshold...maybe something similar with the lat/lon? Guess
not...
> > >
> > > Roz
> > >
> > > On Thu, Jul 12, 2018 at 2:55 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> Roz,
> > >>
> > >> Yes, that's correct. You'd list that new land mask in the
Point-Stat
> > >> config file to control which points are included.
> > >>
> > >> If I remember correctly, you're running some STAT-Analysis jobs
to
> > >> aggregate MPR lines from previous runs of Point-Stat. And
that's the
> > >> problem, that STAT-Analysis cannot use the output of
gen_vx_mask to
> > >> control
> > >> which MPR lines should be included. Here are two possibilities
for
> > >> solving
> > >> this problem:
> > >>
> > >> (1) The MPR line contains a column named OBS_SID which is the
name of
> > the
> > >> station. If you can, through some means, identify the names of
the
> > >> stations that you *DO* want to use, you could write them out to
an
> ASCII
> > >> file. Then when you run STAT-Analysis jobs, you could use the
> > "-mask_sid"
> > >> option to tell it the names of the stations to be included. I
haven't
> > >> done
> > >> this for large numbers of stations. In principle, the logic
should
> > work.
> > >> In practice, it may be a little slow, checking that long list
of
> > stations
> > >> many times.
> > >>
> > >> (2) We have been doing active development for the next MET
release.
> As
> > we
> > >> add new features, we've been building beta releases and
building them
> on
> > >> NOAA machines (theia, jet, wcoss) for NOAA folks to test out.
The
> > current
> > >> development version is named met-7.1_beta6. I could elevate
the
> > priority
> > >> of that development ticket I sent to you, and enhance stat-
analysis to
> > >> define masking regions using the output of gen_vx_mask. And
then I
> > could
> > >> include it in the next beta release for you to test out. That
would
> > >> certainly be easier for you than generating a list of stations
to use.
> > >> But
> > >> it would take a week or two to get you a new beta release to
test out.
> > >>
> > >> If you decided to go with (1), let me know. I have a
suggestion for
> how
> > >> you might generate that list of stations to include.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA
Affiliate
> via
> > >> RT <
> > >> met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
>
> > >> >
> > >> > Oh, but, I can incorporate this new land mask from here on
out,
> right?
> > >> And,
> > >> > I would add that to my Point-stat config file, like you
showed me to
> > do
> > >> in
> > >> > the previous email, correct?
> > >> >
> > >> > Roz
> > >> >
> > >> > On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA
> Affiliate <
> > >> > rosalyn.maccracken at noaa.gov> wrote:
> > >> >
> > >> > > Hi John,
> > >> > >
> > >> > > There's got to be a way around this...I'm sure there is a
work
> > around
> > >> so
> > >> > > that I don't have to go back an get all of the GFS files.
And, I
> > know
> > >> > that
> > >> > > I want to use STAT-Analysis, since I already have all that
in
> place
> > to
> > >> > > regenerate data.
> > >> > >
> > >> > > So, you said I can use a lat/lon polyline file with STAT-
Analysis.
> > Of
> > >> > > course, I already use that with my North Atlantic or North
Pacific
> > >> masks.
> > >> > > So, my first option might be, make my North Atlantic mask
smaller,
> > >> not to
> > >> > > include West Africa, where the bad observations are
located, and
> > don't
> > >> > use
> > >> > > the global file that is generated (if there a way not to
make that
> > >> file,
> > >> > > and only re-generate files for the North Atlantic?).
Ok...that's
> > one
> > >> > > option, and that's probably what I will have to do.
> > >> > >
> > >> > > Here's the question. So, let's say there was a way for us
to go
> > back
> > >> > > through our ASCAT data, and identify lat/lons of
observations that
> > >> were
> > >> > > flagged not to use, or over land, is there a way to have
> > STAT-Analysis
> > >> > > discard matched pairs associated with those lat/lons?
Maybe,
> that's
> > >> like
> > >> > > using the lat/lon ployline file in reverse? Here's the
mask, use
> > all
> > >> > > observations except if it falls inside this masked domain?
Can we
> > do
> > >> > that?
> > >> > >
> > >> > > Roz
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via RT
<
> > >> > > met_help at ucar.edu> wrote:
> > >> > >
> > >> > >> Roz,
> > >> > >>
> > >> > >> Bad news. I had hoped we could simply pass in the gridded
mask
> > file
> > >> > >> you've
> > >> > >> defined as input to STAT-Analysis using "-mask_poly" but
> > >> unfortunately
> > >> > >> that
> > >> > >> doesn't work.
> > >> > >>
> > >> > >> STAT-Analysis currently supports: -mask_grid, -mask_poly,
and
> > >> -mask_sid
> > >> > to
> > >> > >> filter MPR lines by a named grid, polyline file, or list
of
> station
> > >> id
> > >> > >> names. The other MET tools, like Point-Stat and Grid-Stat
also
> > >> support
> > >> > >> multiple masking options.
> > >> > >>
> > >> > >> For example, in Point-Stat:
> > >> > >> mask = {
> > >> > >> grid = [ "FULL" ];
> > >> > >> poly = [];
> > >> > >> sid = [];
> > >> > >> }
> > >> > >>
> > >> > >> The "mask.grid" option in Point-Stat is the same of "-
mask_grid"
> in
> > >> > >> STAT-Analysis. They both process named grids, like "G212"
for
> NCEP
> > >> grid
> > >> > >> number 212.
> > >> > >>
> > >> > >> Likewise, the "mask.sid" option is the same as "-
mask_sid". They
> > >> both
> > >> > >> define lists of station ID names to be included.
> > >> > >>
> > >> > >> *BUT* the "mask.poly" option in Point-Stat is much more
flexible
> > than
> > >> > >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can
only be
> > set
> > >> to
> > >> > a
> > >> > >> lat/lon polyline file. In Point-Stat, it can also be set
to the
> > >> output
> > >> > of
> > >> > >> gen_vx_mask or any gridded data file followed by a
description of
> > >> data
> > >> > to
> > >> > >> be extracted and thresholded.
> > >> > >>
> > >> > >> We actually have a development task already defined to
address
> this
> > >> > issue
> > >> > >> (see attached).
> > >> > >>
> > >> > >> But that doesn't help you. So unfortunately, with met-
7.0, you'd
> > >> would
> > >> > >> need to go all the way back to generating pairs with
Point-Stat.
> > >> > >>
> > >> > >> However, if you were using a future version of MET, you
could do
> > this
> > >> > all
> > >> > >> in STAT-Analysis.
> > >> > >>
> > >> > >> Thanks,
> > >> > >> John
> > >> > >>
> > >> > >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken - NOAA
> Affiliate
> > >> via
> > >> > >> RT <
> > >> > >> met_help at ucar.edu> wrote:
> > >> > >>
> > >> > >> >
> > >> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> >
> > >> > >> >
> > >> > >> > Hi John,
> > >> > >> >
> > >> > >> > Well, good news. We got our MET7 to work, and I was
able to
> > >> create my
> > >> > >> > ocean mask. It was an issue with conflicts in our
libraries,
> and
> > >> the
> > >> > >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> > >> > >> >
> > >> > >> > Now, I have this ocean mask, and now I can go back and
rerun my
> > >> data.
> > >> > >> So,
> > >> > >> > as usual, I had some questions.
> > >> > >> >
> > >> > >> > I have a series of scripts where you helped me set up
> > STATanalysis
> > >> to
> > >> > >> > reprocess the data using the *.stat files and the -job
> > >> aggregate_stat
> > >> > >> > command . Will I be able to use this method again, or,
because
> > >> it's
> > >> > >> > applying a mask, will I need to get the raw data (GFS
and ASCAT
> > >> data)?
> > >> > >> > And, I guess if I have to use the raw data, I will have
to
> start
> > >> with
> > >> > >> > ASCII2NC, etc, as if I'm processing from scratch,
correct?
> > >> > >> >
> > >> > >> > I just need a sense of how big of a job this is....
> > >> > >> >
> > >> > >> > Thanks for your help!
> > >> > >> >
> > >> > >> > Roz
> > >> > >> >
> > >> > >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken -
NOAA
> > >> Affiliate <
> > >> > >> > rosalyn.maccracken at noaa.gov> wrote:
> > >> > >> >
> > >> > >> > > Oh, yeah, nothing seems to be going smoothly
today...anyway,
> I
> > >> > think I
> > >> > >> > > need to wait until Chris and Fran come in tomorrow to
set our
> > >> > >> directories
> > >> > >> > > correctly to point at MET, and get it running again
before I
> do
> > >> > >> anything
> > >> > >> > > else.
> > >> > >> > >
> > >> > >> > > I'll try this again tomorrow and let you know how I
do.
> > >> > >> > >
> > >> > >> > > Thanks for your help!
> > >> > >> > >
> > >> > >> > > Roz
> > >> > >> > >
> > >> > >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway
via RT <
> > >> > >> > > met_help at ucar.edu> wrote:
> > >> > >> > >
> > >> > >> > >> Roz,
> > >> > >> > >>
> > >> > >> > >> Sorry you're having a rough day. No worries though,
this
> > issue
> > >> is
> > >> > >> easy
> > >> > >> > to
> > >> > >> > >> overcome. Here's a list of pre-defined NCEP grids:
> > >> > >> > >>
http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> > >> > >> > >>
> > >> > >> > >> The intention in MET is to support them using the
naming
> > >> convention
> > >> > >> G###
> > >> > >> > >> where ### is the 3 digit grid number. But if you
look
> closely
> > >> on
> > >> > >> that
> > >> > >> > >> website, you'll see that grid 193 is a relatively new
one
> and
> > is
> > >> > >> listed
> > >> > >> > in
> > >> > >> > >> red. That definition just doesn't exist in MET
version 6.0.
> > >> > >> > >>
> > >> > >> > >> The easy fix is this.... just replace "G193" on the
command
> > line
> > >> > with
> > >> > >> > the
> > >> > >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a
selection
> from
> > >> the
> > >> > >> usage
> > >> > >> > >> statement for regrid_data_plane:
> > >> > >> > >>
> > >> > >> > >> Usage: regrid_data_plane
> > >> > >> > >> input_filename
> > >> > >> > >> to_grid
> > >> > >> > >> output_filename
> > >> > >> > >> "to_grid" defines the output grid as
a named
> > >> grid,
> > >> > >> the
> > >> > >> > >> path
> > >> > >> > >> to a gridded data file, or an explicit grid
specification
> > string
> > >> > >> > >> (required).
> > >> > >> > >>
> > >> > >> > >> When you set "to_grid" equal to a gridded data file,
MET
> reads
> > >> the
> > >> > >> grid
> > >> > >> > >> definition from the first record of that file and
uses it.
> > >> > >> > >>
> > >> > >> > >> That should do it.
> > >> > >> > >>
> > >> > >> > >> Thanks,
> > >> > >> > >> John
> > >> > >> > >>
> > >> > >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken -
NOAA
> > >> Affiliate
> > >> > >> via
> > >> > >> > >> RT <
> > >> > >> > >> met_help at ucar.edu> wrote:
> > >> > >> > >>
> > >> > >> > >> >
> > >> > >> > >> > <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> > >> >
> > >> > >> > >> >
> > >> > >> > >> > Hi John,
> > >> > >> > >> >
> > >> > >> > >> > I'm really not having much luck today with this.
Maybe I
> > >> should
> > >> > >> have
> > >> > >> > >> > stayed in bed (haha).
> > >> > >> > >> >
> > >> > >> > >> > So, the first thing I did was check the
LD_LIBRARY_PATH,
> and
> > >> it's
> > >> > >> > >> pointing
> > >> > >> > >> > to the MET7 directories. Ok, that could be most of
the
> > >> problem.
> > >> > >> MET7
> > >> > >> > >> seems
> > >> > >> > >> > to be having some issue, and the guy here at OPC
that
> helps
> > me
> > >> > with
> > >> > >> > that
> > >> > >> > >> > stuff (Chris Juckins) is out on leave until
tomorrow.
> > Anyway,
> > >> > >> MET7 is
> > >> > >> > >> not
> > >> > >> > >> > running any of my verification programs, and giving
out
> some
> > >> > >> errors,
> > >> > >> > so,
> > >> > >> > >> > I'll have to get with him tomorrow to fix that.
> > >> > >> > >> >
> > >> > >> > >> > So, in the mean time, I don't think that any kind
of land
> > mask
> > >> > >> > creation
> > >> > >> > >> > that I'm doing today will work because it's not
pointing
> at
> > >> the
> > >> > >> right
> > >> > >> > >> > directories.
> > >> > >> > >> >
> > >> > >> > >> > But, when I do get this to work, I tried this and
got this
> > >> error:
> > >> > >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
> > >> gwes01.glo_30m.t00z.grib2
> > >> > >> G193
> > >> > >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> > >> > >> > >> > DEBUG 1: Reading data file:
gwes01.glo_30m.t00z.grib2
> > >> > >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720
Ny: 321
> > >> lat_ll:
> > >> > >> > -80.000
> > >> > >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> > >> > >> > >> > ERROR :
> > >> > >> > >> > ERROR : grd_file_type() -> file does not exist
"G193"
> > >> > >> > >> > ERROR :
> > >> > >> > >> >
> > >> > >> > >> > I'm wondering if that's all related to MET7.
> > >> > >> > >> >
> > >> > >> > >> > So, I think I need to fix the MET7 issue before
moving on
> > with
> > >> > >> this,
> > >> > >> > >> don't
> > >> > >> > >> > you?
> > >> > >> > >> >
> > >> > >> > >> > Roz
> > >> > >> > >> >
> > >> > >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley Gotway
via RT
> <
> > >> > >> > >> > met_help at ucar.edu
> > >> > >> > >> > > wrote:
> > >> > >> > >> >
> > >> > >> > >> > > Roz,
> > >> > >> > >> > >
> > >> > >> > >> > > OK, one other possible option to consider. I
figured
> that
> > >> > >> there's
> > >> > >> > >> plenty
> > >> > >> > >> > > of "ocean" products out there. So I found a NOAA
> > WAVEWATCH
> > >> > one:
> > >> > >> > >> > >
> > >> > >> > >> > > (1) Download sample wavewatch file:
> > >> > >> > >> > > wget
> > >> > >> > >> > >
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > >> > >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> > >> > >> > >> > >
> > >> > >> > >> > > (2) Run regrid_data_plane to put some surface
wind speed
> > >> data
> > >> > on
> > >> > >> the
> > >> > >> > >> 1/4
> > >> > >> > >> > > GFS grid:
> > >> > >> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2
G193
> > >> > >> ocean_data.nc
> > >> > >> > >> -field
> > >> > >> > >> > > 'name="WIND"; level="L0";'
> > >> > >> > >> > >
> > >> > >> > >> > > (3) Run gen_vx_mask to select points that contain
valid
> > >> data:
> > >> > >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc
> ocean_mask.nc
> > >> -type
> > >> > >> data
> > >> > >> > >> > > -mask_field 'name="WIND_L0"; level="L0";' -thresh
> ne-9999
> > >> -name
> > >> > >> > OCEAN
> > >> > >> > >> > >
> > >> > >> > >> > > (4) Run plot_data_plane to see the result:
> > >> > >> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
> > >> 'name="OCEAN";
> > >> > >> > >> > > level="(*,*)";'
> > >> > >> > >> > >
> > >> > >> > >> > > As you can see, the result gets rid of the lakes
> problem.
> > >> But
> > >> > >> > >> wavewatch
> > >> > >> > >> > is
> > >> > >> > >> > > only run to +/- 80 degrees, so we're not
including
> points
> > >> near
> > >> > >> the
> > >> > >> > >> poles.
> > >> > >> > >> > >
> > >> > >> > >> > > Figured this would be a lot easier than running
WPS
> > >> yourself.
> > >> > >> > >> > >
> > >> > >> > >> > > Thanks,
> > >> > >> > >> > > John
> > >> > >> > >> > >
> > >> > >> > >> > >
> > >> > >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley Gotway
<
> > >> > >> johnhg at ucar.edu>
> > >> > >> > >> > wrote:
> > >> > >> > >> > >
> > >> > >> > >> > > > Roz,
> > >> > >> > >> > > >
> > >> > >> > >> > > > I talked to some folks and have one suggestion
that
> > >> *might*
> > >> > >> work.
> > >> > >> > >> The
> > >> > >> > >> > > WRF
> > >> > >> > >> > > > Pre-processing system is named WPS. The
geogrid
> program
> > >> > within
> > >> > >> > WPS
> > >> > >> > >> is
> > >> > >> > >> > > used
> > >> > >> > >> > > > to initialize your domain and handles land use
> > >> information.
> > >> > By
> > >> > >> > >> > default,
> > >> > >> > >> > > > lakes and oceans are treated the same way.
However,
> > >> > apparently
> > >> > >> > >> there
> > >> > >> > >> > is
> > >> > >> > >> > > an
> > >> > >> > >> > > > option to distinguish between them. Take a
look here:
> > >> > >> > >> > > >
> > >> > >> > >> > > > http://www2.mmm.ucar.edu/wrf/
> users/docs/user_guide_V3/
> > >> > >> > >> > > users_guide_chap3.htm#_Description_of_the_1
> > >> > >> > >> > > >
> > >> > >> > >> > > > And search for "Alternative Initialization of
Lake
> > SSTs".
> > >> > >> > >> > > >
> > >> > >> > >> > > > So you'd...
> > >> > >> > >> > > > (1) download the MODIS SST data
> > >> > >> > >> > > > (2) configure geogrid for the 0.25 degree GFS
grid
> > >> > >> > >> > > > (3) configure geogrid to distinguish between
lakes and
> > >> oceans
> > >> > >> > >> > > > (4) run geogrid
> > >> > >> > >> > > > (5) run the output through the MET gen_vx_mask
tool to
> > use
> > >> > >> ocean
> > >> > >> > >> values
> > >> > >> > >> > > > and skip the lake values
> > >> > >> > >> > > >
> > >> > >> > >> > > > Thanks,
> > >> > >> > >> > > > John
> > >> > >> > >> > > >
> > >> > >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley
Gotway <
> > >> > >> > johnhg at ucar.edu>
> > >> > >> > >> > > wrote:
> > >> > >> > >> > > >
> > >> > >> > >> > > >> Roz,
> > >> > >> > >> > > >>
> > >> > >> > >> > > >> Whenever you see that error about loading
shared
> > >> libraries,
> > >> > it
> > >> > >> > >> means
> > >> > >> > >> > > that
> > >> > >> > >> > > >> there's a problem in how your LD_LIBRARY_PATH
> > environment
> > >> > >> > variable
> > >> > >> > >> is
> > >> > >> > >> > > set.
> > >> > >> > >> > > >> That environment variable tells the linker
where to
> > look
> > >> for
> > >> > >> > shared
> > >> > >> > >> > > >> libraries at runtime... one of those shared
libraries
> > is
> > >> GSL
> > >> > >> (GNU
> > >> > >> > >> > > >> Scientific Library). You'd "fix" this issue
by
> > modifying
> > >> > how
> > >> > >> > >> > > >> LD_LIBRARY_PATH is set:
> > >> > >> > >> > > >> echo $LD_LIBRARY_PATH
> > >> > >> > >> > > >>
> > >> > >> > >> > > >> Take a look in your ~/.cshrc file for c-shell
or
> > >> ~/.bashrc
> > >> > for
> > >> > >> > >> bash to
> > >> > >> > >> > > >> see how its set.
> > >> > >> > >> > > >>
> > >> > >> > >> > > >> As for the LAND/SEA mask, I was wondering if
those
> > lakes
> > >> > would
> > >> > >> > be a
> > >> > >> > >> > > >> problem. Using the model's LAND/SEA mask is
the
> > easiest,
> > >> > but
> > >> > >> > >> doesn't
> > >> > >> > >> > > >> provide an easy way of selecting out oceans.
My next
> > >> > thought
> > >> > >> was
> > >> > >> > >> to
> > >> > >> > >> > use
> > >> > >> > >> > > >> GIS Shapefiles to define only the ocean area.
That
> > will
> > >> be
> > >> > >> > >> available
> > >> > >> > >> > in
> > >> > >> > >> > > >> the next version of MET, version 7.1. I tried
using
> a
> > >> beta
> > >> > >> > release
> > >> > >> > >> > for
> > >> > >> > >> > > >> met-7.1, but ran into problems when applying
large
> > >> polylines
> > >> > >> to
> > >> > >> > >> global
> > >> > >> > >> > > >> grids.
> > >> > >> > >> > > >>
> > >> > >> > >> > > >> I'll keep thinking about that one.
> > >> > >> > >> > > >>
> > >> > >> > >> > > >> Thanks,
> > >> > >> > >> > > >> John
> > >> > >> > >> > > >>
> > >> > >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn
MacCracken -
> > NOAA
> > >> > >> > Affiliate
> > >> > >> > >> > via
> > >> > >> > >> > > >> RT <met_help at ucar.edu> wrote:
> > >> > >> > >> > > >>
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
> > >> > >> ket/Display.html?id=86091 >
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> Hey John,
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> I have 2 problems. First, I'm able to use
> > >> plot_data_plane,
> > >> > >> but,
> > >> > >> > >> > when I
> > >> > >> > >> > > >>> use
> > >> > >> > >> > > >>> the command for gen_vx_mask, I get this:
> > >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
> > >> gfs.t00z.pgrb2.0p25.f000
> > >> > >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000 gfs_4_WATER_mask.nc
-type
> > data
> > >> > >> > >> -mask_field
> > >> > >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0 -name
WATER
> > >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error while
> loading
> > >> > shared
> > >> > >> > >> > > libraries:
> > >> > >> > >> > > >>> libgsl.so.0: cannot open shared object file:
No such
> > >> file
> > >> > or
> > >> > >> > >> > directory
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> Now, they are both in the same directory, and
I know
> > >> that
> > >> > >> I've
> > >> > >> > >> used
> > >> > >> > >> > > >>> gen_vx_mask before, so, I have no idea why I
would
> be
> > >> > getting
> > >> > >> > that
> > >> > >> > >> > > error
> > >> > >> > >> > > >>> message. Any ideas?
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> Then, I was able to generate a *.ps file,
which
> looks
> > >> > exactly
> > >> > >> > like
> > >> > >> > >> > > yours,
> > >> > >> > >> > > >>> but, there is still the same problem. If you
look
> > >> closely
> > >> > >> are
> > >> > >> > >> your
> > >> > >> > >> > > map,
> > >> > >> > >> > > >>> you'll see these little white dots over land.
Those
> > are
> > >> > >> lakes,
> > >> > >> > >> and
> > >> > >> > >> > > >>> that's
> > >> > >> > >> > > >>> what is giving me a fit, because I have ASCAT
> > >> observations
> > >> > >> over
> > >> > >> > >> those
> > >> > >> > >> > > >>> white
> > >> > >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS data
with 12
> > km
> > >> > ASCAT
> > >> > >> > >> > > data...so,
> > >> > >> > >> > > >>> very sensitive. Anyway, do you have any idea
how to
> > get
> > >> > rid
> > >> > >> of
> > >> > >> > >> those
> > >> > >> > >> > > >>> points? Perhaps a different file with the
same
> > domain?
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> Roz
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn
MacCracken -
> > >> NOAA
> > >> > >> > >> Affiliate <
> > >> > >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> > >> > >> > >> > > >>>
> > >> > >> > >> > > >>> > Ok, I'll let you know if I can get the mask
to
> work.
> > >> > This
> > >> > >> > seems
> > >> > >> > >> > easy
> > >> > >> > >> > > >>> > enough, and pretty straight forward.
> > >> > >> > >> > > >>> >
> > >> > >> > >> > > >>> > Thanks for the help!
> > >> > >> > >> > > >>> >
> > >> > >> > >> > > >>> > Roz
> > >> > >> > >> > > >>> >
> > >> > >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John Halley
Gotway
> > via
> > >> > RT <
> > >> > >> > >> > > >>> > met_help at ucar.edu> wrote:
> > >> > >> > >> > > >>> >
> > >> > >> > >> > > >>> >> Roz,
> > >> > >> > >> > > >>> >>
> > >> > >> > >> > > >>> >> Yes, I expect that using met-6.0 would
work fine.
> > >> Hope
> > >> > it
> > >> > >> > goes
> > >> > >> > >> > > >>> smoothly.
> > >> > >> > >> > > >>> >>
> > >> > >> > >> > > >>> >> Thanks,
> > >> > >> > >> > > >>> >> John
> > >> > >> > >> > > >>> >>
> > >> > >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn
> MacCracken -
> > >> NOAA
> > >> > >> > >> Affiliate
> > >> > >> > >> > > >>> via RT
> > >> > >> > >> > > >>> >> <
> > >> > >> > >> > > >>> >> met_help at ucar.edu> wrote:
> > >> > >> > >> > > >>> >>
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> > >> > >> > >> ket/Display.html?id=86091 >
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > Hi John,
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > I get the general idea and it looks
pretty
> > straight
> > >> > >> > forward.
> > >> > >> > >> > I'm
> > >> > >> > >> > > >>> still
> > >> > >> > >> > > >>> >> > running MET6.0, since we had some
installation
> > >> issues,
> > >> > >> > but, I
> > >> > >> > >> > > >>> should be
> > >> > >> > >> > > >>> >> > able to generate the mask with that
pretty
> > easily,
> > >> > >> correct?
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > So, if this works, I'll need to rerun
all my
> data
> > >> from
> > >> > >> Mar
> > >> > >> > >> 2018
> > >> > >> > >> > -
> > >> > >> > >> > > >>> >> present,
> > >> > >> > >> > > >>> >> > using that method that we worked out
earlier
> with
> > >> the
> > >> > >> > *.stat
> > >> > >> > >> > > files,
> > >> > >> > >> > > >>> >> > correct? Actually, I don't need to do
that...I
> > can
> > >> > >> start
> > >> > >> > >> from
> > >> > >> > >> > the
> > >> > >> > >> > > >>> ASCII
> > >> > >> > >> > > >>> >> > files I've already generated, and then
just
> rerun
> > >> > >> > POINT_STAT
> > >> > >> > >> > with
> > >> > >> > >> > > >>> the
> > >> > >> > >> > > >>> >> > mask. Ok, that will save some steps.
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > Alright, I'll try making the mask and do
a test
> > run
> > >> > >> after
> > >> > >> > >> lunch,
> > >> > >> > >> > > >>> and get
> > >> > >> > >> > > >>> >> > back to you when it works.
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > Thanks!
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > Roz
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John
Halley
> > Gotway
> > >> via
> > >> > >> RT <
> > >> > >> > >> > > >>> >> > met_help at ucar.edu
> > >> > >> > >> > > >>> >> > > wrote:
> > >> > >> > >> > > >>> >> >
> > >> > >> > >> > > >>> >> > > Hi Roz,
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > I see you're wondering how to only use
point
> > >> > >> observations
> > >> > >> > >> over
> > >> > >> > >> > > >>> water
> > >> > >> > >> > > >>> >> and
> > >> > >> > >> > > >>> >> > > discard the ones over land. You're
running
> > >> ASCII2NC
> > >> > >> > >> followed
> > >> > >> > >> > by
> > >> > >> > >> > > >>> >> > Point-Stat
> > >> > >> > >> > > >>> >> > > and want to know where/how to define
that
> > >> masking.
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > The ASCII2NC tool supports 3 command
line
> > options
> > >> > for
> > >> > >> > >> > filtering
> > >> > >> > >> > > >>> point
> > >> > >> > >> > > >>> >> > > observations spatially: -mask_grid,
> -mask_poly,
> > >> and
> > >> > >> > >> -mask_sid,
> > >> > >> > >> > > for
> > >> > >> > >> > > >>> >> grid,
> > >> > >> > >> > > >>> >> > > polyline, and station ID masking,
> respectively.
> > >> But
> > >> > >> > that's
> > >> > >> > >> > not
> > >> > >> > >> > > >>> really
> > >> > >> > >> > > >>> >> > what
> > >> > >> > >> > > >>> >> > > you want. You want to do "data
masking"
> where
> > >> you
> > >> > >> read
> > >> > >> > in
> > >> > >> > >> a
> > >> > >> > >> > > >>> land/sea
> > >> > >> > >> > > >>> >> > mask
> > >> > >> > >> > > >>> >> > > and only use the points over water.
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-Mask
tool to
> > >> create
> > >> > >> the
> > >> > >> > >> > desired
> > >> > >> > >> > > >>> >> masking
> > >> > >> > >> > > >>> >> > > region, and then reference that in the
> > Point-Stat
> > >> > >> config
> > >> > >> > >> file.
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > To illustrate, I pulled a sample GFS
file:
> > >> > >> > >> > > >>> >> > > > wget
> > >> > >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> > >> > >> > >> ata/gfs4/201807/20180702/gfs_
> > >> > >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA
mask:
> > >> > >> > >> > > >>> >> > > > wgrib2
gfs_4_20180702_0000_012.grb2 |
> egrep
> > >> -i
> > >> > >> LAND
> > >> > >> > >> > > >>> >> > > 400:65422867:d=2018070200:
> LAND:surface:12
> > >> hour
> > >> > >> > fcst:
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > Run plot_data_plane to see it (see
attached
> > >> image):
> > >> > >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> > >> > >> > >> gfs_4_20180702_0000_012.grb2
> > >> > >> > >> > > >>> >> > gfs_4_LAND.ps
> > >> > >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > Run gen_vx_mask to create a mask for
your
> > >> > verification
> > >> > >> > >> domain.
> > >> > >> > >> > > If
> > >> > >> > >> > > >>> >> you're
> > >> > >> > >> > > >>> >> > > actually verifying on the GFS domain,
the
> > command
> > >> > >> looks a
> > >> > >> > >> > little
> > >> > >> > >> > > >>> >> > redundant:
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > > /usr/local/met-7.0/bin/gen_vx_mask
\
> > >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > >> > >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> > >> > >> > >> > > >>> >> > > -type data \
> > >> > >> > >> > > >>> >> > > -mask_field 'name="LAND";
level="L0";' \
> > >> > >> > >> > > >>> >> > > -thresh ==0 \
> > >> > >> > >> > > >>> >> > > -name WATER
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > I defined the threshold as "==0"
because we
> > want
> > >> the
> > >> > >> > WATER
> > >> > >> > >> > > >>> points, not
> > >> > >> > >> > > >>> >> > the
> > >> > >> > >> > > >>> >> > > LAND points. And I used the "-name
WATER"
> > >> command
> > >> > >> line
> > >> > >> > >> option
> > >> > >> > >> > > to
> > >> > >> > >> > > >>> name
> > >> > >> > >> > > >>> >> > the
> > >> > >> > >> > > >>> >> > > output NetCDF variable. This will
show up in
> > the
> > >> > >> VX_MASK
> > >> > >> > >> > output
> > >> > >> > >> > > >>> >> column
> > >> > >> > >> > > >>> >> > of
> > >> > >> > >> > > >>> >> > > Point-Stat.
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > Lastly, setup your Point-Stat config
file
> like
> > >> this:
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > mask = {
> > >> > >> > >> > > >>> >> > > grid = [];
> > >> > >> > >> > > >>> >> > > poly = [
"/path/to/gfs_4_WATER_mask.nc"
> > ];
> > >> > >> > >> > > >>> >> > > sid = [];
> > >> > >> > >> > > >>> >> > > }
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > Hope that helps clarify.
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > Thanks,
> > >> > >> > >> > > >>> >> > > John
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM Rosalyn
> > >> MacCracken -
> > >> > >> NOAA
> > >> > >> > >> > > >>> Affiliate via
> > >> > >> > >> > > >>> >> > RT <
> > >> > >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request
86091 was
> > >> acted
> > >> > >> upon.
> > >> > >> > >> > > >>> >> > > > Transaction: Ticket created by
> > >> > >> > >> rosalyn.maccracken at noaa.gov
> > >> > >> > >> > > >>> >> > > > Queue: met_help
> > >> > >> > >> > > >>> >> > > > Subject: masking land features
> questions
> > >> > >> > >> > > >>> >> > > > Owner: Nobody
> > >> > >> > >> > > >>> >> > > > Requestors:
rosalyn.maccracken at noaa.gov
> > >> > >> > >> > > >>> >> > > > Status: new
> > >> > >> > >> > > >>> >> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Tic
> > >> > >> > >> > > >>> >> ket/Display.html?id=86091
> > >> > >> > >> > > >>> >> > >
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > Hi,
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > I'm using ASCAT data to verify the
GFS. I
> > only
> > >> > >> want to
> > >> > >> > >> > verify
> > >> > >> > >> > > >>> >> points
> > >> > >> > >> > > >>> >> > > over
> > >> > >> > >> > > >>> >> > > > the ocean, and not over any inland
lakes.
> I
> > >> > noticed
> > >> > >> > >> that I
> > >> > >> > >> > > was
> > >> > >> > >> > > >>> >> getting
> > >> > >> > >> > > >>> >> > > > matched points over land (mostly
Africa).
> > I'm
> > >> > >> dumping
> > >> > >> > >> out
> > >> > >> > >> > the
> > >> > >> > >> > > >>> >> MGDRlite
> > >> > >> > >> > > >>> >> > > > file to an ascii file, which I use
ASCII2NC
> > to
> > >> > >> create
> > >> > >> > the
> > >> > >> > >> > > netCDF
> > >> > >> > >> > > >>> >> file,
> > >> > >> > >> > > >>> >> > > and
> > >> > >> > >> > > >>> >> > > > then go on to use Point_stat to
create
> > >> statistics
> > >> > >> for
> > >> > >> > the
> > >> > >> > >> > > >>> matched
> > >> > >> > >> > > >>> >> > points.
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > How do I mask out points over land
before
> it
> > >> gets
> > >> > to
> > >> > >> > the
> > >> > >> > >> > > >>> Point_stat
> > >> > >> > >> > > >>> >> > step?
> > >> > >> > >> > > >>> >> > > > Is there something in the ASCII2NC
> processing
> > >> > that I
> > >> > >> > can
> > >> > >> > >> > add,
> > >> > >> > >> > > >>> so I
> > >> > >> > >> > > >>> >> > don't
> > >> > >> > >> > > >>> >> > > > get these matched points?
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > Thanks in advance!
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > Roz
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > --
> > >> > >> > >> > > >>> >> > > > Rosalyn MacCracken
> > >> > >> > >> > > >>> >> > > > Support Scientist
> > >> > >> > >> > > >>> >> > > >
> > >> > >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: John Halley Gotway
Time: Mon Jul 16 14:46:29 2018
Roz,
OK, great. I'll close this ticket for now. Just let us know if more
issues or questions arise.
Thanks,
John
On Mon, Jul 16, 2018 at 2:25 PM Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
>
> John,
>
> I think that it would be too hard to get someone to install the beta
> version to test it. It took us so long to get MET7 to work
correctly, I
> doubt that anyone would want to do that.
>
> I do like Option 2:
> 2) STAT-Analysis supports the "-column_thresh" job command option
as well,
> which could be used to filter lat/lon values. For example, here's
how you
> could use it to define a lat/lon box: -column_thresh OBS_LAT 'ge-
30&&le30'
> -column_thresh OBS_LON 'ge-150&&le-90'
>
> I can define a new lat/lon box, and just rerun everything easily
using the
> *.stat files. I already have all my scripts in order to rerun my
data
> using stat-analysis, so, adding the -column_thresh call would be
easy...I
> think.
>
> Roz
>
> On Mon, Jul 16, 2018 at 11:40 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Roz,
> >
> > I have 3 pieces of info for you:
> >
> > (1) STAT-Analysis supports the "-mask_poly" job command option
which is
> > used to specify a lat/lon polyline file. Only those lat/lon's
falling
> > inside the polyline region are used. However, defining large
polylines
> on
> > global grids has proved problematic in the past. Sometimes the
logic for
> > determining which lat/lon points are *inside* the polyline breaks
down
> for
> > global grids.
> >
> > (2) STAT-Analysis supports the "-column_thresh" job command option
as
> well,
> > which could be used to filter lat/lon values. For example, here's
how
> you
> > could use it to define a lat/lon box: -column_thresh OBS_LAT
> 'ge-30&&le30'
> > -column_thresh OBS_LON 'ge-150&&le-90'
> >
> > (3) Really, the best solution here is to enhance STAT-Analysis to
do
> > exactly what we want it to do... namely, be able to read the
output of
> > Gen-Vx-Mask to define the masking region. But it comes down to
timing.
> We
> > could probably include that in the next beta release for met-7.1
and have
> > it available in a week or two for you to test out.
> >
> > Thanks,
> > John
> >
> > On Fri, Jul 13, 2018 at 12:52 PM Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> > >
> > > hi John,
> > >
> > > Maybe I didn't ask the right question. Can I use the same
formatted
> mask
> > > (polyline file with lat/lon), that I used for my point-stat
mask, with
> > > stat-analysis with new lat/lon coordinates in the vx_mask
option? Or
> > does
> > > it have to be the same set of coordinates that I used in the
original
> > > point-stat mask file?
> > >
> > > Roz
> > >
> > > On Fri, Jul 13, 2018 at 2:08 PM, Rosalyn MacCracken - NOAA
Affiliate <
> > > rosalyn.maccracken at noaa.gov> wrote:
> > >
> > > > Hi John,
> > > >
> > > > Yeah, I don't know if either solution is going to work. There
isn't
> > any
> > > > OBS_ID associated with the observation, but, more like a flag
in the
> > > > original ASCAT data file. I wouldn't even begin to know how
to
> figure
> > > out
> > > > how to translate that into a station id.
> > > >
> > > > Oh, and I can't just change the mask and rerun stat-analysis.
I
> would
> > > > need to rerun point-stat, and now I'm back to square one...
> > > >
> > > > So, there is no way to designate a new box to input into the
> > > > stat-analysis? You know, like you can indicate the wind speed
> > > > threshold...maybe something similar with the lat/lon? Guess
not...
> > > >
> > > > Roz
> > > >
> > > > On Thu, Jul 12, 2018 at 2:55 PM, John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > >> Roz,
> > > >>
> > > >> Yes, that's correct. You'd list that new land mask in the
> Point-Stat
> > > >> config file to control which points are included.
> > > >>
> > > >> If I remember correctly, you're running some STAT-Analysis
jobs to
> > > >> aggregate MPR lines from previous runs of Point-Stat. And
that's
> the
> > > >> problem, that STAT-Analysis cannot use the output of
gen_vx_mask to
> > > >> control
> > > >> which MPR lines should be included. Here are two
possibilities for
> > > >> solving
> > > >> this problem:
> > > >>
> > > >> (1) The MPR line contains a column named OBS_SID which is the
name
> of
> > > the
> > > >> station. If you can, through some means, identify the names
of the
> > > >> stations that you *DO* want to use, you could write them out
to an
> > ASCII
> > > >> file. Then when you run STAT-Analysis jobs, you could use
the
> > > "-mask_sid"
> > > >> option to tell it the names of the stations to be included.
I
> haven't
> > > >> done
> > > >> this for large numbers of stations. In principle, the logic
should
> > > work.
> > > >> In practice, it may be a little slow, checking that long list
of
> > > stations
> > > >> many times.
> > > >>
> > > >> (2) We have been doing active development for the next MET
release.
> > As
> > > we
> > > >> add new features, we've been building beta releases and
building
> them
> > on
> > > >> NOAA machines (theia, jet, wcoss) for NOAA folks to test out.
The
> > > current
> > > >> development version is named met-7.1_beta6. I could elevate
the
> > > priority
> > > >> of that development ticket I sent to you, and enhance stat-
analysis
> to
> > > >> define masking regions using the output of gen_vx_mask. And
then I
> > > could
> > > >> include it in the next beta release for you to test out.
That would
> > > >> certainly be easier for you than generating a list of
stations to
> use.
> > > >> But
> > > >> it would take a week or two to get you a new beta release to
test
> out.
> > > >>
> > > >> If you decided to go with (1), let me know. I have a
suggestion for
> > how
> > > >> you might generate that list of stations to include.
> > > >>
> > > >> Thanks,
> > > >> John
> > > >>
> > > >> On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA
Affiliate
> > via
> > > >> RT <
> > > >> met_help at ucar.edu> wrote:
> > > >>
> > > >> >
> > > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> > > >> >
> > > >> > Oh, but, I can incorporate this new land mask from here on
out,
> > right?
> > > >> And,
> > > >> > I would add that to my Point-stat config file, like you
showed me
> to
> > > do
> > > >> in
> > > >> > the previous email, correct?
> > > >> >
> > > >> > Roz
> > > >> >
> > > >> > On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken - NOAA
> > Affiliate <
> > > >> > rosalyn.maccracken at noaa.gov> wrote:
> > > >> >
> > > >> > > Hi John,
> > > >> > >
> > > >> > > There's got to be a way around this...I'm sure there is a
work
> > > around
> > > >> so
> > > >> > > that I don't have to go back an get all of the GFS files.
And,
> I
> > > know
> > > >> > that
> > > >> > > I want to use STAT-Analysis, since I already have all
that in
> > place
> > > to
> > > >> > > regenerate data.
> > > >> > >
> > > >> > > So, you said I can use a lat/lon polyline file with
> STAT-Analysis.
> > > Of
> > > >> > > course, I already use that with my North Atlantic or
North
> Pacific
> > > >> masks.
> > > >> > > So, my first option might be, make my North Atlantic mask
> smaller,
> > > >> not to
> > > >> > > include West Africa, where the bad observations are
located, and
> > > don't
> > > >> > use
> > > >> > > the global file that is generated (if there a way not to
make
> that
> > > >> file,
> > > >> > > and only re-generate files for the North Atlantic?).
> Ok...that's
> > > one
> > > >> > > option, and that's probably what I will have to do.
> > > >> > >
> > > >> > > Here's the question. So, let's say there was a way for
us to go
> > > back
> > > >> > > through our ASCAT data, and identify lat/lons of
observations
> that
> > > >> were
> > > >> > > flagged not to use, or over land, is there a way to have
> > > STAT-Analysis
> > > >> > > discard matched pairs associated with those lat/lons?
Maybe,
> > that's
> > > >> like
> > > >> > > using the lat/lon ployline file in reverse? Here's the
mask,
> use
> > > all
> > > >> > > observations except if it falls inside this masked
domain? Can
> we
> > > do
> > > >> > that?
> > > >> > >
> > > >> > > Roz
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via
RT <
> > > >> > > met_help at ucar.edu> wrote:
> > > >> > >
> > > >> > >> Roz,
> > > >> > >>
> > > >> > >> Bad news. I had hoped we could simply pass in the
gridded mask
> > > file
> > > >> > >> you've
> > > >> > >> defined as input to STAT-Analysis using "-mask_poly" but
> > > >> unfortunately
> > > >> > >> that
> > > >> > >> doesn't work.
> > > >> > >>
> > > >> > >> STAT-Analysis currently supports: -mask_grid,
-mask_poly, and
> > > >> -mask_sid
> > > >> > to
> > > >> > >> filter MPR lines by a named grid, polyline file, or list
of
> > station
> > > >> id
> > > >> > >> names. The other MET tools, like Point-Stat and Grid-
Stat also
> > > >> support
> > > >> > >> multiple masking options.
> > > >> > >>
> > > >> > >> For example, in Point-Stat:
> > > >> > >> mask = {
> > > >> > >> grid = [ "FULL" ];
> > > >> > >> poly = [];
> > > >> > >> sid = [];
> > > >> > >> }
> > > >> > >>
> > > >> > >> The "mask.grid" option in Point-Stat is the same of
> "-mask_grid"
> > in
> > > >> > >> STAT-Analysis. They both process named grids, like
"G212" for
> > NCEP
> > > >> grid
> > > >> > >> number 212.
> > > >> > >>
> > > >> > >> Likewise, the "mask.sid" option is the same as "-
mask_sid".
> They
> > > >> both
> > > >> > >> define lists of station ID names to be included.
> > > >> > >>
> > > >> > >> *BUT* the "mask.poly" option in Point-Stat is much more
> flexible
> > > than
> > > >> > >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it can
only
> be
> > > set
> > > >> to
> > > >> > a
> > > >> > >> lat/lon polyline file. In Point-Stat, it can also be
set to
> the
> > > >> output
> > > >> > of
> > > >> > >> gen_vx_mask or any gridded data file followed by a
description
> of
> > > >> data
> > > >> > to
> > > >> > >> be extracted and thresholded.
> > > >> > >>
> > > >> > >> We actually have a development task already defined to
address
> > this
> > > >> > issue
> > > >> > >> (see attached).
> > > >> > >>
> > > >> > >> But that doesn't help you. So unfortunately, with met-
7.0,
> you'd
> > > >> would
> > > >> > >> need to go all the way back to generating pairs with
> Point-Stat.
> > > >> > >>
> > > >> > >> However, if you were using a future version of MET, you
could
> do
> > > this
> > > >> > all
> > > >> > >> in STAT-Analysis.
> > > >> > >>
> > > >> > >> Thanks,
> > > >> > >> John
> > > >> > >>
> > > >> > >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken -
NOAA
> > Affiliate
> > > >> via
> > > >> > >> RT <
> > > >> > >> met_help at ucar.edu> wrote:
> > > >> > >>
> > > >> > >> >
> > > >> > >> > <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> > >
> > > >> > >> >
> > > >> > >> > Hi John,
> > > >> > >> >
> > > >> > >> > Well, good news. We got our MET7 to work, and I was
able to
> > > >> create my
> > > >> > >> > ocean mask. It was an issue with conflicts in our
libraries,
> > and
> > > >> the
> > > >> > >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> > > >> > >> >
> > > >> > >> > Now, I have this ocean mask, and now I can go back and
rerun
> my
> > > >> data.
> > > >> > >> So,
> > > >> > >> > as usual, I had some questions.
> > > >> > >> >
> > > >> > >> > I have a series of scripts where you helped me set up
> > > STATanalysis
> > > >> to
> > > >> > >> > reprocess the data using the *.stat files and the -job
> > > >> aggregate_stat
> > > >> > >> > command . Will I be able to use this method again,
or,
> because
> > > >> it's
> > > >> > >> > applying a mask, will I need to get the raw data (GFS
and
> ASCAT
> > > >> data)?
> > > >> > >> > And, I guess if I have to use the raw data, I will
have to
> > start
> > > >> with
> > > >> > >> > ASCII2NC, etc, as if I'm processing from scratch,
correct?
> > > >> > >> >
> > > >> > >> > I just need a sense of how big of a job this is....
> > > >> > >> >
> > > >> > >> > Thanks for your help!
> > > >> > >> >
> > > >> > >> > Roz
> > > >> > >> >
> > > >> > >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken -
NOAA
> > > >> Affiliate <
> > > >> > >> > rosalyn.maccracken at noaa.gov> wrote:
> > > >> > >> >
> > > >> > >> > > Oh, yeah, nothing seems to be going smoothly
> today...anyway,
> > I
> > > >> > think I
> > > >> > >> > > need to wait until Chris and Fran come in tomorrow
to set
> our
> > > >> > >> directories
> > > >> > >> > > correctly to point at MET, and get it running again
before
> I
> > do
> > > >> > >> anything
> > > >> > >> > > else.
> > > >> > >> > >
> > > >> > >> > > I'll try this again tomorrow and let you know how I
do.
> > > >> > >> > >
> > > >> > >> > > Thanks for your help!
> > > >> > >> > >
> > > >> > >> > > Roz
> > > >> > >> > >
> > > >> > >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley Gotway
via RT
> <
> > > >> > >> > > met_help at ucar.edu> wrote:
> > > >> > >> > >
> > > >> > >> > >> Roz,
> > > >> > >> > >>
> > > >> > >> > >> Sorry you're having a rough day. No worries
though, this
> > > issue
> > > >> is
> > > >> > >> easy
> > > >> > >> > to
> > > >> > >> > >> overcome. Here's a list of pre-defined NCEP grids:
> > > >> > >> > >>
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> > > >> > >> > >>
> > > >> > >> > >> The intention in MET is to support them using the
naming
> > > >> convention
> > > >> > >> G###
> > > >> > >> > >> where ### is the 3 digit grid number. But if you
look
> > closely
> > > >> on
> > > >> > >> that
> > > >> > >> > >> website, you'll see that grid 193 is a relatively
new one
> > and
> > > is
> > > >> > >> listed
> > > >> > >> > in
> > > >> > >> > >> red. That definition just doesn't exist in MET
version
> 6.0.
> > > >> > >> > >>
> > > >> > >> > >> The easy fix is this.... just replace "G193" on the
> command
> > > line
> > > >> > with
> > > >> > >> > the
> > > >> > >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a
selection
> > from
> > > >> the
> > > >> > >> usage
> > > >> > >> > >> statement for regrid_data_plane:
> > > >> > >> > >>
> > > >> > >> > >> Usage: regrid_data_plane
> > > >> > >> > >> input_filename
> > > >> > >> > >> to_grid
> > > >> > >> > >> output_filename
> > > >> > >> > >> "to_grid" defines the output grid
as a
> named
> > > >> grid,
> > > >> > >> the
> > > >> > >> > >> path
> > > >> > >> > >> to a gridded data file, or an explicit grid
specification
> > > string
> > > >> > >> > >> (required).
> > > >> > >> > >>
> > > >> > >> > >> When you set "to_grid" equal to a gridded data
file, MET
> > reads
> > > >> the
> > > >> > >> grid
> > > >> > >> > >> definition from the first record of that file and
uses it.
> > > >> > >> > >>
> > > >> > >> > >> That should do it.
> > > >> > >> > >>
> > > >> > >> > >> Thanks,
> > > >> > >> > >> John
> > > >> > >> > >>
> > > >> > >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn MacCracken
- NOAA
> > > >> Affiliate
> > > >> > >> via
> > > >> > >> > >> RT <
> > > >> > >> > >> met_help at ucar.edu> wrote:
> > > >> > >> > >>
> > > >> > >> > >> >
> > > >> > >> > >> > <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> > > >> >
> > > >> > >> > >> >
> > > >> > >> > >> > Hi John,
> > > >> > >> > >> >
> > > >> > >> > >> > I'm really not having much luck today with this.
Maybe
> I
> > > >> should
> > > >> > >> have
> > > >> > >> > >> > stayed in bed (haha).
> > > >> > >> > >> >
> > > >> > >> > >> > So, the first thing I did was check the
LD_LIBRARY_PATH,
> > and
> > > >> it's
> > > >> > >> > >> pointing
> > > >> > >> > >> > to the MET7 directories. Ok, that could be most
of the
> > > >> problem.
> > > >> > >> MET7
> > > >> > >> > >> seems
> > > >> > >> > >> > to be having some issue, and the guy here at OPC
that
> > helps
> > > me
> > > >> > with
> > > >> > >> > that
> > > >> > >> > >> > stuff (Chris Juckins) is out on leave until
tomorrow.
> > > Anyway,
> > > >> > >> MET7 is
> > > >> > >> > >> not
> > > >> > >> > >> > running any of my verification programs, and
giving out
> > some
> > > >> > >> errors,
> > > >> > >> > so,
> > > >> > >> > >> > I'll have to get with him tomorrow to fix that.
> > > >> > >> > >> >
> > > >> > >> > >> > So, in the mean time, I don't think that any kind
of
> land
> > > mask
> > > >> > >> > creation
> > > >> > >> > >> > that I'm doing today will work because it's not
pointing
> > at
> > > >> the
> > > >> > >> right
> > > >> > >> > >> > directories.
> > > >> > >> > >> >
> > > >> > >> > >> > But, when I do get this to work, I tried this and
got
> this
> > > >> error:
> > > >> > >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
> > > >> gwes01.glo_30m.t00z.grib2
> > > >> > >> G193
> > > >> > >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> > > >> > >> > >> > DEBUG 1: Reading data file:
gwes01.glo_30m.t00z.grib2
> > > >> > >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 720
Ny: 321
> > > >> lat_ll:
> > > >> > >> > -80.000
> > > >> > >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon: 0.500
> > > >> > >> > >> > ERROR :
> > > >> > >> > >> > ERROR : grd_file_type() -> file does not exist
"G193"
> > > >> > >> > >> > ERROR :
> > > >> > >> > >> >
> > > >> > >> > >> > I'm wondering if that's all related to MET7.
> > > >> > >> > >> >
> > > >> > >> > >> > So, I think I need to fix the MET7 issue before
moving
> on
> > > with
> > > >> > >> this,
> > > >> > >> > >> don't
> > > >> > >> > >> > you?
> > > >> > >> > >> >
> > > >> > >> > >> > Roz
> > > >> > >> > >> >
> > > >> > >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley
Gotway via
> RT
> > <
> > > >> > >> > >> > met_help at ucar.edu
> > > >> > >> > >> > > wrote:
> > > >> > >> > >> >
> > > >> > >> > >> > > Roz,
> > > >> > >> > >> > >
> > > >> > >> > >> > > OK, one other possible option to consider. I
figured
> > that
> > > >> > >> there's
> > > >> > >> > >> plenty
> > > >> > >> > >> > > of "ocean" products out there. So I found a
NOAA
> > > WAVEWATCH
> > > >> > one:
> > > >> > >> > >> > >
> > > >> > >> > >> > > (1) Download sample wavewatch file:
> > > >> > >> > >> > > wget
> > > >> > >> > >> > >
> ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > > >> > >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> > > >> > >> > >> > >
> > > >> > >> > >> > > (2) Run regrid_data_plane to put some surface
wind
> speed
> > > >> data
> > > >> > on
> > > >> > >> the
> > > >> > >> > >> 1/4
> > > >> > >> > >> > > GFS grid:
> > > >> > >> > >> > > regrid_data_plane gwes01.glo_30m.t00z.grib2
G193
> > > >> > >> ocean_data.nc
> > > >> > >> > >> -field
> > > >> > >> > >> > > 'name="WIND"; level="L0";'
> > > >> > >> > >> > >
> > > >> > >> > >> > > (3) Run gen_vx_mask to select points that
contain
> valid
> > > >> data:
> > > >> > >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc
> > ocean_mask.nc
> > > >> -type
> > > >> > >> data
> > > >> > >> > >> > > -mask_field 'name="WIND_L0"; level="L0";'
-thresh
> > ne-9999
> > > >> -name
> > > >> > >> > OCEAN
> > > >> > >> > >> > >
> > > >> > >> > >> > > (4) Run plot_data_plane to see the result:
> > > >> > >> > >> > > plot_data_plane ocean_mask.nc ocean_mask.ps
> > > >> 'name="OCEAN";
> > > >> > >> > >> > > level="(*,*)";'
> > > >> > >> > >> > >
> > > >> > >> > >> > > As you can see, the result gets rid of the
lakes
> > problem.
> > > >> But
> > > >> > >> > >> wavewatch
> > > >> > >> > >> > is
> > > >> > >> > >> > > only run to +/- 80 degrees, so we're not
including
> > points
> > > >> near
> > > >> > >> the
> > > >> > >> > >> poles.
> > > >> > >> > >> > >
> > > >> > >> > >> > > Figured this would be a lot easier than running
WPS
> > > >> yourself.
> > > >> > >> > >> > >
> > > >> > >> > >> > > Thanks,
> > > >> > >> > >> > > John
> > > >> > >> > >> > >
> > > >> > >> > >> > >
> > > >> > >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley
Gotway <
> > > >> > >> johnhg at ucar.edu>
> > > >> > >> > >> > wrote:
> > > >> > >> > >> > >
> > > >> > >> > >> > > > Roz,
> > > >> > >> > >> > > >
> > > >> > >> > >> > > > I talked to some folks and have one
suggestion that
> > > >> *might*
> > > >> > >> work.
> > > >> > >> > >> The
> > > >> > >> > >> > > WRF
> > > >> > >> > >> > > > Pre-processing system is named WPS. The
geogrid
> > program
> > > >> > within
> > > >> > >> > WPS
> > > >> > >> > >> is
> > > >> > >> > >> > > used
> > > >> > >> > >> > > > to initialize your domain and handles land
use
> > > >> information.
> > > >> > By
> > > >> > >> > >> > default,
> > > >> > >> > >> > > > lakes and oceans are treated the same way.
However,
> > > >> > apparently
> > > >> > >> > >> there
> > > >> > >> > >> > is
> > > >> > >> > >> > > an
> > > >> > >> > >> > > > option to distinguish between them. Take a
look
> here:
> > > >> > >> > >> > > >
> > > >> > >> > >> > > > http://www2.mmm.ucar.edu/wrf/
> > users/docs/user_guide_V3/
> > > >> > >> > >> > > users_guide_chap3.htm#_Description_of_the_1
> > > >> > >> > >> > > >
> > > >> > >> > >> > > > And search for "Alternative Initialization of
Lake
> > > SSTs".
> > > >> > >> > >> > > >
> > > >> > >> > >> > > > So you'd...
> > > >> > >> > >> > > > (1) download the MODIS SST data
> > > >> > >> > >> > > > (2) configure geogrid for the 0.25 degree GFS
grid
> > > >> > >> > >> > > > (3) configure geogrid to distinguish between
lakes
> and
> > > >> oceans
> > > >> > >> > >> > > > (4) run geogrid
> > > >> > >> > >> > > > (5) run the output through the MET
gen_vx_mask tool
> to
> > > use
> > > >> > >> ocean
> > > >> > >> > >> values
> > > >> > >> > >> > > > and skip the lake values
> > > >> > >> > >> > > >
> > > >> > >> > >> > > > Thanks,
> > > >> > >> > >> > > > John
> > > >> > >> > >> > > >
> > > >> > >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley
Gotway <
> > > >> > >> > johnhg at ucar.edu>
> > > >> > >> > >> > > wrote:
> > > >> > >> > >> > > >
> > > >> > >> > >> > > >> Roz,
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >> Whenever you see that error about loading
shared
> > > >> libraries,
> > > >> > it
> > > >> > >> > >> means
> > > >> > >> > >> > > that
> > > >> > >> > >> > > >> there's a problem in how your
LD_LIBRARY_PATH
> > > environment
> > > >> > >> > variable
> > > >> > >> > >> is
> > > >> > >> > >> > > set.
> > > >> > >> > >> > > >> That environment variable tells the linker
where to
> > > look
> > > >> for
> > > >> > >> > shared
> > > >> > >> > >> > > >> libraries at runtime... one of those shared
> libraries
> > > is
> > > >> GSL
> > > >> > >> (GNU
> > > >> > >> > >> > > >> Scientific Library). You'd "fix" this issue
by
> > > modifying
> > > >> > how
> > > >> > >> > >> > > >> LD_LIBRARY_PATH is set:
> > > >> > >> > >> > > >> echo $LD_LIBRARY_PATH
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >> Take a look in your ~/.cshrc file for c-
shell or
> > > >> ~/.bashrc
> > > >> > for
> > > >> > >> > >> bash to
> > > >> > >> > >> > > >> see how its set.
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >> As for the LAND/SEA mask, I was wondering if
those
> > > lakes
> > > >> > would
> > > >> > >> > be a
> > > >> > >> > >> > > >> problem. Using the model's LAND/SEA mask is
the
> > > easiest,
> > > >> > but
> > > >> > >> > >> doesn't
> > > >> > >> > >> > > >> provide an easy way of selecting out oceans.
My
> next
> > > >> > thought
> > > >> > >> was
> > > >> > >> > >> to
> > > >> > >> > >> > use
> > > >> > >> > >> > > >> GIS Shapefiles to define only the ocean
area. That
> > > will
> > > >> be
> > > >> > >> > >> available
> > > >> > >> > >> > in
> > > >> > >> > >> > > >> the next version of MET, version 7.1. I
tried
> using
> > a
> > > >> beta
> > > >> > >> > release
> > > >> > >> > >> > for
> > > >> > >> > >> > > >> met-7.1, but ran into problems when applying
large
> > > >> polylines
> > > >> > >> to
> > > >> > >> > >> global
> > > >> > >> > >> > > >> grids.
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >> I'll keep thinking about that one.
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >> Thanks,
> > > >> > >> > >> > > >> John
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn
MacCracken
> -
> > > NOAA
> > > >> > >> > Affiliate
> > > >> > >> > >> > via
> > > >> > >> > >> > > >> RT <met_help at ucar.edu> wrote:
> > > >> > >> > >> > > >>
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
> > > >> > >> ket/Display.html?id=86091 >
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> Hey John,
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> I have 2 problems. First, I'm able to use
> > > >> plot_data_plane,
> > > >> > >> but,
> > > >> > >> > >> > when I
> > > >> > >> > >> > > >>> use
> > > >> > >> > >> > > >>> the command for gen_vx_mask, I get this:
> > > >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
> > > >> gfs.t00z.pgrb2.0p25.f000
> > > >> > >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000
gfs_4_WATER_mask.nc -type
> > > data
> > > >> > >> > >> -mask_field
> > > >> > >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0
-name WATER
> > > >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error
while
> > loading
> > > >> > shared
> > > >> > >> > >> > > libraries:
> > > >> > >> > >> > > >>> libgsl.so.0: cannot open shared object
file: No
> such
> > > >> file
> > > >> > or
> > > >> > >> > >> > directory
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> Now, they are both in the same directory,
and I
> know
> > > >> that
> > > >> > >> I've
> > > >> > >> > >> used
> > > >> > >> > >> > > >>> gen_vx_mask before, so, I have no idea why
I would
> > be
> > > >> > getting
> > > >> > >> > that
> > > >> > >> > >> > > error
> > > >> > >> > >> > > >>> message. Any ideas?
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> Then, I was able to generate a *.ps file,
which
> > looks
> > > >> > exactly
> > > >> > >> > like
> > > >> > >> > >> > > yours,
> > > >> > >> > >> > > >>> but, there is still the same problem. If
you look
> > > >> closely
> > > >> > >> are
> > > >> > >> > >> your
> > > >> > >> > >> > > map,
> > > >> > >> > >> > > >>> you'll see these little white dots over
land.
> Those
> > > are
> > > >> > >> lakes,
> > > >> > >> > >> and
> > > >> > >> > >> > > >>> that's
> > > >> > >> > >> > > >>> what is giving me a fit, because I have
ASCAT
> > > >> observations
> > > >> > >> over
> > > >> > >> > >> those
> > > >> > >> > >> > > >>> white
> > > >> > >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS
data with
> 12
> > > km
> > > >> > ASCAT
> > > >> > >> > >> > > data...so,
> > > >> > >> > >> > > >>> very sensitive. Anyway, do you have any
idea how
> to
> > > get
> > > >> > rid
> > > >> > >> of
> > > >> > >> > >> those
> > > >> > >> > >> > > >>> points? Perhaps a different file with the
same
> > > domain?
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> Roz
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn
> MacCracken -
> > > >> NOAA
> > > >> > >> > >> Affiliate <
> > > >> > >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> > > >> > >> > >> > > >>>
> > > >> > >> > >> > > >>> > Ok, I'll let you know if I can get the
mask to
> > work.
> > > >> > This
> > > >> > >> > seems
> > > >> > >> > >> > easy
> > > >> > >> > >> > > >>> > enough, and pretty straight forward.
> > > >> > >> > >> > > >>> >
> > > >> > >> > >> > > >>> > Thanks for the help!
> > > >> > >> > >> > > >>> >
> > > >> > >> > >> > > >>> > Roz
> > > >> > >> > >> > > >>> >
> > > >> > >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John
Halley
> Gotway
> > > via
> > > >> > RT <
> > > >> > >> > >> > > >>> > met_help at ucar.edu> wrote:
> > > >> > >> > >> > > >>> >
> > > >> > >> > >> > > >>> >> Roz,
> > > >> > >> > >> > > >>> >>
> > > >> > >> > >> > > >>> >> Yes, I expect that using met-6.0 would
work
> fine.
> > > >> Hope
> > > >> > it
> > > >> > >> > goes
> > > >> > >> > >> > > >>> smoothly.
> > > >> > >> > >> > > >>> >>
> > > >> > >> > >> > > >>> >> Thanks,
> > > >> > >> > >> > > >>> >> John
> > > >> > >> > >> > > >>> >>
> > > >> > >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn
> > MacCracken -
> > > >> NOAA
> > > >> > >> > >> Affiliate
> > > >> > >> > >> > > >>> via RT
> > > >> > >> > >> > > >>> >> <
> > > >> > >> > >> > > >>> >> met_help at ucar.edu> wrote:
> > > >> > >> > >> > > >>> >>
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> > > >> > >> > >> ket/Display.html?id=86091 >
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > Hi John,
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > I get the general idea and it looks
pretty
> > > straight
> > > >> > >> > forward.
> > > >> > >> > >> > I'm
> > > >> > >> > >> > > >>> still
> > > >> > >> > >> > > >>> >> > running MET6.0, since we had some
> installation
> > > >> issues,
> > > >> > >> > but, I
> > > >> > >> > >> > > >>> should be
> > > >> > >> > >> > > >>> >> > able to generate the mask with that
pretty
> > > easily,
> > > >> > >> correct?
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > So, if this works, I'll need to rerun
all my
> > data
> > > >> from
> > > >> > >> Mar
> > > >> > >> > >> 2018
> > > >> > >> > >> > -
> > > >> > >> > >> > > >>> >> present,
> > > >> > >> > >> > > >>> >> > using that method that we worked out
earlier
> > with
> > > >> the
> > > >> > >> > *.stat
> > > >> > >> > >> > > files,
> > > >> > >> > >> > > >>> >> > correct? Actually, I don't need to do
> that...I
> > > can
> > > >> > >> start
> > > >> > >> > >> from
> > > >> > >> > >> > the
> > > >> > >> > >> > > >>> ASCII
> > > >> > >> > >> > > >>> >> > files I've already generated, and then
just
> > rerun
> > > >> > >> > POINT_STAT
> > > >> > >> > >> > with
> > > >> > >> > >> > > >>> the
> > > >> > >> > >> > > >>> >> > mask. Ok, that will save some steps.
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > Alright, I'll try making the mask and
do a
> test
> > > run
> > > >> > >> after
> > > >> > >> > >> lunch,
> > > >> > >> > >> > > >>> and get
> > > >> > >> > >> > > >>> >> > back to you when it works.
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > Thanks!
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > Roz
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John
Halley
> > > Gotway
> > > >> via
> > > >> > >> RT <
> > > >> > >> > >> > > >>> >> > met_help at ucar.edu
> > > >> > >> > >> > > >>> >> > > wrote:
> > > >> > >> > >> > > >>> >> >
> > > >> > >> > >> > > >>> >> > > Hi Roz,
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > I see you're wondering how to only
use
> point
> > > >> > >> observations
> > > >> > >> > >> over
> > > >> > >> > >> > > >>> water
> > > >> > >> > >> > > >>> >> and
> > > >> > >> > >> > > >>> >> > > discard the ones over land. You're
running
> > > >> ASCII2NC
> > > >> > >> > >> followed
> > > >> > >> > >> > by
> > > >> > >> > >> > > >>> >> > Point-Stat
> > > >> > >> > >> > > >>> >> > > and want to know where/how to define
that
> > > >> masking.
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > The ASCII2NC tool supports 3 command
line
> > > options
> > > >> > for
> > > >> > >> > >> > filtering
> > > >> > >> > >> > > >>> point
> > > >> > >> > >> > > >>> >> > > observations spatially: -mask_grid,
> > -mask_poly,
> > > >> and
> > > >> > >> > >> -mask_sid,
> > > >> > >> > >> > > for
> > > >> > >> > >> > > >>> >> grid,
> > > >> > >> > >> > > >>> >> > > polyline, and station ID masking,
> > respectively.
> > > >> But
> > > >> > >> > that's
> > > >> > >> > >> > not
> > > >> > >> > >> > > >>> really
> > > >> > >> > >> > > >>> >> > what
> > > >> > >> > >> > > >>> >> > > you want. You want to do "data
masking"
> > where
> > > >> you
> > > >> > >> read
> > > >> > >> > in
> > > >> > >> > >> a
> > > >> > >> > >> > > >>> land/sea
> > > >> > >> > >> > > >>> >> > mask
> > > >> > >> > >> > > >>> >> > > and only use the points over water.
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-
Mask tool
> to
> > > >> create
> > > >> > >> the
> > > >> > >> > >> > desired
> > > >> > >> > >> > > >>> >> masking
> > > >> > >> > >> > > >>> >> > > region, and then reference that in
the
> > > Point-Stat
> > > >> > >> config
> > > >> > >> > >> file.
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > To illustrate, I pulled a sample GFS
file:
> > > >> > >> > >> > > >>> >> > > > wget
> > > >> > >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> > > >> > >> > >> ata/gfs4/201807/20180702/gfs_
> > > >> > >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA
mask:
> > > >> > >> > >> > > >>> >> > > > wgrib2
gfs_4_20180702_0000_012.grb2 |
> > egrep
> > > >> -i
> > > >> > >> LAND
> > > >> > >> > >> > > >>> >> > > 400:65422867:d=2018070200:
> > LAND:surface:12
> > > >> hour
> > > >> > >> > fcst:
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > Run plot_data_plane to see it (see
attached
> > > >> image):
> > > >> > >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> > > >> > >> > >> gfs_4_20180702_0000_012.grb2
> > > >> > >> > >> > > >>> >> > gfs_4_LAND.ps
> > > >> > >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > Run gen_vx_mask to create a mask for
your
> > > >> > verification
> > > >> > >> > >> domain.
> > > >> > >> > >> > > If
> > > >> > >> > >> > > >>> >> you're
> > > >> > >> > >> > > >>> >> > > actually verifying on the GFS
domain, the
> > > command
> > > >> > >> looks a
> > > >> > >> > >> > little
> > > >> > >> > >> > > >>> >> > redundant:
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > > /usr/local/met-
7.0/bin/gen_vx_mask \
> > > >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > > >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2 \
> > > >> > >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> > > >> > >> > >> > > >>> >> > > -type data \
> > > >> > >> > >> > > >>> >> > > -mask_field 'name="LAND";
> level="L0";' \
> > > >> > >> > >> > > >>> >> > > -thresh ==0 \
> > > >> > >> > >> > > >>> >> > > -name WATER
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > I defined the threshold as "==0"
because we
> > > want
> > > >> the
> > > >> > >> > WATER
> > > >> > >> > >> > > >>> points, not
> > > >> > >> > >> > > >>> >> > the
> > > >> > >> > >> > > >>> >> > > LAND points. And I used the "-name
WATER"
> > > >> command
> > > >> > >> line
> > > >> > >> > >> option
> > > >> > >> > >> > > to
> > > >> > >> > >> > > >>> name
> > > >> > >> > >> > > >>> >> > the
> > > >> > >> > >> > > >>> >> > > output NetCDF variable. This will
show up
> in
> > > the
> > > >> > >> VX_MASK
> > > >> > >> > >> > output
> > > >> > >> > >> > > >>> >> column
> > > >> > >> > >> > > >>> >> > of
> > > >> > >> > >> > > >>> >> > > Point-Stat.
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > Lastly, setup your Point-Stat config
file
> > like
> > > >> this:
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > mask = {
> > > >> > >> > >> > > >>> >> > > grid = [];
> > > >> > >> > >> > > >>> >> > > poly = [
> "/path/to/gfs_4_WATER_mask.nc"
> > > ];
> > > >> > >> > >> > > >>> >> > > sid = [];
> > > >> > >> > >> > > >>> >> > > }
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > Hope that helps clarify.
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > Thanks,
> > > >> > >> > >> > > >>> >> > > John
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM
Rosalyn
> > > >> MacCracken -
> > > >> > >> NOAA
> > > >> > >> > >> > > >>> Affiliate via
> > > >> > >> > >> > > >>> >> > RT <
> > > >> > >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018: Request
86091
> was
> > > >> acted
> > > >> > >> upon.
> > > >> > >> > >> > > >>> >> > > > Transaction: Ticket created by
> > > >> > >> > >> rosalyn.maccracken at noaa.gov
> > > >> > >> > >> > > >>> >> > > > Queue: met_help
> > > >> > >> > >> > > >>> >> > > > Subject: masking land
features
> > questions
> > > >> > >> > >> > > >>> >> > > > Owner: Nobody
> > > >> > >> > >> > > >>> >> > > > Requestors:
> rosalyn.maccracken at noaa.gov
> > > >> > >> > >> > > >>> >> > > > Status: new
> > > >> > >> > >> > > >>> >> > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Tic
> > > >> > >> > >> > > >>> >> ket/Display.html?id=86091
> > > >> > >> > >> > > >>> >> > >
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > Hi,
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > I'm using ASCAT data to verify the
GFS.
> I
> > > only
> > > >> > >> want to
> > > >> > >> > >> > verify
> > > >> > >> > >> > > >>> >> points
> > > >> > >> > >> > > >>> >> > > over
> > > >> > >> > >> > > >>> >> > > > the ocean, and not over any inland
lakes.
> > I
> > > >> > noticed
> > > >> > >> > >> that I
> > > >> > >> > >> > > was
> > > >> > >> > >> > > >>> >> getting
> > > >> > >> > >> > > >>> >> > > > matched points over land (mostly
Africa).
> > > I'm
> > > >> > >> dumping
> > > >> > >> > >> out
> > > >> > >> > >> > the
> > > >> > >> > >> > > >>> >> MGDRlite
> > > >> > >> > >> > > >>> >> > > > file to an ascii file, which I use
> ASCII2NC
> > > to
> > > >> > >> create
> > > >> > >> > the
> > > >> > >> > >> > > netCDF
> > > >> > >> > >> > > >>> >> file,
> > > >> > >> > >> > > >>> >> > > and
> > > >> > >> > >> > > >>> >> > > > then go on to use Point_stat to
create
> > > >> statistics
> > > >> > >> for
> > > >> > >> > the
> > > >> > >> > >> > > >>> matched
> > > >> > >> > >> > > >>> >> > points.
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > How do I mask out points over land
before
> > it
> > > >> gets
> > > >> > to
> > > >> > >> > the
> > > >> > >> > >> > > >>> Point_stat
> > > >> > >> > >> > > >>> >> > step?
> > > >> > >> > >> > > >>> >> > > > Is there something in the ASCII2NC
> > processing
> > > >> > that I
> > > >> > >> > can
> > > >> > >> > >> > add,
> > > >> > >> > >> > > >>> so I
> > > >> > >> > >> > > >>> >> > don't
> > > >> > >> > >> > > >>> >> > > > get these matched points?
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > Thanks in advance!
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > Roz
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > --
> > > >> > >> > >> > > >>> >> > > > Rosalyn MacCracken
> > > >> > >> > >> > > >>> >> > > > Support Scientist
> > > >> > >> > >> > > >>> >> > > >
> > > >> > >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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: masking land features questions
From: Rosalyn MacCracken - NOAA Affiliate
Time: Mon Jul 16 14:47:36 2018
Hi John,
That sounds good. Yes, you can close the ticket. If I have more
questions, I'll open a new ticket.
Thanks for your help!
Roz
On Mon, Jul 16, 2018 at 4:46 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Roz,
>
> OK, great. I'll close this ticket for now. Just let us know if
more
> issues or questions arise.
>
> Thanks,
> John
>
> On Mon, Jul 16, 2018 at 2:25 PM Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> >
> > John,
> >
> > I think that it would be too hard to get someone to install the
beta
> > version to test it. It took us so long to get MET7 to work
correctly, I
> > doubt that anyone would want to do that.
> >
> > I do like Option 2:
> > 2) STAT-Analysis supports the "-column_thresh" job command option
as
> well,
> > which could be used to filter lat/lon values. For example, here's
how
> you
> > could use it to define a lat/lon box: -column_thresh OBS_LAT
> 'ge-30&&le30'
> > -column_thresh OBS_LON 'ge-150&&le-90'
> >
> > I can define a new lat/lon box, and just rerun everything easily
using
> the
> > *.stat files. I already have all my scripts in order to rerun my
data
> > using stat-analysis, so, adding the -column_thresh call would be
easy...I
> > think.
> >
> > Roz
> >
> > On Mon, Jul 16, 2018 at 11:40 AM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Roz,
> > >
> > > I have 3 pieces of info for you:
> > >
> > > (1) STAT-Analysis supports the "-mask_poly" job command option
which is
> > > used to specify a lat/lon polyline file. Only those lat/lon's
falling
> > > inside the polyline region are used. However, defining large
polylines
> > on
> > > global grids has proved problematic in the past. Sometimes the
logic
> for
> > > determining which lat/lon points are *inside* the polyline
breaks down
> > for
> > > global grids.
> > >
> > > (2) STAT-Analysis supports the "-column_thresh" job command
option as
> > well,
> > > which could be used to filter lat/lon values. For example,
here's how
> > you
> > > could use it to define a lat/lon box: -column_thresh OBS_LAT
> > 'ge-30&&le30'
> > > -column_thresh OBS_LON 'ge-150&&le-90'
> > >
> > > (3) Really, the best solution here is to enhance STAT-Analysis
to do
> > > exactly what we want it to do... namely, be able to read the
output of
> > > Gen-Vx-Mask to define the masking region. But it comes down to
timing.
> > We
> > > could probably include that in the next beta release for met-7.1
and
> have
> > > it available in a week or two for you to test out.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, Jul 13, 2018 at 12:52 PM Rosalyn MacCracken - NOAA
Affiliate
> via
> > RT
> > > <met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
>
> > > >
> > > > hi John,
> > > >
> > > > Maybe I didn't ask the right question. Can I use the same
formatted
> > mask
> > > > (polyline file with lat/lon), that I used for my point-stat
mask,
> with
> > > > stat-analysis with new lat/lon coordinates in the vx_mask
option?
> Or
> > > does
> > > > it have to be the same set of coordinates that I used in the
original
> > > > point-stat mask file?
> > > >
> > > > Roz
> > > >
> > > > On Fri, Jul 13, 2018 at 2:08 PM, Rosalyn MacCracken - NOAA
Affiliate
> <
> > > > rosalyn.maccracken at noaa.gov> wrote:
> > > >
> > > > > Hi John,
> > > > >
> > > > > Yeah, I don't know if either solution is going to work.
There
> isn't
> > > any
> > > > > OBS_ID associated with the observation, but, more like a
flag in
> the
> > > > > original ASCAT data file. I wouldn't even begin to know how
to
> > figure
> > > > out
> > > > > how to translate that into a station id.
> > > > >
> > > > > Oh, and I can't just change the mask and rerun stat-
analysis. I
> > would
> > > > > need to rerun point-stat, and now I'm back to square one...
> > > > >
> > > > > So, there is no way to designate a new box to input into the
> > > > > stat-analysis? You know, like you can indicate the wind
speed
> > > > > threshold...maybe something similar with the lat/lon? Guess
not...
> > > > >
> > > > > Roz
> > > > >
> > > > > On Thu, Jul 12, 2018 at 2:55 PM, John Halley Gotway via RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > >> Roz,
> > > > >>
> > > > >> Yes, that's correct. You'd list that new land mask in the
> > Point-Stat
> > > > >> config file to control which points are included.
> > > > >>
> > > > >> If I remember correctly, you're running some STAT-Analysis
jobs to
> > > > >> aggregate MPR lines from previous runs of Point-Stat. And
that's
> > the
> > > > >> problem, that STAT-Analysis cannot use the output of
gen_vx_mask
> to
> > > > >> control
> > > > >> which MPR lines should be included. Here are two
possibilities
> for
> > > > >> solving
> > > > >> this problem:
> > > > >>
> > > > >> (1) The MPR line contains a column named OBS_SID which is
the name
> > of
> > > > the
> > > > >> station. If you can, through some means, identify the
names of
> the
> > > > >> stations that you *DO* want to use, you could write them
out to an
> > > ASCII
> > > > >> file. Then when you run STAT-Analysis jobs, you could use
the
> > > > "-mask_sid"
> > > > >> option to tell it the names of the stations to be included.
I
> > haven't
> > > > >> done
> > > > >> this for large numbers of stations. In principle, the
logic
> should
> > > > work.
> > > > >> In practice, it may be a little slow, checking that long
list of
> > > > stations
> > > > >> many times.
> > > > >>
> > > > >> (2) We have been doing active development for the next MET
> release.
> > > As
> > > > we
> > > > >> add new features, we've been building beta releases and
building
> > them
> > > on
> > > > >> NOAA machines (theia, jet, wcoss) for NOAA folks to test
out. The
> > > > current
> > > > >> development version is named met-7.1_beta6. I could
elevate the
> > > > priority
> > > > >> of that development ticket I sent to you, and enhance
> stat-analysis
> > to
> > > > >> define masking regions using the output of gen_vx_mask.
And then
> I
> > > > could
> > > > >> include it in the next beta release for you to test out.
That
> would
> > > > >> certainly be easier for you than generating a list of
stations to
> > use.
> > > > >> But
> > > > >> it would take a week or two to get you a new beta release
to test
> > out.
> > > > >>
> > > > >> If you decided to go with (1), let me know. I have a
suggestion
> for
> > > how
> > > > >> you might generate that list of stations to include.
> > > > >>
> > > > >> Thanks,
> > > > >> John
> > > > >>
> > > > >> On Thu, Jul 12, 2018 at 7:43 AM Rosalyn MacCracken - NOAA
> Affiliate
> > > via
> > > > >> RT <
> > > > >> met_help at ucar.edu> wrote:
> > > > >>
> > > > >> >
> > > > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091 >
> > > > >> >
> > > > >> > Oh, but, I can incorporate this new land mask from here
on out,
> > > right?
> > > > >> And,
> > > > >> > I would add that to my Point-stat config file, like you
showed
> me
> > to
> > > > do
> > > > >> in
> > > > >> > the previous email, correct?
> > > > >> >
> > > > >> > Roz
> > > > >> >
> > > > >> > On Thu, Jul 12, 2018 at 1:09 PM, Rosalyn MacCracken -
NOAA
> > > Affiliate <
> > > > >> > rosalyn.maccracken at noaa.gov> wrote:
> > > > >> >
> > > > >> > > Hi John,
> > > > >> > >
> > > > >> > > There's got to be a way around this...I'm sure there is
a work
> > > > around
> > > > >> so
> > > > >> > > that I don't have to go back an get all of the GFS
files.
> And,
> > I
> > > > know
> > > > >> > that
> > > > >> > > I want to use STAT-Analysis, since I already have all
that in
> > > place
> > > > to
> > > > >> > > regenerate data.
> > > > >> > >
> > > > >> > > So, you said I can use a lat/lon polyline file with
> > STAT-Analysis.
> > > > Of
> > > > >> > > course, I already use that with my North Atlantic or
North
> > Pacific
> > > > >> masks.
> > > > >> > > So, my first option might be, make my North Atlantic
mask
> > smaller,
> > > > >> not to
> > > > >> > > include West Africa, where the bad observations are
located,
> and
> > > > don't
> > > > >> > use
> > > > >> > > the global file that is generated (if there a way not
to make
> > that
> > > > >> file,
> > > > >> > > and only re-generate files for the North Atlantic?).
> > Ok...that's
> > > > one
> > > > >> > > option, and that's probably what I will have to do.
> > > > >> > >
> > > > >> > > Here's the question. So, let's say there was a way for
us to
> go
> > > > back
> > > > >> > > through our ASCAT data, and identify lat/lons of
observations
> > that
> > > > >> were
> > > > >> > > flagged not to use, or over land, is there a way to
have
> > > > STAT-Analysis
> > > > >> > > discard matched pairs associated with those lat/lons?
Maybe,
> > > that's
> > > > >> like
> > > > >> > > using the lat/lon ployline file in reverse? Here's the
mask,
> > use
> > > > all
> > > > >> > > observations except if it falls inside this masked
domain?
> Can
> > we
> > > > do
> > > > >> > that?
> > > > >> > >
> > > > >> > > Roz
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > On Wed, Jul 11, 2018 at 8:00 PM, John Halley Gotway via
RT <
> > > > >> > > met_help at ucar.edu> wrote:
> > > > >> > >
> > > > >> > >> Roz,
> > > > >> > >>
> > > > >> > >> Bad news. I had hoped we could simply pass in the
gridded
> mask
> > > > file
> > > > >> > >> you've
> > > > >> > >> defined as input to STAT-Analysis using "-mask_poly"
but
> > > > >> unfortunately
> > > > >> > >> that
> > > > >> > >> doesn't work.
> > > > >> > >>
> > > > >> > >> STAT-Analysis currently supports: -mask_grid,
-mask_poly, and
> > > > >> -mask_sid
> > > > >> > to
> > > > >> > >> filter MPR lines by a named grid, polyline file, or
list of
> > > station
> > > > >> id
> > > > >> > >> names. The other MET tools, like Point-Stat and Grid-
Stat
> also
> > > > >> support
> > > > >> > >> multiple masking options.
> > > > >> > >>
> > > > >> > >> For example, in Point-Stat:
> > > > >> > >> mask = {
> > > > >> > >> grid = [ "FULL" ];
> > > > >> > >> poly = [];
> > > > >> > >> sid = [];
> > > > >> > >> }
> > > > >> > >>
> > > > >> > >> The "mask.grid" option in Point-Stat is the same of
> > "-mask_grid"
> > > in
> > > > >> > >> STAT-Analysis. They both process named grids, like
"G212"
> for
> > > NCEP
> > > > >> grid
> > > > >> > >> number 212.
> > > > >> > >>
> > > > >> > >> Likewise, the "mask.sid" option is the same as "-
mask_sid".
> > They
> > > > >> both
> > > > >> > >> define lists of station ID names to be included.
> > > > >> > >>
> > > > >> > >> *BUT* the "mask.poly" option in Point-Stat is much
more
> > flexible
> > > > than
> > > > >> > >> "-mask_poly" in STAT-Analysis. In STAT-Analysis, it
can only
> > be
> > > > set
> > > > >> to
> > > > >> > a
> > > > >> > >> lat/lon polyline file. In Point-Stat, it can also be
set to
> > the
> > > > >> output
> > > > >> > of
> > > > >> > >> gen_vx_mask or any gridded data file followed by a
> description
> > of
> > > > >> data
> > > > >> > to
> > > > >> > >> be extracted and thresholded.
> > > > >> > >>
> > > > >> > >> We actually have a development task already defined to
> address
> > > this
> > > > >> > issue
> > > > >> > >> (see attached).
> > > > >> > >>
> > > > >> > >> But that doesn't help you. So unfortunately, with
met-7.0,
> > you'd
> > > > >> would
> > > > >> > >> need to go all the way back to generating pairs with
> > Point-Stat.
> > > > >> > >>
> > > > >> > >> However, if you were using a future version of MET,
you could
> > do
> > > > this
> > > > >> > all
> > > > >> > >> in STAT-Analysis.
> > > > >> > >>
> > > > >> > >> Thanks,
> > > > >> > >> John
> > > > >> > >>
> > > > >> > >> On Wed, Jul 11, 2018 at 1:17 PM Rosalyn MacCracken -
NOAA
> > > Affiliate
> > > > >> via
> > > > >> > >> RT <
> > > > >> > >> met_help at ucar.edu> wrote:
> > > > >> > >>
> > > > >> > >> >
> > > > >> > >> > <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> > > >
> > > > >> > >> >
> > > > >> > >> > Hi John,
> > > > >> > >> >
> > > > >> > >> > Well, good news. We got our MET7 to work, and I was
able
> to
> > > > >> create my
> > > > >> > >> > ocean mask. It was an issue with conflicts in our
> libraries,
> > > and
> > > > >> the
> > > > >> > >> > LD_LIBRARY_PATH. But, it's fixed, so, I'm happy.
> > > > >> > >> >
> > > > >> > >> > Now, I have this ocean mask, and now I can go back
and
> rerun
> > my
> > > > >> data.
> > > > >> > >> So,
> > > > >> > >> > as usual, I had some questions.
> > > > >> > >> >
> > > > >> > >> > I have a series of scripts where you helped me set
up
> > > > STATanalysis
> > > > >> to
> > > > >> > >> > reprocess the data using the *.stat files and the
-job
> > > > >> aggregate_stat
> > > > >> > >> > command . Will I be able to use this method again,
or,
> > because
> > > > >> it's
> > > > >> > >> > applying a mask, will I need to get the raw data
(GFS and
> > ASCAT
> > > > >> data)?
> > > > >> > >> > And, I guess if I have to use the raw data, I will
have to
> > > start
> > > > >> with
> > > > >> > >> > ASCII2NC, etc, as if I'm processing from scratch,
correct?
> > > > >> > >> >
> > > > >> > >> > I just need a sense of how big of a job this is....
> > > > >> > >> >
> > > > >> > >> > Thanks for your help!
> > > > >> > >> >
> > > > >> > >> > Roz
> > > > >> > >> >
> > > > >> > >> > On Tue, Jul 10, 2018 at 6:35 PM, Rosalyn MacCracken
- NOAA
> > > > >> Affiliate <
> > > > >> > >> > rosalyn.maccracken at noaa.gov> wrote:
> > > > >> > >> >
> > > > >> > >> > > Oh, yeah, nothing seems to be going smoothly
> > today...anyway,
> > > I
> > > > >> > think I
> > > > >> > >> > > need to wait until Chris and Fran come in tomorrow
to set
> > our
> > > > >> > >> directories
> > > > >> > >> > > correctly to point at MET, and get it running
again
> before
> > I
> > > do
> > > > >> > >> anything
> > > > >> > >> > > else.
> > > > >> > >> > >
> > > > >> > >> > > I'll try this again tomorrow and let you know how
I do.
> > > > >> > >> > >
> > > > >> > >> > > Thanks for your help!
> > > > >> > >> > >
> > > > >> > >> > > Roz
> > > > >> > >> > >
> > > > >> > >> > > On Tue, Jul 10, 2018 at 5:43 PM, John Halley
Gotway via
> RT
> > <
> > > > >> > >> > > met_help at ucar.edu> wrote:
> > > > >> > >> > >
> > > > >> > >> > >> Roz,
> > > > >> > >> > >>
> > > > >> > >> > >> Sorry you're having a rough day. No worries
though,
> this
> > > > issue
> > > > >> is
> > > > >> > >> easy
> > > > >> > >> > to
> > > > >> > >> > >> overcome. Here's a list of pre-defined NCEP
grids:
> > > > >> > >> > >>
> > http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html
> > > > >> > >> > >>
> > > > >> > >> > >> The intention in MET is to support them using the
naming
> > > > >> convention
> > > > >> > >> G###
> > > > >> > >> > >> where ### is the 3 digit grid number. But if you
look
> > > closely
> > > > >> on
> > > > >> > >> that
> > > > >> > >> > >> website, you'll see that grid 193 is a relatively
new
> one
> > > and
> > > > is
> > > > >> > >> listed
> > > > >> > >> > in
> > > > >> > >> > >> red. That definition just doesn't exist in MET
version
> > 6.0.
> > > > >> > >> > >>
> > > > >> > >> > >> The easy fix is this.... just replace "G193" on
the
> > command
> > > > line
> > > > >> > with
> > > > >> > >> > the
> > > > >> > >> > >> path to a 1/4 degree GFS GRIB2 file. Here's a
selection
> > > from
> > > > >> the
> > > > >> > >> usage
> > > > >> > >> > >> statement for regrid_data_plane:
> > > > >> > >> > >>
> > > > >> > >> > >> Usage: regrid_data_plane
> > > > >> > >> > >> input_filename
> > > > >> > >> > >> to_grid
> > > > >> > >> > >> output_filename
> > > > >> > >> > >> "to_grid" defines the output grid
as a
> > named
> > > > >> grid,
> > > > >> > >> the
> > > > >> > >> > >> path
> > > > >> > >> > >> to a gridded data file, or an explicit grid
> specification
> > > > string
> > > > >> > >> > >> (required).
> > > > >> > >> > >>
> > > > >> > >> > >> When you set "to_grid" equal to a gridded data
file, MET
> > > reads
> > > > >> the
> > > > >> > >> grid
> > > > >> > >> > >> definition from the first record of that file and
uses
> it.
> > > > >> > >> > >>
> > > > >> > >> > >> That should do it.
> > > > >> > >> > >>
> > > > >> > >> > >> Thanks,
> > > > >> > >> > >> John
> > > > >> > >> > >>
> > > > >> > >> > >> On Tue, Jul 10, 2018 at 9:58 AM Rosalyn
MacCracken -
> NOAA
> > > > >> Affiliate
> > > > >> > >> via
> > > > >> > >> > >> RT <
> > > > >> > >> > >> met_help at ucar.edu> wrote:
> > > > >> > >> > >>
> > > > >> > >> > >> >
> > > > >> > >> > >> > <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86091
> > > > >> >
> > > > >> > >> > >> >
> > > > >> > >> > >> > Hi John,
> > > > >> > >> > >> >
> > > > >> > >> > >> > I'm really not having much luck today with
this.
> Maybe
> > I
> > > > >> should
> > > > >> > >> have
> > > > >> > >> > >> > stayed in bed (haha).
> > > > >> > >> > >> >
> > > > >> > >> > >> > So, the first thing I did was check the
> LD_LIBRARY_PATH,
> > > and
> > > > >> it's
> > > > >> > >> > >> pointing
> > > > >> > >> > >> > to the MET7 directories. Ok, that could be
most of
> the
> > > > >> problem.
> > > > >> > >> MET7
> > > > >> > >> > >> seems
> > > > >> > >> > >> > to be having some issue, and the guy here at
OPC that
> > > helps
> > > > me
> > > > >> > with
> > > > >> > >> > that
> > > > >> > >> > >> > stuff (Chris Juckins) is out on leave until
tomorrow.
> > > > Anyway,
> > > > >> > >> MET7 is
> > > > >> > >> > >> not
> > > > >> > >> > >> > running any of my verification programs, and
giving
> out
> > > some
> > > > >> > >> errors,
> > > > >> > >> > so,
> > > > >> > >> > >> > I'll have to get with him tomorrow to fix that.
> > > > >> > >> > >> >
> > > > >> > >> > >> > So, in the mean time, I don't think that any
kind of
> > land
> > > > mask
> > > > >> > >> > creation
> > > > >> > >> > >> > that I'm doing today will work because it's not
> pointing
> > > at
> > > > >> the
> > > > >> > >> right
> > > > >> > >> > >> > directories.
> > > > >> > >> > >> >
> > > > >> > >> > >> > But, when I do get this to work, I tried this
and got
> > this
> > > > >> error:
> > > > >> > >> > >> > /opt/MET6/met6.0/bin/regrid_data_plane
> > > > >> gwes01.glo_30m.t00z.grib2
> > > > >> > >> G193
> > > > >> > >> > >> > ocean_data.nc -field 'name="WIND"; level="L0";'
> > > > >> > >> > >> > DEBUG 1: Reading data file:
gwes01.glo_30m.t00z.grib2
> > > > >> > >> > >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx:
720 Ny:
> 321
> > > > >> lat_ll:
> > > > >> > >> > -80.000
> > > > >> > >> > >> > lon_ll: -0.000 delta_lat: 0.500 delta_lon:
0.500
> > > > >> > >> > >> > ERROR :
> > > > >> > >> > >> > ERROR : grd_file_type() -> file does not exist
"G193"
> > > > >> > >> > >> > ERROR :
> > > > >> > >> > >> >
> > > > >> > >> > >> > I'm wondering if that's all related to MET7.
> > > > >> > >> > >> >
> > > > >> > >> > >> > So, I think I need to fix the MET7 issue before
moving
> > on
> > > > with
> > > > >> > >> this,
> > > > >> > >> > >> don't
> > > > >> > >> > >> > you?
> > > > >> > >> > >> >
> > > > >> > >> > >> > Roz
> > > > >> > >> > >> >
> > > > >> > >> > >> > On Mon, Jul 9, 2018 at 9:39 PM, John Halley
Gotway via
> > RT
> > > <
> > > > >> > >> > >> > met_help at ucar.edu
> > > > >> > >> > >> > > wrote:
> > > > >> > >> > >> >
> > > > >> > >> > >> > > Roz,
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > OK, one other possible option to consider. I
> figured
> > > that
> > > > >> > >> there's
> > > > >> > >> > >> plenty
> > > > >> > >> > >> > > of "ocean" products out there. So I found a
NOAA
> > > > WAVEWATCH
> > > > >> > one:
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > (1) Download sample wavewatch file:
> > > > >> > >> > >> > > wget
> > > > >> > >> > >> > >
> > ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/wave/prod/
> > > > >> > >> > >> > > gwes.20180708/gwes01.glo_30m.t00z.grib2
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > (2) Run regrid_data_plane to put some surface
wind
> > speed
> > > > >> data
> > > > >> > on
> > > > >> > >> the
> > > > >> > >> > >> 1/4
> > > > >> > >> > >> > > GFS grid:
> > > > >> > >> > >> > > regrid_data_plane
gwes01.glo_30m.t00z.grib2 G193
> > > > >> > >> ocean_data.nc
> > > > >> > >> > >> -field
> > > > >> > >> > >> > > 'name="WIND"; level="L0";'
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > (3) Run gen_vx_mask to select points that
contain
> > valid
> > > > >> data:
> > > > >> > >> > >> > > gen_vx_mask ocean_data.nc ocean_data.nc
> > > ocean_mask.nc
> > > > >> -type
> > > > >> > >> data
> > > > >> > >> > >> > > -mask_field 'name="WIND_L0"; level="L0";'
-thresh
> > > ne-9999
> > > > >> -name
> > > > >> > >> > OCEAN
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > (4) Run plot_data_plane to see the result:
> > > > >> > >> > >> > > plot_data_plane ocean_mask.nc
ocean_mask.ps
> > > > >> 'name="OCEAN";
> > > > >> > >> > >> > > level="(*,*)";'
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > As you can see, the result gets rid of the
lakes
> > > problem.
> > > > >> But
> > > > >> > >> > >> wavewatch
> > > > >> > >> > >> > is
> > > > >> > >> > >> > > only run to +/- 80 degrees, so we're not
including
> > > points
> > > > >> near
> > > > >> > >> the
> > > > >> > >> > >> poles.
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > Figured this would be a lot easier than
running WPS
> > > > >> yourself.
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > Thanks,
> > > > >> > >> > >> > > John
> > > > >> > >> > >> > >
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > On Mon, Jul 9, 2018 at 3:03 PM John Halley
Gotway <
> > > > >> > >> johnhg at ucar.edu>
> > > > >> > >> > >> > wrote:
> > > > >> > >> > >> > >
> > > > >> > >> > >> > > > Roz,
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > > I talked to some folks and have one
suggestion
> that
> > > > >> *might*
> > > > >> > >> work.
> > > > >> > >> > >> The
> > > > >> > >> > >> > > WRF
> > > > >> > >> > >> > > > Pre-processing system is named WPS. The
geogrid
> > > program
> > > > >> > within
> > > > >> > >> > WPS
> > > > >> > >> > >> is
> > > > >> > >> > >> > > used
> > > > >> > >> > >> > > > to initialize your domain and handles land
use
> > > > >> information.
> > > > >> > By
> > > > >> > >> > >> > default,
> > > > >> > >> > >> > > > lakes and oceans are treated the same way.
> However,
> > > > >> > apparently
> > > > >> > >> > >> there
> > > > >> > >> > >> > is
> > > > >> > >> > >> > > an
> > > > >> > >> > >> > > > option to distinguish between them. Take a
look
> > here:
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > > http://www2.mmm.ucar.edu/wrf/
> > > users/docs/user_guide_V3/
> > > > >> > >> > >> > > users_guide_chap3.htm#_Description_of_the_1
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > > And search for "Alternative Initialization
of Lake
> > > > SSTs".
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > > So you'd...
> > > > >> > >> > >> > > > (1) download the MODIS SST data
> > > > >> > >> > >> > > > (2) configure geogrid for the 0.25 degree
GFS grid
> > > > >> > >> > >> > > > (3) configure geogrid to distinguish
between lakes
> > and
> > > > >> oceans
> > > > >> > >> > >> > > > (4) run geogrid
> > > > >> > >> > >> > > > (5) run the output through the MET
gen_vx_mask
> tool
> > to
> > > > use
> > > > >> > >> ocean
> > > > >> > >> > >> values
> > > > >> > >> > >> > > > and skip the lake values
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > > Thanks,
> > > > >> > >> > >> > > > John
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > > On Mon, Jul 9, 2018 at 2:44 PM John Halley
Gotway
> <
> > > > >> > >> > johnhg at ucar.edu>
> > > > >> > >> > >> > > wrote:
> > > > >> > >> > >> > > >
> > > > >> > >> > >> > > >> Roz,
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >> Whenever you see that error about loading
shared
> > > > >> libraries,
> > > > >> > it
> > > > >> > >> > >> means
> > > > >> > >> > >> > > that
> > > > >> > >> > >> > > >> there's a problem in how your
LD_LIBRARY_PATH
> > > > environment
> > > > >> > >> > variable
> > > > >> > >> > >> is
> > > > >> > >> > >> > > set.
> > > > >> > >> > >> > > >> That environment variable tells the linker
where
> to
> > > > look
> > > > >> for
> > > > >> > >> > shared
> > > > >> > >> > >> > > >> libraries at runtime... one of those
shared
> > libraries
> > > > is
> > > > >> GSL
> > > > >> > >> (GNU
> > > > >> > >> > >> > > >> Scientific Library). You'd "fix" this
issue by
> > > > modifying
> > > > >> > how
> > > > >> > >> > >> > > >> LD_LIBRARY_PATH is set:
> > > > >> > >> > >> > > >> echo $LD_LIBRARY_PATH
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >> Take a look in your ~/.cshrc file for c-
shell or
> > > > >> ~/.bashrc
> > > > >> > for
> > > > >> > >> > >> bash to
> > > > >> > >> > >> > > >> see how its set.
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >> As for the LAND/SEA mask, I was wondering
if
> those
> > > > lakes
> > > > >> > would
> > > > >> > >> > be a
> > > > >> > >> > >> > > >> problem. Using the model's LAND/SEA mask
is the
> > > > easiest,
> > > > >> > but
> > > > >> > >> > >> doesn't
> > > > >> > >> > >> > > >> provide an easy way of selecting out
oceans. My
> > next
> > > > >> > thought
> > > > >> > >> was
> > > > >> > >> > >> to
> > > > >> > >> > >> > use
> > > > >> > >> > >> > > >> GIS Shapefiles to define only the ocean
area.
> That
> > > > will
> > > > >> be
> > > > >> > >> > >> available
> > > > >> > >> > >> > in
> > > > >> > >> > >> > > >> the next version of MET, version 7.1. I
tried
> > using
> > > a
> > > > >> beta
> > > > >> > >> > release
> > > > >> > >> > >> > for
> > > > >> > >> > >> > > >> met-7.1, but ran into problems when
applying
> large
> > > > >> polylines
> > > > >> > >> to
> > > > >> > >> > >> global
> > > > >> > >> > >> > > >> grids.
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >> I'll keep thinking about that one.
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >> Thanks,
> > > > >> > >> > >> > > >> John
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >> On Mon, Jul 9, 2018 at 11:48 AM Rosalyn
> MacCracken
> > -
> > > > NOAA
> > > > >> > >> > Affiliate
> > > > >> > >> > >> > via
> > > > >> > >> > >> > > >> RT <met_help at ucar.edu> wrote:
> > > > >> > >> > >> > > >>
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> <URL: https://rt.rap.ucar.edu/rt/Tic
> > > > >> > >> ket/Display.html?id=86091 >
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> Hey John,
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> I have 2 problems. First, I'm able to
use
> > > > >> plot_data_plane,
> > > > >> > >> but,
> > > > >> > >> > >> > when I
> > > > >> > >> > >> > > >>> use
> > > > >> > >> > >> > > >>> the command for gen_vx_mask, I get this:
> > > > >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask
> > > > >> gfs.t00z.pgrb2.0p25.f000
> > > > >> > >> > >> > > >>> gfs.t00z.pgrb2.0p25.f000
gfs_4_WATER_mask.nc
> -type
> > > > data
> > > > >> > >> > >> -mask_field
> > > > >> > >> > >> > > >>> 'name="LAND"; level="L0";' -thresh ==0
-name
> WATER
> > > > >> > >> > >> > > >>> /opt/MET6/met6.0/bin/gen_vx_mask: error
while
> > > loading
> > > > >> > shared
> > > > >> > >> > >> > > libraries:
> > > > >> > >> > >> > > >>> libgsl.so.0: cannot open shared object
file: No
> > such
> > > > >> file
> > > > >> > or
> > > > >> > >> > >> > directory
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> Now, they are both in the same directory,
and I
> > know
> > > > >> that
> > > > >> > >> I've
> > > > >> > >> > >> used
> > > > >> > >> > >> > > >>> gen_vx_mask before, so, I have no idea
why I
> would
> > > be
> > > > >> > getting
> > > > >> > >> > that
> > > > >> > >> > >> > > error
> > > > >> > >> > >> > > >>> message. Any ideas?
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> Then, I was able to generate a *.ps file,
which
> > > looks
> > > > >> > exactly
> > > > >> > >> > like
> > > > >> > >> > >> > > yours,
> > > > >> > >> > >> > > >>> but, there is still the same problem. If
you
> look
> > > > >> closely
> > > > >> > >> are
> > > > >> > >> > >> your
> > > > >> > >> > >> > > map,
> > > > >> > >> > >> > > >>> you'll see these little white dots over
land.
> > Those
> > > > are
> > > > >> > >> lakes,
> > > > >> > >> > >> and
> > > > >> > >> > >> > > >>> that's
> > > > >> > >> > >> > > >>> what is giving me a fit, because I have
ASCAT
> > > > >> observations
> > > > >> > >> over
> > > > >> > >> > >> those
> > > > >> > >> > >> > > >>> white
> > > > >> > >> > >> > > >>> dots. You know, I'm using 0.25 deg GFS
data
> with
> > 12
> > > > km
> > > > >> > ASCAT
> > > > >> > >> > >> > > data...so,
> > > > >> > >> > >> > > >>> very sensitive. Anyway, do you have any
idea
> how
> > to
> > > > get
> > > > >> > rid
> > > > >> > >> of
> > > > >> > >> > >> those
> > > > >> > >> > >> > > >>> points? Perhaps a different file with
the same
> > > > domain?
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> Roz
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> On Mon, Jul 9, 2018 at 5:04 PM, Rosalyn
> > MacCracken -
> > > > >> NOAA
> > > > >> > >> > >> Affiliate <
> > > > >> > >> > >> > > >>> rosalyn.maccracken at noaa.gov> wrote:
> > > > >> > >> > >> > > >>>
> > > > >> > >> > >> > > >>> > Ok, I'll let you know if I can get the
mask to
> > > work.
> > > > >> > This
> > > > >> > >> > seems
> > > > >> > >> > >> > easy
> > > > >> > >> > >> > > >>> > enough, and pretty straight forward.
> > > > >> > >> > >> > > >>> >
> > > > >> > >> > >> > > >>> > Thanks for the help!
> > > > >> > >> > >> > > >>> >
> > > > >> > >> > >> > > >>> > Roz
> > > > >> > >> > >> > > >>> >
> > > > >> > >> > >> > > >>> > On Mon, Jul 9, 2018 at 4:26 PM, John
Halley
> > Gotway
> > > > via
> > > > >> > RT <
> > > > >> > >> > >> > > >>> > met_help at ucar.edu> wrote:
> > > > >> > >> > >> > > >>> >
> > > > >> > >> > >> > > >>> >> Roz,
> > > > >> > >> > >> > > >>> >>
> > > > >> > >> > >> > > >>> >> Yes, I expect that using met-6.0 would
work
> > fine.
> > > > >> Hope
> > > > >> > it
> > > > >> > >> > goes
> > > > >> > >> > >> > > >>> smoothly.
> > > > >> > >> > >> > > >>> >>
> > > > >> > >> > >> > > >>> >> Thanks,
> > > > >> > >> > >> > > >>> >> John
> > > > >> > >> > >> > > >>> >>
> > > > >> > >> > >> > > >>> >> On Mon, Jul 9, 2018 at 9:57 AM Rosalyn
> > > MacCracken -
> > > > >> NOAA
> > > > >> > >> > >> Affiliate
> > > > >> > >> > >> > > >>> via RT
> > > > >> > >> > >> > > >>> >> <
> > > > >> > >> > >> > > >>> >> met_help at ucar.edu> wrote:
> > > > >> > >> > >> > > >>> >>
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > <URL: https://rt.rap.ucar.edu/rt/Tic
> > > > >> > >> > >> ket/Display.html?id=86091 >
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > Hi John,
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > I get the general idea and it looks
pretty
> > > > straight
> > > > >> > >> > forward.
> > > > >> > >> > >> > I'm
> > > > >> > >> > >> > > >>> still
> > > > >> > >> > >> > > >>> >> > running MET6.0, since we had some
> > installation
> > > > >> issues,
> > > > >> > >> > but, I
> > > > >> > >> > >> > > >>> should be
> > > > >> > >> > >> > > >>> >> > able to generate the mask with that
pretty
> > > > easily,
> > > > >> > >> correct?
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > So, if this works, I'll need to
rerun all
> my
> > > data
> > > > >> from
> > > > >> > >> Mar
> > > > >> > >> > >> 2018
> > > > >> > >> > >> > -
> > > > >> > >> > >> > > >>> >> present,
> > > > >> > >> > >> > > >>> >> > using that method that we worked out
> earlier
> > > with
> > > > >> the
> > > > >> > >> > *.stat
> > > > >> > >> > >> > > files,
> > > > >> > >> > >> > > >>> >> > correct? Actually, I don't need to
do
> > that...I
> > > > can
> > > > >> > >> start
> > > > >> > >> > >> from
> > > > >> > >> > >> > the
> > > > >> > >> > >> > > >>> ASCII
> > > > >> > >> > >> > > >>> >> > files I've already generated, and
then just
> > > rerun
> > > > >> > >> > POINT_STAT
> > > > >> > >> > >> > with
> > > > >> > >> > >> > > >>> the
> > > > >> > >> > >> > > >>> >> > mask. Ok, that will save some
steps.
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > Alright, I'll try making the mask
and do a
> > test
> > > > run
> > > > >> > >> after
> > > > >> > >> > >> lunch,
> > > > >> > >> > >> > > >>> and get
> > > > >> > >> > >> > > >>> >> > back to you when it works.
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > Thanks!
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > Roz
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > On Mon, Jul 9, 2018 at 3:46 PM, John
Halley
> > > > Gotway
> > > > >> via
> > > > >> > >> RT <
> > > > >> > >> > >> > > >>> >> > met_help at ucar.edu
> > > > >> > >> > >> > > >>> >> > > wrote:
> > > > >> > >> > >> > > >>> >> >
> > > > >> > >> > >> > > >>> >> > > Hi Roz,
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > I see you're wondering how to only
use
> > point
> > > > >> > >> observations
> > > > >> > >> > >> over
> > > > >> > >> > >> > > >>> water
> > > > >> > >> > >> > > >>> >> and
> > > > >> > >> > >> > > >>> >> > > discard the ones over land.
You're
> running
> > > > >> ASCII2NC
> > > > >> > >> > >> followed
> > > > >> > >> > >> > by
> > > > >> > >> > >> > > >>> >> > Point-Stat
> > > > >> > >> > >> > > >>> >> > > and want to know where/how to
define that
> > > > >> masking.
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > The ASCII2NC tool supports 3
command line
> > > > options
> > > > >> > for
> > > > >> > >> > >> > filtering
> > > > >> > >> > >> > > >>> point
> > > > >> > >> > >> > > >>> >> > > observations spatially:
-mask_grid,
> > > -mask_poly,
> > > > >> and
> > > > >> > >> > >> -mask_sid,
> > > > >> > >> > >> > > for
> > > > >> > >> > >> > > >>> >> grid,
> > > > >> > >> > >> > > >>> >> > > polyline, and station ID masking,
> > > respectively.
> > > > >> But
> > > > >> > >> > that's
> > > > >> > >> > >> > not
> > > > >> > >> > >> > > >>> really
> > > > >> > >> > >> > > >>> >> > what
> > > > >> > >> > >> > > >>> >> > > you want. You want to do "data
masking"
> > > where
> > > > >> you
> > > > >> > >> read
> > > > >> > >> > in
> > > > >> > >> > >> a
> > > > >> > >> > >> > > >>> land/sea
> > > > >> > >> > >> > > >>> >> > mask
> > > > >> > >> > >> > > >>> >> > > and only use the points over
water.
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > I'd recommend running the Gen-Vx-
Mask
> tool
> > to
> > > > >> create
> > > > >> > >> the
> > > > >> > >> > >> > desired
> > > > >> > >> > >> > > >>> >> masking
> > > > >> > >> > >> > > >>> >> > > region, and then reference that in
the
> > > > Point-Stat
> > > > >> > >> config
> > > > >> > >> > >> file.
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > To illustrate, I pulled a sample
GFS
> file:
> > > > >> > >> > >> > > >>> >> > > > wget
> > > > >> > >> > >> > > >>> >> > > https://nomads.ncdc.noaa.gov/d
> > > > >> > >> > >> ata/gfs4/201807/20180702/gfs_
> > > > >> > >> > >> > > >>> >> > > 4_20180702_0000_012.grb2
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > Run wgrib2 and look for a LAND/SEA
mask:
> > > > >> > >> > >> > > >>> >> > > > wgrib2
gfs_4_20180702_0000_012.grb2 |
> > > egrep
> > > > >> -i
> > > > >> > >> LAND
> > > > >> > >> > >> > > >>> >> > > 400:65422867:d=2018070200:
> > > LAND:surface:12
> > > > >> hour
> > > > >> > >> > fcst:
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > Run plot_data_plane to see it (see
> attached
> > > > >> image):
> > > > >> > >> > >> > > >>> >> > > > met-7.0/bin/plot_data_plane
> > > > >> > >> > >> gfs_4_20180702_0000_012.grb2
> > > > >> > >> > >> > > >>> >> > gfs_4_LAND.ps
> > > > >> > >> > >> > > >>> >> > > 'name="LAND"; level="L0";'
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > Run gen_vx_mask to create a mask
for your
> > > > >> > verification
> > > > >> > >> > >> domain.
> > > > >> > >> > >> > > If
> > > > >> > >> > >> > > >>> >> you're
> > > > >> > >> > >> > > >>> >> > > actually verifying on the GFS
domain, the
> > > > command
> > > > >> > >> looks a
> > > > >> > >> > >> > little
> > > > >> > >> > >> > > >>> >> > redundant:
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > > /usr/local/met-
7.0/bin/gen_vx_mask \
> > > > >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2
\
> > > > >> > >> > >> > > >>> >> > > gfs_4_20180702_0000_012.grb2
\
> > > > >> > >> > >> > > >>> >> > > gfs_4_WATER_mask.nc \
> > > > >> > >> > >> > > >>> >> > > -type data \
> > > > >> > >> > >> > > >>> >> > > -mask_field 'name="LAND";
> > level="L0";' \
> > > > >> > >> > >> > > >>> >> > > -thresh ==0 \
> > > > >> > >> > >> > > >>> >> > > -name WATER
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > I defined the threshold as "==0"
because
> we
> > > > want
> > > > >> the
> > > > >> > >> > WATER
> > > > >> > >> > >> > > >>> points, not
> > > > >> > >> > >> > > >>> >> > the
> > > > >> > >> > >> > > >>> >> > > LAND points. And I used the "-
name
> WATER"
> > > > >> command
> > > > >> > >> line
> > > > >> > >> > >> option
> > > > >> > >> > >> > > to
> > > > >> > >> > >> > > >>> name
> > > > >> > >> > >> > > >>> >> > the
> > > > >> > >> > >> > > >>> >> > > output NetCDF variable. This will
show
> up
> > in
> > > > the
> > > > >> > >> VX_MASK
> > > > >> > >> > >> > output
> > > > >> > >> > >> > > >>> >> column
> > > > >> > >> > >> > > >>> >> > of
> > > > >> > >> > >> > > >>> >> > > Point-Stat.
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > Lastly, setup your Point-Stat
config file
> > > like
> > > > >> this:
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > mask = {
> > > > >> > >> > >> > > >>> >> > > grid = [];
> > > > >> > >> > >> > > >>> >> > > poly = [
> > "/path/to/gfs_4_WATER_mask.nc"
> > > > ];
> > > > >> > >> > >> > > >>> >> > > sid = [];
> > > > >> > >> > >> > > >>> >> > > }
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > Hope that helps clarify.
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > Thanks,
> > > > >> > >> > >> > > >>> >> > > John
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > On Mon, Jul 9, 2018 at 9:02 AM
Rosalyn
> > > > >> MacCracken -
> > > > >> > >> NOAA
> > > > >> > >> > >> > > >>> Affiliate via
> > > > >> > >> > >> > > >>> >> > RT <
> > > > >> > >> > >> > > >>> >> > > met_help at ucar.edu> wrote:
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > Mon Jul 09 09:02:05 2018:
Request 86091
> > was
> > > > >> acted
> > > > >> > >> upon.
> > > > >> > >> > >> > > >>> >> > > > Transaction: Ticket created by
> > > > >> > >> > >> rosalyn.maccracken at noaa.gov
> > > > >> > >> > >> > > >>> >> > > > Queue: met_help
> > > > >> > >> > >> > > >>> >> > > > Subject: masking land
features
> > > questions
> > > > >> > >> > >> > > >>> >> > > > Owner: Nobody
> > > > >> > >> > >> > > >>> >> > > > Requestors:
> > rosalyn.maccracken at noaa.gov
> > > > >> > >> > >> > > >>> >> > > > Status: new
> > > > >> > >> > >> > > >>> >> > > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Tic
> > > > >> > >> > >> > > >>> >> ket/Display.html?id=86091
> > > > >> > >> > >> > > >>> >> > >
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > Hi,
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > I'm using ASCAT data to verify
the GFS.
> > I
> > > > only
> > > > >> > >> want to
> > > > >> > >> > >> > verify
> > > > >> > >> > >> > > >>> >> points
> > > > >> > >> > >> > > >>> >> > > over
> > > > >> > >> > >> > > >>> >> > > > the ocean, and not over any
inland
> lakes.
> > > I
> > > > >> > noticed
> > > > >> > >> > >> that I
> > > > >> > >> > >> > > was
> > > > >> > >> > >> > > >>> >> getting
> > > > >> > >> > >> > > >>> >> > > > matched points over land (mostly
> Africa).
> > > > I'm
> > > > >> > >> dumping
> > > > >> > >> > >> out
> > > > >> > >> > >> > the
> > > > >> > >> > >> > > >>> >> MGDRlite
> > > > >> > >> > >> > > >>> >> > > > file to an ascii file, which I
use
> > ASCII2NC
> > > > to
> > > > >> > >> create
> > > > >> > >> > the
> > > > >> > >> > >> > > netCDF
> > > > >> > >> > >> > > >>> >> file,
> > > > >> > >> > >> > > >>> >> > > and
> > > > >> > >> > >> > > >>> >> > > > then go on to use Point_stat to
create
> > > > >> statistics
> > > > >> > >> for
> > > > >> > >> > the
> > > > >> > >> > >> > > >>> matched
> > > > >> > >> > >> > > >>> >> > points.
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > How do I mask out points over
land
> before
> > > it
> > > > >> gets
> > > > >> > to
> > > > >> > >> > the
> > > > >> > >> > >> > > >>> Point_stat
> > > > >> > >> > >> > > >>> >> > step?
> > > > >> > >> > >> > > >>> >> > > > Is there something in the
ASCII2NC
> > > processing
> > > > >> > that I
> > > > >> > >> > can
> > > > >> > >> > >> > add,
> > > > >> > >> > >> > > >>> so I
> > > > >> > >> > >> > > >>> >> > don't
> > > > >> > >> > >> > > >>> >> > > > get these matched points?
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > Thanks in advance!
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > Roz
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > --
> > > > >> > >> > >> > > >>> >> > > > Rosalyn MacCracken
> > > > >> > >> > >> > > >>> >> > > > Support Scientist
> > > > >> > >> > >> > > >>> >> > > >
> > > > >> > >> > >> > > >>> >> > > > Ocean Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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 Applications 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