In the mean time, I have found out that others have attempted GP in
silicon with the goal to configure or co-evolve harware controllers for
robots. Both use FPGAs, probably more suited to this task.

http://www.cs.indiana.edu/l/www/robotics/FPGA97/Main.html
http://www.genobyte.com/robokoneko.html Robokoneko is evolved in a
software simulation first to overcome problems in hardware simulation
(such as human intervention).
There are undoubtedly been more projects like this.

However, I still think it would be interesting to attempt evolutionary
computation on a PIC. Rather than self-modifying code, it may be
sufficient to evolve a set of parameters in data memory. (I do want to
play around with FPGAs eventually though!)

Using two PICs can still be advantageous, even if it were only to have
some kind of co-processor. I'll know it when I need it :)

Peter (who just got his first PICs in the mail 15 minutes ago!)


> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU] On Behalf Of Peter L. Peres
> Sent: Wednesday, October 17, 2001 11:04 PM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: [PIC]: Genetic Programming
>
>
> I think that your approach will work, but I think that it
> would be best to use two PICSIMMs or something like that
> since they can read their own program (bytecode) I think. I
> once made a clock that would learn how much it deviated by
> being attached to an accurate clock (that made square waves
> at 1Hz), and then write a fudge factor into its own EEPROM.
> Then it could write this data to another clock of the same
> kind using TTL RS232 at 1200 Bauds. It used a 16F84. It was
> supposed to be ported to 16C672 but then it was dropped. This
> is not GP but you get the idea.
>
> Peter
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply
> us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body
>
>

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu