[Met_help] [rt.rap.ucar.edu #79729] History for MODE error, can't parse level string
John Halley Gotway via RT
met_help at ucar.edu
Wed Mar 22 10:33:07 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi MET-help,
It's me again. This one should be easier, though!
In attempting to run MODE, I encounter:
ERROR : VarInfo::set_level_info_grib() - failed to parse level string
'(*,*)'
I'm assuming, but don't know for sure, that the issue is in my MODEConfig
file, specifically the line "level = ...". (It could also be the preceding
line, as I'm not confident that the field name is correct.)
Is there a way to inspect the wrfout grib file created by the UPP to know
what the name and dimensions of the variable are? I tried wgrib, but can't
make much sense out of the output / have tried every combination of field
name and level dimensions that seems plausible to me.
I'm looking to compare simulated reflectivity at z=1 km AGL (created by
UPP) to a radar file's REF.
Thanks,
Ryan
--
Ryan Connelly
M.S. Student in Atmospheric Sciences, Stony Brook University
B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
University
rconne01 at gmail.com
ryan.connelly at stonybrook.edu
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MODE error, can't parse level string
From: John Halley Gotway
Time: Mon Mar 06 12:27:07 2017
Ryan,
The way you specify level information differs between NetCDF files and
GRIB
files. Please take a look in met-5.2/data/config/README or in the
user's
guide and search for the string "ANNN". That talks about specifying
level
info for a GRIB file. If it's 1 km AGL, then the level should
probably be
set to "Z1"... unless the level value is stored in meters, then it'd
be
"Z1000".
Please give that a shot and let me know if you're still stuck.
Thanks,
John
On Mon, Mar 6, 2017 at 11:49 AM, Ryan Connelly via RT
<met_help at ucar.edu>
wrote:
>
> Mon Mar 06 11:49:40 2017: Request 79729 was acted upon.
> Transaction: Ticket created by rconne01 at gmail.com
> Queue: met_help
> Subject: MODE error, can't parse level string
> Owner: Nobody
> Requestors: rconne01 at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
>
>
> Hi MET-help,
>
> It's me again. This one should be easier, though!
>
> In attempting to run MODE, I encounter:
>
> ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> '(*,*)'
>
>
> I'm assuming, but don't know for sure, that the issue is in my
MODEConfig
> file, specifically the line "level = ...". (It could also be the
preceding
> line, as I'm not confident that the field name is correct.)
>
> Is there a way to inspect the wrfout grib file created by the UPP to
know
> what the name and dimensions of the variable are? I tried wgrib,
but can't
> make much sense out of the output / have tried every combination of
field
> name and level dimensions that seems plausible to me.
>
> I'm looking to compare simulated reflectivity at z=1 km AGL (created
by
> UPP) to a radar file's REF.
>
> Thanks,
> Ryan
>
> --
> Ryan Connelly
> M.S. Student in Atmospheric Sciences, Stony Brook University
> B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> University
> rconne01 at gmail.com
> ryan.connelly at stonybrook.edu
>
>
------------------------------------------------
Subject: MODE error, can't parse level string
From: Ryan Connelly
Time: Mon Mar 06 14:58:54 2017
Hi John,
Thanks for the info on how to specify the level string; that seems to
not
be a problem now.
However, it is now telling me:
ERROR : is_prelim_match() - unrecognized GRIB1 field abbreviation
'REFD'
for table version 2
In my case, the field abbreviation should be REFD, as in both the
table you
linked and as in the output of wgrib, which shows that REFD is
contained
within the wrfout file. For the sake of debugging, I tried numerous
other
variables, even though the output would be nonsensical. All returned
the
same error, except for PRES, which did not (but then errored because
the
level string Z1 does not make any sense for PRES - as expected).
Ryan
On Mon, Mar 6, 2017 at 2:27 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Ryan,
>
> The way you specify level information differs between NetCDF files
and GRIB
> files. Please take a look in met-5.2/data/config/README or in the
user's
> guide and search for the string "ANNN". That talks about specifying
level
> info for a GRIB file. If it's 1 km AGL, then the level should
probably be
> set to "Z1"... unless the level value is stored in meters, then it'd
be
> "Z1000".
>
> Please give that a shot and let me know if you're still stuck.
>
> Thanks,
> John
>
>
> On Mon, Mar 6, 2017 at 11:49 AM, Ryan Connelly via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Mon Mar 06 11:49:40 2017: Request 79729 was acted upon.
> > Transaction: Ticket created by rconne01 at gmail.com
> > Queue: met_help
> > Subject: MODE error, can't parse level string
> > Owner: Nobody
> > Requestors: rconne01 at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
> >
> >
> > Hi MET-help,
> >
> > It's me again. This one should be easier, though!
> >
> > In attempting to run MODE, I encounter:
> >
> > ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> > '(*,*)'
> >
> >
> > I'm assuming, but don't know for sure, that the issue is in my
MODEConfig
> > file, specifically the line "level = ...". (It could also be the
> preceding
> > line, as I'm not confident that the field name is correct.)
> >
> > Is there a way to inspect the wrfout grib file created by the UPP
to know
> > what the name and dimensions of the variable are? I tried wgrib,
but
> can't
> > make much sense out of the output / have tried every combination
of field
> > name and level dimensions that seems plausible to me.
> >
> > I'm looking to compare simulated reflectivity at z=1 km AGL
(created by
> > UPP) to a radar file's REF.
> >
> > Thanks,
> > Ryan
> >
> > --
> > Ryan Connelly
> > M.S. Student in Atmospheric Sciences, Stony Brook University
> > B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> > University
> > rconne01 at gmail.com
> > ryan.connelly at stonybrook.edu
> >
> >
>
>
--
Ryan Connelly
M.S. Student in Atmospheric Sciences, Stony Brook University
B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
University
rconne01 at gmail.com
ryan.connelly at stonybrook.edu
------------------------------------------------
Subject: MODE error, can't parse level string
From: John Halley Gotway
Time: Mon Mar 06 15:31:30 2017
Ryan,
REFD is defined in GRIB1 parameter table version number 129:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
Ideally you should be able to just say:
name="REFD";
level="Z1";
But if that yields that error, then try:
name="REFD";
level="Z1";
GRIB1_ptv = 129;
I can't remember when we fixed that behavior you're seeing... if it
should
be in 5.2 or is only in version 6.0 which is coming out soon.
Thanks,
John
On Mon, Mar 6, 2017 at 2:58 PM, Ryan Connelly via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
>
> Hi John,
>
> Thanks for the info on how to specify the level string; that seems
to not
> be a problem now.
>
> However, it is now telling me:
>
> ERROR : is_prelim_match() - unrecognized GRIB1 field abbreviation
'REFD'
> for table version 2
>
>
> In my case, the field abbreviation should be REFD, as in both the
table you
> linked and as in the output of wgrib, which shows that REFD is
contained
> within the wrfout file. For the sake of debugging, I tried numerous
other
> variables, even though the output would be nonsensical. All
returned the
> same error, except for PRES, which did not (but then errored because
the
> level string Z1 does not make any sense for PRES - as expected).
>
> Ryan
>
> On Mon, Mar 6, 2017 at 2:27 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> > wrote:
>
> > Ryan,
> >
> > The way you specify level information differs between NetCDF files
and
> GRIB
> > files. Please take a look in met-5.2/data/config/README or in the
user's
> > guide and search for the string "ANNN". That talks about
specifying
> level
> > info for a GRIB file. If it's 1 km AGL, then the level should
probably
> be
> > set to "Z1"... unless the level value is stored in meters, then
it'd be
> > "Z1000".
> >
> > Please give that a shot and let me know if you're still stuck.
> >
> > Thanks,
> > John
> >
> >
> > On Mon, Mar 6, 2017 at 11:49 AM, Ryan Connelly via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> > >
> > > Mon Mar 06 11:49:40 2017: Request 79729 was acted upon.
> > > Transaction: Ticket created by rconne01 at gmail.com
> > > Queue: met_help
> > > Subject: MODE error, can't parse level string
> > > Owner: Nobody
> > > Requestors: rconne01 at gmail.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729
> >
> > >
> > >
> > > Hi MET-help,
> > >
> > > It's me again. This one should be easier, though!
> > >
> > > In attempting to run MODE, I encounter:
> > >
> > > ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> > > '(*,*)'
> > >
> > >
> > > I'm assuming, but don't know for sure, that the issue is in my
> MODEConfig
> > > file, specifically the line "level = ...". (It could also be
the
> > preceding
> > > line, as I'm not confident that the field name is correct.)
> > >
> > > Is there a way to inspect the wrfout grib file created by the
UPP to
> know
> > > what the name and dimensions of the variable are? I tried
wgrib, but
> > can't
> > > make much sense out of the output / have tried every combination
of
> field
> > > name and level dimensions that seems plausible to me.
> > >
> > > I'm looking to compare simulated reflectivity at z=1 km AGL
(created by
> > > UPP) to a radar file's REF.
> > >
> > > Thanks,
> > > Ryan
> > >
> > > --
> > > Ryan Connelly
> > > M.S. Student in Atmospheric Sciences, Stony Brook University
> > > B.S. in Meteorology with Minors in Mathematics and GIS,
Valparaiso
> > > University
> > > rconne01 at gmail.com
> > > ryan.connelly at stonybrook.edu
> > >
> > >
> >
> >
>
>
> --
> Ryan Connelly
> M.S. Student in Atmospheric Sciences, Stony Brook University
> B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> University
> rconne01 at gmail.com
> ryan.connelly at stonybrook.edu
>
>
------------------------------------------------
Subject: MODE error, can't parse level string
From: Ryan Connelly
Time: Wed Mar 15 13:34:04 2017
Hi John,
Picking up form last week...
The addition of GRIB1_ptv = 129; got me past that error, so thank you
for
that.
However, now MODE is telling me
ERROR : setup_fcst_obs_data() -> can't get data from file
"/D2/ryan/met-5.2/test.nc"
where test.nc is the result of running regrid_data_plane, which I have
verified successfully regridded observed radar reflectivity data to
the WRF
grid by examining the output .ps file. Since MODE also can do the
regridding itself without needing to run regrid_data_plane, I tried
using
the original, non-regridded radar netcdf file in the call to MODE, and
got
the same error.
Thanks,
Ryan
On Mon, Mar 6, 2017 at 5:31 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Ryan,
>
> REFD is defined in GRIB1 parameter table version number 129:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>
> Ideally you should be able to just say:
> name="REFD";
> level="Z1";
>
> But if that yields that error, then try:
> name="REFD";
> level="Z1";
> GRIB1_ptv = 129;
>
> I can't remember when we fixed that behavior you're seeing... if it
should
> be in 5.2 or is only in version 6.0 which is coming out soon.
>
> Thanks,
> John
>
> On Mon, Mar 6, 2017 at 2:58 PM, Ryan Connelly via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
> >
> > Hi John,
> >
> > Thanks for the info on how to specify the level string; that seems
to not
> > be a problem now.
> >
> > However, it is now telling me:
> >
> > ERROR : is_prelim_match() - unrecognized GRIB1 field abbreviation
'REFD'
> > for table version 2
> >
> >
> > In my case, the field abbreviation should be REFD, as in both the
table
> you
> > linked and as in the output of wgrib, which shows that REFD is
contained
> > within the wrfout file. For the sake of debugging, I tried
numerous
> other
> > variables, even though the output would be nonsensical. All
returned the
> > same error, except for PRES, which did not (but then errored
because the
> > level string Z1 does not make any sense for PRES - as expected).
> >
> > Ryan
> >
> > On Mon, Mar 6, 2017 at 2:27 PM, John Halley Gotway via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > > Ryan,
> > >
> > > The way you specify level information differs between NetCDF
files and
> > GRIB
> > > files. Please take a look in met-5.2/data/config/README or in
the
> user's
> > > guide and search for the string "ANNN". That talks about
specifying
> > level
> > > info for a GRIB file. If it's 1 km AGL, then the level should
probably
> > be
> > > set to "Z1"... unless the level value is stored in meters, then
it'd be
> > > "Z1000".
> > >
> > > Please give that a shot and let me know if you're still stuck.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > > On Mon, Mar 6, 2017 at 11:49 AM, Ryan Connelly via RT <
> met_help at ucar.edu
> > >
> > > wrote:
> > >
> > > >
> > > > Mon Mar 06 11:49:40 2017: Request 79729 was acted upon.
> > > > Transaction: Ticket created by rconne01 at gmail.com
> > > > Queue: met_help
> > > > Subject: MODE error, can't parse level string
> > > > Owner: Nobody
> > > > Requestors: rconne01 at gmail.com
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=79729
> > >
> > > >
> > > >
> > > > Hi MET-help,
> > > >
> > > > It's me again. This one should be easier, though!
> > > >
> > > > In attempting to run MODE, I encounter:
> > > >
> > > > ERROR : VarInfo::set_level_info_grib() - failed to parse
level
> string
> > > > '(*,*)'
> > > >
> > > >
> > > > I'm assuming, but don't know for sure, that the issue is in my
> > MODEConfig
> > > > file, specifically the line "level = ...". (It could also be
the
> > > preceding
> > > > line, as I'm not confident that the field name is correct.)
> > > >
> > > > Is there a way to inspect the wrfout grib file created by the
UPP to
> > know
> > > > what the name and dimensions of the variable are? I tried
wgrib, but
> > > can't
> > > > make much sense out of the output / have tried every
combination of
> > field
> > > > name and level dimensions that seems plausible to me.
> > > >
> > > > I'm looking to compare simulated reflectivity at z=1 km AGL
(created
> by
> > > > UPP) to a radar file's REF.
> > > >
> > > > Thanks,
> > > > Ryan
> > > >
> > > > --
> > > > Ryan Connelly
> > > > M.S. Student in Atmospheric Sciences, Stony Brook University
> > > > B.S. in Meteorology with Minors in Mathematics and GIS,
Valparaiso
> > > > University
> > > > rconne01 at gmail.com
> > > > ryan.connelly at stonybrook.edu
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Ryan Connelly
> > M.S. Student in Atmospheric Sciences, Stony Brook University
> > B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> > University
> > rconne01 at gmail.com
> > ryan.connelly at stonybrook.edu
> >
> >
>
>
--
Ryan Connelly
M.S. Student in Atmospheric Sciences, Stony Brook University
B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
University
rconne01 at gmail.com
ryan.connelly at stonybrook.edu
------------------------------------------------
Subject: MODE error, can't parse level string
From: John Halley Gotway
Time: Wed Mar 15 14:17:41 2017
Ryan,
My first guess is that we need to edit the configuration file you're
passing to MODE.
Please try this...
ncdump -h test.nc
Look at the name of the NetCDF variable that contains your data.
Let's
just call it "VARNAME". Since you're passing to MODE a GRIB forecast
file
and a NetCDF observation file, you need to set up the config file
accordingly.
By default, the MODE config file has "obs = fcst;". If you want to
use the
same convolution radius and threshold, you could keep that line to
copy
those settings from the "fcst" dictionary to the "obs" dictionary.
But
then you need to update the observation "name" and "level"... like
this:
obs = fcst;
obs = {
field = { name = "VARNAME"; level="(*,*)"; }
}
But replace VARNAME with the actual name of your NetCDF variable.
If that doesn't fix it, please post your sample data (data files and
config
files) to out anonymous ftp site following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On Wed, Mar 15, 2017 at 1:34 PM, Ryan Connelly via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
>
> Hi John,
>
> Picking up form last week...
>
> The addition of GRIB1_ptv = 129; got me past that error, so thank
you for
> that.
>
> However, now MODE is telling me
>
> ERROR : setup_fcst_obs_data() -> can't get data from file
> "/D2/ryan/met-5.2/test.nc"
>
>
> where test.nc is the result of running regrid_data_plane, which I
have
> verified successfully regridded observed radar reflectivity data to
the WRF
> grid by examining the output .ps file. Since MODE also can do the
> regridding itself without needing to run regrid_data_plane, I tried
using
> the original, non-regridded radar netcdf file in the call to MODE,
and got
> the same error.
>
> Thanks,
> Ryan
>
> On Mon, Mar 6, 2017 at 5:31 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> > wrote:
>
> > Ryan,
> >
> > REFD is defined in GRIB1 parameter table version number 129:
> > http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
> >
> > Ideally you should be able to just say:
> > name="REFD";
> > level="Z1";
> >
> > But if that yields that error, then try:
> > name="REFD";
> > level="Z1";
> > GRIB1_ptv = 129;
> >
> > I can't remember when we fixed that behavior you're seeing... if
it
> should
> > be in 5.2 or is only in version 6.0 which is coming out soon.
> >
> > Thanks,
> > John
> >
> > On Mon, Mar 6, 2017 at 2:58 PM, Ryan Connelly via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
> > >
> > > Hi John,
> > >
> > > Thanks for the info on how to specify the level string; that
seems to
> not
> > > be a problem now.
> > >
> > > However, it is now telling me:
> > >
> > > ERROR : is_prelim_match() - unrecognized GRIB1 field
abbreviation
> 'REFD'
> > > for table version 2
> > >
> > >
> > > In my case, the field abbreviation should be REFD, as in both
the table
> > you
> > > linked and as in the output of wgrib, which shows that REFD is
> contained
> > > within the wrfout file. For the sake of debugging, I tried
numerous
> > other
> > > variables, even though the output would be nonsensical. All
returned
> the
> > > same error, except for PRES, which did not (but then errored
because
> the
> > > level string Z1 does not make any sense for PRES - as expected).
> > >
> > > Ryan
> > >
> > > On Mon, Mar 6, 2017 at 2:27 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu
> > > > wrote:
> > >
> > > > Ryan,
> > > >
> > > > The way you specify level information differs between NetCDF
files
> and
> > > GRIB
> > > > files. Please take a look in met-5.2/data/config/README or in
the
> > user's
> > > > guide and search for the string "ANNN". That talks about
specifying
> > > level
> > > > info for a GRIB file. If it's 1 km AGL, then the level should
> probably
> > > be
> > > > set to "Z1"... unless the level value is stored in meters,
then it'd
> be
> > > > "Z1000".
> > > >
> > > > Please give that a shot and let me know if you're still stuck.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > > On Mon, Mar 6, 2017 at 11:49 AM, Ryan Connelly via RT <
> > met_help at ucar.edu
> > > >
> > > > wrote:
> > > >
> > > > >
> > > > > Mon Mar 06 11:49:40 2017: Request 79729 was acted upon.
> > > > > Transaction: Ticket created by rconne01 at gmail.com
> > > > > Queue: met_help
> > > > > Subject: MODE error, can't parse level string
> > > > > Owner: Nobody
> > > > > Requestors: rconne01 at gmail.com
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=79729
> > > >
> > > > >
> > > > >
> > > > > Hi MET-help,
> > > > >
> > > > > It's me again. This one should be easier, though!
> > > > >
> > > > > In attempting to run MODE, I encounter:
> > > > >
> > > > > ERROR : VarInfo::set_level_info_grib() - failed to parse
level
> > string
> > > > > '(*,*)'
> > > > >
> > > > >
> > > > > I'm assuming, but don't know for sure, that the issue is in
my
> > > MODEConfig
> > > > > file, specifically the line "level = ...". (It could also
be the
> > > > preceding
> > > > > line, as I'm not confident that the field name is correct.)
> > > > >
> > > > > Is there a way to inspect the wrfout grib file created by
the UPP
> to
> > > know
> > > > > what the name and dimensions of the variable are? I tried
wgrib,
> but
> > > > can't
> > > > > make much sense out of the output / have tried every
combination of
> > > field
> > > > > name and level dimensions that seems plausible to me.
> > > > >
> > > > > I'm looking to compare simulated reflectivity at z=1 km AGL
> (created
> > by
> > > > > UPP) to a radar file's REF.
> > > > >
> > > > > Thanks,
> > > > > Ryan
> > > > >
> > > > > --
> > > > > Ryan Connelly
> > > > > M.S. Student in Atmospheric Sciences, Stony Brook University
> > > > > B.S. in Meteorology with Minors in Mathematics and GIS,
Valparaiso
> > > > > University
> > > > > rconne01 at gmail.com
> > > > > ryan.connelly at stonybrook.edu
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Ryan Connelly
> > > M.S. Student in Atmospheric Sciences, Stony Brook University
> > > B.S. in Meteorology with Minors in Mathematics and GIS,
Valparaiso
> > > University
> > > rconne01 at gmail.com
> > > ryan.connelly at stonybrook.edu
> > >
> > >
> >
> >
>
>
> --
> Ryan Connelly
> M.S. Student in Atmospheric Sciences, Stony Brook University
> B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> University
> rconne01 at gmail.com
> ryan.connelly at stonybrook.edu
>
>
------------------------------------------------
Subject: MODE error, can't parse level string
From: Ryan Connelly
Time: Wed Mar 15 22:36:50 2017
Hi John,
Thanks, that makes complete sense and has gotten me past that error!
I
have MODE output that I'll examine tomorrow (later today) in the
office.
Thank you so much!
Ryan
On Wed, Mar 15, 2017 at 4:17 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Ryan,
>
> My first guess is that we need to edit the configuration file you're
> passing to MODE.
>
> Please try this...
> ncdump -h test.nc
>
> Look at the name of the NetCDF variable that contains your data.
Let's
> just call it "VARNAME". Since you're passing to MODE a GRIB
forecast file
> and a NetCDF observation file, you need to set up the config file
> accordingly.
>
> By default, the MODE config file has "obs = fcst;". If you want to
use the
> same convolution radius and threshold, you could keep that line to
copy
> those settings from the "fcst" dictionary to the "obs" dictionary.
But
> then you need to update the observation "name" and "level"... like
this:
>
> obs = fcst;
> obs = {
> field = { name = "VARNAME"; level="(*,*)"; }
> }
>
> But replace VARNAME with the actual name of your NetCDF variable.
>
> If that doesn't fix it, please post your sample data (data files and
config
> files) to out anonymous ftp site following these instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
>
>
> On Wed, Mar 15, 2017 at 1:34 PM, Ryan Connelly via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729 >
> >
> > Hi John,
> >
> > Picking up form last week...
> >
> > The addition of GRIB1_ptv = 129; got me past that error, so thank
you for
> > that.
> >
> > However, now MODE is telling me
> >
> > ERROR : setup_fcst_obs_data() -> can't get data from file
> > "/D2/ryan/met-5.2/test.nc"
> >
> >
> > where test.nc is the result of running regrid_data_plane, which I
have
> > verified successfully regridded observed radar reflectivity data
to the
> WRF
> > grid by examining the output .ps file. Since MODE also can do the
> > regridding itself without needing to run regrid_data_plane, I
tried using
> > the original, non-regridded radar netcdf file in the call to MODE,
and
> got
> > the same error.
> >
> > Thanks,
> > Ryan
> >
> > On Mon, Mar 6, 2017 at 5:31 PM, John Halley Gotway via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > > Ryan,
> > >
> > > REFD is defined in GRIB1 parameter table version number 129:
> > > http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
> > >
> > > Ideally you should be able to just say:
> > > name="REFD";
> > > level="Z1";
> > >
> > > But if that yields that error, then try:
> > > name="REFD";
> > > level="Z1";
> > > GRIB1_ptv = 129;
> > >
> > > I can't remember when we fixed that behavior you're seeing... if
it
> > should
> > > be in 5.2 or is only in version 6.0 which is coming out soon.
> > >
> > > Thanks,
> > > John
> > >
> > > On Mon, Mar 6, 2017 at 2:58 PM, Ryan Connelly via RT <
> met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79729
>
> > > >
> > > > Hi John,
> > > >
> > > > Thanks for the info on how to specify the level string; that
seems to
> > not
> > > > be a problem now.
> > > >
> > > > However, it is now telling me:
> > > >
> > > > ERROR : is_prelim_match() - unrecognized GRIB1 field
abbreviation
> > 'REFD'
> > > > for table version 2
> > > >
> > > >
> > > > In my case, the field abbreviation should be REFD, as in both
the
> table
> > > you
> > > > linked and as in the output of wgrib, which shows that REFD is
> > contained
> > > > within the wrfout file. For the sake of debugging, I tried
numerous
> > > other
> > > > variables, even though the output would be nonsensical. All
returned
> > the
> > > > same error, except for PRES, which did not (but then errored
because
> > the
> > > > level string Z1 does not make any sense for PRES - as
expected).
> > > >
> > > > Ryan
> > > >
> > > > On Mon, Mar 6, 2017 at 2:27 PM, John Halley Gotway via RT <
> > > > met_help at ucar.edu
> > > > > wrote:
> > > >
> > > > > Ryan,
> > > > >
> > > > > The way you specify level information differs between NetCDF
files
> > and
> > > > GRIB
> > > > > files. Please take a look in met-5.2/data/config/README or
in the
> > > user's
> > > > > guide and search for the string "ANNN". That talks about
> specifying
> > > > level
> > > > > info for a GRIB file. If it's 1 km AGL, then the level
should
> > probably
> > > > be
> > > > > set to "Z1"... unless the level value is stored in meters,
then
> it'd
> > be
> > > > > "Z1000".
> > > > >
> > > > > Please give that a shot and let me know if you're still
stuck.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > >
> > > > > On Mon, Mar 6, 2017 at 11:49 AM, Ryan Connelly via RT <
> > > met_help at ucar.edu
> > > > >
> > > > > wrote:
> > > > >
> > > > > >
> > > > > > Mon Mar 06 11:49:40 2017: Request 79729 was acted upon.
> > > > > > Transaction: Ticket created by rconne01 at gmail.com
> > > > > > Queue: met_help
> > > > > > Subject: MODE error, can't parse level string
> > > > > > Owner: Nobody
> > > > > > Requestors: rconne01 at gmail.com
> > > > > > Status: new
> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=79729
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi MET-help,
> > > > > >
> > > > > > It's me again. This one should be easier, though!
> > > > > >
> > > > > > In attempting to run MODE, I encounter:
> > > > > >
> > > > > > ERROR : VarInfo::set_level_info_grib() - failed to parse
level
> > > string
> > > > > > '(*,*)'
> > > > > >
> > > > > >
> > > > > > I'm assuming, but don't know for sure, that the issue is
in my
> > > > MODEConfig
> > > > > > file, specifically the line "level = ...". (It could also
be the
> > > > > preceding
> > > > > > line, as I'm not confident that the field name is
correct.)
> > > > > >
> > > > > > Is there a way to inspect the wrfout grib file created by
the UPP
> > to
> > > > know
> > > > > > what the name and dimensions of the variable are? I tried
wgrib,
> > but
> > > > > can't
> > > > > > make much sense out of the output / have tried every
combination
> of
> > > > field
> > > > > > name and level dimensions that seems plausible to me.
> > > > > >
> > > > > > I'm looking to compare simulated reflectivity at z=1 km
AGL
> > (created
> > > by
> > > > > > UPP) to a radar file's REF.
> > > > > >
> > > > > > Thanks,
> > > > > > Ryan
> > > > > >
> > > > > > --
> > > > > > Ryan Connelly
> > > > > > M.S. Student in Atmospheric Sciences, Stony Brook
University
> > > > > > B.S. in Meteorology with Minors in Mathematics and GIS,
> Valparaiso
> > > > > > University
> > > > > > rconne01 at gmail.com
> > > > > > ryan.connelly at stonybrook.edu
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Ryan Connelly
> > > > M.S. Student in Atmospheric Sciences, Stony Brook University
> > > > B.S. in Meteorology with Minors in Mathematics and GIS,
Valparaiso
> > > > University
> > > > rconne01 at gmail.com
> > > > ryan.connelly at stonybrook.edu
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Ryan Connelly
> > M.S. Student in Atmospheric Sciences, Stony Brook University
> > B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> > University
> > rconne01 at gmail.com
> > ryan.connelly at stonybrook.edu
> >
> >
>
>
--
Ryan Connelly
M.S. Student in Atmospheric Sciences, Stony Brook University
B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
University
rconne01 at gmail.com
ryan.connelly at stonybrook.edu
------------------------------------------------
More information about the Met_help
mailing list