-
Notifications
You must be signed in to change notification settings - Fork 132
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
rqt_plot: cannot plot array elements - ROS Indigo #261
Comments
@trainman419 Can you please take a look at this since it might be related to the recent changes? |
I'll take a look at this. |
I'm able to reproduce this error message on the version released into Hydro, but it doesn't prevent me from plotting array elements. In particular, I see this error when I put in the topic name and the name of the array field without brackets, but it doesn't cause rqt_plot to crash and doesn't prevent me from entering and plotting the array elements individually. @decabyte is that causing rqt_plot to crash or preventing you from plotting array elements in Indigo? |
Hi @trainman419 this is not fixing the problem and it is not producing any error on the console. I'm still unable to plot a specific element from the array like: Cheers, |
Hello everyone. The commit that @trainman419 proposed fixes the error, but it does not allow to plot individual elements of the array. The problem is that the function get_topic_type cannot handle the (..)/data[1] part of the topic_name and returns topic type = None. In few seconds I'll create a pull request with a proposed solution to that problem. |
Hi @jczarnowski the behaviour you described is correct and your fix is solving the problem on Indigo. 👍 I'm using it together with the previous fix of @trainman419. |
I've confirmed that my fix works on Hydro, but not on Indigo. Odd. |
The other half of this bug (on Indigo) is actually a bug in rostopic: ros/ros_comm#480 |
I'm able to reproduce this with the |
Handle variable-sized arrays. Fixes #261
Whoops. Re-opening. The pull request didn't fix all the issues this issue brought up. |
Which part of this ticket is still pending? |
Re-reading I guess just the ros_comm bug. Since that is ticketed separately on ros_comm then perhaps it makes sense to close this? |
The |
Well then! |
Hi guys, So the problem has not been solved yet? |
@RoboEvangelist The packages have not been released yet since the patches have been committed. Are you actually using a from source build version of a current checkout of |
I'm using the ROS downloaded from the website, not the repository. So I guess my version is not as updated as the current github version. Is there an easy way to intergrate the patch with my installed version of ROS withouth messing things up or having to start from scratch? |
The easiest way is to clone these repos into your workspace and build them from source together with your other packages. You could also patch the files under /opt/ros/indigo directly with the multiple patches referenced from this ticket but that would be the more nasty approach. |
Bump. This showed up on ROS Answers today: http://answers.ros.org/question/190686/rqt_plot-issues-in-indigo/ @ablasdel is it a good time to do a release of rqt_common_plugins, so that this fix makes its way into the world? |
This has already been done 2 days ago: ros/rosdistro#5315 And the fixed version is waiting in shadow-fixed for a sync: http://www.ros.org/debbuild/indigo.html?q=rqt_common_plugins |
The problem is solved. I just did a sudo upgrade on ubuntu, and now I can plot arrays on rqt_plot. Yay!!! My boss is gonna be happy. Thanks |
Hi there,
after upgrading from the recent Indigo Beta to the latest version I've started to have problem with
rqt_plot
.When plotting a specific element of an array field I'm getting this traceback just after typing the field name (ie.
/<topic_name>/values[1]
) in the gui:The ROS message I'm trying to plot is like this:
Previously with the version 0.3.6 of the package I was able to plot array elements correctly.
The text was updated successfully, but these errors were encountered: