fix: increase costmap floor z_offset to avoid z-fighting

[Nabla7]

No description provided.

[greptile-apps]

Greptile Overview

Greptile Summary

Increased the z_offset parameter from 0.05 to 0.07 for the costmap floor mesh visualization to prevent z-fighting artifacts in the Rerun viewer.

• The change affects only the 3D mesh visualization at world/nav/costmap/floor, not the 2D image view or the actual costmap data
• Z-fighting occurs when two surfaces occupy nearly the same depth, causing flickering; increasing the offset lifts the costmap mesh further above the ground plane
• The new value (0.07m = 7cm) is still much smaller than the path visualization offset (0.2m), maintaining proper visual layering
• No functional or data processing changes; purely a visualization improvement

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• Single-line change to a visualization parameter with no impact on functionality, data processing, or system behavior. The change addresses a well-known graphics rendering issue (z-fighting) with a sensible value adjustment.
• No files require special attention.

Sequence Diagram

sequenceDiagram
    participant GM as global_map (In)
    participant CM as CostMapper
    participant Algo as Occupancy Algorithm
    participant Out as global_costmap (Out)
    participant RR as Rerun Viewer

    GM->>CM: PointCloud2 message
    CM->>CM: _calculate_and_time()
    CM->>Algo: _calculate_costmap()
    Algo-->>CM: OccupancyGrid
    CM->>Out: publish(OccupancyGrid)
    CM->>RR: log 2D image (world/nav/costmap/image)
    CM->>RR: log 3D floor mesh (world/nav/costmap/floor, z_offset=0.07)
    CM->>RR: log metrics (calc_ms, latency_ms)

Loading

[greptile-apps]

_{No files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}