summaryrefslogtreecommitdiffhomepage
path: root/tracker-pt/point_extractor.cpp
AgeCommit message (Collapse)Author
2016-10-10tracker/pt: get rid of heap allocationStanislaw Halik
Use stack arrays rather than vectors. std::array may be a better choice though.
2016-09-28tracker/pt: don't check for blob limit pointlesslyStanislaw Halik
It's branch predicted anyway, but for clarity.
2016-09-25tracker/pt: square the center weightStanislaw Halik
Follow original implementation.
2016-09-21tracker/pt: fix area/radius confusion in extractorStanislaw Halik
2016-09-21tracker/pt: fix harmless fencepost errorStanislaw Halik
2016-09-21many: remove compat/pi-constant.hppStanislaw Halik
With -D_USE_MATH_DEFINES MSVC defines the standard M_PI and friends. Since this preprocessor definition is now always passed as part of the build system for MSVC. We can use M_PI as if on a mission.
2016-09-16tracker/pt: get rid of pt_types classStanislaw Halik
2016-08-28tracker/pt: merge 2 variables used exactly the same wayStanislaw Halik
2016-08-12all: rename modules s#^opentrack-##. and opentrack -> apiStanislaw Halik
Adjust usages.
2016-07-31tracker/{pt,aruco}: don't include opencv highgui, videoio is enoughStanislaw Halik
2016-07-25tracker/pt: drop signed/unsigned warningStanislaw Halik
2016-07-20tracker/pt: change brightness formulaStanislaw Halik
Use square root of area. Otherwise very small bright points are unfairly used.
2016-07-20tracker/pt: adjust min/max radius for auto thresholdStanislaw Halik
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-19move nan check to compatStanislaw Halik
2016-07-19tracker/pt: round text position of displayed point radiiStanislaw 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-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: fix points at (0,0) which are really NaNStanislaw Halik
Issue: #318 cf. http://forum.il2sturmovik.ru/topic/2291-open-track/page-26
2016-05-15many: remove executable bit from source filesStanislaw Halik
We no longer have this recurring problem since I enabled ignoring executable bit changes on the Windows workstation.
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-05-13tracker/pt: adjust auto threshold max pixel valueStanislaw Halik
The confusion stems from the max slider value. It's 255, not 100 as is the default. Max pixel count change to 20 was confused as we'll counting area and not radius here. Taking into account that the value was divided by 100 previously, it's bit less than the previous one but not as confused as then. Reported-by: @MathijsG Issue: #355
2016-04-29tracker/pt: conversion to unsigned char clamps by itselfStanislaw Halik
Remove redundant operation on the frame.
2016-04-27tracker/pt: sensible max point sizeStanislaw Halik
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: cover all "points" usages by a mutexStanislaw Halik
2016-01-09tracker/pt: remove unused blob struct membersStanislaw Halik
2015-12-24tracker/pt: limit max amount of extracted blobsStanislaw Halik
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-19tracker/pt: cv::Mat::at<T> is slow, use cv::Mat::ptrStanislaw Halik
2015-12-18tracker/pt: reduce mutex contentionStanislaw Halik
2015-12-18tracker/pt: remove krapStanislaw Halik
2015-12-18tracker/pt: don't fill mask on frameStanislaw Halik
Saves few % of cpu load
2015-12-17pt: histogram more granular 6 -> 8Stanislaw Halik
256 is divisible by 8, also less cpu usage
2015-12-08tracker/pt: reduce auto thresholding histogram bucket sizeStanislaw Halik
Previously it was too slow to 640x480@75.
2015-10-30move to subdirectory-based build systemStanislaw Halik
Closes #224
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-11 21:54:17 +0000