Unet-Segmentation: Optimized for Mobile Deployment
Real-time segmentation optimized for mobile and edge
UNet is a machine learning model that produces a segmentation mask for an image. The most basic use case will label each pixel in the image as being in the foreground or the background. More advanced usage will assign a class label to each pixel. This version of the model was trained on the data from Kaggle's Carvana Image Masking Challenge (see https://www.kaggle.com/c/carvana-image-masking-challenge) and is used for vehicle segmentation.
This model is an implementation of Unet-Segmentation found here.
This repository provides scripts to run Unet-Segmentation on Qualcomm® devices. More details on model performance across various devices, can be found here.
Model Details
- Model Type: Semantic segmentation
- Model Stats:
- Model checkpoint: unet_carvana_scale1.0_epoch2
- Input resolution: 224x224
- Number of parameters: 31.0M
- Model size: 118 MB
- Number of output classes: 2 (foreground / background)
Model | Device | Chipset | Target Runtime | Inference Time (ms) | Peak Memory Range (MB) | Precision | Primary Compute Unit | Target Model |
---|---|---|---|---|---|---|---|---|
Unet-Segmentation | Samsung Galaxy S23 | Snapdragon® 8 Gen 2 | TFLITE | 150.193 ms | 0 - 525 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | Samsung Galaxy S23 | Snapdragon® 8 Gen 2 | QNN | 161.015 ms | 10 - 40 MB | FP16 | NPU | Unet-Segmentation.so |
Unet-Segmentation | Samsung Galaxy S23 | Snapdragon® 8 Gen 2 | ONNX | 161.889 ms | 15 - 16 MB | FP16 | NPU | Unet-Segmentation.onnx |
Unet-Segmentation | Samsung Galaxy S24 | Snapdragon® 8 Gen 3 | TFLITE | 111.024 ms | 5 - 390 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | Samsung Galaxy S24 | Snapdragon® 8 Gen 3 | QNN | 111.294 ms | 20 - 103 MB | FP16 | NPU | Unet-Segmentation.so |
Unet-Segmentation | Samsung Galaxy S24 | Snapdragon® 8 Gen 3 | ONNX | 113.283 ms | 25 - 425 MB | FP16 | NPU | Unet-Segmentation.onnx |
Unet-Segmentation | Snapdragon 8 Elite QRD | Snapdragon® 8 Elite | TFLITE | 103.436 ms | 5 - 117 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | Snapdragon 8 Elite QRD | Snapdragon® 8 Elite | QNN | 90.17 ms | 9 - 110 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | Snapdragon 8 Elite QRD | Snapdragon® 8 Elite | ONNX | 104.832 ms | 19 - 136 MB | FP16 | NPU | Unet-Segmentation.onnx |
Unet-Segmentation | QCS8550 (Proxy) | QCS8550 Proxy | TFLITE | 153.377 ms | 1 - 451 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | QCS8550 (Proxy) | QCS8550 Proxy | QNN | 136.975 ms | 10 - 11 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | SA8255 (Proxy) | SA8255P Proxy | TFLITE | 149.315 ms | 0 - 451 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | SA8255 (Proxy) | SA8255P Proxy | QNN | 139.944 ms | 10 - 18 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | SA8775 (Proxy) | SA8775P Proxy | TFLITE | 154.145 ms | 6 - 441 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | SA8775 (Proxy) | SA8775P Proxy | QNN | 145.992 ms | 10 - 11 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | SA8650 (Proxy) | SA8650P Proxy | TFLITE | 150.322 ms | 6 - 442 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | SA8650 (Proxy) | SA8650P Proxy | QNN | 138.474 ms | 10 - 11 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | SA8295P ADP | SA8295P | TFLITE | 275.014 ms | 7 - 120 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | SA8295P ADP | SA8295P | QNN | 266.041 ms | 1 - 6 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | QCS8450 (Proxy) | QCS8450 Proxy | TFLITE | 361.208 ms | 8 - 395 MB | FP16 | NPU | Unet-Segmentation.tflite |
Unet-Segmentation | QCS8450 (Proxy) | QCS8450 Proxy | QNN | 290.451 ms | 9 - 100 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | Snapdragon X Elite CRD | Snapdragon® X Elite | QNN | 135.755 ms | 9 - 9 MB | FP16 | NPU | Use Export Script |
Unet-Segmentation | Snapdragon X Elite CRD | Snapdragon® X Elite | ONNX | 147.5 ms | 54 - 54 MB | FP16 | NPU | Unet-Segmentation.onnx |
Installation
This model can be installed as a Python package via pip.
pip install qai-hub-models
Configure Qualcomm® AI Hub to run this model on a cloud-hosted device
Sign-in to Qualcomm® AI Hub with your
Qualcomm® ID. Once signed in navigate to Account -> Settings -> API Token
.
With this API token, you can configure your client to run models on the cloud hosted devices.
qai-hub configure --api_token API_TOKEN
Navigate to docs for more information.
Demo off target
The package contains a simple end-to-end demo that downloads pre-trained weights and runs this model on a sample input.
python -m qai_hub_models.models.unet_segmentation.demo
The above demo runs a reference implementation of pre-processing, model inference, and post processing.
NOTE: If you want running in a Jupyter Notebook or Google Colab like environment, please add the following to your cell (instead of the above).
%run -m qai_hub_models.models.unet_segmentation.demo
Run model on a cloud-hosted device
In addition to the demo, you can also run the model on a cloud-hosted Qualcomm® device. This script does the following:
- Performance check on-device on a cloud-hosted device
- Downloads compiled assets that can be deployed on-device for Android.
- Accuracy check between PyTorch and on-device outputs.
python -m qai_hub_models.models.unet_segmentation.export
Profiling Results
------------------------------------------------------------
Unet-Segmentation
Device : Samsung Galaxy S23 (13)
Runtime : TFLITE
Estimated inference time (ms) : 150.2
Estimated peak memory usage (MB): [0, 525]
Total # Ops : 32
Compute Unit(s) : NPU (32 ops)
How does this work?
This export script leverages Qualcomm® AI Hub to optimize, validate, and deploy this model on-device. Lets go through each step below in detail:
Step 1: Compile model for on-device deployment
To compile a PyTorch model for on-device deployment, we first trace the model
in memory using the jit.trace
and then call the submit_compile_job
API.
import torch
import qai_hub as hub
from qai_hub_models.models.unet_segmentation import
# Load the model
# Device
device = hub.Device("Samsung Galaxy S23")
Step 2: Performance profiling on cloud-hosted device
After compiling models from step 1. Models can be profiled model on-device using the
target_model
. Note that this scripts runs the model on a device automatically
provisioned in the cloud. Once the job is submitted, you can navigate to a
provided job URL to view a variety of on-device performance metrics.
profile_job = hub.submit_profile_job(
model=target_model,
device=device,
)
Step 3: Verify on-device accuracy
To verify the accuracy of the model on-device, you can run on-device inference on sample input data on the same cloud hosted device.
input_data = torch_model.sample_inputs()
inference_job = hub.submit_inference_job(
model=target_model,
device=device,
inputs=input_data,
)
on_device_output = inference_job.download_output_data()
With the output of the model, you can compute like PSNR, relative errors or spot check the output with expected output.
Note: This on-device profiling and inference requires access to Qualcomm® AI Hub. Sign up for access.
Run demo on a cloud-hosted device
You can also run the demo on-device.
python -m qai_hub_models.models.unet_segmentation.demo --on-device
NOTE: If you want running in a Jupyter Notebook or Google Colab like environment, please add the following to your cell (instead of the above).
%run -m qai_hub_models.models.unet_segmentation.demo -- --on-device
Deploying compiled model to Android
The models can be deployed using multiple runtimes:
TensorFlow Lite (
.tflite
export): This tutorial provides a guide to deploy the .tflite model in an Android application.QNN (
.so
export ): This sample app provides instructions on how to use the.so
shared library in an Android application.
View on Qualcomm® AI Hub
Get more details on Unet-Segmentation's performance across various devices here. Explore all available models on Qualcomm® AI Hub
License
- The license for the original implementation of Unet-Segmentation can be found here.
- The license for the compiled assets for on-device deployment can be found here
References
Community
- Join our AI Hub Slack community to collaborate, post questions and learn more about on-device AI.
- For questions or feedback please reach out to us.