Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yad2k.py Unsupported yolo_0(yolov3-tiny)? #144

Open
zihaozhang9 opened this issue Aug 23, 2018 · 1 comment · May be fixed by #154
Open

yad2k.py Unsupported yolo_0(yolov3-tiny)? #144

zihaozhang9 opened this issue Aug 23, 2018 · 1 comment · May be fixed by #154

Comments

@zihaozhang9
Copy link

i use ‘python yad2k.py yolov3-tiny.cfg yolov3-tiny.weights model_data/yolov3-tiny.h5’ .But Throw an exception:

Parsing section yolo_0
Traceback (most recent call last):
File "yad2k.py", line 270, in
_main(parser.parse_args())
File "yad2k.py", line 249, in _main
'Unsupported section header type: {}'.format(section))
ValueError: Unsupported section header type: yolo_0

@zihaozhang9 zihaozhang9 changed the title yad2k.py Unsupported yolo_0? yad2k.py Unsupported yolo_0(yolov3-tiny)? Aug 23, 2018
@prakharcode prakharcode linked a pull request Nov 18, 2018 that will close this issue
@tanzeel-ur-rehman-khan
Copy link

@prakharcode used your changed file as well, but it says (buffer is too small for requested array) for last two layers (conv_20 and yolo_1). i'm actually trying to convert YOLO v4-tiny .weights file into .h5 format so that i can access those weights and reuse them in my own code in c++. i've tried all convert.py files and yad2k.py files on internet but same issue. the cfg and weights file works fine itself when read from cv.dnn.readfromdarkent("cfg path", "weights path") but i need to acess weights as floating point values arrays and always stuck on last two layers, can you plzz help me in this case, i'd be grateful to you. i've attached my cfg file and weights file along with some convert files i tried but each time ended up having the same issue.
yolov4-tiny.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants