RoboCup Simulator Execution - Revision history

Cwehmeyer3 at 03:12, 14 June 2018

2018-06-14T03:12:10Z

Rosawa3: recategorizing

2013-11-09T12:51:05Z

recategorizing

Rosawa3 at 07:10, 18 July 2013

2013-07-18T07:10:19Z

Ehuang: /* Starting the Simulator */

2012-09-14T20:45:22Z

‎Starting the Simulator

BenJ at 00:50, 3 August 2010

2010-08-03T00:50:56Z

BenJ at 22:23, 31 January 2010

2010-01-31T22:23:24Z

BenJ at 22:23, 31 January 2010

2010-01-31T22:23:00Z

Alexgc: /* Starting the Simulator */

2010-01-31T21:59:47Z

‎Starting the Simulator

Alexgc at 17:58, 31 January 2010

2010-01-31T17:58:42Z

Alexgc at 22:14, 24 January 2010

2010-01-24T22:14:18Z

← Older revision		Revision as of 03:12, 14 June 2018
Line 52:		Line 52:

	[[Category: RoboCup]]		[[Category: RoboCup]]
−	~~[[Category: Software]]~~

← Older revision		Revision as of 12:51, 9 November 2013
Line 52:		Line 52:

	[[Category: RoboCup]]		[[Category: RoboCup]]
−	[[Category: ~~RoboCup~~ Software]]	+	[[Category: Software]]

← Older revision		Revision as of 07:10, 18 July 2013
Line 50:		Line 50:

	You can now use the SSL referee box to issue commands to both soccers at once.		You can now use the SSL referee box to issue commands to both soccers at once.
		+
		+	[[Category: RoboCup]]
		+	[[Category: RoboCup Software]]

@@ Line 8: / Line 8: @@
 === Starting the Simulator ===
 <pre>
-./soccsim [-c <config file>]
+./simulator [-c <config file>]
 </pre>

@@ Line 1: / Line 1: @@
-The easiest way to get started using the software is to make use of the simulator, which will be most useful for developing much of the actual system. For these instructions, you will need to be in a terminal in your robocup folder (/robocup/software/trunk).  The first scenario will start a simulator with a single robot, and the second scenario will start two teams with referee control.
+The easiest way to get started using the software is to make use of the simulator, which will be most useful for developing much of the actual system.  The first scenario will start a simulator with a single robot, and the second scenario will start two teams with referee control.
-== Before starting the simulator ==
+All of the commands on this page assume you are in the <i>software/run</i> directory.
 <pre>
-sudo ./doc/mcast_route lo
+./soccsim [-c <config file>]
 </pre>
-== Single-team Simulator Use ==
+If no configuration file is given, it will use <i>default.cfg</i> in the current directory.  Currently, <i>default.cfg</i> creates two full teams.
-=== Starting the Simulator ===
+You can kill the simulator with Ctrl-C.
 <pre>
-cd ./SoccSim/bin
+./soccer -sim
 </pre>
-Now the simulator should report that it is running.  To stop the simulator, kill the process by typing Ctrl-C in the terminal where you started it.
+The status indicator in the upper right corner should be yellow and show SIMULATION.
-=== Starting the soccer interface ===
+You can now issue internal referee commands.  Either use the shortcut buttons at the top of the window for the most common commands (they have tooltips) or go to the Referee tab for a complete set of commands.
-Start a new terminal to run soccer from and use the following commands.  This will start the soccer engine using the simulation configuration file (soccer/config/sim.xml) and using the yellow team (use -b for blue team).
 <pre>
-cd [robocup root]/soccer/bin
+./sslrefbox
 </pre>
-You should now see the GUI for the soccer program.  To to a simple check to ensure that everything is working, you want to enable a play to run.  Go to the plays tab and select "testBasicAttack" from the list, then click the green check button (Force Start) in the upper left of the GUI.  You should see one robot go to the goal (because goalie is enabled by default), and another robot drive at the ball and start kicking.
+The referee buttons in both soccers should now be grayed out and the <i>Use external referee</i> checkbox should be checked.  If you have previously changed this checkbox manually, you will need to check it.
-== Using the Soccer interface ==
+You can now use the SSL referee box to issue commands to both soccers at once.

@@ Line 26: / Line 26: @@
 <pre>
 cd [robocup root]/soccer/bin
-./soccer -y -c ../config/sim.xml -p ../playbooks/Default.pbk
+./soccer -y -c ../config/sim.xml
 </pre>

@@ Line 12: / Line 12: @@
 === Starting the Simulator ===
-We will start the simulator to run in a terminal.  You can run the soccsim executable without parameters to get a small explanation of the correct arguments, if necessary.
+We will start the simulator to run in a terminal.  You can run the soccsim executable without parameters to get a small explanation of the correct arguments, if necessary.  Note that you can choose from the config files in the SoccSim/config/ folder to try different scenarios.
 <pre>
@@ Line 22: / Line 22: @@
 === Starting the soccer interface ===
+== Using the Soccer interface ==
-== Running Under Simulation ==
+There's a lot of data available in the GUI to make debugging the robots easier.  The best place to look if you want to see what the robots are doing is in the tree view tab, where all of the data logged or passed through the system is shown in realtime.

← Older revision		Revision as of 22:14, 24 January 2010
Line 1:		Line 1:
		+	The easiest way to get started using the software is to make use of the simulator, which will be most useful for developing much of the actual system. For these instructions, you will need to be in a terminal in your robocup folder (/robocup/software/trunk). The first scenario will start a simulator with a single robot, and the second scenario will start two teams with referee control.
		+
		+	== Before starting the simulator ==
		+	To avoid flooding the network with data from your simulator, we have a script to reroute some networking processes. You will need to follow these instructions once before running the simulator, but the setting will remain correct until you reboot.
		+
		+	<pre>
		+	sudo ./doc/mcast_route lo
		+	</pre>
		+
		+	== Single-team Simulator Use ==
		+	In this case, we will only drive one team, the other team's robots will just remain stationary
		+
		+	=== Starting the Simulator ===
		+	We will start the simulator to run in a terminal. You can run the soccsim executable without parameters to get a small explanation of the correct arguments, if necessary.
		+
		+	<pre>
		+	cd ./SoccSim/bin
		+	./soccsim -c ../config/two_teams.xml &
		+	</pre>
		+
		+	Now the simulator should report that it is running. To stop the simulator, kill the process by typing Ctrl-C in the terminal where you started it.
		+
		+	=== Starting the soccer interface ===
		+
		+
		+
		+
	== Running Under Simulation ==		== Running Under Simulation ==
	* Reroute the multicast packets - this is to keep your simulator from flooding any network you are on with vision packets.		* Reroute the multicast packets - this is to keep your simulator from flooding any network you are on with vision packets.