You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I try to track some conjugate complex poles of a system estimation. In this case the real part would be the X-Axis and the imaginary part the Y-Axis.
I publish the numerical data on a own ros msg as seperated values in a float list.
It works ok but suddenly a warning pops up "The creation of the XY plot failed because at least two timeseries don't share the same time axis". This window pops up several times, until it continues for some time.
Since both values come in the same message I don't really understand what is going wrong.
If for some reasons some data points cannot be displayed, I would be fine with it. The modal püopup however prevents me from actively using XY-plot.
I am using Tag 1.6.5 (newer version did not compile but that is another problem)
I attached a bag file with some of my data, an xml layout and a screencast video XY_issue.zip
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
I try to track some conjugate complex poles of a system estimation. In this case the real part would be the X-Axis and the imaginary part the Y-Axis.
I publish the numerical data on a own ros msg as seperated values in a float list.
It works ok but suddenly a warning pops up "The creation of the XY plot failed because at least two timeseries don't share the same time axis". This window pops up several times, until it continues for some time.
Since both values come in the same message I don't really understand what is going wrong.
If for some reasons some data points cannot be displayed, I would be fine with it. The modal püopup however prevents me from actively using XY-plot.
I am using Tag 1.6.5 (newer version did not compile but that is another problem)
I attached a bag file with some of my data, an xml layout and a screencast video
XY_issue.zip
Thanks!
The text was updated successfully, but these errors were encountered: