Sbot Common Interface
Revision as of 12:52, 28 March 2006 by Rogrady
What is the common interface, and why should we use it?
- Write Controller Once, instead of modifying for each platform.
- Save time - no code rewrites. Maintain just one version of your code
- When developing in simulation, you can do frequent reality checks on real robots.
- Everyone shares a common build environment. We can stop reinventing the wheel.
- All controllers stored in common repository. Can easily browse other people's code.
- Share and jointly improve tools - eg. scripts for copying files to sbots
- All extra libraries included in common interface - toolchain, sboteyelib etc.
Common Interface QuickStart
- Install subversion.
- apt-get install subversion
- Checkout common interface from repository
- svn checkout svn+ssh://<your iridia username>@iridia.ulb.ac.be/usr/local/share/svn_repositories/sbotci
- Compile one of the example controllers for the real robot
- cd sbotci/real_sbot
- ./build_scripts/build_support_libs.sh (build toolchain, sboteyelib etc)
- make controller=describe_circle
- Copy binary to sbot and run it
- tools/sbot_file_copy/describe_circle <sbotnumber>
- ssh root@sbot<sbotnumber>
- cd /tmp
- Compile twodee and run an example controller
- cd twodee
- ./twodee -e10003 --experiment-parameters controller=describe_circle