Closed alecive closed 9 years ago
Update: I have looked at the code. The module seems too tight to a specific IK task to be easily extended in order to solve any chain. So the --type everything
seems unfeasible in the short term, and --type both*
as well.
@matejhof regarding the yFatals, It happens when the ID of the taxel that has been touched does not correspond to a proper calibrated taxel (e.g. the fingertip). In that situation, the normal direction is [0,0,0] and the software is not able to create a frame of reference around the taxel any more.
This commit 4f45109a79b729ee83f4dedd008caa0ddd426467 from https://github.com/robotology/icub-main fixed the RHtoL
problem.
The branch https://github.com/alecive/periPersonalSpace/tree/test/doubleTouchWithAnyBodyPart Sort of fixed everything. There still seems to be an issue with the LtoR
task (from left forearm to right arm, which does not seem to be working at all).
My idea was to merge the branch, close this issue and eventually open anotehr issue with this problem alone.
Two issues arose during some testing:
--type
option does not seem to work properly, expecially when usingboth*
arguments. Eventually, it would be nice to add a--type all
option, in which any movement is available to the user.--type LHtoR
does the movement (albeit unsuccessfully apparently), but it goes inyFatal
right afterwards--type RHtoL
seems to go toward a wrong orientation