haidai's profile - activity

Does listing it on ros.org impact how it'll be released?

Does listing it on ros.org impact how it'll be released?

I have a stack that's fairly well-behaved with the standard ros tools and such (rosmake cleanly, etc) and listed on ROS.org so it's known by the ROS indexer. How do I get it from this stage to where someone else can do an 'apt-get install PACKAGE-NAME' at the command-line?

Package in question: http://www.ros.org/wiki/rcommander_core Repository: https://code.google.com/p/gt-ros-pkg.rcommander-core/

Our lab hosts code with Google Code and was planing on releasing each stack as a separate repository. Unfortunately, this scheme also generates very ugly repostority URLs as repository names aren't allowed to have underscores (which I've replaced with dashes) but this isn't a preferred ROS naming convention as I understand it. Also, the repository name is also prepended with Google Code project name: https://code.google.com/p/gt-ros-pkg.my-stack-name/

My question is what happens when a repository with this name gets indexed and linked to a page on the wiki? Is there a way to turn "gt-ros-pkg.my-stack-name" to something more friendly like "my_stack_name"?

The outlet detection code is only tested with the default template on outlets that look like the ones used here: http://www.ros.org/wiki/pr2_plugs. Does your outlet look the same? The detector only looks at the position of the holes, not the outlet cover.

Did you look at the output of rxconsole to see if there's any more feedback? Could you describe the behavior of the robot in more detail, that might give a better understanding of where in the state machine the robot got (did the projector turn on, did the robot align with the wall, did the robot succeed in finding the outlet from far away, ...).

I am trying to get our PR2 to use the autonomous plugging action, and was able to get pr2_plugs_actions to run (using app_plugin.py) but the /vision_outlet_detection node would consistenty fail to detect our wall outlets. I looked at textured stereo images from Rviz and can verify that the outlet is in the images that the robot receives. Is there anyway to look into what's going on with the detector more closely to see what's happening with it? I tried changing the template from green_2x1white to white2x1hall, and fake_wall_2x1white_plug but none of these seems to work.

Has anyone else run into this problem? We are running Electric on Ubuntu Lucid and our outlet is a 2x1 with the third prong on the bottom (shadowy side of outlet).