fix rounding error is dotbot calculation of stop position

[Raa37]

Tested and compared dotbot positions calculated at orchestrator and locally for dotbot and all values are identical . There doesnt seem to be a rounding error. will close issue

[Raa37]

Equations 1 , 2 and 3 are the main equations used for bump calculations. (finding actual bump position seems to be fine) but these equations are where we get differences in x, y values :

• timetobump = (distance between (startX, startY) and (bumpX, bumpY))/speed
• bumpX = startX + timetobump * math.cos(math.radians(self.currentHeading - 90))
• bumpY = startY + timetobump * math.sin(math.radians(self.currentHeading - 90)) An example is when bumpX = 9.500738283539821, bumpY = 1.0, speed = 1, angle = 48.37112788046444 If we substitute into equtions 2, we get bumpX = 9.500738283539821, bumpY = 0.9999999999999991 I don't know how much they round the sin and cos in python for example because I'm sure that's one of the mismatches causing the error/difference. So that's why I was rounding, because in theory yes both distances should be the exact same in both equations but there is some hidden rounding in the sin/cos. So when I do the exact same calculations with mu scientific I get different values, and when using calculators online , also different values.

For now, I have decided to round to 5 decimal points instead of 3, and only for the final output of equations 2,3 and the bumpX bumpY calculated by the line clipping algorithm, to compensate for the rounding in sin/cos that causes the mismatch in values.