-
-
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
Compatibility for Spin Image features #1260
base: master
Are you sure you want to change the base?
Conversation
A new feature signature SISignature153 replaces Histogram<153>. SISignature153 is registered to by usable with algorithms like kd-tree search.
Just out of curiosity, why is it necessary with a new point type here? It On Mon, Jun 15, 2015 at 10:09 AM, Jens Garstka [email protected]
|
Histogram<153> is not a registered type when compiling PCL. Hence you'll get linker errors if you try to use Histogram<153> with algorithms like Kdtree. |
Ah, yes you're right! I overlooked that. But shouldn't Histogram be removed then? I mean, otherwise we will have two On Mon, Jun 15, 2015 at 10:30 AM, Jens Garstka [email protected]
|
Histogram is a generic point structure with the ability to use it with different N. It is not exclusively reserved for SpinImage and is still required by other classes, e.g., CRHEstimation. |
Yes, I know - but it's quite bad having two classes encapsulating the same On Mon, Jun 15, 2015 at 11:06 AM, Jens Garstka [email protected]
|
Sure, one could do. But what would be the benefit. It is only consistent to implement the signature of a SpinImage feature in the same manner as it is done for all other features. |
... and by the way: there are no two classes encapsulating the same type of data, since you'll not find instances of Histogram<153> in the code anymore. |
Yes, you're right - types such as e.g. FPFHSignature33 and VFHSignature308 I guess then it would be wise to completely remove Histogram, since it is On Mon, Jun 15, 2015 at 2:04 PM, Jens Garstka [email protected]
|
+1 here, @taketwo what do you think? |
The changes look good, but I must admit I never used any of the affected classes in PCL. |
I would propose to mark |
If we plan to deprecate, maybe it makes sense to deprecate already now, so that users of 1.8.0 see the warning and (hopefully) adapt their code? |
I would vote for that! On Mon, Oct 19, 2015 at 10:57 AM, Sergey Alexandrov <
|
So. Shall we deprecate? @jgarstka can you include deprecation in this pull request? |
This pull request has been automatically marked as stale because it hasn't had Come back whenever you have time. We look forward to your contribution. |
This pull request has been automatically marked as stale because it hasn't had Come back whenever you have time. We look forward to your contribution. |
This pull request has been automatically marked as stale because it hasn't had Come back whenever you have time. We look forward to your contribution. |
A new feature signature SISignature153 replaces Histogram<153>.
SISignature153 is registered to by usable with algorithms like
kd-tree search.