-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
difference with ego planner #12
Comments
In my view, GCOPTER is mostly a planning backend (trajectory optimizer), while ego-planner is a complete planning method including frontend and backend. Ego-planner is an ESDF-free planner by using collision-free trajectory as guiding path in frontend. Ego-planner set same time interval between control points in the first round optimization, then adjust it to ensure dynamical feasibility in the second round optimization (they call it refinement). It utilise B-spline to fit the trajectory and apply gradient-based optimization directly. While GCOPTER is a spatial-temporal joint planning optimizer. their paper proofs a unique optimal trajectory exists in un-constraint case, which is a |
GCOPTER acts as a back-end trajectory optimization module in the whole planning system. You can replace the back-end of EGO-planner with GCOPTER, in fact, this has been done in this project. |
hello! I take care of you work with long time.I have some questions.I would like to know this work and you ego-planner are two different works in trajectory planning?I can use GCOPTER as a black box?thank you very much
The text was updated successfully, but these errors were encountered: