-
Notifications
You must be signed in to change notification settings - Fork 25
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
Implementing end-to-end test with Byzantine-Robust Aggregator for cifar10 task #557
Implementing end-to-end test with Byzantine-Robust Aggregator for cifar10 task #557
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added some comments. one goal to keep in mind is to make the Byzantine robust clipping such that it can later also be used in decentralized. so let's try to define the clipping center based on local info only (and try to minimize additional communication if any).
we should also write down some thoughts&docu on how it will work with async (whenever the buffer size is reached, we do an aggregation with that group, so that's a round)
0322805
to
7b5f30b
Compare
7b5f30b
to
ecaa4fc
Compare
e545f84
to
d3992cb
Compare
6283798
to
d482335
Compare
93a6169
to
09a9863
Compare
Discojs
Server
Changed the end-to-end test case for the federated setting to use both standard aggregator and byzantine-robust one. Also, the test is now considering the presence of multiple users, splitting the training data among them and validating the model computing the accuracy after the training phase. As last step, an assertion has been added to expect a reasonable accuracy after training.