FAQ: Difference between revisions

1,022 bytes added ,  16:48, 14 August 2018
m (→‎(Invented rain) Error in today's total: separated out previous text (as single set of numbered points in single sub-heading) into 3 sub-headings so easier to identify in forum answer)
Line 426: Line 426:
Assuming you use the type of weather station that does have an internal memory that retains observations that have already been read by your computer (and assuming that you have not left Cumulus off for so long that some of the days you want are no longer there)...
Assuming you use the type of weather station that does have an internal memory that retains observations that have already been read by your computer (and assuming that you have not left Cumulus off for so long that some of the days you want are no longer there)...


Use the 'rewind feature' of Cumulus.  Look in the backup folder for the backup which Cumulus took when it first started up today. Stop Cumulus, copy all of the files from that backup folder into the data folder (overwriting the files which are there) - this restores Cumulus to the state it was in before you ran it today. Start Cumulus and it should then download the data (from the date when it last stopped running onwards), to get up to date.
#Use the 'rewind feature' of Cumulus.  Look in the backup folder for the backup which Cumulus took when it first started up today. Stop Cumulus, copy all of the files from that backup folder into the data folder (overwriting the files which are there) - this restores Cumulus to the state it was in before you ran it today. Make sure nothing else on the computer is running that might affect either your station or Cumulus log files.  You can look in [[today.ini]] to see the date and time that you will rewind back to. Start Cumulus and it should then download the data (from the date and time in the "today.ini"), to get up to date. (Ignore remaining paragraphs if this has worked).
#As mentioned elsewhere if option 1 does not work, you can choose an older back-up and rewind back further providing the information is in the station logger. Remember however, that when you restart Cumulus it will only have access to observations at the station's logging interval, so any extremes between logging times previously picked up by the frequent querying of the station while Cumulus was previously running during the period you are now rewinding may be lost.
As mentioned elsewhere, you can even choose an older back-up and rewind back further providing the information is in the station logger. Remember however, that when you restart Cumulus it will only have access to observations at the station's logging interval, so any extremes picked up by the frequent querying of the station while Cumulus was previously running during the period you are now rewinding may be lost.
#If Cumulus still cannot catch-up, then you can try this more risky solution, you can edit the time in [[today.ini]] to exactly match a logging time in your station, the restart should then read all subsequent timed storage locations in the station.  This only applies to makes of stations that store the exact time with each logging, not to station types that only record duration since previous logging.
#If you are very skilled in understanding how Cumulus uses its various files, it is possible (when you stop Cumulus) to back up all the Cumulus log files, before you perform a restart, and then partially merge data from old and new files, this might enable you to keep some extremes that would otherwise be lost by the rewind.


== Cumulus read some invalid figures from my station ==
== Cumulus read some invalid figures from my station ==
5,838

edits