-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
CorrespondenceEstimation with different point types #329
Comments
From what I can tell, no correspondence classes are actually instantiated under normal compilation (making the above changes compiles fine for me). Adding a
to a random file caused the same errors you reported. The errors also occur with or without your changes, I suspect nobody has really tried using two different point types like this. |
But the changes do make sense, no? There is a clear error with the typedefs and the runtime check for the template arguments to be the same is pretty useless, no? :-) |
I've posted a fix, but it makes it less efficient for same-type correspondences (requires creating a full temporary copy even though it's not strictly necessary). |
We could use |
Fixes PointCloudLibrary#329. Credits for @aichim, @jpapon and @taketwo . Added unit test for XYZ point types.
Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs. |
Hi guys,
I think I just opened a can of worms in the CorrespondenceEstimation class and it's quite annoying.
So, I am trying to do the following:
This initially gave me an error of not being able to convert from PointXYZ to PointNormal in the PCL code, so I hunted for bugs and did the following changes:
In the diff above you will also see that I took out the parts where we consider the point types to be the same. I think these tests are wrong, as they are runtime tests, and the compiler is going to compile everything anyway, and will produce errors.
After these changes, I am now getting pages and pages of errors of the form:
The text was updated successfully, but these errors were encountered: