Skip to content

Clarify the docs about which Euler angle convention is used. - #1619

Open
de-vri-es wants to merge 1 commit into
dimforge:mainfrom
de-vri-es:clarify-euler-angle-convention
Open

Clarify the docs about which Euler angle convention is used.#1619
de-vri-es wants to merge 1 commit into
dimforge:mainfrom
de-vri-es:clarify-euler-angle-convention

Conversation

@de-vri-es

Copy link
Copy Markdown

The current documentation calls the angles "roll", "pitch" and "yaw", but it doesn't explain what those are. Roll, pitch and yaw are conventions from aerospace, but there is no authoritative definition on which axes they correspond to, in which order they should be applied, and whether they are intrinsic or extrinsic rotations.

As a math library that uses X, Y and Z for the principal axes, it is more helpful if the documentation sticks to that convention.

This PR adjust the documentation to explain the angles in terms of X, Y and Z, while still mentioning that the angles are often called roll, pitch and yaw.

The PR also adds code snippets that shows how to go from Euler angles to a rotation without using from_euler_angles(). So even if the text explanation isn't clear enough for everyone, the code snippet should make sure there is no ambiguity.

The current documentation calls the angles "roll", "pitch" and "yaw",
but it doesn't explain what those are. Roll, pitch and yaw are
conventions from aerospace, but there is no authoritative definition on
which axes they correspond to, in which order they should be applied,
and whether they are intrinsic or extrinsic rotations.

As a math library that uses X, Y and Z for the principal axes,
it is more helpful if the documentation sticks to that convention.

This PR adjust the documentation to explain the angles in terms of X, Y
and Z, while still mentioning that the angles are often called roll,
pitch and yaw.

The PR also adds code snippets that shows how to go from Euler angles to
a rotation without using `from_euler_angles()`. So even if the text
explanation isn't clear enough for everyone, the code snippet should
make sure there is no ambiguity.
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.

1 participant