5,838
edits
Calculate Missing Values: Difference between revisions
m
→How Cumulus Works
|
=How Cumulus Works=
{{TOCright}}▼
The way that Cumulus works is that:
# At the end of each day, Cumulus logs the daily extremes or daily sums, from monitoring changes in each derived value into [[Dayfile.txt#List_of_fields_in_dayfile.txt|daily summary log]]
==Reading archive data==
▲{{TOCright}}
If you are using a weather station type that has a internal memory storing weather data that Cumulus can read, then when Cumulus is restarted it can read historic data from that logging memory.
This means that if you discover that Cumulus has missed some data, soon after it misses that data, you can '''rewind''', by stopping Cumulus and restarting. Typical reasons for missing some data would include power blips and problems with the interface between Cumulus and the weather station.
* For Cumulus 1, to stop Cumulus, you select [[Cumulus Screenshots|Exit]] from the main menu.
* For MX, how you stop MX depends on your device, and whether running as a service, please see [[MX on Linux]] or [[MX on Windows OS]]
pages as appropriate for advice.
Put simply, Cumulus stores the latest time it successfully read data from the weather station in [[Today.ini|today.ini]]. When Cumulus is restarted, if it is possible to read the historic data from the weather station, then any entries between the time stored and the current time will be read.
With Cumulus 1, there is some dependence on weather station type, but usually two passes are made through the external logging memory, the first pass investigates what records are available in the weather station, by reading backwards in time, and the second pass works forward in past time reading and processing those records.
With MX, again there will be some dependence on weather station type, and the process has not been documented by the developer; it appears just a single pass is made.
=Importing data from other systems for periods when Cumulus was not running=
| |||