WikiManual - User contributions [en]

C plus plus version

2006-04-19T22:42:23Z

216.249.144.14: /* Feature List for 3.0 */

==News and Updates==
(11 April 2006) I haven't actually finished anymore of the remaining features, but I ''have'' been working on all of them, and fixing alot of major bugs. Everything has been started, I just need to finish them all. The only large piece of work left that hasn't been started is the Bot Debug controls. A control does exist for it, but it needs to basically be rewritten to be smoother and easier to use, which calls for a complete reorganization of the code architecture. In addition I still need to get the robot mouse selection code to work.

(05 Feb 2006) The C++ version is nearing completion. It might even be possible to have a beta done by the end of the month, but it means Numsgil needs to really put some effort in, and he's sort of tired of programming. If you know any C++ and want to help, I assure you we'll welcome you with open arms!

== Reasons for Language switch ==

#If you're wondering why we're switching, it's because VB is for relatively simple, GUI based programs. Darwinbots is neither simple nor gui based. C++, on the other hand is a powerful language, but it has a higher development cost. [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controversy]
#Visual Basic does not intrinsically support pointers. As such, complex data structures become something of a chore to try and make.
#Numsgil knows more about C++ than he knows about Visual Basic.
#C++ can be made to be portable (say, we could make a Linux version). And presently the code is being developed with portability in mind (though as yet untested).

== Accessing the Current Code ==
The code is in an online version control system called [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

To access the SVN, you should download a SVN client. The one I found that I like the most is called [http://www.smartsvn.com/smartsvn/index.html Smart SVN]. Its basic (and more than adequate) version is free. You may also want to try [http://tortoisesvn.tigris.org/ TortoiseSVN], which integrates with Windows Explorer.

The SVN for Darwinbots is located at:

* [http://opensvn.csie.org/Darwinbots http://opensvn.csie.org/Darwinbots]
* [https://opensvn.csie.org/Darwinbots https://opensvn.csie.org/Darwinbots] secure server

'''Read only access is open to everyone. If you want to contribute to the code, you'll need Numsgil to give you a username and password.''' He can be reached at Numsgil2002@yahoo.com

== Code Dependencies ==
To get the code to compile and work, you'll need the following:

#A C++ compiler. [http://www.bloodshed.net/devcpp.html Dev-C++] is free, but there have been some issues with it conflicting with Microsoft Visual C++ 6.0 (which Numsgil uses, and hence is the officially supported environment). If you don't have MSVC++ 6.0 and would like it, contact Numsgil at Numsgil2002@yahoo.com
#OpenGL libraries. Specifically, the code must link to glut32.lib, opengl32.lib, and glu32.lib. You probably have these on your computer somewhere, but if you don't, [http://www.opengl.org/resources/faq/getting_started.html this site will help you]
#Fox GUI Toolkit. This is the library which allows Darwinbots to have a GUI at all. [http://www.fox-toolkit.org/ FOX GUI Homepage].
#The STLport for MSVC++ 6.0 if you have MSVC. Dev-C++ won't need this. It can be found at [http://www.ogre3d.org/index.php?option=com_remository&Itemid=57&func=selectcat&cat=1 The Ogre 3D engine download page]. It should be listed at the bottom of the page. This makes MSVC a bit more ANSI compliant, among other things. There are some rather nitpicky specifics you need to address to get the stlport working properly (that is, working without compile or link errors). At the time of this writing (March 2006) [http://www.ogre3d.org/wiki/index.php/Building_From_Source This Ogre wiki page on building the Ogre source] demonstrates what you need to do to get the stlport working properly. Just scroll down to the section called "stlport".
#I don't know how it works for Dev-C++, but if you run MSVC you must be sure that you select the Multithreaded libraries or you'll probably get an error. To set this, inside MSVC in your project go to project->settings. Go to the C/C++ tab, change category "General" to category "Code Generation". The new upper right hand corner drop box will let you set if you're using multithreaded/singlethreaded libraries.
#Fox GUI requires that you include wsock32.lib. Without it, you will get a single linker error (it will try and find gethostname and fail).

If you have any problems at all with any of the above steps, or want to help Numsgil make the process a bit smoother and have some ideas, contact him at Numsgil2002@yahoo.com.

== Coding Style ==
The official policy is that as long as Numsgil understands what's going on in your code, your style is fine. If you want to have a more uniform coding style throughout the code, this is the style Numsgil uses:

for(unsigned int x = 0; x < 10; x++)
{
cout << x; //notice the 4 space tab
}

You are welcome to follow it.

== Coding Doctrine ==
The goal of the code is two things:

#Speed
#Readability

Wherever speed is not an issue (as in 97% of the code) coders are encouraged to make the code as readable to newbies as possible. Imagine your mother's life depends on her deciphering your code and you won't be around to help. That means no clever programming tricks, and sparing use of any standard libraries and especially templates and inheritance and polymorphism and other "advanced" concepts.

== To Do List (updated sparingly) ==
Feb 05 2006

Updated April 13 2006
===Presently, the following needs to be finished before a "BETA" can be achieved:===

*<s>The GUI needs to be finished and integrated with the options data structure</s>
**The Physics Dropdown menus needs to be connected
**The Pond Mode gradient picute needs to be created
**The Robot Placement controls need to be created
**Both species mutation details and global mutation details need to be created/finished
*<s>Physics for robots needs to be finished (specifically, velocity limiting code and non-in-elastic collisions)</s>
*<s>-3, -4, -5, and -6 shots need to be finished,</s> as well as viruses (though viruses may be disabled in the initial release depending)
**<s>power shots need to be implemented.</s>
*Ties need to be coded using the new Tie paradigm discussed [http://forum.darwinbots.com/index.php?showtopic=560 here] and summarized on the [[new tie paradigm]] page
*The Robot Debugging window and robot mouse selection need to be finished.
*The graphics and engine need to be made thread safe.
*<s>Mutations code needs to be finished</s>
**<s>Insertion Code still needs to be written</s>
*Forward and backward compatible save/load routines for <s>Simulation Settings</s>, Simulations, and Robots. Preferably ascii over binary, except where size is an issue (as in Simulations), where some sort of file compression would be nice.
**<s>Save Settings</s>
**<s>Load Settings</s>
**Save Organism
**Load Organism
**Save Simulation
**Load Simulation

===These would be nice, but aren't 100% necessary for the "Beta" label===

*Scripts. PY was working on the idea of what they should be, so he should be consulted.
*Error Database. Basically, on an error an automatic report could be sent to one of the MYSQL databases available through our webspace and a notification sent to anyone working on the code automatically. Also, some sort of error viewer inside Darwinbots would be nice, so users could see how many other users reported the error they received and whether or not it's been addressed by the coders yet.
*Bot Database. A way to upload and download bots from a central database from inside Darwinbots itself. Also using a Database as described above (we have 10 of the things, we won't run out :P)
*Statistical tools. This would involve everything from collecting data from the sim (and analyzing it according to proper statistical tests) to building a graph form and deciding how to draw it to exporting the data as per user specs into a spreadsheet program (like Excel). It is prefered that whoever works on this have some statistics background so they know what sort of stats users would want to collect and test.
*The vision testing algorithm is presently O(n^2), as it uses the "brute force" method. See: [[Vision_algorithm ]] for more info. It can be made nearly linear O(n) by using uniform grid cells. see:

:[http://yallara.cs.rmit.edu.au/~mawurm/cosc1224/asst1/index.xhtml This resource which examines the issue]

:[http://www.harveycartel.org/metanet/tutorials/tutorialB.html This resource which describes the implementation and problems associated with it]

:Collision detection could use a similar technique, though its gains would be complicated by the fact that bots are not uniform in size.

:This would mean an absolutely insane boost in speed for large sims, but also would take some work.
*Since graphics are now using OpenGL, some pretty sweet graphics could be made. Admittedly spheres/circles shooting dots and lines at each other doesn't really inspire great art, but I think there's definitely potential for some sweet demos. Maybe move it to 3D graphics instead of 2D and use some fog effects. Maybe use a shader.

===Long standing feature requests===
Anyone who managed to implement these in a way that didn't drastically increase memory and CPU requirements would be a hero in the Darwinbots community.

*[[Environment Grid]] - Basically the idea that bots should be able to interact with their physical environment. Things like leave poop behind for other bots to deal with, pollute their environment, leave pheromone trails for other bots to follow, etc. There are, unfortunately, some gigantic memory and processing problems that beg for some smart, algorithm-savvy programmer to address.

*[[Metabolism]] - The idea that bots should be able to generate nrg or use nrg based on their own unique bio-chemistry (or is it darwo-chemistry :P). This involves creating a system (or letting it emerge) of bio-chemical pathways and materials. Closely tied with the Environment Grid and likewise inter-related with the memory and processing problems.

*[[Specialization | Specialization and Speciation]] - The idea that bots should be able to become more efficient as they limit the number of activities they participate in. The primary hurdle isn't in coding it, but in designing the basic system to everyone's desires. It must respect multicellular specialization as well as single celled speciation. Not an easy task.

*[[Sexual Reproduction]] - Some way for two bots to, with consent (although 'rape' might have a place as well), produce offspring that robustly intermarries the two parents' DNA.

=== Feature List for 3.0 ===
As the C++ version becomes stable, it will be time to complete some old feature requests and slap a "new and improved" sticker on it ;) Here's the list of features minimally necessary for me to consider such a version 3.0:

* [http://www.darwinbots.com/Forum/index.php?showtopic=1186 Codules]
* Internet Sharing using MySQL on the webspace
* Auto Patcher - checks the FTP automatically and will patch itself for you
* Bot Database using MySQL on the webspace
* Error Database using MySQL on the webspace (to report bugs directly from inside the program)
* Stable as bedrock (which will mean a version will have to exist for a month or so without anyone having any problems with it before I'll slap the 3.0 sticker on it)
* [http://www.darwinbots.com/Forum/index.php?showtopic=861&b=1&st=&p=&#entry Phagocytosis] replacing -6 shots
* Speed Optimizations - Run 1000 bots at 10 cycles/sec average.
* Compressed Save/Load simulation files for ease of sharing
* Advanced Bot Debugging GUI
* Scripts (probably using [http://www.lua.org Lua])
* Graphs
* DPP Environment Grid (see above link)
* Sexual Reproduction (probably using codules as chromosome analogues)
* Walls made of both destructable and indestructable materials (for ant bots primarily, so they can build nests).
* Metabolism (not a small task)
* Combat system revised [http://www.darwinbots.com/Forum/index.php?showtopic=758&b=1&st=&p=&#entry Defence stuff inparticular]
* [http://www.darwinbots.com/Forum/index.php?showtopic=744&b=1&st=&p=&#entry Solar Sun]
* A small but expansive collection of bots, settings, saved simulations, and scripts to provide a very effective and compact program for new users to experiment with.

==New Install==
[[New Install 2.5]]

==Contact==
If you would like to help with the code, and any of the above sound interesting or do able, feel free to contact Numsgil at Numsgil2002@yahoo.com to discuss your ideas.

Physics

2006-04-16T18:22:12Z

216.249.144.14:

The below link (if it ever activates again) was invaluable for designing the tie drag physics:

[http://www.fluidmech.net/jscalc/cdcal26.htm FluidMech]

New tie paradigm

2006-04-14T22:42:54Z

216.249.144.14: /* Sysvars */

For the C++ version (2.5), all old tie sysvars are thrown out. Here's the comprehensive list of all the new tie commands and sysvars:

== Commands ==
*readtie - If settie is set (ie: not 0) writetie takes 1 value from the stack, representing the memory location to be read from, and places a value on the stack representing the value at that location through the tie. If settie is positive, and points to a phase representing more than one tie, the returned values are averaged for each robot thus pointed to.

:.nrg readtie will read the value stored in .nrg from the bot connected through the current tie.
*writetie - If settie is set (ie: not 0) writetie takes 2 values from the stack. 10 .up writetie will place 10 at the location specified (.up) in whichever bots are at the other end of the tie(s) settie addresses.

:When settie isn't set, writetie removes an extra value from the stack to represent the tie being pointed to. ie: -1 10 .up writetie to write to tie -1.

:If a negative memory location is specified (ie: 10 -1 writetie) substance transfer is initiated. 10 -1 writetie would transfer 10 units of energy from the tie being pointed to. If settie is unset, this vesion also takes an additional value form the stack.
*settie - Sets the current tie that the DNA is looking at. When a new tie is set, all the sysvars update for the new information from that tie. Negative nubmers specify a physical tie in the internal array. Positive numbers specifies a tie phase. Multiple ties can be addressed through a single tie phase.
*nexttie - settie's to the next tie. If settie is currently set to negative (ie: internal arrays) it finds the next tie in the internal array. If the present tie is already at the end, it moves back to the beginning. If the present tie is positive, nexttie finds the next valid tie phase, looping back to the lowest tie phase if it's already at the highest. If settie is unset (ie: set to 0) nexttie pushes it to first internal tie (ie: a negative).

== Sysvars ==
*readtielen - A read sysvar. Reads back the length of the current tie.

*writetielen - A read/write sysvar. reads back the ties natural length. If this value is overwritten, the ties natural length is set to the new value.

*tieangle - A read sysvar. Reads back the relative angle of the tie with respect to the bot's eye.

*tie - Attempts to form a tie with the specified phase. Since phases are limited to [1, 200], a value greater than 200 will be modded by 200. A negative value's sign will be flipped then modded 200.

*deltie - If settie is set and the number stored is non negative, the current tie(s) selected are deleted. If settie is not set, the tie phase (positive values) or tie index (negative values) matching the value is deleted.

*currtie - The value that settie is set to. A read sysvar.

*tieK - A read/write sysvar, set to the present spring coefficient. Overwrite and set the spring coefficient of the current tie to a new value (and pay the difference in potential energy).

*tieB - A read/write sysvar, set to the present damping constant. Overwrite and set the damping constant of the current tie to a new value.(and pay the difference in potential energy).

*tietype - Set the kind of constraints the tie uses. example:
*# - Spring (apply a damped spring force)
*# - Rope (offer no resistance until the natural length is reached, then create infinite resistance)
*# - Repulsor (offer no resistance as long as length is greater than the natural length. If the length is less than the natural length, create an infinite repulsive force).
*# - Rod - keep the ties length exactly at the natural length using constraints. Will basically be like a rigid rod is connecting the bots, making the bots into a rigid body.

*numties - Returns the number of phsyical ties connected to the bot.

*birthtietype - Similar to tietype, sets the type of tie that birth ties turn into when they harden. If 0 is specified, birth ties atrophy after 100 cycles.

== Tie Notes ==
*Ports - The internal array index is referred to as a tie's "port". Each tie has a unique port. Each port may or may not have a tie. Port ranges are set by the number of ties in existance when a new tie is formed. Ties always fill in the first gap in the internal tie array.

*Phase - The phase of a tie is a way of addressing multiple ties at once. Each tie has a unique phase. Phases may exist anywhere in the mod range [1,200]. That is, 1 = 201 = 401.

*Length - Max tie length will be 1000, after which all ties become 100% rigid and acts like a stiff rod. This includes birth ties. A later feature will be that the max tie length is a function of the amount of material (nrg) used in its construction. Ties' diameter will stretch and shrink as the tie does. Ties won't be allowed to go below a certain diameter. This diameter will also effect the bandwidth (that is, the max throughput) allowed in sharing/stealing substances.

*Birth Ties - Spring ties that after 100 cycles die off or harden depending on the value set on birthtietype. Birth ties are only formed between a mother and child bot at the moment of reproduction.

New tie paradigm

2006-04-14T22:37:41Z

216.249.144.14: /* Commands */

For the C++ version (2.5), all old tie sysvars are thrown out. Here's the comprehensive list of all the new tie commands and sysvars:

== Commands ==
*readtie - If settie is set (ie: not 0) writetie takes 1 value from the stack, representing the memory location to be read from, and places a value on the stack representing the value at that location through the tie. If settie is positive, and points to a phase representing more than one tie, the returned values are averaged for each robot thus pointed to.

:.nrg readtie will read the value stored in .nrg from the bot connected through the current tie.
*writetie - If settie is set (ie: not 0) writetie takes 2 values from the stack. 10 .up writetie will place 10 at the location specified (.up) in whichever bots are at the other end of the tie(s) settie addresses.

:When settie isn't set, writetie removes an extra value from the stack to represent the tie being pointed to. ie: -1 10 .up writetie to write to tie -1.

:If a negative memory location is specified (ie: 10 -1 writetie) substance transfer is initiated. 10 -1 writetie would transfer 10 units of energy from the tie being pointed to. If settie is unset, this vesion also takes an additional value form the stack.
*settie - Sets the current tie that the DNA is looking at. When a new tie is set, all the sysvars update for the new information from that tie. Negative nubmers specify a physical tie in the internal array. Positive numbers specifies a tie phase. Multiple ties can be addressed through a single tie phase.
*nexttie - settie's to the next tie. If settie is currently set to negative (ie: internal arrays) it finds the next tie in the internal array. If the present tie is already at the end, it moves back to the beginning. If the present tie is positive, nexttie finds the next valid tie phase, looping back to the lowest tie phase if it's already at the highest. If settie is unset (ie: set to 0) nexttie pushes it to first internal tie (ie: a negative).

== Sysvars ==
*readtielen - A read sysvar. Reads back the length of the current tie.

*writetielen - A read/write sysvar. reads back the ties natural length. If this value is overwritten, the ties natural length is set to the new value.

*tieangle - A read sysvar. Reads back the relative angle of the tie with respect to the bot's eye.

*tie - Attempts to form a tie with the specified phase. Since phases are limited to [1, 200], a value greater than 200 will be modded by 200. A negative value's sign will be flipped then modded 200.

*deltie - If settie is set and the number stored is non negative, the current tie(s) selected are deleted. If settie is not set, the tie phase (positive values) or tie index (negative values) matching the value is deleted.

*currtie - The value that settie is set to. A read sysvar.

*setK - A read/write sysvar, set to the present spring coefficient. Overwrite and set the spring coefficient of the current tie to a new value (and pay the difference in potential energy).

*setB - A read/write sysvar, set to the present damping constant. Overwrite and set the damping constant of the current tie to a new value.(and pay the difference in potential energy).

*tietype - Set the kind of constraints the tie uses. example:
*# - Spring (apply a damped spring force)
*# - Rope (offer no resistance until the natural length is reached, then create infinite resistance)
*# - Repulsor (offer no resistance as long as length is greater than the natural length. If the length is less than the natural length, create an infinite repulsive force).
*# - Rod - keep the ties length exactly at the natural length using constraints. Will basically be like a rigid rod is connecting the bots, making the bots into a rigid body.

*numties - Returns the number of phsyical ties connected to the bot.

*birthtietype - Similar to tietype, sets the type of tie that birth ties turn into when they harden. If 0 is specified, birth ties atrophy after 100 cycles.

== Tie Notes ==
*Ports - The internal array index is referred to as a tie's "port". Each tie has a unique port. Each port may or may not have a tie. Port ranges are set by the number of ties in existance when a new tie is formed. Ties always fill in the first gap in the internal tie array.

*Phase - The phase of a tie is a way of addressing multiple ties at once. Each tie has a unique phase. Phases may exist anywhere in the mod range [1,200]. That is, 1 = 201 = 401.

*Length - Max tie length will be 1000, after which all ties become 100% rigid and acts like a stiff rod. This includes birth ties. A later feature will be that the max tie length is a function of the amount of material (nrg) used in its construction. Ties' diameter will stretch and shrink as the tie does. Ties won't be allowed to go below a certain diameter. This diameter will also effect the bandwidth (that is, the max throughput) allowed in sharing/stealing substances.

*Birth Ties - Spring ties that after 100 cycles die off or harden depending on the value set on birthtietype. Birth ties are only formed between a mother and child bot at the moment of reproduction.

New tie paradigm

2006-04-14T22:08:46Z

216.249.144.14: Not done yet

C plus plus version

2006-04-14T21:58:00Z

216.249.144.14: /* Presently, the following needs to be finished before a "BETA" can be achieved: */

==News and Updates==
(11 April 2006) I haven't actually finished anymore of the remaining features, but I ''have'' been working on all of them, and fixing alot of major bugs. Everything has been started, I just need to finish them all. The only large piece of work left that hasn't been started is the Bot Debug controls. A control does exist for it, but it needs to basically be rewritten to be smoother and easier to use, which calls for a complete reorganization of the code architecture. In addition I still need to get the robot mouse selection code to work.

(05 Feb 2006) The C++ version is nearing completion. It might even be possible to have a beta done by the end of the month, but it means Numsgil needs to really put some effort in, and he's sort of tired of programming. If you know any C++ and want to help, I assure you we'll welcome you with open arms!

== Reasons for Language switch ==

#If you're wondering why we're switching, it's because VB is for relatively simple, GUI based programs. Darwinbots is neither simple nor gui based. C++, on the other hand is a powerful language, but it has a higher development cost. [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controversy]
#Visual Basic does not intrinsically support pointers. As such, complex data structures become something of a chore to try and make.
#Numsgil knows more about C++ than he knows about Visual Basic.
#C++ can be made to be portable (say, we could make a Linux version). And presently the code is being developed with portability in mind (though as yet untested).

== Accessing the Current Code ==
The code is in an online version control system called [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

To access the SVN, you should download a SVN client. The one I found that I like the most is called [http://www.smartsvn.com/smartsvn/index.html Smart SVN]. Its basic (and more than adequate) version is free. You may also want to try [http://tortoisesvn.tigris.org/ TortoiseSVN], which integrates with Windows Explorer.

The SVN for Darwinbots is located at:

* [http://opensvn.csie.org/Darwinbots http://opensvn.csie.org/Darwinbots]
* [https://opensvn.csie.org/Darwinbots https://opensvn.csie.org/Darwinbots] secure server

'''Read only access is open to everyone. If you want to contribute to the code, you'll need Numsgil to give you a username and password.''' He can be reached at Numsgil2002@yahoo.com

== Code Dependencies ==
To get the code to compile and work, you'll need the following:

#A C++ compiler. [http://www.bloodshed.net/devcpp.html Dev-C++] is free, but there have been some issues with it conflicting with Microsoft Visual C++ 6.0 (which Numsgil uses, and hence is the officially supported environment). If you don't have MSVC++ 6.0 and would like it, contact Numsgil at Numsgil2002@yahoo.com
#OpenGL libraries. Specifically, the code must link to glut32.lib, opengl32.lib, and glu32.lib. You probably have these on your computer somewhere, but if you don't, [http://www.opengl.org/resources/faq/getting_started.html this site will help you]
#Fox GUI Toolkit. This is the library which allows Darwinbots to have a GUI at all. [http://www.fox-toolkit.org/ FOX GUI Homepage].
#The STLport for MSVC++ 6.0 if you have MSVC. Dev-C++ won't need this. It can be found at [http://www.ogre3d.org/index.php?option=com_remository&Itemid=57&func=selectcat&cat=1 The Ogre 3D engine download page]. It should be listed at the bottom of the page. This makes MSVC a bit more ANSI compliant, among other things. There are some rather nitpicky specifics you need to address to get the stlport working properly (that is, working without compile or link errors). At the time of this writing (March 2006) [http://www.ogre3d.org/wiki/index.php/Building_From_Source This Ogre wiki page on building the Ogre source] demonstrates what you need to do to get the stlport working properly. Just scroll down to the section called "stlport".
#I don't know how it works for Dev-C++, but if you run MSVC you must be sure that you select the Multithreaded libraries or you'll probably get an error. To set this, inside MSVC in your project go to project->settings. Go to the C/C++ tab, change category "General" to category "Code Generation". The new upper right hand corner drop box will let you set if you're using multithreaded/singlethreaded libraries.
#Fox GUI requires that you include wsock32.lib. Without it, you will get a single linker error (it will try and find gethostname and fail).

If you have any problems at all with any of the above steps, or want to help Numsgil make the process a bit smoother and have some ideas, contact him at Numsgil2002@yahoo.com.

== Coding Style ==
The official policy is that as long as Numsgil understands what's going on in your code, your style is fine. If you want to have a more uniform coding style throughout the code, this is the style Numsgil uses:

for(unsigned int x = 0; x < 10; x++)
{
cout << x; //notice the 4 space tab
}

You are welcome to follow it.

== Coding Doctrine ==
The goal of the code is two things:

#Speed
#Readability

Wherever speed is not an issue (as in 97% of the code) coders are encouraged to make the code as readable to newbies as possible. Imagine your mother's life depends on her deciphering your code and you won't be around to help. That means no clever programming tricks, and sparing use of any standard libraries and especially templates and inheritance and polymorphism and other "advanced" concepts.

== To Do List (updated sparingly) ==
Feb 05 2006

Updated April 13 2006
===Presently, the following needs to be finished before a "BETA" can be achieved:===

*<s>The GUI needs to be finished and integrated with the options data structure</s>
**The Physics Dropdown menus needs to be connected
**The Pond Mode gradient picute needs to be created
**The Robot Placement controls need to be created
*<s>Physics for robots needs to be finished (specifically, velocity limiting code and non-in-elastic collisions)</s>
*<s>-3, -4, -5, and -6 shots need to be finished,</s> as well as viruses (though viruses may be disabled in the initial release depending)
**power shots need to be implemented.
*Ties need to be coded using the new Tie paradigm discussed [http://forum.darwinbots.com/index.php?showtopic=560 here] and summarized on the [[new tie paradigm]] page
*The Robot Debugging window and robot mouse selection need to be finished.
*The graphics and engine need to be made thread safe.
*Mutations code needs to be finished (currently Sprotiel is working on this)
*Forward and backward compatible save/load routines for <s>Simulation Settings</s>, Simulations, and Robots. Preferably ascii over binary, except where size is an issue (as in Simulations), where some sort of file compression would be nice.
**<s>Save Settings</s>
**<s>Load Settings</s>
**Save Organism
**Load Organism
**Save Simulation
**Load Simulation

===These would be nice, but aren't 100% necessary for the "Beta" label===

*Scripts. PY was working on the idea of what they should be, so he should be consulted.
*Error Database. Basically, on an error an automatic report could be sent to one of the MYSQL databases available through our webspace and a notification sent to anyone working on the code automatically. Also, some sort of error viewer inside Darwinbots would be nice, so users could see how many other users reported the error they received and whether or not it's been addressed by the coders yet.
*Bot Database. A way to upload and download bots from a central database from inside Darwinbots itself. Also using a Database as described above (we have 10 of the things, we won't run out :P)
*Statistical tools. This would involve everything from collecting data from the sim (and analyzing it according to proper statistical tests) to building a graph form and deciding how to draw it to exporting the data as per user specs into a spreadsheet program (like Excel). It is prefered that whoever works on this have some statistics background so they know what sort of stats users would want to collect and test.
*The vision testing algorithm is presently O(n^2), as it uses the "brute force" method. See: [[Vision_algorithm ]] for more info. It can be made nearly linear O(n) by using uniform grid cells. see:

:[http://yallara.cs.rmit.edu.au/~mawurm/cosc1224/asst1/index.xhtml This resource which examines the issue]

:[http://www.harveycartel.org/metanet/tutorials/tutorialB.html This resource which describes the implementation and problems associated with it]

:Collision detection could use a similar technique, though its gains would be complicated by the fact that bots are not uniform in size.

:This would mean an absolutely insane boost in speed for large sims, but also would take some work.
*Since graphics are now using OpenGL, some pretty sweet graphics could be made. Admittedly spheres/circles shooting dots and lines at each other doesn't really inspire great art, but I think there's definitely potential for some sweet demos. Maybe move it to 3D graphics instead of 2D and use some fog effects. Maybe use a shader.

===Long standing feature requests===
Anyone who managed to implement these in a way that didn't drastically increase memory and CPU requirements would be a hero in the Darwinbots community.

*[[Environment Grid]] - Basically the idea that bots should be able to interact with their physical environment. Things like leave poop behind for other bots to deal with, pollute their environment, leave pheromone trails for other bots to follow, etc. There are, unfortunately, some gigantic memory and processing problems that beg for some smart, algorithm-savvy programmer to address.

*[[Metabolism]] - The idea that bots should be able to generate nrg or use nrg based on their own unique bio-chemistry (or is it darwo-chemistry :P). This involves creating a system (or letting it emerge) of bio-chemical pathways and materials. Closely tied with the Environment Grid and likewise inter-related with the memory and processing problems.

*[[Specialization | Specialization and Speciation]] - The idea that bots should be able to become more efficient as they limit the number of activities they participate in. The primary hurdle isn't in coding it, but in designing the basic system to everyone's desires. It must respect multicellular specialization as well as single celled speciation. Not an easy task.

*[[Sexual Reproduction]] - Some way for two bots to, with consent (although 'rape' might have a place as well), produce offspring that robustly intermarries the two parents' DNA.

==New Install==
[[New Install 2.5]]

==Contact==
If you would like to help with the code, and any of the above sound interesting or do able, feel free to contact Numsgil at Numsgil2002@yahoo.com to discuss your ideas.

C plus plus version

2006-04-14T18:02:37Z

216.249.144.14: /* These would be nice, but aren't 100% necessary for the "Beta" label */ sp

==News and Updates==
(11 April 2006) I haven't actually finished anymore of the remaining features, but I ''have'' been working on all of them, and fixing alot of major bugs. Everything has been started, I just need to finish them all. The only large piece of work left that hasn't been started is the Bot Debug controls. A control does exist for it, but it needs to basically be rewritten to be smoother and easier to use, which calls for a complete reorganization of the code architecture. In addition I still need to get the robot mouse selection code to work.

(05 Feb 2006) The C++ version is nearing completion. It might even be possible to have a beta done by the end of the month, but it means Numsgil needs to really put some effort in, and he's sort of tired of programming. If you know any C++ and want to help, I assure you we'll welcome you with open arms!

== Reasons for Language switch ==

#If you're wondering why we're switching, it's because VB is for relatively simple, GUI based programs. Darwinbots is neither simple nor gui based. C++, on the other hand is a powerful language, but it has a higher development cost. [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controversy]
#Visual Basic does not intrinsically support pointers. As such, complex data structures become something of a chore to try and make.
#Numsgil knows more about C++ than he knows about Visual Basic.
#C++ can be made to be portable (say, we could make a Linux version). And presently the code is being developed with portability in mind (though as yet untested).

== Accessing the Current Code ==
The code is in an online version control system called [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

To access the SVN, you should download a SVN client. The one I found that I like the most is called [http://www.smartsvn.com/smartsvn/index.html Smart SVN]. Its basic (and more than adequate) version is free. You may also want to try [http://tortoisesvn.tigris.org/ TortoiseSVN], which integrates with Windows Explorer.

The SVN for Darwinbots is located at:

* [http://opensvn.csie.org/Darwinbots http://opensvn.csie.org/Darwinbots]
* [https://opensvn.csie.org/Darwinbots https://opensvn.csie.org/Darwinbots] secure server

'''Read only access is open to everyone. If you want to contribute to the code, you'll need Numsgil to give you a username and password.''' He can be reached at Numsgil2002@yahoo.com

== Code Dependencies ==
To get the code to compile and work, you'll need the following:

#A C++ compiler. [http://www.bloodshed.net/devcpp.html Dev-C++] is free, but there have been some issues with it conflicting with Microsoft Visual C++ 6.0 (which Numsgil uses, and hence is the officially supported environment). If you don't have MSVC++ 6.0 and would like it, contact Numsgil at Numsgil2002@yahoo.com
#OpenGL libraries. Specifically, the code must link to glut32.lib, opengl32.lib, and glu32.lib. You probably have these on your computer somewhere, but if you don't, [http://www.opengl.org/resources/faq/getting_started.html this site will help you]
#Fox GUI Toolkit. This is the library which allows Darwinbots to have a GUI at all. [http://www.fox-toolkit.org/ FOX GUI Homepage].
#The STLport for MSVC++ 6.0 if you have MSVC. Dev-C++ won't need this. It can be found at [http://www.ogre3d.org/index.php?option=com_remository&Itemid=57&func=selectcat&cat=1 The Ogre 3D engine download page]. It should be listed at the bottom of the page. This makes MSVC a bit more ANSI compliant, among other things. There are some rather nitpicky specifics you need to address to get the stlport working properly (that is, working without compile or link errors). At the time of this writing (March 2006) [http://www.ogre3d.org/wiki/index.php/Building_From_Source This Ogre wiki page on building the Ogre source] demonstrates what you need to do to get the stlport working properly. Just scroll down to the section called "stlport".
#I don't know how it works for Dev-C++, but if you run MSVC you must be sure that you select the Multithreaded libraries or you'll probably get an error. To set this, inside MSVC in your project go to project->settings. Go to the C/C++ tab, change category "General" to category "Code Generation". The new upper right hand corner drop box will let you set if you're using multithreaded/singlethreaded libraries.
#Fox GUI requires that you include wsock32.lib. Without it, you will get a single linker error (it will try and find gethostname and fail).

If you have any problems at all with any of the above steps, or want to help Numsgil make the process a bit smoother and have some ideas, contact him at Numsgil2002@yahoo.com.

== Coding Style ==
The official policy is that as long as Numsgil understands what's going on in your code, your style is fine. If you want to have a more uniform coding style throughout the code, this is the style Numsgil uses:

for(unsigned int x = 0; x < 10; x++)
{
cout << x; //notice the 4 space tab
}

You are welcome to follow it.

== Coding Doctrine ==
The goal of the code is two things:

#Speed
#Readability

Wherever speed is not an issue (as in 97% of the code) coders are encouraged to make the code as readable to newbies as possible. Imagine your mother's life depends on her deciphering your code and you won't be around to help. That means no clever programming tricks, and sparing use of any standard libraries and especially templates and inheritance and polymorphism and other "advanced" concepts.

== To Do List (updated sparingly) ==
Feb 05 2006

Updated April 13 2006
===Presently, the following needs to be finished before a "BETA" can be achieved:===

*<s>The GUI needs to be finished and integrated with the options data structure</s>
**The Physics Dropdown menus needs to be connected
**The Pond Mode gradient picute needs to be created
**The Robot Placement controls need to be created
*<s>Physics for robots needs to be finished (specifically, velocity limiting code and non-in-elastic collisions)</s>
*<s>-3, -4, -5, and -6 shots need to be finished,</s> as well as viruses (though viruses may be disabled in the initial release depending)
**power shots need to be implemented.
*Ties need to be coded using the new Tie paradigm discussed [http://forum.darwinbots.com/index.php?showtopic=560 here]
*The Robot Debugging window and robot mouse selection need to be finished.
*The graphics and engine need to be made thread safe.
*Mutations code needs to be finished (currently Sprotiel is working on this)
*Forward and backward compatible save/load routines for <s>Simulation Settings</s>, Simulations, and Robots. Preferably ascii over binary, except where size is an issue (as in Simulations), where some sort of file compression would be nice.
**<s>Save Settings</s>
**<s>Load Settings</s>
**Save Organism
**Load Organism
**Save Simulation
**Load Simulation

===These would be nice, but aren't 100% necessary for the "Beta" label===

*Scripts. PY was working on the idea of what they should be, so he should be consulted.
*Error Database. Basically, on an error an automatic report could be sent to one of the MYSQL databases available through our webspace and a notification sent to anyone working on the code automatically. Also, some sort of error viewer inside Darwinbots would be nice, so users could see how many other users reported the error they received and whether or not it's been addressed by the coders yet.
*Bot Database. A way to upload and download bots from a central database from inside Darwinbots itself. Also using a Database as described above (we have 10 of the things, we won't run out :P)
*Statistical tools. This would involve everything from collecting data from the sim (and analyzing it according to proper statistical tests) to building a graph form and deciding how to draw it to exporting the data as per user specs into a spreadsheet program (like Excel). It is prefered that whoever works on this have some statistics background so they know what sort of stats users would want to collect and test.
*The vision testing algorithm is presently O(n^2), as it uses the "brute force" method. See: [[Vision_algorithm ]] for more info. It can be made nearly linear O(n) by using uniform grid cells. see:

:[http://yallara.cs.rmit.edu.au/~mawurm/cosc1224/asst1/index.xhtml This resource which examines the issue]

:[http://www.harveycartel.org/metanet/tutorials/tutorialB.html This resource which describes the implementation and problems associated with it]

:Collision detection could use a similar technique, though its gains would be complicated by the fact that bots are not uniform in size.

:This would mean an absolutely insane boost in speed for large sims, but also would take some work.
*Since graphics are now using OpenGL, some pretty sweet graphics could be made. Admittedly spheres/circles shooting dots and lines at each other doesn't really inspire great art, but I think there's definitely potential for some sweet demos. Maybe move it to 3D graphics instead of 2D and use some fog effects. Maybe use a shader.

===Long standing feature requests===
Anyone who managed to implement these in a way that didn't drastically increase memory and CPU requirements would be a hero in the Darwinbots community.

*[[Environment Grid]] - Basically the idea that bots should be able to interact with their physical environment. Things like leave poop behind for other bots to deal with, pollute their environment, leave pheromone trails for other bots to follow, etc. There are, unfortunately, some gigantic memory and processing problems that beg for some smart, algorithm-savvy programmer to address.

*[[Metabolism]] - The idea that bots should be able to generate nrg or use nrg based on their own unique bio-chemistry (or is it darwo-chemistry :P). This involves creating a system (or letting it emerge) of bio-chemical pathways and materials. Closely tied with the Environment Grid and likewise inter-related with the memory and processing problems.

*[[Specialization | Specialization and Speciation]] - The idea that bots should be able to become more efficient as they limit the number of activities they participate in. The primary hurdle isn't in coding it, but in designing the basic system to everyone's desires. It must respect multicellular specialization as well as single celled speciation. Not an easy task.

*[[Sexual Reproduction]] - Some way for two bots to, with consent (although 'rape' might have a place as well), produce offspring that robustly intermarries the two parents' DNA.

==Contact==
If you would like to help with the code, and any of the above sound interesting or do able, feel free to contact Numsgil at Numsgil2002@yahoo.com to discuss your ideas.

C plus plus version

2006-04-14T17:51:12Z

216.249.144.14: /* Presently, the following needs to be finished before a "BETA" can be achieved: */

==News and Updates==
(11 April 2006) I haven't actually finished anymore of the remaining features, but I ''have'' been working on all of them, and fixing alot of major bugs. Everything has been started, I just need to finish them all. The only large piece of work left that hasn't been started is the Bot Debug controls. A control does exist for it, but it needs to basically be rewritten to be smoother and easier to use, which calls for a complete reorganization of the code architecture. In addition I still need to get the robot mouse selection code to work.

(05 Feb 2006) The C++ version is nearing completion. It might even be possible to have a beta done by the end of the month, but it means Numsgil needs to really put some effort in, and he's sort of tired of programming. If you know any C++ and want to help, I assure you we'll welcome you with open arms!

== Reasons for Language switch ==

#If you're wondering why we're switching, it's because VB is for relatively simple, GUI based programs. Darwinbots is neither simple nor gui based. C++, on the other hand is a powerful language, but it has a higher development cost. [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controversy]
#Visual Basic does not intrinsically support pointers. As such, complex data structures become something of a chore to try and make.
#Numsgil knows more about C++ than he knows about Visual Basic.
#C++ can be made to be portable (say, we could make a Linux version). And presently the code is being developed with portability in mind (though as yet untested).

== Accessing the Current Code ==
The code is in an online version control system called [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

To access the SVN, you should download a SVN client. The one I found that I like the most is called [http://www.smartsvn.com/smartsvn/index.html Smart SVN]. Its basic (and more than adequate) version is free. You may also want to try [http://tortoisesvn.tigris.org/ TortoiseSVN], which integrates with Windows Explorer.

The SVN for Darwinbots is located at:

* [http://opensvn.csie.org/Darwinbots http://opensvn.csie.org/Darwinbots]
* [https://opensvn.csie.org/Darwinbots https://opensvn.csie.org/Darwinbots] secure server

'''Read only access is open to everyone. If you want to contribute to the code, you'll need Numsgil to give you a username and password.''' He can be reached at Numsgil2002@yahoo.com

== Code Dependencies ==
To get the code to compile and work, you'll need the following:

#A C++ compiler. [http://www.bloodshed.net/devcpp.html Dev-C++] is free, but there have been some issues with it conflicting with Microsoft Visual C++ 6.0 (which Numsgil uses, and hence is the officially supported environment). If you don't have MSVC++ 6.0 and would like it, contact Numsgil at Numsgil2002@yahoo.com
#OpenGL libraries. Specifically, the code must link to glut32.lib, opengl32.lib, and glu32.lib. You probably have these on your computer somewhere, but if you don't, [http://www.opengl.org/resources/faq/getting_started.html this site will help you]
#Fox GUI Toolkit. This is the library which allows Darwinbots to have a GUI at all. [http://www.fox-toolkit.org/ FOX GUI Homepage].
#The STLport for MSVC++ 6.0 if you have MSVC. Dev-C++ won't need this. It can be found at [http://www.ogre3d.org/index.php?option=com_remository&Itemid=57&func=selectcat&cat=1 The Ogre 3D engine download page]. It should be listed at the bottom of the page. This makes MSVC a bit more ANSI compliant, among other things. There are some rather nitpicky specifics you need to address to get the stlport working properly (that is, working without compile or link errors). At the time of this writing (March 2006) [http://www.ogre3d.org/wiki/index.php/Building_From_Source This Ogre wiki page on building the Ogre source] demonstrates what you need to do to get the stlport working properly. Just scroll down to the section called "stlport".
#I don't know how it works for Dev-C++, but if you run MSVC you must be sure that you select the Multithreaded libraries or you'll probably get an error. To set this, inside MSVC in your project go to project->settings. Go to the C/C++ tab, change category "General" to category "Code Generation". The new upper right hand corner drop box will let you set if you're using multithreaded/singlethreaded libraries.
#Fox GUI requires that you include wsock32.lib. Without it, you will get a single linker error (it will try and find gethostname and fail).

If you have any problems at all with any of the above steps, or want to help Numsgil make the process a bit smoother and have some ideas, contact him at Numsgil2002@yahoo.com.

== Coding Style ==
The official policy is that as long as Numsgil understands what's going on in your code, your style is fine. If you want to have a more uniform coding style throughout the code, this is the style Numsgil uses:

for(unsigned int x = 0; x < 10; x++)
{
cout << x; //notice the 4 space tab
}

You are welcome to follow it.

== Coding Doctrine ==
The goal of the code is two things:

#Speed
#Readability

Wherever speed is not an issue (as in 97% of the code) coders are encouraged to make the code as readable to newbies as possible. Imagine your mother's life depends on her deciphering your code and you won't be around to help. That means no clever programming tricks, and sparing use of any standard libraries and especially templates and inheritance and polymorphism and other "advanced" concepts.

== To Do List (updated sparingly) ==
Feb 05 2006

Updated April 13 2006
===Presently, the following needs to be finished before a "BETA" can be achieved:===

*<s>The GUI needs to be finished and integrated with the options data structure</s>
**The Physics Dropdown menus needs to be connected
**The Pond Mode gradient picute needs to be created
**The Robot Placement controls need to be created
*<s>Physics for robots needs to be finished (specifically, velocity limiting code and non-in-elastic collisions)</s>
*<s>-3, -4, -5, and -6 shots need to be finished,</s> as well as viruses (though viruses may be disabled in the initial release depending)
**power shots need to be implemented.
*Ties need to be coded using the new Tie paradigm discussed [http://forum.darwinbots.com/index.php?showtopic=560 here]
*The Robot Debugging window and robot mouse selection need to be finished.
*The graphics and engine need to be made thread safe.
*Mutations code needs to be finished (currently Sprotiel is working on this)
*Forward and backward compatible save/load routines for <s>Simulation Settings</s>, Simulations, and Robots. Preferably ascii over binary, except where size is an issue (as in Simulations), where some sort of file compression would be nice.
**<s>Save Settings</s>
**<s>Load Settings</s>
**Save Organism
**Load Organism
**Save Simulation
**Load Simulation

===These would be nice, but aren't 100% necessary for the "Beta" label===

*Scripts. PY was working on the idea of what they should be, so he should be consulted.
*Error Database. Basically, on an error an automatic report could be sent to one of the MYSQL databases available through our webspace and a notification sent to anyone working on the code automatically. Also, some sort of error viewer inside Darwinbots would be nice, so users could see how many other users reported the error they received and whether or not it's been addressed by the coders yet.
*Bot Database. A way to upload and download bots from a central database from inside Darwinbots itself. Also using a Database as described above (we have 10 of the things, we won't run out :P)
*Statistical tools. This would involve everything from collecting data from the sim (and analyzing it according to proper statistical tests) to building a graph form and deciding how to draw it to exporting the data as per user specs into a spreadsheet program (like Excel). It is prefered that whoever works on this have some statistics background so they know what sort of stats users would want to collect and test.
*The vision testing algorithm is presently O(n^2), as it uses the "brute force" method. See: [[Vision_algorithm ]] for more inofo. It can be made nearly linear O(n) by using uniform grid cells. see:

:[http://yallara.cs.rmit.edu.au/~mawurm/cosc1224/asst1/index.xhtml This resource which examines the issue]

:[http://www.harveycartel.org/metanet/tutorials/tutorialB.html This resource which describes the implementation and problems associated with it]

:Collision detection could use a similar technique, though its gains would be complicated by the fact that bots are not uniform in size.

:This would mean an absolutely insane boost in speed for large sims, but also would take some work.
*Since graphics are now using OpenGL, some pretty sweet graphics could be made. Admittedly spheres/circles shooting dots and lines at each other doesn't really inspire great art, but I think there's definitely potential for some sweet demos. Maybe move it to 3D graphics instead of 2D and use some fog effects. Maybe use a shader.

===Long standing feature requests===
Anyone who managed to implement these in a way that didn't drastically increase memory and CPU requirements would be a hero in the Darwinbots community.

*[[Environment Grid]] - Basically the idea that bots should be able to interact with their physical environment. Things like leave poop behind for other bots to deal with, pollute their environment, leave pheromone trails for other bots to follow, etc. There are, unfortunately, some gigantic memory and processing problems that beg for some smart, algorithm-savvy programmer to address.

*[[Metabolism]] - The idea that bots should be able to generate nrg or use nrg based on their own unique bio-chemistry (or is it darwo-chemistry :P). This involves creating a system (or letting it emerge) of bio-chemical pathways and materials. Closely tied with the Environment Grid and likewise inter-related with the memory and processing problems.

*[[Specialization | Specialization and Speciation]] - The idea that bots should be able to become more efficient as they limit the number of activities they participate in. The primary hurdle isn't in coding it, but in designing the basic system to everyone's desires. It must respect multicellular specialization as well as single celled speciation. Not an easy task.

*[[Sexual Reproduction]] - Some way for two bots to, with consent (although 'rape' might have a place as well), produce offspring that robustly intermarries the two parents' DNA.

==Contact==
If you would like to help with the code, and any of the above sound interesting or do able, feel free to contact Numsgil at Numsgil2002@yahoo.com to discuss your ideas.

C plus plus version

2006-02-25T21:28:50Z

216.249.144.14: /* To Do List (updated sparringly) */

==News and Updates==

(05 Feb 2006) The C++ version is nearing completion. It might even be possible to have a beta done by the end of the month, but it means Numsgil needs to really put some effort in, and he's sort of tired of programming. If you know any C++ and want to help, I assure you we'll welcome you with open arms!

== Reasons for Language switch ==

#If you're wondering why we're switching, it's because VB is for relatively simple, GUI based programs. Darwinbots is neither simple nor gui based. C++, on the other hand is a powerfull language, but it has a higher development cost. [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controvercy]
#Visual Basic does not intrinsically support pointers. As such, complex data structures become something of a chore to try and make.
#Numsgil knows more about C++ than he knows about Visual Basic.
#C++ can be made to be portable (say, we could make a Linux version). And presently the code is being developed with portability in mind (though as yet untested).

== Accessing the Current Code ==
The code is in an online version control system called [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

To access the SVN, you should download a SVN client. The one I found that I like the most is called [http://www.smartsvn.com/smartsvn/index.html Smart SVN]. Its basic (and more than adequate) version is free.

The SVN for Darwinbots is located at:

* [http://opensvn.csie.org/Darwinbots http://opensvn.csie.org/Darwinbots]
* [https://opensvn.csie.org/Darwinbots https://opensvn.csie.org/Darwinbots] secure server

'''Read only access is open to everyone. If you want to contribute to the code, you'll need Numsgil to give you a username and password.''' He can be reached at Numsgil2002@yahoo.com

== Code Dependencies ==
To get the code to compile and work, you'll need the following:

#A C++ compiler. [http://www.bloodshed.net/devcpp.html Dev-C++] is free, but there have been some issues with it conflicting with Microsoft Visual C++ 6.0 (which Numsgil uses, and hence is the officially supported environment). If you don't have MSVC++ 6.0 and would like it, contact Numsgil at Numsgil2002@yahoo.com
#OpenGL libraries. Specifically, the code must link to glut32.lib, opengl32.lib, and glu32.lib. You probably have these on your computer somewhere, but if you don't, [http://www.opengl.org/resources/faq/getting_started.html this site will help you]
#Fox GUI Toolkit. This is the library which allows Darwinbots to have a GUI at all. [http://www.fox-toolkit.org/ FOX GUI Homepage].
#The STLport for MSVC++ 6.0 if you have MSVC. Dev-C++ won't need this. It can be found at [http://www.ogre3d.org/index.php?option=com_remository&Itemid=57&func=selectcat&cat=1 The Ogre 3D engine download page]. It should be listed at the bottom of the page. This makes MSVC a bit more ANSI compliant, among other things.
#I don't know how it works for Dev-C++, but if you run MSVC you must be sure that you select the Multithreaded libraries or you'll probably get an error. To set this, inside MSVC in your project go to project->settings. Go to the C/C++ tab, change category "General" to category "Code Generation". The new upper right hand corner drop box will let you set if you're using multithreaded/singlethreaded libraries.

If you have any problems at all with any of the above steps, or want to help Numsgil make the process a bit smoother and have some ideas, contact him at Numsgil2002@yahoo.com.

== Coding Style ==
The official policy is that as long as Numsgil understands what's going on in your code, your style is fine. If you want to have a more uniform coding style throughout the code, this is the style Numsgil uses:

for(unsigned int x = 0; x < 10; x++)
{
cout << x; //notice the 4 space tab
}

You are welcome to follow it.

== Coding Doctrine ==
The goal of the code is two things:

#Speed
#Readability

Wherever speed is not an issue (as in 97% of the code) coders are encouraged to make the code as readable to newbies as possible. Imagine your mother's life depends on her deciphering your code and you won't be around to help. That means no clever programming tricks, and sparing use of any standard libraries and especially templates and inheritance and polymorphism and other "advanced" concepts.

== To Do List (updated sparringly) ==
Feb 05 2006

Updated Feb 25 2006
===Presently, the following needs to be finished before a "BETA" can be achieved:===

*The GUI needs to be finished and integrated with the options data structure
*<s>Physics for robots needs to be finished (specifically, velocity limiting code and non-in-elastic collisions)</s>
*<s>-3, -4, -5, and -6 shots need to be finished,</s> as well as viruses (though viruses may be disabled in the initial release depending)
*Ties need to be coded using the new Tie paradigm discussed [http://forum.darwinbots.com/index.php?showtopic=560 here]
*The Robot Debugging window and robot mouse selection need to be finished.
*The graphics and engine need to be made thread safe.
*Mutations code needs to be finished (currently Sprotiel is working on this)
*Forward and backward compatible save/load routines for Simulation Settings, Simulations, and Robots. Preferably ascii over binary, except where size is an issue (as in Simulation settings), where some sort of file compression would be nice.

===These would be nice, but aren't 100% necessary for the "Beta" label===

*Scripts. PY was working on the idea of what they should be, so he should be consulted.
*Error Database. Basically, on an error an automatic report could be sent to one of the MYSQL databases available through our webspace and a notification sent to anyone working on the code automatically. Also, some sort of error viewer inside Darwinbots would be nice, so users could see how many other users reproted the error they recieved and wether or not it's been addressed by the coders yet.
*Bot Database. A way to upload and download bots from a central database from inside Darwinbots itself. Also using a Database as described above (we have 10 of the things, we won't run out :P)
*Statistical tools. This would involve everything from collecting data from the sim (and analyzing it according to proper statistical tests) to building a graph form and deciding how to draw it to exporting the data as per user specs into a spreadsheet program (like Excel). It is prefered that whoever works on this have some statistics background so they know what sort of stats users would want to collect and test.
*The vision testing algorithm is presently O(n^2), as it uses the "brute force" method. See: [[Vision_algorithm ]] for more inofo. It can be made nearly linear O(n) by using uniform grid cells. see:

:[http://yallara.cs.rmit.edu.au/~mawurm/cosc1224/asst1/index.xhtml This resource which exmines the issue]

:[http://www.harveycartel.org/metanet/tutorials/tutorialB.html This resource which describes the implementation and problems associated with it]

:Collision detection could use a similar technique, though its gains would be complicated by the fact that bots are not uniform in size.

:This would mean an absolutely insane boost in speed for large sims, but also would take some work.
*Since graphics are now using OpenGL, some pretty sweet graphics could be made. Admitedly spheres/circles shooting dots and lines at each other doesn't really inspire great art, but I think there's definately potential for some sweet demos. Maybe move it to 3D graphics instead of 2D and use some fog effects. Maybe use a shader.

===Long standing feature requests===
Anyone who managed to implement these in a way that didn't drastically increase memory and CPU requirements would be a hero in the Darwinbots community.

*[[Environment Grid]] - Basically the idea that bots should be able to interact with their physical environment. Things like leave poop behind for other bots to deal with, polute their environment, leave pheremone trails for other bots to follow, etc. There are, unfortunately, some gigantic memory and processing problems that beg for some smart, algorithm-savy programmer to address.

*[[Metabolism]] - The idea that bots should be able to generate nrg or use nrg based on their own unique bio-chemistry (or is it darwo-chemistry :P). This involves creating a system (or letting it emerge) of bio-chemical pathways and materials. Closely tied with the Environment Grid and likewise inter-related with the memory and processing problems.

*[[Specialization | Specialization and Speciation]] - The idea that bots should be able to become more efficient as they limit the number of activities they participate in. The primary hurdle isn't in coding it, but in designing the basic system to everyone's desires. It must respect multicellular specialization as well as single celled speciation. Not an easy task.

*[[Sexual Reproduction]] - Some way for two bots to, with consent (although 'rape' might have a place as well), produce offspring that robustly intermarries the two parents' DNA.

==Contact==
If you would like to help with the code, and any of the above sound interesting or do able, feel free to contact Numsgil at Numsgil2002@yahoo.com to discuss your ideas.

C plus plus version

2006-02-25T21:28:26Z

216.249.144.14: /* Presently, the following needs to be finished before a "BETA" can be achieved: */

==News and Updates==

(05 Feb 2006) The C++ version is nearing completion. It might even be possible to have a beta done by the end of the month, but it means Numsgil needs to really put some effort in, and he's sort of tired of programming. If you know any C++ and want to help, I assure you we'll welcome you with open arms!

== Reasons for Language switch ==

#If you're wondering why we're switching, it's because VB is for relatively simple, GUI based programs. Darwinbots is neither simple nor gui based. C++, on the other hand is a powerfull language, but it has a higher development cost. [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controvercy]
#Visual Basic does not intrinsically support pointers. As such, complex data structures become something of a chore to try and make.
#Numsgil knows more about C++ than he knows about Visual Basic.
#C++ can be made to be portable (say, we could make a Linux version). And presently the code is being developed with portability in mind (though as yet untested).

== Accessing the Current Code ==
The code is in an online version control system called [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

To access the SVN, you should download a SVN client. The one I found that I like the most is called [http://www.smartsvn.com/smartsvn/index.html Smart SVN]. Its basic (and more than adequate) version is free.

The SVN for Darwinbots is located at:

* [http://opensvn.csie.org/Darwinbots http://opensvn.csie.org/Darwinbots]
* [https://opensvn.csie.org/Darwinbots https://opensvn.csie.org/Darwinbots] secure server

'''Read only access is open to everyone. If you want to contribute to the code, you'll need Numsgil to give you a username and password.''' He can be reached at Numsgil2002@yahoo.com

== Code Dependencies ==
To get the code to compile and work, you'll need the following:

#A C++ compiler. [http://www.bloodshed.net/devcpp.html Dev-C++] is free, but there have been some issues with it conflicting with Microsoft Visual C++ 6.0 (which Numsgil uses, and hence is the officially supported environment). If you don't have MSVC++ 6.0 and would like it, contact Numsgil at Numsgil2002@yahoo.com
#OpenGL libraries. Specifically, the code must link to glut32.lib, opengl32.lib, and glu32.lib. You probably have these on your computer somewhere, but if you don't, [http://www.opengl.org/resources/faq/getting_started.html this site will help you]
#Fox GUI Toolkit. This is the library which allows Darwinbots to have a GUI at all. [http://www.fox-toolkit.org/ FOX GUI Homepage].
#The STLport for MSVC++ 6.0 if you have MSVC. Dev-C++ won't need this. It can be found at [http://www.ogre3d.org/index.php?option=com_remository&Itemid=57&func=selectcat&cat=1 The Ogre 3D engine download page]. It should be listed at the bottom of the page. This makes MSVC a bit more ANSI compliant, among other things.
#I don't know how it works for Dev-C++, but if you run MSVC you must be sure that you select the Multithreaded libraries or you'll probably get an error. To set this, inside MSVC in your project go to project->settings. Go to the C/C++ tab, change category "General" to category "Code Generation". The new upper right hand corner drop box will let you set if you're using multithreaded/singlethreaded libraries.

If you have any problems at all with any of the above steps, or want to help Numsgil make the process a bit smoother and have some ideas, contact him at Numsgil2002@yahoo.com.

== Coding Style ==
The official policy is that as long as Numsgil understands what's going on in your code, your style is fine. If you want to have a more uniform coding style throughout the code, this is the style Numsgil uses:

for(unsigned int x = 0; x < 10; x++)
{
cout << x; //notice the 4 space tab
}

You are welcome to follow it.

== Coding Doctrine ==
The goal of the code is two things:

#Speed
#Readability

Wherever speed is not an issue (as in 97% of the code) coders are encouraged to make the code as readable to newbies as possible. Imagine your mother's life depends on her deciphering your code and you won't be around to help. That means no clever programming tricks, and sparing use of any standard libraries and especially templates and inheritance and polymorphism and other "advanced" concepts.

== To Do List (updated sparringly) ==
Feb 05 2006
===Presently, the following needs to be finished before a "BETA" can be achieved:===

*The GUI needs to be finished and integrated with the options data structure
*<s>Physics for robots needs to be finished (specifically, velocity limiting code and non-in-elastic collisions)</s>
*<s>-3, -4, -5, and -6 shots need to be finished,</s> as well as viruses (though viruses may be disabled in the initial release depending)
*Ties need to be coded using the new Tie paradigm discussed [http://forum.darwinbots.com/index.php?showtopic=560 here]
*The Robot Debugging window and robot mouse selection need to be finished.
*The graphics and engine need to be made thread safe.
*Mutations code needs to be finished (currently Sprotiel is working on this)
*Forward and backward compatible save/load routines for Simulation Settings, Simulations, and Robots. Preferably ascii over binary, except where size is an issue (as in Simulation settings), where some sort of file compression would be nice.

===These would be nice, but aren't 100% necessary for the "Beta" label===

*Scripts. PY was working on the idea of what they should be, so he should be consulted.
*Error Database. Basically, on an error an automatic report could be sent to one of the MYSQL databases available through our webspace and a notification sent to anyone working on the code automatically. Also, some sort of error viewer inside Darwinbots would be nice, so users could see how many other users reproted the error they recieved and wether or not it's been addressed by the coders yet.
*Bot Database. A way to upload and download bots from a central database from inside Darwinbots itself. Also using a Database as described above (we have 10 of the things, we won't run out :P)
*Statistical tools. This would involve everything from collecting data from the sim (and analyzing it according to proper statistical tests) to building a graph form and deciding how to draw it to exporting the data as per user specs into a spreadsheet program (like Excel). It is prefered that whoever works on this have some statistics background so they know what sort of stats users would want to collect and test.
*The vision testing algorithm is presently O(n^2), as it uses the "brute force" method. See: [[Vision_algorithm ]] for more inofo. It can be made nearly linear O(n) by using uniform grid cells. see:

:[http://yallara.cs.rmit.edu.au/~mawurm/cosc1224/asst1/index.xhtml This resource which exmines the issue]

:[http://www.harveycartel.org/metanet/tutorials/tutorialB.html This resource which describes the implementation and problems associated with it]

:Collision detection could use a similar technique, though its gains would be complicated by the fact that bots are not uniform in size.

:This would mean an absolutely insane boost in speed for large sims, but also would take some work.
*Since graphics are now using OpenGL, some pretty sweet graphics could be made. Admitedly spheres/circles shooting dots and lines at each other doesn't really inspire great art, but I think there's definately potential for some sweet demos. Maybe move it to 3D graphics instead of 2D and use some fog effects. Maybe use a shader.

===Long standing feature requests===
Anyone who managed to implement these in a way that didn't drastically increase memory and CPU requirements would be a hero in the Darwinbots community.

*[[Environment Grid]] - Basically the idea that bots should be able to interact with their physical environment. Things like leave poop behind for other bots to deal with, polute their environment, leave pheremone trails for other bots to follow, etc. There are, unfortunately, some gigantic memory and processing problems that beg for some smart, algorithm-savy programmer to address.

*[[Metabolism]] - The idea that bots should be able to generate nrg or use nrg based on their own unique bio-chemistry (or is it darwo-chemistry :P). This involves creating a system (or letting it emerge) of bio-chemical pathways and materials. Closely tied with the Environment Grid and likewise inter-related with the memory and processing problems.

*[[Specialization | Specialization and Speciation]] - The idea that bots should be able to become more efficient as they limit the number of activities they participate in. The primary hurdle isn't in coding it, but in designing the basic system to everyone's desires. It must respect multicellular specialization as well as single celled speciation. Not an easy task.

*[[Sexual Reproduction]] - Some way for two bots to, with consent (although 'rape' might have a place as well), produce offspring that robustly intermarries the two parents' DNA.

==Contact==
If you would like to help with the code, and any of the above sound interesting or do able, feel free to contact Numsgil at Numsgil2002@yahoo.com to discuss your ideas.

Talk:Botsareus's Vision

2005-11-06T01:34:31Z

216.249.144.14:

Note to all folks editing these wiki pages:<br>
if you don't see the changes you make appear ...<br>
you need to clear your browser cache ... and then refresh the page ...<br>
this seems to happen at most wikis ... but i notice it here a lot.
----

Use this talk page to discuss various ideas of the implimentation of DB ...
and provide feedback for Bau.
----

===Evo===
'''Here is how the 'evo' part works in my program:

*A.) It uses femily based periodically changing mutation rates to avoid mullers rachet.

*B.) Saving '''best robot''' at the end of a simulation or after n time, will result in saving a '''nuke problem''' robot or '''geek loophole''' robot, therefor the following must be done.

#) Each robot must have its skill factor calculated to know its '''true''' best value. This is done using <b>".good"</b> in each robots substructure.
#) Troughout the simulation the higest peaking point of a robots skill is determind. Lets call it J
#) J is checked agenst the J of the three previos 'runs' (each run lests 8000 cycles (although I have "/end" display something else, I am talking about my current work right now) this is done by using an external "saecheck.txt" file.
::a) If J is higher then the lest three 'runs', then 'save robots dna' is called. Wait for this 'run' to complete just incase J goes even higher.

*C.) The true 'best robot' is now set as the robot to restart/resume the simulation with.

i like these ideas, Bau ...<br>
makes a lot of sense to me. i will play with this prog this week and see how<br>
things go ... what questions are raised, etc ... and perhaps then know enough<br>
about these new features to ask relevent questions. thanks. {{User:Griz/sig}} 12:16, 2 Nov 2005 (MST)

edit by bots , summary:

'''Geek loophole problem and Nuke problem'''
http://forum.darwinbots.com/index.php?showtopic=781
http://forum.darwinbots.com/index.php?showtopic=703

My definition of 'mullers rachet' is different from the Ensyclopidia it turns out, so here it is:

'''Bau's rachet''' happens when an organism is changing at the same rate and time as all the other organisms (the changes in this case are making the organism worse) Since the saturation of worse organisms are the same for the entire feild, there is no selective presure for killing off the worse robots. Causing overall effiency to go down.

: Not to beat a dead horse or anything, but what you are describing only occurs if Muller's ratchet is, uh, ratcheting. Basically if you don't give evolution time to sort good and bad mutations out, why should you expect to find good mutations accumulating at all? What sort of mutations/generation ratio are you running with anyway? --[[User:216.249.144.14|216.249.144.14]] 18:34, 5 Nov 2005 (MST)

FTP

2005-11-02T03:42:08Z

216.249.144.14: /* Ver 2.4 C++ - ified */

Wiki mirror of FTP (under construction)
----

==Main Installs==
:[http://www.darwinbots.com/FTP/Darwin21.zip Darwin21]
:This must be installed prior to installing the patches/updates. See [[Installation_Instructions]].

==Patches==
<br>Just copy into your Darwinbots folder (wherever you installed it, generally c:\Program File\DarwinbotsII\)
<br>Unzip the zip file. Say yes to all overwrites. Don't worry, everything is backwards compatible.
=== Ver 2.36 ===
:[http://www.darwinbots.com/FTP/DarwinBots2.36.0.zip DarwinBots2.36.0]
:[http://www.darwinbots.com/FTP/DarwinBots2.36.1.zip DarwinBots2.36.1]
:[http://www.darwinbots.com/FTP/DarwinBots2.36.2.zip DarwinBots2.36.2]
:[http://www.darwinbots.com/FTP/DarwinBots2.36.3.zip DarwinBots2.36.3]
:[http://www.darwinbots.com/FTP/DarwinBots2.36.4.zip DarwinBots2.36.4]
:[http://www.darwinbots.com/FTP/DarwinBots2.36.5.zip DarwinBots2.36.5] A Stable Release (New users start here)
=== Ver 2.37 ===
:[http://www.darwinbots.com/FTP/DarwinBots2.37.0.zip DarwinBots2.37.0]
:[http://www.darwinbots.com/FTP/DarwinBots2.37.1.zip DarwinBots2.37.1] Internet Sharing Ready (from here down)
:[http://www.darwinbots.com/FTP/DarwinBots2.37.2.zip DarwinBots2.37.2]
:[http://www.darwinbots.com/FTP/DarwinBots2.37.3.zip DarwinBots2.37.3]
:[http://www.darwinbots.com/FTP/DarwinBots2.37.4.zip DarwinBots2.37.4]
=== Ver 2.4 ===
:[http://www.darwinbots.com/FTP/DarwinBots2.4.BETA.zip DarwinBots2.4 Beta]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.0.zip DarwinBots2.4.0]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.1.zip DarwinBots2.4.1]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.2.zip DarwinBots2.4.2]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.3.zip DarwinBots2.4.3]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.4.zip DarwinBots2.4.4]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.5.zip DarwinBots2.4.5]
:[http://www.darwinbots.com/FTP/DarwinBots2.4.6.zip DarwinBots2.4.6] Almost stable! ;)
:[http://www.darwinbots.com/FTP/DarwinBots2.4.7.zip DarwinBots2.4.7] Released 31Oct05 Testing in progress.

==Source Code==
Old School 2.11 source code
:[http://www.darwinbots.com/FTP/DarwinSource2.11.zip DarwinSource2.11]
=== Ver 2.36 ===
:[http://www.darwinbots.com/FTP/Darwinsource2.36.0.zip Darwinsource2.36.0]
:[http://www.darwinbots.com/FTP/Darwinsource2.36.1.zip Darwinsource2.36.1]
:[http://www.darwinbots.com/FTP/Darwinsource2.36.2.zip Darwinsource2.36.2]
:[http://www.darwinbots.com/FTP/Darwinsource2.36.3.zip Darwinsource2.36.3]
:[http://www.darwinbots.com/FTP/Darwinsource2.36.4.zip Darwinsource2.36.4]
:[http://www.darwinbots.com/FTP/Darwinsource2.36.5.zip Darwinsource2.36.5]
=== Ver 2.37 ===
:[http://www.darwinbots.com/FTP/Darwinsource2.37.0.zip Darwinsource2.37.0]
:[http://www.darwinbots.com/FTP/Darwinsource2.37.1.zip Darwinsource2.37.1]
:[http://www.darwinbots.com/FTP/Darwinsource2.37.2.zip Darwinsource2.37.2]
:[http://www.darwinbots.com/FTP/Darwinsource2.37.3.zip Darwinsource2.37.3]
:[http://www.darwinbots.com/FTP/Darwinsource2.37.4.zip Darwinsource2.37.4]
=== Ver 2.4 ===
:[http://www.darwinbots.com/FTP/Darwinsource2.4.ALPHA.zip Darwinsource2.4.ALPHA]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.BETA.zip Darwinsource2.4.BETA]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.0.zip Darwinsource2.4.0]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.1.zip Darwinsource2.4.1]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.2.zip Darwinsource2.4.2]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.3.zip Darwinsource2.4.3]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.4.zip Darwinsource2.4.4]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.5.zip Darwinsource2.4.5]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.6.zip Darwinsource2.4.6]
:[http://www.darwinbots.com/FTP/Darwinsource2.4.7.zip Darwinsource2.4.7]
===Ver 2.4 C++ - ified ===
:[http://www.darwinbots.com/FTP/DarwinCSource.zip DarwinCSource Oct. 21 2005]

Most current code can be viewed using the SVN. See [http://forum.darwinbots.com/index.php?showtopic=886 this announcement in the forum].

==Working Bots==
:This is a small sample of bots that are guarenteed to work in the latest version.
:Use these if (when) you have trouble with the default bots.
:[http://www.darwinbots.com/FTP/Animal_Minimalis%202.4%20Remix.txt Animal_Minimalis 2.4 Remix.txt]
==Tools==
:[http://www.darwinbots.com/FTP/VB6.zip VB6]
:[http://www.darwinbots.com/FTP/VC++60.zip VC6]
:[http://www.darwinbots.com/FTP/XList.zip Excel]
:[http://www.darwinbots.com/FTP/snapshot.zip Snapshot to Excel utility (zip)?]
:[http://www.darwinbots.com/FTP/snapshot.xls Snapshot to Excel utility (xls)?]
:[http://www.darwinbots.com/FTP/F1Calc.zip time till finished calculator (Excel)]
:[http://www.darwinbots.com/FTP/WindiffIgnoreCaps.zip Windiff Ignore Caps 1.0] Utility to detect differences between programs.
==Tutorials==
:[http://www.darwinbots.com/FTP/DarwinTutorial1+2.zip Darwinbots bot writing tutorial by PY]
==Misc==
:[http://www.darwinbots.com/FTP/HenkX%20-%20Digital%20Cell.mp3 HenkX - Digital Cell mp3]
:[http://www.darwinbots.com/FTP/intro.mp3 BotsAreUS - Intro mp3]
:[http://www.darwinbots.com/FTP/Darwin2.36ND.exe DarwinBots 2.36 nondeterministic]
:[http://www.darwinbots.com/FTP/My_code.zip Darwinbots Bau-ified 2.37]

----
Return to [[Main Page]]

Talk:FTP

2005-11-02T03:40:50Z

216.249.144.14:

Excellent job, I know that probably took some time. --[[User:216.249.144.14|216.249.144.14]] 20:40, 1 Nov 2005 (MST)

Humilis

2005-10-31T03:29:48Z

216.249.144.14:

use NewMove

'Humilis
cond
*.robage 20 mod 0 =
'Finally figured out how to use mod handily :)
start
7 rnd 50 store
stop

cond
'Gene should allow bot to test amongst 8 different refs randomly
.refup *50 add * .myup *50 add * !=
*.eye5 37 >
start
.shoot dec
stop

cond
*.nrg 5000 >
start
50 .repro store
stop

cond
*.eye5 0 >
*.refeye *.myeye = and
*.eye5 0 = or
start
314 rnd .aimdx store
stop

cond
*.eye5 0 >
*.vel 20 <
start
20 *.vel sub
2 div
*.body mult 1000 div
.up store
stop
end

Humilis

2005-10-31T03:29:30Z

216.249.144.14: Modified source to work using the new "use NewMove" operator (which is preferable for new bots)

Main Page

2005-10-24T19:41:24Z

216.249.144.14: /* Oct. 24 2005 = */

__NOTOC__

[[Image:MainpageBanner.jpg]]

Darwinbots Wiki Manual and new homepage. Hopefully a compendium of knowledge that will be more than a manual.

== News ==
=== Oct. 24 2005 ===
2.4.5 is on the FTP. It is very, very stable. I think. If you can't get it to run right, it's been reported that a clean install of 2.1, then patching, will fix the problem.

=== Oct. 19 2005 ===
2.4.3 is released on the [http://www.darwinbots.com/FTP FTP] which addresses the difficulties of new users. If you tried Darwinbots recently and had trouble getting it to work properly, this should address your problem.

=== Oct. 15 2005 ===
A bunch of work has been done with the help page(sidebar). Also added a <nowiki>{{delete}}</nowiki> template that users can add to an Unused page they believe should be deleted. This page is also tracked so anyone can also add a link to the unused page and expect a response.

== New Users Portal ==

[[Introduction]] - New to Darwinbots? Start here, this should answer all your questions.

[[Installation Instructions]] - For when installing later versions requires a bit of work

[[Your First Simulations]] - Or getting to know the program

[[Robot Tutorial]] - Learn to write your own bots

[[Troubleshooting]] - What? Your program crashes 10 seconds after you start a sim? That's not right...

[http://forum.darwinbots.com The Forum] - This is the primary hub of the Darwinbots universe. Feel free to stop in and chat sometime

[http://www.darwinbots.com/FTP Downloads, New Installs and Patches]

== Reference Manual ==

[[Robot DNA]] - Not as complicated as it at first seems.

[[Concepts]] - There are some rather abstract concepts that may need explaining

[[Simulation Options]] - What do all these sliders mean?

[[League | Leagues]] - Learn about the leagues that exist.

[[Evolution Sims]] - The pinacle of any ALife program. It can be a tricky art to master.

[[Technical Details]] - For when you want to know *exactly* how something works.

[[Version History]] - An interesting look at the evolution of Darwinbots itself

[[Other Resources]] - Links to resources you might find useful.

[[Programmers Portal | Programmer's portal]]

===Other===
These are links to central link pages that don't directly reflect what is currently in the DB program

[[Ideas]] - Posting spot for interactive work on different ideas

[[Whimsical]] - Stories and ectera may be posted here

[[RoundTable]] - DB wikipedians unite. Knights talk to Emperors, Lords talk to Gods. So basically its a discussion area

== Wiki Help ==
Please see [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for Wiki usage<br>
and help with [http://en.wikipedia.org/w/wiki.phtml?title=Wikipedia:How_to_edit_a_page&oldid=2360888 Wiki Editing].<br>
In house DarwinBot [[Help:Contents|Wiki Editing Tips]]<br>
There is now a [[Sandbox]] to play in and practice your Wiki code.<br>

[http://meta.wikimedia.org/wiki/Policy Overall WikiPolicy]
[[WikiManual:Policy]]
----
Feel free to come to my [[User_talk:Griz|talk]] page and ask any Wiki questions you might have. {{User:Griz/sig}}

Main Page

2005-10-24T19:41:12Z

216.249.144.14: /* News */

__NOTOC__

[[Image:MainpageBanner.jpg]]

Darwinbots Wiki Manual and new homepage. Hopefully a compendium of knowledge that will be more than a manual.

== News ==
== Oct. 24 2005 ===
2.4.5 is on the FTP. It is very, very stable. I think. If you can't get it to run right, it's been reported that a clean install of 2.1, then patching, will fix the problem.

=== Oct. 19 2005 ===
2.4.3 is released on the [http://www.darwinbots.com/FTP FTP] which addresses the difficulties of new users. If you tried Darwinbots recently and had trouble getting it to work properly, this should address your problem.

=== Oct. 15 2005 ===
A bunch of work has been done with the help page(sidebar). Also added a <nowiki>{{delete}}</nowiki> template that users can add to an Unused page they believe should be deleted. This page is also tracked so anyone can also add a link to the unused page and expect a response.

== New Users Portal ==

[[Introduction]] - New to Darwinbots? Start here, this should answer all your questions.

[[Installation Instructions]] - For when installing later versions requires a bit of work

[[Your First Simulations]] - Or getting to know the program

[[Robot Tutorial]] - Learn to write your own bots

[[Troubleshooting]] - What? Your program crashes 10 seconds after you start a sim? That's not right...

[http://forum.darwinbots.com The Forum] - This is the primary hub of the Darwinbots universe. Feel free to stop in and chat sometime

[http://www.darwinbots.com/FTP Downloads, New Installs and Patches]

== Reference Manual ==

[[Robot DNA]] - Not as complicated as it at first seems.

[[Concepts]] - There are some rather abstract concepts that may need explaining

[[Simulation Options]] - What do all these sliders mean?

[[League | Leagues]] - Learn about the leagues that exist.

[[Evolution Sims]] - The pinacle of any ALife program. It can be a tricky art to master.

[[Technical Details]] - For when you want to know *exactly* how something works.

[[Version History]] - An interesting look at the evolution of Darwinbots itself

[[Other Resources]] - Links to resources you might find useful.

[[Programmers Portal | Programmer's portal]]

===Other===
These are links to central link pages that don't directly reflect what is currently in the DB program

[[Ideas]] - Posting spot for interactive work on different ideas

[[Whimsical]] - Stories and ectera may be posted here

[[RoundTable]] - DB wikipedians unite. Knights talk to Emperors, Lords talk to Gods. So basically its a discussion area

== Wiki Help ==
Please see [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for Wiki usage<br>
and help with [http://en.wikipedia.org/w/wiki.phtml?title=Wikipedia:How_to_edit_a_page&oldid=2360888 Wiki Editing].<br>
In house DarwinBot [[Help:Contents|Wiki Editing Tips]]<br>
There is now a [[Sandbox]] to play in and practice your Wiki code.<br>

[http://meta.wikimedia.org/wiki/Policy Overall WikiPolicy]
[[WikiManual:Policy]]
----
Feel free to come to my [[User_talk:Griz|talk]] page and ask any Wiki questions you might have. {{User:Griz/sig}}

Main Page

2005-10-20T01:42:45Z

216.249.144.14: /* Oct. 18 2005 */

__NOTOC__

[[Image:MainpageBanner.jpg]]

Darwinbots Wiki Manual and new homepage. Hopefully a compendium of knowledge that will be more than a manual.

== News ==
=== Oct. 19 2005 ===
2.4.3 is released on the [http://www.darwinbots.com/FTP FTP] which addresses the difficulties of new users. If you tried Darwinbots recently and had trouble getting it to work properly, this should address your problem.

=== Oct. 15 2005 ===
A bunch of work has been done with the help page(sidebar). Also added a <nowiki>{{delete}}</nowiki> template that users can add to an Unused page they believe should be deleted. This page is also tracked so anyone can also add a link to the unused page and expect a response.

=== Oct. 12 2005 ===
Well, our wiki went down for a little bit. I fixed it, and in the process learned a bit about databases.

== New Users Portal ==

[[Introduction]] - New to Darwinbots? Start here, this should answer all your questions.

[[Installation Instructions]] - For when installing later versions requires a bit of work

[[Your First Simulations]] - Or getting to know the program

[[Robot Tutorial]] - Learn to write your own bots

[[Troubleshooting]] - What? Your program crashes 10 seconds after you start a sim? That's not right...

[http://forum.darwinbots.com The Forum] - This is the primary hub of the Darwinbots universe. Feel free to stop in and chat sometime

[http://www.darwinbots.com/FTP Downloads, New Installs and Patches]

== Reference Manual ==

[[Robot DNA]] - Not as complicated as it at first seems.

[[Concepts]] - There are some rather abstract concepts that may need explaining

[[Simulation Options]] - What do all these sliders mean?

[[League | Leagues]] - Learn about the leagues that exist.

[[Evolution Sims]] - The pinacle of any ALife program. It can be a tricky art to master.

[[Technical Details]] - For when you want to know *exactly* how something works.

[[Version History]] - An interesting look at the evolution of Darwinbots itself

[[Other Resources]] - Links to resources you might find useful.

[[Programmers Portal | Programmer's portal]]

===Other===
These are links to central link pages that don't directly reflect what is currently in the DB program

[[Ideas]] - Posting spot for interactive work on different ideas

[[Whimsical]] - Stories and ectera may be posted here

== Wiki Help ==
Please see [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for Wiki usage<br>
and help with [http://en.wikipedia.org/w/wiki.phtml?title=Wikipedia:How_to_edit_a_page&oldid=2360888 Wiki Editing].<br>
In house DarwinBot [[Help:Contents|Wiki Editing Tips]]<br>
There is now a [[Sandbox]] to play in and practice your Wiki code.<br>

[http://meta.wikimedia.org/wiki/Policy Overall WikiPolicy]
[[WikiManual:Policy]]
----
Feel free to come to my [[User_talk:Griz|talk]] page and ask any Wiki questions you might have. {{User:Griz/sig}}

Talk:Sysvar

2005-10-15T22:50:44Z

216.249.144.14:

I'm hoping to make this page be the backbone of a giant reference. Depending on the sysvar(s) there will be links to another specific section or if small enough just a short blurb.

Awesome work, keep it up. I'll try to post code snipets about relevant sysvars from time to time (like how the code handles the sysvar).

----
:As this page is going to be rather long ...
:would generating a Table of Contents at the top of the page be useful?
Great work, btw. {{User:Griz/sig}} 09:50, 15 Oct 2005 (MST)
:for example:

===Ties===
*[[Ties]]
** [[Soft Ties]]
** [[Hard Ties]]

===Movement===
*[[.up|Movement (.up, .dn. .dx, .sx)]]
**up/1
**dn/2
**sx/3
**dx/4
*[[.aimdx|Basic Turning (.aimdx, .aimsx)]]
**aimdx/5
**aimsx/6
===Shooting===
*[[Shooting]]
**shoot/7
**shootval/8
*backshot/900
*aimshoot/901

*robage/9
*mass/10
*maxvel/11
*aim/18
*setaim/19

*velscalar/196
*velsx/197
*veldx/198
*veldn/199
*velup/200
*vel/200

===Gains and Losses===
*[[Gains and Losses]]
**pain/203
**pleas/204
**bodgain/194
**bodloss/195

===Hit===
*[[Hit]]?
**hit/201
**hitup/205
**hitdn/206
**hitdx/207
**hitsx/208

Table of contents would probably be a very good idea.

Talk:Sysvar

2005-10-15T16:06:40Z

216.249.144.14:

Main Page

2005-10-13T18:55:13Z

216.249.144.14:

[[Image:MainpageBanner.jpg]]

Darwinbots Wiki Manual and new homepage. Hopefully a compendium of knowledge that will be more than a manual.

<h2> News </h2>
=== Oct. 12 2005 ===
Well, our wiki went down for a little bit. I fixed it, and in the process learned a bit about databases.

<h2> New Users Portal </h2>

[[Introduction]] - New to Darwinbots? Start here, this should answer all your questions.

[[Installation Instructions]] - For when installing later versions requires a bit of work

[[Your First Simulations]] - Or getting to know the program

[[Robot Tutorial]] - Learn to write your own bots

[[Troubleshooting]] - What? Your program crashes 10 seconds after you start a sim? That's not right...

[http://forum.darwinbots.com The Forum] - This is the primary hub of the Darwinbots universe. Feel free to stop in and chat sometime

[http://www.darwinbots.com/FTP Downloads, New Installs and Patches]

<h2> Reference Manual </h2>

[[Robot DNA]] - Not as complicated as it at first seems.

[[Concepts]] - There are some rather abstract concepts that may need explaining

[[Simulation Options]] - What do all these sliders mean?

[[League | Leagues]] - Learn about the leagues that exist.

[[Evolution Sims]] - The pinacle of any ALife program. It can be a tricky art to master.

[[Technical Details]] - For when you want to know *exactly* how something works.

[[Version History]] - An interesting look at the evolution of Darwinbots itself

[[Other Resources]] - Links to resources you might find useful.

[[Programmers Portal | Programmer's portal]]

Please see [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage.

Veggy

2005-10-12T21:43:55Z

216.249.144.14:

==Veggies==

===Overview===
A veggie or Alga is any bot that has the autotroph box checked. This enables the bot to be fed by the program and enables it to feed off any [[waste]] it receives. If the veggie population exceeds the population limit set, the program will not allow any veggies to repopulate. Note that this often results in sharp spikes of population as all the veggies reproduce at the same time once the population falls below the threshold.

===Repopulation===
If a certain number of veggies die the species will be repopulated. This number is user set in the veggies options under general. The nrg of the repopulated veggies will be the same as that set for the species in the first options panel. Often repopulation is necessary to keep the bots inside alive, although cancerous veggies (veggies that always try to reproduce) have been shown to be a self sustaining energy source (just make sure you set the maximal veggy population a bit lower than you want it. This is from the aforementioned population spikes).

The repopulation cooldown period allows you to specify how long it takes until new veggies are dropped into the sim. Setting this too low is a significant source of bot overpopulation, since the faster the bots eat the new veggies the faster they get new veggies.

== Veggy feeding methods==
*nrg per cycle - a straight forward feeding method. Each veggy gets a set amount of energy per cycle.
*per kilobody - each veggy gets a set amount of [[Energy]] per 1000 [[Body]] points. This is useful as it discourages cancerous veggies from developing

== Veg Trouble ==
If your vegs become monsterously fat in the first several seconds of a sim, and your cycles per second becomes too low, you're probably giving the vegs too much enrgy.

This makes the program unstable and somewhat unpredictable.

Check the simulation settings for vegs and be sure the nrg/cycle text box for vegs is set to something under about 100.

Veggy

2005-10-12T21:42:08Z

216.249.144.14:

~

2005-10-12T21:39:27Z

216.249.144.14:

The top value of the stack is deconstructed into a bit array. Each element in this array is complimented. That is, if it was a one, it's turned to a zero, and vice versa.

The effect is really quite interesting. The sign of the number changes, and its value becomes significantly different.

0 ~

would be -1 I believe.

64 ~

is -4294967231 I believe.

All values are me working from memory, but you get the idea.

Operator

2005-10-12T21:34:48Z

216.249.144.14:

Anything you're likely to see in DNA.

=== Sysvars ===
* [[Definitions]]
* [[.up|Movement (.up, .dn. .dx, .sx)]]
* [[.aimdx|Basic Turning (.aimdx, .aimsx)]]
* [[Shooting]]
* [[Reproducing]]
* [[Ties]]
** [[Soft Ties]]
** [[Hard Ties]]
*** [[MB Sharing]]
* [[Memloc and Memval]]
* [[In and Out]]

== Basic Commands ==
*[[add]]
*[[sub]]
*[[mult]]
*[[div]]
*[[rnd]]
*[[*]]
*[[mod]]
*[[sgn]]
*[[abs]]
*[[dup]]

== Advanced Commands ==
*[[angle]]
*[[dist]]
*[[ceil]]
*[[floor]]
*[[sqr]]
*[[pow]]
*[[pyth]]

== Bitwise Commands ==

It'd be helpful if you knew the [[bit basics]].
*[[~]] Compliment
*[[&]] AND
*[[pipe| |]] OR
*[[^]] XOR
*[[valinc | ++]] increment stack value
*[[valdec | --]] deincrement stack value
*[[-]] negate stack value
*[[Shift left | <<]] bit shift left
*[[Shift right| >>]] bit shift right

== Conditions ==
* [[Greater than|>]]
* [[Less than|<]]
*[[=]]
*[[!=]]
*[[%=]]
*[[!%=]]
*[[~=]]
*[[!~=]]
* [[Greatthan equals|>= ]]
* [[Lessthan equals|<= ]]

== Logic Operators ==
*[[and]]
*[[or]]
*[[xor]]
*[[not]]

== Store commands ==
*[[store]]
*[[inc/dec]]

=== Flow Commands===
* [[cond]]
* [[start]]
* [[else]]
* [[stop]]
* [[end]]
**[[Robot DNA]]

Robot DNA

2005-10-12T21:34:24Z

216.249.144.14: /* DNA commands */

User talk:Numsgil

2005-10-12T19:39:38Z

216.249.144.14:

You should probably edit the "localsettings.php" file to set the mediawiki license. It should be self explanatory (but let me know if you are stuck.) [[FreeBio:Alexanderwait]]
----
hey Numbskull ... err ... Numsgil ;)<br>
just came aboard ... let me know how/if i can be of use around here. {{User:Griz/sig}} 12:30, 12 Oct 2005 (MST)

Yeah, since you're new, trawl through the wiki and see what doesn't make sense, or needs elaborating, or what is entirely missing. Most of us who work on teh wiki have been with the program so long we know it like the back of our hands. --[[User:Numsgil]] 12:39, 12 Oct 2005 (MST)

User talk:Numsgil

2005-10-12T19:39:25Z

216.249.144.14:

Vision algorithm

2005-10-04T00:07:20Z

216.249.144.14:

== Naive Approach ==

For x = 1 to MaxRobs
For y = 1 to MaxRobs
check if bot x can see bot y

I'm also looking into ''k''-d trees and quad trees. If you are knowledgable in space partitioning algorithms, ''please'' post your thoughts on what the most appropriate algorithm to use is and why!

Robot DNA

2005-10-02T18:47:57Z

216.249.144.14: /* DNA commands */

==How the DNA works==
* [[Genes]]
* [[Execution Flag]]
* [[The Stack]]
* [[Custom labels]] (or variables if you prefer)

== DNA commands==
An overview of each and every DNA command, from sysvars to logical operators.

[[Operators | 2.4 Operators]]

=== Sysvars ===
* [[Definitions]]
* [[.up|Movement (.up, .dn. .dx, .sx)]]
* [[.aimdx|Basic Turning (.aimdx, .aimsx)]]
* [[Shooting]]
* [[Reproducing]]
* [[Ties]]
** [[Soft Ties]]
** [[Hard Ties]]
*** [[MB Sharing]]
* [[Memloc and Memval]]
* [[In and Out]]

===Operators===
* [[store]]
* [[rnd]]
* [[add]]
* [[sub]]
* [[mult]]
* [[div]]
* [[inc/dec]]

=== Logical Operators===
* [[and]]
* [[or]]
* [[xor]]
* [[not]]

=== Logical Comparison Operators===
* [[=]]
* [[!=]]
* [[Greater than|>]]
* [[Less than|<]]
* [[%=]]
* [[!%=]]

=== Flow Commands===
* [[cond]]
* [[start]]
* [[stop]]
* [[end]]

Current events

2005-09-20T02:29:34Z

216.249.144.14:

Numsgil in particular is gearing up for the upcoming release of 2.4, sometime before the end of September 2005.

Birth tie

2005-09-20T02:26:25Z

216.249.144.14: sp

A thick tie seen at birth connecting both parent and offspring. It generally lasts for 100 cycles. A number of cycles are spent transfering epigenic or "[[racial memory]]" from parent to child.

Bots can reduce the time spent in the birth tie by firing ties at the parent or child manually and deleting them, since only one tie can be formed between any two bots, and newer ties always supplant older ones. Ordinarily this is done to reduce motion penalties imposed by attached bot.

Most parents and children coupled together with a birth tie are vulnerable to outside attack. Also, they tend to attempt moving in different directions, with the result that they go nowhere.

Other methods to compensate for this problem:

* limit motion when tied to child
* limit child's motion (either parent does this manually, or its coded into newborn babies)

Other Resources

2005-09-20T02:25:27Z

216.249.144.14: /* Links to other areas related to DB */

==Links to other areas related to DB==

* [http://www.darwinbots.com/ Darwinbots' New Home]
* [http://s9.invisionfree.com/DarwinBots_Forum/index.php?act=idx/index.php?act=site New Forum]
* [http://en.wikipedia.org/wiki/Darwinbots Darwinbots at Wikipedia]
* [http://darwinbots.xwiki.com/ Xwiki vers of Manual (Retired)]
* [http://darwinbots.proboards20.com/index.cgi Old Forum (Dead Feb 05)]
* [http://digilander.libero.it/darwinbots/ Old DB Homepage (No longer updated)]
* [http://www.sodev.free-speicher.de/dbdb/ Database]

== Links to other useful ALife resources ==

* [http://dllab.caltech.edu/avida/ Avida] is pretty much the standard for professional research. But Darwinbots will change that one day!

It seems weird that most ALife websites have such horrible layouts.

User:Numsgil

2005-09-20T00:42:40Z

216.249.144.14: I didn't write this, I swear :P

Numsgil is one of the programmers (I would even argue lead programmer :P) and probably the worst forum spammer alive. By far.

Numsgil currently resides in Murray, Kentucky, which happens to be the exact middle of nowhere. He is finishing up school, and contemplating either graduate school in Artificial Life or some sort of massive head trauma. Some would even argue that they're the same thing.

Numsgil is 20 years old as of 2005. He has also been working on Darwinbots since January 2005. Note how little time that is compared with how long Darwinbots has been around. Yet single handedly (well, he uses both hands. And PY helped. A little.) Numsgil has taken the program to new levels of complexity.

Birth tie

2005-09-20T00:37:07Z

216.249.144.14:

A thick tie seen at birth connecting both parent and offspring. It generally lasts for 100 cycles. A number of cycles are spent transfering epigenic or "[[racial memory]]" from parent to child.

Bots can reduce teh time spent in the birth tie by firing ties at the parent or child manually and deleting them, since only one tie can be formed between any two bots, and newer ties always supplant older ones. Ordinarily this is done to reduce motion penalties imposed by attached bot.

Most parents and children coupled together with a birth tie are vulnerable to outside attack. Also, they tend to attempt moving in different directions, with the result that they go nowhere.

Other methods to compensate for this problem:

* limit motion when tied to child
* limit child's motion (either parent does this manually, or its coded into newborn babies)

Birth tie

2005-09-20T00:36:40Z

216.249.144.14:

A thick tie seen at birth connecting both parent and offspring. It generally lasts for 100 cycles,. A number of cycles are spent transfering epigenic or "[[racial memory]]" from parent to child.

Bots can reduce teh time spent in the birth tie by firing ties at the parent or child manually and deleting them, since only one tie can be formed between any two bots, and newer ties always supplant older ones. Ordinarily this is done to reduce motion penalties imposed by attached bot.

Most parents and children coupled together with a birth tie are vulnerable to outside attack. Also, they tend to attempt moving in different directions, with the result that they go nowhere.

Other methods to compensate for this problem:

* limit motion when tied to child
* limit child's motion (either parent does this manually, or its coded into newborn babies)

Main Page

2005-09-19T22:42:43Z

216.249.144.14: /* Table of Contents */

[[Image:MainpageBanner.jpg]]

== Darwinbots Wiki-Style ==

Hopefully a compendium of knowledge that will be more than a manual.
(Note: currently the manual exists at [http://darwinbots.xwiki.com/xwiki/bin/view/Main/WebHome DB Xwiki], but hopefully a move over will be swift in coming)

== [[Table of Contents]] ==

[http://www.darwinbots.com/FTP Downloads, New Installs and Patches]

[[Introduction]] -New to Darwinbots? Start here, this should answer all your questions.

[[Your First Simulations]] - Or getting to know the program

[[Concepts]] - There are some rather abstract concepts that may need explaining

[[Simulation Options]] - What do all these sliders mean?

[[Robot DNA]] - Not as complicated as it at first seems.

[[Robot Tutorial]] - Learn to write your own bots

[[League | Leagues]] - Learn about the leagues that exist.

[[Evolution Sims]] - The pinacle of any ALife program. It can be a tricky art to master.

[[Technical Details]] - For when you want to know *exactly* how something works.

[[Version History]] - An interesting look at the evolution of Darwinbots itself

[[Other Resources]] - Links to resources you might find useful.

Please see [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage.

Other Resources

2005-09-18T23:20:50Z

216.249.144.14: /* Links to other areas related to DB */

==Links to other areas related to DB==

* [http://www.darwinbots.com/ Darwinbots' New Home]
* [http://s9.invisionfree.com/DarwinBots_Forum/index.php?act=idx/index.php?act=site New Forum]

* [http://darwinbots.xwiki.com/ Xwiki vers of Manual (Retired)]
* [http://darwinbots.proboards20.com/index.cgi Old Forum (Dead Feb 05)]
* [http://digilander.libero.it/darwinbots/ Old DB Homepage (No longer updated)]
* [http://www.sodev.free-speicher.de/dbdb/ Database]

== Links to other useful ALife resources (what little there is) ==

* [http://dllab.caltech.edu/avida/ Avida] is pretty much the standard for professional research. But Darwinbots will change that one day!

It seems weird that most ALife websites have such horrible layouts.

Main Page

2005-09-18T22:53:57Z

216.249.144.14:

[[Image:MainpageBanner.jpg]]

== Darwinbots Wiki-Style ==

Hopefully a compendium of knowledge that will be more than a manual.
(Note: currently the manual exists at [http://darwinbots.xwiki.com/xwiki/bin/view/Main/WebHome DB Xwiki], but hopefully a move over will be swift in coming)

== [[Table of Contents]] ==

[[Introduction]] -New to Darwinbots? Start here, this should answer all your questions.

[[Your First Simulations]] - Or getting to know the program

[[Concepts]] - There are some rather abstract concepts that may need explaining

[[Simulation Options]] - What do all these sliders mean?

[[Robot DNA]] - Not as complicated as it at first seems.

[[Robot Tutorial]] - Learn to write your own bots

[[League | Leagues]] - Learn about the leagues that exist.

[[Evolution Sims]] - The pinacle of any ALife program. It can be a tricky art to master.

[[Technical Details]] - For when you want to know *exactly* how something works.

[[Version History]] - An interesting look at the evolution of Darwinbots itself

[[Other Resources]] - Links to resources you might find useful.

Please see [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage.

WikiManual:About

2005-09-18T19:10:40Z

216.249.144.14:

The Darwinbots manual is the official source for all information pertaining to Darwinbots.