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

python binding - extractKinetics #16

Open
aaa34169 opened this issue Sep 19, 2016 · 2 comments
Open

python binding - extractKinetics #16

aaa34169 opened this issue Sep 19, 2016 · 2 comments
Milestone

Comments

@aaa34169
Copy link

No warnings come up if extract_kinetics run without gravity vectors and mass within subject properties

@Alzathar
Copy link
Member

The function ma::body::extract_joint_kinetics only looks for segment poses and joint forces and moments for each ma::body::DynamicsDescriptor found. The computation of segments and joint forces and moments are done within the function ma::body::reconstruct. Thus, no warning are displayed because no information was found.

The problem might be deeper than the display of a warning. The way to activate the inverse dynamics is not simple (set the gravity vector). The code might be refactored. For example, a new class ma::LaboratorySettings is in development to set the gravity direction and magnitude. This class might manage the need or not to compute the inverse dynamics. A specific option in this class might trigger the computation of the inverse dynamics. Thus, when the function ma::body::extract_joint_kinetics is used, the inverse dynamics computation set to truebut no information was found, a warning could be displayed.

Would it be a better way?

@aaa34169
Copy link
Author

I like the class ma::LaboratorySettings and the proposed process
I thin ma::LaboratorySettings s the best place for stating the gravity vector.

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

No branches or pull requests

2 participants