Why checkpointing preserves progress in PyTorch - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to save the model's state dictionary.

PyTorch

torch.save(model[1], 'model.pth')

Drag options to blanks, or click blank then click option'

A.gradients

B.parameters()

C.weights

D.state_dict()

Attempts:

3 left

💡 Hint

Common Mistakes

Saving model.parameters() instead of state_dict()

Saving model.weights which does not exist

Saving the state_dict() stores the model's learned parameters, which is essential for checkpointing.

2fill in blank

medium

Complete the code to load the saved state dictionary into the model.

PyTorch

model.load_state_dict(torch.load('[1]'))

Drag options to blanks, or click blank then click option'

Astate.pth

Bmodel.pth

Cweights.pth

Dcheckpoint.pth

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different filename than the one used to save

Forgetting to load the state dictionary

The file model.pth is where the model's state dictionary was saved, so it must be loaded from there.

3fill in blank

hard

Fix the error in saving the optimizer state for checkpointing.

PyTorch

torch.save(optimizer[1], 'optimizer.pth')

Drag options to blanks, or click blank then click option'

A.gradients

B.parameters()

C.state_dict()

D.weights

Attempts:

3 left

💡 Hint

Common Mistakes

Saving optimizer.parameters() which does not exist

Saving optimizer.weights which is invalid

The optimizer's state_dict() contains all the information needed to resume training exactly.

4fill in blank

hard

Fill both blanks to save both model and optimizer states in one checkpoint dictionary.

PyTorch

checkpoint = {'model': model[1], 'optimizer': optimizer[2], 'epoch': epoch}
torch.save(checkpoint, 'checkpoint.pth')

Drag options to blanks, or click blank then click option'

A.state_dict()

B.parameters()

C.gradients

D.weights

Attempts:

3 left

💡 Hint

Common Mistakes

Using different methods for model and optimizer

Using .parameters() or .weights instead of .state_dict()

Both model and optimizer states are saved using their state_dict() methods to preserve training progress.

5fill in blank

hard

Fill all three blanks to load checkpoint and resume training with model, optimizer, and epoch.

PyTorch

checkpoint = torch.load('checkpoint.pth')
model.load_state_dict(checkpoint['[1]'])
optimizer.load_state_dict(checkpoint['[2]'])
epoch = checkpoint['[3]']

Drag options to blanks, or click blank then click option'

Amodel

Boptimizer

Cepoch

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong keys like 'state' instead of 'model'

Forgetting to load epoch to resume training correctly

The checkpoint dictionary stores keys 'model', 'optimizer', and 'epoch' to restore training state.

Practice

1. What is the main reason for using checkpointing during PyTorch model training?

easy

A. To save the model's current state so training can resume later without loss

B. To speed up the training by skipping some layers

C. To reduce the size of the training dataset

D. To automatically tune hyperparameters during training

Solution

1. Step 1: Understand checkpointing purpose

   Checkpointing saves the model's current state including weights and optimizer info.

2. Step 2: Connect checkpointing to training progress

   This allows training to stop and resume later without losing progress.

3. Final Answer:

   To save the model's current state so training can resume later without loss -> Option A

4. Quick Check:

   Checkpointing = Save progress [OK]

Hint: Checkpointing means saving progress to continue later [OK]

Common Mistakes:

• Thinking checkpointing speeds up training
• Confusing checkpointing with data reduction
• Assuming checkpointing tunes hyperparameters

2. Which of the following is the correct PyTorch code snippet to save a checkpoint?

easy

A. model.load_state_dict(torch.save('checkpoint.pth'))

B. torch.save(model.state_dict(), 'checkpoint.pth')

C. torch.load('checkpoint.pth')

D. optimizer.save('checkpoint.pth')

Solution

1. Step 1: Identify saving function

   torch.save() is used to save objects like model weights to a file.

2. Step 2: Check correct usage for saving model state

   model.state_dict() returns model weights; saving it with torch.save() is correct.

3. Final Answer:

   torch.save(model.state_dict(), 'checkpoint.pth') -> Option B

4. Quick Check:

   Save model weights = torch.save(state_dict) [OK]

Hint: Use torch.save with model.state_dict() to save checkpoint [OK]

Common Mistakes:

• Using torch.load instead of torch.save to save
• Trying to save optimizer with wrong method
• Confusing load_state_dict with saving

3. Given this code snippet, what will be printed after loading the checkpoint?

model = MyModel()
optimizer = torch.optim.Adam(model.parameters())
checkpoint = torch.load('checkpoint.pth')
model.load_state_dict(checkpoint['model_state'])
optimizer.load_state_dict(checkpoint['optimizer_state'])
epoch = checkpoint['epoch']
print(epoch)

medium

A. An error because checkpoint keys are missing

B. The total number of model parameters

C. The optimizer learning rate

D. The epoch number saved in the checkpoint

Solution

1. Step 1: Understand checkpoint contents

   The checkpoint dictionary contains keys 'model_state', 'optimizer_state', and 'epoch'.

2. Step 2: Identify printed value

   Variable 'epoch' is assigned checkpoint['epoch'], so print(epoch) outputs the saved epoch number.

3. Final Answer:

   The epoch number saved in the checkpoint -> Option D

4. Quick Check:

   Print epoch from checkpoint = epoch number [OK]

Hint: Print shows saved epoch from checkpoint dictionary [OK]

Common Mistakes:

• Thinking print shows model parameters count
• Confusing optimizer state with epoch
• Assuming missing keys cause error here

4. You tried to resume training but got an error: RuntimeError: Error(s) in loading state_dict. What is the most likely cause related to checkpointing?

medium

A. The training data was modified after checkpointing

B. The checkpoint file was saved with torch.load instead of torch.save

C. The model architecture changed after saving the checkpoint

D. The optimizer state was not saved in the checkpoint

Solution

1. Step 1: Understand error meaning

   Loading state_dict errors usually happen if model layers differ from saved checkpoint.

2. Step 2: Connect error to checkpoint cause

   If model architecture changed after saving, weights won't match, causing this error.

3. Final Answer:

   The model architecture changed after saving the checkpoint -> Option C

4. Quick Check:

   State_dict error = architecture mismatch [OK]

Hint: Mismatch model layers cause state_dict loading errors [OK]

Common Mistakes:

• Confusing save/load functions causing error
• Assuming missing optimizer state causes this error
• Blaming training data changes for state_dict error

5. You want to checkpoint your training every 5 epochs to avoid losing progress. Which approach best preserves training progress including optimizer state and epoch count?

hard

A. Save a dictionary with model.state_dict(), optimizer.state_dict(), and current epoch number

B. Save only model.state_dict() every 5 epochs

C. Save optimizer.state_dict() and epoch number but not model weights

D. Save the training data batch every 5 epochs

Solution

1. Step 1: Identify what preserves full training state

   Saving model weights, optimizer state, and epoch number allows full resume.

2. Step 2: Compare options

   Only saving model weights misses optimizer info; saving optimizer and epoch without model is incomplete; saving data batch doesn't preserve progress.

3. Final Answer:

   Save a dictionary with model.state_dict(), optimizer.state_dict(), and current epoch number -> Option A

4. Quick Check:

   Checkpoint = model + optimizer + epoch [OK]

Hint: Checkpoint all: model, optimizer, and epoch for full resume [OK]

Common Mistakes:

• Saving only model weights loses optimizer progress
• Ignoring epoch number causes restart from zero
• Saving training data batch does not preserve model state