Recent History (preserving history): Difference between revisions

Recent history functionality in Cumulus is the ability to store weather values, at up to 1 minute intervals, for the last 7 days.

ItOnly issome importantspot toreadings realise,are thesestored arein spotRecent readingsHistory, andthe stored values will miss any extremes that occur between the times when the recent history values are stored. The weather value that tends to vary the most is wind speed, so that is where peaks are most often missed.

ItWhen Cumulus is alsorunning importantnormally, toentries realiseare thatstored weatheronce stationsa areminute, notregardless supplyingof valueshow tooften Cumulus oninterrogates athe continuousweather basisstation (might be every 10 seconds, dependingor onmore theor weatherless stationfrequently) typeand valuesregardless mayof behow availableoften atthe variousweather intervals,station eithergets everyupdated soreadings manyfrom secondssensors or(might perhapsbe atevery afew rateseconds, lessevery than40 onceseconds, aevery minute or less frequently). This can mean that the readings stored on a 1-minute basis may actually be duplicates if the station has not supplied a new value since the previous minute, or may not capture every reading from sensors if they are read more than once in a minute.

* Release 3.12.0 onwards: Held in [[cumulusmx.db|RecentData table in cumulusmx.db]] (uses SQLite),. soThere are many software tools available outsidethat can read/edit SQLite3, this is not the place to get too technical, but take a look at '''sqlitebrowser''' in a Linux environment, and '''phpLiteAdmin''' in Microsoft Windows. Also, you could use any application that can read ODBC files (e.g. Libre Office's Base functionality) can read the MX databases.