summaryrefslogtreecommitdiffhomepage
path: root/tracker-pt/point_tracker.h
AgeCommit message (Collapse)Author
2022-05-11tracker/{pt-base,trackhat}: add variable deadzone factoropentrack-2022.2.0Stanislaw Halik
2021-10-19cv, tracker/pt: cleanup opencv includesStanislaw Halik
2021-09-28tracker/pt: fix warningsStanislaw Halik
2021-09-28tracker/pt: add point filterStanislaw Halik
2021-09-26tracker/{pt,wii}: cosmetic changes onlyStanislaw Halik
2019-02-21tracker/pt: don't `namespace pt_module' for core PT stuffStanislaw Halik
2019-01-16modernize onlyStanislaw Halik
- replace `static constexpr inline' with `static constexpr'. `inline' is implied. - use braced initializer lists where applicable - still missing `override' usages
2019-01-16cv/numeric: rename namespaceStanislaw Halik
2019-01-16tracker/pt: retire pose reuseStanislaw Halik
2019-01-16tracker/pt: set expected pose to identity reset_state()Stanislaw Halik
Also there's this evil `static' but it probably resulted in having it set to identity anyway.
2019-01-16tracker/pt: cleanup, declarations, lock scopeStanislaw Halik
2018-10-05silly busyworkStanislaw Halik
2018-07-13appease analyzerStanislaw Halik
2018-07-09cleanup onlyStanislaw Halik
2018-02-15clean up "static" and "constexpr" typesStanislaw Halik
- use `static constexpr inline' to avoid requiring explicit declarations in object code - use `const Foo* const' to maybe put into readonly binary segment (at least for ELF DSOs) - `constexpr' in function scope has storage, avoid `static' - don't use `constexpr' where there's no advantage, like arrays We'd like to avoid overhead of atomic initialization for each function call. No idea how `static constexpr' requiring storage in the standard plays with atomic initialization requirement. Hearsay points that `constexpr' without `static' in block scope behaves more to our liking. It's all hazy though. I'm not 100% sure if `static inline constexpr' has any storage. Hopefully none, like a #define, and stuff bigger than registers gets coalesced within the same module, with small stuff being immediates.
2018-01-18compat/util: retireStanislaw Halik
Adjust usages.
2018-01-12tracker/pt: isolate point extractor and image typeStanislaw Halik
Issue: #718
2018-01-11tracker/pt: allow for reuseStanislaw Halik
Issue: #718 This allows for replacing the camera and point extractor code. See `module.cpp' and `pt-api.hpp`.
2018-01-10tracker/pt: reset dynamic pose on centerStanislaw Halik
2017-09-22tracker/pt: add color extraction modesStanislaw Halik
2017-08-14tracker/pt: move Affine class to cv/Stanislaw Halik
2017-07-07tracker/pt: don't return zero pose on failureStanislaw Halik
Issue: #644
2017-06-18tracker/pt: fix broken commitStanislaw Halik
Already pushed, damn
2017-06-12tracker/pt: cleanupStanislaw Halik
Also, changing "f" typedef to "float" won't break the build anymore.
2016-12-16tracker/pt: refactor camera info handlingStanislaw Halik
- Pass `struct CamInfo' rather than several elements separately - Reformat - Return `struct CamInfo' together with the frame since then it's always valid - Move the focal length formula into `struct CamInfo' - Remove incorrect focal length formula rather than #if 0 - Pass some stuff by reference and not by pointer
2016-11-12tracker/pt: refactorStanislaw Halik
- separate .{cpp,hpp} for few classes - don't include namespaces globally; harmless but looks bad anyway - class with all public members to struct
2016-10-19tracker/pt: minor cleanupStanislaw Halik
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-10-07tracker/pt: C++11-izeStanislaw Halik
2016-09-20typoStanisław Halik
2016-09-16tracker/pt: get rid of pt_types classStanislaw Halik
2016-08-12all: rename modules s#^opentrack-##. and opentrack -> apiStanislaw Halik
Adjust usages.
2016-07-31tracker/pt: use max distance for dynamic poseStanislaw Halik
2016-07-19tracker/pt: reduce lockingStanislaw Halik
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: move pi constant to headersStanislaw Halik
2016-06-14tracker/pt: use unsigned index where ableStanislaw Halik
2016-05-13many: remove unneeded implicit type conversion double <-> floatStanislaw Halik
2015-12-18tracker/pt: reduce mutex contentionStanislaw Halik
2015-12-18tracker/pt: nix unusedStanislaw Halik
2015-10-30move to subdirectory-based build systemStanislaw Halik
Closes #224