Skip to content

Land filter gentle threshold - #31

Merged
bw4sz merged 2 commits into
mainfrom
land-filter-gentle-threshold
Aug 26, 2026
Merged

bw4sz merged 2 commits into
mainfrom
land-filter-gentle-threshold

Conversation

@bw4sz

@bw4sz bw4sz commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

bw4sz and others added 2 commits August 26, 2026 17:50
Collaborators asked for maximum gentleness: only unambiguous land should be
screened, nothing with water, a lagoon, or a beach that could hold birds.
Sets WATER_LOSS_BUDGET to 0.0 (was 0.03), moving the fitted operating point
from 0.610 (87.5% land recall, 1/37 water lost) to 0.920 (33.3% land recall,
0/37 water lost) on the current 61 labelled frames. Also adds a Mixed-frame
diagnostic to the refit script so that once collaborators label some Mixed
(shoreline) frames, we can directly check the threshold doesn't screen them.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The check added in the previous commit only looked at the primary "Land
Screen" project and only had features for images already in manifest.csv.
Both real Mixed annotations that exist (found right after that commit, on
BOEM - Land Screen Validation) come from the broader mined pool used for
validation sampling, so the check silently produced zero rows instead of
catching them. Now pulls labels from both projects and falls back to
new_flight_scores.csv / new_flight_scores_deep.csv for features.

Refit with one new Water label since the last commit: threshold 0.920 ->
0.910, cv_auc 0.968 -> 0.971. Confirmed both known Mixed frames score below
the new threshold (0.860 and 0.907 vs 0.910) -- both would have been wrongly
flagged as land under the old 0.610 threshold, neither is now.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@bw4sz
bw4sz merged commit cebcc6b into main Aug 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant