kctess5/range_libc

(Question/Bug) Why we rotate obstacle only at the origin of map when performing raycasting?

Closed this issue · 1 comments

qlibp commented

The method CDDT used to compute range is not consistent with the definition of ray casting as we only store LUT with rotation on obstacle around the origin of map.

Isn't that the exact method should be rotating obstacles around each grid cell?

qlibp commented

The method CDDT used to compute range is not consistent with the definition of ray casting as we only store LUT with rotation on obstacle around the origin of map.

Isn't that the exact method should be rotating obstacles around each grid cell?

Nop, the code should work. We could merely rotate the map with respect to its origin and when we query, we actually transform the robot/sensor heading to the correct index, so that the robot/sensor heading is aligned with the rotated x-axis