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

Define triangle ordering for LEFT_FOOT SkinPart #2

Closed
traversaro opened this issue May 5, 2015 · 5 comments
Closed

Define triangle ordering for LEFT_FOOT SkinPart #2

traversaro opened this issue May 5, 2015 · 5 comments
Assignees

Comments

@traversaro
Copy link
Member

For each "SkinPart" of skin (i.e. group of triangles mounted on a link) there is a triangle ordering, that is used on the real robot for outputting taxel values on the /icub/skin/* ports.
We should properly document this triangle ordering, starting from the LEFT_FOOT patch.

Some information can be extracted from the iCubSkinGui configuration files, available in: https://github.com/robotology/icub-main/tree/master/app/skinGui and the iCubSkinGui source code, available in https://github.com/robotology/icub-main/tree/master/src/tools/iCubSkinGui-qt/plugin .

@traversaro
Copy link
Member Author

@alecive any advice for @prashanthr05 ?

@traversaro traversaro changed the title Define triangle ordering for LEFT_FOOT patch Define triangle ordering for LEFT_FOOT SkinPart May 5, 2015
@alecive
Copy link

alecive commented May 11, 2015

Sorry I read the notification only now. What are you exactly trying to get?

@traversaro
Copy link
Member Author

The mapping between the triangles in the skin patch and the order of the taxels as published in the /icub/skin/left_foot port.

@alecive
Copy link

alecive commented May 11, 2015

As far as I know, there is no mainstream methodology for this. @ale-git should have more information, though (keep me updated :) ).

@traversaro
Copy link
Member Author

traversaro commented Jul 11, 2018

Issue moved to robotology/icub-models-generator#98 .

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

3 participants