In all versions there is a gap in the radar scanning caused by the movement of the robot. This is caused by the radar
sweep being calculated a descrete points during the sweep. For instance robotA is at 1000,1000, traveling at speed 8
with heading of 90 degrees. RobotB is at 800,1004. RobotA scans 190 to 180 degrees this turn. On the next turn, robotA
is at 1000,1008 and scans 180 to 170. Using the current algorythm, robotA missed seeing robot B.
The current algorythm considers a robot to have been scanned if it is between two radials. The first radial is the old
radar heading drawn from the new position, and the second is the new radar heading drawn from the new position. The
algorythm should be changed to have the first radial drawn from the previous possition.
This might sound nit picky, but it does introduce a number of aberations in the tracking software for a number of bots.
The software is probably getting mature enough to address these types of minor bugs.