fix: compare SkillCorner ball IDs by value - #185
Open
Litju wants to merge 1 commit into
Open
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.
Summary
The SkillCorner parser currently associates ball observations using Python object identity:
Match metadata and positional tracking data are decoded from separate JSON files. Equal provider identifiers are therefore not guaranteed to refer to the same Python object, even though they represent the same ball.
This can silently leave valid ball coordinates as
NaN.Change
Use identifier value equality for ball association:
The production change is limited to this predicate.
Regression protection
Added a compact synthetic regression test that:
read_position_data_jsonparser.No proprietary provider data are included.
Measured result
On the deterministic regression fixture:
[NaN, NaN][12.5, -3.25]NaN[0.0, 0.0]Home and Away control outputs remain unchanged.
Validation
1 passed1 passed9 passed280 passed280 passedThe full-repository flake8 output retains exactly two pre-existing unrelated
E226findings. This change introduces no new lint findings.Scope
This PR does not change: