ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

There is already a geometry_visualization stack, so I think it's mainly a matter of moving any remaining visualizers out of tf into there, which is not too difficult (mainly documentation that needs to be fixed). Geometry will likely already be going into a massive rework to catkinize it in Groovy, so I imagine someone willing to help expedite the move (e.g. finding references to the viewer that need to be fixed) would be beneficial.

I'm not sure what is the motivation behind:

"Of course I could file a ticket for the specific problem with geometry/tf but it seems to me that this issue is something that occurs in many of the core stacks/packages."

We focused on cleaning up all the issues that we spotted back in Diamondback/Electric. Some areas may have been missed. Unless you can name more examples, I don't see why filing a ticket/patch is the wrong approach here. With Fuerte, we're at the point where ROS dependencies are becoming very granular.