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 non-collocated wrench estimation in HumanWrenchProvider #309

Conversation

RiccardoGrieco
Copy link
Contributor

This PR adds the estimation of external wrenches as described in https://ieeexplore.ieee.org/abstract/document/9526592 in the HumanStateProvider device.

@RiccardoGrieco RiccardoGrieco self-assigned this Jul 18, 2022
@RiccardoGrieco
Copy link
Contributor Author

CI is failing because the required changes in iDynTree are still in the devel branch (see robotology/idyntree#991) and not yet in master.

@traversaro
Copy link
Member

CI is failing because the required changes in iDynTree are still in the devel branch (see robotology/idyntree#991) and not yet in master.

I can do a release, no problem.

@traversaro
Copy link
Member

CI is failing because the required changes in iDynTree are still in the devel branch (see robotology/idyntree#991) and not yet in master.

I can do a release, no problem.

robotology/idyntree#1005 is for the current master, after that I can merge devel in master and release 6.0.0 .

@RiccardoGrieco RiccardoGrieco force-pushed the feature/add-berdy_ext_wrench_estimation branch from 24e4cfa to 550efac Compare July 25, 2022 10:05
Copy link
Member

@traversaro traversaro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments.

Co-authored-by: Silvio Traversaro <silvio@traversaro.it>
@lrapetti
Copy link
Member

Related to the models used in this PR I have merged robotology/human-gazebo#30 and prepared a new release of human-gazebo models (robotology/human-gazebo#31)

Copy link
Member

@lrapetti lrapetti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, I have added just a minor comment you can evaluate if it makes sense to change it or not.

The only thing, I would add a comment just to recall that for the time being the rate-of-change of momentum is computed without considering link velocities and accelerations, and open a separate issue for that point.

@lrapetti
Copy link
Member

Following this PR, I would also proceed with releasing the devel code into master, what do you thing @RiccardoGrieco?

@RiccardoGrieco
Copy link
Contributor Author

RiccardoGrieco commented Sep 1, 2022

@lrapetti you can proceed with merging the PR.

Following this PR, I would also proceed with releasing the devel code into master, what do you thing @RiccardoGrieco?

I agree!

The only thing, I would add a comment just to recall that for the time being the rate-of-change of momentum is computed without considering link velocities and accelerations, and open a separate issue for that point.

Opened #312

@lrapetti
Copy link
Member

lrapetti commented Sep 2, 2022

Great, we can merge it!

@lrapetti lrapetti merged commit 163f1e4 into robotology:devel Sep 2, 2022
@lrapetti lrapetti mentioned this pull request Sep 2, 2022
@DanielePucci
Copy link
Contributor

Thank you all guys for fixing this longstanding critical situation!

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.

None yet

4 participants