simplify pimcomp compare workflow

validation/README.md

@@ -60,6 +60,27 @@ Validate a network or network slice:
 `--operations-dir` may point to any directory tree containing `.onnx` files.
 The script discovers them recursively.
 
+## Raptor vs PIMCOMP comparison
+
+The PIMCOMP paper-model suite has a one-command Arch-A comparison:
+
+```bash
+.venv/bin/python validation/tools/run_pimcomp_paper_latency.py
+```
+
+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 one at a time. Each PIMCOMP GA run evaluates candidates
+in parallel; set `OMP_NUM_THREADS` to control its worker count. Use
+`--models vgg8` for one model or `--dry-run` to print the commands.
+
+Generated artifacts are stored beside each model and ignored by Git. The
+comparison reuses the same model-level `inputs/`, `outputs/`, `runner/`,
+`raptor/`, and `simulation/` paths as regular validation. PIMCOMP-only
+artifacts and `comparison_report.{md,json}` live under `pimcomp/`. See
+[`networks/pimcomp_models/README.md`](networks/pimcomp_models/README.md) for
+profiles, model provenance, limitations, and remote execution.
+
 ## Validation modes
 
 The default mode performs the complete workflow.
@@ -167,7 +188,8 @@ Artifacts are written beside each model:
 | `outputs/` | ONNX-MLIR reference output CSV files. |
 | `raptor/` | Exported MLIR, dialect snapshots, reports, and final `pim/` artifacts. |
 | `runner/` | Generated reference runner source, build tree, and shared library. |
-| `simulation/out.bin` | Functional simulator output used for comparison. |
+| `simulation/` | Functional simulator outputs used for numerical comparison. |
+| `pimcomp/` | PIMCOMP graph, instruction, simulator, and comparison-report artifacts. |
 
 The `raptor/` directory may include `spatial0.mlir`,
 `spatial1_graph.mlir`, `spatial2_trivial_merged.mlir`,