-
Notifications
You must be signed in to change notification settings - Fork 18
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
Recursive remapping rules when roslaunching #104
Comments
While composing the teleop service, I tried to start android teleop app with "android/virtual_joystick/cmd_vel" to "/robot_teleop/cmd_vel" remapping rule. However, it didn't remap and still "android/virtual_joystick/cmd_vel" was provided. (written in rapp launch file) (passed as /start_app arguement) It ignored the remap rule which is passed as /start_app arguement and only applied first one. |
This is node remapping configuration [u'teleop_velocity_smoother/raw_cmd_vel', u'android/virtual_joystick/cmd_vel'],[u'teleop_velocity_smoother/smooth_cmd_vel', u'/cmd_vel_mux/input/teleop'], |
It seems like roslaunch does not handle the chained remapping rule. So there should be a logic to handle chained remapping rule in rapp.py To be clear, need a logic to handle A -> B -> C ---------> A -> C |
Note that the patch does not find root of the chain. Also triple chained topic would not get resolved. It requires smarter solution. |
Just recursing the function should do the trick no? |
recursive function would work with proper terminate condition. |
have not seen this issue more than 6 month. reopen if necessary. |
The logic problem is still there right? |
@jihoonl bump |
https://github.com/robotics-in-concert/rocon_app_platform/blob/develop/rocon_app_manager/src/rocon_app_manager/rapp.py#L168 should have resolved most of chain remapping problems. The corner cases like chain of chain of chain of chains aren't tested though. |
detail will come soon
The text was updated successfully, but these errors were encountered: