archive mirror
 help / color / mirror / Atom feed
From: Jake Moilanen <>
To: James Bruce <>
Subject: Re: [ANNOUNCE 0/4][RFC] Genetic Algorithm Library
Date: Sat, 8 Jan 2005 16:56:30 -0600	[thread overview]
Message-ID: <20050108165630.4c4e2efa@localhost> (raw)
In-Reply-To: <>

On Sat, 08 Jan 2005 09:19:42 -0500
James Bruce <> wrote:

> Ok I've read the patch and see you do indeed have crossover; Now I have 
> a different question.  What is the motivation for generating two 
> children at once, instead of just one?    Genes values shouldn't get 
> "lost" since the parents are being kept around anyway.  Also, since the 
> parameters in general will not have a meaningful ordering, it might make 
> sense for the generic crossover to be the "each gene randomly picked 
> from one of the two parents" approach.  In practice  I've found that to 
> mix things up a bit better in the parameter optimization problems I've 
> done with GAs.

The intitial motivation for creating two children at once was so each
parent could pass on all of their genes.  The 75% of the parent's genes
might be in child A, but the other 25% would be in child B.  

Thinking about it more, there should be no reason that all of a parent's
genes have to be passed on in a child.  It would not be too difficult to
have each gene come randomly from one of the two parents.  I'll add that
in on the next rev of the patches. 


  reply	other threads:[~2005-01-08 22:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 16:08 [ANNOUNCE 0/4][RFC] Genetic Algorithm Library Jake Moilanen
2005-01-06 16:14 ` [ANNOUNCE 1/4][RFC] " Jake Moilanen
2005-01-06 17:20   ` Cal Peake
2005-01-06 17:26     ` Cal Peake
2005-01-06 16:18 ` [ANNOUNCE 2/4][RFC] " Jake Moilanen
2005-01-06 16:22 ` [ANNOUNCE 3/4][RFC] " Jake Moilanen
2005-01-06 16:27 ` [ANNOUNCE 4/4][RFC] " Jake Moilanen
2005-01-08 14:05 ` [ANNOUNCE 0/4][RFC] " James Bruce
2005-01-08 14:19   ` James Bruce
2005-01-08 22:56     ` Jake Moilanen [this message]
2005-01-08 15:37 ` Pedro Larroy
2005-01-10 15:54   ` Jake Moilanen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050108165630.4c4e2efa@localhost \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).