Skip to content

AMCL localizers: robot_pose carries the robot's velocity - #162

Merged
fmrico merged 1 commit into
rollingfrom
robot_pose_velocity
Oct 31, 2026
Merged

fmrico merged 1 commit into
rollingfrom
robot_pose_velocity

Conversation

@fmrico

@fmrico fmrico commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Fixes #161

The twist of robot_pose is now the robot's velocity (robot frame) instead of zero, in the AMCL localizers (costmap, navmap, simple) and MH-AMCL:

  • From the odometry topic, or the odometry in NavState (MH-AMCL): its twist.
  • With compute_odom_from_tf: from the motion between consecutive odom → robot TF samples. The same sample again (TF slower than the cycle) keeps the previous value.

Tests

One test per localizer: no odometry yet is stopped; the topic's velocity, turning in place included; from TF (navmap, costmap, MH-AMCL): moving, the same sample again, turning in place and stopped.

The AMCL localizers (costmap, navmap, simple) and MH-AMCL published
robot_pose with a zero twist, so whatever read it took the robot as
stopped. It is now the odometry's velocity; with compute_odom_from_tf,
from the motion between TF samples.

Fixes #161

Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
@fmrico
fmrico force-pushed the robot_pose_velocity branch from 0c28bed to 29bd8e5 Compare October 31, 2026 18:29
@fmrico
fmrico merged commit 6d0c5dc into rolling Oct 31, 2026
1 check passed
@fmrico
fmrico deleted the robot_pose_velocity branch October 31, 2026 19:07
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.

AMCL localizers publish robot_pose with a zero velocity

1 participant