Skip to main content

Module lidar_loop_scenario

Module lidar_loop_scenario 

Source
Expand description

Deterministic corridor-loop scenario for LidarGraphSlam.

A robot drives slightly more than one lap of a 3 m wide rectangular corridor (30 × 20 m outer walls, 24 × 14 m inner block) with pillars along the walls — except the top corridor, which is left featureless so the scan-to-map front end cannot observe forward motion there. Wheel odometry over-reports distance and drifts in yaw; the simulated 2D LiDAR adds range noise. run_corridor_loop records every step so examples, gallery renderers, and the playground can replay the same run.

Structs§

CorridorLoopConfig
Scenario parameters for run_corridor_loop.
CorridorLoopFrame
State recorded after one LidarGraphSlam::update.
CorridorLoopRun
A full recorded run of the corridor-loop scenario.

Enums§

CorridorLayout
Pillar arrangement along the bottom corridor.

Functions§

aliased_corridor_config
Perceptual-aliasing variant: identical pillars every 2.5 m along the bottom corridor and a start in its middle, where no corner is in LiDAR range, so loop matches can lock onto the wrong pillar.
corridor_loop_deltas
Body-frame step deltas along the corridor centerline (rounded rectangle), starting start_offset meters along it and covering one lap plus extra_distance.
corridor_loop_lap_length
Length of one lap of the corridor centerline [m].
corridor_loop_start
Start pose of the scenario (bottom corridor, heading +x).
corridor_loop_start_for
Start pose of config: start_offset meters along the centerline.
corridor_loop_walls
Walls of the corridor loop: outer 30 × 20 m, inner block 24 × 14 m, and pillars at irregular spacing except along the top corridor.
corridor_loop_walls_for
Walls of the corridor loop with the given bottom-corridor layout.
position_rmse
Planar position RMSE between two equally indexed pose sequences [m].
run_corridor_loop
Runs LidarGraphSlam through the corridor loop and records every step.