-[Controlling the Robot (Pulse Width Modulation)](/training/controlling-the-robot)
## Intermediate
## Advanced
# All Trainings
## Basic
-[Preparing your computer for R@M programming](/training/preparing-your-computer-for-ram-programming)
-[Basics of the terminal](/training/basics-of-the-terminal)
-[Controlling the Robot (Pulse Width Modulation)](/training/controlling-the-robot)
## Intermediate
*[Designing For Manufacturing](/training/design-for-manufacturing-training)
## Advanced
### :software: \[Reading and visualizing position with GPS\]
# Cheatsheets, FAQs, and References
-[FAQ: Python and ROS](/training/faq-python-and-ros)
-[FAQ: Terminal](/training/faq-terminal)
# Legend
## Basic: Fully Developed Tutorials
- Basic projects should provide a step-by-step guide to achieve the objective(s).
- Basic projects must break down the steps to a low level understanding, such as design considerations - why .5mm tolerance? Or general basics - ESCs amplify power and this is necessary as our motors consume a large amount of amperage.
- Basic projects should be understood by anyone who has completed Level 1 Onboarding.
- Basic projects may overlap with level 1 onboarding.
- Basic projects may be walked through entirely by onboarding lead if the team is falling behind.
## Intermediate: A Deeper Dive with Guard Rails
- Intermediate projects must give design constraints, basic templates, etc. that help the teams get started on the project.
- Intermediate tutorials must leave gaps where teams will use their own knowledge to “fill it in”.
- At the completion of all intermediate projects, the robot must be minimally functional.
- This allows teams to continue making progress even if certain members get stuck.
- Teams should not be walked entirely through these projects.
## Advanced: Most exciting, little oversight
- Any advanced projects are those above what is necessary to complete the robot (minimally).
- Advanced projects must challenge the team to expand their robotics knowledge on their own.
- Advanced projects must still provide detailed product requirements.
- These projects should be optional but heavily encouraged, as they will prepare the member for what it feels like to really work on the robot (Pain…).
- Struggling is a method of learning! The solution to advanced projects should not be given away.
# TODO
## Maybe tag or organize lessons by soft/mech/elec if they are specific to one category
## Maybe change language in the legend
Right now it's just copied from the [Fall 23 Official Onboarding Guide](https://docs.google.com/document/d/1_yCk51co0fgiEHoplCTkrLV1Q3abKg6CtkG5cWzlIIk/edit), which was targeted at leads & returning members and not new members.
