When the ball is dead and not identified in second spectrum tracking data, default ball coordinates [0, 0, -10] are used.
This leads to a SchemaError when creating the game object using the get_game_from_kloppy function.
This can be prevented by setting the only_alive parameter to true when loading the tracking dataset in kloppy, however this raises a warning and impacts the tracking/event synchronisation.
This is a documented issue in kloppy (see PySport/kloppy#523). If the suggested pull request is implemented and there is an option to remove frames where the ball is not identified, may still be some issues:
- how to ensure the
exclude_missing_ball_frames parameter use in kloppy prior to creating the game object (other than the SchemaError discussed above)
- will the tracking/event synchroniser be impacted by the missing frames
When the ball is dead and not identified in second spectrum tracking data, default ball coordinates [0, 0, -10] are used.
This leads to a
SchemaErrorwhen creating the game object using theget_game_from_kloppyfunction.This can be prevented by setting the
only_aliveparameter to true when loading the tracking dataset in kloppy, however this raises a warning and impacts the tracking/event synchronisation.This is a documented issue in kloppy (see PySport/kloppy#523). If the suggested pull request is implemented and there is an option to remove frames where the ball is not identified, may still be some issues:
exclude_missing_ball_framesparameter use in kloppy prior to creating the game object (other than theSchemaErrordiscussed above)