-
Notifications
You must be signed in to change notification settings - Fork 100
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
Problem by running the code #4
Comments
Hi Xiangming Regards |
Hi Ayush, thank you for explanation! I have found that, in your cmakelist you use find_package{} for "Octomap" two times. One for a stand-alone octomap, one for octomap in ROS. If I want to publish a Octomap using octomap-server, with one should I use? One more question, if I just want to set start point manually, shall I just ignore this odometry topic and subscribe another topic which publish some specific point? Thank you! Sorry for so much questions, I'm really new to this area. best regards |
Hi Xiangming You should use octomap_server which will run as a standalone node subscribing to your pointcloud data and will publish the octomap. You will find the instructions here You can replace the odometry subscriber by the message type you prefer. It should just contain the pose information of your drone. It can also be similar to the goal point subscriber. If you have any further questions, I would be glad to answer them. Ayush |
Hi Ayush Thanks for your reply. So far your code works good with a already existed Octomap. Have you ever tried ompl.app? It is a GUI that can loads 3D environments and robots. Is that possible for Ompl do the same things? Xiangming |
@XiangmingHao |
Hi Ayushgaud,
thank you for your awesome work. I had some problem by running the code. The catkin_make is successful. When I use "rosrun ...." to start the planning there is only Ompl-version showed in the terminal.
I have read the issue. But I still can't figure out how to run the code properly. Can you tell me what should I do to make it works? Thank you so much!
best regards
Xiangming
The text was updated successfully, but these errors were encountered: