juliuste / airrohr-prediction

UNMAINTAINED AND PROBABLY NOT WORKING ANYMORE. Airrohr sensor lower boundary predictions (work in progress)

airrohr-prediction

Predicts the next observation made by a given airrohr sensor using the lower bound of the prediction interval in order to provide a more robust threshold monitoring, e. g. in feinstaub-bot. Thanks to @dirkschumacher. Work in progress.

Installation

npm install --save airrohr-prediction

Usage

const prediction = require('airrohr-prediction')

prediction(1438) // sensor ID
.then(…)

Returns a Promise that will resolve in something like this:

{
    "PM10": {
        "lower": 9.416389708062244,
        "upper": 12.069610291937757,
        "expected": 10.743
    },
    "PM2.5": {
        "lower": 8.471014962809521,
        "upper": 10.416985037190477,
        "expected": 9.443999999999999
    }
}

See also

• feinstaub-bot - Twitter bot that monitors fine dust pollution for a given site or area via airrohr sensors.

Contributing

If you found a bug, want to propose a feature or feel the urge to complain about your life, feel free to visit the issues page.

airrohr-prediction's Issues

An in-range update of tape is breaking the build 🚨

The devDependency tape was updated from 4.11.0 to 4.12.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 9 commits.

• 42c84d6 v4.12.0
• 3e0a341 [Deps] update is-regex, string.prototype.trim
• ba7e2b2 [Dev Deps] update eslint
• f3a5925 [Tests] use shared travis-ci configs
• 6e94800 [Deps] update deep-equal, glob, object-inspect, resolve, string.prototype.trim
• 8150c3b [Refactor] use is-regex instead of instanceof RegExp
• 24487cb add tap-nyc to pretty-reporters
• c283615 [New] when the error type is wrong, show the message and stack
• 44cbbf5 [Tests] add a test for the wrong kind of error

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

p < 0.5

The error probability should always be less than 0.5. We could start with 0.3 and then observe if there are too many alarms.

Return more info about distribution

I guess it would make sense to return the expected value and the upper limit of the prediction interval as well. The expected value currently is simply the mean.