summaryrefslogtreecommitdiffhomepage
path: root/tracker-pt/point_extractor.h
AgeCommit message (Collapse)Author
2016-07-20tracker/pt: fix wrong input to flood fillStanislaw Halik
The binary frame needs to be used, not grayscale. v2: Use brightness for sorting points.
2016-07-19tracker/pt: reduce lockingStanislaw Halik
2016-07-19tracker/pt: replace point extractor with original one by Patrick RuoffStanislaw Halik
The new extractor we've been using doesn't take into account brightness at all. All contours give is the ability to sort points by circularity. v2: Change the auto threshold point size range to 2->7 pixels radius. Issue: #389 v3: sort by radius instead
2016-07-19some: replace hardcoded pi values with the same pi constantStanislaw Halik
We can't depend on M_PI existing after including cmath.
2016-07-16tracker/pt: don't scale down auto threshold valueStanislaw Halik
Also, make the slider signify the max point radius (hence squaring).
2016-07-16tracker/pt: declare floating-point type size in one placeStanislaw Halik
We want double precision for POSIT. It's best for the type to be set in ope place without the need to go over everything while switching it back and forth during tests. Machine epsilon for float is very small as per <https://en.wikipedia.org/wiki/Machine_epsilon>. Also see the absurdly high epsilon of 1e-4 of POSIT that we've had. With floats, making the epsilon lower resulted in change deltas flushing to zero. This typically led to the translation Z value being very unstable in PT. After the epsilon and data type size changes the Z value is stable.
2016-06-21tracker/pt: adjust auto threshold max area sizeStanislaw Halik
2016-06-21tracker/pt: move pi constant to headersStanislaw Halik
2016-05-13Revert "tracker/pt: experimental non-white color removal"Stanislaw Halik
This reverts commit 546cfb5ad52dcfe1421d1af5e7baeada588ac735. @MathijsG points out that some users have red LEDs, not uniform white. Issue: #355
2016-04-27tracker/pt: experimental non-white color removalStanislaw Halik
It's enabled only for automatic thresholding. With it on, it's possible to keep tracking in normal light conditions without changing gain or exposure beforehand. It won't function on badly overexposed images, or with other bright white colors in the frame. It should function on somewhat overexposed images. CPU usage is somewhat high, even taking advantage of all OpenCV SIMD goodness as per the code. We can revert the change if user reception is bad.
2016-03-07tracker/pt: less malloc/free each frameStanislaw Halik
2016-02-17tracker/pt: fix buildStanislaw Halik
2016-02-17tracker/pt: retire get_points() in the extractorStanislaw Halik
2016-02-17tracker/pt: protect get_n_points()Stanislaw Halik
There's a race here since further accesses to the points array aren't protected by a mutex in the extractor class. There's no race in "get_points()" in the extractor since it's only used in same thread where updates take place.
2015-12-28tracker/pt: increase auto threshold bucket size againopentrack-2.3-rc21p7Stanislaw Halik
Slowdown was caused by something else. I can no longer reproduce it.
2015-12-19tracker/pt: don't allocate temporary dynamic size arraysStanislaw Halik
2015-12-19tracker/pt: don't copy points array needlesslyStanislaw Halik
2015-12-18tracker/pt: reduce mutex contentionStanislaw Halik
2015-10-30move to subdirectory-based build systemStanislaw Halik
Closes #224