mirror of
https://github.com/jkriege2/JKQtPlotter.git
synced 2024-12-26 18:41:40 +08:00
100 lines
6.2 KiB
Markdown
100 lines
6.2 KiB
Markdown
# Example (JKQTPlotter): Simple line-graph with live-data (speed test) {#JKQTPlotterSpeedTest}
|
|
This project (see `./examples/speed/`) creates a JKQTPlotter widget (as a new window) withs two line-graph (a sine and a cosine wave with a random disturbance). It constantly changes the data (a bit) and redraws the plot. The redraw-rate is measured and displayed at the top of the window. Also the example offers several context-menu entries to alter the plot and thus experiment with different factors that affect the actuak plot speed.
|
|
|
|
Here follows a basic description of the eample's code. Note however that the actual code is more involved and this description is mostly to give you a first clue, what is going on.
|
|
|
|
Data is stored in two [`std::array<double, NDATA>`](https://en.cppreference.com/w/cpp/container/array) objects (`X`, `Y`, and `Y2`) and the data is added as external pointer to the datastore:
|
|
```.cpp
|
|
// 3. make data available to JKQTPlotter by adding it to the internal datastore.
|
|
// Here the data from the std::array's is not copied, but only the pointer to
|
|
// the array is added to the datastore. therefore the datastore does not manage
|
|
// the memory, oly uses the data stored in it!
|
|
JKQTPDatastore* ds=getDatastore();
|
|
size_t columnX=ds->addColumn(X.data(), NDATA, "x");
|
|
size_t columnY=ds->addColumn(Y.data(), NDATA, "y");
|
|
size_t columnY2=ds->addColumn(Y2.data(), NDATA, "y2");
|
|
```
|
|
The datastore then uses the data from the `std::array` instances, i.e. just references the memory managed by the `std::arrays`s.
|
|
|
|
For this example we also don't use axis autoscaling, but set the axes explicitly:
|
|
```.cpp
|
|
// 6. scale the plot so the graph is contained
|
|
setX(X[0], X[NDATA-1]);
|
|
setY(-2,2);
|
|
```
|
|
|
|
Finally a slot is started with a one-shot timer. In that slot, the data is shifted one place to the left and the graph is updated. The slot also calculated the current framerate and displays it in the window title. Finally a single-shot timer with 1ms delay is used to call the slot again (i.e. continuously):
|
|
```.cpp
|
|
void SpeedTestPlot::plotNewData()
|
|
{
|
|
// move old data to the left
|
|
for (size_t i=0; i<NDATA-1; i++) {
|
|
X[i]=X[i+1];
|
|
Y[i]=Y[i+1];
|
|
Y2[i]=Y2[i+1];
|
|
}
|
|
// add one new data point
|
|
X[NDATA-1]=X[NDATA-2]+dx;
|
|
Y[NDATA-1]=sin(X[NDATA-1])+static_cast<double>(std::rand())/static_cast<double>(RAND_MAX + 1u)-0.5;
|
|
Y2[NDATA-1]=cos(X[NDATA-1])+static_cast<double>(std::rand())/static_cast<double>(RAND_MAX + 1u)-0.5;
|
|
|
|
// set new x-range and replot
|
|
setX(X[0], X[NDATA-1]);
|
|
redrawPlot();
|
|
|
|
// calculate and update FPS-rate in window title
|
|
auto tlastalst=t_lastplot;
|
|
t_lastplot=std::chrono::system_clock::now();
|
|
const double delta_secs=static_cast<double>(std::chrono::duration_cast<std::chrono::milliseconds>(t_lastplot-tlastalst).count())/1000.0;
|
|
setWindowTitle(QString("Live Data Speed Test: %2 datapoint, %1 fps").arg(1.0/delta_secs).arg(NDATA));
|
|
// enqueue call for next data value
|
|
QTimer::singleShot(1, this, SLOT(plotNewData()));
|
|
}
|
|
```
|
|
|
|
The result looks like this:
|
|
|
|
|
|
|
|
There are different factors affecting the replot speed:
|
|
1. *Anti-Aliasing:* If `JKQTPlotter` uses Anti-Aliasing for plotting, the plots are much nicer, but also about a factor of 3-4 slower. This is due to the increased amount of calculations, necessary in the drawing sub-system of Qt.
|
|
You can configrue anti-aliasing with these calls:
|
|
```.cpp
|
|
plot.getPlotter()->setUseAntiAliasingForGraphs(false);
|
|
plot.getPlotter()->setUseAntiAliasingForSystem(false);
|
|
plot.getPlotter()->setUseAntiAliasingForText(false);
|
|
```
|
|
2. *Number of Graphs:* The number of plots (and also ther type and complexity) is a major imapct factor in the plotting speed. You can switch off a plot with the context menu:<br>
|
|
3. *Number of Datapoints:* Of course, the more data has to be plotted, the slower the algorithm.
|
|
4. *Graph Type:* the speed also depends on how many elements have to be drawn. So drawing lines and symbols is slower than drawing lines-only or symbols-only.
|
|
5. *Axis Scales and Plot Appearance:* Replotting is done in two steps: First the plot with the axes, labels etc. is drawn. Then the graphs are draw on top. Therefore a replot is faster, if only the graphs change, because the background (plot) does not have to be replotted.
|
|
|
|
You can change all these properties by additional context-menu actions in this test-program.
|
|
|
|
|
|
|
|
|
|
Running this test on a modern AMD Ryzen 7 5800H laptop (eaxct conditions: Qt 6.2.4, 64-bit, MinGW, Release, AMD Ryzen 3600, Win11, high-res display) for two graphs with 500 datapoints each yields:
|
|
|
|
| Graph Style | Anti-Aliasing | Fixed X-Axis | frame rate [fps] |
|
|
| ------------ | ---------------- | --------------- | ----------------- |
|
|
| lines+symbols| yes | no | 20 |
|
|
| lines+symbols| yes | yes | 40 |
|
|
| lines+symbols| no | no | 50 |
|
|
| lines+symbols| no | yes | 95 |
|
|
| lines-only | yes | no | 30 |
|
|
| lines-only | yes | yes | 65 |
|
|
| lines-only | no | no | 78 |
|
|
| lines-only | no | yes | 140 |
|
|
|
|
|
|
Since 5.0.0 JKQTPlotter supports a line-compression algorithm (see `JKQTPSimplifyPolyLines()`). This allows to also draw very large datasets with sub-linear speed-decrease. The algorithm tries to not draw lines that are not visible, because they overlay each other. Using this mode we obtain these framerates for a two line-only graphs without anti-aliasing and with fixed x-axis:
|
|
|
|
| Number of Points | frame rate [fps] |
|
|
| ---------------- | ---------------- |
|
|
| 500 | 67 |
|
|
| 1000 | 42 |
|
|
| 2000 | 23 |
|
|
| 10000 | 11 |
|
|
|