Bmw Yolov4 Inference Api Cpu

This is a repository for an nocode object detection inference API using the Yolov4 and Yolov3 Opencv.
Alternatives To Bmw Yolov4 Inference Api Cpu
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Pytorch Yolo V32,720
4 years ago99Python
A PyTorch implementation of the YOLO v3 object detection algorithm
10 months ago6apache-2.0Python
OpenCV-Python4.1 中文文档
2 years ago18mitPython
🚀 The TensorFlow Object Counting API is an open source framework built on top of TensorFlow and Keras that makes it easy to develop object counting systems!
a year ago9apache-2.0Python
Label images and video for Computer Vision applications
2 years ago27mitPython
:oncoming_automobile: "MORE THAN VEHICLE COUNTING!" This project provides prediction for speed, color and size of the vehicles with TensorFlow Object Counting API.
Multi Object Tracker622
8 days agomitPython
Multi-object trackers in Python
3 years ago19mitJupyter Notebook
Data Augmentation For Object Detection
Multi Camera Live Object Tracking562
a year ago22gpl-3.0Python
Multi-camera live traffic and object counting with YOLO v4, Deep SORT, and Flask.
Openvino Yolov3530
a year ago51apache-2.0Python
YoloV3/tiny-YoloV3+RaspberryPi3/Ubuntu LaptopPC+NCS/NCS2+USB Camera+Python+OpenVINO
Yolo3 4 Py521
12 years ago7March 18, 20214apache-2.0Python
A Python wrapper on Darknet. Compatible with YOLO V3.
Alternatives To Bmw Yolov4 Inference Api Cpu
Select To Compare

Alternative Project Comparisons

YOLO v4-v3 CPU Inference API for Windows and Linux

This is a repository for an object detection inference API using the Yolov4 and Yolo v3 Opencv.

The inference REST API works on CPU and doesn't require any GPU usage. It's supported on both Windows and Linux Operating systems.

Models trained using our training Yolov4 or Yolov3 repository can be deployed in this API. Several object detection models can be loaded and used at the same time.

This repo can be deployed using either docker or docker swarm.

Please use docker swarm only if you need to:

  • Provide redundancy in terms of API containers: In case a container went down, the incoming requests will be redirected to another running instance.

  • Coordinate between the containers: Swarm will orchestrate between the APIs and choose one of them to listen to the incoming request.

  • Scale up the Inference service in order to get a faster prediction especially if there's traffic on the service.

If none of the aforementioned requirements are needed, simply use docker.

predict image


  • OS:
    • Ubuntu 16.04/18.04
    • Windows 10 pro/enterprise
  • Docker

Check for prerequisites

To check if you have docker-ce installed:

docker --version

Install prerequisites


Use the following command to install docker on Ubuntu:

chmod +x && source

Windows 10

To install Docker on Windows, please follow the link.

P.S: For Windows users, open the Docker Desktop menu by clicking the Docker Icon in the Notifications area. Select Settings, and then Advanced tab to adjust the resources available to Docker Engine.

Build The Docker Image

In order to build the project run the following command from the project's root directory:

sudo docker build -t yolov4_inference_api_cpu -f ./docker/dockerfile .

Behind a proxy

sudo docker build --build-arg http_proxy='' --build-arg https_proxy='' -t yolov4_inference_api_cpu -f ./docker/dockerfile .

Run The Docker Container

As mentioned before, this container can be deployed using either docker or docker swarm.

If you wish to deploy this API using docker, please issue the following run command.

If you wish to deploy this API using docker swarm, please refer to following link docker swarm documentation. After deploying the API with docker swarm, please consider returning to this documentation for further information about the API endpoints as well as the model structure sections.

To run the API, go the to the API's directory and run the following:

Using Linux based docker:

sudo docker run -itv $(pwd)/models:/models -v $(pwd)/models_hash:/models_hash -p <docker_host_port>:7770 yolov4_inference_api_cpu

Using Windows based docker:

docker run -itv ${PWD}/models:/models -v ${PWD}/models_hash:/models_hash -p <docker_host_port>:7770 yolov4_inference_api_cpu

The <docker_host_port> can be any unique port of your choice.

The API file will be run automatically, and the service will listen to http requests on the chosen port.

API Endpoints

To see all available endpoints, open your favorite browser and navigate to:


The 'predict_batch' endpoint is not shown on swagger. The list of files input is not yet supported.

P.S: If you are using custom endpoints like /load, /detect, and /get_labels, you should always use the /load endpoint first and then use /detect or /get_labels

Endpoints summary

/load (GET)

Loads all available models and returns every model with it's hashed value. Loaded models are stored and aren't loaded again

load model

/detect (POST)

Performs inference on specified model, image, and returns bounding-boxes

detect image

/get_labels (POST)

Returns all of the specified model labels with their hashed values

get model labels

/models/{model_name}/predict_image (POST)

Performs inference on specified model, image, draws bounding boxes on the image, and returns the actual image as response

predict image

/models (GET)

Lists all available models

/models/{model_name}/load (GET)

Loads the specified model. Loaded models are stored and aren't loaded again

/models/{model_name}/predict (POST)

Performs inference on specified model, image, and returns bounding boxes.

/models/{model_name}/labels (GET)

Returns all of the specified model labels

/models/{model_name}/config (GET)

Returns the specified model's configuration

/models/{model_name}/predict_batch (POST)

Performs inference on specified model and a list of images, and returns bounding boxes

P.S: Custom endpoints like /load, /detect, and /get_labels should be used in a chronological order. First you have to call /load, and then call /detect or /get_labels

Model structure

The folder "models" contains subfolders of all the models to be loaded. Inside each subfolder there should be a:

  • Cfg file (yolo-obj.cfg): contains the configuration of the model

  • Weights file (yolo-obj.weights)

  • Names file (obj.names) : contains the names of the classes

  • Config.json (This is a json file containing information about the model)

        "inference_engine_name": "yolov4_opencv_cpu_detection",
        "confidence": 60,
        "nms_threshold": 0.6,
        "image": {
          "width": 416,
          "height": 416,
          "scale": 0.00392,
          "swapRB": true,
          "crop": false,
          "mean": {
            "R": 0,
            "G": 0,
            "B": 0
        "framework": "yolo",
        "type": "detection",
        "network": "network_name"


    • You can choose "inference_engine_name": between yolov4_opencv_cpu_detection and yolov3_opencv_cpu_detection depending on the model you have.

    • You can change confidence and nms_threshold values while running the API

    • The API will return bounding boxes with a confidence higher than the "confidence" value. A high "confidence" can show you only accurate predictions


Network\Hardware Intel Xeon CPU 2.3 GHz Intel Core i9-7900 3.3 GHZ Tesla V100
COCO Dataset 0.259 seconds/image 0.281 seconds/image 0.0691 seconds/image


Antoine Charbel, , Beirut, Lebanon

Daniel Anani,, Beirut, Lebanon

Hadi Koubeissy, Beirut, Lebanon

Popular Opencv Projects
Popular Object Detection Projects
Popular Machine Learning Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Deep Learning
Rest Api
Neural Network
Computer Vision
Object Detection
Deep Neural Networks
Bounding Boxes