opp-repl-comparing-simulations

To compare simulation results across two project commits, run the compare_simulations workflow on the project variants. It generates a concordance report classifying stdout, fingerprint, and scalar trajectories as identical, divergent, or different to identify regressions.

Simulation stdout trajectory comparison validates refactors by mapping two project variants side-by-side and checking deterministic output streams. It classifies outcomes as IDENTICAL or DIVERGENT, providing interactive debugging hooks to pinpoint exact divergence positions during analysis.

Yes, you can use interactive debugging functions to pinpoint divergence positions within fingerprint trajectories. When comparing scalar results or fingerprints, the tool identifies exact divergence points to help isolate the cause of different simulation outcomes.

The best way to check for regressions in an overlay build is comparing commit-to-commit or side-by-side project variants. This deterministic comparison evaluates stdout, fingerprint, and scalar results to report identical, divergent, or different outcomes for refactor validation.

Comparing simulation scalars fully supports side-by-side project variant checks. It evaluates scalar results deterministically alongside fingerprint and stdout trajectories, classifying outcomes as identical, different, or divergent to confirm whether project changes introduced regressions.