May 6, 2012
Based on the previous discussions about the charts, we're going to modify those to allow the "dynamic" refreshes even if a "grouping" parameter is added to the query. I've got a couple ideas and wanted to mention them here to get some feedback on what our users think.
1. When an "average" data series refreshes, the last data point will float as the average changes. Every 15 seconds, the server will be queried. If the average for that timeslice has changed, the chart will be updated to reflect the new value; otherwise, it won't change. When sufficient time has gone by a new data point will be added to reflect the new timeslice and that point will begin to reflect the average.
2. Create Plugin Templates so multiple charts can be added for each data point. A field could have two charts, one with the average and one with individual points. This way dynamic data would be displayed every time your hardware sends an update, but the average chart would update more slowly to show accumulated data only.
February 1, 2013
May 6, 2012
1) Is not how it worked before. What happened before was that the averages populated the initial chart, then individual points came in. So the final points on a chart weren't averages, they were actual datapoints from the device being monitored. My proposal is to update the last datapoint with a new average rather than just adding new "non-averaged" points.
2) Private and public will stay the same. You'll be able to add additional charts for a view so that there could be public "average" and a public with no calculations for the same feed.
Most Users Ever Online: 166
Currently Browsing this Page:
Guest Posters: 1
Newest Members:Advantagetreeexperts, laundrydaddyuk, techhhelp5, ken, tran, huldacormier
Moderators: cstapels: 460
Administrators: Hans: 405, lee: 457