MPV2.5: refactor in order to remove the assumption of the single kin chain #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR I refactored the code in order to remove the assumption of the single kin chain.
In particular, I populate the idyntree model in two separate steps.
First, the plugin iterates over all the parts, retrieves all the mass and kin properties of the links, and adds links to the idyntree model.
For what concern the joints instead, at this step, I am assuming that the first part that owns a specific axis is the parent link, and the second one will be the child link.
This is an approximation due to the fact right now I couldn't ask for this information from Creo.
After this iteration over all parts, I start adding the joints using the informations retrieved the previous step and voila, for the case of 1 kin chain (MVP2) it works flawlessly:
cc @traversaro @pattacini @mfussi66 @fiorisi