Commit 2e7f985f authored by LIGNEUL CLEMENT's avatar LIGNEUL CLEMENT
Browse files

Merge branch 'Develop' into 'master'

Easea compiler app v2 finished

See merge request !6
parents 54b10fa5 d669eccc
......@@ -2,7 +2,7 @@
_GREEN=$'\x1b[32m'
_END=$'\x1b[0m'
# get Os
# get Os name
UNAME:=$(shell uname)
install:
......@@ -12,7 +12,7 @@ install:
@echo "\n##### Beginning of the packaging #####\n"
@echo "\n##### Initialization #####\n"
@echo "\n##### Initialization #####\n"
rm -rf deploy dist
......@@ -22,10 +22,12 @@ install:
ifeq ($(UNAME), Linux)
cp -rf src/plot.py src/3D_plot.py documentation/ deploy/linux/EASEA-compiler-app/
cp -Rf src/ deploy/linux/EASEA-compiler-app/
endif
ifeq ($(UNAME), Darwin)
cp -rf src/plot.py src/3D_plot.py documentation/ deploy/darwin/EASEA-compiler-app/
cp -Rf src/ deploy/darwin/EASEA-compiler-app/
endif
@echo "\n##### Build dist #####\n"
......@@ -46,7 +48,7 @@ endif
@echo "\n##### Installing executable #####\n"
sudo cp EASEA-compiler-app/easea-compiler-app /bin
sudo cp EASEA-compiler-app/easea-compiler-app /usr/local/easena/bin/easea-compiler-app
@printf "\033[32m\n##### Installation complete #####\n\n\033[0m"
......@@ -58,6 +60,6 @@ uninstall:
@echo "\n##### Uninstalling executable #####\n"
sudo rm -rf /bin/easea-compiler-app
sudo rm -rf /usr/local/easena/bin/easea-compiler-app
@printf "\033[32m\n##### Uninstallation completed #####\n\n\033[0m"
......@@ -33,15 +33,20 @@ To use this program, it is necessary to have installed the most recent version o
- Clone this repository
- Run `sudo make install` in `easea-compiler-app/`
- To run the application run the executable in `EASEA-compiler-app/easea-compiler-app` or run `easea-compiler-app` if the command is installed
- To run the application run `easea-compiler-app`
- To remove the generated executable use `make uninstall`
(DEV) To run the application execute `npm start`
---
## Next features
- Gitlab pages for documentation
## Features in development
- Multiple runs with intervals of population, generations etc...
- 1 plot by run
- Plot more than the best fitness
- Quick EASEA file editor (new tab)
- New run options (genetic programming, ...)
- More run stats (number of runs above/below a certain fitness)
---
## Contact
......
= EASEA Compiler App Documentation
Clément Ligneul <clement.ligneul@etu.unistra.fr>
v1.3 2021-09-12
v2.0 13/02/2022
:toc: left
:toclevels: 4
:hide-uri-scheme:
......@@ -50,16 +50,22 @@ Note that if you are using macOS, plotly only works on version 10.10 or more (OS
== Installation
Once the dependencies are installed :
Once the dependencies are installed, if you are using the https://git.unistra.fr/ligneul/easea-compiler-app[development repository, window=_blank]:
- clone https://git.unistra.fr/ligneul/easea-compiler-app[this repository, window=_blank]
- run `make install` in the main directory
- now you can run the executable in `EASEA-compiler-app/` named `easea-compiler-app`. If the executable is installed, you can also run `easea-compiler-app` from anywhere
- run `make uninstall` in the main directory to uninstall the application
== Dev version
If you are installing the interface from the https://github.com/EASEA/easea[EASEA github repository, window=_blank]:
Running `npm start` in the main directory will allow you to see all the debugging information in the terminal. This is useful if you have any problems. This command recompiles everything each time you use it. You can also see debugging information from the executable if you run it into a terminal.
- move to the `easea-interface/` directory with `cd easea/easea-interface/`
- run `sudo make install`
- you can now launch the application with the `easea-compiler-app` command from anywhere.
- to uninstall the application run `make uninstall` from the directory `easea/easea-interface/`
// == Dev version
// Running `npm start` in the main directory will allow you to see all the debugging information in the terminal. This is useful if you have any problems. This command recompiles everything each time you use it. You can also see debugging information from the executable if you run it into a terminal.
== Quick tutorials
......@@ -73,7 +79,7 @@ In this tutorial we will compile and run the file `weierstrass.ez` from the `/ex
. We don't use any options in this compilation so just click on the `Compile` button
. After clicking on this button you see this :
image::images/compile_weierstrass.png[compile_weierstrass image, 700, align=center]
image::images/compile_weierstrass.png[compile_weierstrass image, 800, align=center]
==== Run
......@@ -91,7 +97,7 @@ If the run finished correctly you can now see the plot in the Result Plot tab (s
=== Run in batch
[red]#Don't use the run in batch if you have compiled with options for <<Multi-objective problems, Multi-objective problems>>.#
// [red]#Don't use the run in batch if you have compiled with options for <<Multi-objective problems, Multi-objective problems>>.#
This application allows to run the same program several times at the same time (batch). In this tutorial we will use the file `weierstrass.ez` from the `/examples` directory of EASEA.
......@@ -105,11 +111,11 @@ image::images/general_menu_batch.png[general menu batch image, 850, align=center
4) At the end of these runs you should see something like this :
image::images/end_run_batch.png[end run batch image, 700, align=center]
image::images/end_run_batch.png[end run batch image, 800, align=center]
5) In the `Result Plot` tab you can see the graph generated as we requested : 5 violin plots (for more informations about this graph see <<Result Plot tab>>)
image::images/2d_results.png[2d results image, 700, align=center]
image::images/2d_results.png[2d results image, 800, align=center]
== Interface detailed
......@@ -121,7 +127,7 @@ The last one is dedicated to plotting the results according to the compilation a
=== Compile tab
image::images/empty_compile.png[empty compilation image, 700, align=center]
image::images/empty_compile.png[empty compilation image, 800, align=center]
① Load your file
......@@ -139,7 +145,7 @@ EASEA offers many options for compiling your `.ez` projects. If you want to see
You must compile your project before running it.
image::images/islands_activated.png[island activation image, 700, align=center]
image::images/islands_activated.png[island activation image, 800, align=center]
① Size of the batch (see <<Run in batch>>)
......@@ -213,7 +219,8 @@ image::images/general_menu.png[general menu image, 900, align=center]
- [underline]#Compression# : Set the compression level
- [underline]#Batch Size# : Number of runs at the same time. [red]#Don't use this option if you have compiled with options for <<Multi-objective problems>>#
- [underline]#Batch Size# : Number of runs at the same time. Batch size is currently limited to 500 but it is recommended to limit to 30. [red]#Caution: run a very large number of executions may cause malfunctions depending on the capabilities of the machine#
// [red]#Don't use this option if you have compiled with options for <<Multi-objective problems>>#
- [underline]#Nb Of Threads# : Number of threads to use
......@@ -257,13 +264,19 @@ This menu is available after activating the remote island model
image::images/island_menu.png[island menu image, 300, align=center]
- [underline]#Migration Probability# : Probability to send an individual each generation
- [underline]#Batch Type# : Type of island model (local or remote)
- [underline]#Ports/machines available# : Number of ports for local executions and machines for remote executions usable
- [underline]#IP file# : File containing all the IPs of the remote islands
- [underline]#Number of islands per run# : Number of islands per run
- [underline]#Server Port# : Port of the server
- [underline]#IP file# : File containing all the IPs of the remote islands. IP files are automatically generated in local mode
- [underline]#Evaluate Immigrants# : ...
- [underline]#Migration Probability# : Probability to send an individual each generation
- [underline]#Evaluate Immigrants# : Evaluate Immigrants
Note that the island model execution does not produce a result plot.
==== See Results
......@@ -295,7 +308,7 @@ In this file we have 35 generations. We choose to run a batch of 10 and print 5
The first graph takes the 7 first generations, the second takes the next 7 etc...
image::images/2d_results.png[2d results image, 700, align=center]
image::images/2d_results.png[2d results image, 800, align=center]
The image quality is reduced to put it in the application, we recommend using the interactive version of the graph to see the details.
......@@ -319,13 +332,14 @@ In each graph there are 3 elements :
- ③ The box plot
link:./images/interactive_2d.html[Here, window=_blank] is an example of a 2D graph.
==== 3D plot
This plot replaces the graph with the violin plots if you have compiled and run a program with the options for <<Multi-objective problems>>.
image::images/3D_update.png[3d results image, 700, align=center]
image::images/3D_update.png[3d results image, 800, align=center]
==== 3D plot interactive version
......@@ -339,6 +353,8 @@ Right click moves the graph on the x y axis.
You can reset the view with the toolbar at the top right.
link:./images/interactive_3d.html[Here, window=_blank] is an example of a 3D graph.
==== Save the results graph
To save the results you can click on the appropriate button :
......@@ -351,13 +367,15 @@ We recommend to save your plots from the interactive version with camera icon. T
==== Edit the results graph
image::images/update_menu.png[ update plot menu image, 300, align=center]
image:images/update_menu.png[ update plot menu image, 300, align=center]
image:images/update_menu_3d.png[ update plot menu image, 300, align=center]
Once you have generated the result plot you can edit it. It is possible to change :
- The plot title
- The axis name if the plot is a 3D plot
- The axis names
- The number of violin plots if the plot is a 2D plot
- The plot color if it is a 2D graph
== Multi-objective problems
......@@ -369,7 +387,7 @@ Compilation options for multi-objective problems are :
- `ibea`
- `cdas`
If you use one of these options do not run in batch because the results will be overwritten with each other.
//If you use one of these options do not run in batch because the results will be overwritten with each other.
== Tips
......
......@@ -444,7 +444,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div class="details">
<span id="author" class="author">Clément Ligneul</span><br>
<span id="email" class="email"><a href="mailto:clement.ligneul@etu.unistra.fr">clement.ligneul@etu.unistra.fr</a></span><br>
<span id="revnumber">version 1.3 2021-09-12</span>
<span id="revnumber">version 2.0 13/02/2022</span>
</div>
<div id="toc" class="toc2">
<div id="toctitle">Table of Contents</div>
......@@ -462,7 +462,6 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</ul>
</li>
<li><a href="#_installation">Installation</a></li>
<li><a href="#_dev_version">Dev version</a></li>
<li><a href="#_quick_tutorials">Quick tutorials</a>
<ul class="sectlevel2">
<li><a href="#_simple_run">Simple run</a>
......@@ -614,14 +613,11 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<h2 id="_installation">Installation</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Once the dependencies are installed :</p>
<p>Once the dependencies are installed, if you are using the <a href="https://git.unistra.fr/ligneul/easea-compiler-app" target="_blank" rel="noopener">development repository</a>:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>clone <a href="https://git.unistra.fr/ligneul/easea-compiler-app" target="_blank" rel="noopener">this repository</a></p>
</li>
<li>
<p>run <code>make install</code> in the main directory</p>
</li>
<li>
......@@ -632,13 +628,24 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_dev_version">Dev version</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Running <code>npm start</code> in the main directory will allow you to see all the debugging information in the terminal. This is useful if you have any problems. This command recompiles everything each time you use it. You can also see debugging information from the executable if you run it into a terminal.</p>
<p>If you are installing the interface from the <a href="https://github.com/EASEA/easea" target="_blank" rel="noopener">EASEA github repository</a>:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>move to the <code>easea-interface/</code> directory with <code>cd easea/easea-interface/</code></p>
</li>
<li>
<p>run <code>sudo make install</code></p>
</li>
<li>
<p>you can now launch the application with the <code>easea-compiler-app</code> command from anywhere.</p>
</li>
<li>
<p>to uninstall the application run <code>make uninstall</code> from the directory <code>easea/easea-interface/</code></p>
</li>
</ul>
</div>
</div>
</div>
......@@ -667,7 +674,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/compile_weierstrass.png" alt="compile_weierstrass image" width="700">
<img src="images/compile_weierstrass.png" alt="compile_weierstrass image" width="800">
</div>
</div>
</div>
......@@ -696,9 +703,6 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div class="sect2">
<h3 id="_run_in_batch">Run in batch</h3>
<div class="paragraph">
<p><span class="red">Don&#8217;t use the run in batch if you have compiled with options for <a href="#_multi_objective_problems">Multi-objective problems</a>.</span></p>
</div>
<div class="paragraph">
<p>This application allows to run the same program several times at the same time (batch). In this tutorial we will use the file <code>weierstrass.ez</code> from the <code>/examples</code> directory of EASEA.</p>
</div>
<div class="paragraph">
......@@ -720,7 +724,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/end_run_batch.png" alt="end run batch image" width="700">
<img src="images/end_run_batch.png" alt="end run batch image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -728,7 +732,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/2d_results.png" alt="2d results image" width="700">
<img src="images/2d_results.png" alt="2d results image" width="800">
</div>
</div>
</div>
......@@ -750,7 +754,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<h3 id="_compile_tab">Compile tab</h3>
<div class="imageblock text-center">
<div class="content">
<img src="images/empty_compile.png" alt="empty compilation image" width="700">
<img src="images/empty_compile.png" alt="empty compilation image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -779,7 +783,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/islands_activated.png" alt="island activation image" width="700">
<img src="images/islands_activated.png" alt="island activation image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -894,7 +898,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<p><span class="underline">Compression</span> : Set the compression level</p>
</li>
<li>
<p><span class="underline">Batch Size</span> : Number of runs at the same time. <span class="red">Don&#8217;t use this option if you have compiled with options for <a href="#_multi_objective_problems">Multi-objective problems</a></span></p>
<p><span class="underline">Batch Size</span> : Number of runs at the same time. Batch size is currently limited to 500 but it is recommended to limit to 30. <span class="red">Caution: run a very large number of executions may cause malfunctions depending on the capabilities of the machine</span></p>
</li>
<li>
<p><span class="underline">Nb Of Threads</span> : Number of threads to use</p>
......@@ -982,19 +986,28 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div class="ulist">
<ul>
<li>
<p><span class="underline">Migration Probability</span> : Probability to send an individual each generation</p>
<p><span class="underline">Batch Type</span> : Type of island model (local or remote)</p>
</li>
<li>
<p><span class="underline">Ports/machines available</span> : Number of ports for local executions and machines for remote executions usable</p>
</li>
<li>
<p><span class="underline">Number of islands per run</span> : Number of islands per run</p>
</li>
<li>
<p><span class="underline">IP file</span> : File containing all the IPs of the remote islands</p>
<p><span class="underline">IP file</span> : File containing all the IPs of the remote islands. IP files are automatically generated in local mode</p>
</li>
<li>
<p><span class="underline">Server Port</span> : Port of the server</p>
<p><span class="underline">Migration Probability</span> : Probability to send an individual each generation</p>
</li>
<li>
<p><span class="underline">Evaluate Immigrants</span> : &#8230;&#8203;</p>
<p><span class="underline">Evaluate Immigrants</span> : Evaluate Immigrants</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>Note that the island model execution does not produce a result plot.</p>
</div>
</div>
<div class="sect3">
<h4 id="_see_results">See Results</h4>
......@@ -1048,7 +1061,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/2d_results.png" alt="2d results image" width="700">
<img src="images/2d_results.png" alt="2d results image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -1094,6 +1107,9 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</li>
</ul>
</div>
<div class="paragraph">
<p><a href="./images/interactive_2d.html" target="_blank" rel="noopener">Here</a> is an example of a 2D graph.</p>
</div>
</div>
<div class="sect3">
<h4 id="_3d_plot">3D plot</h4>
......@@ -1102,7 +1118,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/3D_update.png" alt="3d results image" width="700">
<img src="images/3D_update.png" alt="3d results image" width="800">
</div>
</div>
</div>
......@@ -1125,6 +1141,9 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div class="paragraph">
<p>You can reset the view with the toolbar at the top right.</p>
</div>
<div class="paragraph">
<p><a href="./images/interactive_3d.html" target="_blank" rel="noopener">Here</a> is an example of a 3D graph.</p>
</div>
</div>
<div class="sect3">
<h4 id="_save_the_results_graph">Save the results graph</h4>
......@@ -1147,10 +1166,9 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="sect3">
<h4 id="_edit_the_results_graph">Edit the results graph</h4>
<div class="imageblock text-center">
<div class="content">
<img src="images/update_menu.png" alt="update plot menu image" width="300">
</div>
<div class="paragraph">
<p><span class="image"><img src="images/update_menu.png" alt="update plot menu image" width="300"></span>
<span class="image"><img src="images/update_menu_3d.png" alt="update plot menu image" width="300"></span></p>
</div>
<div class="paragraph">
<p>Once you have generated the result plot you can edit it. It is possible to change :</p>
......@@ -1161,11 +1179,14 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<p>The plot title</p>
</li>
<li>
<p>The axis name if the plot is a 3D plot</p>
<p>The axis names</p>
</li>
<li>
<p>The number of violin plots if the plot is a 2D plot</p>
</li>
<li>
<p>The plot color if it is a 2D graph</p>
</li>
</ul>
</div>
</div>
......@@ -1197,9 +1218,6 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</li>
</ul>
</div>
<div class="paragraph">
<p>If you use one of these options do not run in batch because the results will be overwritten with each other.</p>
</div>
</div>
</div>
<div class="sect1">
......@@ -1239,8 +1257,8 @@ Attribution - Non Commercial 4.0 International" license</p>
</div>
<div id="footer">
<div id="footer-text">
Version 1.3 2021-09-12<br>
Last updated 2021-09-12 10:17:49 +0200
Version 2.0 13/02/2022<br>
Last updated 2022-02-14 09:41:56 +0100
</div>
</div>
</body>
......
This diff is collapsed.
......@@ -444,7 +444,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div class="details">
<span id="author" class="author">Clément Ligneul</span><br>
<span id="email" class="email"><a href="mailto:clement.ligneul@etu.unistra.fr">clement.ligneul@etu.unistra.fr</a></span><br>
<span id="revnumber">version 1.3 2021-09-12</span>
<span id="revnumber">version 2.0 13/02/2022</span>
</div>
<div id="toc" class="toc2">
<div id="toctitle">Table des matières</div>
......@@ -457,7 +457,6 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</ul>
</li>
<li><a href="#_installation">Installation</a></li>
<li><a href="#_version_développeur">Version développeur</a></li>
<li><a href="#_tutoriels">Tutoriels</a>
<ul class="sectlevel2">
<li><a href="#_simple_exécution">Simple exécution</a>
......@@ -588,7 +587,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</ul>
</div>
<div class="paragraph">
<p>Notez que plotly ne fonctionne qu&#8217;à partir de la version 10.10 sur macOS (64 bit seulement).</p>
<p>Notez que plotly ne fonctionne qu&#8217;à partir de la version 10.10 de macOS (64 bit seulement).</p>
</div>
</div>
</div>
......@@ -597,31 +596,39 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<h2 id="_installation">Installation</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Une fois les dépendances installées :</p>
<p>Une fois les dépendances installées si vous utilisez le <a href="https://git.unistra.fr/ligneul/easea-compiler-app" target="_blank" rel="noopener">dépôt de développement</a> :</p>
</div>
<div class="ulist">
<ul>
<li>
<p>clonez <a href="https://git.unistra.fr/ligneul/easea-compiler-app" target="_blank" rel="noopener">ce dépôt</a></p>
</li>
<li>
<p>exécutez <code>sudo make install</code> dans le repertoire principal</p>
</li>
<li>
<p>vous pouvez maintenant lancer l&#8217;application avec l&#8217;exécutable <code>easea-compiler-app</code> dans le répertoire <code>EASEA-compiler-app/</code>. Si l&#8217;exécutable est installé vous pouvez lancer l&#8217;application avec la commande <code>easea-compiler-app</code> depuis n&#8217;importe où.</p>
<p>vous pouvez maintenant lancer l&#8217;application avec la commande <code>easea-compiler-app</code> depuis n&#8217;importe où.</p>
</li>
<li>
<p>pour désinstaller l&#8217;application faites <code>make uninstall</code> depuis le répertoire principal</p>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_version_développeur">Version développeur</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Lancer la commande <code>npm start</code> dans le répertoire principal permet d&#8217;ouvrir l&#8217;application sans devoir générer d&#8217;exécutable mais aussi d&#8217;afficher dans la console les informations pouvant servir au débogage. Démarrer l&#8217;application en lançant l&#8217;exécutable depuis une console permet aussi d&#8217;afficher ces informations.</p>
<p>Si vous installez l&#8217;interface depuis le <a href="https://github.com/EASEA/easea" target="_blank" rel="noopener">dépôt github d&#8217;EASEA</a> :</p>
</div>
<div class="ulist">
<ul>
<li>
<p>déplacez-vous dans le répertoire <code>easea-interface</code> avec <code>cd easea/easea-interface/</code></p>
</li>
<li>
<p>exécutez <code>sudo make install</code></p>
</li>
<li>
<p>vous pouvez maintenant lancer l&#8217;application avec la commande <code>easea-compiler-app</code> depuis n&#8217;importe où.</p>
</li>
<li>
<p>pour désinstaller l&#8217;application faites <code>make uninstall</code> depuis le répertoire <code>easea/easea-interface/</code></p>
</li>
</ul>
</div>
</div>
</div>
......@@ -650,7 +657,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/compile_weierstrass.png" alt="compile_weierstrass image" width="700">
<img src="images/compile_weierstrass.png" alt="compile_weierstrass image" width="800">
</div>
</div>
</div>
......@@ -676,9 +683,6 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<div class="sect2">
<h3 id="_exécution_en_batch">Exécution en batch</h3>
<div class="paragraph">
<p><span class="red">N&#8217;utilisez pas l&#8217;exécution en batch avec les options de compilation pour <a href="#_problèmes_multi_objectifs">problèmes multi-objectifs</a> car seuls les resultats vont s&#8217;écraser entre eux</span></p>
</div>
<div class="paragraph">
<p>Cette application permet de lancer plusieurs fois le même programme en même temps (batch). Dans ce tutoriel nous utiliserons le fichier <code>weierstrass.ez</code> du répertoire <code>/examples</code> d&#8217;EASEA.</p>
</div>
<div class="paragraph">
......@@ -700,7 +704,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/end_run_batch.png" alt="end run batch image" width="700">
<img src="images/end_run_batch.png" alt="end run batch image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -708,7 +712,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/2d_results.png" alt="2d results image" width="700">
<img src="images/2d_results.png" alt="2d results image" width="800">
</div>
</div>
</div>
......@@ -730,7 +734,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<h3 id="_onglet_compile">Onglet Compile</h3>
<div class="imageblock text-center">
<div class="content">
<img src="images/empty_compile.png" alt="empty compilation image" width="700">
<img src="images/empty_compile.png" alt="empty compilation image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -759,7 +763,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
</div>
<div class="imageblock text-center">
<div class="content">
<img src="images/islands_activated.png" alt="island activation image" width="700">
<img src="images/islands_activated.png" alt="island activation image" width="800">
</div>
</div>
<div class="paragraph">
......@@ -874,7 +878,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
<p><span class="underline">Compression</span> : Fixe le niveau de compression</p>
</li>
<li>
<p><span class="underline">Batch Size</span> : Nombre d&#8217;exécutions à effectuer. <span class="red">N&#8217;utilisez pas l&#8217;exécution en batch avec les options de compilation pour un <a href="#_problèmes_multi_objectifs">problème multi-objectifs</a></span></p>
<p><span class="underline">Batch Size</span> : Nombre d&#8217;exécutions à effectuer. La taille du batch est actuellement limitée à 500 mais une taille de 30 maximum est recommandée. <span class="red">Attention : lancer un très grand nombre d&#8217;exécutions peut causer des dysfonctionnements selon les capacités de la machine</span></p>
</li>
<li>
<p><span class="underline">Nb Of Threads</span> : Nombre de threads à utiliser pour chaque exécution</p>
......@@ -960,19 +964,28 @@ Par exemple, la première graine vaut 0 et nous avons un batch de taille 3. Si l
<div class="ulist">
<ul>
<li>
<p><span class="underline">Migration Probability</span> : Probabilité d&#8217;envoyer un individu à chaque génération</p>
<p><span class="underline">Batch Type</span> : Type de modèle en ilôt (local ou à distance)</p>
</li>
<li>
<p><span class="underline">Ports/machines available</span> : Nombre de ports, pour les exécutions locales, ou nombre de machines, pour les exécutions à distance, utilisables</p>
</li>
<li>