MobileNetV3 vs MobileNe t
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- machine-learning
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's model configuration and documentation for the MobileNetV2 choice, then ask the maintainers for the intended explanation; done would be a documented rationale addressing MobileNetV2 versus MobileNetV3.
Written by the indexing model from the issue text.
Description
Hello, thanks for sharing the excellent work.
I'm curious about why you chose the MobileNetV2 rather than V3?
Thanks for replying.
- Dominant language
- Python
- Stars
- 282
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
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.
More from MegEngine/RepLKNet
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
plot receptive field Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
All issues in MegEngine/RepLKNet
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100