Thomas Schöps

Thank you very much for this and the WIP PR. It seems to me that this one should be merged only once the other one is also ready, since libvis...

Unfortunately, I don't know what could cause this given that the driver version should theoretically be sufficient. Two things to try might be: * In case you haven't, restart the...

I think that there is already a file `points.yaml` among the state files that contains the optimized (deformed) pattern point positions, and it should be simple to compute the original...

This is where the feature detector is constructed (it is only allocated if needed): https://github.com/puzzlepaint/camera_calibration/blob/846bb5282a23b68e9fd7f3d240f7c979a016dea6/applications/camera_calibration/src/camera_calibration/main.cc#L462 This then builds the map from feature IDs to positions using `GetCorners()` (if image directories...

Regarding excessive computation time: If I remember correctly, the computation time highly depends on the total number of feature points in all used patterns. This is because the corresponding variables...

While I don't know for sure what the issue is here, I would suspect that it has something to do with separable compilation of CUDA code. Googling something like "visual...

Would it be an option to calibrate the two views as separate cameras within a camera rig, using the central-generic model for each view, instead of using the noncentral model?...

Assuming this concerns the generic camera models: The distortion center is not estimated separately for those, instead it (and any other parameters that parametric models handle explicitly) is handled implicitly...

@WJinhai This is because they model radial distortion explicitly. Therefore, they need to know this center explicitly to be able to model it accurately. However, a generic model can represent...

Which camera model does this question refer to?