Ironically the result from this Bruteforce gif is actually sub-optimal.
Bearing in mind we don't easily have the exact coordinates from the animation: The line from 17,68 to 95,80 (distance approximately 79) should be removed and a new line added from 45,15 to 58,55 (distance approximately 42) to reach the optimal solution. Brendan Hide (talk) 13:08, 21 March 2013 (UTC)
Yes, that also hit my eye. Actually, there seems to be a problem with either the computed distances or the plotting: the coordinates in the plot seem to be about
| 46.5 | 16.2 |
| 33.6 | 26.9 |
| 13.4 | 31.0 |
| 0.9 | 61.1 |
| 15.7 | 66.7 |
| 56.7 | 54.2 |
| 94.0 | 80.6 |
but the computed distances (also those echoed during the running of the algorithms) do not conform at all. With these coordinates the supposed optimal solution corresponds to a length of 211, while the improvement sketched above gives 171 (and is indeed easily visible). Anyone care to fix this? Seattle Jörg (talk) 12:45, 19 June 2013 (UTC)
