You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In main.cpp the following code //Sorting keypoints by deacreasing order of strength vector<**int**> responseVector; for (unsigned int i =0 ; i<keyPoints.size(); i++) responseVector.push_back(keyPoints[i].response);
Since the response of a cv::Keypoint is a float value, I think that the responseVector should be float as well instead of int. In fact, if other detectors than FAST are used, the response vector is going to be populated of zeros because the range is different.
The text was updated successfully, but these errors were encountered:
@lgalardini you are right. it is a bug. cv::KeyPoint::response returns float . Reference.
I will fix it whenever I have time. Meanwhile, since you discovered this, you can create Pull request for this issue. Thank you for your contribution to the project!
Hello everyone,
In main.cpp the following code
//Sorting keypoints by deacreasing order of strength vector<**int**> responseVector; for (unsigned int i =0 ; i<keyPoints.size(); i++) responseVector.push_back(keyPoints[i].response);
Since the response of a cv::Keypoint is a float value, I think that the responseVector should be float as well instead of int. In fact, if other detectors than FAST are used, the response vector is going to be populated of zeros because the range is different.
The text was updated successfully, but these errors were encountered: