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

Ros nodes e2e planner #286

Closed
wants to merge 7 commits into from
Closed

Ros nodes e2e planner #286

wants to merge 7 commits into from

Conversation

halil93ibrahim
Copy link
Collaborator

Hi,

I have started implementing both ROS1 and ROS2 nodes for end to end planner under this branch. I have a question regarding the ROS2 node implementation.

The gym environment I have provided with the learner is currently communicates with Webots and mavros through ROS1. So, the ROS nodes are supposed to interact with this environment. What should be the right strategy when I implement the ROS2 node. Should I have optional ROS2 communication for the gym environment? Or, should I bridge the communication between ROS1 and ROS2?

@passalis
Copy link
Collaborator

Hi Hallil, if you can directly support ROS2 (instead of using a bridge) without much effort then I think this would be better. @ad-daniel @stefaniapedrazzi what do you think?

I also converted this PR to draft until it is ready for review. If this is not the case, please revert it.

@passalis passalis marked this pull request as draft August 22, 2022 06:54
@halil93ibrahim
Copy link
Collaborator Author

Hi, I will try to put everything in ROS2.

@tsampazk tsampazk mentioned this pull request Oct 18, 2022
24 tasks
@halil93ibrahim
Copy link
Collaborator Author

Hi,

I have updated the end-to-end planner tool to be included the work in my recent paper. I have also completed ROS1 node which publishes the output of the planner as a target waypoint,

Unfortunately, I could not complete ROS2 node, because of the issues faced with 2021a version of Webots and ROS2. While trying to solve this, we could merge the already implemented part and complete ROS2 part in another pr. What do you think? In that case, should I target another branch or, is this PR works?

@halil93ibrahim halil93ibrahim marked this pull request as ready for review November 14, 2022 06:57
@tsampazk
Copy link
Collaborator

What do you think? In that case, should I target another branch or, is this PR works?

Hello @halil93ibrahim! I think that it would be better to target develop with this PR as it will no longer include a ROS2 node and it involves changes in a lot of files other than the ROS2 workspace. When you manage to make the ROS2 node work, you can add it later in a new PR that will target the ros2 branch.

@tsampazk tsampazk self-requested a review November 14, 2022 08:32
@halil93ibrahim
Copy link
Collaborator Author

Ok, I am closing this PR and will create a new one targeting develop.

@halil93ibrahim halil93ibrahim deleted the ros-nodes-e2e-planner branch November 14, 2022 10:21
@tsampazk
Copy link
Collaborator

Oh you can retarget the PR by editing it, but it's ok if you already done the work.

@halil93ibrahim halil93ibrahim restored the ros-nodes-e2e-planner branch November 14, 2022 10:26
@halil93ibrahim
Copy link
Collaborator Author

I did not know and had already created a new PR.

@tsampazk
Copy link
Collaborator

I did not know and had already created a new PR.

It's ok no problem, sorry for not mentioning it originally!

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.

None yet

3 participants