[Met_help] [rt.rap.ucar.edu #89709] History for ensemble_stat regrid G003 not defined
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:06:53 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I am working on the Unified Verification project at NRL Monterey, and trying
to support Dr. McLay with the ensemble_stat
Dr. McLay does a regrid_data_plane for global lat lon projection with the G003
regrid_data_plane PYTHON_NUMPY G003 navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
\
-field 'name="./read_NRL_binary.py
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
level="'${plev}'";' \
however, when we next run ensemble_stat with the regrid config set as
regrid = {
to_grid = G003;
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
we get a "G003" not defined in scope
ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC -grid_obs
verifecmwf*2016122000*.nc
DEBUG 1: Default Config File:
/software/depot/met-8.0_bugfix/share/met/config/EnsembleStatConfig_default
DEBUG 1: User Config File: EnsembleStatConfigGC
ERROR :
ERROR : do_assign_id() -> identifier "G003" not defined in this scope!
Would you please let me know how to determine what to_grid's are within scope,
or where to know what "not defined in scope" means? To me, the error is
indicating G003 has not been registered for the regrid to_grid.
--
Mr. Glen CARL
NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
831.325.6269
glen.carl.ctr at nrlmry.navy.mil
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: John Halley Gotway
Time: Mon Apr 15 10:32:29 2019
Mr. Glen Carl,
I see you have a question about what pre-defined grids are supported
in
MET. Currently, those grids are hard-coded in this source code file:
met-8.0/src/libcode/vx_grid/find_grid_by_name.h
In the long run, it'd be better to read these from a static ascii file
at
runtime to enable the users to add to or modify the list. But for
now,
that's where you'll find them.
I see you have a specific question about grid number 3. I think this
really is just a configuration issue that's easily fixed. You need to
request a named grid as a string... meaning you need to put double-
quotes
around "G003". Please try this out:
regrid = {
to_grid = "G003";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
Hopefully that fixes it.
Thanks,
John Halley Gotway
On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> Queue: met_help
> Subject: ensemble_stat regrid G003 not defined
> Owner: Nobody
> Requestors: glen.carl.ctr at nrlmry.navy.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
>
> I am working on the Unified Verification project at NRL Monterey,
and
> trying
> to support Dr. McLay with the ensemble_stat
>
> Dr. McLay does a regrid_data_plane for global lat lon projection
with the
> G003
>
> regrid_data_plane PYTHON_NUMPY G003
> navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> \
> -field 'name="./read_NRL_binary.py
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
>
> level="'${plev}'";' \
>
> however, when we next run ensemble_stat with the regrid config set
as
> regrid = {
> to_grid = G003;
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> we get a "G003" not defined in scope
>
> ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
> DEBUG 1: Default Config File:
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> DEBUG 1: User Config File: EnsembleStatConfigGC
> ERROR :
> ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
>
> Would you please let me know how to determine what to_grid's are
within
> scope,
> or where to know what "not defined in scope" means? To me, the
error is
> indicating G003 has not been registered for the regrid to_grid.
>
> --
> Mr. Glen CARL
> NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> 831.325.6269
> glen.carl.ctr at nrlmry.navy.mil
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Mon Apr 15 10:48:40 2019
Thanks for the confirmation of the double quote. I tried it before,
and was
getting the dataplane error. I still get a range check error, however,
I am
confident it is reading the grid G003. We still do not understand why
we are
triggering the two_to_one error. Both with "G003" and with a
specification fo
the Nx, Ny with the latlon input.
Thanks again,
Glen
regrid = {
to_grid = "G003";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
ERROR :
ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0,
0), (x,
y) = (0, 0)
I also set the latlon for what our G003 would set at and also get the
DataPlane error.
regrid = {
to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0,
0), (x,
y) = (0, 0)
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, April 15, 2019 9:33 AM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
defined
Mr. Glen Carl,
I see you have a question about what pre-defined grids are supported
in
MET. Currently, those grids are hard-coded in this source code file:
met-8.0/src/libcode/vx_grid/find_grid_by_name.h
In the long run, it'd be better to read these from a static ascii file
at
runtime to enable the users to add to or modify the list. But for
now,
that's where you'll find them.
I see you have a specific question about grid number 3. I think this
really is just a configuration issue that's easily fixed. You need to
request a named grid as a string... meaning you need to put double-
quotes
around "G003". Please try this out:
regrid = {
to_grid = "G003";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
Hopefully that fixes it.
Thanks,
John Halley Gotway
On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> Queue: met_help
> Subject: ensemble_stat regrid G003 not defined
> Owner: Nobody
> Requestors: glen.carl.ctr at nrlmry.navy.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
>
> I am working on the Unified Verification project at NRL Monterey,
and
> trying
> to support Dr. McLay with the ensemble_stat
>
> Dr. McLay does a regrid_data_plane for global lat lon projection
with the
> G003
>
> regrid_data_plane PYTHON_NUMPY G003
> navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> \
> -field 'name="./read_NRL_binary.py
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
>
> level="'${plev}'";' \
>
> however, when we next run ensemble_stat with the regrid config set
as
> regrid = {
> to_grid = G003;
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> we get a "G003" not defined in scope
>
> ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
> DEBUG 1: Default Config File:
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> DEBUG 1: User Config File: EnsembleStatConfigGC
> ERROR :
> ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
>
> Would you please let me know how to determine what to_grid's are
within
> scope,
> or where to know what "not defined in scope" means? To me, the
error is
> indicating G003 has not been registered for the regrid to_grid.
>
> --
> Mr. Glen CARL
> NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> 831.325.6269
> glen.carl.ctr at nrlmry.navy.mil
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Mon Apr 15 11:05:34 2019
Looking up find_grid_by_name.h, I changed the latlon input to match,
and now I
am not getting the DataPlane error.
from find_grid_by_name.h
static const LatLonData ncep_latlon_grids [] = {
{ "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
my new config
regrid = {
to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
I was using the decimal placement from my netcdf files before.
However, now the error disappeared.
we are only able to generate on statistic file
// Statistical output types
//
output_flag = {
ecnt = STAT;
rhist = STAT;
phist = STAT;
orank = STAT;
ssvar = STAT;
relp = STAT;
}
============= OUTPUT ==================
ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
verifecmwf*2016122000*.nc
DEBUG 1: Default Config File:
/software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
DEBUG 1: User Config File: EnsembleStatConfigGC
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=699970652
DEBUG 1: Ensemble Files[20]:
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
DEBUG 1: Gridded Observation Files[1]:
DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
DEBUG 2:
DEBUG
2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
DEBUG 2: Processing masking regions.
DEBUG 2:
DEBUG
2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2:
DEBUG
2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing ensemble mean file:
./ensemble_stat_20161220_000000V_ens.nc
DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*) versus
geopht_pre_0500.0(*,*), for observation type ECANL, over region FULL,
for
interpolation method NEAREST(1), using 65160 pairs.
WARNING:
WARNING: PairDataEnsemble::compute_ssvar() -> writing at least 1000
SSVAR
output lines. Increase the ssvar_bin_size config file setting for this
variable to reduce the number of variance bins.
WARNING:
DEBUG 2:
DEBUG
2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
-----Original Message-----
From: Carl, Mr. Glen, Contractor, Code 7532
Sent: Monday, April 15, 2019 9:49 AM
To: 'met_help at ucar.edu'
Cc: McLay, Dr. Justin
Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
defined
Thanks for the confirmation of the double quote. I tried it before,
and was
getting the dataplane error. I still get a range check error, however,
I am
confident it is reading the grid G003. We still do not understand why
we are
triggering the two_to_one error. Both with "G003" and with a
specification fo
the Nx, Ny with the latlon input.
Thanks again,
Glen
regrid = {
to_grid = "G003";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
ERROR :
ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0,
0), (x,
y) = (0, 0)
I also set the latlon for what our G003 would set at and also get the
DataPlane error.
regrid = {
to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0,
0), (x,
y) = (0, 0)
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, April 15, 2019 9:33 AM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
defined
Mr. Glen Carl,
I see you have a question about what pre-defined grids are supported
in
MET. Currently, those grids are hard-coded in this source code file:
met-8.0/src/libcode/vx_grid/find_grid_by_name.h
In the long run, it'd be better to read these from a static ascii file
at
runtime to enable the users to add to or modify the list. But for
now,
that's where you'll find them.
I see you have a specific question about grid number 3. I think this
really is just a configuration issue that's easily fixed. You need to
request a named grid as a string... meaning you need to put double-
quotes
around "G003". Please try this out:
regrid = {
to_grid = "G003";
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
Hopefully that fixes it.
Thanks,
John Halley Gotway
On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> Queue: met_help
> Subject: ensemble_stat regrid G003 not defined
> Owner: Nobody
> Requestors: glen.carl.ctr at nrlmry.navy.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
>
> I am working on the Unified Verification project at NRL Monterey,
and
> trying
> to support Dr. McLay with the ensemble_stat
>
> Dr. McLay does a regrid_data_plane for global lat lon projection
with the
> G003
>
> regrid_data_plane PYTHON_NUMPY G003
> navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> \
> -field 'name="./read_NRL_binary.py
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
>
> level="'${plev}'";' \
>
> however, when we next run ensemble_stat with the regrid config set
as
> regrid = {
> to_grid = G003;
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> we get a "G003" not defined in scope
>
> ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
> DEBUG 1: Default Config File:
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> DEBUG 1: User Config File: EnsembleStatConfigGC
> ERROR :
> ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
>
> Would you please let me know how to determine what to_grid's are
within
> scope,
> or where to know what "not defined in scope" means? To me, the
error is
> indicating G003 has not been registered for the regrid to_grid.
>
> --
> Mr. Glen CARL
> NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> 831.325.6269
> glen.carl.ctr at nrlmry.navy.mil
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: John Halley Gotway
Time: Mon Apr 15 11:42:15 2019
Glen,
I read through your email but am not sure what remaining questions you
have.
Should we debug the source of the "two_to_one" error? Or are you
wondering
why you're only getting an "ensemble_stat...*.stat" file?
John
On Mon, Apr 15, 2019 at 11:05 AM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
> Looking up find_grid_by_name.h, I changed the latlon input to match,
and
> now I
> am not getting the DataPlane error.
>
> from find_grid_by_name.h
> static const LatLonData ncep_latlon_grids [] = {
> { "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
>
> my new config
> regrid = {
> to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> I was using the decimal placement from my netcdf files before.
> However, now the error disappeared.
>
>
> we are only able to generate on statistic file
>
> // Statistical output types
> //
> output_flag = {
> ecnt = STAT;
> rhist = STAT;
> phist = STAT;
> orank = STAT;
> ssvar = STAT;
> relp = STAT;
> }
>
> ============= OUTPUT ==================
>
> ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
> DEBUG 1: Default Config File:
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> DEBUG 1: User Config File: EnsembleStatConfigGC
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=699970652
> DEBUG 1: Ensemble Files[20]:
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
> DEBUG 1: Gridded Observation Files[1]:
> DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
> DEBUG 2: Processing masking regions.
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Processing ensemble mean file:
> ./ensemble_stat_20161220_000000V_ens.nc
> DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*)
versus
> geopht_pre_0500.0(*,*), for observation type ECANL, over region
FULL, for
> interpolation method NEAREST(1), using 65160 pairs.
> WARNING:
> WARNING: PairDataEnsemble::compute_ssvar() -> writing at least 1000
SSVAR
> output lines. Increase the ssvar_bin_size config file setting for
this
> variable to reduce the number of variance bins.
> WARNING:
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
> DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
> DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
>
>
> -----Original Message-----
> From: Carl, Mr. Glen, Contractor, Code 7532
> Sent: Monday, April 15, 2019 9:49 AM
> To: 'met_help at ucar.edu'
> Cc: McLay, Dr. Justin
> Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Thanks for the confirmation of the double quote. I tried it before,
and was
> getting the dataplane error. I still get a range check error,
however, I am
> confident it is reading the grid G003. We still do not understand
why we
> are
> triggering the two_to_one error. Both with "G003" and with a
specification
> fo
> the Nx, Ny with the latlon input.
> Thanks again,
> Glen
>
> regrid = {
> to_grid = "G003";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
> ERROR :
> ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0, 0),
> (x,
> y) = (0, 0)
>
> I also set the latlon for what our G003 would set at and also get
the
> DataPlane error.
>
> regrid = {
> to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0,
0),
> (x,
> y) = (0, 0)
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 15, 2019 9:33 AM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Mr. Glen Carl,
>
> I see you have a question about what pre-defined grids are supported
in
> MET. Currently, those grids are hard-coded in this source code
file:
> met-8.0/src/libcode/vx_grid/find_grid_by_name.h
>
> In the long run, it'd be better to read these from a static ascii
file at
> runtime to enable the users to add to or modify the list. But for
now,
> that's where you'll find them.
>
> I see you have a specific question about grid number 3. I think
this
> really is just a configuration issue that's easily fixed. You need
to
> request a named grid as a string... meaning you need to put double-
quotes
> around "G003". Please try this out:
>
> regrid = {
> to_grid = "G003";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> Hopefully that fixes it.
>
> Thanks,
> John Halley Gotway
>
> On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT <met_help at ucar.edu> wrote:
>
> >
> > Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > Queue: met_help
> > Subject: ensemble_stat regrid G003 not defined
> > Owner: Nobody
> > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> >
> >
> > I am working on the Unified Verification project at NRL Monterey,
and
> > trying
> > to support Dr. McLay with the ensemble_stat
> >
> > Dr. McLay does a regrid_data_plane for global lat lon projection
with the
> > G003
> >
> > regrid_data_plane PYTHON_NUMPY G003
> > navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> > \
> > -field 'name="./read_NRL_binary.py
> >
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
> >
> > level="'${plev}'";' \
> >
> > however, when we next run ensemble_stat with the regrid config set
as
> > regrid = {
> > to_grid = G003;
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > we get a "G003" not defined in scope
> >
> > ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> > verifecmwf*2016122000*.nc
> > DEBUG 1: Default Config File:
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > DEBUG 1: User Config File: EnsembleStatConfigGC
> > ERROR :
> > ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
> >
> > Would you please let me know how to determine what to_grid's are
within
> > scope,
> > or where to know what "not defined in scope" means? To me, the
error is
> > indicating G003 has not been registered for the regrid to_grid.
> >
> > --
> > Mr. Glen CARL
> > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > 831.325.6269
> > glen.carl.ctr at nrlmry.navy.mil
> >
> >
> >
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Mon Apr 15 12:04:27 2019
1) I do not think the "G003" is working, and I would have someone
debug why it
is generating the two_to_one error.
2) We really want to generate a statistic file for " ecnt = STAT ",
and that
is not generating nor is it giving messages why not. We get the ssvar
stat
file from the config, and are not sure why the on stat file is not
generating
for ecnt.
Thanks,
Glen
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, April 15, 2019 10:42 AM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
defined
Glen,
I read through your email but am not sure what remaining questions you
have.
Should we debug the source of the "two_to_one" error? Or are you
wondering
why you're only getting an "ensemble_stat...*.stat" file?
John
On Mon, Apr 15, 2019 at 11:05 AM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
> Looking up find_grid_by_name.h, I changed the latlon input to match,
and
> now I
> am not getting the DataPlane error.
>
> from find_grid_by_name.h
> static const LatLonData ncep_latlon_grids [] = {
> { "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
>
> my new config
> regrid = {
> to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> I was using the decimal placement from my netcdf files before.
> However, now the error disappeared.
>
>
> we are only able to generate on statistic file
>
> // Statistical output types
> //
> output_flag = {
> ecnt = STAT;
> rhist = STAT;
> phist = STAT;
> orank = STAT;
> ssvar = STAT;
> relp = STAT;
> }
>
> ============= OUTPUT ==================
>
> ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
> DEBUG 1: Default Config File:
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> DEBUG 1: User Config File: EnsembleStatConfigGC
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=699970652
> DEBUG 1: Ensemble Files[20]:
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
> DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
> DEBUG 1: Gridded Observation Files[1]:
> DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
> DEBUG 2: Processing masking regions.
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Processing ensemble mean file:
> ./ensemble_stat_20161220_000000V_ens.nc
> DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*)
versus
> geopht_pre_0500.0(*,*), for observation type ECANL, over region
FULL, for
> interpolation method NEAREST(1), using 65160 pairs.
> WARNING:
> WARNING: PairDataEnsemble::compute_ssvar() -> writing at least 1000
SSVAR
> output lines. Increase the ssvar_bin_size config file setting for
this
> variable to reduce the number of variance bins.
> WARNING:
> DEBUG 2:
> DEBUG
> 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
> DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
> DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
>
>
> -----Original Message-----
> From: Carl, Mr. Glen, Contractor, Code 7532
> Sent: Monday, April 15, 2019 9:49 AM
> To: 'met_help at ucar.edu'
> Cc: McLay, Dr. Justin
> Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Thanks for the confirmation of the double quote. I tried it before,
and was
> getting the dataplane error. I still get a range check error,
however, I am
> confident it is reading the grid G003. We still do not understand
why we
> are
> triggering the two_to_one error. Both with "G003" and with a
specification
> fo
> the Nx, Ny with the latlon input.
> Thanks again,
> Glen
>
> regrid = {
> to_grid = "G003";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
> ERROR :
> ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0, 0),
> (x,
> y) = (0, 0)
>
> I also set the latlon for what our G003 would set at and also get
the
> DataPlane error.
>
> regrid = {
> to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0,
0),
> (x,
> y) = (0, 0)
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 15, 2019 9:33 AM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Mr. Glen Carl,
>
> I see you have a question about what pre-defined grids are supported
in
> MET. Currently, those grids are hard-coded in this source code
file:
> met-8.0/src/libcode/vx_grid/find_grid_by_name.h
>
> In the long run, it'd be better to read these from a static ascii
file at
> runtime to enable the users to add to or modify the list. But for
now,
> that's where you'll find them.
>
> I see you have a specific question about grid number 3. I think
this
> really is just a configuration issue that's easily fixed. You need
to
> request a named grid as a string... meaning you need to put double-
quotes
> around "G003". Please try this out:
>
> regrid = {
> to_grid = "G003";
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
> Hopefully that fixes it.
>
> Thanks,
> John Halley Gotway
>
> On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT <met_help at ucar.edu> wrote:
>
> >
> > Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > Queue: met_help
> > Subject: ensemble_stat regrid G003 not defined
> > Owner: Nobody
> > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> >
> >
> > I am working on the Unified Verification project at NRL Monterey,
and
> > trying
> > to support Dr. McLay with the ensemble_stat
> >
> > Dr. McLay does a regrid_data_plane for global lat lon projection
with the
> > G003
> >
> > regrid_data_plane PYTHON_NUMPY G003
> > navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> > \
> > -field 'name="./read_NRL_binary.py
> >
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
> >
> > level="'${plev}'";' \
> >
> > however, when we next run ensemble_stat with the regrid config set
as
> > regrid = {
> > to_grid = G003;
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > we get a "G003" not defined in scope
> >
> > ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> > verifecmwf*2016122000*.nc
> > DEBUG 1: Default Config File:
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > DEBUG 1: User Config File: EnsembleStatConfigGC
> > ERROR :
> > ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
> >
> > Would you please let me know how to determine what to_grid's are
within
> > scope,
> > or where to know what "not defined in scope" means? To me, the
error is
> > indicating G003 has not been registered for the regrid to_grid.
> >
> > --
> > Mr. Glen CARL
> > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > 831.325.6269
> > glen.carl.ctr at nrlmry.navy.mil
> >
> >
> >
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: John Halley Gotway
Time: Mon Apr 15 12:21:01 2019
Glen,
Since you've set all the entries for "output_flag" to STAT, that means
that
all the statistical output will be written to a single .stat output.
I
assume what you're saying is that when you look in the .stat output
file,
you don't find any ECNT output lines. If you'd like to output also
written
to a separate _ecnt.txt file, you can set the config file like this:
*ecnt = BOTH;*
I just tested running ensemble-stat by regridding to G003 with the
config
file using some local test data, and it all worked as expected. So
I'm not
able to replicate the behavior you describe. If you'd like, you could
post
some sample data to our ftp site. I'll go grab it and try to recreate
the
behavior you're seeing. I'd need all the input files you're using to
run
this command:
ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC -grid_obs
verifecmwf*2016122000*.nc
Here are instructions for posting to our ftp site:
https://dtcenter.org/met/users/support/met_help.php#ftp
Thanks
John
On Mon, Apr 15, 2019 at 12:04 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
> 1) I do not think the "G003" is working, and I would have someone
debug
> why it
> is generating the two_to_one error.
>
> 2) We really want to generate a statistic file for " ecnt = STAT
", and
> that
> is not generating nor is it giving messages why not. We get the
ssvar stat
> file from the config, and are not sure why the on stat file is not
> generating
> for ecnt.
>
> Thanks,
> Glen
>
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 15, 2019 10:42 AM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Glen,
>
> I read through your email but am not sure what remaining questions
you
> have.
>
> Should we debug the source of the "two_to_one" error? Or are you
wondering
> why you're only getting an "ensemble_stat...*.stat" file?
>
> John
>
> On Mon, Apr 15, 2019 at 11:05 AM Carl, Mr. Glen, Contractor, Code
7532 via
> RT <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> >
> > Looking up find_grid_by_name.h, I changed the latlon input to
match, and
> > now I
> > am not getting the DataPlane error.
> >
> > from find_grid_by_name.h
> > static const LatLonData ncep_latlon_grids [] = {
> > { "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
> >
> > my new config
> > regrid = {
> > to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > I was using the decimal placement from my netcdf files before.
> > However, now the error disappeared.
> >
> >
> > we are only able to generate on statistic file
> >
> > // Statistical output types
> > //
> > output_flag = {
> > ecnt = STAT;
> > rhist = STAT;
> > phist = STAT;
> > orank = STAT;
> > ssvar = STAT;
> > relp = STAT;
> > }
> >
> > ============= OUTPUT ==================
> >
> > ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> > verifecmwf*2016122000*.nc
> > DEBUG 1: Default Config File:
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > DEBUG 1: User Config File: EnsembleStatConfigGC
> > GSL_RNG_TYPE=mt19937
> > GSL_RNG_SEED=699970652
> > DEBUG 1: Ensemble Files[20]:
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
> > DEBUG 1: Gridded Observation Files[1]:
> > DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
> > DEBUG 2: Processing masking regions.
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2: Processing ensemble mean file:
> > ./ensemble_stat_20161220_000000V_ens.nc
> > DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*)
versus
> > geopht_pre_0500.0(*,*), for observation type ECANL, over region
FULL, for
> > interpolation method NEAREST(1), using 65160 pairs.
> > WARNING:
> > WARNING: PairDataEnsemble::compute_ssvar() -> writing at least
1000 SSVAR
> > output lines. Increase the ssvar_bin_size config file setting for
this
> > variable to reduce the number of variance bins.
> > WARNING:
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
> > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
> > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
> >
> >
> > -----Original Message-----
> > From: Carl, Mr. Glen, Contractor, Code 7532
> > Sent: Monday, April 15, 2019 9:49 AM
> > To: 'met_help at ucar.edu'
> > Cc: McLay, Dr. Justin
> > Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > defined
> >
> > Thanks for the confirmation of the double quote. I tried it
before, and
> was
> > getting the dataplane error. I still get a range check error,
however, I
> am
> > confident it is reading the grid G003. We still do not understand
why we
> > are
> > triggering the two_to_one error. Both with "G003" and with a
> specification
> > fo
> > the Nx, Ny with the latlon input.
> > Thanks again,
> > Glen
> >
> > regrid = {
> > to_grid = "G003";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> > ERROR :
> > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0, 0),
> > (x,
> > y) = (0, 0)
> >
> > I also set the latlon for what our G003 would set at and also get
the
> > DataPlane error.
> >
> > regrid = {
> > to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0, 0),
> > (x,
> > y) = (0, 0)
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, April 15, 2019 9:33 AM
> > To: Carl, Mr. Glen, Contractor, Code 7532
> > Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > defined
> >
> > Mr. Glen Carl,
> >
> > I see you have a question about what pre-defined grids are
supported in
> > MET. Currently, those grids are hard-coded in this source code
file:
> > met-8.0/src/libcode/vx_grid/find_grid_by_name.h
> >
> > In the long run, it'd be better to read these from a static ascii
file at
> > runtime to enable the users to add to or modify the list. But for
now,
> > that's where you'll find them.
> >
> > I see you have a specific question about grid number 3. I think
this
> > really is just a configuration issue that's easily fixed. You
need to
> > request a named grid as a string... meaning you need to put
double-quotes
> > around "G003". Please try this out:
> >
> > regrid = {
> > to_grid = "G003";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > Hopefully that fixes it.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code
7532
> via
> > RT <met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > Queue: met_help
> > > Subject: ensemble_stat regrid G003 not defined
> > > Owner: Nobody
> > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709
> >
> > >
> > >
> > > I am working on the Unified Verification project at NRL
Monterey, and
> > > trying
> > > to support Dr. McLay with the ensemble_stat
> > >
> > > Dr. McLay does a regrid_data_plane for global lat lon projection
with
> the
> > > G003
> > >
> > > regrid_data_plane PYTHON_NUMPY G003
> > > navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> > > \
> > > -field 'name="./read_NRL_binary.py
> > >
> >
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
> > >
> > > level="'${plev}'";' \
> > >
> > > however, when we next run ensemble_stat with the regrid config
set as
> > > regrid = {
> > > to_grid = G003;
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > we get a "G003" not defined in scope
> > >
> > > ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> > > verifecmwf*2016122000*.nc
> > > DEBUG 1: Default Config File:
> > >
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > > DEBUG 1: User Config File: EnsembleStatConfigGC
> > > ERROR :
> > > ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
> > >
> > > Would you please let me know how to determine what to_grid's are
within
> > > scope,
> > > or where to know what "not defined in scope" means? To me, the
error
> is
> > > indicating G003 has not been registered for the regrid to_grid.
> > >
> > > --
> > > Mr. Glen CARL
> > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > 831.325.6269
> > > glen.carl.ctr at nrlmry.navy.mil
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Mon Apr 15 18:19:38 2019
John,
Thanks, I finally found some time to look at this again. Ok, I was
expecting
separate .stat files for both, now the documentation makes more sense,
and the
separation by line type. I think the ecnt.txt file has the data I
need for
scoring the time series difference.
I believe Justin McLay already uploaded the netcdf files that I have
been
generating the errors. Look for navgem_ens_*nc and verifecmwf_geoph*nc
files.
If I set the output_flag, ssvar=NONE, I get the ERROR :
DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0, 0), (x,
y) = (0,
0). The error caused me to believe the error was for something else,
now I see
it is related to the output_flag. Looks like I have set the SSVAR to
be able
to get the ECNT for now.
I appreciate the help, and we are still learning how to use MET.
I will talk with Dr. McLay soon to see if he still needs help
uploading the
data.
Cheers,
Glen
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, April 15, 2019 11:21 AM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
defined
Glen,
Since you've set all the entries for "output_flag" to STAT, that means
that
all the statistical output will be written to a single .stat output.
I
assume what you're saying is that when you look in the .stat output
file,
you don't find any ECNT output lines. If you'd like to output also
written
to a separate _ecnt.txt file, you can set the config file like this:
*ecnt = BOTH;*
I just tested running ensemble-stat by regridding to G003 with the
config
file using some local test data, and it all worked as expected. So
I'm not
able to replicate the behavior you describe. If you'd like, you could
post
some sample data to our ftp site. I'll go grab it and try to recreate
the
behavior you're seeing. I'd need all the input files you're using to
run
this command:
ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC -grid_obs
verifecmwf*2016122000*.nc
Here are instructions for posting to our ftp site:
https://dtcenter.org/met/users/support/met_help.php#ftp
Thanks
John
On Mon, Apr 15, 2019 at 12:04 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
> 1) I do not think the "G003" is working, and I would have someone
debug
> why it
> is generating the two_to_one error.
>
> 2) We really want to generate a statistic file for " ecnt = STAT
", and
> that
> is not generating nor is it giving messages why not. We get the
ssvar stat
> file from the config, and are not sure why the on stat file is not
> generating
> for ecnt.
>
> Thanks,
> Glen
>
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 15, 2019 10:42 AM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Glen,
>
> I read through your email but am not sure what remaining questions
you
> have.
>
> Should we debug the source of the "two_to_one" error? Or are you
wondering
> why you're only getting an "ensemble_stat...*.stat" file?
>
> John
>
> On Mon, Apr 15, 2019 at 11:05 AM Carl, Mr. Glen, Contractor, Code
7532 via
> RT <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> >
> > Looking up find_grid_by_name.h, I changed the latlon input to
match, and
> > now I
> > am not getting the DataPlane error.
> >
> > from find_grid_by_name.h
> > static const LatLonData ncep_latlon_grids [] = {
> > { "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
> >
> > my new config
> > regrid = {
> > to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > I was using the decimal placement from my netcdf files before.
> > However, now the error disappeared.
> >
> >
> > we are only able to generate on statistic file
> >
> > // Statistical output types
> > //
> > output_flag = {
> > ecnt = STAT;
> > rhist = STAT;
> > phist = STAT;
> > orank = STAT;
> > ssvar = STAT;
> > relp = STAT;
> > }
> >
> > ============= OUTPUT ==================
> >
> > ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> > verifecmwf*2016122000*.nc
> > DEBUG 1: Default Config File:
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > DEBUG 1: User Config File: EnsembleStatConfigGC
> > GSL_RNG_TYPE=mt19937
> > GSL_RNG_SEED=699970652
> > DEBUG 1: Ensemble Files[20]:
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
> > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
> > DEBUG 1: Gridded Observation Files[1]:
> > DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
> > DEBUG 2: Processing masking regions.
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 2: Processing ensemble mean file:
> > ./ensemble_stat_20161220_000000V_ens.nc
> > DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*)
versus
> > geopht_pre_0500.0(*,*), for observation type ECANL, over region
FULL, for
> > interpolation method NEAREST(1), using 65160 pairs.
> > WARNING:
> > WARNING: PairDataEnsemble::compute_ssvar() -> writing at least
1000 SSVAR
> > output lines. Increase the ssvar_bin_size config file setting for
this
> > variable to reduce the number of variance bins.
> > WARNING:
> > DEBUG 2:
> > DEBUG
> > 2:
> >
>
--------------------------------------------------------------------------------
> > DEBUG 2:
> > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
> > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
> > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
> >
> >
> > -----Original Message-----
> > From: Carl, Mr. Glen, Contractor, Code 7532
> > Sent: Monday, April 15, 2019 9:49 AM
> > To: 'met_help at ucar.edu'
> > Cc: McLay, Dr. Justin
> > Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > defined
> >
> > Thanks for the confirmation of the double quote. I tried it
before, and
> was
> > getting the dataplane error. I still get a range check error,
however, I
> am
> > confident it is reading the grid G003. We still do not understand
why we
> > are
> > triggering the two_to_one error. Both with "G003" and with a
> specification
> > fo
> > the Nx, Ny with the latlon input.
> > Thanks again,
> > Glen
> >
> > regrid = {
> > to_grid = "G003";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> > ERROR :
> > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0, 0),
> > (x,
> > y) = (0, 0)
> >
> > I also set the latlon for what our G003 would set at and also get
the
> > DataPlane error.
> >
> > regrid = {
> > to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0, 0),
> > (x,
> > y) = (0, 0)
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, April 15, 2019 9:33 AM
> > To: Carl, Mr. Glen, Contractor, Code 7532
> > Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > defined
> >
> > Mr. Glen Carl,
> >
> > I see you have a question about what pre-defined grids are
supported in
> > MET. Currently, those grids are hard-coded in this source code
file:
> > met-8.0/src/libcode/vx_grid/find_grid_by_name.h
> >
> > In the long run, it'd be better to read these from a static ascii
file at
> > runtime to enable the users to add to or modify the list. But for
now,
> > that's where you'll find them.
> >
> > I see you have a specific question about grid number 3. I think
this
> > really is just a configuration issue that's easily fixed. You
need to
> > request a named grid as a string... meaning you need to put
double-quotes
> > around "G003". Please try this out:
> >
> > regrid = {
> > to_grid = "G003";
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> > Hopefully that fixes it.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor, Code
7532
> via
> > RT <met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > Queue: met_help
> > > Subject: ensemble_stat regrid G003 not defined
> > > Owner: Nobody
> > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709
> >
> > >
> > >
> > > I am working on the Unified Verification project at NRL
Monterey, and
> > > trying
> > > to support Dr. McLay with the ensemble_stat
> > >
> > > Dr. McLay does a regrid_data_plane for global lat lon projection
with
> the
> > > G003
> > >
> > > regrid_data_plane PYTHON_NUMPY G003
> > > navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> > > \
> > > -field 'name="./read_NRL_binary.py
> > >
> >
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
> > >
> > > level="'${plev}'";' \
> > >
> > > however, when we next run ensemble_stat with the regrid config
set as
> > > regrid = {
> > > to_grid = G003;
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > we get a "G003" not defined in scope
> > >
> > > ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> > > verifecmwf*2016122000*.nc
> > > DEBUG 1: Default Config File:
> > >
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > > DEBUG 1: User Config File: EnsembleStatConfigGC
> > > ERROR :
> > > ERROR : do_assign_id() -> identifier "G003" not defined in this
scope!
> > >
> > > Would you please let me know how to determine what to_grid's are
within
> > > scope,
> > > or where to know what "not defined in scope" means? To me, the
error
> is
> > > indicating G003 has not been registered for the regrid to_grid.
> > >
> > > --
> > > Mr. Glen CARL
> > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > 831.325.6269
> > > glen.carl.ctr at nrlmry.navy.mil
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: John Halley Gotway
Time: Thu Apr 25 15:01:09 2019
Glen,
I'm wondering if this issue has been resolved. I talked to David
Fillmore
who has been emailing Justin McLay about this error message.
We did find a small oversight in the logic of the Ensemble-Stat tool
that
was causing this runtime problem. The workaround is to configured
Ensemble-Stat to dump both ECNT and SSVAR output statistics:
*output_flag = { ecnt = BOTH; rhist = NONE; phist = NONE;
orank =
NONE; ssvar = BOTH; relp = NONE;}*
But we have found/fixed this problem for the upcoming met-8.1. It's
really
just a one-line change. We need to add logic that so that if the user
requests ECNT output, then we process the ensemble mean field. The
logic
already does this when SSVAR or RHIST is selected, but we just need to
add
one more option to that conditional.
Please let me know if you're all set or if this is still an issue.
Thanks,
John
On Mon, Apr 15, 2019 at 6:20 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
> John,
> Thanks, I finally found some time to look at this again. Ok, I was
> expecting
> separate .stat files for both, now the documentation makes more
sense, and
> the
> separation by line type. I think the ecnt.txt file has the data I
need
> for
> scoring the time series difference.
>
> I believe Justin McLay already uploaded the netcdf files that I have
been
> generating the errors. Look for navgem_ens_*nc and
verifecmwf_geoph*nc
> files.
> If I set the output_flag, ssvar=NONE, I get the ERROR :
> DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0, 0), (x,
y) =
> (0,
> 0). The error caused me to believe the error was for something else,
now I
> see
> it is related to the output_flag. Looks like I have set the SSVAR
to be
> able
> to get the ECNT for now.
>
> I appreciate the help, and we are still learning how to use MET.
>
> I will talk with Dr. McLay soon to see if he still needs help
uploading
> the
> data.
>
> Cheers,
> Glen
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 15, 2019 11:21 AM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Glen,
>
> Since you've set all the entries for "output_flag" to STAT, that
means that
> all the statistical output will be written to a single .stat output.
I
> assume what you're saying is that when you look in the .stat output
file,
> you don't find any ECNT output lines. If you'd like to output also
written
> to a separate _ecnt.txt file, you can set the config file like this:
> *ecnt = BOTH;*
>
> I just tested running ensemble-stat by regridding to G003 with the
config
> file using some local test data, and it all worked as expected. So
I'm not
> able to replicate the behavior you describe. If you'd like, you
could post
> some sample data to our ftp site. I'll go grab it and try to
recreate the
> behavior you're seeing. I'd need all the input files you're using
to run
> this command:
>
> ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
>
> Here are instructions for posting to our ftp site:
> https://dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks
> John
>
>
> On Mon, Apr 15, 2019 at 12:04 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> >
> > 1) I do not think the "G003" is working, and I would have someone
debug
> > why it
> > is generating the two_to_one error.
> >
> > 2) We really want to generate a statistic file for " ecnt = STAT
", and
> > that
> > is not generating nor is it giving messages why not. We get the
ssvar
> stat
> > file from the config, and are not sure why the on stat file is not
> > generating
> > for ecnt.
> >
> > Thanks,
> > Glen
> >
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, April 15, 2019 10:42 AM
> > To: Carl, Mr. Glen, Contractor, Code 7532
> > Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > defined
> >
> > Glen,
> >
> > I read through your email but am not sure what remaining questions
you
> > have.
> >
> > Should we debug the source of the "two_to_one" error? Or are you
> wondering
> > why you're only getting an "ensemble_stat...*.stat" file?
> >
> > John
> >
> > On Mon, Apr 15, 2019 at 11:05 AM Carl, Mr. Glen, Contractor, Code
7532
> via
> > RT <met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> > >
> > > Looking up find_grid_by_name.h, I changed the latlon input to
match,
> and
> > > now I
> > > am not getting the DataPlane error.
> > >
> > > from find_grid_by_name.h
> > > static const LatLonData ncep_latlon_grids [] = {
> > > { "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
> > >
> > > my new config
> > > regrid = {
> > > to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > I was using the decimal placement from my netcdf files before.
> > > However, now the error disappeared.
> > >
> > >
> > > we are only able to generate on statistic file
> > >
> > > // Statistical output types
> > > //
> > > output_flag = {
> > > ecnt = STAT;
> > > rhist = STAT;
> > > phist = STAT;
> > > orank = STAT;
> > > ssvar = STAT;
> > > relp = STAT;
> > > }
> > >
> > > ============= OUTPUT ==================
> > >
> > > ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
> -grid_obs
> > > verifecmwf*2016122000*.nc
> > > DEBUG 1: Default Config File:
> > >
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > > DEBUG 1: User Config File: EnsembleStatConfigGC
> > > GSL_RNG_TYPE=mt19937
> > > GSL_RNG_SEED=699970652
> > > DEBUG 1: Ensemble Files[20]:
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
> > > DEBUG 1: Gridded Observation Files[1]:
> > > DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
> > > DEBUG 2: Processing masking regions.
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2: Processing ensemble mean file:
> > > ./ensemble_stat_20161220_000000V_ens.nc
> > > DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*)
versus
> > > geopht_pre_0500.0(*,*), for observation type ECANL, over region
FULL,
> for
> > > interpolation method NEAREST(1), using 65160 pairs.
> > > WARNING:
> > > WARNING: PairDataEnsemble::compute_ssvar() -> writing at least
1000
> SSVAR
> > > output lines. Increase the ssvar_bin_size config file setting
for this
> > > variable to reduce the number of variance bins.
> > > WARNING:
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
> > > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
> > > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
> > >
> > >
> > > -----Original Message-----
> > > From: Carl, Mr. Glen, Contractor, Code 7532
> > > Sent: Monday, April 15, 2019 9:49 AM
> > > To: 'met_help at ucar.edu'
> > > Cc: McLay, Dr. Justin
> > > Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > > defined
> > >
> > > Thanks for the confirmation of the double quote. I tried it
before, and
> > was
> > > getting the dataplane error. I still get a range check error,
however,
> I
> > am
> > > confident it is reading the grid G003. We still do not
understand why
> we
> > > are
> > > triggering the two_to_one error. Both with "G003" and with a
> > specification
> > > fo
> > > the Nx, Ny with the latlon input.
> > > Thanks again,
> > > Glen
> > >
> > > regrid = {
> > > to_grid = "G003";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > > ERROR :
> > > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny)
= (0,
> 0),
> > > (x,
> > > y) = (0, 0)
> > >
> > > I also set the latlon for what our G003 would set at and also
get the
> > > DataPlane error.
> > >
> > > regrid = {
> > > to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0,
> 0),
> > > (x,
> > > y) = (0, 0)
> > >
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, April 15, 2019 9:33 AM
> > > To: Carl, Mr. Glen, Contractor, Code 7532
> > > Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > > defined
> > >
> > > Mr. Glen Carl,
> > >
> > > I see you have a question about what pre-defined grids are
supported in
> > > MET. Currently, those grids are hard-coded in this source code
file:
> > > met-8.0/src/libcode/vx_grid/find_grid_by_name.h
> > >
> > > In the long run, it'd be better to read these from a static
ascii file
> at
> > > runtime to enable the users to add to or modify the list. But
for now,
> > > that's where you'll find them.
> > >
> > > I see you have a specific question about grid number 3. I think
this
> > > really is just a configuration issue that's easily fixed. You
need to
> > > request a named grid as a string... meaning you need to put
> double-quotes
> > > around "G003". Please try this out:
> > >
> > > regrid = {
> > > to_grid = "G003";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > Hopefully that fixes it.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor,
Code 7532
> > via
> > > RT <met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> > > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > > Queue: met_help
> > > > Subject: ensemble_stat regrid G003 not defined
> > > > Owner: Nobody
> > > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709
> > >
> > > >
> > > >
> > > > I am working on the Unified Verification project at NRL
Monterey, and
> > > > trying
> > > > to support Dr. McLay with the ensemble_stat
> > > >
> > > > Dr. McLay does a regrid_data_plane for global lat lon
projection with
> > the
> > > > G003
> > > >
> > > > regrid_data_plane PYTHON_NUMPY G003
> > > > navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> > > > \
> > > > -field 'name="./read_NRL_binary.py
> > > >
> > >
> >
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
> > > >
> > > > level="'${plev}'";' \
> > > >
> > > > however, when we next run ensemble_stat with the regrid config
set as
> > > > regrid = {
> > > > to_grid = G003;
> > > > method = NEAREST;
> > > > width = 1;
> > > > vld_thresh = 0.5;
> > > > shape = SQUARE;
> > > > }
> > > >
> > > > we get a "G003" not defined in scope
> > > >
> > > > ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
> -grid_obs
> > > > verifecmwf*2016122000*.nc
> > > > DEBUG 1: Default Config File:
> > > >
> > >
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > > > DEBUG 1: User Config File: EnsembleStatConfigGC
> > > > ERROR :
> > > > ERROR : do_assign_id() -> identifier "G003" not defined in
this
> scope!
> > > >
> > > > Would you please let me know how to determine what to_grid's
are
> within
> > > > scope,
> > > > or where to know what "not defined in scope" means? To me,
the error
> > is
> > > > indicating G003 has not been registered for the regrid
to_grid.
> > > >
> > > > --
> > > > Mr. Glen CARL
> > > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > > 831.325.6269
> > > > glen.carl.ctr at nrlmry.navy.mil
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: ensemble_stat regrid G003 not defined
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Fri Apr 26 10:16:27 2019
Thanks for the follow up. We are now using both ecnt and ssvar, and we
may not
have detected the issue if we had started with ssvar. Yes, the work
around
works for us, and we actually need both ecnt and ssvar.
Our current goal with our ensemble data is to get the anomaly
correlation. It
was suggested I could get the Anomaly Correlation from the Grid-Stat,
however,
I am only seeing it made available by the Point-Stat in table-7.7 of
MET 8 UM.
Thanks,
Glen
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, April 25, 2019 2:01 PM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
defined
Glen,
I'm wondering if this issue has been resolved. I talked to David
Fillmore
who has been emailing Justin McLay about this error message.
We did find a small oversight in the logic of the Ensemble-Stat tool
that
was causing this runtime problem. The workaround is to configured
Ensemble-Stat to dump both ECNT and SSVAR output statistics:
*output_flag = { ecnt = BOTH; rhist = NONE; phist = NONE;
orank =
NONE; ssvar = BOTH; relp = NONE;}*
But we have found/fixed this problem for the upcoming met-8.1. It's
really
just a one-line change. We need to add logic that so that if the user
requests ECNT output, then we process the ensemble mean field. The
logic
already does this when SSVAR or RHIST is selected, but we just need to
add
one more option to that conditional.
Please let me know if you're all set or if this is still an issue.
Thanks,
John
On Mon, Apr 15, 2019 at 6:20 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
>
> John,
> Thanks, I finally found some time to look at this again. Ok, I was
> expecting
> separate .stat files for both, now the documentation makes more
sense, and
> the
> separation by line type. I think the ecnt.txt file has the data I
need
> for
> scoring the time series difference.
>
> I believe Justin McLay already uploaded the netcdf files that I have
been
> generating the errors. Look for navgem_ens_*nc and
verifecmwf_geoph*nc
> files.
> If I set the output_flag, ssvar=NONE, I get the ERROR :
> DataPlane::two_to_one() -> range check error: (Nx, Ny) = (0, 0), (x,
y) =
> (0,
> 0). The error caused me to believe the error was for something else,
now I
> see
> it is related to the output_flag. Looks like I have set the SSVAR
to be
> able
> to get the ECNT for now.
>
> I appreciate the help, and we are still learning how to use MET.
>
> I will talk with Dr. McLay soon to see if he still needs help
uploading
> the
> data.
>
> Cheers,
> Glen
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 15, 2019 11:21 AM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003 not
> defined
>
> Glen,
>
> Since you've set all the entries for "output_flag" to STAT, that
means that
> all the statistical output will be written to a single .stat output.
I
> assume what you're saying is that when you look in the .stat output
file,
> you don't find any ECNT output lines. If you'd like to output also
written
> to a separate _ecnt.txt file, you can set the config file like this:
> *ecnt = BOTH;*
>
> I just tested running ensemble-stat by regridding to G003 with the
config
> file using some local test data, and it all worked as expected. So
I'm not
> able to replicate the behavior you describe. If you'd like, you
could post
> some sample data to our ftp site. I'll go grab it and try to
recreate the
> behavior you're seeing. I'd need all the input files you're using
to run
> this command:
>
> ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
-grid_obs
> verifecmwf*2016122000*.nc
>
> Here are instructions for posting to our ftp site:
> https://dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks
> John
>
>
> On Mon, Apr 15, 2019 at 12:04 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT <met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> >
> > 1) I do not think the "G003" is working, and I would have someone
debug
> > why it
> > is generating the two_to_one error.
> >
> > 2) We really want to generate a statistic file for " ecnt = STAT
", and
> > that
> > is not generating nor is it giving messages why not. We get the
ssvar
> stat
> > file from the config, and are not sure why the on stat file is not
> > generating
> > for ecnt.
> >
> > Thanks,
> > Glen
> >
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, April 15, 2019 10:42 AM
> > To: Carl, Mr. Glen, Contractor, Code 7532
> > Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > defined
> >
> > Glen,
> >
> > I read through your email but am not sure what remaining questions
you
> > have.
> >
> > Should we debug the source of the "two_to_one" error? Or are you
> wondering
> > why you're only getting an "ensemble_stat...*.stat" file?
> >
> > John
> >
> > On Mon, Apr 15, 2019 at 11:05 AM Carl, Mr. Glen, Contractor, Code
7532
> via
> > RT <met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709 >
> > >
> > > Looking up find_grid_by_name.h, I changed the latlon input to
match,
> and
> > > now I
> > > am not getting the DataPlane error.
> > >
> > > from find_grid_by_name.h
> > > static const LatLonData ncep_latlon_grids [] = {
> > > { "G003", -90.0, -0.0, 1, 1.0, 181, 360 },
> > >
> > > my new config
> > > regrid = {
> > > to_grid = "latlon 360 181 -90.0 -0.0 1 1.000";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > I was using the decimal placement from my netcdf files before.
> > > However, now the error disappeared.
> > >
> > >
> > > we are only able to generate on statistic file
> > >
> > > // Statistical output types
> > > //
> > > output_flag = {
> > > ecnt = STAT;
> > > rhist = STAT;
> > > phist = STAT;
> > > orank = STAT;
> > > ssvar = STAT;
> > > relp = STAT;
> > > }
> > >
> > > ============= OUTPUT ==================
> > >
> > > ensemble_stat 20 navgem_ens*2016121500*.nc EnsembleStatConfigGC
> -grid_obs
> > > verifecmwf*2016122000*.nc
> > > DEBUG 1: Default Config File:
> > >
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > > DEBUG 1: User Config File: EnsembleStatConfigGC
> > > GSL_RNG_TYPE=mt19937
> > > GSL_RNG_SEED=699970652
> > > DEBUG 1: Ensemble Files[20]:
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_001.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_002.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_003.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_004.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_005.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_006.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_007.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_008.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_009.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_010.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_011.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_012.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_013.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_014.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_015.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_016.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_017.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_018.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_019.nc
> > > DEBUG 1: navgem_ens_geopht_pre_0500_2016121500_120_020.nc
> > > DEBUG 1: Gridded Observation Files[1]:
> > > DEBUG 1: verifecmwf_geopht_pre_0500_2016122000.nc
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2: Processing ensemble field: geopht_pre_0500.0(*,*)
> > > DEBUG 2: Processing masking regions.
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 2: Processing ensemble mean file:
> > > ./ensemble_stat_20161220_000000V_ens.nc
> > > DEBUG 2: Processing gridded verification geopht_pre_0500.0(*,*)
versus
> > > geopht_pre_0500.0(*,*), for observation type ECANL, over region
FULL,
> for
> > > interpolation method NEAREST(1), using 65160 pairs.
> > > WARNING:
> > > WARNING: PairDataEnsemble::compute_ssvar() -> writing at least
1000
> SSVAR
> > > output lines. Increase the ssvar_bin_size config file setting
for this
> > > variable to reduce the number of variance bins.
> > > WARNING:
> > > DEBUG 2:
> > > DEBUG
> > > 2:
> > >
> >
>
--------------------------------------------------------------------------------
> > > DEBUG 2:
> > > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V.stat
> > > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_ens.nc
> > > DEBUG 1: Output file: ./ensemble_stat_20161220_000000V_orank.nc
> > >
> > >
> > > -----Original Message-----
> > > From: Carl, Mr. Glen, Contractor, Code 7532
> > > Sent: Monday, April 15, 2019 9:49 AM
> > > To: 'met_help at ucar.edu'
> > > Cc: McLay, Dr. Justin
> > > Subject: RE: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > > defined
> > >
> > > Thanks for the confirmation of the double quote. I tried it
before, and
> > was
> > > getting the dataplane error. I still get a range check error,
however,
> I
> > am
> > > confident it is reading the grid G003. We still do not
understand why
> we
> > > are
> > > triggering the two_to_one error. Both with "G003" and with a
> > specification
> > > fo
> > > the Nx, Ny with the latlon input.
> > > Thanks again,
> > > Glen
> > >
> > > regrid = {
> > > to_grid = "G003";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > > ERROR :
> > > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny)
= (0,
> 0),
> > > (x,
> > > y) = (0, 0)
> > >
> > > I also set the latlon for what our G003 would set at and also
get the
> > > DataPlane error.
> > >
> > > regrid = {
> > > to_grid = "latlon 360 181 -90.000 -0.000 1.000 1.000";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > ERROR : DataPlane::two_to_one() -> range check error: (Nx, Ny) =
(0,
> 0),
> > > (x,
> > > y) = (0, 0)
> > >
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, April 15, 2019 9:33 AM
> > > To: Carl, Mr. Glen, Contractor, Code 7532
> > > Subject: Re: [rt.rap.ucar.edu #89709] ensemble_stat regrid G003
not
> > > defined
> > >
> > > Mr. Glen Carl,
> > >
> > > I see you have a question about what pre-defined grids are
supported in
> > > MET. Currently, those grids are hard-coded in this source code
file:
> > > met-8.0/src/libcode/vx_grid/find_grid_by_name.h
> > >
> > > In the long run, it'd be better to read these from a static
ascii file
> at
> > > runtime to enable the users to add to or modify the list. But
for now,
> > > that's where you'll find them.
> > >
> > > I see you have a specific question about grid number 3. I think
this
> > > really is just a configuration issue that's easily fixed. You
need to
> > > request a named grid as a string... meaning you need to put
> double-quotes
> > > around "G003". Please try this out:
> > >
> > > regrid = {
> > > to_grid = "G003";
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > > Hopefully that fixes it.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Fri, Apr 12, 2019 at 12:52 PM Carl, Mr. Glen, Contractor,
Code 7532
> > via
> > > RT <met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Apr 12 12:51:43 2019: Request 89709 was acted upon.
> > > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > > Queue: met_help
> > > > Subject: ensemble_stat regrid G003 not defined
> > > > Owner: Nobody
> > > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=89709
> > >
> > > >
> > > >
> > > > I am working on the Unified Verification project at NRL
Monterey, and
> > > > trying
> > > > to support Dr. McLay with the ensemble_stat
> > > >
> > > > Dr. McLay does a regrid_data_plane for global lat lon
projection with
> > the
> > > > G003
> > > >
> > > > regrid_data_plane PYTHON_NUMPY G003
> > > > navgem_ens_${vrb}_${dtg}_${lead}_${mmm}.nc
> > > > \
> > > > -field 'name="./read_NRL_binary.py
> > > >
> > >
> >
>
'${dtg}'/mbr'${mmm}'/outp/'${vrb}'.0_0000.0_glob360x181_'${dtg}'_0'${lead}'0000_fcstfld";
> > > >
> > > > level="'${plev}'";' \
> > > >
> > > > however, when we next run ensemble_stat with the regrid config
set as
> > > > regrid = {
> > > > to_grid = G003;
> > > > method = NEAREST;
> > > > width = 1;
> > > > vld_thresh = 0.5;
> > > > shape = SQUARE;
> > > > }
> > > >
> > > > we get a "G003" not defined in scope
> > > >
> > > > ensemble_stat navgem_ens*2016121500*.nc EnsembleStatConfigGC
> -grid_obs
> > > > verifecmwf*2016122000*.nc
> > > > DEBUG 1: Default Config File:
> > > >
> > >
> >
> /software/depot/met-
8.0_bugfix/share/met/config/EnsembleStatConfig_default
> > > > DEBUG 1: User Config File: EnsembleStatConfigGC
> > > > ERROR :
> > > > ERROR : do_assign_id() -> identifier "G003" not defined in
this
> scope!
> > > >
> > > > Would you please let me know how to determine what to_grid's
are
> within
> > > > scope,
> > > > or where to know what "not defined in scope" means? To me,
the error
> > is
> > > > indicating G003 has not been registered for the regrid
to_grid.
> > > >
> > > > --
> > > > Mr. Glen CARL
> > > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > > 831.325.6269
> > > > glen.carl.ctr at nrlmry.navy.mil
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
More information about the Met_help
mailing list