Repository navigation
Cache GGV interpolation during QSS lap optimization - #138
Open
rhorvath02 wants to merge 1 commit into
Open
rhorvath02 wants to merge 1 commit into
rhorvath02 wants to merge 1 commit into
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
1 participant
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.
What
Reuse the unchanged GGV interpolation data during QSS racing-line optimization. Previously every lookup sorted and filtered every speed slice again. Prepare the signed branches once, interpolate only the neighboring speed slices, and evaluate the existing 40 corner-speed bisections across the track together.
The app also identifies linked-GGV lap processing in the run log. Track resolution, solver tolerances and racing-line settings are unchanged.
Stacked on #137.
How to check
The supplied 6 DOF envelope on the 2,062-sample Michigan track took 30.74 seconds for one profiled fixed-line lap before this change and 0.37 seconds afterward. Every speed sample and the 139.038379-second lap time matched exactly.
All 49 lap and GGV provenance tests pass. The added regression compares the cached interpolation with the full-slice calculation across signed turns, missing data, speed knots and out-of-range speeds. Ruff and type checking pass. Local full-suite validation finished with 1,040 passes and one localhost-binding denial. The denied desktop startup test passed when rerun with socket permission, giving 1,041 passing tests and 21 skips across those runs. The full minimum-time benchmark was stopped at the user's request in favor of a fixed minimum-curvature line. That line and lap solve converged in 29.36 seconds.