paradiseo/edo
nojhan 8948f0a3dc fix doc: big update
- use single doxyfile instead of one per module
- use a cleaner and more modern style
- reorder sections to put details first
- hide diagrams by default
- remove deprecated doxygen variables
- disable latex generation by default
- fix some doc typos
2022-01-26 16:45:51 +01:00
..
application fix new warnings and escape apply namespace 2020-04-28 15:56:14 +02:00
cmake/modules + added FIndEO in edo 2011-10-26 10:20:48 +02:00
doc fix doc: big update 2022-01-26 16:45:51 +01:00
src fix even more warnings and reduce some tests runtimes 2020-04-28 17:41:50 +02:00
test add mininal cmaes 2020-05-03 15:31:12 +02:00
AUTHORS * whitespace cleanup 2011-05-05 17:15:10 +02:00
build_gcc_linux_debug build with eigen by default 2012-07-24 11:47:46 +02:00
build_gcc_linux_eigen_debug conditional build scripts with boost xor eigen 2012-07-09 16:26:19 +02:00
build_gcc_linux_release conflict resolved 2012-07-23 16:05:10 +02:00
CMakeLists.txt Fix the doc build. 2018-12-08 21:11:41 +01:00
COPYING * whitespace cleanup 2011-05-05 17:15:10 +02:00
distclean move edo stuff, that was in the wriong place after the merge, in the edo directory 2011-01-27 11:58:21 +01:00
edo.pc move edo stuff, that was in the wriong place after the merge, in the edo directory 2011-01-27 11:58:21 +01:00
install.cmake-dist edo/install.cmake-dist updated 2012-07-23 16:52:47 +02:00
LICENSE fix licenses 2021-11-03 15:28:52 +01:00
NEWS update news an version for head 2012-07-27 09:23:14 +02:00
package_deb move edo stuff, that was in the wriong place after the merge, in the edo directory 2011-01-27 11:58:21 +01:00
package_rpm move edo stuff, that was in the wriong place after the merge, in the edo directory 2011-01-27 11:58:21 +01:00
Packaging.cmake move edo stuff, that was in the wriong place after the merge, in the edo directory 2011-01-27 11:58:21 +01:00
README the readme talks about eda rather than eda_sa, less simple 2012-07-10 15:35:40 +02:00

This package contains the source code for EDO.

# Step 1 - Configuration
------------------------
Rename the "install.cmake-dist" file as "install.cmake" and edit it, inserting the FULL PATH
to your ParadisEO distribution.
On Windows write your path with double antislash (ex: C:\\Users\\...)


# Step 2 - Build process
------------------------
ParadisEO is assumed to be compiled. To download ParadisEO, please visit http://paradiseo.gforge.inria.fr/.
Go to the DO/build/ directory and lunch cmake:
(Unix)       > cmake ..
(Windows)    > cmake .. -G"Visual Studio 9 2008"

Note for windows users: if you don't use VisualStudio 9, enter the name of your generator instead of "VisualStudio 9 2008".


# Step 3 - Compilation
----------------------
In the edo/build/ directory:
(Unix)       > make
(Windows)    Open the VisualStudio solution and compile it, compile also the target install.
You can refer to this tutorial if you don't know how to compile a solution: http://paradiseo.gforge.inria.fr/index.php?n=Paradiseo.VisualCTutorial


# Step 4 - Execution
---------------------
A toy example is given to test the components. You can run these tests as following.
To define problem-related components for your own problem, please refer to the tutorials available on the website : http://paradiseo.gforge.inria.fr/.
In the edo/build/ directory:
(Unix)       > ctest
Windows users, please refer to this tutorial: http://paradiseo.gforge.inria.fr/index.php?n=Paradiseo.VisualCTutorial

In the directory "application", there are several directory such as eda which instantiate EDA solver.

(Unix) After compilation you can run the binary "build/eda" and see results. Parameters can be modified from command line.

(Windows) Add argument "eda.param" and execute the corresponding algorithms.
Windows users, please refer to this tutorial: http://paradiseo.gforge.inria.fr/index.php?n=Paradiseo.VisualCTutorial


# Documentation
---------------
The API-documentation is available in doc/html/index.html


# Things to keep in mind when using EDO
----------------------------------------
* By default, the EO random generator's seed is initialized by the number of seconds since the epoch (with time(0)). It is available in the status file dumped at each execution. Please, keep in mind that if you start two run at the same second without modifying the seed, you will get exactly the same results.

* Execution times are measured with the boost:timer, that measure wallclock time. Additionaly, it could not measure times larger than approximatively 596.5 hours (or even less). See http://www.boost.org/doc/libs/1_33_1/libs/timer/timer.htm

* The q-quantile computation use averaging at discontinuities (in R, it correspond to the R-2 method, in SAS, SAS-5). For more explanations, see http://en.wikipedia.org/wiki/Quantile#Estimating_the_quantiles_of_a_population and http://stat.ethz.ch/R-manual/R-devel/library/stats/html/quantile.html

* You can send a SIGUSR1 to a process to get some information (written down in the log file) on the current state of the search.