fix issue#6 #7
Merged
fix issue#6 #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix #6.
Details
The root cause was that the Python bindings exposed SpatialML::camera_extrinsics::extrinsics directly (see the old implementation around bindings/spatialmp4.cpp:175), and that field is a cv::Matx<double,4,4>. Pybind11 doesn’t know
how to convert cv::Matx (a fixed-size OpenCV matrix) into a Python object out of the box, so whenever CameraExtrinsics.extrinsics or CameraExtrinsics.as_cvmat() ran, pybind11 couldn’t turn the C++ return value into something Python
understands and raised TypeError: Unregistered type : cv::Matx<double, 4, 4>. Switching the binding to return Eigen matrices—which pybind11 does support—resolved the conversion error.