Skip to content

Use RTTFBuffer's future extrapolation instead of TF fallbacks and waits - #156

Merged
fmrico merged 2 commits into
rollingfrom
tf_future_extrapolation
Oct 31, 2026
Merged

fmrico merged 2 commits into
rollingfrom
tf_future_extrapolation

Conversation

@fmrico

@fmrico fmrico commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Refs EasyNavigation/EasyNavigation#147
Depends on EasyNavigation/EasyNavigation#148

With RTTFBuffer extrapolating a cloud slightly newer than the latest TF, the workarounds for
that case go:

  • NavMap AMCL: the sensor pose at the cloud's stamp no longer falls back to the current TF, or
    to the identity. A cloud without its TF is not scored, with a throttled warning.
  • Bonxai and Octomap maps managers: the TF lookup of each point cloud no longer waits up to
    50 ms, so the callback is not blocked.

Tested in the TIAGo and Summit playgrounds (NavMap AMCL), with normal and stalled odometry TF.

The sensor pose at the cloud's stamp no longer falls back to the current TF,
or to the identity: RTTFBuffer extrapolates a cloud slightly newer than the
odometry, and a cloud without TF is skipped.

Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
RTTFBuffer extrapolates a cloud slightly newer than the latest TF, so the
lookup no longer blocks the callback.

Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
@fmrico
fmrico merged commit 18465c2 into rolling Oct 31, 2026
1 check passed
@fmrico
fmrico deleted the tf_future_extrapolation branch October 31, 2026 05:51
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