Yes, fitness is related to the environment. But...
In this case, if the algorighm becomes simpler if FITNESS is more tightly associated with the INDIVIDUAL. For example, this:
sub choose {
my $self = shift;
my $f = rand(1.0);
my $index = 0;
my $sum = 0.0;
foreach my $fitnes (@{$self->{FITNESSES}}) {
$sum += $fitnes;
return ${$self->{INDIVIDUALS}}[$index] if $sum >= $f;
++$index;
}
die "can't select an individual";
}
becomes:
sub choose {
my $self = shift;
my $f = rand(1.0);
my $sum = 0.0;
foreach my $individual (@{$self->{INDIVIDUALS}}) {
$sum += $individual->{FITNESS};
return $individual if $sum >= $f;
}
die "can't select an individual";
}
which I consider an improvement, not only due to the fact that there's (a little) less code, but the concept of choosing an individual and not a fitness is emphasized.
Finally, I must admit that I have a bias in relation to the idea you presented. Yes, environment does determine fitness. However, what if you're trying to evolved generalized behavior, i.e., a program that will perform well in any environment, and not simply the one's it was trained in? The little bit of work I've done with GP has been focused in the direction of trying to avoid such "over-training" or specialization.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.