BestOf2NearestMatcher gives different result on second run (Bug #3579)
| Status: | Open | Start date: | 2014-02-27 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: |  Alexey Spizhevoy |
% Done: | 0% |
| Category: | stitching | ||
| Target version: | 2.4.10 | ||
| Affected version: | 2.4.8 (latest release) | Operating System: | Mac OSX |
| Difficulty: | HW Platform: | x64 | |
| Pull request: |
Description
When I excecute the folloing code twice with the exact same inputs, I get two different but similar results.
BestOf2NearestMatcher matcher(false, 0.3);
vector<MatchesInfo> temp_pairwise_matches = [...];
vector<ImageFeatures> temp_features = [...];
matcher(temp_features, pairwise_matches);
matcher.collectGarbage();
A little more info: I have spend a lot of time isolating the problem to this code. I create two different copies of BestOf2NearestMatcher and all input data is being cloned, so there is definitively no change in the input. The result on the first run is always the same and so is the result on the second and third run, and so on. But none of the results equals one of the previous results.
Associated revisions
Merge pull request #3579 from basheersubei:patch-1
History
Updated by Dinar Ahmatnurov about 11 years ago
- Status changed from New to Open
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/4709