Skip to content

Conversation

@B1ueber2y
Copy link
Contributor

Sincere request to re-enable this feature. Exposing this interface will make dev much easier when problem is constructed with pyceres, for example, with pycolmap.cost_functions.ReprojErrorCost and non-identity keypoint covariance (e.g. with a scaled covariance due to resizing). Given that we expose the pycolmap.cost_functions module there is no downside to support this.

@B1ueber2y B1ueber2y requested a review from ahojnnes December 18, 2024 16:24
@B1ueber2y B1ueber2y changed the title Re-enable interface support for covariance estimation from a raw Ceres::Problem Re-enable interface support for covariance estimation from a Ceres::Problem instance Dec 18, 2024
@B1ueber2y B1ueber2y enabled auto-merge (squash) December 18, 2024 16:48
@B1ueber2y B1ueber2y merged commit d57639e into colmap:main Dec 18, 2024
16 checks passed
@B1ueber2y B1ueber2y deleted the features/improve_covariance branch December 18, 2024 19:12
HernandoR pushed a commit to HernandoR/colmap that referenced this pull request Dec 30, 2024
…roblem instance (colmap#3061)

Sincere request to re-enable this feature. Exposing this interface will
make dev much easier when problem is constructed with pyceres, for
example, with ``pycolmap.cost_functions.ReprojErrorCost`` and
non-identity keypoint covariance (e.g. with a scaled covariance due to
resizing). Given that we expose the ``pycolmap.cost_functions`` module
there is no downside to support this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants