AutoMoDe Arena Experiments - Revision history

Aligot: /* Getting started */

2019-03-26T11:33:03Z

Getting started

Aligot: /* Getting started */

2019-03-26T11:32:18Z

Getting started

JonasKuckling: /* Preparing the robots */ Added instructions to upload files

2018-04-10T09:02:16Z

Preparing the robots: Added instructions to upload files

JonasKuckling: Added compilation instructions

2018-03-29T12:18:50Z

Added compilation instructions

JonasKuckling at 12:17, 29 March 2018

2018-03-29T12:17:56Z

JonasKuckling at 10:44, 29 March 2018

2018-03-29T10:44:57Z

JonasKuckling: Added first stepst to cross compile

2018-03-29T10:44:27Z

Added first stepst to cross compile

JonasKuckling: Moved checklist to top

2018-03-29T08:16:19Z

Moved checklist to top

JonasKuckling: Added some more titles

2018-03-29T07:49:50Z

Added some more titles

JonasKuckling: Added text to running experiments.

2018-03-27T20:22:33Z

Added text to running experiments.

@@ Line 11: / Line 11: @@
 You will need an account on the arena computer (?) and for the Iridia Tracking System.
-Setup virtual network interface to connect to e-puck network:
+Setup virtual network interface to connect to e-puck network: <code> sudo ifconfig enp2s0:0 10.0.1.95
 == Generating the files ==

@@ Line 9: / Line 9: @@
 Ken has already prepared a number of helpful scripts that can help when running experiments in the arena. They are available on his github account.
-You will need an account on the arena computer (?) and for the Iridia Tracking System. Ask Ken (?) if he can help you set them up.
+You will need an account on the arena computer (?) and for the Iridia Tracking System.
 == Generating the files ==

← Older revision		Revision as of 09:02, 10 April 2018
Line 41:		Line 41:

	Uploading scripts to the e-pucks can be done by either one of two scripts that Ken provided: makeupload.py or massupload.py. The main difference between the two scripts is that makeupload.py will make the AutoMoDe executable and upload it to the specified e-pucks, while massupload will simply copy folders and files from the arena computer to the e-pucks. '''TODO:''' Explain more about how these scripts work and the epucks.json file that they use.		Uploading scripts to the e-pucks can be done by either one of two scripts that Ken provided: makeupload.py or massupload.py. The main difference between the two scripts is that makeupload.py will make the AutoMoDe executable and upload it to the specified e-pucks, while massupload will simply copy folders and files from the arena computer to the e-pucks. '''TODO:''' Explain more about how these scripts work and the epucks.json file that they use.
		+
		+	One way of uploading all the files can be done by:
		+	# Open a terminal in the <code>build_epuck</code> folder for the tracking system, and all of your controllers.
		+	# Then run <code>python3 /path/to/makeupload.py -j /path/to/epucks.json -c <name of the controller in your epucks.json file></code>
		+	# Open a terminal in where you generated the experiment files (that is RobotFiles and PCFiles)
		+	# Then run <code>python3 /path/to/massupload.py -j /path/to/epucks.json -c <name of the controller in your epucks.json file></code>

	Once all the necessary scripts are uploaded to the e-pucks, place them in the arena and make sure that the tags on the top are pointing to the front of the e-puck.		Once all the necessary scripts are uploaded to the e-pucks, place them in the arena and make sure that the tags on the top are pointing to the front of the e-puck.

@@ Line 23: / Line 23: @@
 # In the folder build_epuck run the usual cmake command for that project in your terminal but add the following parameter to cmake <code>-DCMAKE_TOOLCHAIN_FILE=path/to/your/TargetEPuck.cmake</code>
 # Once cmake completed without any errors, run make and get your executable or library.
-# Sometimes you need to install the so created executable or library to the cross-compiler for future linking. Running <code>sudo make install</code> will do so, but also has the side effect of changing the include path <code>lib.d</code>.
+# Sometimes you need to install the so created executable or library to the cross-compiler for future linking. Running <code>sudo make install</code> will do so, but also has the side effect of changing the include path <code>lib.d</code>. '''Question:''' Does this only happen for sudo make install or also for just make install?
 === Generating mission files ===

@@ Line 22: / Line 22: @@
 #* Do we need to compile first before cross-compiling?
 # In the folder build_epuck run the usual cmake command for that project in your terminal but add the following parameter to cmake <code>-DCMAKE_TOOLCHAIN_FILE=path/to/your/TargetEPuck.cmake</code>
 === Generating mission files ===

← Older revision		Revision as of 10:44, 29 March 2018
Line 14:		Line 14:

	=== Compiling libraries and executables ===		=== Compiling libraries and executables ===
		+
		+	In order to run ARGoS and AutoMoDe on the e-pucks, you need to crosscompile all necessary libraries.
		+	# Download the cross-compiler that Ken build ('''TODO:''' Link) and extract it on your computer
		+	# Open the TargetEPuck.cmake file and change each occurence of <code>/usr/local/angstrom/arm</code> with the path to the crosscompiler. '''TODO:''' Verify that this is the correct path.
		+	#* Instead of changing every .cmake file on your system, you can also setup only one TargetEPuck.cmake file and reference it from all of your projects.
		+	# Add to folders to the root level of your project: build and build_epuck
		+	#* Do we need to compile first before cross-compiling?
		+	# In the folder build_epuck run the usual cmake command for that project in your terminal but add the following parameter to cmake <code>-DCMAKE_TOOLCHAIN_FILE=<path/to/your/TargetEPuck.cmake></code>

	=== Generating mission files ===		=== Generating mission files ===

@@ Line 1: / Line 1: @@
 This page is in a very early stage. If you have any questions about the contents of this page, ask Ken or Jonas.
 == Getting started ==
@@ Line 42: / Line 46: @@
 == Trouble shooting ==

@@ Line 8: / Line 8: @@
 == Generating the files ==
 The script <code>ExpGen.py</code> generates most of the files that you will need to run your experiments. It takes a couple of arguments (a short summary can be obtained by the -h option). ('''TODO: Explain the arguments a little bit more''')
@@ Line 36: / Line 40: @@
 == Cleaning up again ==
 == Checklist ==

@@ Line 24: / Line 24: @@
 Uploading scripts to the e-pucks can be done by either one of two scripts that Ken provided: makeupload.py or massupload.py. The main difference between the two scripts is that makeupload.py will make the AutoMoDe executable and upload it to the specified e-pucks, while massupload will simply copy folders and files from the arena computer to the e-pucks. '''TODO:''' Explain more about how these scripts work and the epucks.json file that they use.
-Once all the necessary scripts are uploaded to the e-pucks, place them in the arena and you can start to run your experiment.
+Once all the necessary scripts are uploaded to the e-pucks, place them in the arena and make sure that the tags on the top are pointing to the front of the e-puck.
 == Running the experiments ==
 == Cleaning up again ==