DGC05 Main Page
From DGC Wiki
Main | GOTChA | Timeline [W15] | Test Plan [W15] | 300 mi, 35 mph | 0B, 0N |
Org Chart | Race Teams | System Spec | Test Matrix | NQE GCE |
Project News [Index, Alice Schedule]
[edit] Race Teams / Team Roster[edit] Additional Teams[edit] Additional Project Links
|
[edit] DGC non-Wiki Links
[edit] Test DataThe test_logs and test_logs_2003-2004 directories contain oodles of data. [edit] Contact Information[edit] Project Facebook
[edit] List of available projects[edit] Volunteer Info |
How to Document
Go to Using Wiki for the new and improved information on how to use mediawiki (See also: Tutorial, Syntax list). Be sure to log in with a username when editing things. Or go play in the Sandbox. No throwing sand ...
If you have any questions which are not answered by the Using Wiki page then feel free to email one of the Wiki sysops or (preferably) post your question here on the FAQ or WikiFAQ so that others may partake of the brilliant wisdom with which we answer your questions.
TIP OF THE DAY: When uploading non-image files, make sure to use Media:, not Image: (that way the link will actually look like a link and not a broken image box).
Are you having trouble with coloured text? - resolve your problems! -> Wiki Colour Chart & Howto
Mailing Lists
We use mailman to maintain a number of mailing lists for use by the project. If you would like to have a new list created for use by your team, see the instructions on the system adminstration page.
- http://grandchallenge.caltech.edu/mailman/listinfo: All mailing lists.
- team-students: project announcements, events, meeting agendas. Everyone actively working on the project should be on this list.
- team-volunteers: major project announcements and events. Intended for volunteers who want a lower volume of e-mail; moderated list.
- sysadmin: administration of grandchallenge and the race computers. Everyone with root permission on grandchallenge should be part of this list.
Checklists
We have checklists for most of the major items that we need to keep track of for operating the vehicle. We probably should put this in the Bob User's Manual (BUM), but for now I am linking them here.
2005 NQE and Race Checklists
Click the link above to go to the checklists that will be used for 2005. The checklists in the section below this are old checklists (eg, for Bob) and checklists for more detailed situations.
General Checklists
- Master Checklist: contains links to all of the checklists that we have created. Go here if you don't see the checklist you are looking for.
- RV Checklist: how to prep the RV
- Desert Safety Checklist: Things to bring whenver you go out to the desert
- Checklist to do upon arrival back at shop
- 2005 Race Checklists
Bob Checklists
- Bob Vehicle Checklist: use this checklist to go through the actions that are required to get Bob running.
- Bob Embedded Systems Checklist: use this to get the sensing, actuation, and control hardware on Bob up and running.
- Bob Planning Checklist: navigation and motion planning software
- Transporting Bob Checklist: everything you need to know to get Bob from A to B the easy way (on a trailer)
Alice Checklists
- Alice Vehicle/Transportation Checklist: use this checklist to go through the actions that are required to get Alice running.
- Alice Embedded Systems Checklist: use this to get the sensing, actuation, and control hardware on Alice up and running.
- Alice Planning Checklist: navigation and motion planning software
- Instructions for starting up alice and running a test
- Tire Change Instructions
- Pre-Race Checklist
The Command
The following command works to check out the repository as the current user, assuming that it has been installed (from dgc/local/scripts) on the current machine. Note that a checkout is about 10X faster on the NFS server (skynet2 or grandchallenge) versus NFS clients.
user@machine$ sco trunk dgc user@machine$ sco Usage: sco path name This will run the following command: svn co svn+ssh://gc.caltech.edu/dgc/subversion/dgc/path name
The Other Command
Put this in your ~/.bashrc. It asssumes that you name your repository copy "dgc", as above.
[ -f $HOME/dgc/local/files/dgc.bashrc ] && source $HOME/dgc/local/files/dgc.bashrc
Please note that once you have done this, you will have to source the bashrc in *your current terminal* AND *all* other terminals which are *currently open* in order for the changes to take effect, if you create new terminals after having sourced in one of the ones that was open prior to when sourced, the new terminals will already be sourced and everything will be groovy :), the command for sourcing is:
. ~/.bashrc
If you have done this and your .bashrc file is not being sourced, then you may need to put the following in your ~/.profile (which you may need to create):
[ -f $HOME/.bashrc ] && source $HOME/.bashrc