BFMatcher Indexing not suited for large scale (Bug #3221)


Added by Dominik Van Opdenbosch over 11 years ago. Updated over 9 years ago.


Status:Incomplete Start date:2013-08-14
Priority:Low Due date:
Assignee:Maria Dimashova % Done:

0%

Category:features2d
Target version:2.4.10
Affected version:2.4.0 - 2.4.6 Operating System:Linux
Difficulty:Easy HW Platform:x64
Pull request:

Description

The way the indexing is done in the Brute Force Matcher Implementation is not suited for large scale scenarios.
The indexing is limited by the use of 32bit signed integer instead of (unsigned) 64 bit integer where available (long int):

modules/features2d/src/matchers.cpp
CV_Assert( (int64)imgCount*IMGIDX_ONE < INT_MAX )


Associated revisions

Revision 281ce7a0
Added by Alexander Alekhin over 10 years ago

Merge pull request #3221 from asmorkalov:ocv_2.4.10_version_inc

History

Updated by Sergei Nosov over 11 years ago

Hi, Dominik!

I'm not sure it's clear what you actually want to say. Could you, please, be more specific?

  • Status changed from New to Incomplete
  • Target version set to 2.4.7

Updated by Mathieu Barnachon over 11 years ago

Did you mean: replace INT_MAX by INT64_MAX?
But update variable must be a int64 also.
Is it suitable for OpenCV to use 64 bits variables (for multi-plateform compatibility I mean)?

Updated by Alexander Smorkalov over 11 years ago

  • Target version changed from 2.4.7 to 2.4.8
  • Affected version changed from 2.4.6 (latest release) to 2.4.0 - 2.4.6

Updated by Alexander Smorkalov about 11 years ago

  • Target version changed from 2.4.8 to 2.4.9

Updated by Alexander Smorkalov almost 11 years ago

  • Target version changed from 2.4.9 to 2.4.10

Updated by Maksim Shabunin over 9 years ago

Issue has been transferred to GitHub: https://github.com/Itseez/opencv/issues/4615

Also available in: Atom PDF