-
Notifications
You must be signed in to change notification settings - Fork 14
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
Uniformize usage of integrators API #378
Conversation
5ce5b58
to
cd884ca
Compare
cd884ca
to
911648f
Compare
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.
I strongly agree with these changes, thank you!
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.
Thanks @flferretti !! The changes introduced in the PR seems good to me, and also the math used in the semi-implicit to get the derivative of the origin of the base frame (but @CarlottaSartore if you have time double check it please).
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.
LGTM but also in this case, berfore mergign I would:
- Check if the robot walks in comodo with relaxed rigid (it happened in the past when changing integrator that the tests passed but the robot was not walking)
- Check the time performance
Thanks for your review @CarlottaSartore! Regarding:
Only the interface has been changed. There are no significant changes to the integration method apart from using this formulation: Instead of explicitly converting to mixed representation. This approach has already been verified as it is the one used by the RK4 integrator.
I removed an extra call to the system dynamics for the RK4 as it wasn't used. Since the default contact model has not been changed. Do you think it is really worth at this stage or can we address this in future PRs? |
I would double-check with Comodo, to be sure that we have replicated it correctly, for what concerns the time analysis I think you can do one for both this and #360, (merging in a unique PR) the same olds for comodo check ! Up to you! |
d6bdaf6
to
7e6f942
Compare
The changes correctly run on CoMoDo. Merging |
Cool, I assume then that the time performance check will be done in #360, it would have been better to do it in a unique PR so that we are more careful in merging in main but since we are doing #380 this kind of issues will be automatically correctly handled. |
The performance checks have already been done. The results didn't present any significant difference |
Cool on which machine ? It would be better to report here the performance output as done here https://github.com/ami-iit/component_darwin/issues/59#issuecomment-2639530952 for completeness |
Intel Ultra 7 155H. The tests were performed using comodo walking task as a reference.
You're right, I'll keep working on #380, so we don't have to do this manually |
This PR changes the API usage for integrators by ensuring consistent parameter names and removing redundant calculations. This improves code clarity and maintainability.
📚 Documentation preview 📚: https://jaxsim--378.org.readthedocs.build//378/