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

mnaveau ubuntu20.04 ros2 #93

Conversation

MaximilienNaveau
Copy link

@MaximilienNaveau MaximilienNaveau commented Dec 11, 2021

Description

Implement the ROS2 interface for the SoT.

How did I testes?

Ran the unit-test on my laptop and on the github actions

Ubuntu20.04, ROS2 Continuous Integration

@MaximilienNaveau MaximilienNaveau changed the base branch from devel to foxy December 11, 2021 12:10
@MaximilienNaveau MaximilienNaveau linked an issue Jan 17, 2022 that may be closed by this pull request
@MaximilienNaveau
Copy link
Author

@nim65s

1/ could you checkout the gitlab CI to add ROS2? I naively think that the problem comes from the fact that ament (ROS2 equivalent of catkin cmake modules) is not found.

2/ Should we keep the gitlab CI at all, as the github actions covers the unit-tests?
Is there something special that the gitlab does? like the doc, or other uploads?

@olivier-stasse
Copy link
Member

@nim65s

1/ could you checkout the gitlab CI to add ROS2? I naively think that the problem comes from the fact that ament (ROS2 equivalent of catkin cmake modules) is not found.

2/ Should we keep the gitlab CI at all, as the github actions covers the unit-tests? Is there something special that the gitlab does? like the doc, or other uploads?

Dear @MaximilienNaveau thanks for the PR.
I would go for the second solution. The first one implies that ROS-2 should be present in robotpkg.
If we want to move on, let us drop this.

I will review your PR such that we can move on with it.

@olivier-stasse
Copy link
Member

olivier-stasse commented Feb 11, 2022

Dear @MaximilienNaveau thanks again for this huge PR.
I think that the work you have done on the publishing/subscribe part is very complementary with what I have done.

As for my feedback here is some general comments:

  • Could you apply a clang-format file similar to the one use by gitlab-ci ? They are places with 4 spaces and other with 2 spaces. We use to have a 2 spaces tabulation. You can also use the clang file from dynamic-graph (https://github.com/stack-of-tasks/dynamic-graph/blob/master/.clang-format). The latter has a 80 columns limit to be user friendly when being on the robot. I prefer to avoid line being too long, they are a pain to read, but 80 is a bit too stringent.
  • We should write more unit-tests and documentation.
  • All those remarks needs a lot of work, I would in favor of merging the PR and fix with commits later on.
  • i would suggest that we try the github actions from ROS-2

Again thanks a lot for the work !

Copy link
Member

@olivier-stasse olivier-stasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huge work.
Thanks a lot !

@olivier-stasse
Copy link
Member

And after rethinking over it I would remove dgb-ros1.cmake and dbg-ros2.cmake.
Keeping the compatibility with ROS-1 seems to be too much and will clutter the repo.

@olivier-stasse olivier-stasse merged commit f9c0760 into stack-of-tasks:foxy Feb 11, 2022
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.

Port of dynamic_graph_bridge to ROS-2 - Compiling
2 participants