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

TOPIC TOOLS: add initial_topic param #1199

Merged
merged 2 commits into from
Oct 23, 2017

Conversation

kev-the-dev
Copy link
Contributor

On a ROS-based robot my lab works on, we use topic_tools/mux to manage potential wrenches from the autonomous controller, an xbox controller, and an rf based controller. We need the option to, on startup, have none of these inputs selected (for safety), so that we have to explicitly select one before anything will move. To do this we mux, we needed to use a dummy topic.

This adds an optional private parameter to mux, "initial_topic" which will set the input topic the mux will use on startup. Additionally, it can be set to "__none" for no initial topic. If the param is not set, the default behavior or choosing the first input in the arguments is used.

@dirk-thomas
Copy link
Member

This looks like a nice enhancements. Can you please add a test covering the new functionality.

@kev-the-dev
Copy link
Contributor Author

Tests added for __none and non-default case

@kev-the-dev
Copy link
Contributor Author

On a side note, it seems like a lot of the tests for topic_tools were disabled... do they still need to be? I think they will pass

  ## Latched test disabled until underlying issue in roscpp is resolved,
  ## #3385, #3434.
  #rosbuild_add_rostest(test/relay_latched.test)
  #rosbuild_add_rostest(test/mux.test)
  #rosbuild_add_rostest(test/switch_mux.test)
  #rosbuild_add_rostest(test/switch_mux_leading_slash.test)
  #rosbuild_add_rostest(test/switch_mux_none.test)
  #rosbuild_add_rostest(test/mux_add.test)

@dirk-thomas
Copy link
Member

If they pass it would indeed be great to reenable them.

@dirk-thomas
Copy link
Member

Thank you for the improvement. Can you please mention the new feature on the wiki page and link to the change here.

@dirk-thomas dirk-thomas merged commit 4603efc into ros:lunar-devel Oct 23, 2017
@kev-the-dev
Copy link
Contributor Author

Wiki updated.

What is the process to get this on kinetic/other versions as well? Send separate PR's for each branch?

@dirk-thomas
Copy link
Member

A while after a Lunar release all changes will be considered for backporting into Kinetic. I will then create a "big" PR which backports all the changes desired. That usually includes fixes and sometimes features which have a low chance of regressions (which this one would probably fall into).

Into Indigo usually only significant bug fixes are being backported.

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

Successfully merging this pull request may close these issues.

2 participants