5,838
edits
m (→Differences between Cumulus versions for this log file: Correction to build info) |
m (Update category) |
||
| (3 intermediate revisions by the same user not shown) | |||
|
[[Category:
<div style="background: LemonChiffon;padding:5px; margin:2px;">
== Introduction ==▼
[[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.
The log file "year.ini" (introduced by 1.9.1 beta builds) is where Cumulus software tracks the extremes for this year. Like [[alltime.ini]] (which has been present since very early builds) this log file has section headings with lists of properties (attribute = value). ▼
</div>
{{TOCright}}
▲The log file "year.ini" (introduced by 1.9.1 beta builds) is where Cumulus software tracks the extremes for this year
= Format of the file =
This is as described at [[:Category:Ini_Files]], where some differences between the legacy Cumulus and MX are noted. Therefore if you use decimal commas and are migrating this '''year.ini''' file from Cumulus 1 to MX, you need to do an edit so all the values entries are converted to use a full stop as decimal separator.
You may find it useful to read the [[Month.ini|month.ini]] page, which goes into slightly more detail as much of that applies to this file too.
For more information on this file see in the Cumulus 1 help file, in the section “Data log file format”. MX has changed to an ISO date format for each new time-stamp, but otherwise the file works the same way.
If you do move "year.ini" from Cumulus 1 to Cumulus MX and were using a comma as your decimal separator (e.g. 12,1) you will need to edit your file and change each (e.g. 12,1) to use a full stop before MX can read it (e.g. 12.1).
For full details see [[Correcting Extremes]] page.
The diagnostic logs in the 'diags' sub-folder for Cumulus 1 (and MXDiags for MX when full debugging switched on) record before and after values for updates to highs and lows for monthly and annual extreme records, and can help if this file is corrupted by a false extreme. The stored values can be corrected using the functionality available in both Cumulus 1 and MX for editing this year's records.▼
▲The diagnostic logs
The stored values can be corrected using the functionality available in both Cumulus 1 and MX for editing this year's records.
These lows and highs and their timestamps can be seen by picking the ''Highs and Lows - This year'' screen from the '''View''' menu (Cumulus 1 only - see picture on [[month.ini|this page]]).
If you cannot find the file when using Microsoft Windows [[FAQ#I_can.E2.80.99t_find_my_data_files.21|see this FAQ]].
| |||
edits