ECJ-INTEREST-L Archives

June 2006

ECJ-INTEREST-L@LISTSERV.GMU.EDU
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Date:
Fri, 23 Jun 2006 08:01:20 -0400
MIME-version:
1.0 (Apple Message framework v750)
Reply-To:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Content-type:
text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Subject:
Re: Tree building without terminals for all types
From:
Sean Luke <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-Transfer-Encoding:
8bit
Comments:
To: ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Parts/Attachments:
text/plain (31 lines) 
I suspect _Uniform_ should do the job.  However if I recall it was  
complaining to someone who was doing this earlier: but in ECJ 13 I  
added some fixes.  Try it and let me know.

Sean

On Jun 23, 2006, at 3:28 AM, Stefan Wappler wrote:

>
> Is there a way to configure the tree builders provided by ECJ that  
> they work in the case that for some types of the type set no  
> terminal exists (but only non-terminals)? Or are there alternative  
> tree builders known/available that would do this job?
>
> (Of course, it is possible to build trees using the function set  
> and type set that doesn't contain terminals for all types. But  
> actually, I'm not able to get ECJ do this.)
>
>
>
> Mit freundlichen Grüßen / Kind regards
>
> Stefan Wappler
> DaimlerChrysler Automotive IT Institute
> Ernst-Reuter-Platz 7
> 10587 Berlin/Germany
>
> Phone +49 (0)30 39982 358
> Fax +49 (0)711 3052 160825
> mailto: [log in to unmask]

ATOM RSS1 RSS2