Skip to content

Stage 1C incorporation into educator's guide and several overview pages - #251

Open
Venture-Capitalist wants to merge 23 commits into
frcsoftware:mainfrom
Venture-Capitalist:stage1c
Open

Stage 1C incorporation into educator's guide and several overview pages#251
Venture-Capitalist wants to merge 23 commits into
frcsoftware:mainfrom
Venture-Capitalist:stage1c

Conversation

@Venture-Capitalist

@Venture-Capitalist Venture-Capitalist commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Description

What changed?
Why? (the code + comments should speak for itself on the "how")
Added 1C to the educator's guide via a blank WIP page. Also added 1C mentions to overview pages in both the learner's course and educator's guide.

Closes #159

Any issues this pull request closes or pull requests this supersedes should be linked with Closes #issuenumber.

Meta

Merge checklist:

Venture-Capitalist and others added 22 commits July 31, 2026 12:13
….mdx

Co-authored-by: Zach Harel <zach.harel42@gmail.com>
….mdx

Co-authored-by: Zach Harel <zach.harel42@gmail.com>
…nresolved and need to be sorted out before merging
….mdx

Co-authored-by: Adriana  <16786568+Adrianamm@users.noreply.github.com>
….mdx


sounds good boss

Co-authored-by: Adriana  <16786568+Adrianamm@users.noreply.github.com>
@github-actions github-actions Bot added Curriculum material Curriculum materials, lessons for students, etc stage1 labels Sep 6, 2026
@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

🌐 Preview URL: https://pr-251-frcsoftware.frcsoftware.workers.dev

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question - I originally envisioned Stage 1C as being more about having drive forward + turn commands using PID, but if we want to build 1C around aiming at the hub or a target that also works, probably seems more immediately applicable to FRC anyways. Are you envisioning this as turning to a single fixed angle or more of the sort of dynamic aiming towards the hub from anywhere on the field like you would with actual vision? My only concern with that approach is that it would require actual Pose info, and while we technically have that through sim, user code isn't running any odometry.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way I understood the plan earlier, the idea was to have the user code a command which enables the tank drive to rotate towards a field-relative heading angle passed in by the user (potentially through telemetry if we wanna do that). The project doesn't necessarily have to be a full hub autoaim system; that's a lot more complex imo. On the translational side of things, I'm perfectly good with having the tank drive have forwards/backwards PID commands too if that's what we want.

I think in all cases we'd need to also have some odometry info because you can't really run any feedback loop without encoder data. You can probably get away with just the tank chassis odometry, but this wouldn't necessarily be an atrocious time to introduce users to reading IMU data either.

@DylanB5402

DylanB5402 commented Sep 6, 2026

Copy link
Copy Markdown
Member

Just checking, this is for #252 right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Curriculum material Curriculum materials, lessons for students, etc stage1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants