Frank14f/CelerisLab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: drop 'rigorous' wording for the window tolerance (no threshold change)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Claude
2026-10-18 13:19:44 +00:00
co-authored by Claude Opus 5.5
parent a233c90324
commit aceea293a3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/validation/time_window_dfg.py
+2 -2
View File
@@ -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.
"""