5,838
edits
Dayfile.txt: Difference between revisions
m
→Dealing with rogue measurements: new section
m (→Manipulation outside Cumulus: Introduced 'Rules' and changed order for consistency with monthly log files) |
m (→Dealing with rogue measurements: new section) |
||
| Line 1: | Line 1: | ||
Cumulus maintains a daily file of the highs and lows of each day, as well as a few other nuggets of information. The data contained in the file are used to build the graphs. | Cumulus maintains a daily file of the highs and lows of each day, as well as a few other nuggets of information. The data contained in the file are used to build the graphs. | ||
== Dealing with rogue measurements == | |||
Cumulus provides via '''Configuration''' menu ''Calibration'' screen the ability to screen out spikes in data picked up from your weather station. See Cumulus help screen if you decide to use that to cope with some spikes. But some rogue values may be within the accepted all-time range, but just not really applicable to that particular day. | |||
If you discover a rogue measurement (perhaps the wind affected your tiping bucket rain gauge or your weather station just reported a corrupted value), on the day it occured, see [[today.ini]] or [[FAQ]] for further advice. | |||
If the rogue measurement is discovered some days after it occured, then in many cases it will have affected your highs and lows for the current month, month-by-month, current year, and/or all-time. As first step you should update the appropriate field in the row for the affected date in dayfile.txt. See [[Alltimelog.txt]] for current and previous values to help you know what rogue value to hunt for and know what the high/low value was before the rogue affected it. Once ''dayfile.txt is correct'' the Cumulus editors will allow you to: | |||
* update the highs and lows in [[Alltime.ini]] by choosing ''all time records'' from the '''Edit''' menu. | |||
* update the highs and lows in [[year.ini]] by choosing ''This year's records'' from the '''Edit''' menu. | |||
* update the highs and lows in [[month.ini]] by choosing ''This month's records'' from the '''Edit''' menu. See [[Diags]] for current and previous values of high or low in the current month or the immediate preceding month if the rogue was recorded less than 10 days ago. | |||
* update the highs and lows month-by-month in [[monthlyalltime.ini]] by choosing ''Monthly records'' from the '''Edit''' menu. Click the ''Help'' button for specific instructions on using ''Reset'' and the two ''Copy'' column header buttons in this ''Monthly Records (Highs and Lows) Editor'' to action all rows. | |||
'' '''Note''' in each of above 4 editing screens you can: | |||
# see the currently stored extremes, and optionally ''Reset'' (row by row) to pre-editing value and timestamp. | |||
# load the dayfile.txt to view extremes derived from those figures (after your correction of the rogue values) and | |||
# optionally ''Copy'' (row by row) the logged values (and associated date/time information) into the relevant .ini file. | |||
# click the ''Help'' button for detailed instructions on using ''The Records (Highs and Lows) Editors''. | |||
# store your revised figures by clicking ''OK'' (or abandon all your edits by clicking ''Cancel''). | |||
(Each of these screens is a text editor, and works best when at full screen).'' | |||
Ideally, you will subsequently try to edit the rogue data for the particular time it was logged see [[Monthly_log_files#Correcting_any_logged_data_problems]], but getting the daily summary in dayfile.txt must always be the priority. | |||
==Editing in Cumulus== | ==Editing in Cumulus== | ||
The last command in '''Edit''' menu is ''dayfile.txt''. This is a text editor, and works best when at full screen. | The last command in '''Edit''' menu is ''dayfile.txt''. This is a text editor, and works best when at full screen. | ||
| Line 5: | Line 26: | ||
You can use this editor to correct individual values by overtyping. | You can use this editor to correct individual values by overtyping. | ||
The '''Create missing''' button will insert missing rows (complete days) by reading and calculating from [[Monthly_log_files]] (a technique that is useful for importing, and processing, pre-Cumulus observations | The '''Create missing''' button will insert missing rows (complete days) by reading and calculating from [[Monthly_log_files]] (a technique that is useful for importing, and processing, pre-Cumulus observations). Click the ''Help'' button for detailed instructions. Cumulus Help is comprehensive and explains how a list of inserted records is produced. The procedure is explained in the [[Monthly_log_files | Wiki topic]] in greater context detail than is possible in the Cumulus ''Help''. | ||
If just some fields are missing from a particular row (meteorological day) on day file, then there is a [[Monthly_log_files#Using_Monthly_logs_to_deal_with_shorter_.28or_incomplete.29_dayfile.txt_records_for_particular_dates | workaround]] as at all current versions (up to 1.9.4) you can only import from the [[Monthly_log_files]] if the whole date (row) is missing in ''dayfile.txt''. | If just some fields are missing from a particular row (meteorological day) on day file, then there is a [[Monthly_log_files#Using_Monthly_logs_to_deal_with_shorter_.28or_incomplete.29_dayfile.txt_records_for_particular_dates | workaround]] as at all current versions (up to 1.9.4) you can only import from the [[Monthly_log_files]] if the whole date (row) is missing in ''dayfile.txt''. | ||