Gitiles
Code Review Sign In
realtimeroboticsgroup.org / RealtimeRoboticsGroup / test / 6c6a0a9b0dd092bb3fe06742b6b382997bdeba27
commit6c6a0a9b0dd092bb3fe06742b6b382997bdeba27[log] [tgz]
authorComran Morshed <comranmorsh@gmail.com>Sun Jan 17 12:45:16 2016 +0000
committerComran Morshed <comranmorsh@gmail.com>Fri Jan 29 20:12:42 2016 +0000
tree3ac8f2b8c8cdb809e3c2aa8faf6acc6bddde7012
parent9a9948cf030986c55b5a48254039f2c0c8961421 [diff]
Convert y2014 to y2016, and get the drivetrain running.

I made a y2016 folder based on what was in y2014. Right now, it only has
a drivetrain control loop, and all the constants are not up to date with
the current CAD design. Changes from y2014 can be viewed by comparing to
the BASE commit, since I put this commit on top of a dummy y2014 folder
renamed y2016. Hope this helps.

Change-Id: I3f1d1d1a14a99ac441c51b2a67cbade7cbd708ab
26 files changed
tree: 3ac8f2b8c8cdb809e3c2aa8faf6acc6bddde7012
  1. aos/
  2. build_tests/
  3. debian/
  4. doc/
  5. frc971/
  6. third_party/
  7. tools/
  8. y2012/
  9. y2014/
  10. y2014_bot3/
  11. y2015/
  12. y2015_bot3/
  13. y2016/
  14. .clang-format
  15. .gitignore
  16. LICENSE.txt
  17. NO_BUILD_AMD64
  18. NO_BUILD_ROBORIO
  19. README.md
  20. WORKSPACE
README.md

Introduction

This is FRC Team 971's main code repository. There are README* files throughout the source tree documenting specifics for their respective folders.

Access to the code

The main central location for our code is our Gerrit server at https://robotics.mvla.net/gerrit. To get a copy of the code on your computer to work with, follow these steps:

  1. Contact Michael Schuh to get an SVN account.
  2. Go to Gerrit and create an account.
  3. Contact Brian Silverman with your SVN username to get access to the code in Gerrit.
  4. Go to the 971-Robot-Code project in Gerrit and run the command. Running the clone with commit-msg hook command will save you trouble later.

To learn more about git, see git(1) (man git or git(1) (especially the NOTES section).

Code reviews

We want all code to at least have a second person look over it before it gets merged into the master branch. Gerrit has extensive documentation on starting reviews. TL;DR: git push origin HEAD:refs/for/master and then click on the link to add reviewers. If you just upload a change without adding any reviewers, it might sit around for a long time before anybody else notices it. git-review can make the upload process simpler.

Building the code

The currently supported operating system for building the code is amd64 Debian Jessie. It is likely to work on any x86_64 GNU/Linux system, but that's not at all well-tested.

We use Bazel to build the code. Bazel has extensive docs and does a nice job with fast, correct increment rebuilds.

Steps to set up a computer to build the code: 0. Set up the required APT repositories: Download frc971.list and llvm.org.list and put them in /etc/apt/sources.list.d/.

  1. Install the required packages:
apt-get install python libpython-dev bazel ruby clang-format-3.5 clang-3.6 gfortran libblas-dev liblapack-dev python-scipy python-matplotlib
  1. Allow Bazel's sandboxing to work

Some useful Bazel commands:

  • Build and test everything (on the host system):
bazel test //... -- $(cat NO_BUILD_AMD64)
bazel build --cpu=roborio //... -- $(cat NO_BUILD_ROBORIO)

The NO_BUILD_{AMD64,ROBORIO} files contain lists of the targets which are intentionally not built for the various CPUs.
  • Build the code for a specific robot:
bazel build --cpu=roborio --compilation_mode=opt //y2015/...
  • Download code to a robot:
bazel run --cpu=roborio --compilation_mode=opt //y2015:download roboRIO-971.local