search

bluecherrydvr / bluecherry-apps-issues

1 stars 0 forks source link

Experiment with flag thresholds to reduce false motion events #12

Open curtishall opened 10 years ago

curtishall commented 10 years ago

Issue by curtishall Mon Aug 26 19:08:13 2013 Originally opened as https://github.com/bluecherrydvr/bluecherry-apps/issues/86

Currently, any frame flagged as having motion by the driver will begin a motion event. The threshold required to trigger a flag is configurable, but this still results in a huge number of false positive motion events, often generated by very brief movement like noise or shadows. Most actual motion will be much more consistent, and last over a period longer than a single frame.

Implement a server-level threshold, where a motion event is started only after a number of frames have been flagged within a certain period. This number should be fairly low.

One suggested approach for the threshold is to trigger only when at least N% of frames in the past X seconds contain motion, where N is a low tunable value, and X is a short period of time (generally between .25 and 2 seconds?). A fraction of frames within period X should be used over a static count to avoid false negatives on low framerate devices.

http://improve.bluecherrydvr.com/issues/955

ghost commented 9 years ago

WIP in motion_analysis_stw branch.

ghost commented 9 years ago

Merged in as commit 721fba011bf46dfdc12c5ddf4e06b127d452b5a5 (today).

ghost commented 9 years ago

Reopening because current state lacks web UI configuration part.