Thomas Schöps

The `Project()` function uses an optimization process internally, which is expected to be slow. If your camera calibration does not change too often, it is thus likely helpful to cache...

In general, computing the relative pose between two cameras is not something that is related to the camera calibration project in this repository here, so I would consider it off-topic....

First, the calibration system was not designed for very strong fisheye lenses. The two issues I am aware of are: * The feature detector will at some point fail to...

I think that the CMake line from which this error originates is not relevant for compiling, just to organize the project in IDEs in a nicer way. While I don't...

Based on the description of undistortPoints [here](https://docs.opencv.org/3.4/da/d54/group__imgproc__transform.html#ga55c716492470bfe86b0ee9bf3a1f0f7e), it seems to first unproject the given input pixels and then optionally apply some further steps (with R and P) that are independent...

Sorry, but I don't really understand what the problem is. What exactly would you like to achieve? Do you think that the calculation should return the same value in both...

The generic camera models do not require or use focal length and optical center parameters. These parameters are only necessary for parametric models that include them, and they are not...

I would first like to note that the calibration process involves a full bundle adjustment step without constraints on the pattern geometry. This means that slightly imperfect patterns, such as...

> what do you think about quality of the calibration if we indeed force planarity and exact geometry of our pattern? My impression is that it is typically hard to...

Regarding PixelCornerProjector: I think that this should only be used by the stereo depth estimation tool, which is not required for the calibration process itself, and (due to lacking optimizations)...