Closed hagenw closed 8 years ago
I've fixed this. The bug is due to RotationKS uses information from robot.AzimuthMin and robot.AzimuthMax to make sure rotation angles are within the allowed range. For some reason they are set properly in the example.
In TWOEARS/examples go to the folder
localisation_w_and_wo_head_movements
and run the following:I tested it under Linux and Matlab 2015a.