Skip to content
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

Estimated collision map publishing #10

Open
carlosjoserg opened this issue Feb 17, 2016 · 1 comment
Open

Estimated collision map publishing #10

carlosjoserg opened this issue Feb 17, 2016 · 1 comment

Comments

@carlosjoserg
Copy link
Member

There was really a trouble with the update of the collision map coming from the estimated point cloud and passing through the octomap. I thought of alternating clear point cloud clear octomap routines, but I think it makes more sense to build the collision map within the node and publish from there directly in the processing frame. This would allow to move/plan for the two arms simultaneously to facilitate the planning, otherwise it is a nightmare.

@Tabjones, would be great if you can take a look into the octomap library to publish directly the collision map from the node (in the processing frame), while I continue with the paper. What do you think?

@Tabjones
Copy link
Contributor

@carlosjoserg, ok i dont know how fast this can be, since pcl has an octomap module, but i've have no idea if that is compliant with ros octomap, i'll investigate both and decide what's the best way of doing it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants