updated requirements file and readme of Privacy Meter workflow #1295
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rahulga1
approved these changes
Jan 22, 2025
bandatarunkumar
force-pushed
the
privacy_meter_dependancies_update
branch
2 times, most recently
from
6408831 to
565d20b
Compare
teoparvanov
approved these changes
Jan 27, 2025
openfl-tutorials/experimental/workflow/Privacy_Meter/requirements_privacy_meter.txt
Outdated
Show resolved
Hide resolved
Signed-off-by: Tarunkumar Banda <[email protected]>
bandatarunkumar
force-pushed
the
privacy_meter_dependancies_update
branch
from
565d20b to
bc025fb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixing the requirements.txt for Privacy Meter and readme for running the privacy meter workflow, ran the privacy meter workflow with two optimizers(SGD and Adam) for 2 and 10 rounds. The workflow is running as expected without errors. The max CPU consumed while running was 18.8 gb(out of which 3.6 was previously consumed by vscode and other processes), so added note in readme to have atleast 18GB dedicated ram for running the privacy meter experiment.