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
As getting players team id is quiet long, the idea is to call this process only when a knew player is detected assuming he will not change of team during the play ;).
Then in main.py of example/soccer
in run_radar after players identification from line 342 I suggest
for instance in 2e57b9_0.mp4', on a total of 750 frames, 663 of them show unchanged tracks compared to previous frame i.e avoiding the call to team_classifier (note this should be larger as during the last frames one of the player is lost and seen again when he runs near the lateral lane and is likely considered as a referee.
One my laptop processing time for this video decreased from 817s to 191s :)
As I am not a top coder I guess there are smarter way to code this idea :)
The text was updated successfully, but these errors were encountered:
Many thanks for providing this repo.
As getting players team id is quiet long, the idea is to call this process only when a knew player is detected assuming he will not change of team during the play ;).
Then in main.py of example/soccer
in run_radar after players identification from line 342 I suggest
for instance in 2e57b9_0.mp4', on a total of 750 frames, 663 of them show unchanged tracks compared to previous frame i.e avoiding the call to team_classifier (note this should be larger as during the last frames one of the player is lost and seen again when he runs near the lateral lane and is likely considered as a referee.
One my laptop processing time for this video decreased from 817s to 191s :)
As I am not a top coder I guess there are smarter way to code this idea :)
The text was updated successfully, but these errors were encountered: