Skip to content
This repository has been archived by the owner on Apr 6, 2020. It is now read-only.

[WIP] Add preliminary support in wholeBodyDynamicsDevice to use BerdySparseMAPSolver #240

Closed
wants to merge 5 commits into from

Conversation

traversaro
Copy link
Contributor

@traversaro traversaro commented Sep 4, 2017

Depends on iDynTree's branch floatingBerdyPlusPlus .

@traversaro traversaro changed the title [ Add preliminary support in wholeBodyDynamicsDevice to use BerdySparseMAPSolver [WIP] Add preliminary support in wholeBodyDynamicsDevice to use BerdySparseMAPSolver Sep 4, 2017
@traversaro
Copy link
Contributor Author

I am afraid that for this we need to add a devel branch in codyco-modules .

linearAccelerometer.setParentLink(model.getFrameName(model.getFrameLink(imuFrameIndex)));
linearAccelerometer.setLinkSensorTransform(model.getFrameTransform(imuFrameIndex));
linearAccelerometer.updateIndices(model);
ok = ok && sensorsActuallyUsedInEstimation.addSensor(linearAccelerometer);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

addSensor returns an int.

angularAccelerometer.setParentLink(model.getFrameName(model.getFrameLink(imuFrameIndex)));
angularAccelerometer.setLinkSensorTransform(model.getFrameTransform(imuFrameIndex));
angularAccelerometer.updateIndices(model);
ok = ok && sensorsActuallyUsedInEstimation.addSensor(angularAccelerometer);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@traversaro
Copy link
Contributor Author

This PR (adding Berdy-like estimation support to the WBD device that runs on the robot) adds a lot of complexity to wbd, with little added value.
Unless someone is willing to work on this, I think we can decline it and just recover it when somebody will want to work on this.
cc @DanielePucci

@DanielePucci
Copy link
Collaborator

@traversaro
Completely agree. In the long run, probably @prashanthr05 may take upon this, according to his scheduled activities

@traversaro
Copy link
Contributor Author

Ok. Closing the PR, as GitHub remembers, so if we ever need this code, we can just go back to this PR and recover it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants