LISTSERV mailing list manager LISTSERV 16.0

Help for ECJ-INTEREST-L Archives


ECJ-INTEREST-L Archives

ECJ-INTEREST-L Archives


ECJ-INTEREST-L@LISTSERV.GMU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ECJ-INTEREST-L Home

ECJ-INTEREST-L Home

ECJ-INTEREST-L  April 2007

ECJ-INTEREST-L April 2007

Subject:

Re: Seeding a GP

From:

Sean Luke <[log in to unmask]>

Reply-To:

ECJ Evolutionary Computation Toolkit <[log in to unmask]>

Date:

Tue, 17 Apr 2007 15:06:38 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (126 lines)

Hi Chris.  You're correct, the problem could well be that  
readRootedTree is marching through the function set, asking each node  
in turn to try to load at that position, and your earlier predicate  
is gleefully loading because it matched its name.  The problem  
doesn't lie in readRootedTree, but in GPNode.readNode(DecodeReturn)

What's fundamentally triggering this is that you're using the same  
node twice.  This isn't *really* a bug per se, though I should check  
to see if there are multiple usages of the same GPNode class in a  
given function set.

So how to work around it?  Here's one way:

1. [easier] override toString() to print out not only the node's  
"name", but maybe the constraint number or some other unique  
identifier, so it looks like this perhaps:

     public String toString()
         { return ERC_PREFIX + name() + "{" + constraints + "}[" +  
encode() + "]"; }

This of course only works if you don't change your constraints  
orderings.

2. Override edu.jhuapl.PredicateERCNode.readNode to be just like  
ERC.readNode but instead change the line to:

	String str2 = ERC_PREFIX + name() + "{" + constraints + "}[";

... so it looks for that particular node.

You could of course detect what "kind" of constraints you're  
expecting and put something smarter than just a constraints number in  
there, but something like this might work.

Sean


On Apr 17, 2007, at 12:08 PM, Chris McCubbin wrote:

> Ok, I am now attempting to read in an individual using a text  
> stream but I
> seem to be having a tough issue. I think the problem is that I have  
> a node
> type, "predicate", which is a non-terminal ERC node. This predicate  
> node can
> have many different constraints. It always has 3 children but the 3  
> children
> can be of three different types, say person, place, or thing, or the
> emptyVariable (all terminals, and all ERC's except the empty  
> variable). The
> way I did this was create a whole lot of lines in the parameter  
> file that
> look like these:
>
> //this is the first one in the file btw.
> gp.nc.10 = ec.gp.GPNodeConstraints
> gp.nc.10.name = P-predicateConstraints
> gp.nc.10.returns = disjunction
> gp.nc.10.size = 3
> gp.nc.10.child.0 = person
> gp.nc.10.child.1 = emptyVariable
> gp.nc.10.child.2 = emptyVariable
>
> gp.fs.0.func.10 = edu.jhuapl.PredicateERCNode
> gp.fs.0.func.10.nc = P-predicateConstraints
>
> gp.nc.14 = ec.gp.GPNodeConstraints
> gp.nc.14.name = PL-predicateConstraints
> gp.nc.14.returns = disjunction
> gp.nc.14.size = 3
> gp.nc.14.child.0 = person
> gp.nc.14.child.1 = location
> gp.nc.14.child.2 = emptyVariable
>
> gp.fs.0.func.14 = edu.jhuapl.PredicateERCNode
> gp.fs.0.func.14.nc = PL-predicateConstraints
>
> ...etc.
>
> Before you ask, the predicate and children are ERC's because the  
> predicate
> itself can vary, for example we might have "cute(person1, empty,  
> empty)" or
> "tall(person2, empty, empty)" as two concrete predicates that are
> implemented by func.10 above.
>
> When the readRootedTree method in GPNode gets executed on a  
> predicate node,
> I don't think it can determine which one of the constraints it is  
> really
> supposed to be using so it just picks the first one and always  
> expects the
> first child to be a "person" terminal. When it sees something else,  
> it gives
> me the "I came across a symbol which I could not match up with a  
> type-valid
> node..." error.
>
> I believe the way to fix this may be to somehow modify the way my  
> predicate
> ERC reads itself in, but I could use some hints on how to do that.  
> Is this
> making any sense, or am I just way off base?
>
> Thanks,
> Chris
>
>
> Sean wrote:
>
> ECJ can load whole populations or create them from scratch, neither  
> of which
> you want in this case.  This is most easily done with a new
> subclass of Subpopulation, overriding Subpopulation.populate(...).
> Probably the easiest approach would be:
>
>  - call super.populate(...) to fill the population with random  
> individuals
>  - overwrite individuals[0] with your custom individual, perhaps  
> loaded from
> a file (see the two Individual.readIndividual(...) methods), or by
> constructing your individual programmatically and sticking it in.
>
> ECJ's got several ways of reading and writing individuals, using
> DataInput/DataOutput, or text streams.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2019
August 2019
June 2019
April 2019
March 2019
January 2019
December 2018
November 2018
October 2018
July 2018
May 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004

ATOM RSS1 RSS2



LISTSERV.GMU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager