opentrack.git/tracker-pt/point_extractor.cpp, branch opentrack-2.3-rc49p9

tracker/pt: don't scale down auto threshold value

2016-07-16T21:54:31Z

Also, make the slider signify the max point radius (hence squaring).

tracker/pt: declare floating-point type size in one place

2016-07-16T21:32:59Z

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 . 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.

tracker/pt: adjust auto threshold max area size

2016-06-21T09:11:11Z

tracker/pt: fix points at (0,0) which are really NaN

2016-06-21T09:10:45Z

Issue: #318 cf. http://forum.il2sturmovik.ru/topic/2291-open-track/page-26

many: remove executable bit from source files

2016-05-15T10:34:38Z

We no longer have this recurring problem since I enabled ignoring executable bit changes on the Windows workstation.

Revert "tracker/pt: experimental non-white color removal"

2016-05-13T20:54:50Z

This reverts commit 546cfb5ad52dcfe1421d1af5e7baeada588ac735. @MathijsG points out that some users have red LEDs, not uniform white. Issue: #355

tracker/pt: adjust auto threshold max pixel value

2016-05-13T20:40:51Z

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

tracker/pt: conversion to unsigned char clamps by itself

2016-04-29T07:44:40Z

Remove redundant operation on the frame.

tracker/pt: sensible max point size

2016-04-27T06:00:58Z

tracker/pt: experimental non-white color removal

2016-04-27T05:28:55Z

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.