docker:image-classification-tf-cpp.debian-9 (v2.5.0)
Creation date: 2019-06-01
Source: GitHub
cID: 88eef0cd8c43b68a:2a424213448998b2

Don't hesitate to get in touch if you encounter any issues or would like to discuss this community project!
Please report if this CK component works: 1  or fails: 0 
Sign up to be notified when artifacts are shared or updated!

Description  

This CK-powered container is our attempt to provide a common API to customize, build and run AI and ML applications with different models, frameworks, libraries, datasets, compilers, formats, backends and platforms. Our on-going project is to make the onboarding process as simple as possible via this platform. Please check this CK white paper and don't hesitate to contact us if you have suggestions or feedback!

ReadMe  

MLPerf Inference - Image Classification - TF C++ (Debian 9)

  1. Default image (based on Debian 9 latest)

NB: You may need to run commands below with sudo, unless you manage Docker as a non-root user.

Default image

Download

$ docker pull ctuning/image-classification-tf-cpp.debian-9

Build

$ ck build docker:image-classification-tf-cpp.debian-9

NB: Equivalent to:

$ cd `ck find docker:image-classification-tf-cpp.debian-9`
$ docker build -f Dockerfile -t ctuning/image-classification-tf-cpp.debian-9 .

Run

Image Classification (default command)

$ ck run docker:image-classification-tf-cpp.debian-9

NB: Equivalent to:

$ docker run --rm ctuning/image-classification-tf-cpp.debian-9 \
"ck run program:image-classification-tf-cpp --dep_add_tags.weights=mobilenet,non-quantized --env.CK_BATCH_COUNT=2"

Image Classification (custom command)

$ docker run --rm ctuning/image-classification-tf-cpp.debian-9 \
"ck run program:image-classification-tf-cpp --dep_add_tags.weights=resnet --env.CK_BATCH_COUNT=10"

Bash

$ docker run -it --rm ctuning/image-classification-tf-cpp.debian-9 bash

Versions  

Files  

Comments  

Please log in to add your comments!
If you notice any inapropriate content that should not be here, please report us as soon as possible and we will try to remove it within 48 hours!