FAQ: Difference between revisions

337 bytes added ,  14:38, 27 October 2013
Line 122: Line 122:


As far as the timestamps in the logs (and the graphs) are concerned, Cumulus doesn't do anything in particular for DST. It generates timestamps based on the Windows clock. So basically, at the start of DST (i.e. when the clocks 'go forward') you will get an apparent gap of one hour in your data, and similarly at the end of DST (i.e. when the clocks 'go back') you will get an apparent hour of duplicate timestamps in your logs and graphs. The exact timing of the affected hours depends on the type of station and when Cumulus was running. You will tend to get better results if you leave Cumulus running during the clock change.
As far as the timestamps in the logs (and the graphs) are concerned, Cumulus doesn't do anything in particular for DST. It generates timestamps based on the Windows clock. So basically, at the start of DST (i.e. when the clocks 'go forward') you will get an apparent gap of one hour in your data, and similarly at the end of DST (i.e. when the clocks 'go back') you will get an apparent hour of duplicate timestamps in your logs and graphs. The exact timing of the affected hours depends on the type of station and when Cumulus was running. You will tend to get better results if you leave Cumulus running during the clock change.
Note that there seems to be an issue with Davis stations, either in the console/logger, or in the Davis DLL which Cumulus uses. If you don't have Cumulus running when DST ends, then when you start Cumulus up again, it doesn't receive all of the logger data it needs to catch up to the present time - the previous hour or so is missing.


== What formula does Cumulus use for Apparent Temperature?  ==
== What formula does Cumulus use for Apparent Temperature?  ==