Closed ghost closed 2 years ago
Sorry for replying so late!
In fact, our old version took the continuous global traj generation logic. We modified it to the current logic later.
You could check the difference between them to see what we did to FSM via this link.
I'll close this issue if there are no more questions
Hi, thanks for the amazing work. I was wondering if the
EGOPlannerManager::planGlobalTrajWaypoints
method inplanner_manager.cpp
can be used for multi-WP continuous global trajectory generation. By default the FSM logic seems to visit each WP one-by-one. I wanted your insight on how to go about adding the multi-WP continuous global traj generation. The above-mentioned function already has the core planning logic, but I wanted to get some clarity on how to integrate this with the FSM.