Difference between revisions of "RoboCup Simulator"
Jump to navigation
Jump to search
Cwehmeyer3 (talk | contribs) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
./simulator [-c <config file>] [--sv] | ./simulator [-c <config file>] [--sv] | ||
</pre> | </pre> | ||
| + | |||
| + | 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 <tt>simulator.cfg</tt> in the current directory. | If no configuration file is given, it will use <tt>simulator.cfg</tt> in the current directory. | ||
| Line 14: | Line 16: | ||
* No carpet effects such as loss of traction and variable height. | * No carpet effects such as loss of traction and variable height. | ||
* Only partial simulation of robot status in RadioRx packets. | * 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.
