History

PL Ghost 00cf5c90ca Adding test for legacy checkpoint created with 2.3.3 (#20061 )		2024-07-08 18:16:19 -04:00
..
checkpoints	Future 4/n: test & legacy in test/ folder (#13295 )	2022-06-15 18:10:49 -04:00
README.md	Enable and fix recent legacy checkpoint tests in CI (#12491 )	2022-10-26 11:24:53 +00:00
back-compatible-versions.txt	Adding test for legacy checkpoint created with 2.3.3 (#20061 )	2024-07-08 18:16:19 -04:00
generate_checkpoints.sh	ci: adding missing requirements for generating legacy ckpt (#19353 )	2024-01-28 11:22:07 +01:00
requirements.txt	ci: adding missing requirements for generating legacy ckpt (#19353 )	2024-01-28 11:22:07 +01:00
simple_classif_training.py	ruff: replace isort with ruff +TPU (#17684 )	2023-09-26 11:54:55 -04:00

README.md

Maintaining backward compatibility with legacy versions

The aim of this section is to set some baselines and workflows/guidelines for maintaining backward compatibility with some legacy versions of PyTorch Lightning.

At this moment, we focus on ability to run old checkpoints, so the flow here is to create a checkpoint with every release and store it in our public AWS storage. Stored legacy checkpoints are then used in each CI to test loading and resuming training with the archived checkpoints.

Download legacy checkpoints

If you want to pull all saved version-checkpoints for local testing/development, call

bash .actions/pull_legacy_checkpoints.sh

Generate legacy checkpoints locally

To back populate collection with past versions you can use the following command:

bash generate_checkpoints.sh "1.3.7" "1.3.8"
zip -r checkpoints.zip checkpoints/