Unit 07

Reading the Library You Depend On

By the end of this unit you can trace one iteration of a scheduler you did not write and use it to explain something the robot actually did, say which classes on your robot arrived by Gradle and which your team owns, read a method's source against its own documentation and name the consequence when they disagree, and put a hook that must run where the base class guarantees it will.

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

  1. You have been taking its word for it
  2. Whose code is this, actually
  3. One iteration, in the order it really happens
  4. periodic() is not interrupted, because it was never scheduled
  5. A docstring is a claim; the source is the evidence
  6. Which method does what the sentence says
  7. The biggest version number is not the newest release
  8. Where the base class guarantees your hook will run
  9. Why it cannot live at the end of the last command

12 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.

2 Get in

Open the class link your teacher posted — that's the usual way, and it enrolls you on the spot. Or paste an access key if you were handed one.

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