subt.drone: draw control inputs #693
Conversation
| #height = [(a[1], a[1] - a[2], a[1] + a[3], a[4]) for a in self.debug_arr] | ||
| #line_obj = plt.plot(t, height, '-o', linewidth=2) | ||
| #plt.legend(iter(line_obj), ('altitude', 'alt - bottom', 'alt + top', 'pose3D.z')) | ||
| #plt.xlabel('time (s)') |
There was a problem hiding this comment.
label would be nice (from the code I see that it is bottom_scan count. Ideal would be simulated time
There was a problem hiding this comment.
I am not that proficient with matplotlib and was in kind of a hurry.
| a = [A for count, H, E, A in self.debug_arr2] | ||
| e = [E for count, H, E, A in self.debug_arr2] | ||
| h = [H for count, H, E, A in self.debug_arr2] | ||
| plt.plot(x, a) | ||
| plt.plot(x, e) | ||
| plt.plot(x, h) | ||
| plt.xlabel('sim time (s)') |
There was a problem hiding this comment.
It's approximation since the messages can be dropped out on the ROS side but I guess that does not really matter for this much.
There was a problem hiding this comment.
Yes, it is misleading (the absolute time) - it can give us hint about period of the oscillations but as I was wondering why the mode changes at time 658s then the answer is that it is +/-100 because of initial simulation time offset. When things calms down I would add input also sim_time_sec and compensate for it.
There was a problem hiding this comment.
I am not sure if that is the best solution. I am thinking about a bigger change that would involve adding "time" to a lot of messages we are sending in osgar which would say at which point of time was the data relevant (ie. for a sensor - when was the data measured etc).
|
Lets merge this and continue with #698 |
| @@ -72,6 +72,7 @@ def main(): | |||
| format='%(name)-12s %(levelname)-8s %(message)s', | |||
| #datefmt='%Y-%m-%d %H:%M', | |||
| ) | |||
| logging.getLogger("matplotlib").setLevel(logging.INFO) | |||
There was a problem hiding this comment.
what happens if there is not logger for matplotlib?
No description provided.