-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Resnet50, SqueezeNet and VGG19 represented twice from different source frameworks #82
Comments
For the case of SqueezeNet models, there are not only two different models, but also one of the models results in poor accuracy values when I execute it. For the first SqueezeNet model the link is given as the following: The probabilities that I get after executing this model is given below:
Whereas, for the second model, the probabilities predicted for each class is pretty inaccurate. The link to this model is given as the following: The probabilities are also given below:
|
Right now, I think, the top priority thing is getting them correct. All models here should conform to ONNX standard, and have a reasonable accuracy. I don't think it's a good time point to dedup models. Let's close issues like: #90 first. |
@snnn What I mentioned above is not related to models being duplicate but rather one model having a really low accuracy value (not being correct) compared to the other one. |
The model zoo currently contains three models (Resnet50, SqueezeNet and VGG19) that each have two variants which is confusing to end consumers.
Ideally these should be de-duplicated. If that doesn't make sense then they should state their differences outside of origin framework and be organized in a way that places them all in the same sub-folder/path on the repo.
Following are pointers to the existing duplicated models:
The text was updated successfully, but these errors were encountered: