Skip to content
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

Merged
merged 16 commits into from
Apr 3, 2024
Merged

Conversation

bruingineer
Copy link
Collaborator

@bruingineer bruingineer commented Apr 2, 2024

src-tauri/Cargo.toml Outdated Show resolved Hide resolved
@calcmogul calcmogul changed the title PointAt constraint Add PointAt constraint Apr 3, 2024
@calcmogul calcmogul linked an issue Apr 3, 2024 that may be closed by this pull request
@calcmogul
Copy link
Member

calcmogul commented Apr 3, 2024

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.

@calcmogul
Copy link
Member

calcmogul commented Apr 3, 2024

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.

@calcmogul calcmogul merged commit 478751a into SleipnirGroup:main Apr 3, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Point toward/away from point" constraint
3 participants