Year.ini - Revision history

Sfws: Update category

2021-06-08T15:17:12Z

Update category

← Older revision		Revision as of 15:17, 8 June 2021
Line 1:		Line 1:
	[[Category:~~Log~~ Files]]		[[Category:Ini Files]]
	<div style="background: LemonChiffon;padding:5px; margin:2px;">		<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!		[[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!
Line 8:		Line 8:


	== Introduction ==		= Introduction =

	{{TOCright}}		{{TOCright}}

	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)~~.		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.		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.
Line 38:		Line 43:
	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).		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).

	== Dealing with errors ==		= Dealing with errors =

	For full details see [[Correcting Extremes]] page.		For full details see [[Correcting Extremes]] page.

Sfws: /* Introduction */

2021-04-06T10:19:08Z

Introduction

← Older revision		Revision as of 10:19, 6 April 2021
Line 13:		Line 13:

	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).		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).

			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.		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.

Sfws at 10:17, 6 April 2021

2021-04-06T10:17:01Z

@@ Line 1: / Line 1: @@
 [[Category:Log Files]]
 == Introduction ==
 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).

Sfws: /* Dealing with errors */

2021-04-06T10:11:26Z

Dealing with errors

← Older revision		Revision as of 10:11, 6 April 2021
Line 28:		Line 28:
	== Dealing with errors ==		== Dealing with errors ==

			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 (for cumulus 1 in [[Diags folder]]) 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 in Cumulus 1 using the ''This month's records'' screen on the '''Edit''' menu. In MX the equivalent editor is accessed via the user interface you see in a browser.

			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]]).		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]].

Sfws: /* Differences between Cumulus versions for this log file */ Correction to build info

2021-04-06T09:50:04Z

Differences between Cumulus versions for this log file: Correction to build info

← Older revision		Revision as of 09:50, 6 April 2021
Line 14:		Line 14:
	== Differences between Cumulus versions for this log file ==		== Differences between Cumulus versions for this log file ==

	~~The~~ year functionality is not present prior to Cumulus 1.9.2 (build ~~1002~~ - 5 ~~July~~ ~~2011~~), so this file only exists for that and later builds of Cumulus 1, and all MX builds.		This year extreme record functionality is not present prior to Cumulus 1.9.1 (build 958 - Mon 01 Nov 2010), so this file only exists for that and later builds of Cumulus 1, and all MX builds.

	Some of the notes about problems with '''month.ini''' in particular builds apply equally to '''year.ini'''. An editor for this file is not available in MX until version 3.2.5 build 3061.		Some of the notes about problems with '''month.ini''' in particular builds apply equally to '''year.ini'''. An editor for this file is not available in MX until version 3.2.5 build 3061.

Sfws: /* Introduction */

2021-04-06T09:45:28Z

Introduction

← Older revision		Revision as of 09:45, 6 April 2021
Line 2:		Line 2:
	== Introduction ==		== Introduction ==

	The log file "year.ini" is where Cumulus software tracks the extremes for this year. Like [[alltime.ini]] this log file has section headings with lists of properties (attribute = value).		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).

	For more information on this file see in the Cumulus 1 help file, in the section “Data log file format”. ~~This~~ ~~still~~ ~~applies~~ for MX.		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.

	The sections (after the first [General]) can be in any order, Cumulus will maintain whatever order the sections are currently in. For readability you can insert blank lines into this file, Cumulus will not mind. Do not however introduce any punctuation nor change the format of any parameter line.		The sections (after the first [General]) can be in any order, Cumulus will maintain whatever order the sections are currently in. For readability you can insert blank lines into this file, Cumulus will not mind. Do not however introduce any punctuation nor change the format of any parameter line.

	== Content ==		== Content ==

Sfws: /* Differences between Cumulus versions for this log file */

2020-07-27T12:06:57Z

Differences between Cumulus versions for this log file

← Older revision		Revision as of 12:06, 27 July 2020
Line 15:		Line 15:

	The year functionality is not present prior to Cumulus 1.9.2 (build 1002 - 5 July 2011), so this file only exists for that and later builds of Cumulus 1, and all MX builds.		The year functionality is not present prior to Cumulus 1.9.2 (build 1002 - 5 July 2011), so this file only exists for that and later builds of Cumulus 1, and all MX builds.

			Some of the notes about problems with '''month.ini''' in particular builds apply equally to '''year.ini'''. An editor for this file is not available in MX until version 3.2.5 build 3061.

	The sections that are included in this file vary by version. There are more for MX than there were for Cumulus 1. The sections are same as for [[Month.ini\|month.ini]].		The sections that are included in this file vary by version. There are more for MX than there were for Cumulus 1. The sections are same as for [[Month.ini\|month.ini]].

Sfws: Resequence

2020-05-18T15:03:10Z

Resequence

← Older revision		Revision as of 15:03, 18 May 2020
Line 1:		Line 1:
	[[Category:Log Files]]		[[Category:Log Files]]
	== Introduction ==		== Introduction ==

	The log file "year.ini" is where Cumulus software tracks the extremes for this year. Like [[alltime.ini]] this log file has section headings with lists of properties (attribute = value).		The log file "year.ini" is where Cumulus software tracks the extremes for this year. Like [[alltime.ini]] this log file has section headings with lists of properties (attribute = value).

	For more information on this file see in the Cumulus 1 help file, in the section “Data log file format”.		For more information on this file see in the Cumulus 1 help file, in the section “Data log file format”. This still applies for MX.

	The sections (after the first [General]) can be in any order, Cumulus will maintain whatever order the sections are currently in. For readability you can insert blank lines into this file, Cumulus will not mind. Do not however introduce any punctuation nor change the format of any parameter line.		The sections (after the first [General]) can be in any order, Cumulus will maintain whatever order the sections are currently in. For readability you can insert blank lines into this file, Cumulus will not mind. Do not however introduce any punctuation nor change the format of any parameter line.

			== Content ==
⚫	The sections that are included in this file vary by version. There are more for MX than there were for Cumulus 1. The sections are same as for [[Month.ini\|month.ini]].

	This log file holds the information that feeds the [[Webtags#Yearly]] for the 'thisyearT.htm' web template. So '''you won't find the yearly rainfall total in this file''', that is not in that template.		This log file holds the information that feeds the [[Webtags#Yearly]] for the 'thisyearT.htm' web template. So '''you won't find the yearly rainfall total in this file''', that is not in that template.

	== Differences between Cumulus versions for this log file ==		== Differences between Cumulus versions for this log file ==

	The year functionality is not present prior to Cumulus 1.9.2 (build 1002 - 5 July 2011).		The year functionality is not present prior to Cumulus 1.9.2 (build 1002 - 5 July 2011), so this file only exists for that and later builds of Cumulus 1, and all MX builds.

		⚫	The sections that are included in this file vary by version. There are more for MX than there were for Cumulus 1. The sections are same as for [[Month.ini\|month.ini]].

	Some Cumulus 1 builds did not store correct values for those using 9am/10am rollover, see [[alltime.ini]] for some examples.		Some Cumulus 1 builds did not store correct values for those using 9am/10am rollover, see [[alltime.ini]] for some examples.
Line 18:		Line 22:
	Any date/time entries are in different formats for Cumulus 1 and Cumulus MX as illustrated for [[month.ini]]. That page also tells you that MX can read the Cumulus 1 date/time formats, so if you move a "year.ini" from Cumulus 1 you do not need to edit the date/time entries, MX will update them when its hits the first new extreme to record for the year.		Any date/time entries are in different formats for Cumulus 1 and Cumulus MX as illustrated for [[month.ini]]. That page also tells you that MX can read the Cumulus 1 date/time formats, so if you move a "year.ini" from Cumulus 1 you do not need to edit the date/time entries, MX will update them when its hits the first new extreme to record for the year.

	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.		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).

	== Dealing with errors ==		== Dealing with errors ==

	The diagnostic logs in the 'diags' sub-folder 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		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.

	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]]).		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]]).

Sfws: /* Introduction */

2020-05-18T14:57:15Z

Introduction

← Older revision		Revision as of 14:57, 18 May 2020
Line 1:		Line 1:
	[[Category:Log Files]]		[[Category:Log Files]]
	== Introduction ==		== Introduction ==
	The log file "year.ini" is where Cumulus software tracks the extremes for this year. Like [[alltime.ini]] this log file has section headings with lists of properties (attribute = value). For more information on this file see in the Cumulus 1 help file, in the section “Data log file format”. The sections (after the first [General]) can be in any order, Cumulus will maintain whatever order the sections are currently in. For readability you can insert blank lines into this file, Cumulus will not mind. Do not however introduce any punctuation nor change the format of any parameter line.		The log file "year.ini" is where Cumulus software tracks the extremes for this year. Like [[alltime.ini]] this log file has section headings with lists of properties (attribute = value).

			For more information on this file see in the Cumulus 1 help file, in the section “Data log file format”.
⚫	This log file holds the information that feeds the [[Webtags#Yearly]] for the 'thisyearT.htm' web template. So you won't find the yearly rainfall total in this file, that is not in that template.

			The sections (after the first [General]) can be in any order, Cumulus will maintain whatever order the sections are currently in. For readability you can insert blank lines into this file, Cumulus will not mind. Do not however introduce any punctuation nor change the format of any parameter line.

			The sections that are included in this file vary by version. There are more for MX than there were for Cumulus 1. The sections are same as for [[Month.ini\|month.ini]].

		⚫	This log file holds the information that feeds the [[Webtags#Yearly]] for the 'thisyearT.htm' web template. So '''you won't find the yearly rainfall total in this file''', that is not in that template.

	== Differences between Cumulus versions for this log file ==		== Differences between Cumulus versions for this log file ==

Sfws: /* Differences between Cumulus versions for this log file */

2020-03-19T17:46:52Z

Differences between Cumulus versions for this log file

← Older revision		Revision as of 17:46, 19 March 2020
Line 10:		Line 10:
	Some Cumulus 1 builds did not store correct values for those using 9am/10am rollover, see [[alltime.ini]] for some examples.		Some Cumulus 1 builds did not store correct values for those using 9am/10am rollover, see [[alltime.ini]] for some examples.

	Any date/time entries are in different formats for Cumulus 1 and Cumulus MX as illustrated for [[month.ini]]. That page also tells you ~~what~~ ~~you~~ ~~need~~ to do if you move from Cumulus 1 to ~~Cumulus~~ MX ~~and~~ ~~wish~~ to ~~keep~~ ~~using~~ ~~existing~~ ~~files~~ in the ~~"data"~~ ~~folder~~.		Any date/time entries are in different formats for Cumulus 1 and Cumulus MX as illustrated for [[month.ini]]. That page also tells you that MX can read the Cumulus 1 date/time formats, so if you move a "year.ini" from Cumulus 1 you do not need to edit the date/time entries, MX will update them when its hits the first new extreme to record for the year.

			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.

	== Dealing with errors ==		== Dealing with errors ==