5,838
edits
Correcting Extremes: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Introduction: restored accidentally deleted cell
m (→Introduction: restored accidentally deleted cell) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 23: | Line 23: | ||
!style="width:300px"|Notes | !style="width:300px"|Notes | ||
|- | |- | ||
|For current day so far | ! scope="row"|For current day so far | ||
|[[today.ini]] | |[[today.ini]] | ||
| Editor for "Today's rain" (no editor for other derivatives) | | Editor for "Today's rain" (no editor for other derivatives) | ||
| Line 29: | Line 29: | ||
|Many entries in this file (for non-midnight rollover, use is made of [[yesterday.ini]] too) get transferred to [[dayfile.txt]] at end of day. | |Many entries in this file (for non-midnight rollover, use is made of [[yesterday.ini]] too) get transferred to [[dayfile.txt]] at end of day. | ||
|- | |- | ||
| For past days | ! scope="row"| For past days | ||
| [[dayfile.txt]] | | [[dayfile.txt]] | ||
| See [[Amending dayfile]] | | See [[Amending dayfile]] | ||
| Line 35: | Line 35: | ||
| Often used as source for corrections - see [[#Accuracy Note]] | | Often used as source for corrections - see [[#Accuracy Note]] | ||
|- | |- | ||
|For current month-to-date | ! scope="row"|For current month-to-date | ||
|[[month.ini]] | |[[month.ini]] | ||
| Editor for "This month's records" | | Editor for "This month's records" | ||
| Line 41: | Line 41: | ||
| Please see [[#Accuracy Note]] | | Please see [[#Accuracy Note]] | ||
|- | |- | ||
|For current year-to-date | |colspan="5" style="background:pink;"|monthyyyyMM.ini are archived copies for past months | ||
|- | |||
! scope="row"|For current year-to-date | |||
|[[year.ini]] | |[[year.ini]] | ||
| Editor for "This year's records" | | Editor for "This year's records" | ||
|[[Webtags#Yearly|thisyear.htm]] | |[[Webtags#Yearly|thisyear.htm]] | ||
| Please see [[#Accuracy Note]] | | Please see [[#Accuracy Note]] | ||
|- | |||
|colspan="5" style="background:pink;"|yearyyyy.ini are archived copies for past years | |||
|- | |- | ||
|For all readings since a '''start date'' | ! scope="row"|For all readings since a '''start date'' | ||
|[[alltime.ini]] | |[[alltime.ini]] | ||
| Editor for "All Time Records" | | Editor for "All Time Records" | ||
| Line 53: | Line 57: | ||
|See table below for start date | |See table below for start date | ||
|- | |- | ||
|For a particular month in all years | ! scope="row"|For a particular month in all years | ||
|[[monthlyalltime.ini]] | |[[monthlyalltime.ini]] | ||
| Editor for "Monthly Records" | | Editor for "Monthly Records" | ||
|[[Webtags#Monthly_All_Time_Records|monthlyrecord.htm]] | |[[Webtags#Monthly_All_Time_Records|monthlyrecord.htm]] | ||
| | | Similar to previous row, but different start date, and separate extremes maintained for each month (regardless of the year) | ||
|} | |} | ||
Explaining columns in above table: | Explaining columns in above table: | ||
# The first column is self-explanatory | # The first (label) column is self-explanatory | ||
# The second column contains a link to the page that explains more about the file named there, which is where the extreme records are stored for that period | # The second column contains a link to the page that explains more about the file named there, which is where the extreme records are stored for that period | ||
# The third column gives the name for the '''Edit''' menu item to choose to edit these extreme records | # The third column gives the name for the '''Edit''' menu item to choose to edit these extreme records | ||
# The links in fourth column leads you to more information about the web tags associated with that period, you can incorporate those in your own [[Customised_templates|templates]]. | # The links in fourth column leads you to more information about the web tags associated with that period, you can incorporate those in your own [[Customised_templates|templates]]. | ||
== | ==How editing accuracy depends on source selected== | ||
The editors built into Cumulus, for extremes over a period of a month or more, give you the ability to display, for each extreme record: | The editors built into Cumulus, for long term extremes (over a period of a month or more), give you the ability to display, for each extreme record: | ||
# The figure taken from a search for that extreme by examining entries in the [[dayfile.txt]] for that period | # The (hopefully more accurate) figure taken from a search for that extreme by examining all entries in the [[dayfile.txt]] for that period | ||
# The figure taken from a search for that extreme by examining entries in the [[Standard log files]] for that period | # The (usually less accurate) figure taken from a search for that extreme by examining all entries in the [[Standard log files]] for that period | ||
Let me explain why the first returns the more accurate result (unless the '''dayfile.txt''' line, either was created with a rogue value, or has been corrupted): | |||
* Using [[Standard log files]] as source for recalculating past extremes: | * Using [[Standard log files]] as source for recalculating past extremes: | ||
** Let us assume you are using the default logging interval of 10 minutes | ** Let us assume you are using the default logging interval of 10 minutes | ||
| Line 77: | Line 81: | ||
** That means the [[Monthly log files]] do not capture any extremes recorded in the time (by default 599 seconds) between logs | ** That means the [[Monthly log files]] do not capture any extremes recorded in the time (by default 599 seconds) between logs | ||
** Therefore the detailed log files are not normally the most accurate source | ** Therefore the detailed log files are not normally the most accurate source | ||
** Please note, this less accurate way of deducing daily extremes/totals (to update dayfile.txt) is used by Cumulus software: | |||
*** For Legacy Cumulus 1: [[Amending_dayfile#Create_Missing_on_legacy_dayfile_editor|Create Missing in legacy dayfile editor]]. | |||
*** For MX: [[Calculate_Missing_Values#CreateMissing.exe|CreateMissing.exe]] utility. | |||
* Using [[dayfile.txt]] as source for recalculating past extremes | * Using [[dayfile.txt]] as source for recalculating past extremes | ||
** MX typically processes data from your weather station every second (even if you use a weather station type that only reads its sensors every 40 or 60 seconds). Cumulus 1 processes data from your weather station at intervals that vary for the different station types, but we can assume it is at least every 60 seconds. | ** MX typically processes data from your weather station every second (even if you use a weather station type that only reads its sensors every 40 or 60 seconds). Cumulus 1 processes data from your weather station at intervals that vary for the different station types, but we can assume it is at least every 60 seconds. | ||
** Therefore extremes recorded in '''today.ini''' (and from there into '''dayfile.ini'') are based on the full sampling done by Cumulus | ** Therefore extremes recorded in '''today.ini''' (and from there into '''dayfile.ini'') are based on the full sampling done by Cumulus | ||
** This means none, or very few, extremes are missed | ** This means none, or very few, extremes are missed | ||
** In March 2021, a new utility '''Create Records''' was planned (for use with MX only), as at July 2021 no progress has been made in coding it. It appears that this utility will read '''dayfile.txt''' and use the more accurate daily extremes it finds there, as a basis for updating longer term extremes in the other [[:Category:Ini Files|files like monthly-all-time and all-time]]. ''<big>Perhaps you my reader can be the contributor who updates this if the proposed utility becomes available</big>''. | |||
However, if you either have had an electrical supply problem or there has been corruption of data within your weather station generating a rogue value, it is possible that the files currently being used by Cumulus get corrupted. Provided you act, as soon as possible afterwards, you can make use of the [[Backup folder|backups]] that Cumulus takes. All the extreme record files mentioned in the table above are backed up when Cumulus is restarted and (depending on which release you are using - see [[today.ini]] - either | However, if you either have had an electrical supply problem or there has been corruption of data within your weather station generating a rogue value, it is possible that the files currently being used by Cumulus get corrupted. Provided you act, as soon as possible afterwards, [[Calculate_Missing_Values#Reading_archive_data|you can make use]] of the [[Backup folder|backups]] that Cumulus takes. All the extreme record files mentioned in the table above are backed up when Cumulus is restarted and (depending on which release you are using - see [[today.ini]]) - either with the end of day or start of day contents. For this month and this year extreme records, it is often better to find the previous extreme by examining a backup copy, providing a true extreme has not happened since, than by using the values displayed in the editor as those might be corrupted in the same problem. | ||
For all-time (and for MX only, monthly-all-time) extreme records, there is a log [[Alltimelog.txt]] (and for MX only,[[Monthlyalltimelog.txt]]) that logs each time the extreme is updated, so you can get an accurate previous value from there. | For all-time (and for MX only, monthly-all-time) extreme records, there is a log [[Alltimelog.txt]] (and for MX only,[[Monthlyalltimelog.txt]]) that logs each time the extreme is updated, so you can get an accurate previous value from there. | ||
| Line 94: | Line 102: | ||
==Why might your extremes need to be corrected?== | ==Why might your extremes need to be corrected?== | ||
Sometimes a mistake is made in setting up or calibrating a sensor, or (despite the warnings within both flavours of Cumulus about getting your choice of units correct from the start), you decide to change your units. In both cases, you will identify a constant/multiplier adjustment to be applied to adjust all values (luckily times and dates of extremes are not affected) over the past period. In both cases, you need to correct past entries in any [[Extra Sensor Files]], any [[Standard log files]], in [[dayfile.txt]], plus the multiple [[Category:Ini Files|extreme record files]]. | |||
'''The instructions on this page will help you correct the extreme record files''' as there are relatively few edits to do for a single source value changing because of units, or a calibration multiplier. There is no change to when a maximum/minimum occured, nor does it affect any derived values. For example a change in units, or calibration multiplier, for temperature or wind speed, does not affect calculations for wind chill and feels like temperature. It is a bit more complex if you change a calibration offset, as that might affect threshold for calculation of some derivatives (e.g. changing an offset for temperature or wind speed also affects wind chill). It is slightly more complicated changing units for temperature (as you may have many extra temperatures). | |||
The easiest way to change entries in any Extra Sensor Files, any Standard log files, and in dayfile.txt, is to either write a batch editing script (see [https://cumulus.hosiene.co.uk/viewtopic.php?p=155539#p155539 changed rainfall units example]), or to use a spreadsheet (be careful not to affects dates or times) like '''Libre Office Calc''' where you can paste special a multiplier to all cells in a particular column. | |||
If there is a [[Correcting_Extremes#Rogue_value|rogue value]] read from your weather station (this could be due to noise affecting communications, or because a sensor has been knocked), it can get into the daily summary file, any of the extreme record files, and any related derived value extremes may become wrong as well. | |||
A sensor might fail, and Cumulus does not recognise that "Null" (this might mean the weather station sends all bits set to zero or all bits set to one) values should be ignored when comparing against existing extreme records, and so set the extreme record to zero or maximum number that the number of bits can convey. | A sensor might fail, and Cumulus does not recognise that "Null" (this might mean the weather station sends all bits set to zero or all bits set to one) values should be ignored when comparing against existing extreme records, and so set the extreme record to zero or maximum number that the number of bits can convey. | ||
| Line 119: | Line 130: | ||
!style="width:100px"|First in Build | !style="width:100px"|First in Build | ||
|- | |- | ||
|highest/lowest apparent temperature | ! scope="row"|highest/lowest apparent temperature | ||
|26 Oct 2010 | |26 Oct 2010 | ||
|1.9.1 beta | |1.9.1 beta | ||
|957 | |957 | ||
|- | |- | ||
|highest/lowest feels like temperature | ! scope="row"|highest/lowest feels like temperature | ||
|24 June 2020 | |24 June 2020 | ||
|3.6.10 | |3.6.10 | ||
|3086 | |3086 | ||
|- | |- | ||
|highest Canadian Humidity Index (humidex) | ! scope="row"|highest Canadian Humidity Index (humidex) | ||
|28 Jul 2020 | |28 Jul 2020 | ||
|3.7.0 | |3.7.0 | ||
|3089 | |3089 | ||
|- | |- | ||
|highest minimum temperature | ! scope="row"|highest minimum temperature | ||
|15 April 2004 | |15 April 2004 | ||
|1.2.2 | |1.2.2 | ||
|(lost) | |(lost) | ||
|- | |- | ||
|highest USA heat index | ! scope="row"|highest USA heat index | ||
|29 Aug 2010 | |29 Aug 2010 | ||
|1.9.0 beta | |1.9.0 beta | ||
|955 | |955 | ||
|- | |- | ||
|wettest month | ! scope="row"|wettest month | ||
|5 April 2004 | |5 April 2004 | ||
|1.2 | |1.2 | ||
|(lost) | |(lost) | ||
|- | |- | ||
|highest daily wind run | ! scope="row"|highest daily wind run | ||
|3 Jul 2011 | |3 Jul 2011 | ||
|1.9.2 beta | |1.9.2 beta | ||
