You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i changed example to allow diagonal movement and experimented a little with it. seems like manhattan fails to find shortest solution under certain conditions. e.g. it produces this
instead of
(which is produced by other heuristics)
The text was updated successfully, but these errors were encountered:
In Manhattan distance you only care about the distance in terms of horizontal and vertical movement, not about the number of nodes in between. So imho, the calculated solution is equally correct with the one you get from other heuristics or even this one:
i changed example to allow diagonal movement and experimented a little with it. seems like manhattan fails to find shortest solution under certain conditions. e.g. it produces this


instead of
(which is produced by other heuristics)
The text was updated successfully, but these errors were encountered: