5,838
edits
Month.ini: Difference between revisions
m
→Differences between Cumulus 1 and MX versions of file
(Major rewrite of the very basic previous page) |
|||
| Line 6: | Line 6: | ||
== Differences between Cumulus 1 and MX versions of file == | == Differences between Cumulus 1 and MX versions of file == | ||
Any date/time entries are in different formats as this example from the wind section shows. Also note that Cumulus 1 will use a comma for representing the decimal point if that is how a decimal point is defined for the locale defined in your device, but Cumulus MX always expects periods/full stops in .ini files regardless of the locale in use. Thus if you want to swap from Cumulus 1 to Cumulus MX during a month, you will copy your existing Cumulus 1 "data" folder to within your MX installation, but you will also need to manually edit your '''month.ini''' file so all the date/time entries are converted to the format shown for MX in the table below. (Note that as Cumulus 1 and MX cannot be run together accessing the same weather station, the dates in the two columns do not match). | Any date/time entries are in different formats as this example from the wind section shows. Also note that Cumulus 1 will use a comma for representing the decimal point if that is how a decimal point is defined for the locale defined in your device, but Cumulus MX always expects periods/full stops in .ini files regardless of the locale in use. Thus if you want to swap from Cumulus 1 to Cumulus MX during a month, you will copy your existing Cumulus 1 "data" folder to within your MX installation, but you will also need to manually edit your '''month.ini''' file so all the date/time entries are converted to the format shown for MX in the table below. (Note that as Cumulus 1 and MX cannot be run together accessing the same weather station, the dates in the two columns do not match). | ||
The wind speed and gust speed may be shown as integers if that is how your weather station outputs them, and you have not asked Cumulus to calculate them in different units. | The wind speed and gust speed may be shown as integers if that is how your weather station outputs them, and you have not asked Cumulus to calculate them in different units. | ||
| Line 28: | Line 26: | ||
| WindrunTime=11/03/2019 23:59:01 || WindrunTime=2019-03-10T19:54:00 | | WindrunTime=11/03/2019 23:59:01 || WindrunTime=2019-03-10T19:54:00 | ||
|} | |} | ||
== Retaining month.ini after month changes == | |||
[[File:Badge vMx.png]]In Cumulus MX, at the end of each month, the final ''month.ini'' for that month is renamed '''monthYYYYMM.ini''' (where YYYY denotes the year using 4 digits and MM denotes the month using two digits) e.g. ''month201703.ini'', thus ensuring that statistics for all past months remain accessible. | |||
[[File:Badge v1.png]]There is no obvious facility to achieve a similar retention automatically in Cumulus 1, although all the information can be generated by doing calculations from the relevant lines in dayfile.txt and those calculations are very easy to code in SQL if the daily summary is available in a database. However, there is an inefficient (because there is no facility within Cumulus 1 to perform an action only when month ends, and this technique therefore adds an action each time Cumulus does an update) work-around using the "extra files" feature that you can include "<currentlogfile>": | |||
ExtraLocal25=data\month.ini | |||
ExtraRemote25=data\month<currentlogfile>.ini | |||
ExtraProcess25=0 | |||
ExtraUTF25=1 | |||
ExtraBinary25=0 | |||
ExtraRealtime25=1 | |||
ExtraFTP25=0 | |||
== Meaning of the different parameters == | == Meaning of the different parameters == | ||
You have probably worked out that the attribute ''Speed'' in the examples in the above table is the maximum wind speed, that ''Gust'' is the maximum gust speed in the month and that ''Windrun'' is the maximum daily wind run. Those are the three rows that appear in the wind section of the table in the '''thismonth.htm''' web page. But you might be puzzled that the web page only shows a date for the maximum daily wind run, yet the month.ini entry includes a time. All that means is there was no wind after that time on that day, in Cumulus 1 if you edit your template '''thismonthT.htm''' and specify ''<#MonthWindRunHD format=HH:nn>'' you will see the time appear instead of the date. Put simply, the date/time entry is when Cumulus last updated that figure. In this particular case its calculated wind run never exceeded that figure in this month, so the entry has not been updated. | You have probably worked out that the attribute ''Speed'' in the examples in the above table is the maximum wind speed, that ''Gust'' is the maximum gust speed in the month and that ''Windrun'' is the maximum daily wind run. Those are the three rows that appear in the wind section of the table in the '''thismonth.htm''' web page. But you might be puzzled that the web page only shows a date for the maximum daily wind run, yet the month.ini entry includes a time. All that means is there was no wind after that time on that day, in Cumulus 1 if you edit your template '''thismonthT.htm''' and specify ''<#MonthWindRunHD format=HH:nn>'' you will see the time appear instead of the date. Put simply, the date/time entry is when Cumulus last updated that figure. In this particular case its calculated wind run never exceeded that figure in this month, so the entry has not been updated. | ||