Fix/anymal msg contact detection#16
Closed
ylenianistico wants to merge 6 commits into
Closed
Conversation
Updated README to reflect changes regarding ROS2 and unitree sdk.
Revise ROS1 deprecation notice and add unitree sdk info
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
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.
Summary
This PR updates the contact detection pipeline to support the ANYmal proprioception data from the GrandTour dataset.
Changes include:
anymal_msgsmessage definitions to match the rosbag message typeanymal_msgs/AnymalState.ContactDetectionPluginto subscribe toanymal_msgs/AnymalState./anymal/state_estimator/anymal_state.INFOlogs..gitignoreentries for local catkin artifacts and logs.Motivation
The GrandTour proprioception rosbag publishes ANYmal state data on: