Skip to content

improve odometry publishing speed #234

@goldbattle

Description

@goldbattle

The odometry with high frequency IMU (greater than 400hz) can be slow since the state is re-integrated from the previous update timestep. More ideally we should cache the result of the previous odometry result and only integrate the next IMU amount. This cache would need to be invalided after update (or propagation). This caused 3x slower simulations compared to before (see a3a209b)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions