This PR exposes IterativeGenerator as a Trainer, named Attacker, that we inject into an Adversary. This PR also raises of the question of whether Composer should be a component of the Attacker or the Adversary.
Type of change
Please check all relevant options.
[x] Improvement (non-breaking)
[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.
[x] make test
Before submitting
[x] The title is self-explanatory and the description concisely explains the PR
[x] My PR does only one thing, instead of bundling different changes together
[ ] I list all the breaking changes introduced by this pull request
[ ] I have commented my code
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have run pre-commit hooks with pre-commit run -a command without errors
What does this PR do?
This PR exposes IterativeGenerator as a Trainer, named
Attacker, that we inject into an Adversary. This PR also raises of the question of whetherComposershould be a component of theAttackeror theAdversary.Type of change
Please check all relevant options.
Testing
Please describe the tests that you ran to verify your changes. Consider listing any relevant details of your test configuration.
make testBefore submitting
pre-commit run -acommand without errorsDid you have fun?
Make sure you had fun coding 🙃