Skip to content

voxel_layer: Wrong bounding box coordinates printed on "costmap cannot raytrace" warning #3415

@jlblancoc

Description

@jlblancoc

Bug report

Required Info:

  • Operating System:
    • u22.04
  • ROS2 Version:
    • Humble / ...
  • Version or commit hash:
    • main branch

Steps to reproduce issue

VoxelLayer::raytraceFreespace() gets an observation origin point out of the map bounding box. This is actually happening to me while debugging the integration of MVSim with Nav2, so this condition is probably a bug somewhere else, but this ticket is about a wrong warning message.

Expected behavior

Prints that origin is out of bounding box.

Actual behavior

Incorrect bbox coordinates are printed.

Additional information

Trivial fix. I'm opening a PR to fix it now.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions