-
Notifications
You must be signed in to change notification settings - Fork 364
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
Waypoints- input explanation #53
Comments
No the track.json file for the miniature race cars is the middle line. MPCC is a path following controller, thus, it needs a reference path it should roughly follow, we often use the middle line, but an ideal line does also work. For the full-size car implementation, I did only have a rough ideal line, but still if you allow MPCC to deviate it will cut the corners more than the ideal line. Finally, there is a difference between an ideal path and the corresponding full state trajectory. P.S. using the ideal line actually helps the performance as we showed in a IROS 2020 paper: https://arxiv.org/abs/2003.04882 |
@alexliniger hi. i was trying to test the code with separate waypoints without the inner and outer boundaries . It worked for one set of waypoints bu not for the other. I am getting an error - bounds initialized The waypoint file is attached here. |
Your file has 1178 element in X but only 1169 in Y |
The way points in the C++/Params/track.json already consists of the racing line (X and Y co-ordinate ) as input which the RC cars follows. Shouldn't the trajectory (X and Y co-ordinates ) be calculated by the cost functions as an output ?
The text was updated successfully, but these errors were encountered: