28.50 mAP
YOLOv8n · COCO val2017 · 320 × 320
Exact report value: 0.284969The pinned 320×320 YOLOv8n FLOAT export and signed-symmetric INT8 ONNX Runtime proxy were evaluated over 5,000 COCO val2017 images. The proxy loses 0.887 mAP50–95 points, within the project’s one-point budget. A deterministic 512-image train2017 subset supplied calibration data.
YOLOv8n · COCO val2017 · 320 × 320
Exact report value: 0.284969Signed-symmetric INT8 proxy · 320 × 320
Exact report value: 0.2760983.11% relative loss · 96.9% retained
Exact loss: 0.887 pointsScores use the familiar 0–100 mAP scale; exact 0–1 report values remain visible for traceability. YOLOv8n · 320 × 320 · 5,000 COCO val2017 images. Both software evaluations were repeated with identical predictions. The INT8 result uses an ONNX Runtime QOperator proxy; COCO-wide HASLAB command-path accuracy and hardware measurements remain future work.
ONNX Runtime uses QLinear sigmoid and multiply rather than HASLAB’s fused SiLU lookup, and requantizes learned-head outputs where v0 preserves an INT32 boundary. The proxy measures a calibration candidate; it does not establish whole-detector HASLAB command accuracy. See the INT8 report and calibration record.
The compiler and simulator execute accelerator nodes 0–217 through three raw INT32 learned-head boundaries. The synthetic diagnostic run compares 106 retained or aliased boundaries with the independent integer oracle; release mode matches all 302,400 final INT32 values. Across six additional diagnostic inputs, 37,900,800 stored values match exactly and 1,058,400 decoded host-tail values pass the stated tolerance.
The detection-head report records 44,598,232 scheduled DMA bytes and exact final boundaries. The six-input report records independent accelerator and host-tail comparisons. These counts are not hardware timing or throughput. COCO-wide command-path accuracy, command delivery, RTL, and FPGA execution remain open.
Understand command execution →The full candidate schedule makes command transport and package compaction a concrete pre-RTL decision.
The candidate conformance corpus stores binary commands, initial and expected memory images, completion state, errors, hashes, and provenance. It covers successful and rejected behavior so another implementation can consume the same expected bytes. Stable ABI freeze and final corpus release await independent review.
Rounding, saturation, accumulation order, layouts, conversions, and SiLU behavior have documented semantics and tests.
Memory bounds, DMA, lifecycle, reset, completion, and architectural faults are specified in the v0 contract.
The fixture format and manifest record expectations and integrity checks.
Reports below are linked to reviewed source revision e605bb0. Model weights and COCO images require their own setup; the workload guide gives commands and artifact requirements.