Following scenarios should be circumvented which appeared in a test game:
ball track lost for some frames, reappearing and geting lost again within the goal boundaries
ball track lost for a couple of frames "near" a goal and counted as goal (as it was not lost factually inside a goal, but within the wrongly recognized boundaries)
Solution:
Make analyzer count a goal only after some grace period of x frames or x fractions of a second without a track re appearing
Following scenarios should be circumvented which appeared in a test game:
Solution:
Make analyzer count a goal only after some grace period of x frames or x fractions of a second without a track re appearing