You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, In game 0021500196, event 2, 'time_left': [705, 704, 685, 684]}, 'event_str': ['miss', 'rebound', 'miss', 'rebound'],
and match these with the shot clock left and the court visualization, the time_left in play-by-play seems like not describing the event segmentation correctly.
For 685.0 the shot clock is at 21.77, which at the time the shot was already missed for a while and the defending team got rebound and was already switching to offense. The event miss should be marked right after 24s shot clock reset.
The text was updated successfully, but these errors were encountered:
For example, In game
0021500196
, event2
,'time_left': [705, 704, 685, 684]}
,'event_str': ['miss', 'rebound', 'miss', 'rebound'],
and match these with the shot clock left and the court visualization, the time_left in play-by-play seems like not describing the event segmentation correctly.
For 685.0 the shot clock is at 21.77, which at the time the shot was already missed for a while and the defending team got rebound and was already switching to offense. The event
miss
should be marked right after 24s shot clock reset.The text was updated successfully, but these errors were encountered: