-
Notifications
You must be signed in to change notification settings - Fork 51
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
Add PointAt constraint #427
Add PointAt constraint #427
Conversation
I've confirmed this works. There's a lot of gotchas around when the constraint is valid to use tho, vs immediately making the trajectory infeasible. In my test, I had to make a translation waypoint between two pose waypoints, then add the point-at constraint to the translation waypoint only. It would be nice if there was a separate point the user could drag around that represented where to point at, but we can do that later. |
A requirement when using this seems to be to bracket the constraint with two translation waypoints, so the heading has time to transition between a point-to region and a pose waypoint after it. Using a sufficiently large heading tolerance is also important. Seems to work fine though, once you have those two things. |
#381
along with SleipnirGroup/TrajoptLib#140