Difference between revisions of "RoboCup Simulator"

From RoboJackets Wiki
Jump to navigation Jump to search
Line 1: Line 1:
==64 bit==
+
The simulator, <tt>soccsim</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>
 +
./soccsim [-c <config file>] [--ui] [--sv]
 +
</pre>
  
==Running the Simulator==
+
If no configuration file is given, it will use <tt>simulator.cfg</tt> in the current directory.
#Build components
+
 
#*soccer
+
* <tt>--ui</tt> displays a GUI that is really only useful for debugging the geometry given to the physics engine.
#*SoccSim
+
* <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>
#Run System
+
 
##Execute "/SoccSim/bin/soccsim" - This will start the simulation engine, with a 3D wireframe view of the field and robots.
+
==Limitations==
##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.
+
* No noise.
 +
* 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.

Revision as of 20:41, 2 August 2010

The simulator, soccsim, 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

./soccsim [-c <config file>] [--ui] [--sv]

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

  • --ui displays a GUI that is really only useful for debugging the geometry given to the physics engine.
  • --sv causes the simulator to send data to the ssl-vision multicast address. Do not use this on a competition network!

Limitations

  • No noise.
  • 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.