Getting Started
NOTE:
By default the application runs by pulling the pre-built images. If you want to build the images locally and then run the application, set the flag:
REGISTRY=false
usage: make <command> REGISTRY=false (applicable for all commands like benchmark, benchmark-stream-density..)
Example: make run-demo REGISTRY=false
(If this is the first time, it will take some time to download videos, models, docker images and build images)
Step by step instructions:
-
Download the models using download_models/downloadModels.sh
make download-models -
Update github submodules
make update-submodules -
Download sample videos used by the performance tools
make download-sample-videos -
Start Automated Self Checkout using the Docker Compose file.
make run-render-mode -
The above series of commands can be executed using only one command:
5. To build the images locally step by step: - Follow the following steps:make run-demo- Now build the pipeline-runner image locally:make download-models REGISTRY=false make update-submodules REGISTRY=false make download-sample-videos- Finally, start Automated self checkout using docker compose up.make build REGISTRY=false- The above series of commands can be executed using only one command:make run-render-mode REGISTRY=falsemake run-demo REGISTRY=false -
Verify Docker containers
Verify Docker images
Result:docker ps --format 'table{{.Names}}\t{{.Status}}\t{{.Image}}'NAMES STATUS IMAGE camera-simulator0 Up 12 seconds jrottenberg/ffmpeg:4.1-alpine src-ClientGst-1 Up 14 seconds dlstreamer:dev camera-simulator Up 13 seconds aler9/rtsp-simple-server -
Verify Results
After starting Automated Self Checkout you will begin to see result files being written into the results/ directory. Here are example outputs from the 3 log files.
gst-launch_
pipeline
r
-
Stop the containers:
When pre-built images are used-
make downWhen images are built locally-
make down REGISTRY=false