Repository navigation
PLZA walk_to_marker: drop near reads the walk cannot have reached - #626
Merged
Merged
Conversation
Run 9 of 03.09 (console B, 2026-11-16 21:33) took 4 5.4 s after 40 at Wild Zone 1's exit (the marker showed 39) and passed on the exit pillar's prompt. A read of 20 or less is now taken only if the walk can have come that near since the last read taken (5 m/s plus 2 m of OCR jitter, from run 10's 23 down to 12 in 3.2 s); rejected reads are logged.
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.
Base:
plza/port-original-0308-0311(#623); the diff shows only this change.In run 9 of 03.09 (console B, 2026-11-16 21:33) walk_to_marker took a read of 4 just 5.4 s after 40 at Wild Zone 1's exit, where the marker showed 39, and passed on the exit pillar's "Esci" prompt, so research_lab_gate never started. MarkerArrival now takes a read of 20 or less only if the walk can have come that near since the last read taken (5 m/s plus 2 m of OCR jitter; run 10 read 23 down to 12 in 3.2 s), and the walk logs each rejected read ("read 4 after 40 in 5.4 s: ignored"). Looks now carry their time. AutoStoryMarkerArrival tests gain the run 9 log sequence (red before the fix: arrived on the 4) and two genuine fast approaches that still arrive; the suite was run locally in a scratch harness, the touched files syntax-checked, and CI runs the full build.