Is it possible to configure environment server with empty collision map?

asked 2012-05-14 05:44:11 -0600

3907 ●28 ●45 ●71

updated 2012-05-15 06:21:45 -0600

I have a robot with an arm_navigation stack configured to use a collision map, and it works fine. However, if arm_navigation is started with no visible environment obstacles, the environment server will not complete its configuration sequence and disallow planning motions. This is the typical output:

Waiting for environment server planning scene registration service /register_planning_scene

Publishing an empty point cloud does not seem to make the environment server happy, so is there a way about this use case?. Currently I'm publishing a dummy cloud with a single point outside the workspace of my robot (a hack that works in the meantime).

Further details on what's going on: An environment server instance is not completely constructed because it gets stuck in a loop, which requires waking up this CollisionSpaceMonitor callback to break it.

Edit The problem statement can be generalized to saying that apparently the collision map is not updated when an empty point cloud is published. I'm using the collider node, and with an already configured environment server, the octomap cells are not updated if I go from an environment with obstacles to one without any.

TIA.

edit retag flag offensive close merge delete

Comments

While we are still waiting for a proper solution, what about starting the environment server with "use_collision_map:=false" and then restart it with "true", once a populated collision map is available?

bit-pirate ( 2012-05-17 13:39:41 -0600 )edit

The use_collision_map parameter is read only once in the constructor of the environment server, so unfortunately that won't work.

Adolfo Rodriguez T ( 2012-05-18 03:45:53 -0600 )edit

I meant, shutting down the whole environment server and then bringing it up again. In this way the use_collision_map parameter will be read again. Maybe ros::shutdown() + the restart parameter in roslaunch could do the trick.

bit-pirate ( 2012-05-23 13:27:12 -0600 )edit

You could think of doing that. It just seems a more complicated hack than the one I already have in place, which is to publish a minimal obstacle slightly outside the reach of the robot _until_ the environment server successfully initializes. Note that this is _still_ a hack, though.

Adolfo Rodriguez T ( 2012-05-23 21:26:20 -0600 )edit

Reported as Issue 5198, so it does not get lost.

Adolfo Rodriguez T ( 2012-05-31 01:50:27 -0600 )edit

add a comment

#include <ros/ros.h> #include <arm_navigation_msgs/CollisionMap.h> int main(int argc, char** argv) { ros::init(argc, argv, "empty_collision_map_publisher"); //figuring out whether robot_description has been remapped ros::NodeHandle nh; ros::Publisher pub = nh.advertise<arm_navigation_msgs::CollisionMap>("/collision_map_occ", 1, true); while(ros::ok()) { arm_navigation_msgs::CollisionMap coll; coll.header.frame_id = "odom_combined"; coll.header.stamp = ros::Time::now(); pub.publish(coll); } return 0; }

Comments

That is indeed acceptable. I've updated the relevant ticket with your answer, and a patch.

Adolfo Rodriguez T ( 2012-06-10 21:35:36 -0600 )edit

add a comment

Is it possible to configure environment server with empty collision map?

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

Is it possible to configure environment server with empty collision map? edit

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

Is it possible to configure environment server with empty collision map?