-
Notifications
You must be signed in to change notification settings - Fork 116
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
What is the difference between scrfd_10g_bnkps and scrfd_10g_gnkps #130
Comments
Hi! Yes, all the difference is in GN vs BN, nothing else was changed during training. I've commited GN config to main insightface repo, if I recall correctly, so all the training can be reproduced with original repo. You can read the discussion on this issue here: deepinsight/insightface#1518 BTW: for now yolov5-face models performs much better in edge cases. |
Thanks for your quick response. I want to run test.py in scrfd/tools/ but as you know it needs --config and --checkpoint file OR perhaps you could suggest another way to run test.py with scrfd_10g_gnkps. |
Hi! Unfortunately I have lost original pth files with faulty ssd, only ONNX on google drive have left. |
Could you share link to google drive's folder with scrfd models on onnx? |
https://drive.google.com/drive/folders/109D__GLXHPmiW9tIgsCadTdjcXB0u0vK?usp=drive_link |
I have installed scrfd_2.5g_gnkps.onnx from this folder. And I get error |
Proper model for
It seems library have tried building TRT engine, but it failed. Try cleaning |
Hey.
I have analyzed .onnx files of both gnkps and bnkps models for scrfd_10g, and I saw that there are so many differences in architecture of these models.
So what is the DIFFERENCES between gnkps and bnkps. I mean, If I want to create gnkps on my own, how would I do?
For example, I know that one of them is trained with GN(group normalization) and the other one is BN(batch normalization) BUT is that all?
I wonder of why GNKPS is more successful, and the bnkps is not, especially for big faces but small faces too.
Thanks in advance.
The text was updated successfully, but these errors were encountered: