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

Port Image_pipeline on ROS2 #360

Closed
7 tasks done
yechun1 opened this issue Sep 30, 2018 · 13 comments
Closed
7 tasks done

Port Image_pipeline on ROS2 #360

yechun1 opened this issue Sep 30, 2018 · 13 comments
Labels

Comments

@yechun1
Copy link
Contributor

yechun1 commented Sep 30, 2018

Image_pioeline porting status: (updated on 7/8/2019)

@yechun1
Copy link
Contributor Author

yechun1 commented Oct 16, 2018

Could image_pipeline's owner/maintainer please help to create ros2 branch for ros-perception/image_pipeline?

@yechun1
Copy link
Contributor Author

yechun1 commented Oct 23, 2018

@mjcarroll thanks for help to create ros2 branch, first PR to enable ros2 depth_image_proc is ready on #362.

@jacobperron
Copy link
Contributor

Any update on stereo_image_proc?

@SteveMacenski
Copy link
Member

SteveMacenski commented Sep 10, 2019

I can tell you @JWhitleyAStuff and I aren't thinking about it. I had alot of the ROS2 work in this repo scheduled post-ROSCon as I'm a little preoccupied with Navigation2 and slam toolbox.

@jacobperron is that something you're motivated to look at?

@yechun1
Copy link
Contributor Author

yechun1 commented Sep 10, 2019

I tried to port stereo_image_proc in the beginning of the year but blocked by image_proc which is not ready then. And now the image_proc has been ported and stereo_image_proc porting could be continue, but very sorry that I have no resource on this right now.
It would be glad if some one could have a time to work on it. Below is previously patch(not fully completed) just for reference.

port ros2 stereo_image_proc: yechun1@e9993be
on (https://github.com/yechun1/image_pipeline/tree/ros2_stereo_image_proc)

@klintan
Copy link
Contributor

klintan commented Sep 11, 2019

@yechun1 one version of image_proc is actually already merged, unfortunately it is not possible to run it as a component yet, but I'll put in some PRs for that. However I think it might still be considered "ready/done" for image_pipeline. (at least as a initial release candidate)

edit: and the PR you are referencing for image_proc is merged and closed :)

@jacobperron
Copy link
Contributor

@jacobperron is that something you're motivated to look at?

@SteveMacenski I don't have the bandwidth at the moment, I'll let you know if things change.

@SteveMacenski
Copy link
Member

@jacobperron that doesn't surprise me in the slightest 😉

@jacobperron
Copy link
Contributor

FYI, I have some bandwidth now and will start porting stereo_image_proc.

@laszloturanyi
Copy link

laszloturanyi commented Dec 11, 2019

Hi,
I managed to port stereo_image_proc some days ago. There is still some work to do to pass all the tests but now it can function.

@jacobperron you do not have to do it from scratch I rebased it to your jacob/ros2_image_processor
you can find a link to my fork. (https://github.com/laszloturanyi/image_pipeline/tree/ros2_stereo_image_proc)

I would be glad if you could have a look at it I have limited capacity to finish this but maybe we can find a way to do this efficiently.

Also some other notes:

  • .cfg files should removed (not only in stereo_image_proc) after comments are copied and parameter limits are handled correctly.
  • launch file is still the old one from ROS1
  • QoS policy is not consistent in image_pipeline. e.g disparity output of depth_image_proc will not be received by image_view nodes because the latter uses default profile while the first uses sensor data profile

@jacobperron
Copy link
Contributor

@laszloturanyi Thanks for sharing your effort! I'm happy to build on your fork if you don't have the time to finish the port.

@laszloturanyi
Copy link

@jacobperron that would be great. I added you as collaborator.

@jacobperron
Copy link
Contributor

See #486 for a port of stereo_image_proc.

@laszloturanyi I ended up not basing my fork on yours, as I had already done some of the same preliminary refactoring as you. It would be great if you could help review/try out the proposed port :)

I'll be adding support for parameter limits/reconfiguring shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants