LATCH descriptor does not seem to work well on my dataset

[LingyuMa]

@mdaiter I have tried the LATCH binary and LATCH unsigned, it seems both of them work very well on my image set (it seems there are less features detected and much less matches found), is there any suggestions to tune the parameters or something?

[LingyuMa]

Also, the matching is still not fast even I use GPU_LATCH,is there any way to speed it up?

[mdaiter]

@LingyuMa what's your dataset and what numbers are you getting?

[mdaiter]

@LingyuMa I also set the ratio parameter to 0.99 when matching: binary descriptors are sensitive to those sorts of changes, and these fluctuations can seriously kill matching ability.

[LingyuMa]

I have also changed that to 0.99

[LingyuMa]

I have attached the image set and matches.bin, can you have a look?
https://drive.google.com/file/d/0BwWAt5w3811WdG16Z1ZKRGpVTFk/view?usp=sharing
https://drive.google.com/file/d/0BwWAt5w3811WV1U5Wm9hTEdGTk0/view?usp=sharing

[LingyuMa]

@mdaiter What parameters are you using for matching?

[mdaiter]

@LingyuMa I'm just using -r 0.99 . That's it...hm. How many putatives do you get, and how many geometrics? Are you using -g e or -g f?

[LingyuMa]

@mdaiter Can you run my dataset in your computer (to see what will happen)? I am using fundamental matrix for filtering, so it is -g f. I have attached my matches.f.bin, not sure how to check it.

[mdaiter]

./bin/openMVG_main_exportMatches -i outputLatch/sfm_data.json -d outputLatch -m outputLatch/matches.putative.bin -o matches will give you all of your matcher data back and export it to svgs. Curious to see the numbers.

[LingyuMa]

it seems it gave me a bunch of svg to show matches, is there a way to show the total number?

[LingyuMa]

@mdaiter for matches.f.bin, All I can say is that it gave me 136 image pairs. The pairs seem to be reasonable, though the number is 49.5MB, though it is much less than the sift (209.4MB), I can also see since the matching becomes sparse when it comes to LATCH

[mdaiter]

The total number between each pair appears right before the end of the SVG file. x_y_n_.svg is the format, where x is the first ID of the image, y is the second ID of the image, and n is the number of matches between images

[LingyuMa]

Here are the two output matches svg files screenshots

[LingyuMa]

@mdaiter the second image is LATCH

[LingyuMa]

I know it is hard to see, but the number of image pairs is about 5 times less.