-
Notifications
You must be signed in to change notification settings - Fork 0
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
Refactor run_protocol #17
base: dev/ond
Are you sure you want to change the base?
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.
I'm not really qualified to review this, but the code looks ok to me at a glance.
Is there some specific insight I can provide?
Nothing specific, just wanted to check if this would make sense (or if it seems unnecessary) from a software engineering and code structure perspective. |
if file_list is not None: | ||
features_dict, logits_dict = algorithm.execute( | ||
"FeatureExtraction", file_list | ||
try: |
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.
Should this be moved in round too? This would require changing the return type of _run_round
to bool
pass | ||
else: | ||
( | ||
algo_test_data["features_dict"], |
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.
I would recommend using update
here rather than assigning since you would need to aggregate features across multiple rounds to save them
This PR aims to move the per-round logic to its own method outside of
run_protocol
to more clearly delineate what's happening within rounds (as opposed to within tests) and to improve readability of therun_protocol
method. This refactoring should not change any of the core logic or functionality.Depends on #14.