- 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
@@ -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>>)
@@ -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
<p>Once the dependencies are installed, if you are using the <ahref="https://git.unistra.fr/ligneul/easea-compiler-app"target="_blank"rel="noopener">development repository</a>:</p>
<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 <ahref="https://github.com/EASEA/easea"target="_blank"rel="noopener">EASEA github repository</a>:</p>
</div>
<divclass="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>
<p><spanclass="red">Don’t use the run in batch if you have compiled with options for <ahref="#_multi_objective_problems">Multi-objective problems</a>.</span></p>
</div>
<divclass="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>
<p><spanclass="underline">Compression</span> : Set the compression level</p>
</li>
<li>
<p><spanclass="underline">Batch Size</span> : Number of runs at the same time. <spanclass="red">Don’t use this option if you have compiled with options for <ahref="#_multi_objective_problems">Multi-objective problems</a></span></p>
<p><spanclass="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. <spanclass="red">Caution: run a very large number of executions may cause malfunctions depending on the capabilities of the machine</span></p>
</li>
<li>
<p><spanclass="underline">Nb Of Threads</span> : Number of threads to use</p>
<p>Une fois les dépendances installées si vous utilisez le <ahref="https://git.unistra.fr/ligneul/easea-compiler-app"target="_blank"rel="noopener">dépôt de développement</a>:</p>
<p>exécutez <code>sudo make install</code> dans le repertoire principal</p>
</li>
<li>
<p>vous pouvez maintenant lancer l’application avec l’exécutable <code>easea-compiler-app</code> dans le répertoire <code>EASEA-compiler-app/</code>. Si l’exécutable est installé vous pouvez lancer l’application avec la commande <code>easea-compiler-app</code> depuis n’importe où.</p>
<p>vous pouvez maintenant lancer l’application avec la commande <code>easea-compiler-app</code> depuis n’importe où.</p>
</li>
<li>
<p>pour désinstaller l’application faites <code>make uninstall</code> depuis le répertoire principal</p>
<p>Lancer la commande <code>npm start</code> dans le répertoire principal permet d’ouvrir l’application sans devoir générer d’exécutable mais aussi d’afficher dans la console les informations pouvant servir au débogage. Démarrer l’application en lançant l’exécutable depuis une console permet aussi d’afficher ces informations.</p>
<p>Si vous installez l’interface depuis le <ahref="https://github.com/EASEA/easea"target="_blank"rel="noopener">dépôt github d’EASEA</a> :</p>
</div>
<divclass="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’application avec la commande <code>easea-compiler-app</code> depuis n’importe où.</p>
</li>
<li>
<p>pour désinstaller l’application faites <code>make uninstall</code> depuis le répertoire <code>easea/easea-interface/</code></p>
<h3id="_exécution_en_batch">Exécution en batch</h3>
<divclass="paragraph">
<p><spanclass="red">N’utilisez pas l’exécution en batch avec les options de compilation pour <ahref="#_problèmes_multi_objectifs">problèmes multi-objectifs</a> car seuls les resultats vont s’écraser entre eux</span></p>
</div>
<divclass="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’EASEA.</p>
<p><spanclass="underline">Compression</span> : Fixe le niveau de compression</p>
</li>
<li>
<p><spanclass="underline">Batch Size</span> : Nombre d’exécutions à effectuer. <spanclass="red">N’utilisez pas l’exécution en batch avec les options de compilation pour un <ahref="#_problèmes_multi_objectifs">problème multi-objectifs</a></span></p>
<p><spanclass="underline">Batch Size</span> : Nombre d’exécutions à effectuer. La taille du batch est actuellement limitée à 500 mais une taille de 30 maximum est recommandée. <spanclass="red">Attention : lancer un très grand nombre d’exécutions peut causer des dysfonctionnements selon les capacités de la machine</span></p>
</li>
<li>
<p><spanclass="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
<divclass="ulist">
<ul>
<li>
<p><spanclass="underline">Migration Probability</span> : Probabilité d’envoyer un individu à chaque génération</p>
<p><spanclass="underline">Batch Type</span> : Type de modèle en ilôt (local ou à distance)</p>
</li>
<li>
<p><spanclass="underline">Ports/machines available</span> : Nombre de ports, pour les exécutions locales, ou nombre de machines, pour les exécutions à distance, utilisables</p>
