Distance Regions
TODO:
- [ ] Add page-specific notes for
autonomy-stack/lidar-safety/distance-regions.mdafter inspecting the real project files. - [ ] Cross-link
Distance Regionsto the most relevant code, data, testing, and safety pages. - [ ] Document the exact input entering this subsystem.
- [ ] Document the exact output leaving this subsystem.
- [ ] Map the subsystem to the owning runtime file or module.
- [ ] Describe the control priority when this subsystem disagrees with another subsystem.
- [ ] List the settings, constants, and flags that change this behavior.
- [ ] Add a failure-mode checklist for field testing.
- [ ] Add how to verify the subsystem on the bench before a driving test.
- [ ] Add how to verify the subsystem during a real outdoor run.
- [ ] Document serial port, packet format, reconnect behavior, and stale-scan handling.
- [ ] Add bench test steps with the LiDAR disconnected and reconnected.
- [ ] Document the safety priority order and manual override behavior.
- [ ] Add what must be true before any autonomous outdoor run.
- [ ] Add the exact source path, artifact path, or hardware component name.