Custom learning blocks are a way to extend the capabilities of Edge Impulse beyond the learning blocks built into the platform. If none of the existing blocks created by Edge Impulse fit your needs, you can create custom learning blocks to integrate your own model architectures for unique project requirements. Ready to dive in and start building? Jump to the examples!
Custom learning blocks are available for all usersUnlike other custom blocks, which are only available to customers on the Enterprise plan, custom learning blocks are available to all users of the platform. If you are an enterprise customer, your custom learning blocks will be available in your organization. If you are not an enterprise customer, your custom learning blocks will be available in your developer profile.
Expert modeIf you only want to make small modifications to the neural network architecture or loss function, you can instead use expert mode directly in Studio, eliminating the need to create a custom learning blocks. Go to any learning block settings page, select the three dots, and select Switch to Keras (expert) mode.

​
Block structure

The learning block structure is shown below. Please see the custom blocks overview page for more details.

Custom learning block structure

​
Block interface

The sections below define the required and optional inputs and the expected outputs for custom learning blocks.

​
Inputs

Learning blocks have access to command line arguments and training data.

​
Command line arguments

The parameters defined in your parameters.json file will be passed as command line arguments to the script you defined in your Dockerfile as the ENTRYPOINT for the Docker image. Please refer to the parameters.json documentation for further details about creating this file, parameter options available, and examples. In addition to the items defined by you, the following arguments will be automatically passed to your custom learning block.
ArgumentPassedDescription
--info-file <file>AlwaysProvides the file path for train_input.json as a string. The train_input.json file contains configuration details for model training options. See train_input.json.
--data-directory <dir>AlwaysProvides the directory path for training/validation datasets as a string.
--out-directory <dir>AlwaysProvides the directory path to the output directory as a string. This is where block output needs to be written.
--epochs <value>ConditionalPassed if no custom parameters are provided. Provides the number of epochs for model training as an integer.
--learning-rate <value>ConditionalPassed if no custom parameters are provided. Provides the learning rate for model training as a float.

​
Data

Learning blocks operate on data that has already been processed by an input block and a processing block. This processed data is available to your learning block in a single directory, in the NumPy format, and already split into training (train) and validation (test) datasets. By default the train/validation split is 80/20. You can change this ratio using the advanced training settings. The NumPy datasets can be converted to the required format (e.g. tf.data.Dataset) for your model and batched as desired within your custom learning block training script. In addition to the datasets, a sample_id_details.json file (see sample_id_details.json) is located within the data directory. The location of this directory is specified by the --data-directory <dir> argument and its structure is shown below. 
data/
├── X_split_test.npy
├── X_split_train.npy
├── Y_split_test.npy
├── Y_split_train.npy
└── sample_id_details.json
The X_*.npy files are float32 arrays in the appropriate shape. You can typically load these into your training pipeline without any modification. The Y_*.npy files are int32 arrays with four columns: label_index, sample_id, sample_slice_start_ms, and sample_slice_end_ms, unless the labels are bounding boxes. See below.

​
Image data

The X_*.npy files follow the NHWC (batch_size, height, width, channels) format for image data. The Y_*.npy files are a JSON array in the form of: 
[
    {
        "sampleId": 234731,
        "boundingBoxes": [
            {
                "label": 1,
                "x": 260,
                "y": 313,
                "w": 234,
                "h": 261
            }
        ]
    }
]
Image data is formatted as NHWCIf you need your data in the channels-first, NCHW format, you will need to transpose the input data yourself before training your model.
Image data is provided to your custom learning block in the NHWC (batch_size, height, width, channels) format. If you are training a PyTorch model that requires data to be in the NCHW (batch_size, channels, height, width) format, you will need to transpose the data before training your model. You do not need to worry about this when running on device. As long as your custom learning block outputs an ONNX model, the required transpose will be handled for you in the Edge Impulse SDK.
Image data is formatted as RGBIf you have a model that requires BGR input, you will need to transpose the first and last channels.
For models that require BGR channel format, you can have Edge Impulse automatically transpose the first and last channels by selecting the RGB->BGR option when configuring pixel scaling for your block. See below.
Image data has pixels that are already scaledThere is no need to scale the pixel values yourself for training nor for inference on-device. If the options provided in Edge Impulse do not suit your needs, please contact us to let us know what option(s) you require.
Image data is provided to your learning block with pixels that are already scaled. Pixel scaling is handled automatically by Edge Impulse. There are several options to scale your pixels, some of which include additional processing (e.g. standardization or centering):
  • Pixels ranging 0..1 (not normalized)
  • Pixels ranging -1..1 (not normalized)
  • Pixels ranging -128..127 (not normalized)
  • Pixels ranging 0..255 (not normalized)
  • PyTorch (pixels ranging 0..1, then standardized using ImageNet mean/std)
  • RGB->BGR (pixels ranging 0..255, then centered using ImageNet mean)
This can be configured when initializing your custom learning block with the Edge Impulse CLI, and changed later in Studio if required by editing your custom learning block.

​
Outputs

The expected output from your custom learning block should be in TensorFlow SavedModel, TFLite, ONNX, or pickled scikit-learn format. For object detection models, it is also important to ensure that the output layer of your model is supported by Edge Impulse.

​
File output options

TFLite file(s):
  • model.tflite - a TFLite file with float32 inputs and outputs
  • model_quantized_int8_io.tflite - a quantized TFLite file with int8 inputs and outputs
At least one of the above file options is required (both are recommended). If the source of the TFLite files are a TensorFlow SavedModel, then also write the saved_model.zip file. TensorFlow SavedModel:
  • saved_model.zip - a TensorFlow SavedModel file
Edge Impulse automatically converts this file to both unquantized and quantized TFLite files after training. ONNX file:
  • model.onnx - an ONNX file with int8, float16 or float32 inputs and outputs
Edge Impulse automatically converts this file to both unquantized and quantized TFLite files after training. Pickled scikit-learn file:
  • model.pkl - a pickled instance of the scikit-learn model
Edge Impulse will automatically convert this file to the required format. Note that arbitrary scikit-learn pipelines cannot be converted. For a list of supported model types, please refer to Supported classical ML algorithms. Internally Edge Impulse uses scikit-learn==1.3.2 for conversion, so pin to this scikit-learn version for best results. LightGBM (3.3.5) and XGBOOST (1.7.6) models are also supported.

​
Object detection output layers

Unfortunately object detection models typically don’t have a standard way to go from neural network output layer to bounding boxes. Currently Edge Impulse supports the following types of output layers. The most up-to-date list can be found in the API documentation for ObjectDetectionLastLayer.
  • FOMO
  • MobileNet SSD
  • NVIDIA TAO RetinaNet
  • NVIDIA TAO SSD
  • NVIDIA TAO YOLOv3
  • NVIDIA TAO YOLOv4
  • YOLOv2 for BrainChip Akida
  • YOLOv5 (coordinates scaled 0..1)
  • YOLOv5 (coordinates in absolute values)
  • YOLOv7
  • YOLOv11 (coordinates scaled 0..1)
  • YOLOv11 (coordinates in absolute values)
  • YOLOX
  • YOLO Pro

​
Configuring advanced training settings

After pushing your custom learning block to Edge Impulse, in Studio you will notice that below the section of custom parameters that you have exposed for your block, there is another section titled “Advanced training settings”. These settings allow you to optionally adjust the train/validation split, split on a metadata key, and profile the int8 version of your model. If you are testing your block locally using the edge-impulse-blocks runner tool as described below, you can adjust the train/validation split using the --validation-set-size <size> argument but you are unable to split using a metadata key. To profile your model after training locally, see Getting profiling metrics.

​
Getting profiling metrics

After training a custom learning block locally, you can use the profiling API to get latency, RAM and ROM estimates. This is very useful as you can immediately see whether your model will fit on device or not. Additionally, you can use this API as part your experiment tracking (e.g. in Weights & Biases or MLFlow) to wield out models that won’t fit your latency or memory constraints. You can also use the Python SDK to profile your model easily. See here for an example on how to profile a model created in Keras.

​
Editing built-in blocks

Most learning blocks built in the Edge Impulse (e.g. classifier, regression, or FOMO blocks) can be edited locally and then pushed back to Edge Impulse as a custom block. This is great if you want to make heavy modifications to these training pipelines, for example to do custom data augmentation. To download a block, go to any learning block settings page in your project, click the three dots, and select Edit block locally. Once downloaded, follow the instructions in the README file.

Option to edit a built-in block locally

​
Initializing the block

When you are finished developing your block locally, you will want to initialize it. The procedure to initialize your block is described in the custom blocks overview page. Please refer to that documentation for details.

​
Testing the block locally

The train_input.json file is not available when training locallyIf your script needs information that is contained within train_input.json, you will not be able to train locally. You will either need to push your block to Edge Impulse to train and test in Studio or alter your training script such that you can pass in that information (or eliminate it all together).
To speed up your development process, you can test and train your custom learning block locally. There are two ways to achieve this. You will need to have Docker installed on your machine for either approach.

​
With blocks runner

For the first method, you can use the CLI edge-impulse-blocks runner tool. See Block runner for additional details. The runner expects the following arguments for learning blocks.
ArgumentDescription
--epochs <number>If not provided, you will be prompted to enter a value.
--learning-rate <learningRate>If not provided, you will be prompted to enter a value.
--validation-set-size <size>Defaults to 0.2 but can be overwritten.
--input-shape <shape>Automatically identified but can be overwritten.
--extra-args <args>Additional arguments for your script.
For the additional arguments, you will need to provide the data directory (/home), an output directory (e.g. /home/out), and any other parameters required for your script. 
 edge-impulse-blocks runner --extra-args "--data-directory /home --out-directory /home/out --custom-param foo"
Using the above approach will create an ei-block-data directory within your custom block directory. It will contain a subdirectory with the associated project ID as the name - this is the directory that gets mounted into the container as /home. The first time you enter the above command, you will be asked some questions to configure the runner. Follow the prompts to complete this. If you would like to change the configuration in future, you can execute the runner command with the --clean flag.

​
With Docker

For the second method, you can use the block runner to download the required data from your project, then build the Docker image and run the container directly. The advantage of this approach is that you do not need to go through the feature generation and data splitting process each time you want to train your block. If your data changes, you can download it again. 
edge-impulse-blocks runner --download-data data/

docker build -t custom-learning-block .
docker run --rm -v $PWD/data:/data custom-learning-block --epochs 30 --learning-rate 0.01 --data-directory /data --out-directory /data/out --custom-param foo

​
Pushing the block to Edge Impulse

When you have initalized and finished testing your block locally, you will want to push it to Edge Impulse. The procedure to push your block to Edge Impulse is described in the custom blocks overview page. Please refer to that documentation for details.

​
Using the block in a project

After you have pushed your block to Edge Impluse, it can be used in the same way as any other built-in block.

​
Examples

Edge Impulse has developed several example custom learning blocks. The code for these blocks can be found in public repositories under the Edge Impulse GitHub account. The repository names typically follow the convention of example-custom-ml-<description>. As such, they can be found by going to the Edge Impulse account and searching the repositories for ml-block. Below are direct links to some examples:

​
Troubleshooting

​
Additional resources