-
Notifications
You must be signed in to change notification settings - Fork 68
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
Kabirk/add simple subscriber #580
Kabirk/add simple subscriber #580
Conversation
e178f24
to
cad1aee
Compare
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.
Thank you for the PR!
Also, to ensure the linting check passes, can you run |
fc563c8
to
493af1e
Compare
Hey @khughes-bdai I made all the changes you requested! Please review them and let me know if some other changes are needed |
560eac6
to
0d33cbe
Compare
Hello I made the changes you requested @khughes-bdai . |
pre-commit is failing but I am not sure why! |
super small but it looks like you are missing a newline at the end of the docs file -- if you run the pre-commit command again locally it should fix it! |
Fixed NVM |
…to bdai_ros_wrappers Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
## Change Overview Made a descriptor class for trigger services to reduce boilerplate + copy/paste code in trigger service handlers ## Testing Done Tested all trigger services on robot. Found a bug with estop handling within `spot_wrapper` (will make a new ticket to track this but out of scope for this PR) Please create a checklist of tests you plan to do and check off the ones that have been completed successfully. Ensure that ROS 2 tests use `domain_coordinator` to prevent port conflicts. Further guidance for testing can be found on the [ros utilities wiki](https://github.com/bdaiinstitute/ros_utilities/wiki/Testing-guidelines). Signed-off-by: kabirkedia <[email protected]>
…tute#582) Bumps [spot_wrapper](https://github.com/bdaiinstitute/spot_wrapper) from `3555ca1` to `d96cfb8`. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bdaiinstitute/spot_wrapper/commit/d96cfb8e66cad5791fed8f40dc03bdb83ac3720f"><code>d96cfb8</code></a> Fix false trajectory success when blocked by obstacle (<a href="https://redirect.github.com/bdaiinstitute/spot_wrapper/issues/156">#156</a>)</li> <li>See full diff in <a href="https://github.com/bdaiinstitute/spot_wrapper/compare/3555ca137677ed265a91c85e22d4505ebea3bc14...d96cfb8e66cad5791fed8f40dc03bdb83ac3720f">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: kabirkedia <[email protected]>
) Co-authored-by: Tiffany Cappellari <[email protected]> Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
Signed-off-by: kabirkedia <[email protected]>
f2b568c
to
66f80d9
Compare
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!
Change Overview
This PR addresses issue #569 and provides an example for controlling Spot via a ROS 2 subscriber.
I initially faced challenges using a subscriber to control Spot while integrating a learning-based MPPI model. To make this process easier for others, I’ve added an example demonstrating how to use a topic to send movement commands to Spot.
How It Works
Additionally, I have fixed broken documentation links that referenced bdai_ros2_wrappers instead of synchros2.
Testing Done
✅ Tested with the real Spot multiple times.
(Thank you @khughes-bdai for the prompt help)
Please create a checklist of tests you plan to do and check off the ones that have been completed successfully. Ensure that ROS 2 tests use
domain_coordinator
to prevent port conflicts. Further guidance for testing can be found on the ros utilities wiki.This has been tested with the real spot multiple times.