Routing strategy for ambiguous routes assigned with AssignRouteAction shall remain simulator specific
With #596 (closed) the default routing behaviour was defined more explicitly. The default behaviour was changed to "go straight" if no route is assigned to the entity. With this change, however, also the behaviour for ambiguous routes assigned via an AssignRouteAction was modified (see 6.8.2 Explicitly assigned route). The new criterion might be difficult to implement for most of the standard routing algorithms and should be reverted to the old simulator-specific definition.
Document version of this comment
Branch: v1.3.0-RC1
Description:
For ambiguous routes assigned with an AssignRouteAction, the following change was made:
Before:
If, for example, the RouteStrategy
"shortest" results in multiple possible routes of equal lengths, it is up to the simulator which route to choose.
After:
There may be cases where even the use of a RouteStrategy
will lead to ambiguous routes. If, for example, the RouteStrategy
"shortest" results in multiple possible routes of equal lengths, the algorithm above ("go straight") shall apply. In this case, only valid lanes on possible routes shall be used.
Suggestion:
Revert behaviour such that simulator can decide which route to choose.
"If, for example, the RouteStrategy
"shortest" results in multiple possible routes of equal lengths, it is up to the simulator which route to choose."