Closed structure7 closed 7 years ago
Idea no. 1:
cycleAverage
will be a running array of 10 previous cycle times. The most recent cycle duration pushes out the oldest cycle duration.
When to update the array? During a very long cycle, if the information is added only at the end, there really isn't a good trend line including that cycle. Wow... sounds like this might be logic heavy!
Array positions:
int cycleTimes[10];
0----1----2----3----4----5----6----7----8----9----
|-5--|-5--|-6--|----|----|----|----|----|----|----
*\ Work in progress... P.S. There are running average libraries.
Will revisit if I think it's important.
To report on Twitter (or elsewhere) need
currentRuntimeMin
and(eeCurrent -1)
(current number of runs) to report to a vPin or something for another device to provide analytics.Ideas for analytics:
Over what duration is cycleDuration averaged? Daily? Past x hours. Maybe just stick into an array?