{
  "case_id": "gear_sonic/end_to_end_cli_loop",
  "command_fixture": {
    "data": [
      0.3,
      0.0,
      0.0
    ],
    "kind": "velocity"
  },
  "description": "RoboWBC CLI loop running configs/sonic_g1.toml through the synthetic transport with a JSON report, after rewriting all three GEAR-Sonic provider blocks to the requested provider.",
  "host_fingerprint": "runnervmeorf1 | Linux 6.17.0-1010-azure | x86_64 | AMD EPYC 7763 64-Core Processor",
  "hz": 48.867,
  "implementation": "ort-cpp-sonic",
  "implementation_label": "ORT-cpp-sonic",
  "interpretation": "This is the full deployment-loop question: can the live velocity path hold frequency end to end on the requested provider, not just in one isolated inference call?",
  "notes": "Measured via the ORT-cpp-sonic GEAR-Sonic C++ ONNX Runtime harness on the pinned source checkout.",
  "p50_ns": 3573092,
  "p95_ns": 4192086,
  "p99_ns": 6002150,
  "provider": "cpu",
  "provider_family": "cpu-baseline",
  "raw_source": "/home/runner/work/robowbc/robowbc/artifacts/benchmarks/nvidia/ort-cpp-sonic/cpu/raw/gear_sonic__end_to_end_cli_loop.json",
  "robowbc_commit": "53994db55a58041ebb4e63f3e0e0a1b424ba0cf6",
  "samples": 200,
  "schema_version": 1,
  "source_command": "python3 scripts/benchmarks/bench_nvidia_official.py --case gear_sonic/end_to_end_cli_loop --provider cpu",
  "stack": "official_nvidia",
  "status": "ok",
  "upstream_commit": "bc38f6d0ce6cab4589e025037ad0bfbab7ba73d8",
  "variant_label": "cpu-baseline",
  "variant_slug": "cpu-baseline",
  "warmup_policy": "default_cli_loop_200_ticks"
}