Unit 07
Reading the Library You Depend On
By the end of this unit you can trace a scheduler you did not write to explain what the robot did, read a library's source against its docs, and put a hook where it is sure to run.
Robotics Programming · members' unit
Reading the Library You Depend On is behind a locked door
Units in Robotics Programming are for people taking the course. Getting in takes a link or a key — signing in on its own doesn't do it.
What's in this unit · 11 min read
- You have been taking its word for it
- Whose code is this, actually
- One iteration, in the order it really happens
- periodic() is not interrupted, because it was never scheduled
- A docstring is a claim; the source is the evidence
- Which method does what the sentence says
- The biggest version number is not the newest release
- Where the base class guarantees your hook will run
- Why it cannot live at the end of the last command
14 quick checkscode exercises
1 Sign in
With your school Google account. This is how your work reaches the gradebook — it doesn't open the unit by itself.
A key unlocks this browser and keeps your progress here; signing in keeps it with you across devices. Either way the key itself is only ever checked as a hash. Manage all of this on your account, read what signing in stores, or go back to Robotics Programming.
Sources
- GA-Moonshots — Artemis, the team base code
- Seattle Solvers — SolversLib — read at tag 0.3.6, the version Artemis depends on
- Gilmour Academy Competitive Robotics — Software Team course notes — the chapters these standards were harvested from