feat(lidar): add ground segmentation diagnostic benchmark
This commit is contained in:
@@ -14,6 +14,16 @@ equivalence report. The React surface reads those reports through the read-only
|
||||
`/api/v1/lidar/replay-packs` boundary; CUDA/TensorRT and ROS do not move into the
|
||||
browser.
|
||||
|
||||
`missioncore.lidar-ground-benchmark/v1` extends the same boundary for L2. It
|
||||
keeps point-aligned ground/assigned masks for the current local-percentile
|
||||
proposal and a candidate provider, exact provider/source/binary identities,
|
||||
host latency and algorithm disagreement. The first official Patchwork++ v1.4.1
|
||||
run is diagnostic-only: current K1 evidence is a vendor-map increment, not the
|
||||
sensor-centric scan and physical-height contract Patchwork++ expects. The
|
||||
read-only `/api/v1/lidar/ground-benchmarks` surface therefore publishes
|
||||
`production_promotion=false` until an independent annotation generation or an
|
||||
admitted raw scan closes the input gate.
|
||||
|
||||
## Boundary
|
||||
|
||||
```text
|
||||
|
||||
Reference in New Issue
Block a user