==============================
TFLite(LiteRT) - Analytical AI
==============================

The resources in this section support both the **Online** and **Offline inference paths** for **TFLite-analytical AI** workloads. This section provides the necessary TFLite models and pre-compiled Deep Learning Archives (DLAs) required to execute models via the TFLite Interpreter or directly through the Neuron Runtime.

.. image:: /_asset/analytical-ai-workflow.png
   :alt: Analytical AI inference paths: Online and Offline
   :align: center
   :width: 100%

.. raw:: html

   <br>

.. note::

   To prepare your own models for these paths (such as quantization or compilation), refer to :doc:`AI Development Resources </ai_hub/related_resource>` to obtain the required NeuroPilot SDKs and host tools.


Vision models in the TFLite Analytical Model collection perform three core tasks on image data: image classification, object detection, and recognition.
Together, these tasks help identify what appears in an image, where it is, and who or what a specific entity is.
The Analytical Model section provides a curated set of commonly used TensorFlow Lite models and their converted Deep Learning Archives (DLAs) for deployment on MediaTek Genio platforms.

Each model package includes the following artifacts:

* A baseline TensorFlow Lite (``.tflite``) model.
* One or more version-specific DLA binaries:

  * ``mdla2`` for MDLA 2.x,
  * ``mdla3`` for MDLA 3.x, and
  * ``mdla5`` for MDLA 5.x.

You must run each DLA variant only on platforms that support the corresponding MDLA version.

MDLA Version Mapping
====================

Use the following table to look up the MDLA version and the hardware accelerator supported by each Genio platform and select the matching DLA model:

.. csv-table:: MDLA Version and Supported Hardware Accelerator 
   :class: longtable
   :file: /_asset/tables/ml-platform-tflite-analytical-mdla-support.csv
   :width: 100%


Vision Tasks and Model Categories
=================================

The TFLite Analytical Model collection focuses on three primary visual AI tasks: image classification, object detection, and recognition.
Each model family page documents the conversion workflow and benchmark performance for representative models on MediaTek Genio platforms.

Image Classification
--------------------

Image classification is a fundamental computer vision task that predicts the category or class of an input image.
Unlike object detection, classification models do not provide object locations.
They output only the most likely label for the entire image.

For TFLite Analytical image classification models, the most common backbones are the following families on Genio platforms:

.. toctree::
   :maxdepth: 1

   DenseNet <litert_analytical/DenseNet>
   EfficientNet <litert_analytical/EfficientNet>
   MobileNetV2 <litert_analytical/MobileNetV2>
   MobileNetV3 <litert_analytical/MobileNetV3>
   ResNet <litert_analytical/ResNet>
   SqueezeNet <litert_analytical/SqueezeNet>
   VGG <litert_analytical/VGG>

Object Detection
----------------

Object detection is a key task in computer vision that identifies and localizes objects within an image.
Unlike classification, it outputs both the class and the bounding box of each detected object.

For TFLite Analytical object detection models, the most common backbones are the following families on Genio platforms:

.. toctree::
   :maxdepth: 1

   YOLOv5 <litert_analytical/YOLOv5s>
   YOLOv8 <litert_analytical/YOLOv8s>

Recognition
-----------

Recognition models identify or verify specific entities from input data, such as faces, persons, gestures, or text.
Unlike classification, which predicts a general category, recognition focuses on determining *who* or *what* a target object is.
These models often compare the target against a known database of identities or reference templates.


For TFLite Analytical recognition models, the most common backbones are the following families on Genio platforms:

.. toctree::
   :maxdepth: 1

   VGGFace <litert_analytical/VGGFace>

Community Contributed Models
----------------------------

In addition to the primary task categories, the collection includes **Community Contributed Models** that are provided by the community.
These models are shared without the original source training models, and model provenance or training recipes might not be available.

.. toctree::
   :maxdepth: 1

   Community Contributed Model <litert_analytical/community_contributed_model>

The available analytical and community contributed models for each task and Genio platform are listed in the tables below.

Supported Models on Genio Products
==================================

The following tables list the supported analytical models per Genio platform for each task category.

.. note::

   The performance statistics shown in these tables were measured using **offline inference** with **performance mode enabled** across different Genio products, models, and data types.

.. csv-table:: Models for Detection
   :class: longtable
   :file: /_asset/tables/ml-model-hub-detection.csv
   :width: 100%

.. csv-table:: Models for Classification
   :class: longtable
   :file: /_asset/tables/ml-model-hub-classification.csv
   :width: 100%

.. csv-table:: Models for Recognition
   :class: longtable
   :file: /_asset/tables/ml-model-hub-recognition.csv
   :width: 100%

Performance Notes and Limitations
=================================

.. note::

   The measurements were obtained using **Neuron SDK(neuronrt)**, and each model’s detail page (linked from the tables) provides additional information about the test setup and configuration.

   Performance can vary depending on:

   * The specific Genio platform and hardware configuration.
   * The version of the board image and evaluation kit (EVK).
   * The selected backend and model variant.

   To obtain the most accurate performance numbers for your use case, you must run the application directly on the target platform.

.. important::

   For **online inference on Yocto**, some models may not run on certain backends due to custom operators generated by the MediaTek converter.
   These custom operators (for example, ``MTK_EXT`` ops) are not recognized or supported by the standard TensorFlow Lite interpreter, which can lead to incompatibility issues during inference.
   In such cases, the corresponding entries in the tables are marked as ``N/A`` to indicate unavailable data.

   The exact cause of a failure or unsupported configuration may vary per model.
   For more details, refer to the model‑specific documentation.