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

Compatibility for Spin Image features #1260

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Compatibility for Spin Image features #1260

wants to merge 1 commit into from

Conversation

jgarstka
Copy link
Contributor

A new feature signature SISignature153 replaces Histogram<153>.
SISignature153 is registered to by usable with algorithms like
kd-tree search.

A new feature signature SISignature153 replaces Histogram<153>.
SISignature153 is registered to by usable with algorithms like
kd-tree search.
@andersgb1
Copy link
Contributor

Just out of curiosity, why is it necessary with a new point type here? It
has the exact same signature as the Histogram struct.

On Mon, Jun 15, 2015 at 10:09 AM, Jens Garstka [email protected]
wrote:

A new feature signature SISignature153 replaces Histogram<153>.
SISignature153 is registered to by usable with algorithms like

kd-tree search.

You can view, comment on, or merge this pull request online at:

#1260
Commit Summary

  • Compatibility for Spin Image features

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#1260.

@jgarstka
Copy link
Contributor Author

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.

@andersgb1
Copy link
Contributor

Ah, yes you're right! I overlooked that.

But shouldn't Histogram be removed then? I mean, otherwise we will have two
identical structs with different names.

On Mon, Jun 15, 2015 at 10:30 AM, Jens Garstka [email protected]
wrote:

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.


Reply to this email directly or view it on GitHub
#1260 (comment)
.

@jgarstka
Copy link
Contributor Author

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.

@andersgb1
Copy link
Contributor

Yes, I know - but it's quite bad having two classes encapsulating the same
type of data. It would imo be better to just register a Histogram<153>
instead of introducing a new struct.

On Mon, Jun 15, 2015 at 11:06 AM, Jens Garstka [email protected]
wrote:

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.


Reply to this email directly or view it on GitHub
#1260 (comment)
.

@jgarstka
Copy link
Contributor Author

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.

@jgarstka
Copy link
Contributor Author

... 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.

@andersgb1
Copy link
Contributor

Yes, you're right - types such as e.g. FPFHSignature33 and VFHSignature308
support your argument.

I guess then it would be wise to completely remove Histogram, since it is
becoming superfluous if we are using dedicated containers for all features.
But maybe that should be another PR...

On Mon, Jun 15, 2015 at 2:04 PM, Jens Garstka [email protected]
wrote:

... 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.


Reply to this email directly or view it on GitHub
#1260 (comment)
.

@jspricke
Copy link
Member

+1 here, @taketwo what do you think?

@taketwo
Copy link
Member

taketwo commented Oct 16, 2015

The changes look good, but I must admit I never used any of the affected classes in PCL.
The proposal to remove Histogram sounds a bit radical though.

@jspricke
Copy link
Member

I would propose to mark Histogram deprecated in a future version.

@taketwo
Copy link
Member

taketwo commented Oct 19, 2015

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?

@andersgb1
Copy link
Contributor

I would vote for that!

On Mon, Oct 19, 2015 at 10:57 AM, Sergey Alexandrov <
[email protected]> wrote:

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?


Reply to this email directly or view it on GitHub
#1260 (comment)
.

@taketwo
Copy link
Member

taketwo commented Nov 16, 2015

So. Shall we deprecate? @jgarstka can you include deprecation in this pull request?

@SergioRAgostinho SergioRAgostinho added the needs: author reply Specify why not closed/merged yet label Jul 14, 2016
@SergioRAgostinho SergioRAgostinho added this to the pcl-1.9.0 milestone Aug 22, 2016
@stale
Copy link

stale bot commented Dec 14, 2017

This pull request has been automatically marked as stale because it hasn't had
any activity in the past 60 days. Commenting or adding a new commit to the
pull request will revert this.

Come back whenever you have time. We look forward to your contribution.

@stale stale bot added the status: stale label Dec 14, 2017
@SergioRAgostinho SergioRAgostinho removed this from the pcl-1.9.0 milestone Jan 25, 2018
@stale stale bot removed the status: stale label Jan 25, 2018
@stale
Copy link

stale bot commented Mar 26, 2018

This pull request has been automatically marked as stale because it hasn't had
any activity in the past 60 days. Commenting or adding a new commit to the
pull request will revert this.

Come back whenever you have time. We look forward to your contribution.

@stale stale bot added the status: stale label Mar 26, 2018
@stale
Copy link

stale bot commented Feb 21, 2020

This pull request has been automatically marked as stale because it hasn't had
any activity in the past 60 days. Commenting or adding a new commit to the
pull request will revert this.

Come back whenever you have time. We look forward to your contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: author reply Specify why not closed/merged yet status: stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants