[Met_help] [rt.rap.ucar.edu #97240] History for PB2NCConfig_default
John Halley Gotway via RT
met_help at ucar.edu
Wed Oct 28 10:01:41 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I have two questions about the "PB2NCConfig_default" file about the
vertical layer definition:
1. The unit for " elevation_range" as used below is MSL
elevation_range = {
beg = -1000;
end = 100000;
}
But for this one below, the unit is layer, NOT "mb". Then how to define the
range using mb? e.g: if I want the pressure level covering 200-300mb, how
to do that?
level_range = {
beg = 1;
end = 511;
}
2. If both " elevation_range" and "level_range" are defined in the
configuration, which one will be used? I guess the one on the top will be
overwritten (not used at all), am I correct? Or there will be two outputs
using different standards.
Please help to clarify.
Thank you.
Binyu
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: PB2NCConfig_default
From: John Halley Gotway
Time: Tue Oct 27 14:25:23 2020
Binyu,
While you *can* filter point observations in PB2NC, I generally
wouldn't
recommend doing that unless you have a good reason to do so. Instead,
just
run pb2nc to pass through whatever observations are present in the
input...
and then configure Point-Stat to filter the observations that are
actually
used for your verification task.
To answer your question, when you define multiple filters in the PB2NC
config file, only those point observations which meet ALL the
filtering
criteria will be written to the output. For details about the
filtering
options in PB2NC, please see:
https://dtcenter.github.io/MET/latest/Users_Guide/reformat_point.html?highlight=pb2nc#pb2nc-
configuration-file
And the entries for level_range and level_category link to the nitty
gritty
details here:
https://www.emc.ncep.noaa.gov/mmb/data_processing/prepbufr.doc/table_1.htm
But again, I do think it's simpler NOT to filter by level in pb2nc but
define the filters in point_stat instead.
Thanks,
John
On Tue, Oct 27, 2020 at 1:55 PM binyu.wang at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Tue Oct 27 13:55:12 2020: Request 97240 was acted upon.
> Transaction: Ticket created by binyu.wang at noaa.gov
> Queue: met_help
> Subject: PB2NCConfig_default
> Owner: Nobody
> Requestors: binyu.wang at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97240 >
>
>
> Hello,
>
> I have two questions about the "PB2NCConfig_default" file about the
> vertical layer definition:
>
> 1. The unit for " elevation_range" as used below is MSL
> elevation_range = {
> beg = -1000;
> end = 100000;
> }
>
> But for this one below, the unit is layer, NOT "mb". Then how to
define the
> range using mb? e.g: if I want the pressure level covering 200-
300mb, how
> to do that?
> level_range = {
> beg = 1;
> end = 511;
> }
>
> 2. If both " elevation_range" and "level_range" are defined in the
> configuration, which one will be used? I guess the one on the top
will be
> overwritten (not used at all), am I correct? Or there will be two
outputs
> using different standards.
>
> Please help to clarify.
>
> Thank you.
> Binyu
>
>
------------------------------------------------
Subject: PB2NCConfig_default
From: binyu.wang at noaa.gov
Time: Tue Oct 27 19:10:49 2020
Hello John,
Thank you for clarifying. It makes sense to filter point observation
by
level to use point_stat. The reason I want to do that using "pb2nc" is
because I try to find the obs. location in the upper level only
(~250mb)
using "plot_point_obs". You had told me that there’s currently no way
to
filter points by their vertical level.
Roughly I can use "elevation_range" in the utility "pb2nc" to replace
the
pressure level to solve my problem. At the same time I did check the
link
that you provided, but it seems there is no explanation about the
level
range. Like in the default file, what 1-511 refers to?
level_range = {
beg = 1;
end = 511;
}
Binyu
On Tue, Oct 27, 2020 at 4:26 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Binyu,
>
> While you *can* filter point observations in PB2NC, I generally
wouldn't
> recommend doing that unless you have a good reason to do so.
Instead, just
> run pb2nc to pass through whatever observations are present in the
input...
> and then configure Point-Stat to filter the observations that are
actually
> used for your verification task.
>
> To answer your question, when you define multiple filters in the
PB2NC
> config file, only those point observations which meet ALL the
filtering
> criteria will be written to the output. For details about the
filtering
> options in PB2NC, please see:
>
>
https://dtcenter.github.io/MET/latest/Users_Guide/reformat_point.html?highlight=pb2nc#pb2nc-
configuration-file
>
> And the entries for level_range and level_category link to the nitty
gritty
> details here:
>
https://www.emc.ncep.noaa.gov/mmb/data_processing/prepbufr.doc/table_1.htm
>
> But again, I do think it's simpler NOT to filter by level in pb2nc
but
> define the filters in point_stat instead.
>
> Thanks,
> John
>
> On Tue, Oct 27, 2020 at 1:55 PM binyu.wang at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Oct 27 13:55:12 2020: Request 97240 was acted upon.
> > Transaction: Ticket created by binyu.wang at noaa.gov
> > Queue: met_help
> > Subject: PB2NCConfig_default
> > Owner: Nobody
> > Requestors: binyu.wang at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97240 >
> >
> >
> > Hello,
> >
> > I have two questions about the "PB2NCConfig_default" file about
the
> > vertical layer definition:
> >
> > 1. The unit for " elevation_range" as used below is MSL
> > elevation_range = {
> > beg = -1000;
> > end = 100000;
> > }
> >
> > But for this one below, the unit is layer, NOT "mb". Then how to
define
> the
> > range using mb? e.g: if I want the pressure level covering 200-
300mb,
> how
> > to do that?
> > level_range = {
> > beg = 1;
> > end = 511;
> > }
> >
> > 2. If both " elevation_range" and "level_range" are defined in
the
> > configuration, which one will be used? I guess the one on the top
will
> be
> > overwritten (not used at all), am I correct? Or there will be two
outputs
> > using different standards.
> >
> > Please help to clarify.
> >
> > Thank you.
> > Binyu
> >
> >
>
>
------------------------------------------------
Subject: PB2NCConfig_default
From: John Halley Gotway
Time: Wed Oct 28 09:28:25 2020
Binyu,
The PrepBUFR file format has slots for up to 512 level settings. We
passed
this option through the PB2NC because it exists, but I have never
actually
used it myself to filter data. I don't think it will be a good way of
extracting obs at 250mb... at least as far as I know.
FYI, based on your recent question about plot_point_obs, I wrote up
this
GitHub feature request issue:
https://github.com/dtcenter/MET/issues/1528
But we don't have it identified as a very high priority.
If you really need to see the location of P250 obs, you can:
(1) Run pb2nc.
(2) Run an Rscript to dump the output to ascii.
(3) Filter out the P250 obs from that ascii file.
(4) Run ascii2nc on the result.
(5) Run plot_point_obs on that result.
Here I've used the output from MET's "make test" command to
demonstrate:
Rscript scripts/Rscripts/pntnc2ascii.R out/pb2nc/sample_pb.nc >
out/pb2nc/sample_pb.txt
grep " 250 " out/pb2nc/sample_pb.txt | grep ADPUPA > ADPUPA_P250.txt
bin/ascii2nc ADPUPA_P250.txt ADPUPA_P250.nc
bin/plot_point_obs ADPUPA_P250.nc ADPUPA_P250.ps
The resulting image is attached. This is obviously not an ideal or
efficient process. But if you're digging into the data for a single
case,
it's doable.
Thanks,
John
On Tue, Oct 27, 2020 at 7:11 PM binyu.wang at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97240 >
>
> Hello John,
>
> Thank you for clarifying. It makes sense to filter point observation
by
> level to use point_stat. The reason I want to do that using "pb2nc"
is
> because I try to find the obs. location in the upper level only
(~250mb)
> using "plot_point_obs". You had told me that there’s currently no
way to
> filter points by their vertical level.
>
> Roughly I can use "elevation_range" in the utility "pb2nc" to
replace the
> pressure level to solve my problem. At the same time I did check the
link
> that you provided, but it seems there is no explanation about the
level
> range. Like in the default file, what 1-511 refers to?
>
> level_range = {
> beg = 1;
> end = 511;
> }
>
> Binyu
>
>
> On Tue, Oct 27, 2020 at 4:26 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Binyu,
> >
> > While you *can* filter point observations in PB2NC, I generally
wouldn't
> > recommend doing that unless you have a good reason to do so.
Instead,
> just
> > run pb2nc to pass through whatever observations are present in the
> input...
> > and then configure Point-Stat to filter the observations that are
> actually
> > used for your verification task.
> >
> > To answer your question, when you define multiple filters in the
PB2NC
> > config file, only those point observations which meet ALL the
filtering
> > criteria will be written to the output. For details about the
filtering
> > options in PB2NC, please see:
> >
> >
>
https://dtcenter.github.io/MET/latest/Users_Guide/reformat_point.html?highlight=pb2nc#pb2nc-
configuration-file
> >
> > And the entries for level_range and level_category link to the
nitty
> gritty
> > details here:
> >
>
https://www.emc.ncep.noaa.gov/mmb/data_processing/prepbufr.doc/table_1.htm
> >
> > But again, I do think it's simpler NOT to filter by level in pb2nc
but
> > define the filters in point_stat instead.
> >
> > Thanks,
> > John
> >
> > On Tue, Oct 27, 2020 at 1:55 PM binyu.wang at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Oct 27 13:55:12 2020: Request 97240 was acted upon.
> > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > Queue: met_help
> > > Subject: PB2NCConfig_default
> > > Owner: Nobody
> > > Requestors: binyu.wang at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97240
> >
> > >
> > >
> > > Hello,
> > >
> > > I have two questions about the "PB2NCConfig_default" file about
the
> > > vertical layer definition:
> > >
> > > 1. The unit for " elevation_range" as used below is MSL
> > > elevation_range = {
> > > beg = -1000;
> > > end = 100000;
> > > }
> > >
> > > But for this one below, the unit is layer, NOT "mb". Then how to
define
> > the
> > > range using mb? e.g: if I want the pressure level covering 200-
300mb,
> > how
> > > to do that?
> > > level_range = {
> > > beg = 1;
> > > end = 511;
> > > }
> > >
> > > 2. If both " elevation_range" and "level_range" are defined in
the
> > > configuration, which one will be used? I guess the one on the
top will
> > be
> > > overwritten (not used at all), am I correct? Or there will be
two
> outputs
> > > using different standards.
> > >
> > > Please help to clarify.
> > >
> > > Thank you.
> > > Binyu
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: PB2NCConfig_default
From: binyu.wang at noaa.gov
Time: Wed Oct 28 09:47:29 2020
Sounds good, thank you very much!
Binyu
On Wed, Oct 28, 2020 at 11:28 AM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Binyu,
>
> The PrepBUFR file format has slots for up to 512 level settings. We
passed
> this option through the PB2NC because it exists, but I have never
actually
> used it myself to filter data. I don't think it will be a good way
of
> extracting obs at 250mb... at least as far as I know.
>
> FYI, based on your recent question about plot_point_obs, I wrote up
this
> GitHub feature request issue:
> https://github.com/dtcenter/MET/issues/1528
> But we don't have it identified as a very high priority.
>
> If you really need to see the location of P250 obs, you can:
> (1) Run pb2nc.
> (2) Run an Rscript to dump the output to ascii.
> (3) Filter out the P250 obs from that ascii file.
> (4) Run ascii2nc on the result.
> (5) Run plot_point_obs on that result.
>
> Here I've used the output from MET's "make test" command to
demonstrate:
>
> Rscript scripts/Rscripts/pntnc2ascii.R out/pb2nc/sample_pb.nc >
> out/pb2nc/sample_pb.txt
> grep " 250 " out/pb2nc/sample_pb.txt | grep ADPUPA > ADPUPA_P250.txt
> bin/ascii2nc ADPUPA_P250.txt ADPUPA_P250.nc
> bin/plot_point_obs ADPUPA_P250.nc ADPUPA_P250.ps
>
> The resulting image is attached. This is obviously not an ideal or
> efficient process. But if you're digging into the data for a single
case,
> it's doable.
>
> Thanks,
> John
>
> On Tue, Oct 27, 2020 at 7:11 PM binyu.wang at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97240 >
> >
> > Hello John,
> >
> > Thank you for clarifying. It makes sense to filter point
observation by
> > level to use point_stat. The reason I want to do that using
"pb2nc" is
> > because I try to find the obs. location in the upper level only
(~250mb)
> > using "plot_point_obs". You had told me that there’s currently no
way to
> > filter points by their vertical level.
> >
> > Roughly I can use "elevation_range" in the utility "pb2nc" to
replace the
> > pressure level to solve my problem. At the same time I did check
the link
> > that you provided, but it seems there is no explanation about the
level
> > range. Like in the default file, what 1-511 refers to?
> >
> > level_range = {
> > beg = 1;
> > end = 511;
> > }
> >
> > Binyu
> >
> >
> > On Tue, Oct 27, 2020 at 4:26 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Binyu,
> > >
> > > While you *can* filter point observations in PB2NC, I generally
> wouldn't
> > > recommend doing that unless you have a good reason to do so.
Instead,
> > just
> > > run pb2nc to pass through whatever observations are present in
the
> > input...
> > > and then configure Point-Stat to filter the observations that
are
> > actually
> > > used for your verification task.
> > >
> > > To answer your question, when you define multiple filters in the
PB2NC
> > > config file, only those point observations which meet ALL the
filtering
> > > criteria will be written to the output. For details about the
> filtering
> > > options in PB2NC, please see:
> > >
> > >
> >
>
https://dtcenter.github.io/MET/latest/Users_Guide/reformat_point.html?highlight=pb2nc#pb2nc-
configuration-file
> > >
> > > And the entries for level_range and level_category link to the
nitty
> > gritty
> > > details here:
> > >
> >
>
https://www.emc.ncep.noaa.gov/mmb/data_processing/prepbufr.doc/table_1.htm
> > >
> > > But again, I do think it's simpler NOT to filter by level in
pb2nc but
> > > define the filters in point_stat instead.
> > >
> > > Thanks,
> > > John
> > >
> > > On Tue, Oct 27, 2020 at 1:55 PM binyu.wang at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Tue Oct 27 13:55:12 2020: Request 97240 was acted upon.
> > > > Transaction: Ticket created by binyu.wang at noaa.gov
> > > > Queue: met_help
> > > > Subject: PB2NCConfig_default
> > > > Owner: Nobody
> > > > Requestors: binyu.wang at noaa.gov
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97240
> > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I have two questions about the "PB2NCConfig_default" file
about the
> > > > vertical layer definition:
> > > >
> > > > 1. The unit for " elevation_range" as used below is MSL
> > > > elevation_range = {
> > > > beg = -1000;
> > > > end = 100000;
> > > > }
> > > >
> > > > But for this one below, the unit is layer, NOT "mb". Then how
to
> define
> > > the
> > > > range using mb? e.g: if I want the pressure level covering
> 200-300mb,
> > > how
> > > > to do that?
> > > > level_range = {
> > > > beg = 1;
> > > > end = 511;
> > > > }
> > > >
> > > > 2. If both " elevation_range" and "level_range" are defined
in the
> > > > configuration, which one will be used? I guess the one on the
top
> will
> > > be
> > > > overwritten (not used at all), am I correct? Or there will be
two
> > outputs
> > > > using different standards.
> > > >
> > > > Please help to clarify.
> > > >
> > > > Thank you.
> > > > Binyu
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list