-
Notifications
You must be signed in to change notification settings - Fork 4
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
Inconsistent behavior when different seeds are initialized at evaluations time #3
Comments
Hi Marco, Thank you for reaching out and for your interest in our work. In the detection evaluation, the randomness exists in the "shuffle" method: Beatrix/defenses/Beatrix/Beatrix.py Line 432 in 685827e
You may be able to get more stable detection results under different random seeds, if you increase the available clean data in detection: Beatrix/defenses/Beatrix/Beatrix.py Line 415 in 685827e
|
Thanks for your answer. Indeed, we arrived to the same conclusion by replacing 30 with 300. However, at this point, my questions are:
|
Hi Marco, Thanks for your questions.
|
Thanks for your answer.
We understand this point and we did the same too. However we couldn’t obtain the same results.
|
In the experiments, we used 30 clean samples per class for backdoor detection. And as shown in the implementation, we did not set "random seed". |
Thank you for your work and code!
After running the command
python train.py --dataset cifar10 --target_label 0 --gpu 0
we have tried to evaluate the performance of your detector with
python Beatrix.py --dataset cifar10 --gpu 0
limiting ourselves to only checking the effect of poisoning label 0.
In particular, we have changed this code to the following
to study the effect of different seeds on the performance.
From the attached log file, we have noticed that for some seeds, namely [3, 5, 7, 9] the value of the anomaly index for the target class 0 is not the highest.$e^2$ reported in the paper, resulting in missed detections.
Moreover, for some seeds, namely [0, 2, 3, 5, 7, 9], the anomaly index for class 0 appears to be below the threshold
These phenomena seem to appear more often than we expected.
Could you help interpreting this, and suggest what to change in case we are doing something wrong?
The text was updated successfully, but these errors were encountered: