-
Notifications
You must be signed in to change notification settings - Fork 110
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
Final_speed and Target_spins_per_s #3328
Conversation
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.
Nice work! Looks like simulated_hrvo_test.py
is failing -- if you can't figure out how to fix it, it's probably ok to disable that test for now since we don't use HRVO any more. We might be able to repurpose the test cases for a general motion planning test later
Co-authored-by: William Ha <[email protected]>
Co-authored-by: William Ha <[email protected]>
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.
💯
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.
LGTM 🔥
* Final_speed and Target_spins_per_s * [pre-commit.ci lite] apply automatic fixes * Field chancge * Update src/proto/tactic.proto Co-authored-by: William Ha <[email protected]> * Update tactic.proto Co-authored-by: William Ha <[email protected]> * simulated hrvo fix --------- Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: William Ha <[email protected]>
The full deletion of anything having to do with target_spin_rev_per_s and final_speed as being control params especially being updated
Testing involved building all files and watching thunderscope gameplay to ensure nothing seemed off
Resolved Issues
resolves #3145
Length Justification and Key Files to Review
Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
.h
file) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom
. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.TODO
(or similar) statements should either be completed or associated with a github issueJust if you could recheck it builds would be lovely thanks!