Under Construction

ALoTO extracts from the FTC Springboard

All the extra ALoTO-specific stuff that had originally polluted my first draft (though I should definitely have a section on commonly used libraries)

All links (except Navigation) open in a new tab.

Last updated 6-29-23

[INCOMPLETE]     |     [complete]

• ALoTO-specific [CREATE] Part 1 - Connecting Studio to GitHub (which I will have to make once we have an actually good system in place... if it's even possible - basically, people should ideally connect their own accounts rather than signing into ALoTO's, but Studio doesn't like this all that much, so I might actually just pass around a token (I saved one) or something)
  • I should probably also find or create a generic tutorial. I should make sure both sign-in and tokens get covered in case the signin breaks again or in a new way (it's still a little broken, actually).



---



• [LOCATE] Any libraries we may want to use, either from the community or custom
  • Here's the Roadrunner documentation. Keep in mind that this is a pathfinding library, but it also provides facilities to handle reading and calibrating dead wheels and standalone encoders which the FTC SDK does not.
  • Additional notes I've gathered from the documentation:
  • Nothing yet!
  • Additional resources to this end include:
    • learnroadrunner.com
    • gm0 topic on dead wheels