-
Notifications
You must be signed in to change notification settings - Fork 45
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
add covariance fields to imu message #333
Conversation
Codecov Report
@@ Coverage Diff @@
## main #333 +/- ##
=======================================
Coverage 95.71% 95.71%
=======================================
Files 9 9
Lines 1073 1073
=======================================
Hits 1027 1027
Misses 46 46 |
I think this breaks ABI so will need to go into |
@mjcarroll I just pushed the changes to re-order and document the new fields to stick to ros conventions |
@iche033 so are you proposing to change the branch into which we merge this PR ? |
Yes, please. Our policy is to not break ABI in an existing release. We are working on a mechanism for message changes to not break ABI, but it is not in version 9. Please target |
Other than branch target, changes LGTM. |
@mjcarroll Thanks for the answer. I just resolved the merge conflicts and updated the PR with it. |
@mjcarroll How do you plan on releasing this? Since it's related to PRs on other repos ? |
We will need to get each of the other ones landed first and released, and then this one can get in. |
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.
conflicts
@ahcorde fixed the conflicts |
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.
Signed-off-by: Alaa El Jawad <[email protected]>
Signed-off-by: Alaa El Jawad <[email protected]>
@ahcorde @mjcarroll The confligs mainly came from the various merge from main into this branch. |
@ahcorde @mjcarroll Hey guys, any update on this PR ? shall I rebase again ? |
Thank you for the PR merge! :) |
* add covariance fields to imu message Signed-off-by: Alaa El Jawad <[email protected]> * re-order msg fields and doc to stick to ros convention Signed-off-by: Alaa El Jawad <[email protected]> --------- Signed-off-by: Alaa El Jawad <[email protected]> Co-authored-by: Michael Carroll <[email protected]>
* add covariance fields to imu message Signed-off-by: Alaa El Jawad <[email protected]> * re-order msg fields and doc to stick to ros convention Signed-off-by: Alaa El Jawad <[email protected]> --------- Signed-off-by: Alaa El Jawad <[email protected]> Co-authored-by: Michael Carroll <[email protected]>
* add covariance fields to imu message Signed-off-by: Alaa El Jawad <[email protected]> * re-order msg fields and doc to stick to ros convention Signed-off-by: Alaa El Jawad <[email protected]> --------- Signed-off-by: Alaa El Jawad <[email protected]> Co-authored-by: Michael Carroll <[email protected]>
Are there plans to implement or release this feature for older versions, including Fortress? |
Unfortunately, this is not a backward compatible change. |
🎉 New feature
Add the covariance fields to the imu message
Summary
The imu message is missing the covariance fields for linear_acceleration, angular_velocity and orientation_covariance.
Those can be very useful when bridging between gz and ros.
Note: a PR is coming to gz-sensors to fill those field.
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.