[Met_help] [rt.rap.ucar.edu #80541] History for a running error with key words of do_assign_id()

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Dear Mr. or Mrs.,

I'm running MET on theia. The same scripts works previous for MET5.2
However, now, i got the error message:
^^
DEBUG 1: Default Config File:
/scratch4/BMC/dtc/MET/met-6.0/share/met/config/PointStatConfig_default
DEBUG 1: User Config File: PointStatConfig_hi_imp_ADPSFC
ERROR  :
ERROR  : do_assign_id() -> identifier "SINGLE" not defined in this scope!
ERROR  :

VV

I made a minimum example tared as tlei-deb-met.tar in /home/Ting.Lei/tmp.
After taring it, in the generated dir, , type "deb.ksh", which will
reproduce the error.
Your help is appreciated.
Best Regards,
Ting


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: a running error with key words of do_assign_id()
From: John Halley Gotway
Time: Fri May 19 13:19:12 2017

Ting,

I see you're getting an error from Point-Stat when it's parsing your
configuration file.  Specifically, it has a problem with the "SINGLE"
setting.  Thanks for pointing me to an example... that make it much
easier
to debug.

I looked in your config file (PointStatConfig_hi_imp_ADPSFC) for and
found
the reference to "SINGLE":
      duplicate_flag = SINGLE;

Then I opened up the config README file for met-6.0 to see valid
settings
for duplicate_flag:
     /scratch4/BMC/dtc/MET/met-6.0/share/met/config/README
And I found that duplicate_flag can be set to "NONE" or "UNIQUE".

This config file option has changed from version 5.2 of MET to version
6.0.  In 5.2, duplicate_flag could be set to "SINGLE" to indicate that
the
*single* observation closest in valid time to the forecast valid time
should be used.  However, in version 6.0, that logic is now supported
by
the new "obs_summary" option.  Specifically, set "obs_summary =
NEAREST" to
only use the single observation values nearest in time to the forecast
valid time.

Sorry for the confusion, but removing duplicate_flag = SINGLE as an
option
made logical sense with the addition of the obs_summary option.

Hope that helps clarify.

Thanks,
John


On Fri, May 19, 2017 at 12:58 PM, Ting Lei - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:

>
> Fri May 19 12:58:24 2017: Request 80541 was acted upon.
> Transaction: Ticket created by ting.lei at noaa.gov
>        Queue: met_help
>      Subject: a running error with key words of do_assign_id()
>        Owner: Nobody
>   Requestors: ting.lei at noaa.gov
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80541 >
>
>
> Dear Mr. or Mrs.,
>
> I'm running MET on theia. The same scripts works previous for MET5.2
> However, now, i got the error message:
> ^^
> DEBUG 1: Default Config File:
> /scratch4/BMC/dtc/MET/met-
6.0/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File: PointStatConfig_hi_imp_ADPSFC
> ERROR  :
> ERROR  : do_assign_id() -> identifier "SINGLE" not defined in this
scope!
> ERROR  :
>
> VV
>
> I made a minimum example tared as tlei-deb-met.tar in
/home/Ting.Lei/tmp.
> After taring it, in the generated dir, , type "deb.ksh", which will
> reproduce the error.
> Your help is appreciated.
> Best Regards,
> Ting
>
>

------------------------------------------------
Subject: a running error with key words of do_assign_id()
From: Ting Lei - NOAA Affiliate
Time: Fri May 19 13:58:33 2017

Hi, John,
Thanks a lot for your prompt help and perfect explanation.
Your solution did work.
Really appreciate your help.
Have a good weekend,
Ting

On Fri, May 19, 2017 at 3:19 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:

> Ting,
>
> I see you're getting an error from Point-Stat when it's parsing your
> configuration file.  Specifically, it has a problem with the
"SINGLE"
> setting.  Thanks for pointing me to an example... that make it much
easier
> to debug.
>
> I looked in your config file (PointStatConfig_hi_imp_ADPSFC) for and
found
> the reference to "SINGLE":
>       duplicate_flag = SINGLE;
>
> Then I opened up the config README file for met-6.0 to see valid
settings
> for duplicate_flag:
>      /scratch4/BMC/dtc/MET/met-6.0/share/met/config/README
> And I found that duplicate_flag can be set to "NONE" or "UNIQUE".
>
> This config file option has changed from version 5.2 of MET to
version
> 6.0.  In 5.2, duplicate_flag could be set to "SINGLE" to indicate
that the
> *single* observation closest in valid time to the forecast valid
time
> should be used.  However, in version 6.0, that logic is now
supported by
> the new "obs_summary" option.  Specifically, set "obs_summary =
NEAREST" to
> only use the single observation values nearest in time to the
forecast
> valid time.
>
> Sorry for the confusion, but removing duplicate_flag = SINGLE as an
option
> made logical sense with the addition of the obs_summary option.
>
> Hope that helps clarify.
>
> Thanks,
> John
>
>
> On Fri, May 19, 2017 at 12:58 PM, Ting Lei - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri May 19 12:58:24 2017: Request 80541 was acted upon.
> > Transaction: Ticket created by ting.lei at noaa.gov
> >        Queue: met_help
> >      Subject: a running error with key words of do_assign_id()
> >        Owner: Nobody
> >   Requestors: ting.lei at noaa.gov
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80541 >
> >
> >
> > Dear Mr. or Mrs.,
> >
> > I'm running MET on theia. The same scripts works previous for
MET5.2
> > However, now, i got the error message:
> > ^^
> > DEBUG 1: Default Config File:
> > /scratch4/BMC/dtc/MET/met-
6.0/share/met/config/PointStatConfig_default
> > DEBUG 1: User Config File: PointStatConfig_hi_imp_ADPSFC
> > ERROR  :
> > ERROR  : do_assign_id() -> identifier "SINGLE" not defined in this
scope!
> > ERROR  :
> >
> > VV
> >
> > I made a minimum example tared as tlei-deb-met.tar in
/home/Ting.Lei/tmp.
> > After taring it, in the generated dir, , type "deb.ksh", which
will
> > reproduce the error.
> > Your help is appreciated.
> > Best Regards,
> > Ting
> >
> >
>
>

------------------------------------------------