Open Thonners opened 4 years ago
Sounds good - there is a draw_data function within visualiser, I accidentally removed the call to it from main.py when tidying up some timing functions. It's been fed with a data dictionary from vehicle. Perhaps worth rehashing this function? We can keep the data dictionary and also use it to export the data back to the driver along with the lidar
Model inputs visualisation now merged to master.
Actual driver demands visualisations (as output by GamePad) still need to be added
When using keyboard (and also when / if using autonomous control) it'll be useful to visualise the rThrottle/rBrake/aSteeringWheel demand.
Suggestion is a couple of bars for pedal demands (similar to youtube vids) where demand level is indicated by bar fill %, and a lateral scale with a moving marker for the steering?