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 the possibility to update the contact list in the swing foot trajectory planner #637

Merged
merged 3 commits into from
Mar 29, 2023

Conversation

GiulioRomualdi
Copy link
Member

With this PR it will be possible to update the contact list in the SwingFootTrajectoryPlanner.
If the contact list is not empty, we check if it is possible to update the list. Given some limitations of the framework (mainly due to the SO3 trajectory generation) for the time being, we support only the two following cases:

  • Given the current time instant, both the stored and the new contact lists must have an active contact at the same pose.
  • If the contact is not active (swing phase) the next contact must satisfy the following two hypothesis
    1. the orientation of the next contact must be the same as the orientation of the next contact in the contact list stored in the class.
    2. the impact time of the next contact must be the same as the one of the next contact in the contact list stored in the class.

⚠️ Similar to #624 advance() must be called before getting the output

@LoreMoretti you can directly use this class along with the MPC you developed 😄 (cc @traversaro)

…ectory planner.

- Avoid to reset the internal time of the SwingFootPlanner when a new ContactList is set
- Advance must be called before getOutput()
- implement `SwingFootPlanner::setTime()`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants