-
Notifications
You must be signed in to change notification settings - Fork 81
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
Segmentation error from "solved = self.ss.solve(allowed_time)" #27
Comments
Hi, I think this indicates that there is some error in the installed ompl python binding. |
I have installed the pre-released version of ompl
|
@ubgaokk I’m experiencing the same issue. Have you found any solutions? I’d really appreciate any insights you might have. Thanks! |
@yilin404 I have got some solution: Then (this determines which ompl will be called)
It should be OK for you to run '''execute.py'''. |
@ubgaokk Thank you for your response and suggestions! I will try the method you recommended and provide feedback on the results. I really appreciate your help! |
Thank you for your solution, I also encountered the same problem when running “execute.py”, but I have a few questions after trying it. |
Hello, I would like to ask if you have solved this problem? |
When I am running
python execute.py --task_config_path example_tasks/Change_Lamp_Direction/Change_Lamp_Direction_The_robotic_arm_will_alter_the_lamps_light_direction_by_manipulating_the_lamps_head.yaml
, I got the segmentation error as following. I found the problem is coming fromCould you help me understand why? Thanks.
The text was updated successfully, but these errors were encountered: