[Met_help] [rt.rap.ucar.edu #79340] History for Grid Stat Error or regrid_data_plane error

John Halley Gotway via RT met_help at ucar.edu
Mon Feb 6 09:17:06 MST 2017


----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Now that I am able to regrid my data, I am getting an error when running grid_stat against the NetCDF model files.  The command line I am running is:

['/h/WXQC/met-5.1/bin/grid_stat', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150600', '/h/WXQC/met-5.1/data/config/GridStatConfig_ac_updated', '-outdir', '/h/data/global/WXQC/data/met/galwem/ac', '-v', '4']

And the error I am getting is:

DEBUG 1: Default Config File: /h/WXQC/met-5.1/share/met/config/GridStatConfig_default
DEBUG 1: User Config File: /h/WXQC/met-5.1/data/config/GridStatConfig_ac_updated
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -90
DEBUG 4: lon_ll = -0
DEBUG 4: delta_lat = 1
DEBUG 4: delta_lon = 1
DEBUG 4: Nlat = 181
DEBUG 4: Nlon = 360
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -90
DEBUG 4: lon_ll = -0
DEBUG 4: delta_lat = 1
DEBUG 4: delta_lon = 1
DEBUG 4: Nlat = 181
DEBUG 4: Nlon = 360
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of type "FileType_NcMet".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of type "FileType_NcMet".
DEBUG 3: Use the matching forecast and observation grids.
DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181 lat_ll: -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=1840813144
DEBUG 1: Forecast File: /h/data/global/WXQC/data/met/nc_mdl/umm/1701150006
DEBUG 1: Observation File: /h/data/global/WXQC/data/met/nc_mdl/umm/1701150600
DEBUG 3: Reading forecast data for HGT_P500(181,360).
ERROR  : 
ERROR  : MetNcFile::data(NcVar *, const LongArray &, DataPlane &) const ->  bad star count ... 0
ERROR  : 
[1192488575 qcteam hpc9-lsn-01d /h/WXQC/bin]

The command to regrid the data is:

['/h/WXQC/met-5.1/bin/regrid_data_plane', '/h/data/global/WXQC/data/umm/1701150006', 'G003', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006', '-field', 'name="HGT"; level="P500";', '-field', 'name="TMP"; level="Z2";']

I notice the some of the NetCDF file is empty, not sure why.  On the webstite I placed the model file and the NetCDF file produced.

Thanks
Bob



----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Grid Stat Error or regrid_data_plane error
From: John Halley Gotway
Time: Fri Feb 03 15:38:01 2017

Bob,

Looking at the NetCDF files you sent (using ncview), I don't see any
problem with the data being empty.  So I'm not sure what you mean
about it
being empty.

Looking at the error message you sent, I think this is a simple
problem in
how you set up the Grid-Stat config file.  I suspect you've set it up
like
this:

fcst = {
   field = [
      { name = "HGT_P500"; level = [ "(181,360)" ]; }
   ];
}

Instead of "(181,360)", please use "(*,*)" instead.  NetCDF variables
can
have an arbitrary number of dimensions.  For example, many variables
in the
NetCDF output WRF have 4 dimensions... time, vertical level, lat, and
lon.
That cryptic level string with *'s in it tells MET which 2D slice of
lat/lon data to process.  For a WRF file "(3, 5, *, *)" would say get
data
from the 3rd time dimension and 5th vertical level.

However the NetCDF files that the MET tools generate are much simpler,
and
only contain 2 dimensional variables.  So using "(*,*)" suffices.

Please give that a shot and let me know how it goes.

Thanks,
John


On Fri, Feb 3, 2017 at 12:15 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Fri Feb 03 12:15:55 2017: Request 79340 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Grid Stat Error or regrid_data_plane error
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79340 >
>
>
> Now that I am able to regrid my data, I am getting an error when
running
> grid_stat against the NetCDF model files.  The command line I am
running is:
>
> ['/h/WXQC/met-5.1/bin/grid_stat',
'/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150600',
> '/h/WXQC/met-5.1/data/config/GridStatConfig_ac_updated', '-outdir',
> '/h/data/global/WXQC/data/met/galwem/ac', '-v', '4']
>
> And the error I am getting is:
>
> DEBUG 1: Default Config File: /h/WXQC/met-5.1/share/met/
> config/GridStatConfig_default
> DEBUG 1: User Config File: /h/WXQC/met-5.1/data/config/
> GridStatConfig_ac_updated
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -90
> DEBUG 4: lon_ll = -0
> DEBUG 4: delta_lat = 1
> DEBUG 4: delta_lon = 1
> DEBUG 4: Nlat = 181
> DEBUG 4: Nlon = 360
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -90
> DEBUG 4: lon_ll = -0
> DEBUG 4: delta_lat = 1
> DEBUG 4: delta_lon = 1
> DEBUG 4: Nlat = 181
> DEBUG 4: Nlon = 360
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_NcMet".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_NcMet".
> DEBUG 3: Use the matching forecast and observation grids.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1840813144
> DEBUG 1: Forecast File:
/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006
> DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> nc_mdl/umm/1701150600
> DEBUG 3: Reading forecast data for HGT_P500(181,360).
> ERROR  :
> ERROR  : MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
const
> ->  bad star count ... 0
> ERROR  :
> [1192488575 qcteam hpc9-lsn-01d /h/WXQC/bin]
>
> The command to regrid the data is:
>
> ['/h/WXQC/met-5.1/bin/regrid_data_plane',
'/h/data/global/WXQC/data/umm/1701150006',
> 'G003', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006', '-
field',
> 'name="HGT"; level="P500";', '-field', 'name="TMP"; level="Z2";']
>
> I notice the some of the NetCDF file is empty, not sure why.  On the
> webstite I placed the model file and the NetCDF file produced.
>
> Thanks
> Bob
>
>
>

------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #79340] Grid Stat Error or regrid_data_plane error
From: robert.craig.2 at us.af.mil
Time: Fri Feb 03 15:52:24 2017

Weird, I thought I had tried (*,*) and it didn't work, but now it does
so some other issue must have been occurring at the same time.   I had
noticed the NETCDF file had some empty lines in it.  When I did an
ncdump and the end of each data section there were empty fields.
Take a look.  If that is not a big deal then I will ignore it.

Thanks




-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, February 03, 2017 4:38 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79340] Grid Stat Error or
regrid_data_plane error

Bob,

Looking at the NetCDF files you sent (using ncview), I don't see any
problem with the data being empty.  So I'm not sure what you mean
about it being empty.

Looking at the error message you sent, I think this is a simple
problem in how you set up the Grid-Stat config file.  I suspect you've
set it up like
this:

fcst = {
   field = [
      { name = "HGT_P500"; level = [ "(181,360)" ]; }
   ];
}

Instead of "(181,360)", please use "(*,*)" instead.  NetCDF variables
can have an arbitrary number of dimensions.  For example, many
variables in the NetCDF output WRF have 4 dimensions... time, vertical
level, lat, and lon.
That cryptic level string with *'s in it tells MET which 2D slice of
lat/lon data to process.  For a WRF file "(3, 5, *, *)" would say get
data from the 3rd time dimension and 5th vertical level.

However the NetCDF files that the MET tools generate are much simpler,
and only contain 2 dimensional variables.  So using "(*,*)" suffices.

Please give that a shot and let me know how it goes.

Thanks,
John


On Fri, Feb 3, 2017 at 12:15 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Fri Feb 03 12:15:55 2017: Request 79340 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Grid Stat Error or regrid_data_plane error
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79340
> >
>
>
> Now that I am able to regrid my data, I am getting an error when
> running grid_stat against the NetCDF model files.  The command line
I am running is:
>
> ['/h/WXQC/met-5.1/bin/grid_stat',
> '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150600',
> '/h/WXQC/met-5.1/data/config/GridStatConfig_ac_updated', '-outdir',
> '/h/data/global/WXQC/data/met/galwem/ac', '-v', '4']
>
> And the error I am getting is:
>
> DEBUG 1: Default Config File: /h/WXQC/met-5.1/share/met/
> config/GridStatConfig_default DEBUG 1: User Config File:
> /h/WXQC/met-5.1/data/config/ GridStatConfig_ac_updated DEBUG 4:
> Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -90
> DEBUG 4: lon_ll = -0
> DEBUG 4: delta_lat = 1
> DEBUG 4: delta_lon = 1
> DEBUG 4: Nlat = 181
> DEBUG 4: Nlon = 360
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -90
> DEBUG 4: lon_ll = -0
> DEBUG 4: delta_lat = 1
> DEBUG 4: delta_lon = 1
> DEBUG 4: Nlat = 181
> DEBUG 4: Nlon = 360
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> DEBUG 3: Use the matching forecast and observation grids.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1840813144
> DEBUG 1: Forecast File:
> /h/data/global/WXQC/data/met/nc_mdl/umm/1701150006
> DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> nc_mdl/umm/1701150600
> DEBUG 3: Reading forecast data for HGT_P500(181,360).
> ERROR  :
> ERROR  : MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
> const
> ->  bad star count ... 0
> ERROR  :
> [1192488575 qcteam hpc9-lsn-01d /h/WXQC/bin]
>
> The command to regrid the data is:
>
> ['/h/WXQC/met-5.1/bin/regrid_data_plane',
> '/h/data/global/WXQC/data/umm/1701150006',
> 'G003', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> '-field', 'name="HGT"; level="P500";', '-field', 'name="TMP";
> level="Z2";']
>
> I notice the some of the NetCDF file is empty, not sure why.  On the
> webstite I placed the model file and the NetCDF file produced.
>
> Thanks
> Bob
>
>
>



------------------------------------------------
Subject: Grid Stat Error or regrid_data_plane error
From: John Halley Gotway
Time: Fri Feb 03 16:32:07 2017

Bob,

I assume you're talking about this sort of thing:
  245.9765, 245.8765, 245.8765, 245.8765, 245.8765, 245.8765,
245.8765,
    245.9765, 245.8765,
  _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
_,
_,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
_, _,
    _, _, _, _, _, _, _,

Those underscores indicate a fill value.  I ran the following
plot_data_plane command to view the HGT_P500 data:
   met-5.1/bin/plot_data_plane 1701150006 HGT_P500.ps
'name="HGT_P500";
level="(*,*)";'

A png version of the resulting plot is attached.  As you can see, the
data
looks fine.

Using ncview I can see that those fill values appear along one row at
the
top of the grid and one column along the left side of the grid.  There
must
not have been any valid data near those lat/lon's in the input grid.

Here's the input grid definition:

[johnhg at number5]% wgrib2 -d 1 -V 1701150006_grb2
1:0:vt=2017011506:1000 mb:6 hour fcst:TMP Temperature [K]:
    ndata=1769472:undef=0:mean=279.738:min=222.75:max=312.75
    grid_template=0:winds(N/S):
        lat-lon grid:(1536 x 1152) units 1e-06 input WE:SN output
WE:SN res
48
        lat -89.921875 to 89.921875 by 0.156250
        lon 0.117187 to 359.882812 by 0.234375 #points=1769472

And the output grid definition starts at 0 degrees longitude.  But 0
degrees longitude doesn't fall within the input grid (which starts at
0.117187 longitude).  That's why you're getting missing output values
along
the edge.  So I'd say nothing to worry about.

Note that the default regridding logic for regrid_data_plane is
nearest
neighbor.  For heights and temperatures, you might consider using
bilinear
interpolation instead.  You can specify that using:
   -method BILIN -width 2

Thanks,
John


On Fri, Feb 3, 2017 at 3:52 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79340 >
>
> Weird, I thought I had tried (*,*) and it didn't work, but now it
does so
> some other issue must have been occurring at the same time.   I had
noticed
> the NETCDF file had some empty lines in it.  When I did an ncdump
and the
> end of each data section there were empty fields.   Take a look.  If
that
> is not a big deal then I will ignore it.
>
> Thanks
>
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, February 03, 2017 4:38 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79340] Grid Stat Error or
> regrid_data_plane error
>
> Bob,
>
> Looking at the NetCDF files you sent (using ncview), I don't see any
> problem with the data being empty.  So I'm not sure what you mean
about it
> being empty.
>
> Looking at the error message you sent, I think this is a simple
problem in
> how you set up the Grid-Stat config file.  I suspect you've set it
up like
> this:
>
> fcst = {
>    field = [
>       { name = "HGT_P500"; level = [ "(181,360)" ]; }
>    ];
> }
>
> Instead of "(181,360)", please use "(*,*)" instead.  NetCDF
variables can
> have an arbitrary number of dimensions.  For example, many variables
in the
> NetCDF output WRF have 4 dimensions... time, vertical level, lat,
and lon.
> That cryptic level string with *'s in it tells MET which 2D slice of
> lat/lon data to process.  For a WRF file "(3, 5, *, *)" would say
get data
> from the 3rd time dimension and 5th vertical level.
>
> However the NetCDF files that the MET tools generate are much
simpler, and
> only contain 2 dimensional variables.  So using "(*,*)" suffices.
>
> Please give that a shot and let me know how it goes.
>
> Thanks,
> John
>
>
> On Fri, Feb 3, 2017 at 12:15 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Feb 03 12:15:55 2017: Request 79340 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> >        Queue: met_help
> >      Subject: Grid Stat Error or regrid_data_plane error
> >        Owner: Nobody
> >   Requestors: robert.craig.2 at us.af.mil
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79340
> > >
> >
> >
> > Now that I am able to regrid my data, I am getting an error when
> > running grid_stat against the NetCDF model files.  The command
line I am
> running is:
> >
> > ['/h/WXQC/met-5.1/bin/grid_stat',
> > '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> > '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150600',
> > '/h/WXQC/met-5.1/data/config/GridStatConfig_ac_updated', '-
outdir',
> > '/h/data/global/WXQC/data/met/galwem/ac', '-v', '4']
> >
> > And the error I am getting is:
> >
> > DEBUG 1: Default Config File: /h/WXQC/met-5.1/share/met/
> > config/GridStatConfig_default DEBUG 1: User Config File:
> > /h/WXQC/met-5.1/data/config/ GridStatConfig_ac_updated DEBUG 4:
> > Met2dDataFileFactory::new_met_2d_data_file() -> created new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -90
> > DEBUG 4: lon_ll = -0
> > DEBUG 4: delta_lat = 1
> > DEBUG 4: delta_lon = 1
> > DEBUG 4: Nlat = 181
> > DEBUG 4: Nlon = 360
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -90
> > DEBUG 4: lon_ll = -0
> > DEBUG 4: delta_lat = 1
> > DEBUG 4: delta_lon = 1
> > DEBUG 4: Nlat = 181
> > DEBUG 4: Nlon = 360
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > DEBUG 3: Use the matching forecast and observation grids.
> > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> > GSL_RNG_TYPE=mt19937
> > GSL_RNG_SEED=1840813144
> > DEBUG 1: Forecast File:
> > /h/data/global/WXQC/data/met/nc_mdl/umm/1701150006
> > DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> > nc_mdl/umm/1701150600
> > DEBUG 3: Reading forecast data for HGT_P500(181,360).
> > ERROR  :
> > ERROR  : MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
> > const
> > ->  bad star count ... 0
> > ERROR  :
> > [1192488575 qcteam hpc9-lsn-01d /h/WXQC/bin]
> >
> > The command to regrid the data is:
> >
> > ['/h/WXQC/met-5.1/bin/regrid_data_plane',
> > '/h/data/global/WXQC/data/umm/1701150006',
> > 'G003', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> > '-field', 'name="HGT"; level="P500";', '-field', 'name="TMP";
> > level="Z2";']
> >
> > I notice the some of the NetCDF file is empty, not sure why.  On
the
> > webstite I placed the model file and the NetCDF file produced.
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>

------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #79340] Grid Stat Error or regrid_data_plane error
From: robert.craig.2 at us.af.mil
Time: Mon Feb 06 07:07:51 2017

Okay, thanks for verifying it was expected.

Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, February 03, 2017 5:32 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79340] Grid Stat Error or
regrid_data_plane error

Bob,

I assume you're talking about this sort of thing:
  245.9765, 245.8765, 245.8765, 245.8765, 245.8765, 245.8765,
245.8765,
    245.9765, 245.8765,
  _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
_, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
_, _,
    _, _, _, _, _, _, _,

Those underscores indicate a fill value.  I ran the following
plot_data_plane command to view the HGT_P500 data:
   met-5.1/bin/plot_data_plane 1701150006 HGT_P500.ps
'name="HGT_P500"; level="(*,*)";'

A png version of the resulting plot is attached.  As you can see, the
data looks fine.

Using ncview I can see that those fill values appear along one row at
the top of the grid and one column along the left side of the grid.
There must not have been any valid data near those lat/lon's in the
input grid.

Here's the input grid definition:

[johnhg at number5]% wgrib2 -d 1 -V 1701150006_grb2
1:0:vt=2017011506:1000 mb:6 hour fcst:TMP Temperature [K]:
    ndata=1769472:undef=0:mean=279.738:min=222.75:max=312.75
    grid_template=0:winds(N/S):
        lat-lon grid:(1536 x 1152) units 1e-06 input WE:SN output
WE:SN res
48
        lat -89.921875 to 89.921875 by 0.156250
        lon 0.117187 to 359.882812 by 0.234375 #points=1769472

And the output grid definition starts at 0 degrees longitude.  But 0
degrees longitude doesn't fall within the input grid (which starts at
0.117187 longitude).  That's why you're getting missing output values
along the edge.  So I'd say nothing to worry about.

Note that the default regridding logic for regrid_data_plane is
nearest neighbor.  For heights and temperatures, you might consider
using bilinear interpolation instead.  You can specify that using:
   -method BILIN -width 2

Thanks,
John


On Fri, Feb 3, 2017 at 3:52 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79340 >
>
> Weird, I thought I had tried (*,*) and it didn't work, but now it
does so
> some other issue must have been occurring at the same time.   I had
noticed
> the NETCDF file had some empty lines in it.  When I did an ncdump
and the
> end of each data section there were empty fields.   Take a look.  If
that
> is not a big deal then I will ignore it.
>
> Thanks
>
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, February 03, 2017 4:38 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79340] Grid Stat Error or
> regrid_data_plane error
>
> Bob,
>
> Looking at the NetCDF files you sent (using ncview), I don't see any
> problem with the data being empty.  So I'm not sure what you mean
> about it being empty.
>
> Looking at the error message you sent, I think this is a simple
> problem in how you set up the Grid-Stat config file.  I suspect
you've
> set it up like
> this:
>
> fcst = {
>    field = [
>       { name = "HGT_P500"; level = [ "(181,360)" ]; }
>    ];
> }
>
> Instead of "(181,360)", please use "(*,*)" instead.  NetCDF
variables
> can have an arbitrary number of dimensions.  For example, many
> variables in the NetCDF output WRF have 4 dimensions... time,
vertical level, lat, and lon.
> That cryptic level string with *'s in it tells MET which 2D slice of
> lat/lon data to process.  For a WRF file "(3, 5, *, *)" would say
get
> data from the 3rd time dimension and 5th vertical level.
>
> However the NetCDF files that the MET tools generate are much
simpler,
> and only contain 2 dimensional variables.  So using "(*,*)"
suffices.
>
> Please give that a shot and let me know how it goes.
>
> Thanks,
> John
>
>
> On Fri, Feb 3, 2017 at 12:15 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Feb 03 12:15:55 2017: Request 79340 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> >        Queue: met_help
> >      Subject: Grid Stat Error or regrid_data_plane error
> >        Owner: Nobody
> >   Requestors: robert.craig.2 at us.af.mil
> >       Status: new
> >  Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79340
> > >
> >
> >
> > Now that I am able to regrid my data, I am getting an error when
> > running grid_stat against the NetCDF model files.  The command
line
> > I am
> running is:
> >
> > ['/h/WXQC/met-5.1/bin/grid_stat',
> > '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> > '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150600',
> > '/h/WXQC/met-5.1/data/config/GridStatConfig_ac_updated', '-
outdir',
> > '/h/data/global/WXQC/data/met/galwem/ac', '-v', '4']
> >
> > And the error I am getting is:
> >
> > DEBUG 1: Default Config File: /h/WXQC/met-5.1/share/met/
> > config/GridStatConfig_default DEBUG 1: User Config File:
> > /h/WXQC/met-5.1/data/config/ GridStatConfig_ac_updated DEBUG 4:
> > Met2dDataFileFactory::new_met_2d_data_file() -> created new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -90
> > DEBUG 4: lon_ll = -0
> > DEBUG 4: delta_lat = 1
> > DEBUG 4: delta_lon = 1
> > DEBUG 4: Nlat = 181
> > DEBUG 4: Nlon = 360
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -90
> > DEBUG 4: lon_ll = -0
> > DEBUG 4: delta_lat = 1
> > DEBUG 4: delta_lon = 1
> > DEBUG 4: Nlat = 181
> > DEBUG 4: Nlon = 360
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > DEBUG 3: Use the matching forecast and observation grids.
> > DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> > -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> > GSL_RNG_TYPE=mt19937
> > GSL_RNG_SEED=1840813144
> > DEBUG 1: Forecast File:
> > /h/data/global/WXQC/data/met/nc_mdl/umm/1701150006
> > DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> > nc_mdl/umm/1701150600
> > DEBUG 3: Reading forecast data for HGT_P500(181,360).
> > ERROR  :
> > ERROR  : MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
> > const
> > ->  bad star count ... 0
> > ERROR  :
> > [1192488575 qcteam hpc9-lsn-01d /h/WXQC/bin]
> >
> > The command to regrid the data is:
> >
> > ['/h/WXQC/met-5.1/bin/regrid_data_plane',
> > '/h/data/global/WXQC/data/umm/1701150006',
> > 'G003', '/h/data/global/WXQC/data/met/nc_mdl/umm/1701150006',
> > '-field', 'name="HGT"; level="P500";', '-field', 'name="TMP";
> > level="Z2";']
> >
> > I notice the some of the NetCDF file is empty, not sure why.  On
the
> > webstite I placed the model file and the NetCDF file produced.
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>



------------------------------------------------


More information about the Met_help mailing list