Node explore cannot be found after launching explore.launch about m-explore HOT 20 CLOSED

This probably means you don't have this package installed correctly.

To resolve this I need more information.

• How did you installed explore_lite?
• package version
• which ros distribution you are using

It might be also problem with your specific installation of ROS. Do other packages work correctly?

from m-explore.

I have installed explore_lite with:
sudo apt install ros-kinetic-multirobot-map-merge ros-kinetic-explore-lite
I'm not sure which package version I have cloned the master
And I'm using Kinetic.

I'm not entirely sure what you mean with other packages?

from m-explore.

I don't understand. Have you installed your package from repository, or have you cloned from master and compiled it yourself?

Does other packages works as expected? For example for explore_lite you need to have configured move_base. Does move_base work? (Can you navigate your robot with move_base?)

from m-explore.

We are now trying to configure it the way it's mentioned in the quick-start.txt, I will let you know.

from m-explore.

That file is outdated. I should probably remove that.

from m-explore.

Can you provide me a recent quickstart for ROS Kinetic for Turtlebot2

from m-explore.

I have removed the mentioned file. Thanks for pointing that out. I have forgotten about that file.

I think there is no quickstart no longer needed. Package is now properly released in ROS, so installation is very easy. quickstart.txt was just about installation of early development version of this package.

I can reproduce the error you have. Thanks for reporting. I will fix it soon.

from m-explore.

As a workaround you can uninstall packages via apt and clone this repo to your workspace. From workspace everything works as expected.

from m-explore.

What I did was:

• I uninstalled the packages
• removed the repo from source
• cleaned the build
• recloned
• catkin_make

And from here we are stuck because we are not sure how to launch the package because nothing seems to be working

from m-explore.

After compiling you should be able to run explore.launch via roslaunch. You might need to source again setup.bash from your workspace for completion to work again.

from m-explore.

Okay we did a source and we have successfully been able to run explore_lite explore.launch, after doing a minimal launch on the turtlebot. What are the next steps to make the robot mapping autonomously? Thank you in advance

from m-explore.

you need to have correctly configured move_base. You should be able to navigate the robot with move_base manually. Then explore.launch should work for your more or less out of the box (I was also using that launch file with turtlebot).

Of course, you might need to change some topic names and tf frames names depending on your configuration. Check the wiki how to configure the parameters.

from m-explore.

Okay, we will try that. Do you perhaps have the launchfile for a Turtlebot?

from m-explore.

the launchfile shipped with explore_lite is the same launchfile that I have used for experiments.

from m-explore.

Okay, we have an issue with configuring the move_base. Our move_base package is empty except for a package.xml file.

from m-explore.

ok, come back when you get your move_base up and running and let me if you have any further issues with explore_lite.

Thanks again for reporting this issue, I will fix it in the next package release, so the package from ROS repository works out of the box.

from m-explore.

After configuring move_base, we have been able to successfully launch explore.launch. It works very well, but some parameters need to be tweaked in order to make it run more efficient.

from m-explore.

Great. Unfortunately filtering of small frontiers is now hard-coded because of #7 (but it is fixed in master, so it should not affect you). You can still tune weights of frontiers (potential_scale, gain_scale), which affects the exploration considerably.

If you have some other issues or suggestions for improvements let me know.

from m-explore.

Thanks. The only issue we encountered since then is mapping small and crowded rooms (with or without moving obstacles). It constantly keeps trying to recover and eventually never accomplishes to map the room and therefor never moves out of a specific room (atleast the smaller ones). If finetuning it doesnt't help we will be considering to try and fix this.

from m-explore.

Oh yeah. That is a general problem with move_base. Exploring can't do much about it. Maybe exploring should avoid such spaces, but I'm not sure if that is viable.

Tweaking parameters of move_base usually helps .I had some success with big inflation on global map (to keep it from walls) an small inflation in local map (to leave the planner as much space as possible).

from m-explore.