Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If my feature extractor changes from arcface to adaface, will it not work as well, and will I need to retrain the model with adaface? #24

Open
xlovej opened this issue Aug 11, 2024 · 3 comments

Comments

@xlovej
Copy link

xlovej commented Aug 11, 2024

If my feature extractor changes from arcface to adaface, will it not work as well, and will I need to retrain the model with adaface?

@nikky4D
Copy link

nikky4D commented Aug 16, 2024

I have this question as well. How does the dependency on ArcFace affect performance

@foivospar
Copy link
Owner

Hi, the method works with the FR network in a black-box setting, using only its output embeddings (thus, any ID features could have been used for conditioning). However, since each network's embeddings reside in different spaces, the provided model is not interchangeable with, for example, AdaFace, as it was trained on ArcFace. Re-training would be required when switching to a different FR network.

@lambdaterm
Copy link

Another possible solution is to try converting AdaFace embeddings to the ArcFace latent space. We have achieved some successful results by converting buffalo_l embeddings to antelopev2 without having to retrain the Arc2Face models. https://github.com/lambdaterm/biometricshack-2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants