-
Notifications
You must be signed in to change notification settings - Fork 694
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump PyTorch Lightning version to v1.9.* (#870)
* Modified padim configs * Removed registry * Replace LightningLoggerBase with Logger * Remove resume_from_checkpoint arg from Trainer * Updated cfa configs for v1.9.0 * Udate cflow configs to run on v1.9.0 * Udate csflow configs to run on v1.9.0 * Udate dfkde configs to run on v1.9.0 * Udate dfm configs to run on v1.9.0 * Udate draem configs to run on v1.9.0 * Udpdate fasatflow configs to run on v1.9.0 * Udpdate ganomaly configs to run on v1.9.0 * Udpdate patchcore configs to run on v1.9.0 * Udpdate reverse_distillation configs to run on v1.9.0 * Udpdate rkde configs to run on v1.9.0 * Udpdate stfpm configs to run on v1.9.0 * Update CHANGELOG.md * Remove `inference_mode` from the configs to support PyTorch Lightning v1.6.* * Update CHANGELOG.md * Address pre-commit issues * PL v1.6.* is not supported anymore * Ignore no-member issue when getting trainer.callbacks * Added requirements to pre-commit * Resolve merge conflicts properly * Revert the changes in tox.ini * Address pre-commit errors * Address pylint comments from pre-commit * Address pylint comments from pre-commit. - This is the final one!! * Fix tests. Tensorboard logger has not been addressed yet. * 🩹 Patch requirements (#892) * check extras dependencies in loggers * Add recreate to workflow * Revert -r flag * Fix mocks --------- Co-authored-by: Ashwin Vaidya <ashwinitinvaidya@gmail.com> * replace in-place torch operations in Denormalize --------- Co-authored-by: Ashwin Vaidya <ashwin.vaidya@intel.com> Co-authored-by: Ashwin Vaidya <ashwinitinvaidya@gmail.com>
- Loading branch information
1 parent
476655a
commit d390fb5
Showing
57 changed files
with
507 additions
and
593 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.