From 2300080ffd7a8ed46410b9b3c93d43ddea6565b5 Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Sat, 20 Apr 2024 00:16:44 +0900 Subject: [PATCH] Update checkpointer.rst identifer -> identifier --- docs/source/deep_dives/checkpointer.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/deep_dives/checkpointer.rst b/docs/source/deep_dives/checkpointer.rst index 39d1b4fbbb..5fc9873f26 100644 --- a/docs/source/deep_dives/checkpointer.rst +++ b/docs/source/deep_dives/checkpointer.rst @@ -35,7 +35,7 @@ Let's take a close look at these different formats. Very simply put, the format of a checkpoint is dictated by the state_dict and how this is stored in files on disk. Each weight is associated with a string key that identifies it in the state dict. -If the string identifer of the keys in the stored checkpoints don't match up +If the string identifier of the keys in the stored checkpoints don't match up exactly with those in the model definition, you'll either run into explicit errors (loading the state dict will raise an exception) or worse - silent errors (loading will succeed but training or inference will not work as expected). In addition to the keys lining up, you also need the shapes