-
Notifications
You must be signed in to change notification settings - Fork 2
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
the value of 'm‘ in “Batched Adversarial Attack” of your paper #16
Comments
By default |
In the paper you can find that the algorithm will go through the whole dataset for reporting the number. |
I follow the step of README.md, I think there's no wrong step. And the result is trained on CUB dataset |
This difference is normal. What you see here is within the error bar. Due to different initialization and other factors (such as the number of GPUs in DDP mode), the performance differs slightly. If you want to see a higher ERS, just try to limit the GPU number to 1 or 2 (if I remember correctly. If not, it should be the reverse way -- more GPUs -- there will be a slight trade-off between R1 and ERS when changing the GPU number. This is a common phenomenon in parallel training), and try some more initialization. |
Yes, they are reported at the training end status. Because in adversarial training, these standard benign metrics may look like a U-shape curve or directly a descending curve ... That's a part of adversarial training sacrificing the benign performance. |
Get it, thank you very much! |
Excuse me, which is the mAP in 《Enhancing Adversarial Robustness for Deep Metric Learning》, mAP or mAP@R? |
It's simply the original mAP. If mAP@R is used, it should have been explicitly justified. |
Excuse me, what's the value of 'm‘ in “Batched Adversarial Attack” of your paper? Could you give a detailed guidance to reproduce the result of Table in your paper?
The text was updated successfully, but these errors were encountered: