TorchScript export in PyTorch - Model Pipeline Trace

Model Pipeline - TorchScript export

This pipeline shows how a PyTorch model is prepared and exported using TorchScript. TorchScript helps save the model so it can run independently from Python, making it easier to deploy.

Data Flow - 4 Stages

1Original Model

1 batch x 3 channels x 224 height x 224 width→Define and initialize a CNN model in PyTorch→1 batch x 10 classes

Input: image tensor with shape (1, 3, 224, 224), Output: raw scores for 10 classes

↓

2Model Tracing

1 batch x 3 channels x 224 height x 224 width→Trace the model with example input to create a TorchScript graph→TorchScript traced model object

Tracing with example input tensor to record operations

↓

3Model Saving

TorchScript traced model object→Save the traced model to a file (.pt)→File saved on disk

Saved model file 'model_traced.pt' for deployment

↓

4Model Loading

File 'model_traced.pt'→Load the TorchScript model from file→TorchScript model ready for inference

Loaded model used for prediction without Python source code

Training Trace - Epoch by Epoch

Loss
1.2 |*****
0.9 |****
0.7 |***
0.5 |**
0.4 |*
Epochs -> 1 2 3 4 5

Epoch	Loss ↓	Accuracy ↑	Observation
1	1.2	0.45	Initial training with high loss and low accuracy
2	0.9	0.60	Loss decreased, accuracy improved
3	0.7	0.72	Model learning well, loss continues to drop
4	0.5	0.80	Good convergence, accuracy nearing 80%
5	0.4	0.85	Training stabilizes with low loss and high accuracy

Prediction Trace - 4 Layers

Layer 1: Input tensor

Layer 2: TorchScript model forward pass

Layer 3: Softmax activation

Layer 4: Prediction output

Model Quiz - 3 Questions

What is the main purpose of tracing a PyTorch model with TorchScript?

A To add more layers to the model

B To save the model so it can run without Python

C To increase training speed

D To convert the model to TensorFlow format

Key Insight

TorchScript export allows a PyTorch model to be saved and run independently from Python. This is useful for deploying models in production environments where Python may not be available. The training trace shows the model improving over time, and the prediction trace demonstrates how input data flows through the saved model to produce class probabilities.

Practice

1. What is the main purpose of exporting a PyTorch model using TorchScript?

easy

A. To increase the training speed of the model

B. To save the model so it can run independently without Python

C. To convert the model into a TensorFlow format

D. To visualize the model architecture

Solution

1. Step 1: Understand TorchScript export purpose

   TorchScript export saves PyTorch models in a format that can run without Python, making deployment easier.

2. Step 2: Compare options with purpose

   Only To save the model so it can run independently without Python correctly states the main purpose: saving for standalone use without Python.

3. Final Answer:

   To save the model so it can run independently without Python -> Option B

4. Quick Check:

   TorchScript export = standalone model saving [OK]

Hint: TorchScript export = run model without Python [OK]

Common Mistakes:

• Thinking it speeds up training
• Confusing with TensorFlow conversion
• Assuming it is for visualization

2. Which of the following is the correct way to export a PyTorch model using scripting in TorchScript?

easy

A. torch.jit.trace(model, example_input)

B. torch.load('model.pt')

C. torch.save(model.state_dict(), 'model.pt')

D. torch.jit.script(model)

Solution

1. Step 1: Identify scripting syntax

   Using scripting to export a model requires torch.jit.script(model).

2. Step 2: Differentiate from tracing and saving

   torch.jit.trace(model, example_input) is tracing, torch.save(model.state_dict(), 'model.pt') saves weights only, torch.load('model.pt') loads a model, so only torch.jit.script(model) is correct for scripting export.

3. Final Answer:

   torch.jit.script(model) -> Option D

4. Quick Check:

   Scripting export uses torch.jit.script [OK]

Hint: Scripting export uses torch.jit.script(model) [OK]

Common Mistakes:

• Confusing scripting with tracing
• Using torch.save instead of torch.jit.script
• Trying to load instead of export

3. Given the code below, what will be the output of print(traced_model(torch.tensor([2.0])))?

import torch
class SimpleModel(torch.nn.Module):
    def forward(self, x):
        return x * 3

model = SimpleModel()
example_input = torch.tensor([1.0])
traced_model = torch.jit.trace(model, example_input)
print(traced_model(torch.tensor([2.0])))

medium

A. tensor([2.0])

B. tensor([3.0])

C. tensor([6.0])

D. RuntimeError

Solution

1. Step 1: Understand model behavior

   The model multiplies input by 3, so input 2.0 becomes 6.0.

2. Step 2: Check traced model output

   Tracing records the multiply by 3 operation, so traced_model(2.0) outputs tensor([6.0]).

3. Final Answer:

   tensor([6.0]) -> Option C

4. Quick Check:

   Input 2.0 * 3 = 6.0 [OK]

Hint: Model multiplies input by 3, so output is input*3 [OK]

Common Mistakes:

• Confusing input with output
• Expecting tracing to fail
• Thinking output is unchanged input

4. What is the error in the following code snippet when exporting a model with TorchScript scripting?

import torch
class MyModel(torch.nn.Module):
    def forward(self, x):
        if x.sum() > 0:
            return x * 2
        else:
            return x - 2

model = MyModel()
scripted_model = torch.jit.trace(model, torch.tensor([1.0]))

medium

A. Using torch.jit.trace instead of torch.jit.script for model with conditions

B. Missing example input tensor

C. Model class missing __init__ method

D. Incorrect tensor datatype

Solution

1. Step 1: Identify model features

   The model has a condition (if statement) in forward, which tracing cannot capture correctly.

2. Step 2: Understand TorchScript export methods

   Tracing works only for simple models without control flow; scripting is needed for conditions.

3. Final Answer:

   Using torch.jit.trace instead of torch.jit.script for model with conditions -> Option A

4. Quick Check:

   Model with conditions requires scripting, not tracing [OK]

Hint: Use scripting for models with if/else, not tracing [OK]

Common Mistakes:

• Using trace on models with control flow
• Assuming missing input tensor causes error
• Thinking __init__ is mandatory here

5. You want to export a PyTorch model that uses a loop and conditional statements inside its forward method. Which approach should you use to export it with TorchScript, and why?

hard

A. Use torch.jit.script because it supports control flow like loops and conditions

B. Use torch.jit.trace because it records operations for any model

C. Use torch.save to save the model weights only

D. Use torch.jit.trace with multiple example inputs to cover all paths

Solution

1. Step 1: Analyze model features

   The model has loops and conditions, which require TorchScript to understand control flow.

2. Step 2: Choose correct export method

   torch.jit.script compiles the model including control flow, while tracing cannot handle dynamic paths.

3. Final Answer:

   Use torch.jit.script because it supports control flow like loops and conditions -> Option A

4. Quick Check:

   Loops and conditions need scripting export [OK]

Hint: Loops and conditions require torch.jit.script export [OK]

Common Mistakes:

• Using tracing for models with dynamic control flow
• Saving weights only instead of full model
• Trying to cover all paths with tracing