Machine Learning

1 readers

1 users here now

Community Rules:

Be nice. No offensive behavior, insults or attacks: we encourage a diverse community in which members feel safe and have a voice.
Make your post clear and comprehensive: posts that lack insight or effort will be removed. (ex: questions which are easily googled)
Beginner or career related questions go elsewhere. This community is focused in discussion of research and new projects that advance the state-of-the-art.
Limit self-promotion. Comments and posts should be first and foremost about topics of interest to ML observers and practitioners. Limited self-promotion is tolerated, but the sub is not here as merely a source for free advertisement. Such posts will be removed at the discretion of the mods.

founded 1 year ago

MODERATORS

communick@academy.garden

[D] Is it a good idea to use VGG16 for a image classification mobile app? (alien.top)

submitted 1 year ago by Rhet98@alien.top to c/machinelearning@academy.garden

5 comments fedilink hide all child comments

I'm new to image classification and ML and this is going to be my first project on those topics. I'm considering using VGG16 because I saw some studies showing that it has a generally great accuracy score (80-95%) but I'm worried that the model might not be fast enough or the app file size might get massive if I want the app to be usable without internet connection.

What do you guys think?

you are viewing a single comment's thread
view the rest of the comments

[–] shubham0204_dev@alien.top 1 points 1 year ago

You may use MobileNet models as they use separable convolutions, which have lesser parameters and execution time than simple/regular convolutions. Moreover, MobileNets are easy to train and setup (tf.keras.applications.* has a pre-trained model) and can be used as a backbone model for fine-tuning on datasets other than the ImageNet.

Further, you can also explore quantization and weight pruning. These are some techniques that can be used to optimize models to have a smaller memory footprint and smaller execution time on embedded devices.