RoboCupSoftware2007
From GT RoboJackets
Contents |
Team
Team Lead: Roman Shtylman
- aim: shtylman
- @: shtylman 'at' gmail.com
Master of Shadows: Ben J.
Overview
Note: referee box commands http://www.cs.cmu.edu/~brettb/robocup/referee.html#Rules
Subversion
We are using subversion to manage our source code. Please play in the sandbox on the subversion page and get a feel for version control before working on the main code/project.
repository path: https://svn.shtylman.com/robocup
online code browsing: https://websvn.shtylman.com/index/robocup
- The simulator code is in /trunk relative to the repository path: https://svn.shtylman.com/robocup/trunk
- The coding conventions are in /resource/conventions
Subversion etiquette
Following these rules will lead to a good subversion experience. Not following them...I will leave that up to you to imagine what I will do. (Remember...we have logs)
- DO NOT commit code that does not compile
- DO NOT commit binaries
- DO NOT commit IDE/Environment specific project files
- ALWAYS state a comment for your commit
- ALWAYS perform svn update before starting to make changes
- ALWAYS perform svn update right before you commit
- DO NOT stop working without performing svn commit on the code
Collaboration
Any online group meetings that we will hold will occur in IRC (Internet Relay Chat) on the irc.freenode.net server in channel #robojackets.
Environment
All the code most compile on the gcc 4.0 in linux at the end. Thus it must be C++ standards compliant. We suggest using either gcc or another reputable compiler. Below are some options.
Code::Blocks IDE
A free c++ IDE and compiler based on gcc 3.4
http://www.codeblocks.org/
Dev-C++
A free c++ IDE and compiler based on gcc 3.4
http://www.bloodshed.net/devcpp.html
Visual Studio
Compiler, IDE, and overall good project maintainer. Good if you can get it.
Resources
Path Planning: use later for the thinking code http://planning.cs.uiuc.edu
