Currently, I am saving the execution results from an external simulation tool into a database every hour based on the simulation time. This data is then retrieved using CDCsync. From this data, I extract the timestamps to create a timeseries and build a system using Quiver that updates the Time Series Chart in real-time.
The implementation up to this point is complete; however, an issue has arisen.
In the current simulation setup, data can only be retrieved from “2024/5/30 07:00:00” to “2024/5/31 00:00”. As a result, even if I run the simulation multiple times for verification, the Quiver graph always displays data up to “2024/5/31 00:00”. This makes it impossible to confirm in real-time whether data is being successfully retrieved using Quiver’s Time Series Chart.
One of the requirements is that data for the same period (“2024/5/30 07:00:00” to “2024/5/31 00:00”) exists separately from the simulation data and can be used for comparison.
For instance, is there a way to ensure that the graph does not display data beyond the timestamp of the most recently retrieved data?
This makes it impossible to confirm in real-time whether data is being successfully retrieved using Quiver’s Time Series Chart.
Which data is updating in real time here? Are you referring to the simulation data or the actual sensor data? If you are referring the the actual sensor data, and this data is in a streaming time series sync (the backing dataset of the time series sync is a stream), then you can toggle stream mode by hovering over the x-axis and selecting “Stream”. This will continuously query for new data points on an interval defined in the Quiver analysis settings.
is there a way to ensure that the graph does not display data beyond the timestamp of the most recently retrieved data?
You can filter these time series using the “Filter time series” card to specify the range you want to show! You can specify a dynamic or static time range for this filter.
