Skip to content
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

Upgrade dependency to torchmetrics == 1.0.1 #205

Merged
merged 1 commit into from
Jul 20, 2023

Conversation

mzweilin
Copy link
Contributor

@mzweilin mzweilin commented Jul 20, 2023

What does this PR do?

Upgrade to torchmetrics v1.0.1 because it fixes a bug in AveragePrecision: Lightning-AI/torchmetrics#1913

Type of change

Please check all relevant options.

  • 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.

  • pytest
  • CUDA_VISIBLE_DEVICES=0 python -m mart experiment=CIFAR10_CNN_Adv trainer=gpu trainer.precision=16 reports 70% (21 sec/epoch).
  • CUDA_VISIBLE_DEVICES=0,1 python -m mart experiment=CIFAR10_CNN_Adv trainer=ddp trainer.precision=16 trainer.devices=2 model.optimizer.lr=0.2 trainer.max_steps=2925 datamodule.ims_per_batch=256 datamodule.world_size=2 reports 70% (14 sec/epoch).

Before submitting

  • The title is self-explanatory and the description concisely explains the PR
  • 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
  • New and existing unit tests pass locally with my changes
  • I have run pre-commit hooks with pre-commit run -a command without errors

Did you have fun?

Make sure you had fun coding 🙃

@dxoigmn dxoigmn self-requested a review July 20, 2023 21:16
Copy link
Contributor

@dxoigmn dxoigmn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mzweilin mzweilin marked this pull request as ready for review July 20, 2023 22:05
@mzweilin mzweilin merged commit 74600c4 into main Jul 20, 2023
@mzweilin mzweilin deleted the upgrade_torchmetrics_1.0.1 branch July 20, 2023 22:06
mzweilin added a commit that referenced this pull request Aug 25, 2023
* Initial implementation of adversarial training callback

* Make callback work in CPU

* style

* Add and use on_after_batch_transfer hook

* Override on_after_batch_transfer in callback setup

* Restore on_after_batch_transfer hook in teardown

* cleanup

* Call original on_after_batch_transfer hook

* Move Adversary.attack into callback

* Upgrade dependency to torchmetrics == 1.0.1 (#205)

* Move adversary out of the model sequence.

* Make an adversarial training/evaluation callback.

* Remove stuff that is related to callback entry points.

* Replace model wrapper with a configurable model_transform.

* Comment.

* Rename as train/val/test.

* Rename the callback to AdversaryConnector because we may not perform adversarial training by allowing train_adversary=None.

* Rename config: adversarial_training -> adversary_connector.

* Add configure_model() and simplify batch in Adversary.

* Delete Adversary.get_input_adv().

* Move model_transform() to configure_model().

* Add model back to attack batch, because we don't want to wrap LightningModule inside a LightningModule in case of Trainer interference.

* Move LightningModuleAsTarget logic into Adversary.

* Leave model_transform() for future PRs.

* Expand get_input_adv().

* Fix visualizer test.

---------

Co-authored-by: Cory Cornelius <[email protected]>
mzweilin added a commit that referenced this pull request Aug 31, 2023
* Initial implementation of adversarial training callback

* Make callback work in CPU

* style

* Add and use on_after_batch_transfer hook

* Override on_after_batch_transfer in callback setup

* Restore on_after_batch_transfer hook in teardown

* cleanup

* Call original on_after_batch_transfer hook

* Move Adversary.attack into callback

* Upgrade dependency to torchmetrics == 1.0.1 (#205)

* Move adversary out of the model sequence.

* Make an adversarial training/evaluation callback.

* Remove stuff that is related to callback entry points.

* Replace model wrapper with a configurable model_transform.

* Add Adversary.batch_converter().

* Comment.

* Rename as train/val/test.

* Rename the callback to AdversaryConnector because we may not perform adversarial training by allowing train_adversary=None.

* Rename config: adversarial_training -> adversary_connector.

* Update comments.

* Remove model_transform, again.

* Comment.

* Comments.

* Rename batch_converter as batch_c15n.

* Replace the _transformed suffix with the _orig suffix, because _orig is rare.

* Seperate fit() from forward() in Adversary.

* Always require batch canonicalizatoin in Adversary.forward().

* Always enforce the threat model in Adversary.forward().

* adversary.forward() -> adversary().

* Allow None enforcer.

---------

Co-authored-by: Cory Cornelius <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants