[Met_help] [rt.rap.ucar.edu #67484] History for MET-TC create consensus option
John Halley Gotway via RT
met_help at ucar.edu
Fri Jun 6 15:12:50 MDT 2014
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I'm trying to create a consensus, but get a syntax error with my Config
file. I've attached the config file here. I've tried to copy the
formatting from the MET-TC users guide, but can't seem to find the source
of the error. Do you have an idea what it is? The error message is
attached in "error.txt".
-Dave Zelinsky
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #67484] MET-TC create consensus option
From: John Halley Gotway
Time: Thu Jun 05 12:10:50 2014
Dave,
Seems silly, but try using lower case for the true/false in the
"required" setting:
required = [false, false];
I'll see if I can get that resolved for the next release.
Thanks,
John
On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT wrote:
>
> Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
> Transaction: Ticket created by david.a.zelinsky at noaa.gov
> Queue: met_help
> Subject: MET-TC create consensus option
> Owner: Nobody
> Requestors: david.a.zelinsky at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>
>
> I'm trying to create a consensus, but get a syntax error with my
Config
> file. I've attached the config file here. I've tried to copy the
> formatting from the MET-TC users guide, but can't seem to find the
source
> of the error. Do you have an idea what it is? The error message is
> attached in "error.txt".
>
>
> -Dave Zelinsky
>
------------------------------------------------
Subject: MET-TC create consensus option
From: David Zelinsky - NOAA Affiliate
Time: Thu Jun 05 12:23:16 2014
John,
Thanks, that did it. In the meantime, it might be worth putting lower
case
in the users guide example.
-Dave
On Thu, Jun 5, 2014 at 2:10 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Dave,
>
> Seems silly, but try using lower case for the true/false in the
"required"
> setting:
> required = [false, false];
>
> I'll see if I can get that resolved for the next release.
>
> Thanks,
> John
>
> On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT
wrote:
> >
> > Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
> > Transaction: Ticket created by david.a.zelinsky at noaa.gov
> > Queue: met_help
> > Subject: MET-TC create consensus option
> > Owner: Nobody
> > Requestors: david.a.zelinsky at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
> >
> >
> > I'm trying to create a consensus, but get a syntax error with my
Config
> > file. I've attached the config file here. I've tried to copy the
> > formatting from the MET-TC users guide, but can't seem to find the
source
> > of the error. Do you have an idea what it is? The error message
is
> > attached in "error.txt".
> >
> >
> > -Dave Zelinsky
> >
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #67484] MET-TC create consensus option
From: John Halley Gotway
Time: Thu Jun 05 12:25:25 2014
Will do. Thanks for letting us know.
John
On 06/05/2014 12:23 PM, David Zelinsky - NOAA Affiliate via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>
> John,
>
> Thanks, that did it. In the meantime, it might be worth putting
lower case
> in the users guide example.
>
> -Dave
>
>
> On Thu, Jun 5, 2014 at 2:10 PM, John Halley Gotway via RT
<met_help at ucar.edu
>> wrote:
>
>> Dave,
>>
>> Seems silly, but try using lower case for the true/false in the
"required"
>> setting:
>> required = [false, false];
>>
>> I'll see if I can get that resolved for the next release.
>>
>> Thanks,
>> John
>>
>> On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT
wrote:
>>>
>>> Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
>>> Transaction: Ticket created by david.a.zelinsky at noaa.gov
>>> Queue: met_help
>>> Subject: MET-TC create consensus option
>>> Owner: Nobody
>>> Requestors: david.a.zelinsky at noaa.gov
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>>>
>>>
>>> I'm trying to create a consensus, but get a syntax error with my
Config
>>> file. I've attached the config file here. I've tried to copy the
>>> formatting from the MET-TC users guide, but can't seem to find the
source
>>> of the error. Do you have an idea what it is? The error message
is
>>> attached in "error.txt".
>>>
>>>
>>> -Dave Zelinsky
>>>
>>
>>
------------------------------------------------
Subject: MET-TC create consensus option
From: David Zelinsky - NOAA Affiliate
Time: Thu Jun 05 13:09:55 2014
This might be a silly question, but is it possible to make a consensus
which includes another user-defined a consensus?
For instance, say I wanted to make a consensus of GFSI and EMXI and
call it
GFEX. Then, I want to make a consensus of GFEX and OFCI as a "first
guess"
forecast, and verify it against OFCL. Is this possible with the
current
setup?
-Dave
On Thu, Jun 5, 2014 at 2:25 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Will do. Thanks for letting us know.
>
> John
>
> On 06/05/2014 12:23 PM, David Zelinsky - NOAA Affiliate via RT
wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
> >
> > John,
> >
> > Thanks, that did it. In the meantime, it might be worth putting
lower
> case
> > in the users guide example.
> >
> > -Dave
> >
> >
> > On Thu, Jun 5, 2014 at 2:10 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> >> wrote:
> >
> >> Dave,
> >>
> >> Seems silly, but try using lower case for the true/false in the
> "required"
> >> setting:
> >> required = [false, false];
> >>
> >> I'll see if I can get that resolved for the next release.
> >>
> >> Thanks,
> >> John
> >>
> >> On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT
wrote:
> >>>
> >>> Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
> >>> Transaction: Ticket created by david.a.zelinsky at noaa.gov
> >>> Queue: met_help
> >>> Subject: MET-TC create consensus option
> >>> Owner: Nobody
> >>> Requestors: david.a.zelinsky at noaa.gov
> >>> Status: new
> >>> Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
> >>>
> >>>
> >>> I'm trying to create a consensus, but get a syntax error with my
Config
> >>> file. I've attached the config file here. I've tried to copy
the
> >>> formatting from the MET-TC users guide, but can't seem to find
the
> source
> >>> of the error. Do you have an idea what it is? The error
message is
> >>> attached in "error.txt".
> >>>
> >>>
> >>> -Dave Zelinsky
> >>>
> >>
> >>
>
>
------------------------------------------------
Subject: MET-TC create consensus option
From: David Zelinsky - NOAA Affiliate
Time: Thu Jun 05 13:38:35 2014
And a related question, what is the proper syntax for computing 2 or
more
consensus models at once?
-Dave
On Thu, Jun 5, 2014 at 3:09 PM, David Zelinsky - NOAA Affiliate <
david.a.zelinsky at noaa.gov> wrote:
> This might be a silly question, but is it possible to make a
consensus
> which includes another user-defined a consensus?
>
> For instance, say I wanted to make a consensus of GFSI and EMXI and
call
> it GFEX. Then, I want to make a consensus of GFEX and OFCI as a
"first
> guess" forecast, and verify it against OFCL. Is this possible with
the
> current setup?
>
> -Dave
>
>
> On Thu, Jun 5, 2014 at 2:25 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Will do. Thanks for letting us know.
>>
>> John
>>
>> On 06/05/2014 12:23 PM, David Zelinsky - NOAA Affiliate via RT
wrote:
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>> >
>> > John,
>> >
>> > Thanks, that did it. In the meantime, it might be worth putting
lower
>> case
>> > in the users guide example.
>> >
>> > -Dave
>> >
>> >
>> > On Thu, Jun 5, 2014 at 2:10 PM, John Halley Gotway via RT <
>> met_help at ucar.edu
>> >> wrote:
>> >
>> >> Dave,
>> >>
>> >> Seems silly, but try using lower case for the true/false in the
>> "required"
>> >> setting:
>> >> required = [false, false];
>> >>
>> >> I'll see if I can get that resolved for the next release.
>> >>
>> >> Thanks,
>> >> John
>> >>
>> >> On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT
wrote:
>> >>>
>> >>> Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
>> >>> Transaction: Ticket created by david.a.zelinsky at noaa.gov
>> >>> Queue: met_help
>> >>> Subject: MET-TC create consensus option
>> >>> Owner: Nobody
>> >>> Requestors: david.a.zelinsky at noaa.gov
>> >>> Status: new
>> >>> Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>> >>>
>> >>>
>> >>> I'm trying to create a consensus, but get a syntax error with
my
>> Config
>> >>> file. I've attached the config file here. I've tried to copy
the
>> >>> formatting from the MET-TC users guide, but can't seem to find
the
>> source
>> >>> of the error. Do you have an idea what it is? The error
message is
>> >>> attached in "error.txt".
>> >>>
>> >>>
>> >>> -Dave Zelinsky
>> >>>
>> >>
>> >>
>>
>>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #67484] MET-TC create consensus option
From: John Halley Gotway
Time: Fri Jun 06 10:16:04 2014
Dave,
I tested it out, and yes, using a previously defined consensus track
in the definition of another consensus track works fine. Each time
tc_pairs defines a new consensus track, it just tacks it on to
the end of all the other tracks. So it's available to be found in the
next iteration.
Here's an example of defining multiple consensus tracks:
consensus = [
{
name = "CONS1";
members = ["HWRF","OCD5"];
required = [false, false];
min_req = 1;
},
{
name = "CONS2";
members = ["CONS1","HWRF"];
required = [false, false];
min_req = 1;
}
];
You just add another consensus definition block surrounded by curly
braces. And those blocks are comma-separated since they're elements
of the "consensus" array.
Thanks,
John
On 06/05/2014 01:38 PM, David Zelinsky - NOAA Affiliate via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>
> And a related question, what is the proper syntax for computing 2 or
more
> consensus models at once?
>
> -Dave
>
>
> On Thu, Jun 5, 2014 at 3:09 PM, David Zelinsky - NOAA Affiliate <
> david.a.zelinsky at noaa.gov> wrote:
>
>> This might be a silly question, but is it possible to make a
consensus
>> which includes another user-defined a consensus?
>>
>> For instance, say I wanted to make a consensus of GFSI and EMXI and
call
>> it GFEX. Then, I want to make a consensus of GFEX and OFCI as a
"first
>> guess" forecast, and verify it against OFCL. Is this possible with
the
>> current setup?
>>
>> -Dave
>>
>>
>> On Thu, Jun 5, 2014 at 2:25 PM, John Halley Gotway via RT <
>> met_help at ucar.edu> wrote:
>>
>>> Will do. Thanks for letting us know.
>>>
>>> John
>>>
>>> On 06/05/2014 12:23 PM, David Zelinsky - NOAA Affiliate via RT
wrote:
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>>>>
>>>> John,
>>>>
>>>> Thanks, that did it. In the meantime, it might be worth putting
lower
>>> case
>>>> in the users guide example.
>>>>
>>>> -Dave
>>>>
>>>>
>>>> On Thu, Jun 5, 2014 at 2:10 PM, John Halley Gotway via RT <
>>> met_help at ucar.edu
>>>>> wrote:
>>>>
>>>>> Dave,
>>>>>
>>>>> Seems silly, but try using lower case for the true/false in the
>>> "required"
>>>>> setting:
>>>>> required = [false, false];
>>>>>
>>>>> I'll see if I can get that resolved for the next release.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT
wrote:
>>>>>>
>>>>>> Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
>>>>>> Transaction: Ticket created by david.a.zelinsky at noaa.gov
>>>>>> Queue: met_help
>>>>>> Subject: MET-TC create consensus option
>>>>>> Owner: Nobody
>>>>>> Requestors: david.a.zelinsky at noaa.gov
>>>>>> Status: new
>>>>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
>>>>>>
>>>>>>
>>>>>> I'm trying to create a consensus, but get a syntax error with
my
>>> Config
>>>>>> file. I've attached the config file here. I've tried to copy
the
>>>>>> formatting from the MET-TC users guide, but can't seem to find
the
>>> source
>>>>>> of the error. Do you have an idea what it is? The error
message is
>>>>>> attached in "error.txt".
>>>>>>
>>>>>>
>>>>>> -Dave Zelinsky
>>>>>>
>>>>>
>>>>>
>>>
>>>
>>
------------------------------------------------
Subject: MET-TC create consensus option
From: David Zelinsky - NOAA Affiliate
Time: Fri Jun 06 12:12:26 2014
Great, thanks!
-Dave
On Fri, Jun 6, 2014 at 12:16 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Dave,
>
> I tested it out, and yes, using a previously defined consensus track
in
> the definition of another consensus track works fine. Each time
tc_pairs
> defines a new consensus track, it just tacks it on to
> the end of all the other tracks. So it's available to be found in
the
> next iteration.
>
> Here's an example of defining multiple consensus tracks:
>
> consensus = [
> {
> name = "CONS1";
> members = ["HWRF","OCD5"];
> required = [false, false];
> min_req = 1;
> },
> {
> name = "CONS2";
> members = ["CONS1","HWRF"];
> required = [false, false];
> min_req = 1;
> }
> ];
>
> You just add another consensus definition block surrounded by curly
> braces. And those blocks are comma-separated since they're elements
of the
> "consensus" array.
>
> Thanks,
> John
>
> On 06/05/2014 01:38 PM, David Zelinsky - NOAA Affiliate via RT
wrote:
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
> >
> > And a related question, what is the proper syntax for computing 2
or more
> > consensus models at once?
> >
> > -Dave
> >
> >
> > On Thu, Jun 5, 2014 at 3:09 PM, David Zelinsky - NOAA Affiliate <
> > david.a.zelinsky at noaa.gov> wrote:
> >
> >> This might be a silly question, but is it possible to make a
consensus
> >> which includes another user-defined a consensus?
> >>
> >> For instance, say I wanted to make a consensus of GFSI and EMXI
and call
> >> it GFEX. Then, I want to make a consensus of GFEX and OFCI as a
"first
> >> guess" forecast, and verify it against OFCL. Is this possible
with the
> >> current setup?
> >>
> >> -Dave
> >>
> >>
> >> On Thu, Jun 5, 2014 at 2:25 PM, John Halley Gotway via RT <
> >> met_help at ucar.edu> wrote:
> >>
> >>> Will do. Thanks for letting us know.
> >>>
> >>> John
> >>>
> >>> On 06/05/2014 12:23 PM, David Zelinsky - NOAA Affiliate via RT
wrote:
> >>>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
> >>>>
> >>>> John,
> >>>>
> >>>> Thanks, that did it. In the meantime, it might be worth
putting lower
> >>> case
> >>>> in the users guide example.
> >>>>
> >>>> -Dave
> >>>>
> >>>>
> >>>> On Thu, Jun 5, 2014 at 2:10 PM, John Halley Gotway via RT <
> >>> met_help at ucar.edu
> >>>>> wrote:
> >>>>
> >>>>> Dave,
> >>>>>
> >>>>> Seems silly, but try using lower case for the true/false in
the
> >>> "required"
> >>>>> setting:
> >>>>> required = [false, false];
> >>>>>
> >>>>> I'll see if I can get that resolved for the next release.
> >>>>>
> >>>>> Thanks,
> >>>>> John
> >>>>>
> >>>>> On 06/05/2014 06:40 AM, David Zelinsky - NOAA Affiliate via RT
wrote:
> >>>>>>
> >>>>>> Thu Jun 05 06:40:26 2014: Request 67484 was acted upon.
> >>>>>> Transaction: Ticket created by david.a.zelinsky at noaa.gov
> >>>>>> Queue: met_help
> >>>>>> Subject: MET-TC create consensus option
> >>>>>> Owner: Nobody
> >>>>>> Requestors: david.a.zelinsky at noaa.gov
> >>>>>> Status: new
> >>>>>> Ticket <URL:
> >>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=67484 >
> >>>>>>
> >>>>>>
> >>>>>> I'm trying to create a consensus, but get a syntax error with
my
> >>> Config
> >>>>>> file. I've attached the config file here. I've tried to
copy the
> >>>>>> formatting from the MET-TC users guide, but can't seem to
find the
> >>> source
> >>>>>> of the error. Do you have an idea what it is? The error
message is
> >>>>>> attached in "error.txt".
> >>>>>>
> >>>>>>
> >>>>>> -Dave Zelinsky
> >>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>
>
>
------------------------------------------------
More information about the Met_help
mailing list