Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yearly graph: data quality and data capture % #89

Open
ProBackup-nl opened this issue Dec 24, 2021 · 0 comments
Open

Yearly graph: data quality and data capture % #89

ProBackup-nl opened this issue Dec 24, 2021 · 0 comments

Comments

@ProBackup-nl
Copy link
Contributor

ProBackup-nl commented Dec 24, 2021

EC No 13/2007 annex 1 mentions that the minimum data capture for particulate matter should be 90%, excluding servicing of instrumentation. It does not give a standard for data availability.

Sensor.community and NAM firmware defaults to measurement intervals of 145 seconds.

Thus in one (1) year (excluding leap year = 366 days) there should be 365 times 86400 ÷ 145 = 217.489 measurements recorded. Below 90% (<.895 ≅ 194,653 measurements) this percentage should be displayed in yearly view as "Capture: ".

It's a pity that "Sensor uptime" is displayed but not pushed upstream with each measurement. One could argue that when the sensor is not up, that time can be seen as "service interval". For the time being, this missing downtime might be worked around with the user being able to configure a "instrumentation servicing time" value per device (to be substracted from the number of seconds per year).

To make the value even better, exclude zero (0) measurements as invalid, as well as measurements where the PM2.5 value is identical to the PM10 value. Another questionable thing related to data quality are outliers, as well as measurement values that are identical to the previous reported value (In my opinion not likely to happen). I mean PM2.5-#1 == PM2.5-#2 && PM10-#1 == PM10-#2. Only PM2.5 to be the same as the previous measurement (PM2.5-#1 == PM2.5-#2) does happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant