Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracab Meta added (V4) #353

Merged
merged 3 commits into from
Oct 22, 2024
Merged

Conversation

UnravelSports
Copy link
Contributor

I've added an option for reading yet another version of the Tracab Meta data (as requested by here #352)

My main concern is the ever growing amount of random Tracab Meta file configurations, but for now this implementation should hold. Not sure how to approach this other than wait for issues to be raised...

It first checks if there is a "match" attribute in the meta_data and if not it will check a key I have yet only seen in this new version of the meta data (Phase1StartFrame). Additionally there are some small additions to make the create_team function a bit more flexible because some tags have slightly changed in this version. <Player> became <item> and <TeamId> became <TeamID> (same for player ids).

I've also added new tests.

@UnravelSports
Copy link
Contributor Author

The tests seem to fail at a random file I didn't touch?

@Alek050
Copy link

Alek050 commented Sep 27, 2024

The tests seem to fail at a random file I didn't touch?

Was just sniffing around this issue. Seems like the git actions fail on the formatting of kloppy/infra/serializers/event/sportec/deserializer.py. I am guessing that your local formatting settings (maybe with black?) are different from the ones on git, but not sure though.

@UnravelSports
Copy link
Contributor Author

I see my commit contains that file, in a slightly different format. Weird 🤷‍♀️

@UnravelSports
Copy link
Contributor Author

I had black version 23.3.0 instead of 22.3.0...

@koenvo koenvo merged commit 64302b7 into PySport:master Oct 22, 2024
19 checks passed
@koenvo koenvo added this to the 3.16.0 milestone Oct 22, 2024
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.

3 participants