fix: data range of euler angles for sensor-independent vehicle frame(#5676) #13494
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.
Reference: https://github.com/JeffYoung17/Blog/blob/master/support_files/v2_gnssins_euler_angles.pdf
As mentioned in (#5676 (comment)) by @hillbrook ,the sensor-independent frame in novatel_parser.cc is FLU, and the frame is converted back to RFU in data_parser.cc.
In novatel_parser.cc, the euler angle around z axis equals (90-azimuth)*deg_to_rad, and its range is [-3pi/2, pi/2], although it’s orientation is right, but the code in novatel_parser.cc lacks of a common theoretical derivation, and the range of Euler angle is also not symmetric.
Meanwhile, in
modules/localization/proto/pose.proto
, the range of euler angle around z axis is in [-pi, pi), so I think that it is better to unify them.@jilinzhou @fengqikai1414 @xmyqsh @JackFu123