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

Modularize ROS2 packages and Docker images #45

Open
luca-byte opened this issue Nov 1, 2024 · 0 comments
Open

Modularize ROS2 packages and Docker images #45

luca-byte opened this issue Nov 1, 2024 · 0 comments
Assignees

Comments

@luca-byte
Copy link
Member

We want to separate the code in different ROS2 packages (reseq-core, reseq-digital-twin, reseq-sensors) and split them on two different docker images: the first will use Ubuntu Jammy with ROS, the second for the sensors only will need to deal with the RealSense peculiarities. We alse want to be alble to start both the containers with the same ROS2 configuration which will be passed to both, and provide a default configuration.

  • Most modules can use only the standard image (Ubuntu Jammy, arm64) like this (link)
  • The optional RealSense module will need some extra work
    • Either compile from source (as it is now)
    • Or use NVIDIA Isaac ROS (preferably)
      • Specifically the RealSense page
      • Or the other pages that explain how the container infrastructure work link.
      • We are specifically interested in the image compression at the moment since we have a CPU/bandwidth bottleneck
  • When splitting we are interested in separating also the ROS2 packages (link to EC’s task)
    • creating a dependency chain
    • and correctly identifying the dependencies for the single package
    • (core reseq, sensors, digital twin)
@luca-byte luca-byte self-assigned this Nov 12, 2024
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

No branches or pull requests

1 participant