-
Notifications
You must be signed in to change notification settings - Fork 294
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
ps3joy - Make '--continuous-output' the default choice in Hydro #56
Comments
@jbohren Bump. |
Yeah, I'm thinking about it. For hydro we could warn people who aren't using --continuous output, and then make it the default in Igloo, how does that sound? |
I'm not aware that it will break any functionality on any robot. Most/all of the teleop nodes rely on unstable frequencies. They should have timeouts (not affected by this change) AND also have to handle that the controller sends very fast updates while moving an axis, for example. We aren't changing the maximum output frequency, just the average. On the other hand, not enabling this makes people look like goobers when they have to "wiggle" the controller to get say.... the PR2 to move. There's always topic_tools throttle if users need a lower rate. |
👍 for setting to continuous ASAP. :) |
So we should do this for Indigo, and I think the joy node should also have a continuous output mode. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
This zombie issue was just resurrected. It looks like quite a few people are in favor of this. Since many ROS versions have passed since this was first considered, what are the thoughts on notifying users for Lunar and above about this change and leaving Kinetic and below with the current functionality? I'd specifically like to hear from @chadrockey and @jbohren if they're still around and/or have opinions on this issue. Would also be good to hear from @dirk-thomas or @tfoote on their thoughts regarding affects to the community. |
Here's a 👍 to raising the dead on this zombie issue. |
In testing I've done with ROS Melodic, it doesn't seem that the --continuous-output flag works. For reference, we are launching via systemd like this: |
I've been using --continuous-output a lot here at WG and I've found no problems with it. It's much better overall and prevents users doing odd things like "rocking" the ps3 controllers while trying to drive PR2.
I propose that we either make --continuous-output the only option, or make it the default and add a --sparse-output option for backwards compatibility.
@jbohren Any thoughts?
The text was updated successfully, but these errors were encountered: