Commit 7ec76bff7f0603920aed1e70b13e93b2630ec307
1 parent
cb8b74f2
Exists in
master
main tidy up
change to clock schedule from a constant to unlimited seems to make multiple plots less stuttery and axes update more smoothly. Obviously at expense of higher cpu usage. less apparent with only 1 plot. Probably to do with how pyglet deals with display buffers
Showing
1 changed file
with
2 additions
and
6 deletions
Show diff stats
robots/little_john/telemetry/code/monitor/version1/main.py
| ... | ... | @@ -7,16 +7,11 @@ |
| 7 | 7 | |
| 8 | 8 | # This code is incomplete, and is missing core features |
| 9 | 9 | |
| 10 | -# import math | |
| 11 | 10 | import time |
| 12 | -# import serial | |
| 13 | - | |
| 14 | 11 | import pyglet |
| 15 | -# import numpy | |
| 16 | 12 | import os |
| 17 | 13 | import platform |
| 18 | 14 | import sys |
| 19 | -# import easygui | |
| 20 | 15 | import logging |
| 21 | 16 | |
| 22 | 17 | from serialselect import selectserial |
| ... | ... | @@ -67,6 +62,7 @@ def shrubbery(ni): |
| 67 | 62 | # Pyglet looks after the main event loop, |
| 68 | 63 | # but this ensures that data keeps being read in |
| 69 | 64 | |
| 70 | -pyglet.clock.schedule_interval(shrubbery, 0.1) | |
| 65 | +#pyglet.clock.schedule_interval(shrubbery, 0.1) | |
| 66 | +pyglet.clock.schedule(shrubbery) | |
| 71 | 67 | |
| 72 | 68 | pyglet.app.run() | ... | ... |