Closed raffaelemazziotti closed 3 years ago
this is probably due to UI updates, primarily the graph plotting which is more expensive as more samples are to plot. same goes for tabular data updates, even if only marginally compared to the plot.
I'll add checkboxes to disable auto-updates to UI for long run experiments; this should alleviate a lot the problem. However, the problem might still occur due to other uncontrollable factors (e.g. CPU frequency scaling, system load).
For prerecorded (non-webcam) inputs, we should add non-realtime processing to ensure reproducibility, see #15
framerate seems to drop dramatically during the time. If the live plot is checked showing the entire trace, fps constantly drop to 4 or 5 fps (or even more) in both firefox and chrome. Without a live plot, the effects are milder even though constant.