-
Notifications
You must be signed in to change notification settings - Fork 653
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
Containers and PCL point type for backwards compatibility #347
base: melodic-devel
Are you sure you want to change the base?
Conversation
We should have this also in the master for |
container_ptr_ = getContainer(default_container_.second); | ||
} | ||
ROS_WARN_STREAM("Using default container \"" << container_name << "\"!"); | ||
ROS_WARN_STREAM("Please use the \"container\" param with one of the following container names: " << container_list.str()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please either do one of the following:
- Add the
container
parameter to all launch files and set it to the un-organized default ofPointCloudXYZIR
; or - Set this to be an
INFO
statement instead of a warning.
Having the new default value cause a warning seems problematic and could unnecessarily alarm users. I would prefer the first option since it should also be accompanied by some documentation with the possible values in the launch file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also prefer the first option! Will do that.
} | ||
EIGEN_ALIGN16; | ||
|
||
}; // namespace velodyne_pointcloud |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we also define the PointXYZIRT in terms of a PCL structure so people can use it in the same way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes for melodic that makes sense. For noetic, I'll move this to the velodyne_pcl package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This item still needs to be done.
@spuetz Can you please address my concerns? After that, I'll see if I can find a package to test with. |
@spuetz ping for changes. |
@spuetz Any update here? |
Sorry for the late reply. I'll have time in two weeks to finish this. |
Thanks, @spuetz! |
@spuetz ping |
@spuetz Still two items remaining when you can make time. |
@spuetz Can we get this wrapped up? |
Any update on this? @spuetz @JWhitleyWork |
ca6c24b
to
0305426
Compare
Rebased on current |
This is a possible solution for #340 for melodic.
point_type.h
is added again.organized_cloudXYZIRT.cc
.Things to do before merging / releasing
point_type.h
should test this.velodyne_pcl
package (Velodyne pcl #335)convert.h
andtransform.h
, since it more or less identical now. (Unify tf frame parameters between transform and cloud nodes (Backport of #344 to Melodic) #351)