Skip to content

TF service should take the match tolerance into account not just into the past but in the future #2212

@leshy

Description

@leshy

if transform match isn't found, and we are searching around a current ts, block and wait a bit, it might arrive

use default tolerance, unless a special forward_tolerance kwarg is set (we often want to search further in the past then block in the future)

this is an issue that caused #2215 and also april tag marker having issues in replays but not in real runs

git checkout feat/ivan/village_recordings
uv run dimos --dtop --replay --replay-db hk_village4 run unitree-go2-markers

Metadata

Metadata

Assignees

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions