-
Notifications
You must be signed in to change notification settings - Fork 39
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
C++ refactoring of Contact #204
Conversation
I think it is safe to do so at this point? We have a big warning in the README exactly for that. |
If @paolo-viceconte and @diegoferigo agree we can proceed in this way
This will unblock @prashanthr05 from porting the estimator in python |
Yes you can proceed in this way. No problem if some code here and there breaks, it seems a trivial change. |
I agree as well. |
Related issue: #162 |
I suppose we could move the data structures
to |
I also created the bindings for the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks @GiulioRomualdi !!
This is the C++ refactoring of
Contact
class. I'm not really sure about this solution for the following reasons:Right now we are exposing

Contacts
andContact
. The former is in https://github.com/dic-iit/bipedal-locomotion-framework/tree/master/src/Contacts while the latter is in https://github.com/dic-iit/bipedal-locomotion-framework/tree/master/src/Planners. This is confusing 😭Shall we move also the
ContactLists
etc inContacts
?I do not know how to handle the transition in the bindings for the following reasons
Contact
is just a typedef ofPlannedContact
,Contact
class is a base class that we should wrap in python so this will destroy the retro compatibilitycc @prashanthr05 @traversaro @S-Dafarra and @diegoferigo
This will close #162