On Fri, 15 Oct 2010 20:10:05 -0400
Chris Gahan ch...@ill-logic.com wrote:
I think so too. Genetic Programming always struck me as quite wasteful
because your algorithm doesn't care about *why* any of your offspring
succeeded or failed.
Intelligence has been a huge evolutionary boon because
Cunningham's Extreme Genetic Programming might be of interest:
http://www.neocoretechs.com/.
Murat
On Fri, Oct 15, 2010 at 1:33 AM, John Nilsson j...@milsson.nu wrote:
On Fri, Oct 15, 2010 at 3:20 AM, Casey Ransberger
casey.obrie...@gmail.com wrote:
I wonder: what if all we did was write
Also, some interesting research along these lines by Stephanie Forrest of
the University of New Mexico:
http://genprog.adaptive.cs.unm.edu/
-- Max
On Fri, Oct 15, 2010 at 11:04 AM, Murat Girgin gir...@gmail.com wrote:
Cunningham's Extreme Genetic Programming might be of interest:
I think genetic programming is probably most interesting if you don't
write a mere battery of black-box tests for the fitness evaluation.
It would be much cooler to have code that reasons about the candidat
solutions, and see how much of each is proovably correct, IMHO. =)
Casey Ransberger
I think so too. Genetic Programming always struck me as quite wasteful
because your algorithm doesn't care about *why* any of your offspring
succeeded or failed.
Intelligence has been a huge evolutionary boon because it allows
critters to learn from the mistakes of others, and then over time
I'd say the biggest problem is more in the selection than generation /
mutation. In the world, it's easy to determine the winner - he passes on
more of his genes. But if we've got two potential solutions, neither of
which actually pass the test, how do we select which to continue mutating,
and
On 15/10/2010, at 12:20 PM, Casey Ransberger wrote:
The previous thread about testing got me thinking about this again. One of
the biggest problems I have in the large with getting developers to write
tests is the burden of maintaining the tests when the code changes.
I have this wacky
On 14 October 2010 21:20, Casey Ransberger casey.obrie...@gmail.com wrote:
The previous thread about testing got me thinking about this again. One of
the biggest problems I have in the large with getting developers to write
tests is the burden of maintaining the tests when the code changes.
