Does min_num_features: not apply when HAHOG is used?

WebODM
1

When using georeferenced drone images and SIFT feature extraction, I can set the minimum number of features, and if the number is not reached a 2nd or even a 3rd pass at lower thresholds will take place, until the min number of features is reached or exceeded.

This does not appear to be the case with HAHOG, which it defaults to with non-georeferenced images from phone or DSLR, and it appears that no second passes are made if the min num features is not reached.

Is this how it is supposed to be?

1 Like
2

Anyone… Bueller?

1 Like
3

I am noticing the same, but I have not been able to find where in the code this is all set.

1 Like
4

here?
D:\WebODM\resources\app\apps\ODM\SuperBuild\install\bin\opensfm\opensfm\src\features\src\hahog.cc

1 Like
5

Maybe! But it also seems to impact ORB and AKAZE, so I wonder if it isn’t something more general in addition to each feature type.

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.