[Met_help] [rt.rap.ucar.edu #90787] History for field string for ULWRF
John Halley Gotway via RT
met_help at ucar.edu
Tue Jun 25 09:49:21 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Do you know if there is a way to specify in the field string of a call to plot_data_plane which of multiple fields with the same name you want to be plotted? The field string I am currently using for ULWRF is 'name="ULWRF"; level="L0";' That results in the following warning:
WARNING: MetGrib2DataFile::data_plane() - Multiple matching records found for 'ULWRF/L0' - 500, 502 - using 500
Here is a short subset of what's in the data:
500 20190529 00Z +0Hr ULWRF3Hr_AVG 'Upward Long-Wave Rad. Flux' (W m^-2) SFC 'Ground or water surface'
501 20190529 00Z +0Hr USWRF3Hr_AVG 'Upward Short-Wave Rad. Flux' (W m^-2) NTAT 'Nominal top of atmosphere'
502 20190529 00Z +0Hr ULWRF3Hr_AVG 'Upward Long-Wave Rad. Flux' (W m^-2) NTAT 'Nominal top of atmosphere'
The one that is getting used by plot_data_plane is the SFC one (500), which Ken says is not the one we want. We want the NTAT one (502). I have been looking at the MET User's Guide and trying various ways to specify the NTAT one, but so far have not found much detail on what constitutes a valid field string (just a few examples), and haven't stumbled into a way that actually works.
Do you know if it can be done, and if so, how?
Thanks!
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: field string for ULWRF
From: John Halley Gotway
Time: Mon Jun 24 11:58:07 2019
Hi Jeff,
Tina copied me on this message, and I turned it into a ticket through
for met-help. In the future, feel free to write met_help at ucar.edu
with these sorts of questions.
I see that you're running plot_data_plane and getting multiple matches
for the field you requested. Tina is right, you can always request an
explicit record number like this:
'name="ULWRF"; level="R500";'
But that's not a good idea. There's no guarantee that a record #500
today will be in the same spot tomorrow. Instead, we just need to add
more info to the request for data. Record numbers 500 and 502 are
both for ULWRF and both have a level value of 0, but are probably for
different level types. Just specify the "GRIB_lvl_typ" value you want
(take a look in /usr/local/met-8.0/share/met/config/README and search
for GRIB_lvl_typ to see all of the additional filtering options).
Perhaps you want level type 113
(https://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html)
'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
Give that a shot and let me know if you have questions.
Thanks,
John
------------------------------------------------
Subject: field string for ULWRF
From: Jeffrey Hancock
Time: Mon Jun 24 13:46:22 2019
Thanks John!
Using level="R500" works for me, thank you. While not ideal, I think
it
will do for my purposes. I did try your other suggestion, but got the
following warning and error:
/usr/local/met-8.0/bin/plot_data_plane
/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027
/dev/null 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;' -plot_range
120.0
320.0
WARNING: MetGrib2DataFile::data_plane() - No matching record found for
'ULWRF/L0'
ERROR : plot_data_plane -> trouble getting field "name="ULWRF";
level="L0"; GRIB_lvl_typ=113;" from file
"/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027"
I also tried the same, but with 114 (long wave instead of short), and
212
(ULWRF), but those didn't work either.
Thanks again!
Jeff
On Mon, Jun 24, 2019 at 11:58 AM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi Jeff,
>
> Tina copied me on this message, and I turned it into a ticket
through for
> met-help. In the future, feel free to write met_help at ucar.edu with
these
> sorts of questions.
>
> I see that you're running plot_data_plane and getting multiple
matches for
> the field you requested. Tina is right, you can always request an
explicit
> record number like this:
> 'name="ULWRF"; level="R500";'
>
> But that's not a good idea. There's no guarantee that a record #500
today
> will be in the same spot tomorrow. Instead, we just need to add
more info
> to the request for data. Record numbers 500 and 502 are both for
ULWRF and
> both have a level value of 0, but are probably for different level
types.
> Just specify the "GRIB_lvl_typ" value you want (take a look in
> /usr/local/met-8.0/share/met/config/README and search for
GRIB_lvl_typ to
> see all of the additional filtering options).
>
> Perhaps you want level type 113 (
> https://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html)
>
> 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
>
> Give that a shot and let me know if you have questions.
>
> Thanks,
> John
>
>
>
--
Jeff Hancock
NCAR / RAL / AAP
Software Engineer / Programmer II
303-497-2896
FL2-1019
------------------------------------------------
Subject: field string for ULWRF
From: John Halley Gotway
Time: Mon Jun 24 13:58:51 2019
Jeff,
If you'd like to post a sample data file somewhere, I could go take a
look
and figure it out. You could post it to the RAL anonymous ftp site (
https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk)
or just put it on scratch somewhere.
John
On Mon, Jun 24, 2019 at 1:46 PM Jeffrey Hancock via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90787 >
>
> Thanks John!
>
> Using level="R500" works for me, thank you. While not ideal, I
think it
> will do for my purposes. I did try your other suggestion, but got
the
> following warning and error:
>
> /usr/local/met-8.0/bin/plot_data_plane
>
>
/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027
> /dev/null 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;' -plot_range
120.0
> 320.0
> WARNING: MetGrib2DataFile::data_plane() - No matching record found
for
> 'ULWRF/L0'
> ERROR : plot_data_plane -> trouble getting field "name="ULWRF";
> level="L0"; GRIB_lvl_typ=113;" from file
>
>
"/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027"
>
> I also tried the same, but with 114 (long wave instead of short),
and 212
> (ULWRF), but those didn't work either.
>
> Thanks again!
>
> Jeff
>
> On Mon, Jun 24, 2019 at 11:58 AM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hi Jeff,
> >
> > Tina copied me on this message, and I turned it into a ticket
through for
> > met-help. In the future, feel free to write met_help at ucar.edu
with
> these
> > sorts of questions.
> >
> > I see that you're running plot_data_plane and getting multiple
matches
> for
> > the field you requested. Tina is right, you can always request an
> explicit
> > record number like this:
> > 'name="ULWRF"; level="R500";'
> >
> > But that's not a good idea. There's no guarantee that a record
#500
> today
> > will be in the same spot tomorrow. Instead, we just need to add
more
> info
> > to the request for data. Record numbers 500 and 502 are both for
ULWRF
> and
> > both have a level value of 0, but are probably for different level
types.
> > Just specify the "GRIB_lvl_typ" value you want (take a look in
> > /usr/local/met-8.0/share/met/config/README and search for
GRIB_lvl_typ to
> > see all of the additional filtering options).
> >
> > Perhaps you want level type 113 (
> > https://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html)
> >
> > 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
> >
> > Give that a shot and let me know if you have questions.
> >
> > Thanks,
> > John
> >
> >
> >
>
> --
> Jeff Hancock
> NCAR / RAL / AAP
> Software Engineer / Programmer II
> 303-497-2896
> FL2-1019
>
>
------------------------------------------------
Subject: field string for ULWRF
From: Jeffrey Hancock
Time: Mon Jun 24 14:41:55 2019
Thanks for the offer, John! I have placed a sample file at:
/scratch/jhancock/forJohn/gfs.t12z.pgrb2.0p50.f024
Jeff
On Mon, Jun 24, 2019 at 1:58 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Jeff,
>
> If you'd like to post a sample data file somewhere, I could go take
a look
> and figure it out. You could post it to the RAL anonymous ftp site
(
>
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> )
> or just put it on scratch somewhere.
>
> John
>
> On Mon, Jun 24, 2019 at 1:46 PM Jeffrey Hancock via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90787 >
> >
> > Thanks John!
> >
> > Using level="R500" works for me, thank you. While not ideal, I
think it
> > will do for my purposes. I did try your other suggestion, but got
the
> > following warning and error:
> >
> > /usr/local/met-8.0/bin/plot_data_plane
> >
> >
>
/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027
> > /dev/null 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
-plot_range 120.0
> > 320.0
> > WARNING: MetGrib2DataFile::data_plane() - No matching record found
for
> > 'ULWRF/L0'
> > ERROR : plot_data_plane -> trouble getting field "name="ULWRF";
> > level="L0"; GRIB_lvl_typ=113;" from file
> >
> >
>
"/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027"
> >
> > I also tried the same, but with 114 (long wave instead of short),
and 212
> > (ULWRF), but those didn't work either.
> >
> > Thanks again!
> >
> > Jeff
> >
> > On Mon, Jun 24, 2019 at 11:58 AM John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Hi Jeff,
> > >
> > > Tina copied me on this message, and I turned it into a ticket
through
> for
> > > met-help. In the future, feel free to write met_help at ucar.edu
with
> > these
> > > sorts of questions.
> > >
> > > I see that you're running plot_data_plane and getting multiple
matches
> > for
> > > the field you requested. Tina is right, you can always request
an
> > explicit
> > > record number like this:
> > > 'name="ULWRF"; level="R500";'
> > >
> > > But that's not a good idea. There's no guarantee that a record
#500
> > today
> > > will be in the same spot tomorrow. Instead, we just need to add
more
> > info
> > > to the request for data. Record numbers 500 and 502 are both
for ULWRF
> > and
> > > both have a level value of 0, but are probably for different
level
> types.
> > > Just specify the "GRIB_lvl_typ" value you want (take a look in
> > > /usr/local/met-8.0/share/met/config/README and search for
GRIB_lvl_typ
> to
> > > see all of the additional filtering options).
> > >
> > > Perhaps you want level type 113 (
> > > https://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html)
> > >
> > > 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
> > >
> > > Give that a shot and let me know if you have questions.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> >
> > --
> > Jeff Hancock
> > NCAR / RAL / AAP
> > Software Engineer / Programmer II
> > 303-497-2896
> > FL2-1019
> >
> >
>
>
--
Jeff Hancock
NCAR / RAL / AAP
Software Engineer / Programmer II
303-497-2896
FL2-1019
------------------------------------------------
Subject: field string for ULWRF
From: John Halley Gotway
Time: Mon Jun 24 16:14:31 2019
Jeff,
I see that you're using GRIB2 data. The link I sent you was for
GRIB1, not
GRIB2, and that's probably why the numbers didn't work. Here's the
relevant GRIB2 table:
https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-
5.shtml
And the top of the atmosphere is level type 8. We can also confirm
that
using wgrib2 and checking the 23rd byte of the 4th octet (as listed at
the
top of the GRIB2 table):
[johnhg at number5]% *wgrib2 -d 500 -get_byte 4 23 1
gfs.t12z.pgrb2.0p50.f024*
500:82030174:4-23=1
[johnhg at number5]%* wgrib2 -d 502 -get_byte 4 23 1
gfs.t12z.pgrb2.0p50.f024*
502:82308851:4-23=8
So records 500 and 502 have the GRIB level type set to 1 and 8,
respectively. Adding that filtering option does the trick:
*/usr/local/met-8.0/bin/plot_data_plane gfs.t12z.pgrb2.0p50.f024
ulwrf.ps
<http://ulwrf.ps> 'name="ULWRF"; level="L0"; GRIB_lvl_typ=8;' *
DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
'ULWRF/L0'
in GRIB2 record 502 field 1 of GRIB2 file 'gfs.t12z.pgrb2.0p50.f024'
And produces the attached plot.
Thanks,
John
On Mon, Jun 24, 2019 at 2:42 PM Jeffrey Hancock via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90787 >
>
> Thanks for the offer, John! I have placed a sample file at:
> /scratch/jhancock/forJohn/gfs.t12z.pgrb2.0p50.f024
>
> Jeff
>
> On Mon, Jun 24, 2019 at 1:58 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Jeff,
> >
> > If you'd like to post a sample data file somewhere, I could go
take a
> look
> > and figure it out. You could post it to the RAL anonymous ftp
site (
> >
> >
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> > )
> > or just put it on scratch somewhere.
> >
> > John
> >
> > On Mon, Jun 24, 2019 at 1:46 PM Jeffrey Hancock via RT <
> met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90787 >
> > >
> > > Thanks John!
> > >
> > > Using level="R500" works for me, thank you. While not ideal, I
think
> it
> > > will do for my purposes. I did try your other suggestion, but
got the
> > > following warning and error:
> > >
> > > /usr/local/met-8.0/bin/plot_data_plane
> > >
> > >
> >
>
/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027
> > > /dev/null 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
-plot_range
> 120.0
> > > 320.0
> > > WARNING: MetGrib2DataFile::data_plane() - No matching record
found for
> > > 'ULWRF/L0'
> > > ERROR : plot_data_plane -> trouble getting field "name="ULWRF";
> > > level="L0"; GRIB_lvl_typ=113;" from file
> > >
> > >
> >
>
"/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027"
> > >
> > > I also tried the same, but with 114 (long wave instead of
short), and
> 212
> > > (ULWRF), but those didn't work either.
> > >
> > > Thanks again!
> > >
> > > Jeff
> > >
> > > On Mon, Jun 24, 2019 at 11:58 AM John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Hi Jeff,
> > > >
> > > > Tina copied me on this message, and I turned it into a ticket
through
> > for
> > > > met-help. In the future, feel free to write met_help at ucar.edu
with
> > > these
> > > > sorts of questions.
> > > >
> > > > I see that you're running plot_data_plane and getting multiple
> matches
> > > for
> > > > the field you requested. Tina is right, you can always
request an
> > > explicit
> > > > record number like this:
> > > > 'name="ULWRF"; level="R500";'
> > > >
> > > > But that's not a good idea. There's no guarantee that a
record #500
> > > today
> > > > will be in the same spot tomorrow. Instead, we just need to
add more
> > > info
> > > > to the request for data. Record numbers 500 and 502 are both
for
> ULWRF
> > > and
> > > > both have a level value of 0, but are probably for different
level
> > types.
> > > > Just specify the "GRIB_lvl_typ" value you want (take a look in
> > > > /usr/local/met-8.0/share/met/config/README and search for
> GRIB_lvl_typ
> > to
> > > > see all of the additional filtering options).
> > > >
> > > > Perhaps you want level type 113 (
> > > > https://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html)
> > > >
> > > > 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
> > > >
> > > > Give that a shot and let me know if you have questions.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > >
> > >
> > > --
> > > Jeff Hancock
> > > NCAR / RAL / AAP
> > > Software Engineer / Programmer II
> > > 303-497-2896
> > > FL2-1019
> > >
> > >
> >
> >
>
> --
> Jeff Hancock
> NCAR / RAL / AAP
> Software Engineer / Programmer II
> 303-497-2896
> FL2-1019
>
>
------------------------------------------------
Subject: field string for ULWRF
From: Jeffrey Hancock
Time: Mon Jun 24 17:08:11 2019
Sweet! Indeed it does work (for me too). Thanks!
On Mon, Jun 24, 2019 at 4:15 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Jeff,
>
> I see that you're using GRIB2 data. The link I sent you was for
GRIB1, not
> GRIB2, and that's probably why the numbers didn't work. Here's the
> relevant GRIB2 table:
>
> https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-
5.shtml
> And the top of the atmosphere is level type 8. We can also confirm
that
> using wgrib2 and checking the 23rd byte of the 4th octet (as listed
at the
> top of the GRIB2 table):
>
> [johnhg at number5]% *wgrib2 -d 500 -get_byte 4 23 1
> gfs.t12z.pgrb2.0p50.f024*
> 500:82030174:4-23=1
> [johnhg at number5]%* wgrib2 -d 502 -get_byte 4 23 1
> gfs.t12z.pgrb2.0p50.f024*
> 502:82308851:4-23=8
>
> So records 500 and 502 have the GRIB level type set to 1 and 8,
> respectively. Adding that filtering option does the trick:
>
> */usr/local/met-8.0/bin/plot_data_plane gfs.t12z.pgrb2.0p50.f024
ulwrf.ps
> <http://ulwrf.ps> 'name="ULWRF"; level="L0"; GRIB_lvl_typ=8;' *
> DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
'ULWRF/L0'
> in GRIB2 record 502 field 1 of GRIB2 file 'gfs.t12z.pgrb2.0p50.f024'
>
> And produces the attached plot.
>
> Thanks,
> John
>
> On Mon, Jun 24, 2019 at 2:42 PM Jeffrey Hancock via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90787 >
> >
> > Thanks for the offer, John! I have placed a sample file at:
> > /scratch/jhancock/forJohn/gfs.t12z.pgrb2.0p50.f024
> >
> > Jeff
> >
> > On Mon, Jun 24, 2019 at 1:58 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Jeff,
> > >
> > > If you'd like to post a sample data file somewhere, I could go
take a
> > look
> > > and figure it out. You could post it to the RAL anonymous ftp
site (
> > >
> > >
> >
> https://dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk
> > > )
> > > or just put it on scratch somewhere.
> > >
> > > John
> > >
> > > On Mon, Jun 24, 2019 at 1:46 PM Jeffrey Hancock via RT <
> > met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90787
>
> > > >
> > > > Thanks John!
> > > >
> > > > Using level="R500" works for me, thank you. While not ideal,
I think
> > it
> > > > will do for my purposes. I did try your other suggestion, but
got
> the
> > > > following warning and error:
> > > >
> > > > /usr/local/met-8.0/bin/plot_data_plane
> > > >
> > > >
> > >
> >
>
/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027
> > > > /dev/null 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
-plot_range
> > 120.0
> > > > 320.0
> > > > WARNING: MetGrib2DataFile::data_plane() - No matching record
found
> for
> > > > 'ULWRF/L0'
> > > > ERROR : plot_data_plane -> trouble getting field
"name="ULWRF";
> > > > level="L0"; GRIB_lvl_typ=113;" from file
> > > >
> > > >
> > >
> >
>
"/d1/fieldData/EpochOps/raw/gfsPgrb2/gfs.20190620/12/gfs.t12z.pgrb2.0p50.f027"
> > > >
> > > > I also tried the same, but with 114 (long wave instead of
short), and
> > 212
> > > > (ULWRF), but those didn't work either.
> > > >
> > > > Thanks again!
> > > >
> > > > Jeff
> > > >
> > > > On Mon, Jun 24, 2019 at 11:58 AM John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > > Hi Jeff,
> > > > >
> > > > > Tina copied me on this message, and I turned it into a
ticket
> through
> > > for
> > > > > met-help. In the future, feel free to write
met_help at ucar.edu
> with
> > > > these
> > > > > sorts of questions.
> > > > >
> > > > > I see that you're running plot_data_plane and getting
multiple
> > matches
> > > > for
> > > > > the field you requested. Tina is right, you can always
request an
> > > > explicit
> > > > > record number like this:
> > > > > 'name="ULWRF"; level="R500";'
> > > > >
> > > > > But that's not a good idea. There's no guarantee that a
record
> #500
> > > > today
> > > > > will be in the same spot tomorrow. Instead, we just need to
add
> more
> > > > info
> > > > > to the request for data. Record numbers 500 and 502 are
both for
> > ULWRF
> > > > and
> > > > > both have a level value of 0, but are probably for different
level
> > > types.
> > > > > Just specify the "GRIB_lvl_typ" value you want (take a look
in
> > > > > /usr/local/met-8.0/share/met/config/README and search for
> > GRIB_lvl_typ
> > > to
> > > > > see all of the additional filtering options).
> > > > >
> > > > > Perhaps you want level type 113 (
> > > > > https://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html)
> > > > >
> > > > > 'name="ULWRF"; level="L0"; GRIB_lvl_typ=113;'
> > > > >
> > > > > Give that a shot and let me know if you have questions.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Jeff Hancock
> > > > NCAR / RAL / AAP
> > > > Software Engineer / Programmer II
> > > > 303-497-2896
> > > > FL2-1019
> > > >
> > > >
> > >
> > >
> >
> > --
> > Jeff Hancock
> > NCAR / RAL / AAP
> > Software Engineer / Programmer II
> > 303-497-2896
> > FL2-1019
> >
> >
>
>
--
Jeff Hancock
NCAR / RAL / AAP
Software Engineer / Programmer II
303-497-2896
FL2-1019
------------------------------------------------
More information about the Met_help
mailing list