I discovered this bug yesterday night, and solved it this morning.
Essentially, the agent's current location was not included in the list of origin_locations, causing route suggestions like ->B->A to be possible when the AwarenessLevel is higher than 1.
In addition, the routefinding branching would be terminated whenever any previous location touched upon by the algorithm was hit, which caused routes to be wrongly eliminated when the AwarenessLevel is higher than 1.
These issues resulted in malfunctions when the AwarenessLevel is higher than 1, but did not affect the behavior for values 1 or 0.
I discovered this bug yesterday night, and solved it this morning.
Essentially, the agent's current location was not included in the list of
origin_locations, causing route suggestions like ->B->A to be possible when theAwarenessLevelis higher than 1.In addition, the routefinding branching would be terminated whenever any previous location touched upon by the algorithm was hit, which caused routes to be wrongly eliminated when the
AwarenessLevelis higher than 1.These issues resulted in malfunctions when the
AwarenessLevelis higher than 1, but did not affect the behavior for values 1 or 0.