Repository navigation
Split corner-crossing marks, share the ground entry cap, aim at one missing run #154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the newly separated run has exactly
needed(three) cells and is bordered by.skippedcells, this selects its midpoint even though an aim task always checks a fixed 0.6 m window. With 0.1524 m cells, that window covers five cells; after the homeowner covers all three cells in the selected run,isSatisfiedsees only 3/5 covered because the skipped boundary cells are not coverage, below the 0.8 threshold, so the instruction cannot complete without re-observing an area the homeowner already marked inaccessible and will instead stall or reappear. Keep the task span within the selected run or require a run wide enough for the fixed aim window.AGENTS.md reference: AGENTS.md:L34-L34
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AidenJohnston Independent six-file review plus lead source tracing confirm the three-cell case at 9d0a662. Missing cells14-16 center at s=2.3622m; the fixed ±0.3m aim window overlaps13-17. If13 and17 are skipped, covering all three accessible cells reaches3/5=0.6, below0.8. The instruction can leave via the20-second stall timeout, so this is stalled completion rather than a permanent lock. Please keep the requested/settled span within the selected accessible run, or select a satisfiable window, and cover this three-cell case without counting skipped ground as observed. The four-cell changed test misses it. Shared export budget and split rendering had no additional concrete finding in this review; physical behavior is unverified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 3ec22b2.
laggingBandnow skips any run whose aim can't be met:canSatisfychecks that the non-skipped cells in the fixed ±0.3 m stretch around the run's middle still reachaimSatisfied. Skipped cells are never treated as observed. New testthreeMissingCellsBetweenSkippedOnesAreNotAskedForcovers this exact case: missing ground cells 14 to 16 centred at s = 2.3622, with 13 and 17 skipped. No ground aim is asked for there. As a control, with 13 and 17 open the same map still aims at 2.3622. Mac minig5-tf1at 3ec22b2: drift passed, and HouseScanKitswift test -warnings-as-errorspassed (517 tests), as did the device build. UI tests are still queued.firstHolehas the same pattern but predates this PR, so it is noted under Known gaps in the PR body and not changed here.