-
Notifications
You must be signed in to change notification settings - Fork 337
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
ROS2 port pcl_ros/filters #383
Conversation
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
Signed-off-by: Daisuke Sato <[email protected]>
If I'm being honest, this is such an overwhelmingly large PR that I'm not sure I'll ever have time to fully review it to the point that I would be fine merging it. If you could break this down into a series of PRs, that would be much more likely to be merged in (and you'd get more fake internet points for contributions 😉 ). Perhaps 1 PR for the preliminaries, and then a PR for every filter separately (or a couple if short). Large PRs are incredibly difficult and time intensive to review all at once. I can easily spend 15 minutes every couple of days reviewing, but its difficult for me to spend 4 hours all in 1 sitting on it. I'd rather be up front with you, cards on the table, than let this languish silently. |
@SteveMacenski |
I migrated a subset of the filters into a smaller PR if it helps: I hadn't realized you were already working on it. |
@asymingt It helps! I may not have time to do the last piece of PR soon (maybe next week). |
I'm sure @daisukes doesn't mind @asymingt! Please reopen any PRs that aren't already having others from @daisukes open. @daisukes, you might want to tell him what you're working on so neither of you have to do duplicate porting :-) @asymingt I'd prefer smaller PRs (1-2 filters each). It makes it much easier for me to review and for us to do cycles. The more code, the longer of a delay it will be for review cycles (since review times grow non-linearly with PR size) |
These three filters are not migrated yet.
|
Cool -- I'll set up three PRs to each add each one in isolation. |
Done, here they are:
Let me know if you want to handle |
Oh, I missed it. Please handle it. Thank you! |
OK -- I'm starting to hate the linter in Jenkins. Is there an easy way to to do it pre-commit? |
|
Totally, but wheres the |
@SteveMacenski and @daisukes : Looks like I missed a key fact that the filter-specific ros2 parameters are meant to be declared in their constructor. I'll need to go back and take them out of the EDIT: I refactored all four PRs and they are ready for a review. I'm ignoring the |
It's done here: Do you all perhaps have a turnaround time on the reviews? I don't want them to bit rot. |
They're in my queue but admittedly perception_pcl is not on my priority list like Nav2 is. PCL_ROS only gets time when I'm able to find it on a volunteer basis. They're not forgotten, they're in my notifications tray to get to. |
I completely forgot to close it. Thank you for the support, @asymingt and @SteveMacenski ! |
This is a ros2 porting of pcl_ros filters.
I have been working on my ROS2 migration project and found that most of the pcl_ros functions are not ported yet.
https://discourse.ros.org/t/call-for-help-pcl-ros-for-ros2/15131
I have just ported filters because I need them, and they could be ported without type adaptation REP-2007.
https://github.com/ros-perception/perception_pcl/blob/melodic-devel/pcl_ros/src/pcl_ros/filters/filter.cpp#L130
contributions
This work is based on #255