-
Notifications
You must be signed in to change notification settings - Fork 38
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
Accuracy check #7
Comments
Hello, did you successfully reproduce the attack on the krum and coomed aggregation rules? |
For simplicity, the code as implemented does not discard updates from agents with accuracy lower than a given threshold, as we found that, even with the attack, the accuracy of all agents is satisfactorily high, and will not trigger removal in a realistic setting. That said, this function can be easily implemented and I would urge you to submit a PR if possible.
The results can be easily reproduced by running the following commands for coordinate-wise median
and krum respectively, where LAMBDA=2 to reproduce the results from the paper exactly:
Note that |
I did not find the code for accuracy check as mentioned in this paper. Is the 'accuracy check' included in the source code? In other words, will the central server check the accuracy of model updates from different participants before aggregating them?
Further, would you please give the parameters (or a running command) to reproduce the results in the paper on attacking 'krum' and 'coomed' aggregation rule?
The text was updated successfully, but these errors were encountered: