Skip to content

YOLOv3 support#11322

Merged
opencv-pushbot merged 1 commit intoopencv:3.4from
dkurt:dnn_yolov3
Apr 18, 2018
Merged

YOLOv3 support#11322
opencv-pushbot merged 1 commit intoopencv:3.4from
dkurt:dnn_yolov3

Conversation

@dkurt
Copy link
Copy Markdown
Member

@dkurt dkurt commented Apr 16, 2018

This pullrequest changes

YOLOv3 support

resolves #11310

Efficiency measurements:

Backend, Target Median time per 416x416 image
DNN_BACKEND_DEFAULT, DNN_TARGET_CPU 216.11ms
DNN_BACKEND_DEFAULT, DNN_TARGET_OPENCL 353.77ms

CPU: Intel® Core™ i7-6700K CPU @ 4.00GHz x 8
GPU: Intel® HD Graphics 530 (Skylake GT2)

Merge with extra: opencv/opencv_extra#459

@dkurt dkurt mentioned this pull request Apr 16, 2018
@vpisarev vpisarev self-assigned this Apr 18, 2018
@vpisarev
Copy link
Copy Markdown
Contributor

another great new feature! 👍

@opencv-pushbot opencv-pushbot merged commit 97fec07 into opencv:3.4 Apr 18, 2018
opencv-pushbot pushed a commit that referenced this pull request Apr 18, 2018
@SoullessStone
Copy link
Copy Markdown

Thanks a lot!

@ASShusharin
Copy link
Copy Markdown

Hi, I try to run dnn/object_detection.cpp with params: -c=yolov3.cfg -m=yolov3.weights -classes=coco.names --scale=0.00392 --width=416 --height=416 and it works, but time it takes for one image is about 4 seconds. Function: net.forward(outs, getOutputsNames(net)) takes the most time.
Although on the image (https://drive.google.com/open?id=1kZIUS5Dct3sPRZrMKsixFCWLgizbKnzd) on top is written about 745 ms. I run in release and use opencv4.
Also on top of this page is written that median time per 416x416 image is 216.11ms.
What may be the reason of this time difference?
I have Ubuntu OS: https://drive.google.com/open?id=1MvbLah4gNFB-P2JvW5P5MZ7znhlX5u8Y

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants