[Met_help] [rt.rap.ucar.edu #90740] History for Error when running MET using METplus
David Fillmore via RT
met_help at ucar.edu
Tue Jul 9 15:22:55 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi, there,
I'm getting this weird error now when I run MET (though apparently only for
the air quality instance) that gives me this error.
ERROR :
ERROR : PointStatVxOpt::set_vx_pd() -> "message_type_group_map" must
contain an entry for "LANDSF".
ERROR :
I'm not sure why this is becoming an error for this particular execution
and not for others. FWIW, I'm using the command:
/meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py -c
/meso/save/Perry.Shafran/METplus-2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
-c
/meso/save/Perry.Shafran/METplus-2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
-c /meso/save/Perry.Shafran/METplus-2.1/parm/use_cases/perry/pb2nc.conf_aq
-c
/meso/save/Perry.Shafran/METplus-2.1/parm/use_cases/perry/point_stat.conf_aq
-c /meso/save/Perry.Shafran/METplus-2.1/parm/use_cases/perry/shared.conf
-c /meso/save/Perry.Shafran/METplus-2.1/parm/use_cases/perry/system.conf
The "LANDSF" entry seems to come from Julie's default file, but for some
reason I'm having issues. What am I missing here?
Thanks!
Perry
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Error when running MET using METplus
From: David Fillmore
Time: Fri Jun 21 10:11:28 2019
Hi Perry -
Can you attach your point_stat.conf_aq file?
The message_type_group_map needs to have an entry for key = "LANDSF"
in the
user config file as well.
thanks,
David
On Fri, Jun 21, 2019 at 9:25 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Fri Jun 21 09:25:04 2019: Request 90740 was acted upon.
> Transaction: Ticket created by perry.shafran at noaa.gov
> Queue: met_help
> Subject: Error when running MET using METplus
> Owner: Nobody
> Requestors: perry.shafran at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90740 >
>
>
> Hi, there,
>
> I'm getting this weird error now when I run MET (though apparently
only for
> the air quality instance) that gives me this error.
>
> ERROR :
> ERROR : PointStatVxOpt::set_vx_pd() -> "message_type_group_map"
must
> contain an entry for "LANDSF".
> ERROR :
>
> I'm not sure why this is becoming an error for this particular
execution
> and not for others. FWIW, I'm using the command:
>
> /meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py -c
>
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> -c
>
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> -c /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/pb2nc.conf_aq
> -c
>
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/point_stat.conf_aq
> -c /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/shared.conf
> -c /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/system.conf
>
> The "LANDSF" entry seems to come from Julie's default file, but for
some
> reason I'm having issues. What am I missing here?
>
> Thanks!
>
> Perry
>
>
------------------------------------------------
Subject: Error when running MET using METplus
From: perry.shafran at noaa.gov
Time: Fri Jun 21 10:23:49 2019
Hi, David,
Here are the complete contents. Other executions of point_stat work
without any mapping for LANDSF in the config file.
[dir]
# Forecast and Obs file input directories (netCDF files)
FCST_POINT_STAT_INPUT_DIR = /gpfs/hps/nco/ops/com/aqm/prod
OBS_POINT_STAT_INPUT_DIR = {OUTPUT_BASE}/aqm/conus_sfc
# Final output directory for point_stat output
POINT_STAT_OUTPUT_DIR = {OUTPUT_BASE}/aqm/stat
[config]
# MET configuration file
POINT_STAT_CONFIG_FILE ={PARM_BASE}/met_config/PointStatConfig_AIRNOW
# Forecast hour start, end, and interval. Interval is the forecast
interval
in
# hours.
LEAD_SEQ = begin_end_incr(0,48,1)
# Model/fcst and obs name, e.g. GFS, NAM, GDAS, etc.
MODEL_NAME = aqm
OBS_NAME = nam
# Regrid to specified grid. Indicate NONE if no regridding, or the
grid id
# (e.g. G212)
POINT_STAT_REGRID_TO_GRID = G104
# Verification Masking regions
# Indicate which grid and polygon masking region, if applicable
POINT_STAT_GRID = FULL
# List of full path to poly masking files. NOTE: Only short lists of
poly
# files work (those that fit on one line), a long list will result in
an
# environment variable that is too long, resulting in an error. For
long
# lists of poly masking files (i.e. all the mask files in the
NCEP_mask
# directory), define these in the MET point_stat configuration file.
POINT_STAT_POLY =
POINT_STAT_STATION_ID =
# Message types, if all message types are to be returned, leave this
empty,
# otherwise indicate the message types of interest.
POINT_STAT_MESSAGE_TYPE = ONLYSF
# Variables and levels as specified in the field dictionary of the MET
# point_stat configuration file. Specify as FCST_VARn_NAME,
FCST_VARn_LEVELS,
# (optional) FCST_VARn_OPTION
FCST_VAR1_NAME = TMP
FCST_VAR1_LEVELS = Z2
FCST_VAR2_NAME = RH
FCST_VAR2_LEVELS = Z2
FCST_VAR3_NAME = DPT
FCST_VAR3_LEVELS = Z2
FCST_VAR4_NAME = UGRD
FCST_VAR4_LEVELS = Z10
FCST_VAR5_NAME = VGRD
FCST_VAR5_LEVELS = Z10
FCST_VAR6_NAME = TCDC
FCST_VAR6_LEVELS = L0
FCST_VAR6_OPTIONS = GRIB_lvl_typ = 200
FCST_VAR7_NAME = PRMSL
FCST_VAR7_LEVELS = Z0
# Regular expressions for files relevant to this use case. Use
parentheses
# around any date, cycle, lead (forecast) and offset time.
#FCST_INPUT_DIR_REGEX = .*nam.([0-9]{8})
#FCST_INPUT_DIR_REGEX =
[filename_templates]
# NOTE: These are EXAMPLE FILENAME TEMPLATES
#FCST_INPUT_FILE_TMPL =
nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm{offset?fmt=%H}.grib2
#FCST_INPUT_FILE_TMPL =
nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm00.grib2
#FCST_INPUT_FILE_TMPL =
rap.t{cycle?fmt=%H}z.awp130pgrbf{lead?fmt=%H}.grib2
#FCST_INPUT_FILE_TMPL =
.*nam.{init?fmt=%Y%m%d}/nam.t{cycle?fmt=%HH}z.awphys{lead?fmt=%HH}.tm{offset?fmt=%HH}.grib2
FCST_POINT_STAT_INPUT_TEMPLATE =
aqm.{init?fmt=%Y%m%d}/aqm.t{init?fmt=%2H}z.awpozcon.f{lead?fmt=%2H}.148.grib2
#OBS_INPUT_FILE_TMPL =
prepbufr.nam.{init?fmt=%Y%m%d}.t{cycle?fmt=%HH}z.tm
{offset?fmt=%HH}.nc
#OBS_INPUT_FILE_TMPL = prepbufr.nam.{valid?fmt=%Y%m%d%H}.nc
OBS_POINT_STAT_INPUT_TEMPLATE = prepbufr.aqm.{valid?fmt=%Y%m%d%H}.nc
POINT_STAT_OUTPUT_TEMPLATE = aqm
On Fri, Jun 21, 2019 at 12:11 PM David Fillmore via RT
<met_help at ucar.edu>
wrote:
> Hi Perry -
> Can you attach your point_stat.conf_aq file?
> The message_type_group_map needs to have an entry for key = "LANDSF"
in the
> user config file as well.
> thanks,
> David
>
> On Fri, Jun 21, 2019 at 9:25 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jun 21 09:25:04 2019: Request 90740 was acted upon.
> > Transaction: Ticket created by perry.shafran at noaa.gov
> > Queue: met_help
> > Subject: Error when running MET using METplus
> > Owner: Nobody
> > Requestors: perry.shafran at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90740 >
> >
> >
> > Hi, there,
> >
> > I'm getting this weird error now when I run MET (though apparently
only
> for
> > the air quality instance) that gives me this error.
> >
> > ERROR :
> > ERROR : PointStatVxOpt::set_vx_pd() -> "message_type_group_map"
must
> > contain an entry for "LANDSF".
> > ERROR :
> >
> > I'm not sure why this is becoming an error for this particular
execution
> > and not for others. FWIW, I'm using the command:
> >
> > /meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py -c
> >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > -c
> >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > -c
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/pb2nc.conf_aq
> > -c
> >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/point_stat.conf_aq
> > -c /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/shared.conf
> > -c /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/system.conf
> >
> > The "LANDSF" entry seems to come from Julie's default file, but
for some
> > reason I'm having issues. What am I missing here?
> >
> > Thanks!
> >
> > Perry
> >
> >
>
>
------------------------------------------------
Subject: Error when running MET using METplus
From: John Halley Gotway
Time: Fri Jun 21 14:17:36 2019
Perry and David,
Thought I'd jump in on this one.
One explanation for this error would be using a met-8.0 config to run
met-8.1 tools. Here's some background. We enhanced Point-Stat in
met-8.1
to support a new interpolation option named "GEOG_MATCH". This option
only
verifies land obs using land model points and water obs using water
model
points. And it also checks the height of the obs relative to the
model
topography.
So Point-Stat now needs to know what message types qualify as being
land vs
water. Previously we'd had these things hard-coded but in met-8.1, we
moved them to the config file in the "message_type_group_map".
In met-8.0:
message_type_group_map = [
{ key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET"; },
{ key = "ANYAIR"; val = "AIRCAR,AIRCFT"; },
{ key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
{ key = "ONLYSF"; val = "ADPSFC,SFCSHP"; }
];
In met-8.1:
message_type_group_map = [
{ key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET"; },
{ key = "ANYAIR"; val = "AIRCAR,AIRCFT"; },
{ key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
{ key = "ONLYSF"; val = "ADPSFC,SFCSHP"; },
{ key = "LANDSF"; val = "ADPSFC,MSONET"; },
{ key = "WATERSF"; val = "SFCSHP"; }
];
You see we added entries for LANDSF and WATERSF and these are included
in
the default config file.
Perhaps we failed to update the Point-Stat config files in METplus to
include these changes?
Thanks,
John
On Fri, Jun 21, 2019 at 10:24 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=90740 >
>
> Hi, David,
>
> Here are the complete contents. Other executions of point_stat work
> without any mapping for LANDSF in the config file.
>
> [dir]
>
> # Forecast and Obs file input directories (netCDF files)
> FCST_POINT_STAT_INPUT_DIR = /gpfs/hps/nco/ops/com/aqm/prod
> OBS_POINT_STAT_INPUT_DIR = {OUTPUT_BASE}/aqm/conus_sfc
>
> # Final output directory for point_stat output
> POINT_STAT_OUTPUT_DIR = {OUTPUT_BASE}/aqm/stat
>
> [config]
>
> # MET configuration file
> POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_AIRNOW
>
> # Forecast hour start, end, and interval. Interval is the forecast
interval
> in
> # hours.
> LEAD_SEQ = begin_end_incr(0,48,1)
>
> # Model/fcst and obs name, e.g. GFS, NAM, GDAS, etc.
> MODEL_NAME = aqm
> OBS_NAME = nam
>
> # Regrid to specified grid. Indicate NONE if no regridding, or the
grid id
> # (e.g. G212)
> POINT_STAT_REGRID_TO_GRID = G104
>
> # Verification Masking regions
> # Indicate which grid and polygon masking region, if applicable
> POINT_STAT_GRID = FULL
>
> # List of full path to poly masking files. NOTE: Only short lists
of poly
> # files work (those that fit on one line), a long list will result
in an
> # environment variable that is too long, resulting in an error. For
long
> # lists of poly masking files (i.e. all the mask files in the
NCEP_mask
> # directory), define these in the MET point_stat configuration file.
> POINT_STAT_POLY =
> POINT_STAT_STATION_ID =
>
> # Message types, if all message types are to be returned, leave this
empty,
> # otherwise indicate the message types of interest.
> POINT_STAT_MESSAGE_TYPE = ONLYSF
>
> # Variables and levels as specified in the field dictionary of the
MET
> # point_stat configuration file. Specify as FCST_VARn_NAME,
> FCST_VARn_LEVELS,
> # (optional) FCST_VARn_OPTION
> FCST_VAR1_NAME = TMP
> FCST_VAR1_LEVELS = Z2
>
> FCST_VAR2_NAME = RH
> FCST_VAR2_LEVELS = Z2
>
> FCST_VAR3_NAME = DPT
> FCST_VAR3_LEVELS = Z2
>
> FCST_VAR4_NAME = UGRD
> FCST_VAR4_LEVELS = Z10
>
> FCST_VAR5_NAME = VGRD
> FCST_VAR5_LEVELS = Z10
>
> FCST_VAR6_NAME = TCDC
> FCST_VAR6_LEVELS = L0
> FCST_VAR6_OPTIONS = GRIB_lvl_typ = 200
>
> FCST_VAR7_NAME = PRMSL
> FCST_VAR7_LEVELS = Z0
>
> # Regular expressions for files relevant to this use case. Use
parentheses
> # around any date, cycle, lead (forecast) and offset time.
> #FCST_INPUT_DIR_REGEX = .*nam.([0-9]{8})
> #FCST_INPUT_DIR_REGEX =
>
> [filename_templates]
>
> # NOTE: These are EXAMPLE FILENAME TEMPLATES
> #FCST_INPUT_FILE_TMPL =
> nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm{offset?fmt=%H}.grib2
> #FCST_INPUT_FILE_TMPL =
nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm00.grib2
> #FCST_INPUT_FILE_TMPL =
rap.t{cycle?fmt=%H}z.awp130pgrbf{lead?fmt=%H}.grib2
> #FCST_INPUT_FILE_TMPL =
>
>
.*nam.{init?fmt=%Y%m%d}/nam.t{cycle?fmt=%HH}z.awphys{lead?fmt=%HH}.tm{offset?fmt=%HH}.grib2
> FCST_POINT_STAT_INPUT_TEMPLATE =
>
>
aqm.{init?fmt=%Y%m%d}/aqm.t{init?fmt=%2H}z.awpozcon.f{lead?fmt=%2H}.148.grib2
> #OBS_INPUT_FILE_TMPL =
prepbufr.nam.{init?fmt=%Y%m%d}.t{cycle?fmt=%HH}z.tm
> {offset?fmt=%HH}.nc
> #OBS_INPUT_FILE_TMPL = prepbufr.nam.{valid?fmt=%Y%m%d%H}.nc
> OBS_POINT_STAT_INPUT_TEMPLATE = prepbufr.aqm.{valid?fmt=%Y%m%d%H}.nc
> POINT_STAT_OUTPUT_TEMPLATE = aqm
>
> On Fri, Jun 21, 2019 at 12:11 PM David Fillmore via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Perry -
> > Can you attach your point_stat.conf_aq file?
> > The message_type_group_map needs to have an entry for key =
"LANDSF" in
> the
> > user config file as well.
> > thanks,
> > David
> >
> > On Fri, Jun 21, 2019 at 9:25 AM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Jun 21 09:25:04 2019: Request 90740 was acted upon.
> > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > Queue: met_help
> > > Subject: Error when running MET using METplus
> > > Owner: Nobody
> > > Requestors: perry.shafran at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90740
> >
> > >
> > >
> > > Hi, there,
> > >
> > > I'm getting this weird error now when I run MET (though
apparently only
> > for
> > > the air quality instance) that gives me this error.
> > >
> > > ERROR :
> > > ERROR : PointStatVxOpt::set_vx_pd() -> "message_type_group_map"
must
> > > contain an entry for "LANDSF".
> > > ERROR :
> > >
> > > I'm not sure why this is becoming an error for this particular
> execution
> > > and not for others. FWIW, I'm using the command:
> > >
> > > /meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py -c
> > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > -c
> > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > -c
> > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/pb2nc.conf_aq
> > > -c
> > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/point_stat.conf_aq
> > > -c
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/shared.conf
> > > -c
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/system.conf
> > >
> > > The "LANDSF" entry seems to come from Julie's default file, but
for
> some
> > > reason I'm having issues. What am I missing here?
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Error when running MET using METplus
From: perry.shafran at noaa.gov
Time: Fri Jun 21 14:20:21 2019
Oh, so all I have to do is include the WATERSF and LANDSF line in my
point_stat conf file?
If that's the case, why is another execution of point_stat working
without
these lines, using 8.1?
Perry
On Fri, Jun 21, 2019 at 4:17 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Perry and David,
>
> Thought I'd jump in on this one.
>
> One explanation for this error would be using a met-8.0 config to
run
> met-8.1 tools. Here's some background. We enhanced Point-Stat in
met-8.1
> to support a new interpolation option named "GEOG_MATCH". This
option only
> verifies land obs using land model points and water obs using water
model
> points. And it also checks the height of the obs relative to the
model
> topography.
>
> So Point-Stat now needs to know what message types qualify as being
land vs
> water. Previously we'd had these things hard-coded but in met-8.1,
we
> moved them to the config file in the "message_type_group_map".
>
> In met-8.0:
> message_type_group_map = [
> { key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET"; },
> { key = "ANYAIR"; val = "AIRCAR,AIRCFT"; },
> { key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
> { key = "ONLYSF"; val = "ADPSFC,SFCSHP"; }
> ];
>
> In met-8.1:
> message_type_group_map = [
> { key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET"; },
> { key = "ANYAIR"; val = "AIRCAR,AIRCFT"; },
> { key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
> { key = "ONLYSF"; val = "ADPSFC,SFCSHP"; },
> { key = "LANDSF"; val = "ADPSFC,MSONET"; },
> { key = "WATERSF"; val = "SFCSHP"; }
> ];
>
> You see we added entries for LANDSF and WATERSF and these are
included in
> the default config file.
>
> Perhaps we failed to update the Point-Stat config files in METplus
to
> include these changes?
>
> Thanks,
> John
>
> On Fri, Jun 21, 2019 at 10:24 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=90740 >
> >
> > Hi, David,
> >
> > Here are the complete contents. Other executions of point_stat
work
> > without any mapping for LANDSF in the config file.
> >
> > [dir]
> >
> > # Forecast and Obs file input directories (netCDF files)
> > FCST_POINT_STAT_INPUT_DIR = /gpfs/hps/nco/ops/com/aqm/prod
> > OBS_POINT_STAT_INPUT_DIR = {OUTPUT_BASE}/aqm/conus_sfc
> >
> > # Final output directory for point_stat output
> > POINT_STAT_OUTPUT_DIR = {OUTPUT_BASE}/aqm/stat
> >
> > [config]
> >
> > # MET configuration file
> > POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_AIRNOW
> >
> > # Forecast hour start, end, and interval. Interval is the forecast
> interval
> > in
> > # hours.
> > LEAD_SEQ = begin_end_incr(0,48,1)
> >
> > # Model/fcst and obs name, e.g. GFS, NAM, GDAS, etc.
> > MODEL_NAME = aqm
> > OBS_NAME = nam
> >
> > # Regrid to specified grid. Indicate NONE if no regridding, or
the grid
> id
> > # (e.g. G212)
> > POINT_STAT_REGRID_TO_GRID = G104
> >
> > # Verification Masking regions
> > # Indicate which grid and polygon masking region, if applicable
> > POINT_STAT_GRID = FULL
> >
> > # List of full path to poly masking files. NOTE: Only short lists
of
> poly
> > # files work (those that fit on one line), a long list will result
in an
> > # environment variable that is too long, resulting in an error.
For long
> > # lists of poly masking files (i.e. all the mask files in the
NCEP_mask
> > # directory), define these in the MET point_stat configuration
file.
> > POINT_STAT_POLY =
> > POINT_STAT_STATION_ID =
> >
> > # Message types, if all message types are to be returned, leave
this
> empty,
> > # otherwise indicate the message types of interest.
> > POINT_STAT_MESSAGE_TYPE = ONLYSF
> >
> > # Variables and levels as specified in the field dictionary of the
MET
> > # point_stat configuration file. Specify as FCST_VARn_NAME,
> > FCST_VARn_LEVELS,
> > # (optional) FCST_VARn_OPTION
> > FCST_VAR1_NAME = TMP
> > FCST_VAR1_LEVELS = Z2
> >
> > FCST_VAR2_NAME = RH
> > FCST_VAR2_LEVELS = Z2
> >
> > FCST_VAR3_NAME = DPT
> > FCST_VAR3_LEVELS = Z2
> >
> > FCST_VAR4_NAME = UGRD
> > FCST_VAR4_LEVELS = Z10
> >
> > FCST_VAR5_NAME = VGRD
> > FCST_VAR5_LEVELS = Z10
> >
> > FCST_VAR6_NAME = TCDC
> > FCST_VAR6_LEVELS = L0
> > FCST_VAR6_OPTIONS = GRIB_lvl_typ = 200
> >
> > FCST_VAR7_NAME = PRMSL
> > FCST_VAR7_LEVELS = Z0
> >
> > # Regular expressions for files relevant to this use case. Use
> parentheses
> > # around any date, cycle, lead (forecast) and offset time.
> > #FCST_INPUT_DIR_REGEX = .*nam.([0-9]{8})
> > #FCST_INPUT_DIR_REGEX =
> >
> > [filename_templates]
> >
> > # NOTE: These are EXAMPLE FILENAME TEMPLATES
> > #FCST_INPUT_FILE_TMPL =
> > nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm{offset?fmt=%H}.grib2
> > #FCST_INPUT_FILE_TMPL =
> nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm00.grib2
> > #FCST_INPUT_FILE_TMPL =
> rap.t{cycle?fmt=%H}z.awp130pgrbf{lead?fmt=%H}.grib2
> > #FCST_INPUT_FILE_TMPL =
> >
> >
>
.*nam.{init?fmt=%Y%m%d}/nam.t{cycle?fmt=%HH}z.awphys{lead?fmt=%HH}.tm{offset?fmt=%HH}.grib2
> > FCST_POINT_STAT_INPUT_TEMPLATE =
> >
> >
>
aqm.{init?fmt=%Y%m%d}/aqm.t{init?fmt=%2H}z.awpozcon.f{lead?fmt=%2H}.148.grib2
> > #OBS_INPUT_FILE_TMPL =
prepbufr.nam.{init?fmt=%Y%m%d}.t{cycle?fmt=%HH}
> z.tm
> > {offset?fmt=%HH}.nc
> > #OBS_INPUT_FILE_TMPL = prepbufr.nam.{valid?fmt=%Y%m%d%H}.nc
> > OBS_POINT_STAT_INPUT_TEMPLATE =
prepbufr.aqm.{valid?fmt=%Y%m%d%H}.nc
> > POINT_STAT_OUTPUT_TEMPLATE = aqm
> >
> > On Fri, Jun 21, 2019 at 12:11 PM David Fillmore via RT <
> met_help at ucar.edu>
> > wrote:
> >
> > > Hi Perry -
> > > Can you attach your point_stat.conf_aq file?
> > > The message_type_group_map needs to have an entry for key =
"LANDSF" in
> > the
> > > user config file as well.
> > > thanks,
> > > David
> > >
> > > On Fri, Jun 21, 2019 at 9:25 AM perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Jun 21 09:25:04 2019: Request 90740 was acted upon.
> > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > Queue: met_help
> > > > Subject: Error when running MET using METplus
> > > > Owner: Nobody
> > > > Requestors: perry.shafran at noaa.gov
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90740
> > >
> > > >
> > > >
> > > > Hi, there,
> > > >
> > > > I'm getting this weird error now when I run MET (though
apparently
> only
> > > for
> > > > the air quality instance) that gives me this error.
> > > >
> > > > ERROR :
> > > > ERROR : PointStatVxOpt::set_vx_pd() ->
"message_type_group_map" must
> > > > contain an entry for "LANDSF".
> > > > ERROR :
> > > >
> > > > I'm not sure why this is becoming an error for this particular
> > execution
> > > > and not for others. FWIW, I'm using the command:
> > > >
> > > > /meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py -c
> > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > > -c
> > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > > -c
> > > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/pb2nc.conf_aq
> > > > -c
> > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/point_stat.conf_aq
> > > > -c
> > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/shared.conf
> > > > -c
> > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/system.conf
> > > >
> > > > The "LANDSF" entry seems to come from Julie's default file,
but for
> > some
> > > > reason I'm having issues. What am I missing here?
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Error when running MET using METplus
From: John Halley Gotway
Time: Fri Jun 21 14:34:37 2019
Perry,
The LANDSF and WATERSF entries are missing from the PointStatConfig
file
itself, not the METplus conf file. This is basically a bug that we
failed
to update those PointStat config files in the METplus repo.
So I created this GitHub issue:
https://github.com/NCAR/METplus/issues/248
Just take a look in this file:
POINT_STAT_CONFIG_FILE ={PARM_BASE}/met_config/PointStatConfig_AIRNOW
If LANDSF and WATERSF are missing from message_type_group_map, please
try
adding them.
But I have no idea why one run would work and another would not?
John
On Fri, Jun 21, 2019 at 2:20 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=90740 >
>
> Oh, so all I have to do is include the WATERSF and LANDSF line in my
> point_stat conf file?
>
> If that's the case, why is another execution of point_stat working
without
> these lines, using 8.1?
>
> Perry
>
> On Fri, Jun 21, 2019 at 4:17 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Perry and David,
> >
> > Thought I'd jump in on this one.
> >
> > One explanation for this error would be using a met-8.0 config to
run
> > met-8.1 tools. Here's some background. We enhanced Point-Stat in
> met-8.1
> > to support a new interpolation option named "GEOG_MATCH". This
option
> only
> > verifies land obs using land model points and water obs using
water model
> > points. And it also checks the height of the obs relative to the
model
> > topography.
> >
> > So Point-Stat now needs to know what message types qualify as
being land
> vs
> > water. Previously we'd had these things hard-coded but in met-
8.1, we
> > moved them to the config file in the "message_type_group_map".
> >
> > In met-8.0:
> > message_type_group_map = [
> > { key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET";
},
> > { key = "ANYAIR"; val = "AIRCAR,AIRCFT";
},
> > { key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET";
},
> > { key = "ONLYSF"; val = "ADPSFC,SFCSHP";
}
> > ];
> >
> > In met-8.1:
> > message_type_group_map = [
> > { key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET";
},
> > { key = "ANYAIR"; val = "AIRCAR,AIRCFT";
},
> > { key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET";
},
> > { key = "ONLYSF"; val = "ADPSFC,SFCSHP";
},
> > { key = "LANDSF"; val = "ADPSFC,MSONET";
},
> > { key = "WATERSF"; val = "SFCSHP";
}
> > ];
> >
> > You see we added entries for LANDSF and WATERSF and these are
included in
> > the default config file.
> >
> > Perhaps we failed to update the Point-Stat config files in METplus
to
> > include these changes?
> >
> > Thanks,
> > John
> >
> > On Fri, Jun 21, 2019 at 10:24 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=90740 >
> > >
> > > Hi, David,
> > >
> > > Here are the complete contents. Other executions of point_stat
work
> > > without any mapping for LANDSF in the config file.
> > >
> > > [dir]
> > >
> > > # Forecast and Obs file input directories (netCDF files)
> > > FCST_POINT_STAT_INPUT_DIR = /gpfs/hps/nco/ops/com/aqm/prod
> > > OBS_POINT_STAT_INPUT_DIR = {OUTPUT_BASE}/aqm/conus_sfc
> > >
> > > # Final output directory for point_stat output
> > > POINT_STAT_OUTPUT_DIR = {OUTPUT_BASE}/aqm/stat
> > >
> > > [config]
> > >
> > > # MET configuration file
> > > POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_AIRNOW
> > >
> > > # Forecast hour start, end, and interval. Interval is the
forecast
> > interval
> > > in
> > > # hours.
> > > LEAD_SEQ = begin_end_incr(0,48,1)
> > >
> > > # Model/fcst and obs name, e.g. GFS, NAM, GDAS, etc.
> > > MODEL_NAME = aqm
> > > OBS_NAME = nam
> > >
> > > # Regrid to specified grid. Indicate NONE if no regridding, or
the
> grid
> > id
> > > # (e.g. G212)
> > > POINT_STAT_REGRID_TO_GRID = G104
> > >
> > > # Verification Masking regions
> > > # Indicate which grid and polygon masking region, if applicable
> > > POINT_STAT_GRID = FULL
> > >
> > > # List of full path to poly masking files. NOTE: Only short
lists of
> > poly
> > > # files work (those that fit on one line), a long list will
result in
> an
> > > # environment variable that is too long, resulting in an error.
For
> long
> > > # lists of poly masking files (i.e. all the mask files in the
NCEP_mask
> > > # directory), define these in the MET point_stat configuration
file.
> > > POINT_STAT_POLY =
> > > POINT_STAT_STATION_ID =
> > >
> > > # Message types, if all message types are to be returned, leave
this
> > empty,
> > > # otherwise indicate the message types of interest.
> > > POINT_STAT_MESSAGE_TYPE = ONLYSF
> > >
> > > # Variables and levels as specified in the field dictionary of
the MET
> > > # point_stat configuration file. Specify as FCST_VARn_NAME,
> > > FCST_VARn_LEVELS,
> > > # (optional) FCST_VARn_OPTION
> > > FCST_VAR1_NAME = TMP
> > > FCST_VAR1_LEVELS = Z2
> > >
> > > FCST_VAR2_NAME = RH
> > > FCST_VAR2_LEVELS = Z2
> > >
> > > FCST_VAR3_NAME = DPT
> > > FCST_VAR3_LEVELS = Z2
> > >
> > > FCST_VAR4_NAME = UGRD
> > > FCST_VAR4_LEVELS = Z10
> > >
> > > FCST_VAR5_NAME = VGRD
> > > FCST_VAR5_LEVELS = Z10
> > >
> > > FCST_VAR6_NAME = TCDC
> > > FCST_VAR6_LEVELS = L0
> > > FCST_VAR6_OPTIONS = GRIB_lvl_typ = 200
> > >
> > > FCST_VAR7_NAME = PRMSL
> > > FCST_VAR7_LEVELS = Z0
> > >
> > > # Regular expressions for files relevant to this use case. Use
> > parentheses
> > > # around any date, cycle, lead (forecast) and offset time.
> > > #FCST_INPUT_DIR_REGEX = .*nam.([0-9]{8})
> > > #FCST_INPUT_DIR_REGEX =
> > >
> > > [filename_templates]
> > >
> > > # NOTE: These are EXAMPLE FILENAME TEMPLATES
> > > #FCST_INPUT_FILE_TMPL =
> > > nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm{offset?fmt=%H}.grib2
> > > #FCST_INPUT_FILE_TMPL =
> > nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm00.grib2
> > > #FCST_INPUT_FILE_TMPL =
> > rap.t{cycle?fmt=%H}z.awp130pgrbf{lead?fmt=%H}.grib2
> > > #FCST_INPUT_FILE_TMPL =
> > >
> > >
> >
>
.*nam.{init?fmt=%Y%m%d}/nam.t{cycle?fmt=%HH}z.awphys{lead?fmt=%HH}.tm{offset?fmt=%HH}.grib2
> > > FCST_POINT_STAT_INPUT_TEMPLATE =
> > >
> > >
> >
>
aqm.{init?fmt=%Y%m%d}/aqm.t{init?fmt=%2H}z.awpozcon.f{lead?fmt=%2H}.148.grib2
> > > #OBS_INPUT_FILE_TMPL =
prepbufr.nam.{init?fmt=%Y%m%d}.t{cycle?fmt=%HH}
> > z.tm
> > > {offset?fmt=%HH}.nc
> > > #OBS_INPUT_FILE_TMPL = prepbufr.nam.{valid?fmt=%Y%m%d%H}.nc
> > > OBS_POINT_STAT_INPUT_TEMPLATE =
prepbufr.aqm.{valid?fmt=%Y%m%d%H}.nc
> > > POINT_STAT_OUTPUT_TEMPLATE = aqm
> > >
> > > On Fri, Jun 21, 2019 at 12:11 PM David Fillmore via RT <
> > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Perry -
> > > > Can you attach your point_stat.conf_aq file?
> > > > The message_type_group_map needs to have an entry for key =
"LANDSF"
> in
> > > the
> > > > user config file as well.
> > > > thanks,
> > > > David
> > > >
> > > > On Fri, Jun 21, 2019 at 9:25 AM perry.shafran at noaa.gov via RT
<
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Fri Jun 21 09:25:04 2019: Request 90740 was acted upon.
> > > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > Queue: met_help
> > > > > Subject: Error when running MET using METplus
> > > > > Owner: Nobody
> > > > > Requestors: perry.shafran at noaa.gov
> > > > > Status: new
> > > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90740
> > > >
> > > > >
> > > > >
> > > > > Hi, there,
> > > > >
> > > > > I'm getting this weird error now when I run MET (though
apparently
> > only
> > > > for
> > > > > the air quality instance) that gives me this error.
> > > > >
> > > > > ERROR :
> > > > > ERROR : PointStatVxOpt::set_vx_pd() ->
"message_type_group_map"
> must
> > > > > contain an entry for "LANDSF".
> > > > > ERROR :
> > > > >
> > > > > I'm not sure why this is becoming an error for this
particular
> > > execution
> > > > > and not for others. FWIW, I'm using the command:
> > > > >
> > > > > /meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py
-c
> > > > >
> > > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > > > -c
> > > > >
> > > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > > > -c
> > > >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/pb2nc.conf_aq
> > > > > -c
> > > > >
> > > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/point_stat.conf_aq
> > > > > -c
> > > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/shared.conf
> > > > > -c
> > > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/system.conf
> > > > >
> > > > > The "LANDSF" entry seems to come from Julie's default file,
but for
> > > some
> > > > > reason I'm having issues. What am I missing here?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Perry
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Error when running MET using METplus
From: perry.shafran at noaa.gov
Time: Fri Jun 21 14:36:14 2019
Hi, John,
I have no idea, but I will indeed add those to all my point_stat
config
files and try again.
Thanks!
Perry
On Fri, Jun 21, 2019 at 4:34 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Perry,
>
> The LANDSF and WATERSF entries are missing from the PointStatConfig
file
> itself, not the METplus conf file. This is basically a bug that we
failed
> to update those PointStat config files in the METplus repo.
>
> So I created this GitHub issue:
> https://github.com/NCAR/METplus/issues/248
>
> Just take a look in this file:
> POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_AIRNOW
>
> If LANDSF and WATERSF are missing from message_type_group_map,
please try
> adding them.
>
> But I have no idea why one run would work and another would not?
>
> John
>
> On Fri, Jun 21, 2019 at 2:20 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=90740 >
> >
> > Oh, so all I have to do is include the WATERSF and LANDSF line in
my
> > point_stat conf file?
> >
> > If that's the case, why is another execution of point_stat working
> without
> > these lines, using 8.1?
> >
> > Perry
> >
> > On Fri, Jun 21, 2019 at 4:17 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Perry and David,
> > >
> > > Thought I'd jump in on this one.
> > >
> > > One explanation for this error would be using a met-8.0 config
to run
> > > met-8.1 tools. Here's some background. We enhanced Point-Stat
in
> > met-8.1
> > > to support a new interpolation option named "GEOG_MATCH". This
option
> > only
> > > verifies land obs using land model points and water obs using
water
> model
> > > points. And it also checks the height of the obs relative to
the model
> > > topography.
> > >
> > > So Point-Stat now needs to know what message types qualify as
being
> land
> > vs
> > > water. Previously we'd had these things hard-coded but in met-
8.1, we
> > > moved them to the config file in the "message_type_group_map".
> > >
> > > In met-8.0:
> > > message_type_group_map = [
> > > { key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET";
},
> > > { key = "ANYAIR"; val = "AIRCAR,AIRCFT";
},
> > > { key = "ANYSFC"; val =
"ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
> > > { key = "ONLYSF"; val = "ADPSFC,SFCSHP";
}
> > > ];
> > >
> > > In met-8.1:
> > > message_type_group_map = [
> > > { key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET";
},
> > > { key = "ANYAIR"; val = "AIRCAR,AIRCFT";
},
> > > { key = "ANYSFC"; val =
"ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
> > > { key = "ONLYSF"; val = "ADPSFC,SFCSHP";
},
> > > { key = "LANDSF"; val = "ADPSFC,MSONET";
},
> > > { key = "WATERSF"; val = "SFCSHP";
}
> > > ];
> > >
> > > You see we added entries for LANDSF and WATERSF and these are
included
> in
> > > the default config file.
> > >
> > > Perhaps we failed to update the Point-Stat config files in
METplus to
> > > include these changes?
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, Jun 21, 2019 at 10:24 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=90740
>
> > > >
> > > > Hi, David,
> > > >
> > > > Here are the complete contents. Other executions of
point_stat work
> > > > without any mapping for LANDSF in the config file.
> > > >
> > > > [dir]
> > > >
> > > > # Forecast and Obs file input directories (netCDF files)
> > > > FCST_POINT_STAT_INPUT_DIR = /gpfs/hps/nco/ops/com/aqm/prod
> > > > OBS_POINT_STAT_INPUT_DIR = {OUTPUT_BASE}/aqm/conus_sfc
> > > >
> > > > # Final output directory for point_stat output
> > > > POINT_STAT_OUTPUT_DIR = {OUTPUT_BASE}/aqm/stat
> > > >
> > > > [config]
> > > >
> > > > # MET configuration file
> > > > POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_AIRNOW
> > > >
> > > > # Forecast hour start, end, and interval. Interval is the
forecast
> > > interval
> > > > in
> > > > # hours.
> > > > LEAD_SEQ = begin_end_incr(0,48,1)
> > > >
> > > > # Model/fcst and obs name, e.g. GFS, NAM, GDAS, etc.
> > > > MODEL_NAME = aqm
> > > > OBS_NAME = nam
> > > >
> > > > # Regrid to specified grid. Indicate NONE if no regridding,
or the
> > grid
> > > id
> > > > # (e.g. G212)
> > > > POINT_STAT_REGRID_TO_GRID = G104
> > > >
> > > > # Verification Masking regions
> > > > # Indicate which grid and polygon masking region, if
applicable
> > > > POINT_STAT_GRID = FULL
> > > >
> > > > # List of full path to poly masking files. NOTE: Only short
lists of
> > > poly
> > > > # files work (those that fit on one line), a long list will
result in
> > an
> > > > # environment variable that is too long, resulting in an
error. For
> > long
> > > > # lists of poly masking files (i.e. all the mask files in the
> NCEP_mask
> > > > # directory), define these in the MET point_stat configuration
file.
> > > > POINT_STAT_POLY =
> > > > POINT_STAT_STATION_ID =
> > > >
> > > > # Message types, if all message types are to be returned,
leave this
> > > empty,
> > > > # otherwise indicate the message types of interest.
> > > > POINT_STAT_MESSAGE_TYPE = ONLYSF
> > > >
> > > > # Variables and levels as specified in the field dictionary of
the
> MET
> > > > # point_stat configuration file. Specify as FCST_VARn_NAME,
> > > > FCST_VARn_LEVELS,
> > > > # (optional) FCST_VARn_OPTION
> > > > FCST_VAR1_NAME = TMP
> > > > FCST_VAR1_LEVELS = Z2
> > > >
> > > > FCST_VAR2_NAME = RH
> > > > FCST_VAR2_LEVELS = Z2
> > > >
> > > > FCST_VAR3_NAME = DPT
> > > > FCST_VAR3_LEVELS = Z2
> > > >
> > > > FCST_VAR4_NAME = UGRD
> > > > FCST_VAR4_LEVELS = Z10
> > > >
> > > > FCST_VAR5_NAME = VGRD
> > > > FCST_VAR5_LEVELS = Z10
> > > >
> > > > FCST_VAR6_NAME = TCDC
> > > > FCST_VAR6_LEVELS = L0
> > > > FCST_VAR6_OPTIONS = GRIB_lvl_typ = 200
> > > >
> > > > FCST_VAR7_NAME = PRMSL
> > > > FCST_VAR7_LEVELS = Z0
> > > >
> > > > # Regular expressions for files relevant to this use case. Use
> > > parentheses
> > > > # around any date, cycle, lead (forecast) and offset time.
> > > > #FCST_INPUT_DIR_REGEX = .*nam.([0-9]{8})
> > > > #FCST_INPUT_DIR_REGEX =
> > > >
> > > > [filename_templates]
> > > >
> > > > # NOTE: These are EXAMPLE FILENAME TEMPLATES
> > > > #FCST_INPUT_FILE_TMPL =
> > > >
nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm{offset?fmt=%H}.grib2
> > > > #FCST_INPUT_FILE_TMPL =
> > > nam.t{cycle?fmt=%H}z.awphys{lead?fmt=%H}.tm00.grib2
> > > > #FCST_INPUT_FILE_TMPL =
> > > rap.t{cycle?fmt=%H}z.awp130pgrbf{lead?fmt=%H}.grib2
> > > > #FCST_INPUT_FILE_TMPL =
> > > >
> > > >
> > >
> >
>
.*nam.{init?fmt=%Y%m%d}/nam.t{cycle?fmt=%HH}z.awphys{lead?fmt=%HH}.tm{offset?fmt=%HH}.grib2
> > > > FCST_POINT_STAT_INPUT_TEMPLATE =
> > > >
> > > >
> > >
> >
>
aqm.{init?fmt=%Y%m%d}/aqm.t{init?fmt=%2H}z.awpozcon.f{lead?fmt=%2H}.148.grib2
> > > > #OBS_INPUT_FILE_TMPL =
> prepbufr.nam.{init?fmt=%Y%m%d}.t{cycle?fmt=%HH}
> > > z.tm
> > > > {offset?fmt=%HH}.nc
> > > > #OBS_INPUT_FILE_TMPL = prepbufr.nam.{valid?fmt=%Y%m%d%H}.nc
> > > > OBS_POINT_STAT_INPUT_TEMPLATE =
prepbufr.aqm.{valid?fmt=%Y%m%d%H}.nc
> > > > POINT_STAT_OUTPUT_TEMPLATE = aqm
> > > >
> > > > On Fri, Jun 21, 2019 at 12:11 PM David Fillmore via RT <
> > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Perry -
> > > > > Can you attach your point_stat.conf_aq file?
> > > > > The message_type_group_map needs to have an entry for key =
> "LANDSF"
> > in
> > > > the
> > > > > user config file as well.
> > > > > thanks,
> > > > > David
> > > > >
> > > > > On Fri, Jun 21, 2019 at 9:25 AM perry.shafran at noaa.gov via
RT <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Fri Jun 21 09:25:04 2019: Request 90740 was acted upon.
> > > > > > Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > > Queue: met_help
> > > > > > Subject: Error when running MET using METplus
> > > > > > Owner: Nobody
> > > > > > Requestors: perry.shafran at noaa.gov
> > > > > > Status: new
> > > > > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90740
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi, there,
> > > > > >
> > > > > > I'm getting this weird error now when I run MET (though
> apparently
> > > only
> > > > > for
> > > > > > the air quality instance) that gives me this error.
> > > > > >
> > > > > > ERROR :
> > > > > > ERROR : PointStatVxOpt::set_vx_pd() ->
"message_type_group_map"
> > must
> > > > > > contain an entry for "LANDSF".
> > > > > > ERROR :
> > > > > >
> > > > > > I'm not sure why this is becoming an error for this
particular
> > > > execution
> > > > > > and not for others. FWIW, I'm using the command:
> > > > > >
> > > > > > /meso/save/Perry.Shafran/METplus-2.1/ush/master_metplus.py
-c
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > > > > -c
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > > > > -c
> > > > >
> > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/pb2nc.conf_aq
> > > > > > -c
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/point_stat.conf_aq
> > > > > > -c
> > > > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/shared.conf
> > > > > > -c
> > > > /meso/save/Perry.Shafran/METplus-
2.1/parm/use_cases/perry/system.conf
> > > > > >
> > > > > > The "LANDSF" entry seems to come from Julie's default
file, but
> for
> > > > some
> > > > > > reason I'm having issues. What am I missing here?
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Perry
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list