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

Building on Humble with Colcon #44

Open
beshankulapala opened this issue May 25, 2023 · 10 comments
Open

Building on Humble with Colcon #44

beshankulapala opened this issue May 25, 2023 · 10 comments

Comments

@beshankulapala
Copy link

Is there a port or guide to build this package on humble ? On humble catkin is having all sorts of issues, and lots of forums point to Colcon as the tool to build. Appreciate your help. Newbie here, sorry if this is not the right place to ask this question. Thanks !

@Timple
Copy link
Member

Timple commented May 25, 2023

This package is not yet ROS2 compatible. Some effort has been made on the galactic branch.

Can you try that branch to see if it works?

@joeldushouyu
Copy link

joeldushouyu commented Jun 7, 2023

It did compile with Galactic !

@joeldushouyu
Copy link

I am wondering if this has a ros2 version documentation.

I am willing to help testing this package in the ros2 environment if needed.

@Timple
Copy link
Member

Timple commented Jun 8, 2023

We have discussed this internally and we'll make an effort to support ros2 humble as well. I'll keep you posted!

@mikolodz
Copy link

Hi @Timple ! What's the current status of the ROS2 branch? Should I consider using it in my simulation or is it highly unlikely that it's going to be usable in the nearest future? Thank you a lot!

@Timple
Copy link
Member

Timple commented Jun 15, 2023

It should be operational for Humble. Please go ahead and try it out!

edit: documentation etc are not up to date yet.

@mikolodz
Copy link

mikolodz commented Jun 16, 2023

It should be operational for Humble. Please go ahead and try it out!

edit: documentation etc are not up to date yet.

Hi Timple!

I've successfully build the project with your full_coverage_path_planner package and all the dependencies (at least the ones I'm aware of). But I'm not sure how to run the test examples.

I have copied the launch files into the ./install/full_coverage_path_planner/share/full_coverage_path_planner/ folder.

When I try to run the launch file example I'm getting the error:

$ ros2 launch full_coverage_path_planner test_full_coverage_path_planner.launch 
[INFO] [launch]: All log files can be found below /home/administrator/.ros/log/2023-06-16-15-08-37-447741-administrator-VirtualBox-118378
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught exception when trying to load file of format [launch]: Error trying to process rule "substitution":

Unknown substitution: find

Maybe you could give me some hints how to launch the examples? I've read your documentation in this repo, but it seems not to apply to the ros2 branch.
Thank you!

edit:
I replaced the substitutions "find" with "find-pkg-share" within the launch file and the error changed to:

ros2 launch full_coverage_path_planner test_full_coverage_path_planner.launch
[INFO] [launch]: All log files can be found below /home/administrator/.ros/log/2023-06-16-16-18-30-170012-administrator-VirtualBox-119430
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught exception when trying to load file of format [launch]: Attribute exec of type <class 'str'> not found in Entity node

It's the first time I'm trying to fix a launch file, so I'm not sure what I'm doing.. rotfl

edit 2:
Migration process for launch files is described here:
Migrating launch files from ROS 1 to ROS 2

I tried to apply most of the changes, but the error message is still the same which doesn't help with debugging. Also, when using --debug param in the launch command is not helping, because I'm getting no trace about which particular line in the xml launch file causes the error.

ros2 launch full_coverage_path_planner test_full_coverage_path_planner.launch --debug

I assume that you must have some testing script that you've beed using during the migration process to Ros2. Could you consider sharing it here or in the repo? Even if it's just a simple dirty snippet, it would help a lot! I would really appreciate that!

@mikolodz
Copy link

mikolodz commented Jul 3, 2023

Hi @Timple,
By any chance could you give me some hints on how should I proceed?
It's been two weeks since I'm stuck and I'd really love to take a chance and test your module.

Thank you so much!

@rikhsitlladeveloper
Copy link

Hi @Timple, By any chance could you give me some hints on how should I proceed? It's been two weeks since I'm stuck and I'd really love to take a chance and test your module.

Thank you so much!

Hello @mikolodz.

Did you get any update?

I am also starting to use this package for ROS2 Humble. Getting error for launching.
If you have any update pls share.
Thanks

@mikolodz
Copy link

Hi @Timple, By any chance could you give me some hints on how should I proceed? It's been two weeks since I'm stuck and I'd really love to take a chance and test your module.
Thank you so much!

Hello @mikolodz.

Did you get any update?

I am also starting to use this package for ROS2 Humble. Getting error for launching. If you have any update pls share. Thanks

Hello, no, I didn’t succeed.

Maybe you could take a look into the fields2cover lib (2.0)? In the opennav_coverage ROS2 project, there is a pull request regarding the official support of the F2C. Unfortunately, It’s frozen from a while now, because it failed the tests.

You can refer to this issue (with the F2C 2.0 feature list):
Fields2Cover/Fields2Cover#73 (comment)

And this PR (integration with ROS2):
open-navigation/opennav_coverage#53 (comment)

If you find a way to make it running (F2C or FCPP), please let me know! :)

Regards!

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

5 participants