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
Firstly, thank you for your work, @guipotje et al.
There are issues like #59 that show SIFT performing better than vanilla XFeat for large geometric transformations, or when there is a large scale difference in objects being matched between images (#58).
In this case, what are the cases where, in practice, one should prefer XFeat over SIFT? Can you share more examples of cases and some prescriptive use cases where XFeat surpasses SIFT? For example, maybe in cases of motion blur in videos, or lighting inconstancy, I am guessing XFeat may be better than SIFT - could you please share such analysis, if you have done this. I am particularly mentioning SIFT since it is a de facto standard for non-earned features.
Steerable-XFeat (WIP combining xfeat with steerers #32) - do you have any plans to integrate the Steerers work into the Xfeat codebase with pretrained networks?
Thank you.
The text was updated successfully, but these errors were encountered:
Hello @AruniRC , sorry for the delayed reply, and thanks for the interest in our work!
I don't have more quantitative experiments other than those reported in the paper, but from my experience with XFeat, I will try to give some directions for further exploration:
When it comes to large geometric transformations, you have the option to perform multi-scale feature extraction. This is similar to what's done in SIFT, ORB and other classic approaches. This should increase XFeat invariance to strong scale changes.
Compared to handcrafted features, XFeat has the following advantages:
(a) Improved robustness to photometric changes (illumination, shadows, etc), and blur, as shown in the demo;
(b) The ability to be easily fine-tuned for specific problems;
(c) Neural processing hardware is now ubiquitous and is becoming cheaper and more accessible everyday, and provide highly optimized inference for CNN and other common network architectures. Thus, you can deploy XFeat in hardware-constrained devices, probably obtaining much better computational performance than general-purpose implementations of SIFT, ORB, & friends on cheap hardware such as mobile processors (ARM, etc).
Yes, It would be very nice to provide an implementation of steerers in this repo. Maybe someone could help providing a tight integration between them.
Firstly, thank you for your work, @guipotje et al.
There are issues like #59 that show SIFT performing better than vanilla XFeat for large geometric transformations, or when there is a large scale difference in objects being matched between images (#58).
Thank you.
The text was updated successfully, but these errors were encountered: