Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PiPER simulation repeatedly allocated a force array and contact membership sets during each contact scan. This experimental patch reuses scratch storage within a scan while retaining every fresh force query and all 1 ms mechanics, safety and outcome checks.
Four fixed ABBA action-tape runs measured 15.70% lower pooled mean environment-step wall compute and 12.60% lower process CPU compute on the shared host. Ten separate diagnostics exactly match 200,010 recorded native snapshots, contact evidence and independently recomputed outcome state. The original 64 MiB reader refusal and supplemental streaming audit are both retained; no physics or timing reruns were used.
Validation: 11 native PiPER tests, six feedback tests, three contact freshness/threshold tests, four profile tests, ten comparison tests, packaging and guarded publication checks. This is one synthetic scenario and two timing pairs; no new task accuracy, physical qualification or real-time guarantee. No new wheel, stable-main change or production-runtime promotion is included. The prior learned held-out result remains 5/12.