-
Notifications
You must be signed in to change notification settings - Fork 56
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
/tmp/irtmodel-ik failuer file will become segmentation fault when I execute with roseus #138
Comments
please remove :additional-weight-list ((#<bodyset-link #Xe6e4df0 torso_lift_link ...)) from pr2-sensor-robot-2014-07-12-17-44-47-failure.l and see if this works. |
Removing surpress the segmentation fault! Thanks. |
ok, it is not end, we just find starting point ;-) the problem is so please check
|
Hmm... I couldn't understand what should I do... I did 1) at previous my comment. but what is "different solution" you meand and what to check? At this time , I replase |
when and if you remove :additional-weight-list and execute "-filufre.l" then you will see ik fail error message with different distance or it may success, because it uses different ik parameters than when euslisp generated "-failure.l" generated. [1] https://github.com/euslisp/jskeus/blob/master/irteus/irtmodel.l#L2034 |
OK. I may understand. BTW, I get some error when I did ik_setup and ik_check, so I will open new issue. |
The diff results were as below.
2.and 3. was same, so the replace didn't seem to affect. Below is Summary
Below is detail output
|
…ll links and list to fix jsk-ros-pkg/jsk_roseus#138 and fix bug in move-target or target-coords
I fixed segmentation fault from @aginika
|
@snozawa I run the code with roseus and the ik-check functions seems to work!!
|
When I try to execute kind of below code with roseus command, it become segmentation fault. Ths success one doesn't fail.
Is it because of my environment?(it failed ,though I tried in other robot environment too)
failuer sample
When I execute roseus
The text was updated successfully, but these errors were encountered: