5,838
edits
Cumulus.ini (preserving history): Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
Cumulus.ini (preserving history) (view source)
Revision as of 17:07, 9 October 2013
, 9 October 2013→Section: Station: a few minor clarifications, mostly by changing order of parameters to simpify cross-reference
m (→Section: FTP Site: Edit advice for 'binary' as per Mark Crossley's comment in forum at http://sandaysoft.com/forum/viewtopic.php?f=11&t=10612) |
m (→Section: Station: a few minor clarifications, mostly by changing order of parameters to simpify cross-reference) |
||
|
*For a Davis station set to match your station logging interval. (Otherwise you may activate the 'feature' in the Davis stations where they send the entire contents of the data logger when Cumulus asks for the data since it was last running). See Readme.txt.
*For some station Types, Cumulus only reads latest readings while it is running, and missing station readings are not captured if Cumulus is restarted.
*For other makes as ''Cumulus on restarting is able (see next parameter) to read logged data from your station'' you can choose to match Cumulus and station logging intervals, then the frequency of logged information will be same regardless of whether Cumulus is running continuously or restarted.
*Some Cumulus users set this Cumulus logging interval to be one of the two shorter times so they retain the maximum measurement detail in case of any need to correct rogue measurements, but have set their station logging interval at a longer time so that the station does not overwrite the memory locations over the longest period they might be away. In this case, the frequency of logged information will change between the periods Cumulus is running and the catch-up readings from station logger when it is restarted.
|-▼
|UseDataLogger=1 ▼
|If selected, at start-up, Cumulus will download data from the stations data logger (if it has one) to catch up from the point where Cumulus was last shut down. See last parameter for advice re station logging interval.▼
*0 = Disabled▼
*1 = Enabled (Default)▼
|-
|WindUnit=0
*0 = mm
*1 = in
These are the labels that Cumulus applies on its screens and web pages, most weather stations work in one unit (e.g. dm for Fine Offset) and so the values are converted to either of the 2 listed during processing
|-
|TempUnit=0
|-
|StartDate=13/08/2009
|By default this will be set to the date of initial installation of the Cumulus application. See [[
|-
|LastLoggerDownload=13/08/2008 12:48:52
|YTDrainyear=0
|The year for which the YTDrain is to be applied. Default is 0 meaning not applied to any year.
▲|-
▲|UseDataLogger=1
▲|If selected, at start-up, Cumulus will download data from the stations data logger (if it has one) to catch up from the point where Cumulus was last shut down.
▲*0 = Disabled
▲*1 = Enabled (Default)
|-
|UseCumulusForecast=0
|From the Station Configuration Screen Forecast block, if selected Cumulus will generate a simple weather forecast, if your station does not supply one, or as an alternative to the one supplied by your station. See the [[Forecast webtag]] for more information. See next parameter for interval between forecast updates.
*0 = Disabled (default)
*1 = Enabled
|-▼
|HourlyForecast=0▼
|If Cumulus is set (see previous parameter) to generate a forecast (see [[FAQ#My_forecast_says_.22Not_available.22]]),
*0 = Disabled, (default) Cumulus will use Zambretti Forecaster every time it updates the web pages.
|-
|UseCumulusPresstrendstr=0
|UseSpeedForAvgCalc=0
|When enabled (=1) Cumulus will use the longer-term 'speed' values in the average speed calculation. The 'Use 10-min average wind speed' option must be selected for this option to have any effect.
▲|-
▲|HourlyForecast=0
▲|If Cumulus is set to generate a forecast, this setting (=1) causes the forecast to be updated only once an hour (on the hour).
|-
|RoundWindSpeed=0
| |||
