Difference between revisions of "RoboCup Simulator"

From RoboJackets Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==64 bit==
+
The simulator, <tt>simulator</tt>, is used heavily for off-line development and testing.  It provides the same interfaces as <tt>ssl-vision</tt> and <tt>radio</tt>, allowing <tt>soccer</tt> to run in (nearly) the same way for simulation and real operation.
* perform the following actions to be able to compile for a 64bit system
 
# ''sudo dpkg -i --force-architecture libphysx-*''
 
# ''sudo aptitude install libc6-dev-i386''
 
# ''sudo aptitude install g++-multilib''
 
# ''sudo aptitude install ia32-libs''
 
# ''if you don't have a libQtOpenGL library in /usr/lib32, get it from a 32bit deb''
 
# make symbolic links to libraries in /usr/lib32
 
#* ''ln -s libQtOpenGL.so.4 libQtOpenGL.so''
 
#* ''ln -s libQtCore.so.4 libQtCore.so''
 
#* ''ln -s libQtGui.so.4 libQtGui.so''
 
#* ''ln -s libQtXml.so.4 libQtXml.so''
 
#* ''ln -s libQtNetwork.so.4 libQtNetwork.so''
 
#* ''ln -s libGLU.so.1 libGLU.so''
 
#* ''ln -s libGL.so.1 libGL.so''
 
#* ''ln -s libXext.so.6 libXext.so''
 
#* ''ln -s libX11.so.6 libX11.so''
 
  
==Links==
+
==Invocation==
[http://awakenedmmo.org/docs/physx/html/index.html PhysX Documentation]
+
<pre>
 +
./simulator [-c <config file>] [--sv]
 +
</pre>
  
==Running the Simulator==
+
The configuration file specifies the number and model of the robots on the blue team and yellow team.
#Build components
+
 
#*soccer
+
If no configuration file is given, it will use <tt>simulator.cfg</tt> in the current directory.
#*SoccSim
+
 
#Run System
+
* <tt>--sv</tt> causes the simulator to send data to the <tt>ssl-vision</tt> multicast address. <b>Do not use this on a competition network!</b>
##Execute "/SoccSim/bin/soccsim" - This will start the simulation engine, with a 3D wireframe view of the field and robots.
+
 
##Execute "/soccer/bin/soccer <-y|-b> -c ../config/sim.xml" - This starts the soccer control system, with your choice of yellow (-y) or blue (-b) teams, as well as a configuration file.
+
==Limitations==
 +
* Only outputs data for one camera. Ball-occlusion simulation is still done as if there were two cameras.
 +
* No carpet effects such as loss of traction and variable height.
 +
* Only partial simulation of robot status in RadioRx packets.
 +
 
 +
[[Category: RoboCup]]

Latest revision as of 23:11, 13 June 2018

The simulator, simulator, is used heavily for off-line development and testing. It provides the same interfaces as ssl-vision and radio, allowing soccer to run in (nearly) the same way for simulation and real operation.

Invocation

./simulator [-c <config file>] [--sv]

The configuration file specifies the number and model of the robots on the blue team and yellow team.

If no configuration file is given, it will use simulator.cfg in the current directory.

  • --sv causes the simulator to send data to the ssl-vision multicast address. Do not use this on a competition network!

Limitations

  • Only outputs data for one camera. Ball-occlusion simulation is still done as if there were two cameras.
  • No carpet effects such as loss of traction and variable height.
  • Only partial simulation of robot status in RadioRx packets.