ECJ-INTEREST-L Archives

February 2014

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
Mime-Version:
1.0
Sender:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Subject:
From:
Raymond Shpeley <[log in to unmask]>
Date:
Sun, 16 Feb 2014 21:50:50 -0500
Content-Transfer-Encoding:
8bit
Content-Type:
text/plain; charset="ISO-8859-1"
Reply-To:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Parts/Attachments:
text/plain (40 lines)
On Sun, 16 Feb 2014 17:59:10 -0500, Sean Luke <[log in to unmask]> wrote:


>That's because the tutorial example does not implement the describe() 
method.  But all the stats are outputted.
>

I'll look into that.

>I do note one oddity with the statistics you provided: though the system 
finds a solution that has a standardized fitness of 0.0, it's not the best 
individual of run!  This is for two reasons:
>
>- Floating point error results in the both 0.0 and 1.6653345E-16 getting 
converted to an adjusted fitness of 1.0
>
>- Comparison is done based on adjusted fitness; but determination of ideal 
individuals is done based on standardized fitness. [ In a perfect world, with no 
floating point error, this wouldn't be an issue]
>
>So I think we should move the GP comparisons to be entirely based on 
standardized fitness.  Or alternatively swich to doubles.  Or both.

Right. I see your point.

>
>> The console didn't show any early termination.
>
>Sure it did:
>
>> Found Ideal Individual
>
>
>Sean

Well, I meant it didn't show an early termination due to an error... I should turn 
verbosity on, shouldn't I?

-- ray

ATOM RSS1 RSS2