-
Notifications
You must be signed in to change notification settings - Fork 131
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
Failed to call update polygon service #41
Comments
Thanks for taking it for a spin - frontier_exploration in melodic has undergone a pretty significant refactor, and I'm still shuffling things around. |
@paulbovbel - thanks for providing/maintaining this package. Do you have an ETC for when the reshuffle will be done? |
Not really. Can you link me to a fork of something of |
Sorry for the long delay, @paulbovbel. (I got called off on something else for a couple of weeks.) I started looking into this again, today. My original costmap_exploration.yaml file looked like this:
And my costmap_common.yaml looked like this:
I found that the
That brings us to today, when I did some more digging. From the digging, I updated the file to this:
With this latest update, I think that all my layers (and parameters) are named properly. It succesfully gets past the line that was triggering the "Failed to call update polygon service" error. So, in short, problem solved! (It now gets stuck on something else...but I'll ask about that in a separate issue.) |
@jaredjohansen regarding:
What change did you make to the nodes in exploration.launch to fit the new naming/organization scheme? I am trying to do the same thing, but new to ROS and simply renaming the nodes in the launch file did not work for me. (I may have the new names wrong as well- I assume explore_server is now exploration_server and explore_client is now plugin_client, is that correct?) Perhaps you could post your file, exploration.launch? |
Nevermind, figured it out from looking at the frontier_exploration package's exploration.launch. In case anyone else has the same question, the nodes' packages have to be changed as well. These are the relevant lines in husky_navigation/launch/exploration.launch, modified to work with the latest frontier_exploration package: (And of course you also have to make the changes to costmap_exploration.yaml mentioned above by @jaredjohansen ) |
I am getting the following error when attempting to use frontier_exploration:
A few notes about my environment:
After making these changes, I am able to get my workspace to compile. I am able to run the exploration_demo.launch without any errors. I am able to select points in rviz without any errors. I am able to complete the polygon without any errors. I am able to select a point to initialize the exploration without any errors. But when it tries to communicate with the polygon service, things die.
The mechanisms for how it uses the service and communicates with the other nodes is a bit beyond my initial attempts to understand. Any help to understand (or to fix any bugs that may be involved) would be appreciated!
The text was updated successfully, but these errors were encountered: