From 4ce2ec8171b342f2851d3e6b3db2ea4358c1ef92 Mon Sep 17 00:00:00 2001 From: NiccoloN Date: Thu, 6 Aug 2026 22:04:43 +0200 Subject: [PATCH] avoid raptor automatic build from comparison script --- validation/README.md | 5 +++-- validation/networks/pimcomp_models/README.md | 7 ++++--- .../pim/pimcomp/compare/run_pimcomp_paper_latency.py | 10 ---------- 3 files changed, 7 insertions(+), 15 deletions(-) diff --git a/validation/README.md b/validation/README.md index 6824118..8874d02 100644 --- a/validation/README.md +++ b/validation/README.md @@ -70,8 +70,9 @@ The PIMCOMP paper-model suite has a one-command multi-architecture comparison: ``` The runner verifies PIMCOMP's population-200, 1000-iteration GA settings, -builds Raptor and the existing `third_party/PIMCOMP-NN/build` tree, and compares -the four paper models in parallel. Set `--jobs` to control comparison workers; +expects Raptor and the existing `third_party/PIMCOMP-NN/build` tree to already +be built, and compares the configured paper models in parallel. Set `--jobs` to +control comparison workers; the runner leaves `OMP_NUM_THREADS` at its environment default. Use `--models vgg8` for one model or `--dry-run` to print the commands. diff --git a/validation/networks/pimcomp_models/README.md b/validation/networks/pimcomp_models/README.md index a30048b..b554e77 100644 --- a/validation/networks/pimcomp_models/README.md +++ b/validation/networks/pimcomp_models/README.md @@ -215,9 +215,10 @@ functional validation through `pim-simulator`, and writes Markdown and JSON reports. To reproduce all configured architectures and both latency/throughput modes, -use the model-by-model runner. It verifies the paper GA settings, builds Raptor -and the existing `third_party/PIMCOMP-NN/build` tree, then runs the comparisons -in parallel and regenerates `results.csv` from the JSON reports: +use the model-by-model runner. It verifies the paper GA settings, expects Raptor +and the existing `third_party/PIMCOMP-NN/build` tree to already be built, then +runs the comparisons in parallel and regenerates `results.csv` from the JSON +reports: ```bash .venv/bin/python validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py diff --git a/validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py b/validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py index 17a1de3..25c2aa5 100755 --- a/validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py +++ b/validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py @@ -607,16 +607,6 @@ def main() -> int: print(f"Results root: {out_dir or SUITE}") print("=" * 72) - print_stage("Build Raptor", STAGE_COLORS["Build Runner"]) - run(["cmake", "--build", str(REPO / "build_release")], dry_run=args.dry_run) - - if args.only != "raptor": - print_stage("Build PIMCOMP", STAGE_COLORS["Build Runner"]) - run( - ["cmake", "--build", str(PIMCOMP_SOURCE / "build"), "--target", "PIMCOMP-NN"], - dry_run=args.dry_run, - ) - print_stage("Prepare shared artifacts", STAGE_COLORS["Build Runner"]) for name in args.models: run(