Skip to content

Add downloaded version of StateMachine link #144

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.

Sign up for GitHub

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
TaylerUva wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add downloaded version of StateMachine link #144

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1477f79
Update README to enhance state machine documentation and remove simul…
TaylerUva Dec 6, 2025
c91e636
Add VSCode extension recommendations and update README for TLDraw ext…
TaylerUva Dec 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .vscode/extensions.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"recommendations": [
"tldraw-org.tldraw-vscode"
]
}
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,12 @@ Interested in learning more about CRESCENDO? Visit [FIRST's website](https://www
## Code Details
This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!

Copilot AI Dec 6, 2025

Copy link

Choose a reason for hiding this comment

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

Spelling error: "eachother" should be "each other" (two words).

Suggested change
This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!
This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with each other. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!

Copilot uses AI. Check for mistakes.

Copilot AI Dec 6, 2025

Copy link

Choose a reason for hiding this comment

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

Spelling error: "staring" should be "starting".

Suggested change
This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!
This offseason, we chose to control our robot using a state machine! Prior to starting our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!

Copilot uses AI. Check for mistakes.

Copilot AI Dec 6, 2025

Copy link

Choose a reason for hiding this comment

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

Spelling error: "dicussed" should be "discussed".

Suggested change
This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!
This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and discussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!

Copilot uses AI. Check for mistakes.

Check out our diagram below or visit the interactive link [here.](https://www.tldraw.com/ro/DX06u039erL_iV6q0ARSn?d=v-1103.-1504.5212.2506.page)
Check out our diagram below, [view in VSCode](StateMachineMap.tldr), or [visit the interactive web link](https://www.tldraw.com/ro/DX06u039erL_iV6q0ARSn?d=v-1103.-1504.5212.2506.page)

![State Machine Diagram](src/main/assets/StateMachine.png)

*Viewing TLDraw in VSCode requires the [TLDraw VSCode Extension](https://marketplace.visualstudio.com/items?itemName=tldraw-org.tldraw-vscode)*

## Controls
![Controller Map](src/main/assets/Controller_Map.png)

## Robot Simulation
Coming Soon!
1 change: 1 addition & 0 deletions StateMachineMap.tldr
View file
Open in desktop

Large diffs are not rendered by default.