Running AI Model Inference
This is a walkthrough for running predictions. You'll learn about input data types, understanding the results, and finally processing inputs in batches for efficiency.
Running AI Model Inference
Once you loaded an AI model and obtained a model handling object, you can start doing AI inferences on your model. The degirum.model.Model class has two methods for performing AI inference:
degirum.model.Model.predict: Runs prediction on a single data frame.
degirum.model.Model.predict_batch: Runs prediction on a batch of frames.
Model.predict()
The predict()
method takes a single input data frame and returns an inference result object. You can also call this method by calling degirum.model.Model.__call__
. This is an alias for Model()
. See Single Frame Inference for more information.
Example:
Model.predict_batch()
The predict_batch()
method takes an iterator object of data frames (such as a list or stream) and returns a generator object. It processes the iterator object in a pipelined manner, which is more efficient than calling predict()
repeatedly in a loop. This method is ideal for processing a list of images or a video stream. See the Batch Inference section for more information.
Supported Input Data Types
PySDK models can handle images and raw tensors as data types.
The input you pass to predict()
depends on the number of inputs the model has. If the model has one input, then you pass only one object to predict()
.
The model may have multiple inputs. In this case, the data you pass to predict()
is a list of objects: one object per corresponding input.
Check Input Data Type of Your Model
You can check what input type your model expects by inspecting the model.model_info.InputType
property.
In this example, we check the input data type of our model.
The InputType
property of the ModelParams
class returned by the degirum.model.Model.model_info property describes the number and the type of inputs of the model (see Model Info section for details about model info properties).
The model_info.InputType
property returns a list of input types (one entry per model input). The length of this list tells you how many separate inputs the model expects. For instance, a model that takes two images will have two entries in this list.
Images
If your model expects image inputs (InputType == "Image"
), you can supply the input frame in any of the following formats:
Path to an image file.
HTTP URL to an image.
NumPy array.
PIL
Image
object.Raw
bytes
of image data.
PySDK will automatically convert these inputs into the format required by the model’s neural network, according to the model’s preprocessor settings in its JSON configuration. You may read more about the preprocessor parameters here.
Tensors
If your model expects raw tensor inputs (InputType == "Tensor"
), you should provide a multi-dimensional NumPy array with the appropriate shape and data type.
The array’s dimensions must match the model’s expected input shape, which you can find in the model info (model.model_info.InputShape
). The data type of the array’s elements should match the model’s expected raw data type (model.model_info.InputRawDataType
).
Single Frame Inference
When you want to process one frame, use predict()
.
Batch Inference
When you have multiple frames to process, use predict_batch()
. The predict_batch()
method runs predictions on an iterable list of frames. These predictions are run in a pipeline, which maximizes throughput and is more efficient than calling predict()
in a loop.
The predict_batch
method accepts single parameter: an iterator object, for example, a list. You populate your iterator object with the same type of data you pass to regular predict()
, i.e. input image path strings, input image URL string, NumPy arrays, or PIL Image objects (in case of PIL image backend).
predict_batch()
returns a generator of results. You can loop over these results just as you would iterate through results from successive predict()
calls.
Since predict_batch
returns a generator, simply calling the method won’t immediately run the inference. Frames are processed only when you iterate over the returned generator (for example, in a for
loop).
Example: Iterating over predict_batch results
Example: Using predict_batch()
on a video file
predict_batch()
on a video fileIn this example, we use predict_batch()
to process a video file. The frame_source
generator yields frames from the video, and for each frame, the model’s predictions are obtained. We then overlay the results on the frame (result.image_overlay
) and display it using OpenCV.
Inference Results
When you call predict()
, you get back an inference result object derived from the degirum.postprocessor.InferenceResults class. Likewise, when you callpredict_batch()
, you get a generator object that yields inference result objects. These result classes are called postprocessors. Particular postprocessor class types depend on the AI model type: classification, object detection, pose detection, segmentation, and etc. From your point of view, they deliver identical functionality.
InferenceResults
objects contain the following data:
degirum.postprocessor.InferenceResults.image: Original input image as a NumPy array or PIL image.
degirum.postprocessor.InferenceResults.image_overlay: Original image with inference results drawn on top. The drawing is model-dependent:
Classification models: class labels with probabilities are printed below the original image.
Object detection models: bounding boxes are printed on the original image.
Hand and pose detection models: keypoints and keypoint connections are printed on the original image.
Segmentation models: segments are printed on the original image.
degirum.postprocessor.InferenceResults.results: Keeps a list of inference results in dictionary form. Follow the property link for detailed explanation of all result formats.
degirum.postprocessor.InferenceResults.image_model: Preprocessed image tensor that was fed into the model (in binary form). Populated only if you enable Model.save_model_image before performing predictions.
The results property is what you will typically use in your code. This property contains the core prediction data. Note that if the model outputs coordinates (e.g., bounding boxes), these have been converted back to the coordinates of the original image for your convenience.
Example: Combine predict_batch() with image_overlay to show prediction results on original video
Last updated
Was this helpful?