Score nested arrays, pairing cost, and schema defaults in extract value F1 - #38
Open
xujustinj wants to merge 2 commits into
Open
Score nested arrays, pairing cost, and schema defaults in extract value F1#38xujustinj wants to merge 2 commits into
xujustinj wants to merge 2 commits into
Conversation
…ue F1. Treat primitive arrays as one opaque cell, pair nested objects by child-field cost, fill omitted keys from JSON Schema default, and treat NaN/Inf/zero-size bbox IoU as a miss. Envelope grounding and per-layer metrics are unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
xujustinj
force-pushed
the
justin/port-canonical-value-f1
branch
from
September 9, 2026 15:44
d7b3d54 to
93763e4
Compare
xujustinj
changed the title
Pairing walked nested keys with .get, so omitted defaulted fields looked like None while F1 scored them as the default and could assign the wrong rows. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
string[],number[], and null combinators) as one opaque cell instead of silently skipping them.defaultwhen present; withoutdefault, an omitted key is a one-sided miss (not implicit null). Pairing reads those same nested leaves throughlookup, so omitted defaulted fields pair as the default rather thanNone.Test plan
uv run --extra dev python -m pytest tests/extract_bench/evaluation/metrics/extract/test_unified_evidence_metric.py tests/extract_bench/evaluation/metrics/extract/test_array_record_match_metric.py"default": nullstill treat omit as gold-null (same as before on this corpus)Made with Cursor