Stanislaw Halik
Stanislaw Halik
A covariance or correlation matrix would be appropriate here. I don't fully understand why the PT calibrator uses a precision matrix, though.
I removed manual "camera offset" for translation. Every time I tried using it, it wasn't right. It now centers varying upon the centered position. Here's a WIP build. Note that...
I'm working on interconnect calibration. Calibration works, but the data isn't used yet.
I'll consider getting these settings back. Are there other examples where this setting is useful for you? Do you have any help with: - yaw caused by pitch - pitch...
Or other way of stating the same: Which of the axis influences another badly?
I wrote some working code for estimating axis interconnect. But it was too complex to use. Basically we had `6*6 - 6` buttons to calibrate each axis in relation to...
Now having that, we could have only 3 buttons (for yaw, pitch, and Z), estimating bleed over axis where it's the most visible. But don't expect it to remove bleed...
Seems like we're gonna need the camera offset implemented again based on the amount of complaints.
We definitely need a way to remotely operate opentrack programmatically or from the command line, but dbus isn't the right solution for this. It's too platform-specific, has a lot of...
The pose estimation code hasn't been updated since 2012. There were improvements to other parts of tracker/pt almost every year. I don't see any reason why the code would have...