Repository navigation
docs: align documentation with the code and lead benchmark pages with results - #200
Merged
Merged
Conversation
A newer push could cancel a docs-changing run on main, and its own diff would then skip the deploy, leaving the site behind main. Main pushes now always build and deploy the documentation. Also drop the deleted benchmarks/plot_homepage.py from CI routing, extract the GIST archive in sample/run_cpp.sh into ./data like run_python.sh (the archive has a top-level gist/ directory), and record the OpenAI dataset source the downloader actually uses.
Correct statements that no longer match the code: advanced-encoder preconditions, HNSW ef/pool clamping, add capacity, M validation and cluster_id_of, the IVF k limit, wheel OpenMP bundling, contributor commands (ctest --no-tests=error, clang-tidy flags, Ruff coverage of .github/scripts), CI routing and caching notes, and the test layout. Add the missing 0.7.1 release notes, point README links at absolute URLs so they also work on PyPI, and remove an unused image.
Benchmark pages now show results before setup and reproduction details, and the overview opens with the GIST1M key results. QPS-recall figures compare methods with similar storage in separate panels, use a validated three-color palette with line and marker encoding, start the recall axis at 0.5 where possible, and keep legends clear of the data. Figure subtitles take the CPU from the build records, and mixed-CPU selections are rejected. The pages also correct setup statements that no longer matched the scripts: the installer's native-optimization setting, the host and thread requirements, the training-time columns and the unpublished raw records. The home page states the RaBitQ error-bound guarantee and gives GIST1M numbers per index. Tables, code and figures use a wider column while prose keeps its measure, and charts scroll sideways on narrow screens.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A pass over the repository docs and the documentation site, checked against the code at
bac860d, plus a refresh of the benchmark pages. The three commits can be reviewed separately.ci:deploy docs on every main push and fix stale script pathsdocs.yml: main pushes always build and deploy. Before, a newer push without docs changes could cancel a docs-changing run, and its own diff would skip the deploy, leaving the site behind main. The workflow contract test checks the new condition.ci_changes.py: remove the deletedbenchmarks/plot_homepage.pyand update its tests.sample/run_cpp.sh: extract the GIST archive into./data, asrun_python.shdoes. The archive has a top-levelgist/directory.DBPEDIA_MANIFEST.json: thesourcefield now names the file the downloader actually fetches.docs:align documentation with the current codequantize_scalardoes not check the code width.ef/pool clamping, add capacity,Mvalidation,cluster_id_of.klimit.ctest --no-tests=errorthroughout;.github/scripts;docs/development.md.v0.7.0..v0.7.1and PRs IVF per cluster storage #140, Fix parallel index execution and zero-range quantization #142–Limit IVF append metadata work to affected clusters #145 and perf(symqg): complete degrees with worker-local reverse candidates #156.docs:lead benchmark pages with results and redraw QPS-recall figuresqps-recall-points.csvwith the newplot_family(). No new measurements were taken; the raw records are not available locally, so the CPU string follows/proc/cpuinfoformat.No API, saved-index format or dependency changes.
Testing
python -m mkdocs build --strict --config-file docs/mkdocs.yml: no warnings. Layout checked in headless-browser screenshots at 1440 px and 390 px, light and dark../scripts/check-python.sh, plusruff format --checkandruff checkon.github/scripts: pass.python -m unittest discover -s .github/scripts -p 'test_*.py': 60 tests OK.python -m pytest tests/python/test_benchmark_protocol.py: 14 passed. The two new plot tests usepytest.importorskip("matplotlib"), so they are skipped in the Python quality job, which does not install matplotlib.shellcheck sample/run_cpp.shandgit diff --check: clean.sample/run_cpp.shend to end (it needs the 2.7 GB GIST download). The fix is based on the archive layout andrun_python.sh.