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  January 2006

ECJ-INTEREST-L January 2006

Subject:

Re: Messing with the parameters database in ec.Evolve

From:

Sean Luke <[log in to unmask]>

Reply-To:

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

Date:

Fri, 20 Jan 2006 01:22:39 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (167 lines)

So some explanation.

ECJ's new Evolve.java code (which I personally wrote a few months  
back :-) has the additional wrinkle of a jobs facility because so  
many people asked for one.  The problem is how to start up from  
checkpoint and continue right at the job number you had done before.   
That's where it's a little complicated, but not too bad.

A simpler, job-free main, would go something like this (I'm doing  
this at 12:30 PM so pardon me if I screw up somewhere!)

main(...)
	{
	state = possiblyRestoreFromCheckpoint(args);
	if (state!=null)  // meaning we loaded from checkpoint
		state.run(EvolutionState.C_STARTED_FROM_CHECKPOINT);
	else
		{
		parameters = loadParameterDatabase(args);
		state = initialize(parameters, 0);  // no job offset
		startFresh(state, null);  // no job prefix
		}
	System.exit(0);
	}

All the job stuff proceeds from there.

The way we're doing jobs is that ECJ maintains an Object[array] in  
EvolutionState.java called "job".  You can use this array for  
whatever you want if you're writing your own main().  Or you can, in  
the example above, not use it at all.  The purpose of the array is to  
enable you to store your job information and have it survive  
checkpoints and restores.  There is another variable in  
EvolutionState also called "runtimeArguments", which is the array of  
strings passed in as args[] originally to main().  Because jobs might  
need that info to survive too.

The basic main() we have is very simple -- it just increments a  
single job number, starting at 0.  We store the number as an Integer  
in jobs[0].  So here's some explanation of the code.  Keep in mind  
this is the DEFAULT main().  ECJ has been carefully arranged so that  
you can do your own main loop in any way you like.

1. We first try to load the state from a checkpoint if there was  
one.  If so, we finish that run.

         state = possiblyRestoreFromCheckpoint(args);
         if (state!=null)
             state.run(EvolutionState.C_STARTED_FROM_CHECKPOINT);

2. Okay, that job is finished if it existed.  Now, we make the job  
number 0 if we're starting from the very beginning (not from  
checkpoint), but if we had loaded from checkpoint, we want to set the  
new job number to the old job number (stored away in job[0]) plus 1.

         int jobCurrent = 0;
         if (state != null)
             {
             try
                 {
                 if (state.runtimeArguments == null)
                     Output.initialError("...");
                 args = state.runtimeArguments;
                 jobCurrent = ((Integer)(state.job[0])).intValue() + 1;
                 }
             catch (Exception e)
                 {
                 Output.initialError("...");
                 }
             }

3.  Now we load the parameter database.  Here's where the confusion  
comes in.  We're loading the parameter database every job in our  
simple main().  Why do we do this?  Mostly because parameter  
databases can get modified at runtime by the experimenter.  Otherwise  
there's not much reason I think.  The ParameterDatabase has a File  
called "directory" which might be problematic if it's restored from  
checkpoint, and a Vector called listeners, but I don't think either  
is probably a problem in most cases.  So sure, you could try just  
loading the parameter database only if we're starting fresh, and  
reusing the database in other cases.  I was throwing away the old  
database and reloading it because it was cleaner and less likely to  
generate experimenter-tickled bugs.

         parameters = loadParameterDatabase(args);
         int numJobs = parameters.getIntWithDefault(new Parameter 
("jobs"), null, 1);
         if (numJobs < 1)
             Output.initialError("...");

4. Now we just loop through the jobs. Each time we reload the  
parameter database if necessary, then initialize the EvolutionState  
from the database (this calls all the setup() methods, and the random  
number generators, more or less.  The RNG's seeds are incremented  
using the job# perhaps).  Then we stash away the job number in the  
EvolutionState in case it's going to get checkpointed out.  We also  
figure out the prefix that the job should use to make filenames  
specific to that job so jobs don't write on each other's output  
files.  If only one job, we don't use a prefix (for backwards  
compatibility).  And then we start the run with startFresh!  Then  
trash the parameters:

         for(int job = jobCurrent ; job < numJobs; job++)
             {
             if (parameters == null)
                 parameters = loadParameterDatabase(args);

             state = initialize(parameters, job);
             state.output.systemMessage("Job: " + job);
             state.job = new Object[1];
             state.job[0] = new Integer(job);
             state.runtimeArguments = args;

             String jobFilePrefix = null;
             if (numJobs > 1)
                 jobFilePrefix = "job." + job + ".";

             startFresh(state, jobFilePrefix);
             parameters = null;
             }

5. And then we quit.

         System.exit(0);



In truth, you don't have to follow this scheme at all; you can setup  
and pulse EvolutionState any way you like.  Here's the general  
procedure:

A. If starting up from checkpoint, call  
Checkpoint.restoreFromCheckpoint(filename),
	which does a bunch of stuff for you.
B. Else you need to make a parameter database and set up various things:
	1. The Output and logs for stdout, stderr, etc.
	2. The random number generators
	3. The evolutionState, and set some variables in it
	[All this is done by Evolve.initialize if you want to use that instead]
	4. if (jobFilePrefix != null)
             state.output.setFilePrefix(jobFilePrefix);
	5. state.startFresh()
C. Now you have a functioning EvolutionState.  Repeatedly call
	result = state.evolve();
	... until result = EvolutionState.R_NOTDONE
D. state.finish(result)
E. state.output.flush()
F. print out the used parameters etc. if you wish (See  
Evolve.startFresh(...) for code)
G. If you're all done, flush various streams and close the Output,  
and exit(0)

And you don't even have to load a parameter database from a file --  
you can construct one by hand if you like.


But in explaining this on this email I see an ugliness I didn't clean  
up.  I use state.run(...) to finish out the checkpointed run, but I  
use startFresh(...) to do a noncheckpointed run.  startFresh(...)  
does a bunch of items, including the same basic code as state.run 
(...).  But they're [1] not orthogonal and [2] startFresh cleans up  
afterwards and dumps parameters but it looks like my main(...) code  
does *not* do that if restoring from checkpoint.  Not a big bug, but  
I should make that prettier.  Thanks guys, even if inadvertently!


Sean

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

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