Fixing and documenting the CrowdGuard workflow tutorial #1289
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR I've focused on enabling the CrowdGuard example to run on CPU (5 train/defend rounds are runnable within a reasonable amount of time). It is noteworthy, however, that this example cannot execute on a normal PC, as it requires at least 18GB of dedicated RAM. Running CrowdGuard on GPU-accelerated collaborators probably doesn't make much sense anyway as GPUs offer limited (if any) support for confidential computing.
Thanks, @bandatarunkumar for helping me thoroughly test the proposed changes!
PS: I've also added a step-by-step guide on how to run the
cifar10_crowdguard.py
demo script.