<div dir="ltr">Same happen again some days ago, with a new driver for DepthSense DS325 3D Camera.<div><br></div><div>Maybe we need some short of index of packages organized by category... no idea if something like this exists<br><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-06 14:56 GMT+02:00 Mike Purvis via ros-users <span dir="ltr"><<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Agree, but I think teleop and muxers in particular are a bit of a special case. They're so easy to write, and are a decent learning opportunity, so a lot of them get created by novices in the learning process, and then unwittingly made available as "universal" or "generic".<div><br></div><div>If you're integrating a robot and need either of these services, I encourage you to check out the <a href="https://github.com/ros-teleop" target="_blank">ros-teleop org on github</a>.</div><div><br></div><div>Even within the org, there's slight repetition, but the basic idea is that joy_teleop and key_teleop are python-implemented and very flexible, able to publish <i>any</i> message based on configuration from a yaml file, whereas teleop_twist_joy is specifically for publishing twist messages, and is C++ implemented, intended to be able to easily compile into a larger "base robot" node.</div><div><br></div><div>The twist_mux package does what it says on the tin, and is similarly easy to embed into another process.</div><div><br></div><div>M.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 5 April 2015 at 22:48, Daniel Stonier via ros-users <span dir="ltr"><<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><br></div>Seems to be rather alot of parallelisation happening these days. <div><br></div><div>I understand that it takes time to collaborate and that natural selection from multiple implementations are also a way of evolving the code available in our robotic community, but I do believe at least some preliminary discussion and collaboration on software that 90% fits can often get you that last 10% much faster than evolving it entirely yourself. It also rounds out an implementation to be more satisfactory for everyone. Another problem everpresent with ROS software is maintenance - n implementations are of no use long term if maintainers can't keep up with all that they try to maintain.</div><div><br></div><div>I'd like to encourage people to first look to see what is there, see if something is a 90% fit, discuss and then iterate using the usual fork/pull request cycle where possible. <br><div class="gmail_extra"><br></div><div class="gmail_extra">Daniel.</div><span><div class="gmail_extra"><br><div class="gmail_quote">On 6 April 2015 at 09:27, Jihoon via ros-users <span dir="ltr"><<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
FYI,<br>
<br>
There has also been another twist mux.
<a href="http://wiki.ros.org/yocs_cmd_vel_mux" target="_blank">http://wiki.ros.org/yocs_cmd_vel_mux</a><br>
<br>
Cheers,<br>
Jihoon<div><div><br>
<br>
<br>
<br>
<div>On 2015년 04월 06일 09:19, Enrique
Fernández Perdomo via ros-users wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div dir="ltr">Hello everyone,
<div><br>
</div>
<div>I've recently and finally added some documentation for the
twist_mux package; although it still can be improved. This
package allows to multiplex geometry_msgs::Twist messages.</div>
<div><br>
</div>
<div><a href="http://wiki.ros.org/twist_mux" target="_blank">http://wiki.ros.org/twist_mux</a><br>
</div>
<div><br>
</div>
<div>Please, don't hesitate to contact me for any doubt or
suggestion.</div>
<div>Note that I've recently updated my e-mail as maintainer,
and here I'm using my personal one. Feel free to reach me
which any of them.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Enrique</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div></blockquote></div></blockquote></div><div><div dir="ltr"><div><div><a href="http://rnd.yujinrobot.com/" target="_blank"><br></a><br></div></div></div></div>
</div></span></div></div>
<br></div></div><span class="">_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@lists.ros.org" target="_blank">ros-users@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br></span></blockquote></div><br></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div>