From aceea293a3ad3ba4b6b8de0c21c1ed4413efece1 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 18 Oct 2026 13:19:44 +0000 Subject: [PATCH] docs: drop 'rigorous' wording for the window tolerance (no threshold change) Co-Authored-By: Claude Opus 5.5 --- tests/validation/time_window_dfg.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/validation/time_window_dfg.py b/tests/validation/time_window_dfg.py index b90a9cd..5f7bbe0 100644 --- a/tests/validation/time_window_dfg.py +++ b/tests/validation/time_window_dfg.py @@ -10,8 +10,8 @@ Equal simulated duration, same fresh state and warm-up per variant, one observat All variants keep observe_raw_exchange=True; the backend is built once with observe_window_exchange=True (a closed window adds no launch). Populations (bitwise) and per-interval total impulses are compared OUTSIDE timing; the impulse tolerance is a -conservative engineering tolerance (see INTERVAL_RTOL), the rigorous substep-scaled comparison -being the capability test in tests/validation/multigrid/test_exchange_window.py. +conservative engineering tolerance (see INTERVAL_RTOL); the tighter substep-scaled engineering +tolerance is exercised by the capability test tests/validation/multigrid/test_exchange_window.py. Wall time (perf_counter) with explicit stream synchronization is the only timing source. """