Update odometry implementation in diff_drive #1854
Conversation
github-actions
bot
requested review from
bijoua29,
christophfroehlich,
erickisos,
fmauch,
harderthan,
Maverobot and
saikishor
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #1854 +/- ##
==========================================
- Coverage 85.26% 85.04% -0.22%
==========================================
Files 143 143
Lines 13794 13833 +39
Branches 1193 1197 +4
==========================================
+ Hits 11761 11764 +3
- Misses 1636 1673 +37
+ Partials 397 396 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
| bool updateFromVelocity(double left_vel, double right_vel, const rclcpp::Time & time); | ||
| [[deprecated( | ||
| "Replaced by bool updateOpenLoop(const double & linear_vel, const double & angular_vel, const " |
There was a problem hiding this comment.
| "Replaced by bool updateOpenLoop(const double & linear_vel, const double & angular_vel, const " | |
| "Replaced by bool tryUpdateOpenLoop(const double & linear_vel, const double & angular_vel, const " |
There was a problem hiding this comment.
Fixed in commit 629cf5e,
diff_drive_controller/include/diff_drive_controller/odometry.hpp
Outdated
Show resolved
Hide resolved
diff_drive_controller/include/diff_drive_controller/odometry.hpp
Outdated
Show resolved
Hide resolved
| bool Odometry::updateFromVel( | ||
| const double & left_vel, const double & right_vel, const rclcpp::Time & time) | ||
| { | ||
| const double dt = time.seconds() - timestamp_.seconds(); |
There was a problem hiding this comment.
this is exactly the pattern mentioned with #271 to be removed?
There was a problem hiding this comment.
Sorry, I should have explained this in the PR description.
The reasoning here is the same as that of this #260 (comment).
Additionally, timestamp_ records the last time an update was run; therefore, the correct value of dt can only be obtained from there.
It is used in this function despite (std::fabs(dt) < 1e-6) not being used, as it is also called from updateFromPos() which uses the timestamp_ variable.
| linear_ = linear_vel; | ||
| angular_ = angular_vel; | ||
|
|
||
| return true; |
There was a problem hiding this comment.
why a return value, which is always true?
There was a problem hiding this comment.
This is there to maintain consistency with other update methods, make it easier to add code to this function in the future that may return false, and make the diff_drive_controller.cpp code simpler.
updateFromVel() also has this line for the same reason.
I can change everything back to the normal updateOpenLoop() function if needed, though.
| odometry_.updateFromVelocity( | ||
| left_feedback_mean * left_wheel_radius * period.seconds(), | ||
| right_feedback_mean * right_wheel_radius * period.seconds(), time); | ||
| odometry_updated = odometry_.updateFromVel(left_feedback_mean, right_feedback_mean, time); |
There was a problem hiding this comment.
where did the wheel_radius go?
There was a problem hiding this comment.
My bad! This was meant to be multiplied in the updateFromVel() function. Fixed with d387750.
Co-authored-by: Christoph Fröhlich <[email protected]>
|
Sorry for the delay in fixing the failing checks here! I was busy shifting Linux distros and had tried to make the commits that caused the checks to fail through the web. |
Fixes #271.
Fixes #357.
I have updated the odometry implementation of the
diff_drive_controllerto fix the above two issues alongside improving the code's readability. This implementation is similar to that ofomni_wheel_drive_controller.I have created some new methods and deprecated the older ones.
Should I also make similar changes to other controllers? If yes, should I do that in a separate PR?