Model packaging (.mar files) in PyTorch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

PyTorch

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

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

A.state_dict()

B.parameters()

C.weights

D.get_state()

Attempts:

3 left

💡 Hint

Common Mistakes

Using model.parameters() instead of model.state_dict()

Trying to save the entire model object directly

We save the model's state dictionary using model.state_dict() to capture the learned parameters.

2fill in blank

medium

Complete the command to create a .mar file using torch-model-archiver.

PyTorch

torch-model-archiver --model-name my_model --version 1.0 --serialized-file [1] --handler handler.py --export-path model_store

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

Amodel.pth

Bmodel.pt

Cmodel.pkl

Dmodel.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong file extensions like .json or .pkl

Confusing the handler file with the serialized file

The serialized file is the saved model weights file, typically named model.pth.

3fill in blank

hard

Fix the error in loading a model from a .mar file using TorchServe.

PyTorch

torchserve --start --model-store model_store --models my_model=[1]

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

Amy_model.py

Bmy_model-1.0.mar

Chandler.py

Dmodel.pth

Attempts:

3 left

💡 Hint

Common Mistakes

Using the raw weights file instead of the .mar file

Using the handler or source code file name

When starting TorchServe, the model must be referenced by its .mar file name.

4fill in blank

hard

Fill both blanks to define a custom handler class for TorchServe.

PyTorch

from ts.torch_handler.base_handler import {{BLANK_1 }}

class CustomHandler({{BLANK_2}}):
    def preprocess(self, data):
        pass

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

ABaseHandler

BTorchHandler

CBaseModel

DTorchBase

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect base class names like TorchHandler or BaseModel

The custom handler should inherit from BaseHandler to implement TorchServe methods.

5fill in blank

hard

Fill all three blanks to create a dictionary for model metadata in the .mar packaging process.

PyTorch

model_info = {
    'model_name': [1],
    'model_version': [2],
    'handler': [3]
}

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

A'my_model'

B'1.0'

C'handler.py'

D'model.pth'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the model weights file name instead of the handler file

Not using quotes around string values

The dictionary keys hold the model name, version, and handler script file name as strings.

Practice

1. What is the main purpose of packaging a PyTorch model into a .mar file?

easy

A. To visualize the model architecture

B. To convert the model into a different training format

C. To compress the model for storage only

D. To bundle the model and code for easy deployment with TorchServe

Solution

1. Step 1: Understand what a .mar file contains

   A .mar file bundles the trained model and the handler code needed to serve it.

2. Step 2: Identify the use case of .mar files

   These files are used by TorchServe to deploy models as APIs easily.

3. Final Answer:

   To bundle the model and code for easy deployment with TorchServe -> Option D

4. Quick Check:

   Model packaging = deployment bundle [OK]

Hint: Think deployment: .mar bundles model + code [OK]

Common Mistakes:

• Confusing .mar with just compression
• Thinking .mar changes training format
• Assuming .mar is for visualization

2. Which command correctly creates a .mar file using torch-model-archiver?

easy

A. torch-model-archiver --model-name mymodel --model-file model.pth --handler handler.py --export-path model_store

B. torch-model-archiver --model-name mymodel --model-file model.pth --handler handler.txt --export-path model_store

C. torch-model-archiver --model-name mymodel --model-file model.txt --handler handler.py --export-path model_store

D. torch-model-archiver --model-name mymodel --model-file model.py --handler handler.py --export-path model_store

Solution

1. Step 1: Identify correct model file type

   The model file should be a PyTorch model file like .pth, not a Python script or text file.

2. Step 2: Confirm handler file type

   The handler must be a Python script .py, not a text file.

3. Final Answer:

   torch-model-archiver --model-name mymodel --model-file model.pth --handler handler.py --export-path model_store -> Option A

4. Quick Check:

   Model file = .pth, handler = .py [OK]

Hint: Model file is .pth, handler is .py script [OK]

Common Mistakes:

• Using .py file as model file
• Using .txt as handler file
• Mixing file extensions incorrectly

3. Given this command:

torch-model-archiver --model-name resnet --model-file resnet.pth --handler image_classifier.py --export-path model_store

What will be the output?

medium

A. A Python script named resnet.py created

B. An error because resnet.pth is not a valid model file

C. A file named resnet.mar created in model_store directory

D. A folder named resnet.mar created

Solution

1. Step 1: Understand torch-model-archiver output

   The command packages the model and handler into a single .mar file.

2. Step 2: Check output location and file name

   The .mar file is named after the model name and saved in the export path.

3. Final Answer:

   A file named resnet.mar created in model_store directory -> Option C

4. Quick Check:

   .mar file = model + handler bundle [OK]

Hint: Output is a .mar file named after model [OK]

Common Mistakes:

• Expecting a Python script output
• Thinking .mar is a folder
• Assuming error due to .pth file

4. You ran this command:

torch-model-archiver --model-name mymodel --model-file model.pth --handler handler.py --export-path model_store

But got an error: Handler file not found. What is the likely cause?

medium

A. The handler.py file is missing or path is incorrect

B. The model.pth file is corrupted

C. The export path model_store does not exist

D. The model name contains invalid characters

Solution

1. Step 1: Analyze the error message

   The error says handler file not found, so the problem is with the handler.py file location or name.

2. Step 2: Check other options

   Model file corruption or export path issues would cause different errors, not handler missing.

3. Final Answer:

   The handler.py file is missing or path is incorrect -> Option A

4. Quick Check:

   Error message = handler file missing [OK]

Hint: Check handler file path if 'Handler file not found' error occurs [OK]

Common Mistakes:

• Blaming model file for handler error
• Ignoring file path correctness
• Assuming export path causes handler error

5. You want to package two different PyTorch models with custom handlers into .mar files for TorchServe. Which approach correctly packages both models for deployment?

hard

A. Package one model as .mar and copy the second model file into the model_store folder without packaging

B. Run torch-model-archiver twice, each time with the respective model file, handler, and unique model name, exporting to the same model_store folder

C. Combine both models into one .pth file and use a single handler to package once

D. Use torch-model-archiver once with both model files and handlers listed separated by commas

Solution

1. Step 1: Understand packaging multiple models

   Each model requires its own .mar file with its specific handler and unique model name.

2. Step 2: Confirm correct packaging method

   Running torch-model-archiver twice with different parameters and exporting to the same folder is the correct way.

3. Final Answer:

   Run torch-model-archiver twice, each time with the respective model file, handler, and unique model name, exporting to the same model_store folder -> Option B

4. Quick Check:

   One .mar per model + handler [OK]

Hint: Package each model separately with unique names [OK]

Common Mistakes:

• Trying to combine models in one .mar file
• Copying model files without packaging
• Passing multiple files in one command