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

The output of the object category detected by onnxruntime C++ is all 0 #220

Closed
GitHubLuGeng opened this issue Oct 29, 2021 · 2 comments · Fixed by #221
Closed

The output of the object category detected by onnxruntime C++ is all 0 #220

GitHubLuGeng opened this issue Oct 29, 2021 · 2 comments · Fixed by #221
Assignees
Labels
bug / fix Something isn't working

Comments

@GitHubLuGeng
Copy link

🐛 Describe the bug

onnxruntime C++检测到的物体输出类型全是person
相同yolov5s v6.0 onnx模型python demo推理正确

如下图:
result_screenshot_29 10 2021

Versions

main

@zhiqwang
Copy link
Owner

Hi @GitHubLuGeng

boxes 信息似乎都是对的哈? person是 COCO 的第一类,似乎把 labels 都算成 0 了。

周末我实测一下看看问题是哪里导致的。

@zhiqwang zhiqwang added the bug / fix Something isn't working label Oct 29, 2021
@zhiqwang zhiqwang changed the title onnxruntime C++检测到的物体输出类型全是person The output of the object category detected by onnxruntime C++ is all 0 Oct 30, 2021
@zhiqwang
Copy link
Owner

zhiqwang commented Oct 30, 2021

Hi @GitHubLuGeng

The reason for this occurs should be a bug of the type casting of the following classId, it should be int64_t rather than float, we fixed this issue in #221 .

https://github.com/zhiqwang/yolov5-rt-stack/blob/b8d845d1c164d86723e79ed4ad0a288864becc12/deployment/onnxruntime/main.cpp#L150

Please pull the latest code to verify that this issue is fixed correctly.

And as such I'm closing this issue, feel free to reopen this or create a new ticket if you have more questions.

cc @itsnine @xiguadong .

@zhiqwang zhiqwang self-assigned this Oct 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug / fix Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants