forked from ros-perception/image_pipeline
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/rolling' into rolling
- Loading branch information
Showing
64 changed files
with
1,598 additions
and
1,110 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,38 @@ | |
Changelog for package camera_calibration | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
6.0.3 (2024-08-20) | ||
------------------ | ||
* Refactoring calibration code (`#1000 <https://github.com/ros-perception/image_pipeline/issues/1000>`_) | ||
Co-authored-by: Alejandro Hernández Cordero <[email protected]> | ||
* Contributors: Myron Rodrigues | ||
|
||
6.0.2 (2024-07-23) | ||
------------------ | ||
|
||
6.0.1 (2024-07-22) | ||
------------------ | ||
* Change camera info message to lower case (`#1005 <https://github.com/ros-perception/image_pipeline/issues/1005>`_) | ||
Change camera info message to lower case since message type had been | ||
change in rolling and humble. | ||
[](https://github.com/ros2/common_interfaces/blob/rolling/sensor_msgs/msg/CameraInfo.msg) | ||
* Formatting calib code before refactoring (`#999 <https://github.com/ros-perception/image_pipeline/issues/999>`_) | ||
As discussed in `#975 <https://github.com/ros-perception/image_pipeline/issues/975>`_ and `#973 <https://github.com/ros-perception/image_pipeline/issues/973>`_ | ||
doing the linting first. | ||
using style from | ||
[here](https://github.com/ament/ament_lint/blob/rolling/ament_pycodestyle/ament_pycodestyle/configuration/ament_pycodestyle.ini) | ||
* Added stereo calibration using charuco board (`#976 <https://github.com/ros-perception/image_pipeline/issues/976>`_) | ||
From `#972 <https://github.com/ros-perception/image_pipeline/issues/972>`_ | ||
Doing this first for rolling. | ||
This was a TODO in the repository, opening this PR to add this feature. | ||
- The main issue why this wasn't possible imo is the way `mk_obj_points` | ||
works. I'm using the inbuilt opencv function to get the points there. | ||
- The other is a condition when aruco markers are detected they are | ||
added as good points, This is fine in case of mono but in stereo these | ||
have to be the same number as the object points to find matches although | ||
this should be possible with aruco. | ||
* Contributors: Myron Rodrigues, SFhmichael | ||
|
||
6.0.0 (2024-05-27) | ||
------------------ | ||
* fix: cv2.aruco.interpolateCornersCharuco is deprecated (`#979 <https://github.com/ros-perception/image_pipeline/issues/979>`_) | ||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,8 @@ | ||
API Documentation | ||
================= | ||
|
||
.. autoclass:: camera_calibration.calibrator.MonoCalibrator | ||
.. autoclass:: camera_calibration.mono_calibrator.MonoCalibrator | ||
:members: | ||
|
||
.. autoclass:: camera_calibration.calibrator.StereoCalibrator | ||
.. autoclass:: camera_calibration.stereo_calibrator.StereoCalibrator | ||
:members: |
This file contains 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
This file contains 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
Oops, something went wrong.