nnicolosi/Raptor
1
0
Fork 0
Code Issues Pull Requests Actions 7 Packages Projects Releases Wiki Activity

avoid raptor automatic build from comparison script
Validate Operations / validate-operations (push) Waiting to run
Details

Browse Source
This commit is contained in:
NiccoloN
2026-08-06 22:04:43 +02:00
parent 1c07faace9
commit 4ce2ec8171
3 changed files with 7 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
validation/README.md
+3 -2
View File
@@ -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, The runner verifies PIMCOMP's population-200, 1000-iteration GA settings,
builds Raptor and the existing `third_party/PIMCOMP-NN/build` tree, and compares expects Raptor and the existing `third_party/PIMCOMP-NN/build` tree to already
the four paper models in parallel. Set `--jobs` to control comparison workers; 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 the runner leaves `OMP_NUM_THREADS` at its environment default. Use
`--models vgg8` for one model or `--dry-run` to print the commands. `--models vgg8` for one model or `--dry-run` to print the commands.
validation/networks/pimcomp_models/README.md
+4 -3
View File
@@ -215,9 +215,10 @@ functional validation through `pim-simulator`, and writes Markdown and JSON
reports. reports.
To reproduce all configured architectures and both latency/throughput modes, To reproduce all configured architectures and both latency/throughput modes,
use the model-by-model runner. It verifies the paper GA settings, builds Raptor use the model-by-model runner. It verifies the paper GA settings, expects Raptor
and the existing `third_party/PIMCOMP-NN/build` tree, then runs the comparisons and the existing `third_party/PIMCOMP-NN/build` tree to already be built, then
in parallel and regenerates `results.csv` from the JSON reports: runs the comparisons in parallel and regenerates `results.csv` from the JSON
reports:
```bash ```bash
.venv/bin/python validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py .venv/bin/python validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py
validation/tools/pim/pimcomp/compare/run_pimcomp_paper_latency.py
-10
View File
@@ -607,16 +607,6 @@ def main() -> int:
print(f"Results root: {out_dir or SUITE}") print(f"Results root: {out_dir or SUITE}")
print("=" * 72) 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"]) print_stage("Prepare shared artifacts", STAGE_COLORS["Build Runner"])
for name in args.models: for name in args.models:
run( run(