Skip to content

Parse rpyOffset as radians#497

Merged
chapulina merged 1 commit intosdf6from
iche033/urdr_parser_rpy
Mar 16, 2021
Merged

Parse rpyOffset as radians#497
chapulina merged 1 commit intosdf6from
iche033/urdr_parser_rpy

Conversation

@iche033
Copy link
Copy Markdown
Contributor

@iche033 iche033 commented Feb 18, 2021

During fixed joint reduction, the xyzOffset and rpyOffset plugin parameters are modified. It was found that the rpyOffset is actually parsed as degrees instead of radians.

This created a problem when you have chained fixed joints - in the first joint reduction, the code writes out the new rpyOffset vector in radians, but in the second fixed joint reduction, the code parses it back as degrees.

Looking at plugins in gazebo_ros_pkgs, this parameter should be in radians

Signed-off-by: Ian Chen ichen@osrfoundation.org

Signed-off-by: Ian Chen <ichen@osrfoundation.org>
Copy link
Copy Markdown
Collaborator

@azeey azeey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a remnant of when Gazebo XML (before sdformat) used degrees for rpy. Traced back to when parser_urdf.cc was added to the Gazebo code base (gazebosim/gazebo-classic@db34cd7)

@iche033
Copy link
Copy Markdown
Contributor Author

iche033 commented Feb 25, 2021

@osrf-jenkins run tests please

1 similar comment
@iche033
Copy link
Copy Markdown
Contributor Author

iche033 commented Feb 26, 2021

@osrf-jenkins run tests please

@chapulina chapulina merged commit 3848066 into sdf6 Mar 16, 2021
@chapulina chapulina deleted the iche033/urdr_parser_rpy branch March 16, 2021 22:27
@osrf-triage
Copy link
Copy Markdown

This pull request has been mentioned on Gazebo Community. There might be relevant details there:

https://community.gazebosim.org/t/new-ignition-releases-2022-03-25-fortress-edifice-citadel/1343/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants