Fix Sportec coordinate scaling and own goal issue #216
Conversation
This file contains 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
UnravelSports
changed the title
|
I've also added changed Orientation from Orientation.FIXED_HOME_TEAM to Orieantation.HOME/AWAY_TEAM for both Tracking and Event data, because the assumption that the Orientation is fixed is wrong. Since we have different attacking directions for both period 1 and 2 for both event and tracking data sets |
Merged
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.
Partially resolving #212 and resolving #211
transformer.change_point_dimensions()to the interpreted end coordinatesOWN_GOALas a ShotResult optionEdit: The formatting checks fail, but I've ran
black kloppy/infra/serializers/event/sportec/deserializer.py... Don't know what that's about