Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some minor changes regarding sensor info #41

Merged
merged 6 commits into from
Sep 17, 2024
Merged

Conversation

luator
Copy link
Member

@luator luator commented Sep 17, 2024

Description

Several minor additions/fixes concerning the sensor info. See individual commits for details.

Based on answers to [this SO
question](https://stackoverflow.com/q/39932391),

- `virtual` should only should be used on the first appearance of a
  method (i.e. in the base class), and
- all child classes should use `override` (or `final` if appropriate).
If the `CalibratedCamera` is used, set also the distortion_coefficients
in sensor_info_.

When using `Camera`, there is no distortion, so just leaving them at
zero (which they are initialised to by default) should be correct.
So it can conveniently be accessed in back-end code (or when just using
the driver class directly).
Add function `print_tricamera_sensor_info` to the utils module.  It
pretty-prints the data from TriCameraInfo in a table.

Add this here, so we don't have to duplicate the code in all the scripts
where we want to print this.
@luator luator self-assigned this Sep 17, 2024
@luator luator merged commit 701b773 into master Sep 17, 2024
5 checks passed
@luator luator deleted the fkloss/sensor_info branch September 17, 2024 15:17
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.

1 participant