Resnet50, SqueezeNet and VGG19 represented twice from different source frameworks
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9.8k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
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:
- Resnet50
- SqueezeNet (different revisions of the network, likely makes sense to leave both but should consolidate their paths)
- VGG19
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the model directories at resnet50, squeezenet, models/image_classification/squeezenet, and vgg19, along with the linked model-zoo artifacts. Determine whether the variants are duplicates or meaningful revisions, then consolidate their locations or document their differences. Done means the affected models have one clear organization and consumers are no longer confused by duplicate paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- machine-learning
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100