Repository navigation
Keep coastal planning alive and prefer 400 m offshore - #7
Merged
Merged
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.
A 120-second controller watchdog repeatedly cancelled terrain preparation whose provider deadline is 620 seconds. Preserve pending work within one 660-second preparation budget and consume completed results before restarting. Start with a 6 km fine grid within 1.5 km of shore, expand once when no checked connection exists, and retain compatible checked runway during the 400 m preference migration.
Validation: all 89 routing tests passed, including pending-work survival, expired-work cancellation, fine-grid expansion, and migration continuity. A replay on the actual Quy Nhon terrain found a checked coastal route at 387 m endpoint standoff, with 3.29 km progress toward Singapore and unchanged land/depth checks.