[Met_help] [rt.rap.ucar.edu #83537] History for question regarding heights at various levels
John Halley Gotway via RT
met_help at ucar.edu
Fri Jan 19 15:39:40 MST 2018
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi, there,
I'm hoping this is a quick and easy question. Several of the items that I
need to verify are heights at certain named levels. For example:
1) The ceiling is indicated in the grib file as HGT but the level
indicator is "ceiling height".
2) The cloud base is also "HGT" but is level indicator in the grib is
"cloud base level".
3) Finally, the PBL is also considered HGT but the level is "planetary
boundary level height".
What should I put as the level indicator for these quantities?
Thanks!
Perry
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: question regarding heights at various levels
From: John Halley Gotway
Time: Wed Jan 10 09:47:05 2018
Hi Perry,
I see you have a question about discriminating between HGT fields for
different level types. As you've already found, the PBL height and
cloud
base height are both encoded using the same GRIB1 or GRIB2
identification
information. However, they do differ by the GRIB level type value.
In the MET config files, you can use the GRIB_lvl_typ to discriminate
between these fields.
Here's the GRIB table which defines these level type values:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
I used a GFS file for example and ran it through wgrib to reveal many
HGT
levels:
248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=24:P2=0:TimeU=1:sfc:24hr
fcst:NAve=0
326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1=24:P2=0:TimeU=1:tropopause:24hr
fcst:NAve=0
333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1=24:P2=0:TimeU=1:max
wind lev:24hr fcst:NAve=0
354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1=24:P2=0:TimeU=1:0C
isotherm:24hr fcst:NAve=0
356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:P1=24:P2=0:TimeU=1:high
trop freezing lvl:24hr fcst:NAve=0
I ran it through plot_data_plane like this:
met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
'name="HGT"; level="L0";'
But I get this warning message telling me that MET found 5 matches:
WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches for VarInfo
"HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using the first
match
found.
So I rerun using GRIB_lvl_typ=7; to select only the tropopause level:
met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
And the output log confirms that it correctly found record number 326,
which matches what wgrib said:
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact match for
VarInfo "HGT/L0" in GRIB record 326 of GRIB file
"GFS_20170615_CY12_FH24.GR1".
Hope that helps get you going! There are several GRIB filtering
options
like this that can be found either in the MET User's Guide or is
met-6.1/data/config/README.
Thanks,
John
On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> Transaction: Ticket created by perry.shafran at noaa.gov
> Queue: met_help
> Subject: question regarding heights at various levels
> Owner: Nobody
> Requestors: perry.shafran at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
>
>
> Hi, there,
>
> I'm hoping this is a quick and easy question. Several of the items
that I
> need to verify are heights at certain named levels. For example:
>
> 1) The ceiling is indicated in the grib file as HGT but the level
> indicator is "ceiling height".
>
> 2) The cloud base is also "HGT" but is level indicator in the grib
is
> "cloud base level".
>
> 3) Finally, the PBL is also considered HGT but the level is
"planetary
> boundary level height".
>
> What should I put as the level indicator for these quantities?
>
> Thanks!
>
> Perry
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: Minna Win
Time: Wed Jan 10 09:53:10 2018
Hi Perry,
It looks like you need to be able to indicate different levels in your
configuration files. In order to do so, you will need to use the
following
syntax:
Example:
{
//tropopause
name = "TMP";
GRIB_lvl_typ = 7;
GRIB_lvl_val1 = 0;
desc = tropo;
},
Where the GRIB_lvl_type=7 in the example above corresponds to the
GRIB2
Code Table 4.5 code figure value for tropopause. Here is the link to
that
document:
http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_table4-5.shtml
<http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_table4-5.shtml>
and set GRIB_lvl_val1 to 0 (a 'default' value used in MET since there
is
only one tropopause level)
If your data is GRIB, you'll need to look at the table:
http://www.wmo.int/pages/prog/www/WDM/Guides/Guide-binary-2.html#GRIB
(scroll towards bottom for TABLE 3. TYPE AND VALUE OF LEVEL)
The desc= is optional and should not contain any whitespace.
So if your data is GRIB2, GRIB2 Code Table 4.5 has cloud base level
code
figure= 2, level of cloud tops code figure= 3, planetary boundary
level
code figure = 220. Use these values for GRIB_lvl_typ and set
GRIB_lvl_val1=0. You should check that I'm pointing you to the correct
levels to use for ceiling height.
Give that a try and let us know if you still have any issues.
Regards,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 302-497-8401
On Wed, Jan 10, 2018 at 2:48 PM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> Transaction: Ticket created by perry.shafran at noaa.gov
> Queue: met_help
> Subject: question regarding heights at various levels
> Owner: Nobody
> Requestors: perry.shafran at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
>
>
> Hi, there,
>
> I'm hoping this is a quick and easy question. Several of the items
that I
> need to verify are heights at certain named levels. For example:
>
> 1) The ceiling is indicated in the grib file as HGT but the level
> indicator is "ceiling height".
>
> 2) The cloud base is also "HGT" but is level indicator in the grib
is
> "cloud base level".
>
> 3) Finally, the PBL is also considered HGT but the level is
"planetary
> boundary level height".
>
> What should I put as the level indicator for these quantities?
>
> Thanks!
>
> Perry
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: perry.shafran at noaa.gov
Time: Wed Jan 10 10:33:19 2018
Hi, John,
The information that both Minna and you provided should help. I will
try
it.
Thanks!
Perry
On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi Perry,
>
> I see you have a question about discriminating between HGT fields
for
> different level types. As you've already found, the PBL height and
cloud
> base height are both encoded using the same GRIB1 or GRIB2
identification
> information. However, they do differ by the GRIB level type value.
>
> In the MET config files, you can use the GRIB_lvl_typ to
discriminate
> between these fields.
>
> Here's the GRIB table which defines these level type values:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
>
> I used a GFS file for example and ran it through wgrib to reveal
many HGT
> levels:
>
> 248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:
> P1=24:P2=0:TimeU=1:sfc:24hr
> fcst:NAve=0
>
> 326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:
> P1=24:P2=0:TimeU=1:tropopause:24hr
> fcst:NAve=0
>
> 333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:
> P1=24:P2=0:TimeU=1:max
> wind lev:24hr fcst:NAve=0
>
> 354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:
> P1=24:P2=0:TimeU=1:0C
> isotherm:24hr fcst:NAve=0
>
> 356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=
> 0:P1=24:P2=0:TimeU=1:high
> trop freezing lvl:24hr fcst:NAve=0
>
>
> I ran it through plot_data_plane like this:
>
>
> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
> 'name="HGT"; level="L0";'
>
>
> But I get this warning message telling me that MET found 5 matches:
>
>
> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches for
VarInfo
> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using the first
match
> found.
>
>
> So I rerun using GRIB_lvl_typ=7; to select only the tropopause
level:
>
>
> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
>
>
> And the output log confirms that it correctly found record number
326,
> which matches what wgrib said:
>
>
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact match
for
> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> "GFS_20170615_CY12_FH24.GR1".
>
>
> Hope that helps get you going! There are several GRIB filtering
options
> like this that can be found either in the MET User's Guide or is
> met-6.1/data/config/README.
>
>
> Thanks,
> John
>
> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> > Transaction: Ticket created by perry.shafran at noaa.gov
> > Queue: met_help
> > Subject: question regarding heights at various levels
> > Owner: Nobody
> > Requestors: perry.shafran at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> >
> >
> > Hi, there,
> >
> > I'm hoping this is a quick and easy question. Several of the
items that
> I
> > need to verify are heights at certain named levels. For example:
> >
> > 1) The ceiling is indicated in the grib file as HGT but the level
> > indicator is "ceiling height".
> >
> > 2) The cloud base is also "HGT" but is level indicator in the
grib is
> > "cloud base level".
> >
> > 3) Finally, the PBL is also considered HGT but the level is
"planetary
> > boundary level height".
> >
> > What should I put as the level indicator for these quantities?
> >
> > Thanks!
> >
> > Perry
> >
> >
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: perry.shafran at noaa.gov
Time: Fri Jan 12 08:52:06 2018
Hi, John,
I need help setting this up.
In PB2NC, I am adding (for example) "CEILING" to the list of desired
items
in the observed value to verify:
obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB", "HOVI",
"TOCC","CEILING" ];
But then I want to give it an equivalent value in the model to verify
with,
which is HGT at ceiling level (which would be GRIB_lvl_typ = 215. So
how
would I put this in the obs_bufr_map section of the PB2NC file?
obs_bufr_map = [
{ key = "HOVI"; val = "VIS"; },
{ key = "TOCC"; val = "TCDC"; }
];
In point_stat, I have set it up like this:
{
name = "HGT";
level = "L0";
GRIB_lvl_typ = 215;
},
Is this correct?
Thanks!
Perry
On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA Affiliate <
perry.shafran at noaa.gov> wrote:
> Hi, John,
>
> The information that both Minna and you provided should help. I
will try
> it.
>
> Thanks!
>
> Perry
>
> On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Hi Perry,
>>
>> I see you have a question about discriminating between HGT fields
for
>> different level types. As you've already found, the PBL height and
cloud
>> base height are both encoded using the same GRIB1 or GRIB2
identification
>> information. However, they do differ by the GRIB level type value.
>>
>> In the MET config files, you can use the GRIB_lvl_typ to
discriminate
>> between these fields.
>>
>> Here's the GRIB table which defines these level type values:
>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
>>
>> I used a GFS file for example and ran it through wgrib to reveal
many HGT
>> levels:
>>
>> 248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
>> 24:P2=0:TimeU=1:sfc:24hr
>> fcst:NAve=0
>>
>> 326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
>> =24:P2=0:TimeU=1:tropopause:24hr
>> fcst:NAve=0
>>
>> 333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
>> =24:P2=0:TimeU=1:max
>> wind lev:24hr fcst:NAve=0
>>
>> 354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
>> =24:P2=0:TimeU=1:0C
>> isotherm:24hr fcst:NAve=0
>>
>> 356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
>> P1=24:P2=0:TimeU=1:high
>> trop freezing lvl:24hr fcst:NAve=0
>>
>>
>> I ran it through plot_data_plane like this:
>>
>>
>> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
>> 'name="HGT"; level="L0";'
>>
>>
>> But I get this warning message telling me that MET found 5 matches:
>>
>>
>> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches for
VarInfo
>> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using the
first match
>> found.
>>
>>
>> So I rerun using GRIB_lvl_typ=7; to select only the tropopause
level:
>>
>>
>> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
>> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
>>
>>
>> And the output log confirms that it correctly found record number
326,
>> which matches what wgrib said:
>>
>>
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact match
for
>> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
>> "GFS_20170615_CY12_FH24.GR1".
>>
>>
>> Hope that helps get you going! There are several GRIB filtering
options
>> like this that can be found either in the MET User's Guide or is
>> met-6.1/data/config/README.
>>
>>
>> Thanks,
>> John
>>
>> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via RT <
>> met_help at ucar.edu> wrote:
>>
>> >
>> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
>> > Transaction: Ticket created by perry.shafran at noaa.gov
>> > Queue: met_help
>> > Subject: question regarding heights at various levels
>> > Owner: Nobody
>> > Requestors: perry.shafran at noaa.gov
>> > Status: new
>> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
>> >
>> >
>> > Hi, there,
>> >
>> > I'm hoping this is a quick and easy question. Several of the
items
>> that I
>> > need to verify are heights at certain named levels. For example:
>> >
>> > 1) The ceiling is indicated in the grib file as HGT but the
level
>> > indicator is "ceiling height".
>> >
>> > 2) The cloud base is also "HGT" but is level indicator in the
grib is
>> > "cloud base level".
>> >
>> > 3) Finally, the PBL is also considered HGT but the level is
"planetary
>> > boundary level height".
>> >
>> > What should I put as the level indicator for these quantities?
>> >
>> > Thanks!
>> >
>> > Perry
>> >
>> >
>>
>>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: John Halley Gotway
Time: Tue Jan 16 15:56:50 2018
Perry,
I think you'll just need to make the Point-Stat config file a little
more
complex. Rather than setting up the "fcst" dictionary and then
copying it
over to the "obs" using "obs = fcst", you'll need to specify them
separately. Something like this:
fcst = {
field = [
{ name = "HGT"; level = "L0"; GRIB_lvl_typ = 215; }
];
}
obs = {
field = [
{ name = "CEILING"; level = "L0";' }
];
}
Does that make sense?
Thanks,
John
On Fri, Jan 12, 2018 at 8:52 AM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
>
> Hi, John,
>
> I need help setting this up.
>
> In PB2NC, I am adding (for example) "CEILING" to the list of desired
items
> in the observed value to verify:
>
> obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB", "HOVI",
> "TOCC","CEILING" ];
>
> But then I want to give it an equivalent value in the model to
verify with,
> which is HGT at ceiling level (which would be GRIB_lvl_typ = 215.
So how
> would I put this in the obs_bufr_map section of the PB2NC file?
>
> obs_bufr_map = [
> { key = "HOVI"; val = "VIS"; },
> { key = "TOCC"; val = "TCDC"; }
> ];
>
> In point_stat, I have set it up like this:
>
> {
> name = "HGT";
> level = "L0";
> GRIB_lvl_typ = 215;
> },
>
> Is this correct?
>
> Thanks!
>
> Perry
>
>
>
> On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA Affiliate <
> perry.shafran at noaa.gov> wrote:
>
> > Hi, John,
> >
> > The information that both Minna and you provided should help. I
will try
> > it.
> >
> > Thanks!
> >
> > Perry
> >
> > On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Hi Perry,
> >>
> >> I see you have a question about discriminating between HGT fields
for
> >> different level types. As you've already found, the PBL height
and
> cloud
> >> base height are both encoded using the same GRIB1 or GRIB2
> identification
> >> information. However, they do differ by the GRIB level type
value.
> >>
> >> In the MET config files, you can use the GRIB_lvl_typ to
discriminate
> >> between these fields.
> >>
> >> Here's the GRIB table which defines these level type values:
> >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
> >>
> >> I used a GFS file for example and ran it through wgrib to reveal
many
> HGT
> >> levels:
> >>
> >> 248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
> >> 24:P2=0:TimeU=1:sfc:24hr
> >> fcst:NAve=0
> >>
> >> 326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
> >> =24:P2=0:TimeU=1:tropopause:24hr
> >> fcst:NAve=0
> >>
> >> 333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
> >> =24:P2=0:TimeU=1:max
> >> wind lev:24hr fcst:NAve=0
> >>
> >> 354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
> >> =24:P2=0:TimeU=1:0C
> >> isotherm:24hr fcst:NAve=0
> >>
> >> 356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
> >> P1=24:P2=0:TimeU=1:high
> >> trop freezing lvl:24hr fcst:NAve=0
> >>
> >>
> >> I ran it through plot_data_plane like this:
> >>
> >>
> >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
> >> 'name="HGT"; level="L0";'
> >>
> >>
> >> But I get this warning message telling me that MET found 5
matches:
> >>
> >>
> >> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches for
VarInfo
> >> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using the
first
> match
> >> found.
> >>
> >>
> >> So I rerun using GRIB_lvl_typ=7; to select only the tropopause
level:
> >>
> >>
> >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/plot.ps
> >> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
> >>
> >>
> >> And the output log confirms that it correctly found record number
326,
> >> which matches what wgrib said:
> >>
> >>
> >> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact
match for
> >> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> >> "GFS_20170615_CY12_FH24.GR1".
> >>
> >>
> >> Hope that helps get you going! There are several GRIB filtering
options
> >> like this that can be found either in the MET User's Guide or is
> >> met-6.1/data/config/README.
> >>
> >>
> >> Thanks,
> >> John
> >>
> >> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via RT <
> >> met_help at ucar.edu> wrote:
> >>
> >> >
> >> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> >> > Transaction: Ticket created by perry.shafran at noaa.gov
> >> > Queue: met_help
> >> > Subject: question regarding heights at various levels
> >> > Owner: Nobody
> >> > Requestors: perry.shafran at noaa.gov
> >> > Status: new
> >> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537
> >
> >> >
> >> >
> >> > Hi, there,
> >> >
> >> > I'm hoping this is a quick and easy question. Several of the
items
> >> that I
> >> > need to verify are heights at certain named levels. For
example:
> >> >
> >> > 1) The ceiling is indicated in the grib file as HGT but the
level
> >> > indicator is "ceiling height".
> >> >
> >> > 2) The cloud base is also "HGT" but is level indicator in the
grib is
> >> > "cloud base level".
> >> >
> >> > 3) Finally, the PBL is also considered HGT but the level is
> "planetary
> >> > boundary level height".
> >> >
> >> > What should I put as the level indicator for these quantities?
> >> >
> >> > Thanks!
> >> >
> >> > Perry
> >> >
> >> >
> >>
> >>
> >
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: perry.shafran at noaa.gov
Time: Wed Jan 17 06:56:45 2018
Hi, John,
Yes, that does make sense. But what about all the other variables
where
obs=fcst? I have a series of different variables to verify and if I
set up
the obs dictionary that way, wouldn't it be a problem for the other
variables?
Perry
On Tue, Jan 16, 2018 at 5:56 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Perry,
>
> I think you'll just need to make the Point-Stat config file a little
more
> complex. Rather than setting up the "fcst" dictionary and then
copying it
> over to the "obs" using "obs = fcst", you'll need to specify them
> separately. Something like this:
>
> fcst = {
> field = [
> { name = "HGT"; level = "L0"; GRIB_lvl_typ = 215; }
> ];
> }
>
> obs = {
> field = [
> { name = "CEILING"; level = "L0";' }
> ];
> }
>
> Does that make sense?
>
> Thanks,
> John
>
> On Fri, Jan 12, 2018 at 8:52 AM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> >
> > Hi, John,
> >
> > I need help setting this up.
> >
> > In PB2NC, I am adding (for example) "CEILING" to the list of
desired
> items
> > in the observed value to verify:
> >
> > obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB", "HOVI",
> > "TOCC","CEILING" ];
> >
> > But then I want to give it an equivalent value in the model to
verify
> with,
> > which is HGT at ceiling level (which would be GRIB_lvl_typ = 215.
So how
> > would I put this in the obs_bufr_map section of the PB2NC file?
> >
> > obs_bufr_map = [
> > { key = "HOVI"; val = "VIS"; },
> > { key = "TOCC"; val = "TCDC"; }
> > ];
> >
> > In point_stat, I have set it up like this:
> >
> > {
> > name = "HGT";
> > level = "L0";
> > GRIB_lvl_typ = 215;
> > },
> >
> > Is this correct?
> >
> > Thanks!
> >
> > Perry
> >
> >
> >
> > On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA Affiliate <
> > perry.shafran at noaa.gov> wrote:
> >
> > > Hi, John,
> > >
> > > The information that both Minna and you provided should help. I
will
> try
> > > it.
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> Hi Perry,
> > >>
> > >> I see you have a question about discriminating between HGT
fields for
> > >> different level types. As you've already found, the PBL height
and
> > cloud
> > >> base height are both encoded using the same GRIB1 or GRIB2
> > identification
> > >> information. However, they do differ by the GRIB level type
value.
> > >>
> > >> In the MET config files, you can use the GRIB_lvl_typ to
discriminate
> > >> between these fields.
> > >>
> > >> Here's the GRIB table which defines these level type values:
> > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
> > >>
> > >> I used a GFS file for example and ran it through wgrib to
reveal many
> > HGT
> > >> levels:
> > >>
> > >> 248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
> > >> 24:P2=0:TimeU=1:sfc:24hr
> > >> fcst:NAve=0
> > >>
> > >> 326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
> > >> =24:P2=0:TimeU=1:tropopause:24hr
> > >> fcst:NAve=0
> > >>
> > >> 333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
> > >> =24:P2=0:TimeU=1:max
> > >> wind lev:24hr fcst:NAve=0
> > >>
> > >> 354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
> > >> =24:P2=0:TimeU=1:0C
> > >> isotherm:24hr fcst:NAve=0
> > >>
> > >> 356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
> > >> P1=24:P2=0:TimeU=1:high
> > >> trop freezing lvl:24hr fcst:NAve=0
> > >>
> > >>
> > >> I ran it through plot_data_plane like this:
> > >>
> > >>
> > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > >> 'name="HGT"; level="L0";'
> > >>
> > >>
> > >> But I get this warning message telling me that MET found 5
matches:
> > >>
> > >>
> > >> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches for
VarInfo
> > >> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using the
first
> > match
> > >> found.
> > >>
> > >>
> > >> So I rerun using GRIB_lvl_typ=7; to select only the tropopause
level:
> > >>
> > >>
> > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > >> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
> > >>
> > >>
> > >> And the output log confirms that it correctly found record
number 326,
> > >> which matches what wgrib said:
> > >>
> > >>
> > >> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact
match
> for
> > >> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> > >> "GFS_20170615_CY12_FH24.GR1".
> > >>
> > >>
> > >> Hope that helps get you going! There are several GRIB
filtering
> options
> > >> like this that can be found either in the MET User's Guide or
is
> > >> met-6.1/data/config/README.
> > >>
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via RT
<
> > >> met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> > >> > Transaction: Ticket created by perry.shafran at noaa.gov
> > >> > Queue: met_help
> > >> > Subject: question regarding heights at various levels
> > >> > Owner: Nobody
> > >> > Requestors: perry.shafran at noaa.gov
> > >> > Status: new
> > >> > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=83537
> > >
> > >> >
> > >> >
> > >> > Hi, there,
> > >> >
> > >> > I'm hoping this is a quick and easy question. Several of the
items
> > >> that I
> > >> > need to verify are heights at certain named levels. For
example:
> > >> >
> > >> > 1) The ceiling is indicated in the grib file as HGT but the
level
> > >> > indicator is "ceiling height".
> > >> >
> > >> > 2) The cloud base is also "HGT" but is level indicator in
the grib
> is
> > >> > "cloud base level".
> > >> >
> > >> > 3) Finally, the PBL is also considered HGT but the level is
> > "planetary
> > >> > boundary level height".
> > >> >
> > >> > What should I put as the level indicator for these
quantities?
> > >> >
> > >> > Thanks!
> > >> >
> > >> > Perry
> > >> >
> > >> >
> > >>
> > >>
> > >
> >
> >
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: perry.shafran at noaa.gov
Time: Wed Jan 17 08:25:07 2018
Also level="L0" doesn't seem to work for this variable.
Perry
On Tue, Jan 16, 2018 at 5:56 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Perry,
>
> I think you'll just need to make the Point-Stat config file a little
more
> complex. Rather than setting up the "fcst" dictionary and then
copying it
> over to the "obs" using "obs = fcst", you'll need to specify them
> separately. Something like this:
>
> fcst = {
> field = [
> { name = "HGT"; level = "L0"; GRIB_lvl_typ = 215; }
> ];
> }
>
> obs = {
> field = [
> { name = "CEILING"; level = "L0";' }
> ];
> }
>
> Does that make sense?
>
> Thanks,
> John
>
> On Fri, Jan 12, 2018 at 8:52 AM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> >
> > Hi, John,
> >
> > I need help setting this up.
> >
> > In PB2NC, I am adding (for example) "CEILING" to the list of
desired
> items
> > in the observed value to verify:
> >
> > obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB", "HOVI",
> > "TOCC","CEILING" ];
> >
> > But then I want to give it an equivalent value in the model to
verify
> with,
> > which is HGT at ceiling level (which would be GRIB_lvl_typ = 215.
So how
> > would I put this in the obs_bufr_map section of the PB2NC file?
> >
> > obs_bufr_map = [
> > { key = "HOVI"; val = "VIS"; },
> > { key = "TOCC"; val = "TCDC"; }
> > ];
> >
> > In point_stat, I have set it up like this:
> >
> > {
> > name = "HGT";
> > level = "L0";
> > GRIB_lvl_typ = 215;
> > },
> >
> > Is this correct?
> >
> > Thanks!
> >
> > Perry
> >
> >
> >
> > On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA Affiliate <
> > perry.shafran at noaa.gov> wrote:
> >
> > > Hi, John,
> > >
> > > The information that both Minna and you provided should help. I
will
> try
> > > it.
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> Hi Perry,
> > >>
> > >> I see you have a question about discriminating between HGT
fields for
> > >> different level types. As you've already found, the PBL height
and
> > cloud
> > >> base height are both encoded using the same GRIB1 or GRIB2
> > identification
> > >> information. However, they do differ by the GRIB level type
value.
> > >>
> > >> In the MET config files, you can use the GRIB_lvl_typ to
discriminate
> > >> between these fields.
> > >>
> > >> Here's the GRIB table which defines these level type values:
> > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
> > >>
> > >> I used a GFS file for example and ran it through wgrib to
reveal many
> > HGT
> > >> levels:
> > >>
> > >> 248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
> > >> 24:P2=0:TimeU=1:sfc:24hr
> > >> fcst:NAve=0
> > >>
> > >> 326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
> > >> =24:P2=0:TimeU=1:tropopause:24hr
> > >> fcst:NAve=0
> > >>
> > >> 333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
> > >> =24:P2=0:TimeU=1:max
> > >> wind lev:24hr fcst:NAve=0
> > >>
> > >> 354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
> > >> =24:P2=0:TimeU=1:0C
> > >> isotherm:24hr fcst:NAve=0
> > >>
> > >> 356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
> > >> P1=24:P2=0:TimeU=1:high
> > >> trop freezing lvl:24hr fcst:NAve=0
> > >>
> > >>
> > >> I ran it through plot_data_plane like this:
> > >>
> > >>
> > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > >> 'name="HGT"; level="L0";'
> > >>
> > >>
> > >> But I get this warning message telling me that MET found 5
matches:
> > >>
> > >>
> > >> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches for
VarInfo
> > >> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using the
first
> > match
> > >> found.
> > >>
> > >>
> > >> So I rerun using GRIB_lvl_typ=7; to select only the tropopause
level:
> > >>
> > >>
> > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > >> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
> > >>
> > >>
> > >> And the output log confirms that it correctly found record
number 326,
> > >> which matches what wgrib said:
> > >>
> > >>
> > >> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact
match
> for
> > >> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> > >> "GFS_20170615_CY12_FH24.GR1".
> > >>
> > >>
> > >> Hope that helps get you going! There are several GRIB
filtering
> options
> > >> like this that can be found either in the MET User's Guide or
is
> > >> met-6.1/data/config/README.
> > >>
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via RT
<
> > >> met_help at ucar.edu> wrote:
> > >>
> > >> >
> > >> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> > >> > Transaction: Ticket created by perry.shafran at noaa.gov
> > >> > Queue: met_help
> > >> > Subject: question regarding heights at various levels
> > >> > Owner: Nobody
> > >> > Requestors: perry.shafran at noaa.gov
> > >> > Status: new
> > >> > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=83537
> > >
> > >> >
> > >> >
> > >> > Hi, there,
> > >> >
> > >> > I'm hoping this is a quick and easy question. Several of the
items
> > >> that I
> > >> > need to verify are heights at certain named levels. For
example:
> > >> >
> > >> > 1) The ceiling is indicated in the grib file as HGT but the
level
> > >> > indicator is "ceiling height".
> > >> >
> > >> > 2) The cloud base is also "HGT" but is level indicator in
the grib
> is
> > >> > "cloud base level".
> > >> >
> > >> > 3) Finally, the PBL is also considered HGT but the level is
> > "planetary
> > >> > boundary level height".
> > >> >
> > >> > What should I put as the level indicator for these
quantities?
> > >> >
> > >> > Thanks!
> > >> >
> > >> > Perry
> > >> >
> > >> >
> > >>
> > >>
> > >
> >
> >
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: John Halley Gotway
Time: Wed Jan 17 13:34:04 2018
Perry,
Yes, unfortunately, it leads to some redundancy in the config file.
Please
take a look on theia here:
/scratch4/BMC/dtc/John.H.Gotway/MET/MET_Help/shafran_data_20180117
In PointStatConfig_cv, I listed out the "fcst" and "obs" dictionaries
separately.
You'll see in the run_ps.log file that I was able to find 239 matched
pairs
for CEILING at L0 for the ADPSFC message type.
I ran this example on the command line like this:
module use /contrib/modulefiles
module load met/6.1
point_stat AWIP3D00.tm00 prepda.2018010100.nc PointStatConfig_cv
-outdir
out -log run_ps.log
Hopefully, this example helps.
Thanks,
John
On Wed, Jan 17, 2018 at 8:25 AM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
>
> Also level="L0" doesn't seem to work for this variable.
>
> Perry
>
> On Tue, Jan 16, 2018 at 5:56 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Perry,
> >
> > I think you'll just need to make the Point-Stat config file a
little more
> > complex. Rather than setting up the "fcst" dictionary and then
copying
> it
> > over to the "obs" using "obs = fcst", you'll need to specify them
> > separately. Something like this:
> >
> > fcst = {
> > field = [
> > { name = "HGT"; level = "L0"; GRIB_lvl_typ = 215; }
> > ];
> > }
> >
> > obs = {
> > field = [
> > { name = "CEILING"; level = "L0";' }
> > ];
> > }
> >
> > Does that make sense?
> >
> > Thanks,
> > John
> >
> > On Fri, Jan 12, 2018 at 8:52 AM, perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> > >
> > > Hi, John,
> > >
> > > I need help setting this up.
> > >
> > > In PB2NC, I am adding (for example) "CEILING" to the list of
desired
> > items
> > > in the observed value to verify:
> > >
> > > obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB",
"HOVI",
> > > "TOCC","CEILING" ];
> > >
> > > But then I want to give it an equivalent value in the model to
verify
> > with,
> > > which is HGT at ceiling level (which would be GRIB_lvl_typ =
215. So
> how
> > > would I put this in the obs_bufr_map section of the PB2NC file?
> > >
> > > obs_bufr_map = [
> > > { key = "HOVI"; val = "VIS"; },
> > > { key = "TOCC"; val = "TCDC"; }
> > > ];
> > >
> > > In point_stat, I have set it up like this:
> > >
> > > {
> > > name = "HGT";
> > > level = "L0";
> > > GRIB_lvl_typ = 215;
> > > },
> > >
> > > Is this correct?
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > >
> > >
> > > On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA Affiliate
<
> > > perry.shafran at noaa.gov> wrote:
> > >
> > > > Hi, John,
> > > >
> > > > The information that both Minna and you provided should help.
I will
> > try
> > > > it.
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > > On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > >> Hi Perry,
> > > >>
> > > >> I see you have a question about discriminating between HGT
fields
> for
> > > >> different level types. As you've already found, the PBL
height and
> > > cloud
> > > >> base height are both encoded using the same GRIB1 or GRIB2
> > > identification
> > > >> information. However, they do differ by the GRIB level type
value.
> > > >>
> > > >> In the MET config files, you can use the GRIB_lvl_typ to
> discriminate
> > > >> between these fields.
> > > >>
> > > >> Here's the GRIB table which defines these level type values:
> > > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
> > > >>
> > > >> I used a GFS file for example and ran it through wgrib to
reveal
> many
> > > HGT
> > > >> levels:
> > > >>
> > > >> 248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
> > > >> 24:P2=0:TimeU=1:sfc:24hr
> > > >> fcst:NAve=0
> > > >>
> > > >> 326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
> > > >> =24:P2=0:TimeU=1:tropopause:24hr
> > > >> fcst:NAve=0
> > > >>
> > > >> 333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
> > > >> =24:P2=0:TimeU=1:max
> > > >> wind lev:24hr fcst:NAve=0
> > > >>
> > > >> 354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
> > > >> =24:P2=0:TimeU=1:0C
> > > >> isotherm:24hr fcst:NAve=0
> > > >>
> > > >> 356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
> > > >> P1=24:P2=0:TimeU=1:high
> > > >> trop freezing lvl:24hr fcst:NAve=0
> > > >>
> > > >>
> > > >> I ran it through plot_data_plane like this:
> > > >>
> > > >>
> > > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > > >> 'name="HGT"; level="L0";'
> > > >>
> > > >>
> > > >> But I get this warning message telling me that MET found 5
matches:
> > > >>
> > > >>
> > > >> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches
for
> VarInfo
> > > >> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using
the first
> > > match
> > > >> found.
> > > >>
> > > >>
> > > >> So I rerun using GRIB_lvl_typ=7; to select only the
tropopause
> level:
> > > >>
> > > >>
> > > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > > >> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
> > > >>
> > > >>
> > > >> And the output log confirms that it correctly found record
number
> 326,
> > > >> which matches what wgrib said:
> > > >>
> > > >>
> > > >> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found exact
match
> > for
> > > >> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> > > >> "GFS_20170615_CY12_FH24.GR1".
> > > >>
> > > >>
> > > >> Hope that helps get you going! There are several GRIB
filtering
> > options
> > > >> like this that can be found either in the MET User's Guide or
is
> > > >> met-6.1/data/config/README.
> > > >>
> > > >>
> > > >> Thanks,
> > > >> John
> > > >>
> > > >> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via
RT <
> > > >> met_help at ucar.edu> wrote:
> > > >>
> > > >> >
> > > >> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> > > >> > Transaction: Ticket created by perry.shafran at noaa.gov
> > > >> > Queue: met_help
> > > >> > Subject: question regarding heights at various levels
> > > >> > Owner: Nobody
> > > >> > Requestors: perry.shafran at noaa.gov
> > > >> > Status: new
> > > >> > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=83537
> > > >
> > > >> >
> > > >> >
> > > >> > Hi, there,
> > > >> >
> > > >> > I'm hoping this is a quick and easy question. Several of
the
> items
> > > >> that I
> > > >> > need to verify are heights at certain named levels. For
example:
> > > >> >
> > > >> > 1) The ceiling is indicated in the grib file as HGT but
the level
> > > >> > indicator is "ceiling height".
> > > >> >
> > > >> > 2) The cloud base is also "HGT" but is level indicator in
the
> grib
> > is
> > > >> > "cloud base level".
> > > >> >
> > > >> > 3) Finally, the PBL is also considered HGT but the level
is
> > > "planetary
> > > >> > boundary level height".
> > > >> >
> > > >> > What should I put as the level indicator for these
quantities?
> > > >> >
> > > >> > Thanks!
> > > >> >
> > > >> > Perry
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: perry.shafran at noaa.gov
Time: Wed Jan 17 13:53:09 2018
OK, I am seeing the problem - the grib file I am reading doesn't have
ceiling in it (grib level of 215 - you had level 2 in your point_stat
config file). Doing a wgrib2 of the original grib file confirms that.
So
now I need to do this same thing for something that has ceiling in it.
Perry
On Wed, Jan 17, 2018 at 3:34 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Perry,
>
> Yes, unfortunately, it leads to some redundancy in the config file.
Please
> take a look on theia here:
>
/scratch4/BMC/dtc/John.H.Gotway/MET/MET_Help/shafran_data_20180117
>
> In PointStatConfig_cv, I listed out the "fcst" and "obs"
dictionaries
> separately.
>
> You'll see in the run_ps.log file that I was able to find 239
matched pairs
> for CEILING at L0 for the ADPSFC message type.
>
> I ran this example on the command line like this:
>
> module use /contrib/modulefiles
> module load met/6.1
> point_stat AWIP3D00.tm00 prepda.2018010100.nc PointStatConfig_cv
> -outdir
> out -log run_ps.log
>
> Hopefully, this example helps.
>
> Thanks,
> John
>
> On Wed, Jan 17, 2018 at 8:25 AM, perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> >
> > Also level="L0" doesn't seem to work for this variable.
> >
> > Perry
> >
> > On Tue, Jan 16, 2018 at 5:56 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Perry,
> > >
> > > I think you'll just need to make the Point-Stat config file a
little
> more
> > > complex. Rather than setting up the "fcst" dictionary and then
copying
> > it
> > > over to the "obs" using "obs = fcst", you'll need to specify
them
> > > separately. Something like this:
> > >
> > > fcst = {
> > > field = [
> > > { name = "HGT"; level = "L0"; GRIB_lvl_typ = 215; }
> > > ];
> > > }
> > >
> > > obs = {
> > > field = [
> > > { name = "CEILING"; level = "L0";' }
> > > ];
> > > }
> > >
> > > Does that make sense?
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, Jan 12, 2018 at 8:52 AM, perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537
>
> > > >
> > > > Hi, John,
> > > >
> > > > I need help setting this up.
> > > >
> > > > In PB2NC, I am adding (for example) "CEILING" to the list of
desired
> > > items
> > > > in the observed value to verify:
> > > >
> > > > obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB",
"HOVI",
> > > > "TOCC","CEILING" ];
> > > >
> > > > But then I want to give it an equivalent value in the model to
verify
> > > with,
> > > > which is HGT at ceiling level (which would be GRIB_lvl_typ =
215. So
> > how
> > > > would I put this in the obs_bufr_map section of the PB2NC
file?
> > > >
> > > > obs_bufr_map = [
> > > > { key = "HOVI"; val = "VIS"; },
> > > > { key = "TOCC"; val = "TCDC"; }
> > > > ];
> > > >
> > > > In point_stat, I have set it up like this:
> > > >
> > > > {
> > > > name = "HGT";
> > > > level = "L0";
> > > > GRIB_lvl_typ = 215;
> > > > },
> > > >
> > > > Is this correct?
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > >
> > > >
> > > > On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA
Affiliate <
> > > > perry.shafran at noaa.gov> wrote:
> > > >
> > > > > Hi, John,
> > > > >
> > > > > The information that both Minna and you provided should
help. I
> will
> > > try
> > > > > it.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Perry
> > > > >
> > > > > On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via RT
<
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > >> Hi Perry,
> > > > >>
> > > > >> I see you have a question about discriminating between HGT
fields
> > for
> > > > >> different level types. As you've already found, the PBL
height
> and
> > > > cloud
> > > > >> base height are both encoded using the same GRIB1 or GRIB2
> > > > identification
> > > > >> information. However, they do differ by the GRIB level
type
> value.
> > > > >>
> > > > >> In the MET config files, you can use the GRIB_lvl_typ to
> > discriminate
> > > > >> between these fields.
> > > > >>
> > > > >> Here's the GRIB table which defines these level type
values:
> > > > >> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
> > > > >>
> > > > >> I used a GFS file for example and ran it through wgrib to
reveal
> > many
> > > > HGT
> > > > >> levels:
> > > > >>
> > > > >>
248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
> > > > >> 24:P2=0:TimeU=1:sfc:24hr
> > > > >> fcst:NAve=0
> > > > >>
> > > > >>
326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
> > > > >> =24:P2=0:TimeU=1:tropopause:24hr
> > > > >> fcst:NAve=0
> > > > >>
> > > > >>
333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
> > > > >> =24:P2=0:TimeU=1:max
> > > > >> wind lev:24hr fcst:NAve=0
> > > > >>
> > > > >>
354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
> > > > >> =24:P2=0:TimeU=1:0C
> > > > >> isotherm:24hr fcst:NAve=0
> > > > >>
> > > > >>
356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
> > > > >> P1=24:P2=0:TimeU=1:high
> > > > >> trop freezing lvl:24hr fcst:NAve=0
> > > > >>
> > > > >>
> > > > >> I ran it through plot_data_plane like this:
> > > > >>
> > > > >>
> > > > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > > > >> 'name="HGT"; level="L0";'
> > > > >>
> > > > >>
> > > > >> But I get this warning message telling me that MET found 5
> matches:
> > > > >>
> > > > >>
> > > > >> WARNING: MetGrib1DataFile::data_plane() -> Found 5 matches
for
> > VarInfo
> > > > >> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1". Using
the
> first
> > > > match
> > > > >> found.
> > > > >>
> > > > >>
> > > > >> So I rerun using GRIB_lvl_typ=7; to select only the
tropopause
> > level:
> > > > >>
> > > > >>
> > > > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1
~/plot.ps
> > > > >> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
> > > > >>
> > > > >>
> > > > >> And the output log confirms that it correctly found record
number
> > 326,
> > > > >> which matches what wgrib said:
> > > > >>
> > > > >>
> > > > >> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
exact
> match
> > > for
> > > > >> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> > > > >> "GFS_20170615_CY12_FH24.GR1".
> > > > >>
> > > > >>
> > > > >> Hope that helps get you going! There are several GRIB
filtering
> > > options
> > > > >> like this that can be found either in the MET User's Guide
or is
> > > > >> met-6.1/data/config/README.
> > > > >>
> > > > >>
> > > > >> Thanks,
> > > > >> John
> > > > >>
> > > > >> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov via
RT <
> > > > >> met_help at ucar.edu> wrote:
> > > > >>
> > > > >> >
> > > > >> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> > > > >> > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > >> > Queue: met_help
> > > > >> > Subject: question regarding heights at various
levels
> > > > >> > Owner: Nobody
> > > > >> > Requestors: perry.shafran at noaa.gov
> > > > >> > Status: new
> > > > >> > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=83537
> > > > >
> > > > >> >
> > > > >> >
> > > > >> > Hi, there,
> > > > >> >
> > > > >> > I'm hoping this is a quick and easy question. Several of
the
> > items
> > > > >> that I
> > > > >> > need to verify are heights at certain named levels. For
> example:
> > > > >> >
> > > > >> > 1) The ceiling is indicated in the grib file as HGT but
the
> level
> > > > >> > indicator is "ceiling height".
> > > > >> >
> > > > >> > 2) The cloud base is also "HGT" but is level indicator
in the
> > grib
> > > is
> > > > >> > "cloud base level".
> > > > >> >
> > > > >> > 3) Finally, the PBL is also considered HGT but the level
is
> > > > "planetary
> > > > >> > boundary level height".
> > > > >> >
> > > > >> > What should I put as the level indicator for these
quantities?
> > > > >> >
> > > > >> > Thanks!
> > > > >> >
> > > > >> > Perry
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: question regarding heights at various levels
From: John Halley Gotway
Time: Wed Jan 17 14:06:25 2018
Perry,
Yes, I used 2 because the sample GRIB file I had didn't have 215
either.
Sounds like you're on the right track.
John
On Wed, Jan 17, 2018 at 1:53 PM, perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
>
> OK, I am seeing the problem - the grib file I am reading doesn't
have
> ceiling in it (grib level of 215 - you had level 2 in your
point_stat
> config file). Doing a wgrib2 of the original grib file confirms
that. So
> now I need to do this same thing for something that has ceiling in
it.
>
> Perry
>
> On Wed, Jan 17, 2018 at 3:34 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Perry,
> >
> > Yes, unfortunately, it leads to some redundancy in the config
file.
> Please
> > take a look on theia here:
> >
/scratch4/BMC/dtc/John.H.Gotway/MET/MET_Help/shafran_data_20180117
> >
> > In PointStatConfig_cv, I listed out the "fcst" and "obs"
dictionaries
> > separately.
> >
> > You'll see in the run_ps.log file that I was able to find 239
matched
> pairs
> > for CEILING at L0 for the ADPSFC message type.
> >
> > I ran this example on the command line like this:
> >
> > module use /contrib/modulefiles
> > module load met/6.1
> > point_stat AWIP3D00.tm00 prepda.2018010100.nc
PointStatConfig_cv
> > -outdir
> > out -log run_ps.log
> >
> > Hopefully, this example helps.
> >
> > Thanks,
> > John
> >
> > On Wed, Jan 17, 2018 at 8:25 AM, perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> > >
> > > Also level="L0" doesn't seem to work for this variable.
> > >
> > > Perry
> > >
> > > On Tue, Jan 16, 2018 at 5:56 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Perry,
> > > >
> > > > I think you'll just need to make the Point-Stat config file a
little
> > more
> > > > complex. Rather than setting up the "fcst" dictionary and
then
> copying
> > > it
> > > > over to the "obs" using "obs = fcst", you'll need to specify
them
> > > > separately. Something like this:
> > > >
> > > > fcst = {
> > > > field = [
> > > > { name = "HGT"; level = "L0"; GRIB_lvl_typ = 215; }
> > > > ];
> > > > }
> > > >
> > > > obs = {
> > > > field = [
> > > > { name = "CEILING"; level = "L0";' }
> > > > ];
> > > > }
> > > >
> > > > Does that make sense?
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Fri, Jan 12, 2018 at 8:52 AM, perry.shafran at noaa.gov via RT
<
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83537 >
> > > > >
> > > > > Hi, John,
> > > > >
> > > > > I need help setting this up.
> > > > >
> > > > > In PB2NC, I am adding (for example) "CEILING" to the list of
> desired
> > > > items
> > > > > in the observed value to verify:
> > > > >
> > > > > obs_bufr_var = [ "POB", "TOB", "ZOB", "QOB", "UOB", "VOB",
"HOVI",
> > > > > "TOCC","CEILING" ];
> > > > >
> > > > > But then I want to give it an equivalent value in the model
to
> verify
> > > > with,
> > > > > which is HGT at ceiling level (which would be GRIB_lvl_typ =
215.
> So
> > > how
> > > > > would I put this in the obs_bufr_map section of the PB2NC
file?
> > > > >
> > > > > obs_bufr_map = [
> > > > > { key = "HOVI"; val = "VIS"; },
> > > > > { key = "TOCC"; val = "TCDC"; }
> > > > > ];
> > > > >
> > > > > In point_stat, I have set it up like this:
> > > > >
> > > > > {
> > > > > name = "HGT";
> > > > > level = "L0";
> > > > > GRIB_lvl_typ = 215;
> > > > > },
> > > > >
> > > > > Is this correct?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Perry
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Jan 10, 2018 at 12:33 PM, Perry Shafran - NOAA
Affiliate <
> > > > > perry.shafran at noaa.gov> wrote:
> > > > >
> > > > > > Hi, John,
> > > > > >
> > > > > > The information that both Minna and you provided should
help. I
> > will
> > > > try
> > > > > > it.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Perry
> > > > > >
> > > > > > On Wed, Jan 10, 2018 at 11:47 AM, John Halley Gotway via
RT <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > >> Hi Perry,
> > > > > >>
> > > > > >> I see you have a question about discriminating between
HGT
> fields
> > > for
> > > > > >> different level types. As you've already found, the PBL
height
> > and
> > > > > cloud
> > > > > >> base height are both encoded using the same GRIB1 or
GRIB2
> > > > > identification
> > > > > >> information. However, they do differ by the GRIB level
type
> > value.
> > > > > >>
> > > > > >> In the MET config files, you can use the GRIB_lvl_typ to
> > > discriminate
> > > > > >> between these fields.
> > > > > >>
> > > > > >> Here's the GRIB table which defines these level type
values:
> > > > > >>
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table3.html
> > > > > >>
> > > > > >> I used a GFS file for example and ran it through wgrib to
reveal
> > > many
> > > > > HGT
> > > > > >> levels:
> > > > > >>
> > > > > >>
248:99369978:d=17061512:HGT:kpds5=7:kpds6=1:kpds7=0:TR=0:P1=
> > > > > >> 24:P2=0:TimeU=1:sfc:24hr
> > > > > >> fcst:NAve=0
> > > > > >>
> > > > > >>
326:122162046:d=17061512:HGT:kpds5=7:kpds6=7:kpds7=0:TR=0:P1
> > > > > >> =24:P2=0:TimeU=1:tropopause:24hr
> > > > > >> fcst:NAve=0
> > > > > >>
> > > > > >>
333:125086734:d=17061512:HGT:kpds5=7:kpds6=6:kpds7=0:TR=0:P1
> > > > > >> =24:P2=0:TimeU=1:max
> > > > > >> wind lev:24hr fcst:NAve=0
> > > > > >>
> > > > > >>
354:133333000:d=17061512:HGT:kpds5=7:kpds6=4:kpds7=0:TR=0:P1
> > > > > >> =24:P2=0:TimeU=1:0C
> > > > > >> isotherm:24hr fcst:NAve=0
> > > > > >>
> > > > > >>
356:134080438:d=17061512:HGT:kpds5=7:kpds6=204:kpds7=0:TR=0:
> > > > > >> P1=24:P2=0:TimeU=1:high
> > > > > >> trop freezing lvl:24hr fcst:NAve=0
> > > > > >>
> > > > > >>
> > > > > >> I ran it through plot_data_plane like this:
> > > > > >>
> > > > > >>
> > > > > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/
> plot.ps
> > > > > >> 'name="HGT"; level="L0";'
> > > > > >>
> > > > > >>
> > > > > >> But I get this warning message telling me that MET found
5
> > matches:
> > > > > >>
> > > > > >>
> > > > > >> WARNING: MetGrib1DataFile::data_plane() -> Found 5
matches for
> > > VarInfo
> > > > > >> "HGT/L0" in GRIB file "GFS_20170615_CY12_FH24.GR1".
Using the
> > first
> > > > > match
> > > > > >> found.
> > > > > >>
> > > > > >>
> > > > > >> So I rerun using GRIB_lvl_typ=7; to select only the
tropopause
> > > level:
> > > > > >>
> > > > > >>
> > > > > >> met-6.1/bin/plot_data_plane GFS_20170615_CY12_FH24.GR1 ~/
> plot.ps
> > > > > >> 'name="HGT"; level="L0"; GRIB_lvl_typ=7;' -v 3
> > > > > >>
> > > > > >>
> > > > > >> And the output log confirms that it correctly found
record
> number
> > > 326,
> > > > > >> which matches what wgrib said:
> > > > > >>
> > > > > >>
> > > > > >> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
exact
> > match
> > > > for
> > > > > >> VarInfo "HGT/L0" in GRIB record 326 of GRIB file
> > > > > >> "GFS_20170615_CY12_FH24.GR1".
> > > > > >>
> > > > > >>
> > > > > >> Hope that helps get you going! There are several GRIB
filtering
> > > > options
> > > > > >> like this that can be found either in the MET User's
Guide or is
> > > > > >> met-6.1/data/config/README.
> > > > > >>
> > > > > >>
> > > > > >> Thanks,
> > > > > >> John
> > > > > >>
> > > > > >> On Wed, Jan 10, 2018 at 7:48 AM, perry.shafran at noaa.gov
via RT
> <
> > > > > >> met_help at ucar.edu> wrote:
> > > > > >>
> > > > > >> >
> > > > > >> > Wed Jan 10 07:48:11 2018: Request 83537 was acted upon.
> > > > > >> > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > >> > Queue: met_help
> > > > > >> > Subject: question regarding heights at various
levels
> > > > > >> > Owner: Nobody
> > > > > >> > Requestors: perry.shafran at noaa.gov
> > > > > >> > Status: new
> > > > > >> > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > > Ticket/Display.html?id=83537
> > > > > >
> > > > > >> >
> > > > > >> >
> > > > > >> > Hi, there,
> > > > > >> >
> > > > > >> > I'm hoping this is a quick and easy question. Several
of the
> > > items
> > > > > >> that I
> > > > > >> > need to verify are heights at certain named levels.
For
> > example:
> > > > > >> >
> > > > > >> > 1) The ceiling is indicated in the grib file as HGT
but the
> > level
> > > > > >> > indicator is "ceiling height".
> > > > > >> >
> > > > > >> > 2) The cloud base is also "HGT" but is level indicator
in the
> > > grib
> > > > is
> > > > > >> > "cloud base level".
> > > > > >> >
> > > > > >> > 3) Finally, the PBL is also considered HGT but the
level is
> > > > > "planetary
> > > > > >> > boundary level height".
> > > > > >> >
> > > > > >> > What should I put as the level indicator for these
quantities?
> > > > > >> >
> > > > > >> > Thanks!
> > > > > >> >
> > > > > >> > Perry
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list