nyuuzyou/wikis huggingface dataset:
API Data Logs

Back to Cumulus MX Local API
== Day file Data ==
The all time records data response is designed for displaying on a web page, the text is formatted with HTML codes.
The format of the day file data API request is as follows...
http://localhost:8998:/api/data/dayfile?draw=1&start=XXXX&length=YYYY
Where...
* draw=1 is not used in this context, just pass a number, eg 1
* start=XXXX is the line number of the day file to start returning data for (0 relative)
* length=YYYY is the number of lines to return
eg.
http://localhost:8998/api/data/dayfile?draw=1&start=3510&length=5
Returns...
 {
 "draw": 1,
 "recordsTotal": 3825,
 "recordsFiltered": 3825,
 "data": [
 [3511, "24/08/19", "15.0", "142", "15:04", "12.1", "06:03", "27.9", "16:25", "1015.58", "18:47", "1019.95", "00:31", "0.0", "00:00", "0.0", "20.3", "61.3", "7.0", "12:14", "44", "16:13", "98", "07:13", "2.77", "12.0", "28.1", "16:29", "28.3", "16:38", "12.2", "06:12", "0.0", "00:00", "12.1", "06:03", "17.1", "13:31", "11.3", "06:03", "158", "0.5", "3.4", "417", "12:50", "2.1", "14:13", "", "", "", "", "", ""],
 [3512, "25/08/19", "19.0", "138", "14:20", "15.4", "23:57", "30.6", "16:29", "1016.05", "16:38", "1018.83", "22:44", "0.0", "00:00", "0.0", "21.8", "75.5", "9.0", "14:30", "39", "13:14", "93", "23:50", "3.02", "11.9", "31.2", "16:06", "31.4", "16:25", "15.9", "06:22", "0.0", "00:00", "15.4", "23:57", "20.1", "17:47", "12.1", "04:28", "156", "0.0", "4.3", "392", "13:06", "2.1", "14:39", "", "", "", "", "", ""],
 [3513, "26/08/19", "10.0", "264", "16:28", "13.0", "04:58", "25.7", "15:24", "1015.61", "19:07", "1018.69", "00:20", "0.0", "00:00", "0.0", "18.2", "28.5", "4.0", "13:15", "65", "15:24", "98", "06:01", "1.60", "6.8", "25.7", "15:24", "28.4", "15:23", "13.7", "04:58", "0.0", "00:00", "13.0", "04:58", "19.6", "15:48", "12.4", "04:58", "274", "0.5", "1.8", "418", "12:39", "2.0", "12:50", "", "", "", "", "", ""],
 [3514, "27/08/19", "10.0", "276", "14:32", "13.4", "04:18", "26.3", "13:34", "1011.58", "20:00", "1016.42", "00:02", "0.0", "00:00", "0.2", "19.0", "27.7", "5.0", "14:39", "60", "13:37", "97", "05:39", "1.40", "5.2", "26.3", "13:34", "29.3", "13:25", "14.1", "06:12", "0.2", "22:58", "13.4", "04:18", "19.9", "14:33", "12.7", "03:41", "250", "0.5", "2.2", "538", "12:40", "2.2", "12:40", "", "", "", "", "", ""],
 [3515, "28/08/19", "14.0", "225", "09:46", "10.1", "23:40", "16.7", "00:00", "1010.19", "07:50", "1015.14", "23:53", "9.8", "11:24", "3.4", "14.7", "50.6", "6.0", "16:37", "87", "07:41", "97", "23:43", "0.41", "1.6", "16.7", "00:00", "18.5", "00:00", "9.4", "23:56", "2.6", "12:01", "10.1", "23:40", "15.8", "00:48", "9.4", "23:40", "220", "1.0", "0.0", "123", "12:38", "0.9", "12:39", "", "", "", "", "", ""]
 ]
 }
Where...
* "recordsTotal" and "recordsFiltered" are the total number of lines found in the dayfile.txt file
* The first number in the array is the line number (1 relative)
* The rest of the array entries are the fields from the dayfile.txt - refer to Dayfile.txt
API Graph Data

Back to Cumulus MX Local API
The general format of the graph data API request is as follows...
http://localhost:8998:/api/graphdata/xxxxx
Where xxxx is the specific request as below:
=== tempdata.json ===
Returns inside temp, dew point, apparent temp, feels like, wind chill, heat index, outdoor temp as a JSON object, each value is an array of timestamp (JavaScript number) and value pairs...
 {
 "intemp": [[timestamp1,value1],[timestamp2,value2]...],
 "dew": [[timestamp1,value1],[timestamp2,value2]...],
 "apptemp": [[timestamp1,value1],[timestamp2,value2]...],
 "feelslike": [[timestamp1,value1],[timestamp2,value2]...],
 "wchill": [[timestamp1,value1],[timestamp2,value2]...],
 "heatindex": [[timestamp1,value1],[timestamp2,value2]...],
 "temp": [[timestamp1,value1],[timestamp2,value2]...]
 }
=== winddata.json ===
Same as temp data...
 {
 "wgust": [[,],[,]...],
 "wspeed": [[,],[,]...]
 }
=== raindata.json ===
Same as temp...
 {
 "rfall": [[,],[,]...],
 "rrate": [[,],[,]...]
 }
=== pressdata.json ===
Same as temp...
 {
 "press": [[,],[,]...]
 }
=== wdirdata.json ===
Same as temp...
 {
 "bearing": [[,],[,]...],
 "avgbearing": [[,],[,]...]
 }
=== humdata.json ===
Same as temp...
 {
 "hum": [[,],[,]...],
 "inhum": [[,],[,]...]
 }
=== solardata.json ===
Same as temp...
 {
 "UV": [[,],[,]...],
 "SolarRad": [[,],[,]...],
 "CurrentSolarMax": [[,],[,]...]
 }
=== sunhours.json ===
Same as temp...
 {
 "sunshours": [[,],[,]...]
 }
=== dailyrain.json ===
Same as temp...
 {
 "dailyrain": [[,],[,]...]
 }
=== dailytemp.json ===
 {
 "mintemp": [[,],[,]...],
 "maxtemp": [[,],[,]...],
 "avgtemp": [[,],[,]...]
 }
=== units.json or graphconfig.json ===
Returns the units of measurement used for the graph values above.
 {
 "temp": {"units": "C|F", "decimals": 0|1|2},
 "wind": {"units": "windunit", "decimals": N},
 "rain": {"units": "rainunit", "decimals": N},
 "press": {"units": "pressunit", "decimals": N},
 "hum": {decimals": N},
 "UV": {decimals": N}
 }
== Example response ==
A truncated response for humdata.json...
 {"hum":[[1602861480000,75],[1602861540000,75],[1602861600000,75],[1602861660000,74],....]}
API NOAA Reports

Back to Cumulus MX Local API
== Get Year Reports ==
The general format of the NOAA Year Report API request is as follows...
http://localhost:8998:/api/reports/noaayear&year=NNNN
Where NNNN is the year requested.
The report is returned as a partial JSON structure. A simple array of strings, each string composed of one line of the report...
 [
 " Annual Climatological Summary for 2019",
 "",
 "Name: Wilmslow Astro City: Wilmslow State: Cheshire, UK",
 "Elevation: 70 m Lat: N 53 19 32 Lon: W 002 14 33",
 "",
 " Temperature (°C), Heat Base: 15.5 Cool Base: 18.3",
 " Dep. Heat Cool Max Max Min Min",
 " Mean Mean From Deg Deg >= <= <= <=",
 " YR MO Max Min Mean Norm Days Days Hi Date Low Date 27.0 0.0 0.0 -18.0",
 "------------------------------------------------------------------------------------",
 " 19 1 5.9 1.2 3.8 -0.4 361 0 10.8 7 -3.7 31 0 0 15 0",
 " 19 2 11.6 3.0 7.2 2.7 235 0 20.2 26 -6.1 3 0 0 4 0",
 ... etc
 ]
== Get Month Reports ==
The general format of the NOAA Month Report API request is as follows...
http://localhost:8998:/api/reports/noaamonth&year=NNNN&month=XX
Where NNNN is the year requested, and XX the month.
The report is returned as a partial JSON structure. A simple array of strings, each string composed of one line of the report...
 [
 " Monthly Climatological Summary for Jun 2019",
 "",
 "Name: Wilmslow Astro City: Wilmslow State: Cheshire, UK",
 "Elevation: 70 m Lat: N 53 19 32 Lon: W 002 14 33",
 "",
 " Temperature (°C), Rain (mm), Wind Speed (mph)",
 "",
 " Heat Cool Avg",
 " Mean Deg Deg Wind Dom",
 "Day Temp High Time Low Time Days Days Rain Speed High Time Dir",
 "----------------------------------------------------------------------------------",
 "01 17.3 21.7 16:30 13.4 01:51 0.6 0.9 0.0 2.5 14.0 13:07 SSW",
 "02 17.2 20.6 11:18 13.2 23:43 0.4 0.3 4.8 5.7 24.0 16:54 SSW",
 ... etc
 ]
== Regenerate Year Report ==
The general format of the API request to regenerate a NOAA year report from the data logs is as follows...
http://localhost:8998:/api/genreports?year=NNNN
Where NNNN is the year to regenerate.
Cumulus MX will return the new report in the format described above.
== Regenerate Month Reports ==
The general format of the API request to regenerate a NOAA monthly reports from the data logs is as follows...
http://localhost:8998:/api/genreports/noaamonth&year=NNNN&month=XX
Where NNNN is the year requested, and XX the month.
Cumulus MX will return the new report in the format described above.
API Today/Yesterday Data

Back to Cumulus MX Local API
The all time records data response is designed for displaying on a web page, the text is formatted with HTML codes.
Each record in the returned array has the general format...
 ["Description", "Todays_value", "Todays_time", "Yesterdays_value", "Yesterdays_time"]
The general format of the today/yesterday data API request is as follows...
http://localhost:8998:/api/todayyest/xxxxx
Where xxxx is the specific request as below:
=== temp.json ===
Returns temperature data for today and yesterday.
An example response is given below...
 {
 "data": [
 ["High Temperature", "11.5 °C", "15:36", "10.5 °C", "15:56"],
 ["Low Temperature", "7.6 °C", "05:00", "4.6 °C", "04:41"],
 ["Temperature Range", "3.9 °C", " ", "5.9 °C", " "],
 ["High Apparent Temperature", "10.9 °C", "15:35", "10.1 °C", "16:38"],
 ["Low Apparent Temperature", "6.4 °C", "05:28", "3.1 °C", "04:41"],
 ["High Feels Like", "11.5 °C", "15:36", "10.5 °C", "16:02"],
 ["Low Feels Like", "7.6 °C", "05:00", "4.6 °C", "04:41"],
 ["High Humidex", "12.3", "15:36", "11.3", "15:56"],
 ["High Dew Point", "8.7 °C", "15:31", "8.4 °C", "15:56"],
 ["Low Dew Point", "6.4 °C", "04:46", "3.0 °C", "04:41"],
 ["Low Wind Chill", "7.6 °C", "05:00", "4.6 °C", "04:41"],
 ["High Heat Index", "11.5 °C", "15:36", "10.5 °C", "15:56"]
 ]
 }
=== hum.json ===
 {
 "data": [
 ["High Humidity", "96 %", "01:04", "96 %", "05:43"],
 ["Low Humidity", "83 %", "15:37", "82 %", "01:34"]
 ]
 }
=== rain.json ===
 {
 "data": [
 ["Total Rain", "0.0 mm", " ", "0.0 mm", " "],
 ["High Rain Rate", "0.0 mm/hr", "00:00", "0.0 mm/hr", "00:00"],
 ["High Hourly Rain", "0.0 mm", "00:00", "0.0 mm", "00:00"]
 ]
 }
=== wind.json ===
 {
 "data": [
 ["Highest Gust", "10.0 mph", "13:38", "8.0 mph", "01:27"],
 ["Highest Speed", "4.8 mph", "14:14", "3.1 mph", "12:07"],
 ["Wind Run", "20.0 miles", " ", "23.0 miles", " "],
 ["Dominant Direction", "179 ° S", " ", "333 ° NNW", " "]
 ]
 }
=== pressure.json ===
 {
 "data": [
 ["High Pressure", "1024.6 hPa", "10:18", "1025.8 hPa", "00:00"],
 ["Low Pressure", "1021.8 hPa", "15:54", "1022.4 hPa", "16:24"]
 ]
 }
=== solar.json ===
 {
 "data": [
 ["High Solar Radiation", "171 W/m2", "13:51", "216 W/m2", "09:53"],
 ["Hours of Sunshine", "0.00 hrs", " ", "0.58 hrs", " "]
 ]
 }
AirFileHeader.txt

This file is included in the MX distributions from build ???. It is not applicable to earlier versions.
Can someone who uses an airlink, please expand the text here to explain the significance of this file and the log files it relates to
Date(dd/MM/yy), Time(HH:mm),
In.temp,In.hum,In.pm1,In.pm2p5,In.pm2p5_1hr,In.pm2p5_3hr,In.pm2p5_24hr,In.pm2p5_nowcast,In.pm10,In.pm10_1hr,In.pm10_3hr,In.pm10_24hr,In.pm10_nowcast,In.pct_1hr,In.pct_3hr,In.pct_24hr,In.pct_nowcast,In.AQIpm2p5,In.AQIpm2p5_1hr,In.AQIpm2p5_3hr,In.AQIpm2p5_24hr,In.AQIpm2p5_nowcast,In.AQIPm10,In.AQIPm10_1hr,In.AQIPm10_3hr,In.AQIPm10_24hr,In.AQIPm10_nowcast,
Out.temp,Out.hum,Out.pm1,Out.pm2p5,Out.pm2p5_1hr,Out.pm2p5_3hr,Out.pm2p5_24hr,Out.pm2p5_nowcast,Out.pm10,Out.pm10_1hr,Out.pm10_3hr,Out.pm10_24hr,Out.pm10_nowcast,Out.pct_1hr,Out.pct_3hr,Out.pct_24hr,Out.pct_nowcast,Out.AQIpm2p5,Out.AQIpm2p5_1hr,Out.AQIpm2p5_3hr,Out.AQIpm2p5_24hr,Out.AQIpm2p5_nowcast,Out.AQIPm10,Out.AQIPm10_1hr,Out.AQIPm10_3hr,Out.AQIPm10_24hr,Out.AQIPm10_nowcast
Category:Cumulus Files
Air Link Log.txt

Category:Files_with_Comma_Separated_Values
=Introduction=
From MX release version 3.9.0 - b3095, functionality is added to offer support for the Davis AirLink air quality monitors.
== Naming==
The log files are created each month and are named using the "AirLink<yyyyMM>log.txt" standard, i.e. the year as 4 numerals is followed by the month as two digits in the middle of every file name.
== Content==
The fields stored in the file are as specified in AirFileHeader.txt.
==Uploading latest log to your web server==
Put <airlinklogfile> into the Local Filename column in Settings -->> Extra Web Files.
==Example==
Will somebody post an example of file contents here please
Alldailyhumdata.json

Category:Cumulus MXCategory:JSON Files
This file contains daily high and low values for Relative Humidity.
The file contents follow the following format:
Format 	Function
{ 	Start of JSON stream
"minHum":[ 	Signifies that the daily minimums follow
[JavaScript_Date_object,value]	Multiple data pairs (each occurrence is separated by a comma between closing bracket of one pair and opening bracket of next):
*The JavaScript Date object contains the number of milliseconds since 00:00:00.000 UTC on 1st January 1970, that date and time is known as the UNIX Epoch.
*The value is numerical, in this case a positive integer up to 100
], 	Ends the daily lowest figures
"maxHum":[ 	Signifies that the daily maximum follow
[JavaScript_Date_object,value]	Multiple data pairs (each occurrence is separated by a comma between closing bracket of one pair and opening bracket of next):
*The JavaScript Date object contains the number of milliseconds since 00:00:00.000 UTC on 1st January 1970, that date and time is known as the UNIX Epoch.
*The value is numerical, in this case a positive integer up to 100
] 	Ends the daily highest figures
} 	End of JSON stream
Alltimelog.txt

This page applies to both and . Category:Files_with_Comma_Separated_ValuesCategory:Cumulus 1Category:Cumulus MX
This file was introduced at Build 920 (28 Feb 2010) as a log of changes to the "alltime.rec" records, and it can be found in the data folder. From Build 924 (4 March 2010 beta version 1.8.9), the use of "alltime.rec" was discontinued, instead Alltime.ini was used, so this file now logs changes made in that file.
An entry is added to this file every time an all-time record changes, with details of the old and new records. This log can then be used to 'backtrack' if spurious data causes an all-time record to be broken incorrectly. It is also a useful log of when records were actually broken.
This file is just a log of changes, it is not read by Cumulus, Cumulus just appends to it. Editing any existing content in this file has no effect on Cumulus being able to continue to append to it.
== Format of the file ==
each line in the text file is made up of the following detail, delimited with a space 
*new date 
*new time 
*new value
*"item name"
*old date
*old time 
*old value
The dates are in ISO format (yyyy-mm-dd) and the times are in hh:mm 24-hour format (the separator is always a colon, irrespective of system settings), and the values are always to three decimal places. You should round the values appropriately when using them. The quotes are present with the item names.
==Example line of the file==
 2010-02-24 05:19 -7.600 "Lowest temperature" 2009-02-09 04:50 -6.500
Backup folder

All flavours of Cumulus (1, 2, and MX) create a sub-folder called backup. Within that is another sub-folder called daily.
Category:Cumulus FilesCategory:Configuration Files
In these folders, further sub-folders are created, each named by a string of digits representing the date and time the directory was created (without any punctuation) e.g. 20060519090000.
Inside each of these lowest level directory , you will find copies of some of the files from the data sub-folder. Which files are included does vary depending on which build you are running, but generally it is the files that are just about to be updated. The purpose of these backup copies of the files is simply to enable Cumulus to be rewound back to a previous time, and is useful if there is a problem. If you do such a rewind, you do lose data, while Cumulus is running it can read from your weather station in real-time; after a rewind all it can get from the weather station is any readings (at whatever interval is available) stored in any logger either that is part of, or is connected to, your weather station.
The directories within the daily sub-folder backup/daily represent start of day position and are created during the end of day process. Be aware that the files do not instantly contain full contents, so if for any reason you need to read them (as I do in my end of day batch procedure that Cumulus starts), you should wait half a minute or so after their creation. 
The directories, created within backup directly (instead of within backup/daily) are used to store the same files as they are when Cumulus starts.
Cumulus has a mechanism that deletes older directories when new ones are created. Consequently, it is useful if you are backing up your Cumulus installation (as you should do to another device) that you ensure these folders are backed up at least once a week.
CDL - EVAL

== Introduction ==
The Equations are kind of in continuous BETA, by the nature of all possible combinations and the recursive parsing not all possible equations have been tested (haha)
The EVAL functions gives the possibility to modify a measurement and plot the result as a separate line. So theoretically one could plot the Dewpoint as a calculated derivative of the Temperature. Also the Growth Degree Days can be simply calculated. The effect of EVAL is that it is not required to transfer data if it can be derived from measurement. Only the measurement needs to be transferred.
To be able to accomplish the calculations, one needs certain additional functions such as SUM, LN and EXP. The functions which are available to the user are described below. The list will grow as the functions become available.
== Equation ==
Each equation is formulated between square brackets and is meant to modify a weather variable. Available to the user are functions, the weather variables and the mathematical operators +, -, * and /. EVAL Equations are more or less formally described as:
 EVAL '[' Equation ']'
 Equation := Term [ '+'|'-'|'*'|'/' Term ]
 Term := '(' Equation ')' | Function '(' Equation ')' | Plotvariable | Number
 Function := 'SUM' | 'LN' | 'EXP'
 Number := <Integer>[.[<Integer>]]
NOTE: The plotvariable MUST be from the range as defined for the PLOT i.e. ALL | DAILY | RECENT.
== Functions ==
=== SUM ===
The SUM function produces the sum of the Plotvariable from the first of january to the 31 of december after which it resets to zero. So it is a cyclic function!
When applied to the temperature this leads to the Growing Degree Days, when applied to rain it leads to the yearly rainfall until the current day. For other variables it may have meaning or it may have not.
At the moment there can be only one sum function per chart.
The following example shows the daily average temperature modified to the Growing Degree Days with an offset of 5 °C:
 CHART GrowingDgreeDays TITLE TempSum with offset 5
 PLOT ALL AverageTemp colour CornflowerBlue as column
 PLOT ALL AverageTemp EVAL [ SUM(AverageTemp-5) ] colour green Axis DegreeDays
 EndChart
=== LN ===
The LN function provides the Natural Logarithm (the logarithm on the basis of the Euler number e).
It is implemented as the JavaScript function Math.log.
=== EXP ===
The EXP function provides the power function for the base of the Euler number e.
It is implemented as the JavaScript Math.exp.
Category:CumulusUtils
CDL - STATS

== Introduction ==
The STATS plots a statistic of a specific Plotvariable in the chart. The normal PLOT of that variable must be present. STATS implies the ALL or DAILY range specification. 
RECENT PLOTS have no STATS defined (at the moment).
A STATistic is by definition a derivative of a series of a Plotvariable e.g. the Standard deviation or a running average. A Mean in itself is a single value and single value statistics are not plottable as such. They are usually reported in other ways. To be able to use the STATS for a certain Plotvariable the statistic needs to be made available in the runtime of the compiler. Technically it might be possible to supply statistics through the EVAL functionality and in some cases that might work. In general that technique is disadvised.
== Statistical functions ==
The STATS keyword requires a Plotvariable on which to apply the statistics and a method to apply and a statistical method to use.
 STATS [ALL||DAILY|RECENT|EXTRA] <Plotvariable> <Statistical method>
The following statistical methods are available in the ChartsCompiler:
#SMA - Best explained in the external Wiki: Simple Moving Average. The period for the Moving Average is given by the user as value to the parameter : PeriodMovingAverage= <value> (section [graphs])
-- To be Expanded --
=== Examples ===
The following example shows the Rain for all days (all observations). 
In addition the yearly cumulative curve is shown and the moving average (SMA - Simple Moving Average). See image on the right.
 CHART DailyRain TITLE Rain with statistics
 PLOT ALL DayRain colour CornflowerBlue as column 
 PLOT ALL SumDayRain EVAL [ SUM( DayRain ) ] COLOUR crimson AXIS Free
 STATS ALL DayRain SMA colour green
 EndChart
Category:CumulusUtils
Cumulus.ini (Beta)

= Introduction =
The main cumulus.ini configuration file is located in the directory in which you installed Cumulus.exe. It is a text file containing initialization parameters used by the Cumulus application, and is read only when Cumulus starts up. Parameter lines are in the form 'attribute=value' and grouped into sections. Cumulus re-writes the contents of the application configuration screens to the file when it shuts down.
Each new version of cumulus may add additional parameters set by revised configuration screens (these initially appear at the end of the relevant section), and/or permit additional parameters to be added manually (these can be inserted anywhere within the section). If you are using an old version, then checking the release information may be advisable to identify the sections applicable to your build and the parameters allowed within those sections may be a subset of those listed below.
== Live Version ==
See cumulus.ini for list of sections, attributes and allowed values for the current live version of Cumulus.
== Beta builds ==
If you are using a beta build, there may be additional sections and/or additional parameters (attribute=value) under test. Brief details of such changes will be given in the support forum announcement for the relevant build. Once such changes seem established they should be added here.
Below is a list of the additional items available in any current beta version. These details will be explained fully and transferred to the main page when each beta version becomes 'live'.
= File Contents =
== Introduction ==
The entries shown include the default value from the configuration screen where applicable, a typical example value where appropriate, or just the attribute and an equals sign where there is no typical value.
== Current Beta ==
No changes.
See main Cumulus.ini_(Cumulus_1) page.
Category: Configuration_Files
CumulusMX and Cumulus1 UI style Multilingual Websites

CumulusMX and Cumulus1 UI style Multilingual Websites
default=(https://cumulus.hosiene.co.uk/viewtopic.php?f=18&t=17845&p=140004#p140004)
Working sites may be viewed at
https://silveracorn.nz/cumulusmx/
and
https://silveracorn/cumulus1/
This website template is based on the look and feel of the internal User Interface website incorporated into CumulusMX.
It is completely different from the included Cumulus1 style website in the cumulusMX/web and cumulusMX/webfiles folders.
This website template also includes additional modules that are not part of CumulusMX.
It uses HTML5 / UTF-8, PHP, Ajax, JavaScript, and jQuery to provide an improved end user experience when compared to the C1 style website.
 
There are extensive help files included.
There are two versions
 One for Cumulus MX
 One for Cumulus1
Many of the files are the same.
The main difference is the graphs - Charts for MX and Trends for C1
Category:User Contributions