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

NearbyPoint bug fix and minor fixes #46

Merged
merged 3 commits into from
Feb 10, 2017
Merged

Conversation

fabiencastan
Copy link
Member

No description provided.

@@ -863,9 +863,9 @@ void cctagDetection(
/* identification in CUDA requires a host-side nearby point struct
* in pinned memory for safe, non-blocking memcpy.
*/
if( markers.size() > 60 ) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lcalvet: is that ok for you?

@lcalvet
Copy link
Member

lcalvet commented Nov 28, 2016

The scale should not be exposed as it could be interpret as the scale of a point of interest, typically like in SIFT, SURF, etc. and could therefore be used for sorting purpose, etc. which doesn't make any sense.
The quality must not be exposed as its value its use is meaningless outside of the library. At the moment, it reveals neither the quality of extraction nor the identification one.

@simogasp simogasp added this to the 2016_11 milestone Nov 28, 2016
@fabiencastan
Copy link
Member Author

  1. Ok, so if the name "scale" is confusing it could be nice to rename it.
  2. Is there a way to get an information about the quality of extraction?

@lcalvet
Copy link
Member

lcalvet commented Nov 28, 2016

  1. The name is not confusing for contributors but will be misused by users if exposed.
  2. Not a clean way yet, that is why it is not exposed.

@simogasp simogasp modified the milestones: V1.0.0, 2016_11 Dec 1, 2016
@fcastan fcastan force-pushed the dev_nearbyPoint_fixes branch 2 times, most recently from 629688e to 1b4ce2f Compare February 6, 2017 09:43
@fabiencastan
Copy link
Member Author

I removed the commit which expose the scale & quality.
@lcalvet Can you merge?

@fabiencastan fabiencastan requested a review from lcalvet February 6, 2017 09:45
@fcastan fcastan force-pushed the dev_nearbyPoint_fixes branch from 1b4ce2f to ebc8a82 Compare February 6, 2017 10:53
@fabiencastan fabiencastan merged commit b6ec156 into develop Feb 10, 2017
@fabiencastan fabiencastan deleted the dev_nearbyPoint_fixes branch February 10, 2017 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants