5,838
edits
mNo edit summary |
|||
The file now known as alltime.ini was originally in a different format as alltime.rec.
== Introduction ==▼
<div style="background: LemonChiffon;padding:5px; margin:2px;">
[[File:Crystal Clear info.png|40px]] This page was written for the (legacy) Cumulus 1 software. It has been partially updated to cover MX, but that was for a MX release that is no longer latest!
Please can a contributor redesign this page and update content, so it is more friendly for those using latest release, while still helping those using older MX releases and the legacy Cumulus software.
</div>
Cumulus maintains a number of 'all time records' for the station -- highs and lows and their timestamps for many of the readings. For ''more information'' on this file see in the '''Cumulus help''' file, in the section “The Data log files”.
==Which build are you using? ==
=== Up to Build 920 (version 1.8.9) ===
The highs and lows were stored in a database file (alltime.rec), this was efficient for Cumulus 1 to read and update, but being in binary code made it hard for any corrections to be made outside Cumulus.
Build 920 (28 Feb 2010) initiated the use of a log of changes to the "alltime.rec" records, called [[alltimelog.txt]], which can be found in the '''data''' folder. An entry is added to this file every time an all-time record changes, with details of the old and new records. This log can then be used to 'backtrack' if spurious data causes an all-time record to be broken incorrectly. It is also a useful log of when records were actually broken.
== Editing this log file ==
For full details see [[Correcting Extremes]] page.
It is possible that rogue values read from your weather station will cause this log file to show an incorrect extreme. As mentioned earlier, there is a log of changes to the "alltime.ini" records, called [[alltimelog.txt]], so look at that to see when your rogue value was processed and what was the previous extreme that you should reset to in "alltime.ini".
|
edits