diff --git a/eo/tutorial/html/SecondBitEA.html b/eo/tutorial/html/SecondBitEA.html
index d57e1a4ec..4061d9c03 100644
--- a/eo/tutorial/html/SecondBitEA.html
+++ b/eo/tutorial/html/SecondBitEA.html
@@ -92,14 +92,16 @@ or in a parameter file (same syntax, order independent,
or in the environment (TODO)
// First define a parser from the command-line
arguments
-
eoParser parser(argc, argv);
+
eoParser
+parser(argc, argv);
// For each parameter, define Parameter, read
it through the parser,
// and assign the value to the variable
eoValueParam<uint32> seedParam(time(0),
"seed", "Random number seed", 'S');
-
parser.processParam( seedParam );
+
parser.processParam(
+seedParam );
unsigned seed
= seedParam.value();
// decription
@@ -308,15 +310,15 @@ of initializatio of the population
// The robust tournament selection
- eoDetTournament<Indi> selectOne(tSize);
+ eoDetTournament<Indi> selectOne(tSize);
+
// tSize in [2,POPSIZE]
// is now encapsulated in a
eoSelectPerc (entage)
eoSelectPerc<Indi> select(selectOne);
// or eoSelectPerc<Indi> select(selectOne,
rate);
- // but by default rate==1
- |
+
// but by default rate==1
diff --git a/eo/tutorial/html/eoLesson3.html b/eo/tutorial/html/eoLesson3.html
index f1a5aac5b..b69671cc5 100644
--- a/eo/tutorial/html/eoLesson3.html
+++ b/eo/tutorial/html/eoLesson3.html
@@ -2,7 +2,7 @@
-
+
Tutorial: Lesson 3
@@ -12,7 +12,8 @@
Main page -
Algorithm-Based
- Component-Based - Hints
-- EO documentation
+- EO
+documentation
@@ -129,13 +130,15 @@ for volunteers to create a Graphical User Interface :-)
The eoValueParam
class, templatized by the type of the variable
-you want to handle (i.e. iinteger, double,
-yourPrivateClass, ...). In this lesson,
-we will not go into details: e.g. we will not tell you that the
+you want to handle (i.e. iinteger,
+double, yourPrivateClass, ...). In
+this lesson, we will not go into details: e.g. we will not tell you that
+the
eoValueParam
is actually a templatized sub-class of abstract class eoParam (oops, I
said it!), nor will we deal with parameters outside their use from an eoParser.
-See the parameter section of the Component-Based tutorial, or wait until lesson
+See the parameter section of the Component-Based tutorial, or wait until
+lesson
4).
@@ -170,7 +173,8 @@ and optionally by a short (1 character) keyword.
-
+
+
--longKeyword=value
or -c=value
if 'c' is the short keyword
@@ -180,18 +184,21 @@ so, after compiling the executable for Lesson 3 (ma
lesson3 at system prompt in Unix), you can try to type
in
-
+
+
SecondBitEA
and see the algorithm run as before (OneMax optimized on 8-bits bitstrings).
But you can now type in
-
+
+
SecondBitEA --vecSize=100
and see the output of the optimization of OneMax on 100-bit bitstrings.
Take a look at all available parameters by typing in
-
+
+
SecondBitEA --help
or by going into the code: all parameter inputs have been grouped in
the
@@ -203,8 +210,7 @@ it contains the list of all actual parameters used, and can directly be
used as parameter input file: change the file name (e.g. to SecondBitEA.param),
edit it, change whichever parameter you want, and type in
-
-
+
SecondBitEA @SecondBitEA.param
and you will see all values that you defined into the file taken into
account.
@@ -216,34 +222,31 @@ new value directly on the command-line.
Programming parameter input:
the code of SeconBitEA provides examples of parameters reading. Lets
-take the example of the random number generator seed.
+take the example of the random number generator seed.
+Of course, you first need to declare
+an eoParser object (it needs the standard argc and argv in its constructor).
-
-You first need to declare it
-in the main_function. As parameter
-reading will be done in the read_param
-function, you need to pass it the variable seed. Note that read_param receives
-it by reference, as it is going
-to modify its value!
+You must first declare a parameter
+of type uint32 (32-bits integer).
+The arguments are: default value, long keyword, comment (that will appear
+in the help message and in the output "status" file if any) and optional
+character keyword.
-
-In read_param, you need first to declare
-an eoParser object (it needs the standard argc and argv in its constructor).
+Then you must pass it to the parser
+using the processParam method. The optional argument is a section name,
+that will be used to make the output of the parser look clean and ordered.
-
Then, declare a parameter
-of type uint32 (32-bits integer),
-and read it directly from the parser, using method create_param.
-The arguments are obvious: default value, long keyword, comment (that will
-appear in the help message and in the output "status" file if any).
-
Finally, you need to assign the
-value to the variable _seed (hence modifying the original seed variable).
+value to the variable seed
eoState:
-saving and loading
-
You might have noticed in the read_param
+saving and loadingYou might have
+noticed in the read_param
described above a new parameter
named load_name.
Now if you go to the init section of
@@ -347,12 +350,12 @@ the corresponding eoStat objects, and add
them to the eoCheckpoint you
use in the algorithm.
Note: actually, there are 2 distinct
-classes that compute and give access to statistics: eoStat
-and eoSortedStat. As its name
-indicate, the latter is used whenever computing the statistics require
-a sorted population: not only this avoids to sort the population many times,
-but also it avoids changing the order of the population at all as eoSortedStat
-work on a temporary vector of fitnesses . But as
+classes that compute and give access to statistics: eoStatand
+eoSortedStat.
+As its name indicate, the latter is used whenever computing the statistics
+require a sorted population: not only this avoids to sort the population
+many times, but also it avoids changing the order of the population at
+all as eoSortedStat work on a temporary vector of fitnesses . But as
far as their usage is concerned, its makes no difference.
@@ -372,13 +375,12 @@ parameters in text format on the screen. The
false, parsimonious output displays one line for all parameters.
-eoFileMonitor writes its
-parameters in text format in a file. A file
-name is required in the constructor, and an optional separator character
-can be added (default is ' '). Note that the file is by default overwritten
-by next call to the same program, unless you pass "true" as third (optional)
-boolean parameter, which will result in appending to the file if it
-ever exists.
+eoFileMonitor writes its parameters
+in text format in a file. A file name is required
+in the constructor, and an optional separator character can be added (default
+is ' '). Note that the file is by default overwritten by next call to the
+same program, unless you pass "true" as third (optional) boolean parameter,
+which will result in appending to the file if it ever exists.
eoGnuplot1DMonitor displays
@@ -521,7 +523,8 @@ construct.
Main page -
Algorithm-Based
- Component-Based - Hints
-- EO documentation
+- EO
+documentation