Add Optionally Shown Window With Numerical Motion Data #2
Conversation
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
SanjayRam-code
pushed a commit
to overchargers/MeepMeep
that referenced
this pull request
Oct 10, 2025
…pdate Update `build.gradle.kts` to Reference New Repository
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds tracking for robot velocity, acceleration, and jerk (along X and Y, not heading). Pressing the P key during runtime shows a panel containing this information in a new window, and data is separated for each robot. To enable clear differentiation of which data belongs to which robot in multi-robot scenarios, robots can now optionally be named via the .setName() method of the DefaultBotBuilder, and these names show up as labels in the data panel.
Our team believes this could be helpful for folks to compare the projected velocity/acceleration/jerk of their trajectory to the actual velocity/acceleration/jerk readings from their robot while debugging.