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

Different Results on GPU vs CPU #6528

Open
VisionEp1 opened this issue Aug 21, 2020 · 4 comments
Open

Different Results on GPU vs CPU #6528

VisionEp1 opened this issue Aug 21, 2020 · 4 comments
Labels
Likely bug Maybe a bug, maybe not

Comments

@VisionEp1
Copy link

VisionEp1 commented Aug 21, 2020

see last comment- better problem description

@VisionEp1
Copy link
Author

VisionEp1 commented Aug 22, 2020

update it happens also with the normal pre trained yolov4 file
yolov4.cfg.txt

image

i used the most recent opencv version + the most recent darknet.

windows with cmake (one time i disabled cuda+cudnn via cmake the other time i didnt)

4-5% confidence difference seems huge to me

@VisionEp1
Copy link
Author

image
or with lower confidence. even more different

@VisionEp1
Copy link
Author

after days of testing.

avx is the issue after forcing is_avx to -1 everything works perfect.
might be linked with
see issue: #5793

@AlexeyAB AlexeyAB added the Likely bug Maybe a bug, maybe not label Aug 23, 2020
@truongbv1
Copy link

truongbv1 commented May 6, 2024

Hi, @AlexeyAB
I see another bug that causes different results on GPU and CPU
GPU=1 - working properly
GPU=0 - not working properly
with GPU=0, you missed the case of RELU6 in float activate(float x, ACTIVATION a), if use RELU6 activation func then all return 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Likely bug Maybe a bug, maybe not
Projects
None yet
Development

No branches or pull requests

3 participants