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

Difference with 0.2.0 vs 0.1.0 #57

Open
hgaiser opened this issue Jun 18, 2019 · 1 comment · Fixed by fizyr-forks/keras-resnet#2
Open

Difference with 0.2.0 vs 0.1.0 #57

hgaiser opened this issue Jun 18, 2019 · 1 comment · Fixed by fizyr-forks/keras-resnet#2

Comments

@hgaiser
Copy link
Contributor

hgaiser commented Jun 18, 2019

The network architecture in 0.2.0 is no longer identical to that in the original Caffe implementation. I am using the ResNet50 imagenet weights available here, which were generated using the caffe weights and this tool.

On some Tabby Cat image I get the following predictions from 0.1.0:

[[('n02123045', 'tabby', 0.4307788), ('n02124075', 'Egyptian_cat', 0.32408533), ('n02123159', 'tiger_cat', 0.18477823), ('n02127052', 'lynx', 0.008598777), ('n03443371', 'goblet', 0.0048426227)]]

On 0.2.0:

[[('n02123045', 'tabby', 0.39859685), ('n02124075', 'Egyptian_cat', 0.26450825), ('n02123159', 'tiger_cat', 0.22655205), ('n02127052', 'lynx', 0.012361869), ('n03443371', 'goblet', 0.00793589)]]

If I find some more time, I will also show the results using Caffe. But for now, it is clear that there is an unintended difference between 0.2.0 and 0.1.0. I believe this difference comes from 5005c37 . @0x00b1 do you know why that commit was applied?

hgaiser added a commit to fizyr/keras-retinanet that referenced this issue Jul 5, 2019
@hgaiser
Copy link
Contributor Author

hgaiser commented Jul 26, 2019

@0x00b1 , any feedback on this?

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.

1 participant