FAQ: Difference between revisions

Over successive versions of Cumulus more and more code has been incorporated to deal with the way some stations are prone to reporting rogue readings. In general, if Cumulus identifies an odd value it will reuse the last good value instead, assuming that the problem will either right itself or be spotted and dealt with quickly.

*Ensure you are using the latest Cumulus build, if you are using an old version you will not have any enhancements made since them that might improve the way Cumulus reads from the station.

*If you have just restarted Cumulus, and encounter multiple rogue readings in the catch-up from the station logger, one possibility is to stop Cumulus and find the backup files that it took when you started it up (or just after the previous roll-over time), copy those files into the data folder, overwriting the ones that are there, then when you start it up again it could sort itself out. The purpose of the backup files is to allow Cumulus to be 'rewound' to a particular point in time. It simulates the situation where someone had closed Cumulus down at that point, and is only now starting it up again, and needs data to be downloaded from the station's logger to catch up to the present time.

The [[Diags]] log often contains useful information for sorting out what has been read, which values have been ignored, and which highs or lows may have been updated incorrectly. Note that automatic backups are made just after roll-over time because restarting Cumulus when there are no logger records to read before roll-over has been known to cause problems.