5,838
edits
Standard log files: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Correcting any logged data problems
| Line 160: | Line 160: | ||
==Correcting any logged data problems== | ==Correcting any logged data problems== | ||
As already mentioned, it is only MX where the ' | As already mentioned, it is only MX where the 'Data Logs' screen will allow editing of values in any standard log file, but in both flavours you can use their viewer to look and see if you are happy with what has been recorded. | ||
Some Weather stations may occasionally supply corrupted or rogue values to Cumulus | The MX editor is in the admin interface where it has no access to the actual log file which is stored wherever the MX engine runs. When you ask to load a selected month in that editor, what happens is that the MX engine does a quick read of the log file and puts its contents into the format used by dataTables software. That is what you see on the web page. Subsequently you can select a line there, click the '''Edit a line''' button, and the AltEditor software will raise a pop up showing all the fields in the line. This is where you make the edits. When you click the '''Save edit''' button, the line is sent back to the MX engine. On arrival of an updated line, the MX engine reads the log file again, into a standard array, replaces the array element corresponding to the received line, writes the array back into log file (replacing previous contents) and regenerates the dataTables format to send back to web page. | ||
Some Weather stations may occasionally supply corrupted or rogue values to Cumulus: | |||
*Cumulus 1 provides via '''Configuration''' menu [[Cumulus.ini#Section:_Offsets|''Calibration'']] screen the ability to screen out spikes (i.e. abnormal differences between two successive readings from weather station) in data picked up from some weather stations, it does not work for all types. See Cumulus help screen if you decide to use that to cope with future spikes. | *Cumulus 1 provides via '''Configuration''' menu [[Cumulus.ini#Section:_Offsets|''Calibration'']] screen the ability to screen out spikes (i.e. abnormal differences between two successive readings from weather station) in data picked up from some weather stations, it does not work for all types. See Cumulus help screen if you decide to use that to cope with future spikes. | ||
*Cumulus MX provides the same functionality, for the same restricted set of station types in its admin interface. | *Cumulus MX provides the same functionality, for the same restricted set of station types in its admin interface. | ||
If a weather station for some reason does not make a new reading available for a particular parameter, then both flavours of Cumulus reuse the same value as before for up to 6 times of reading the other parameters successfully. After that, Cumulus may stop any further processing. By default, Cumulus (of any flavour) will stop any further processing if certain outdoor sensors stop sending information: | |||
*pressure | |||
*wind speed | |||
*temperature | |||
*humidity | |||
Cumulus records in the standard log file various parameters that cannot be obtained from every weather station. Both flavours store zero if no value can be obtained for that parameter. | |||
Some rogue values may be obviously invalid (e.g. a zero pressure), others (e.g. wind shake on a tipping bucket rain gauge on a fine day) may be within the accepted all-time range, but you know the value is not right for that particular time. | Some rogue values may be obviously invalid (e.g. a zero pressure), others (e.g. wind shake on a tipping bucket rain gauge on a fine day) may be within the accepted all-time range, but you know the value is not right for that particular time. | ||
You may choose to just edit the rogue value into a reasonable value, or (if you are unable to decide on a better value) to delete that particular entire row in the | You may choose to just edit the rogue value into a reasonable value, or (if you are unable to decide on a better value) to delete that particular entire row in the standard log. | ||
In Cumulus MX you can do both of these in the data logs screen, in Cumulus 1 you will need to use an external editor. | |||
As explained above once any monthly log has been corrected, new highs and lows in other logs are easily rectified. | As explained above once any monthly log has been corrected, new highs and lows in other logs are easily rectified. | ||
| Line 183: | Line 194: | ||
===Manipulation outside Cumulus=== | ===Manipulation outside Cumulus=== | ||
Any log files for ''previous'' months can be edited (outside Cumulus) with Cumulus running, and after editing them, you can do further fetch edits within Cumulus as described above. The current month | Any log files for ''previous'' months can be edited (outside Cumulus) with Cumulus running, and after editing them, you can do further fetch edits within Cumulus as described above. The standard log file for the current month can also be edited outside Cumulus, but as it is being updated frequently you must stop Cumulus first (that explains why there was no edit option within Cumulus 1!). | ||
'''Tips''' -- take a copy of the original log file before you work on it outside Cumulus (perhaps give the ''not to be touched copy'' a filename of "<Month><Year>log.csv"). | '''Tips''' -- take a copy of the original log file before you work on it outside Cumulus (perhaps give the ''not to be touched copy'' a filename of "<Month><Year>log.csv"). | ||
