Commit 07d80bc5 authored by GONZALES ZUNIGA Juan Diego's avatar GONZALES ZUNIGA Juan Diego
Browse files

Update README

parent 137e55ad
# DOCKERVINO
Dockervino = Docker + Openvino
DockerVINO = Docker + OpenVINO
## Introduction
The current version of Openvino is only available on Ubuntu 16.04 and Centos 4.
The current version of OpenVINO is only available on Ubuntu 16.04 and Centos 4.
I needed Openvino on different platforms such as Fedora, Centos, Ubuntu 18.04.
I needed OpenVINO on different platforms such as Fedora, Centos, Ubuntu 18.04.
So, the logical option was to create a Docker image.
......@@ -15,7 +15,7 @@ So, the logical option was to create a Docker image.
-Docker CE
-Openvino TGZ file. Currently using 2019_R2, l_openvino_toolkit_p_2019.2.242.tgz.
-Openvino TGZ file. Currently using 2019_R3.1, l_openvino_toolkit_p_2019.3.376.tgz.
-Download from https://software.intel.com/en-us/openvino-toolkit/choose-download/free-download-linux
......@@ -24,26 +24,24 @@ The final image is around 3GB but the in between images can make up to 8GB.
## Instructions
Since Openvino releases are quite frequent (2019_R2 now), I choose to make the dockerfile public instead of the Docker images.
You may want to experiment with other tgz Openvino versions.
Since Openvino releases are quite frequent (2019_R3.1 now), I choose to make the dockerfile public instead of the Docker images.
You may want to experiment with other tgz OpenVINO versions.
We have 6 images
We have 5 images
phase1 -- installs the Openvino SDK
phase1 -- installs the Openvino SDK, launches a small benchmark
phase2 -- downloads the demo_squeezenet_download_conver_run
phase3 -- downloads the ssd, yolov3, humanpose, face motion, maskrcnn models and convert them to FP32 and FP16
phase2 -- downloads various dl models
demo -- reduces space, adds script to run examples
benchmark -- adds different traditional networks (vgg, resnet, inception)
debug -- adds debugging tools to the image.
debug -- adds debugging tools to the image to use with open_model_zoo repo
You need to build phase1 first then phase2, phase3, demo, benchmark and at last debug
You need to build phase1 first then phase2, demo, benchmark and at last debug
```sh
bash buildcmd
```
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment