Gitiles
Code Review Sign In
realtimeroboticsgroup.org / RealtimeRoboticsGroup / test / 648b3613e7ad9e6d77a55ef5cba27fa7ef87b92b
commit648b3613e7ad9e6d77a55ef5cba27fa7ef87b92b[log] [tgz]
authorAustin Schuh <austin.linux@gmail.com>Mon Nov 20 01:02:24 2017 -0800
committerAustin Schuh <austin.linux@gmail.com>Mon Nov 20 01:03:46 2017 -0800
treeb1c6f2b3d5769208fb229b171890c2e055b086b9
parentda3b88249f25ed0dd3b4dbffc704dc49e5996704 [diff]
Remove rounding on printing time.

1.999999999 was rendering as 1.1000000 seconds instead of 2.000000 or
1.999999 seconds.  Wrapping the big digit is not worth it at this
level, so let's drop that feature.

Change-Id: I46a9b75049332d530e7c3c5ccc4cca30430d9572
2 files changed
tree: b1c6f2b3d5769208fb229b171890c2e055b086b9
  1. aos/
  2. build_tests/
  3. compilers/
  4. debian/
  5. doc/
  6. frc971/
  7. motors/
  8. third_party/
  9. tools/
  10. vm/
  11. y2012/
  12. y2014/
  13. y2014_bot3/
  14. y2015/
  15. y2015_bot3/
  16. y2016/
  17. y2016_bot3/
  18. y2016_bot4/
  19. y2017/
  20. y2017_bot3/
  21. .clang-format
  22. .gitignore
  23. LICENSE.txt
  24. README.md
  25. 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:

  1. Set up the required APT repositories: Download frc971.list and llvm.org.list and put them in /etc/apt/sources.list.d/.
  2. 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: Follow the direction in doc/frc971.conf.

Some useful Bazel commands:

  • Build and test everything (on the host system):
bazel test //...
bazel build --cpu=roborio //...
  • 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