Closed MTDzi closed 1 year ago
I'm not sure if I did a good job at explaining what the issue is, please let me know if I should clarify / expand what I mean. Also, if the plots are not clear, let me know.
Hey @MTDzi, it all looks good except one part, np.unique
returns a sorted array, so if you notice your plots are always sorted on the x-axis. Without it it should be fine, otherwise let me know :slightly_smiling_face:
Kudos for spotting this bug. Thanks!
I'm looking at the
MLPlanner._initialization
attribute and I'm trying to extract a (rough) route based on that. I extended theMLPlanner
class, and added a method:but I noticed the roadblocks don't come in the order that complies with the expert (GT) trajectory.
I made a plot in which we can see the expert trajectory (orange) and the route extracted with the function above (blue) with the points connected so that it's clear which point follows which:
(This is for the
2021.10.05.07.10.04_veh-52_01442_01802
log file, but there are many such cases.)I assumed that the roadblocks are in an order that "tells" the planner how to go. (I guess the reason I thought so is that the mission goal and the last roadblock match.)
Is this assumption wrong? Or should the roadblocks be in an order that complies with the GT trajectory?
Addendum: I suspected the roadblock connectors might cause some issues but even if I use the following version of that method:
but even then this is what I get: