54a44a177f
Replace http://paradiseo.gforge.inria.fr with https://nojhan.github.io/paradiseo/ and paradiseo-help@lists.gforge.inria.fr with https://github.com/nojhan/paradiseo/issues across all source files, doxyfile templates, cmake packaging, and eo documentation. Also updates eodev.sourceforge.net references in EO headers. Applied to .h, .cpp, .cmake, and miscellaneous files in eo/, mo/, moeo/, smp/, and problems/.
89 lines
3 KiB
Text
89 lines
3 KiB
Text
EO README FILE
|
||
|
||
=======================================================================
|
||
check latest news at https://nojhan.github.io/paradiseo/
|
||
=======================================================================
|
||
|
||
Welcome to EO, the Evolving Objects library.
|
||
|
||
The latest news about EO can be found on the sourceforge repository at
|
||
https://nojhan.github.io/paradiseo/
|
||
|
||
In case of any problem, please e-mail us at
|
||
eodev-main@lists.sourceforge.net
|
||
|
||
To get started, take a look at the tutorial, starting with
|
||
./tutorial/html/eoTutorial.html
|
||
|
||
The easiest way to start programming a new genome with all EO
|
||
evolution engines handy is to create a new standalone EO project from
|
||
the tutorial/Templates/ directory. Read Lesson 5 of the tutorial for
|
||
an introduction ;)
|
||
|
||
|
||
==================================================================
|
||
BUILDING EO
|
||
==================================================================
|
||
The basic installation procedure goes the following:
|
||
|
||
Go to the "eo/" and run one of the "build_*" script.
|
||
|
||
Using the "build_gcc_linux_release" script is generally what you want. The
|
||
binaries are then located in the "release/" directory.
|
||
|
||
Now you should probably go to the tutorial and start learning about EO
|
||
features and programming.
|
||
|
||
In case of problems or if you want advanced options, you can read the INSTALL file.
|
||
|
||
===================================================================
|
||
DIRECTORY STRUCTURE
|
||
===================================================================
|
||
After unpacking the archive file, you should end up with the following
|
||
structure:
|
||
|
||
.../ the MAIN EO dir, created when unpacking
|
||
|
|
||
+-- src SOURCE dir. Contains most EO .h files
|
||
| |
|
||
| +- utils general utilities (e.g. RNG-related source files)
|
||
| |
|
||
| +- ga bistring-genotypes source files
|
||
| |
|
||
| +- es real-valued-genotypes source files
|
||
| |
|
||
| +- gp Genetic Programming source files
|
||
| |
|
||
| +- obsolete files from old versions - for upward compatibility
|
||
|
|
||
|
|
||
|
|
||
+-- tutorial TUTORIAL dir (indeed :-)
|
||
| |
|
||
| +- html all html files - start by browsing index.html
|
||
| |
|
||
| +- LessonX for X=1, 2, 3, ... : example of increasing complexity
|
||
|
|
||
|
|
||
|
|
||
+-- doc DOCUMENTATION dir (generated by Doxygen)
|
||
| |
|
||
| +- html HTML files - start at index.html (see also tutorial)
|
||
| |
|
||
| +- latex latex files - use to generate Poatscript doc.
|
||
| |
|
||
| +- man Unix man format documentation
|
||
|
|
||
|
|
||
+-- test TEST files - for debugging purposes only
|
||
|
|
||
|
|
||
+-- app APPLICATIONS - one dir per separate application
|
||
| |
|
||
| +- gprop GA/backpropagation for neural nets
|
||
| |
|
||
| +- mastermind the wellknown MasterMind game
|
||
|
|
||
|
|
||
+-- win WINDOWS dir: project files for MS/VC5+
|
||
|