tzhouamandClaude Opus 5
3834de3105
Renamed from vllm-embedding: nothing here is about embeddings, and the name had come from the parent working directory. edge-infer says what it does. The GitHub repository is renamed to match; nothing had been pushed yet. The audit found the packaging was incomplete in two ways. Scripts: 56 of them produced results that are published in this repo but were not included, so the numbers could be read and not checked. Added under benchmarks/edge_harness/experiments/ (one-off drivers: the AI Hub on-device runs, the 4-bit GEMM microbenchmark, fidelity and parity checks, checkpoint build and round-trip, activation capture, and the load generator used to prove the contention guard actually refuses) and benchmarks/edge_harness/runs/ (the 24 shell drivers behind published grids). Both directories carry a README saying plainly that they are a record of what was run rather than a supported interface -- most hardcode absolute paths from the machine they ran on. The supported entry points remain the tools one level up. One broken relative link fixed (comparison.md is under docs/engines/, not docs/analysis/). All other links and every script reference in the docs now resolve inside the repo. Secret scan: the token in ~/.qai_hub/client.ini is absent from the worktree and from all 61 commits. Worth noting that an earlier version of my own check reported a false positive, because `grep -rl ... | head` takes its exit status from head, which always succeeds -- the same class of mistake as the measurement errors this project keeps recording. The AI Hub scripts authenticate by reading that file at runtime and contain no credential. README reframed for the new name and the wider scope: the repository is the engine changes, the harness, the raw results, the baselines and the analyses, not just a patch set. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L1ax5wYLA6XbqEL1i8L9gZ
1.4 KiB
1.4 KiB
One-off experiment drivers
Scripts that produced a specific result rather than tooling meant to be reused.
Kept because the results in ../results/ are only checkable if the script that
made them is here.
| group | what |
|---|---|
aihub_*.py |
Qualcomm AI Hub on-device runs — Snapdragon layer timings, calibration, w8a16/w4a16 parity. Authentication comes from ~/.qai_hub/client.ini; no credential is in these files |
bench_int4_kernels.py |
the 4-bit GEMM microbenchmark — kernel-level shapes, used to size decisions before building anything |
quality_int4.py, ppl_vllm.py, parity_hf_vs_vllm.py, ref_hf.py |
fidelity: greedy divergence, perplexity, and parity against a HuggingFace reference |
quantize_int8.py, export_gptq_cpu.py, dequantize_int4.py, verify_export.py |
building and round-tripping checkpoints |
capture_real_acts.py, capture_lm_head.py |
activation capture for calibrated quantization |
cpu_busy.py |
a load generator, used to test that the harness's contention guard actually refuses |
They are not portable as written. Most carry absolute paths from the machine
they ran on (/data/<user>/embedding_infer/...) and expect checkpoints under
models/. They are a record of what was run, not a supported interface — the
supported entry points are the tools one level up, described in
docs/edge/harness.md.