Extra Sensor Files: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
128 bytes added ,  21:37, 1 August 2021
m
m (→‎Design flaw?: new sub-heading, as a break for existing text)
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Template:Version badge Mx}}{{Version badge 1}}This Wiki page applies to both Cumulus flavours.[[Category:Cumulus MX]][[Category:Cumulus Files]][[Category:MX txt Files]][[Category:Cumulus 1]] <big>This page was however created when only the legacy Cumulus 1 existed, and would benefit from further improvement now that MX is the dominant flavour in use.</big>
{{Template:Version badge Mx}}{{Version badge 1}}This Wiki page applies to both Cumulus flavours.
[[Category:Cumulus Files]][[Category:MX txt Files]]
<big>This page was however created when only the legacy Cumulus 1 existed, and would benefit from further improvement now that MX is the dominant flavour in use.</big>


=The extra sensor files=
=The extra sensor files=
Line 10: Line 12:


The fields that can appear in the file vary depending on which release you are using.  The list of fields available for your release can be seen in a file: <code>Extrafileheader.txt</code> stored in the folder containing the executable.  The standard names shown in that list can be [[#General customisation|customised, as described below,]] to names that suit you better.
The fields that can appear in the file vary depending on which release you are using.  The list of fields available for your release can be seen in a file: <code>Extrafileheader.txt</code> stored in the folder containing the executable.  The standard names shown in that list can be [[#General customisation|customised, as described below,]] to names that suit you better.
In later MX releases, some extra sensor information is available for [[Recent history]], please see [[cumulusmx.db]] page for the values that are available from 3.12.0.


==Design flaw?==
==Design flaw?==
Line 178: Line 182:
All data is logged in the units which which have been selected by the Cumulus user, so a conversion is applied if the values are read from the weather station in other units, without any ability for any readings to be calibrated.
All data is logged in the units which which have been selected by the Cumulus user, so a conversion is applied if the values are read from the weather station in other units, without any ability for any readings to be calibrated.


As at August 2013, Cumulus has no tracking of extra sensor readings, so it does not calculate extremes for these extra sensors (unless it is the Oregon Scientific extra temperature sensor replacing the main one, see below), and extra sensors do not feed into the [[Category:Ini Files|extreme record tracking files]].  
As at August 2013, Cumulus has no tracking of extra sensor readings, so it does not calculate extremes for these extra sensors (unless it is the Oregon Scientific extra temperature sensor replacing the main one, see below), and extra sensors do not feed into the [[:Category:Ini Files|extreme record tracking files]].  


If you did want to try to calculate extremes for yourself, or draw graphs based on these logged extra values, then you must remember that as only spot values are logged, any extremes between the times that spot values are logged are lost.  But if you are skilled enough, it is possible to write [[PHP#Incorporating_Script|a script]] to read the file into either an array or database table for further processing. There are advantages in using databases, as Structured Query Language (SQL) makes reading and processing data from a database table easier than the code you would need to write to extract the same information directly from the original file. You might take inspiration from some php scripts available at [https://cumulus.hosiene.co.uk/viewtopic.php?f=18&t=18096 Forum's Create missing topic].
If you did want to try to calculate extremes for yourself, or draw graphs based on these logged extra values, then you must remember that as only spot values are logged, any extremes between the times that spot values are logged are lost.  But if you are skilled enough, it is possible to write [[PHP#Incorporating_Script|a script]] to read the file into either an array or database table for further processing. There are advantages in using databases, as Structured Query Language (SQL) makes reading and processing data from a database table easier than the code you would need to write to extract the same information directly from the original file. You might take inspiration from some php scripts available at [https://cumulus.hosiene.co.uk/viewtopic.php?f=18&t=18096 Forum's Create missing topic].
5,838

edits

Navigation menu