-
Notifications
You must be signed in to change notification settings - Fork 22
Added Stage 1C overview and Stage 1C section on sidebar #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Venture-Capitalist
wants to merge
6
commits into
frcsoftware:main
Choose a base branch
from
Venture-Capitalist:stage1c
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e181658
Updated sidebarConfig with stage 1C and added overview for 1C
Venture-Capitalist 7bd54ef
updated 1c overview to match linter recommendations
Venture-Capitalist 61ec184
Merge branch 'main' into stage1c
Adrianamm 056dc95
Update src/content/docs/learning-course/stage1/stage1c/stage-overview…
Venture-Capitalist 13973ac
Update src/content/docs/learning-course/stage1/stage1c/stage-overview…
Venture-Capitalist d5e682e
Merge branch 'main' into stage1c
Adrianamm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
36 changes: 36 additions & 0 deletions
36
src/content/docs/learning-course/stage1/stage1c/stage-overview.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| --- | ||
| title: Stage 1C Overview | ||
| description: An overview of Stage 1A | ||
| prev: ../stage-overview | ||
| next: false | ||
| --- | ||
|
|
||
| import YouTube from '../../../../../components/YouTube.astro'; | ||
|
|
||
| If you've watched matches from any recent FRC game, you'll notice that robots typically have to line up quite precisely with a field element to score. | ||
| Take this example from Purdue University's Robot in 3 Days (Ri3D) team showcasing their autoalign program: | ||
|
|
||
| <YouTube url="https://www.youtube.com/watch?v=MV6SQ46Dijs" /> | ||
|
|
||
| In 2026, robots had to line up with the hub to successfully shoot fuel. | ||
| In 2025, robots had to line up with hangers on the reef to place coral. | ||
| To execute these tasks, teams run automatic positioning programs rather than burdening the driver with such precise movements. | ||
| In Stage 1C, you will learn fundamental concepts pertaining to "control theory:" a field of research dedicated to guiding real-world systems (such as robots) to do the things we want. | ||
| Control theory guides the motion of each and every mechanism you will program in FRC. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm honestly kinda opposed to talking about the term "control theory" explicitly at all - or maybe bring it up later. Seems a little more academic than what we want to focus on here. Not an awful strongly held opinion though |
||
|
|
||
| ## Key Concepts | ||
|
|
||
| In FRC, different mechanisms can be thought of as "systems." | ||
| Mechanisms have "states" such as position, angle, velocity, and acceleration. | ||
| A PID (Proportional, Integral, Derivative) controller takes a desired state of a system, called a "setpoint," and guides a system's actual state towards this setpoint. | ||
| The output of your mechanism's control algorithm is called "control effort," and, in FRC, control effort will almost always be measured in Volts. | ||
| You can track the states, setpoints, and control efforts of your robots through logging with Telemetry, a system for sending data between the robot and the driver station. | ||
|
|
||
| ## Stage 1C Goals | ||
|
|
||
| By the end of Stage 1C, you'll program a feature which enables your kitbot's drivetrain to automatically and smoothly turn in place to any given angle such that your kitbot can aim towards the hub on its own. | ||
| You will also be able to read data from your kitbot via logging with Telemetry. | ||
|
|
||
| This stage will cover the following topics: | ||
|
|
||
| - WIP | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like what you're getting at here, but I wonder if this is the right framing. We're more making a robot turn in place here, not aligning to a target - even if those are pretty similar operations in practice. Also in the sense that this is showing a swerve bot while they're actually programming a tank bot.
Drive + turn in place autos aren't really a think you see in the program these days, in the age of swerve, but that's kinda what we're building towards in this stage.
@Adrianamm @roboteer5291 thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think that it would then be better to instead show video from a past game of a tank robot turning in place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you can find a good video, maybe? But any tank video like that would be a bit dated anyways. I wouldn't stress about this too much, we can always look back over this once 1c is more built out