Skip to content

Conversation

@juelg
Copy link
Contributor

@juelg juelg commented Jun 2, 2025

  • cameraset implementation are realized with composition instead of inheritance
  • camera specific settings such as resolution are at the camera config level not the cameraset level
  • multiple camerasets are possible, this allows to have realsense and digits both represented by a single camera wrapper
  • Limitation: currently there is only support for a common single frame rate, as otherwise the complexity would increase massively

@juelg juelg force-pushed the juelg/refactor-camera branch from 7739d57 to 3ebb182 Compare June 3, 2025 12:27
put base camera config into cpp code
@juelg juelg force-pushed the juelg/refactor-camera branch 4 times, most recently from ece7875 to e31c766 Compare June 4, 2025 16:28
@juelg
Copy link
Contributor Author

juelg commented Jun 4, 2025

@khaledmohamed00 I finished the camera refactoring. The only thing with which I am not happy atm is that we now have set of sets on the hardware part. It would be good to refactor the code that we only have the camera set which contains single cameras, but that would require to let the real sense class represent only a single camera. I have checked already that it should be possible to do so on the realsense API level.

- each camera can be configured individually
- HardwareCameraSet uses HardwareCamera interface with composition instead of inheritance
- BaseCameraConfig moved to cpp
- removed digit camera set wrapper as camera set wrapper is used now
@juelg juelg force-pushed the juelg/refactor-camera branch from e31c766 to e7f839e Compare June 4, 2025 19:00
@juelg juelg merged commit 70e7774 into master Jun 11, 2025
4 checks passed
@juelg juelg deleted the juelg/refactor-camera branch June 11, 2025 08:55
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