5 ms·

Hey, I'm the one who made the site. Thanks for your feedback. Most of the models listed on the site are taken from lists of deep learning resources (and framewo

Hey, I'm the one who made the site. Thanks for your feedback. Most of the models listed on the site are taken from lists of deep learning resources (and framework specific model zoos), so I did not validate every repo to ensure they actually offer pretrained models. I guess a more accurate text for the link would be "view code" or "more info" instead of "get model". Indeed a lot of papers don't release their models but just the code. The goal of the site was to create a common platform to search and aggregate models (or code) available for reimplementation. I'm planning to add tools to allow users to flag or report errors on pages, since most of the content is automatically scraped.

draugadrotten 8y ago
> I did not validate every repo to ensure they actually offer pretrained models. please do.
throwawaymath 8y ago
I hate to be "that guy" but I have pretty serious problems with the site and your response here. Respectfully, you're admitting that you're not doing the thing the website principally claims. It doesn't matter what you intended - the site is claiming that it aggregates pretrained models. Not only does it not do that, but it apparently only scrapes third party resources with little to no manual oversight in whether or not the e.g. code repository even contains a pretrained model. But wait: your plan going forward is to offload the moderation onto users?! So instead of being responsible for the content, the users (who ostensibly came to your site because they couldn't find what they were looking for) are now obligated to do due diligence. What's the difference between this and just searching GitHub for paper titles or keywords? The final issue I have is more meta. I don't really see the value of the site as implemented. Why are you automatically scraping all of these resources? Why don't you curate them yourself and demonstrate that competency to the community? As it stands this is blatantly misleading and seems like a transparent attempt to cash in views for buzzwords, regardless of whether or not the user is ultimately helped by the content. Sorry for being harsh, but this is kind of brazenly inept. I can understand that automatically scraping these resources gives you a lot of leeway to scale up inclusion to make it more viable. However you really can't just turn on a scraper, direct it at a few keywords and tell your users to sort it out. Users will want this site to make their lives easier instead of wading into the complexity themselves. You're not reducing that complexity, you're just adding another layer of abstraction to it.
Erlich_Bachman 8y ago
> I guess a more accurate text for the link would be "view code" or "more info" instead of "get model" It's not about accurate link caption. It's that you make a site with it's whole purpose being getting models, you call it "model zoo", and then you don't link to models and don't check whether models exist in all your links! A site for aggregating models (for the ones that provide it) and code already exists: it's github. Your site simply does not work.
karmakaze 8y ago
> so I did not validate every repo to ensure they actually offer pretrained models You don't have to manually verify each one--that's what machines are for. If you find a file that is recognized as a model list and link to the_model. Obviously a README is not a model.

draugadrotten 8y ago

> I did not validate every repo to ensure they actually offer pretrained models. please do.

throwawaymath 8y ago

I hate to be "that guy" but I have pretty serious problems with the site and your response here. Respectfully, you're admitting that you're not doing the thing the website principally claims. It doesn't matter what you intended - the site is claiming that it aggregates pretrained models. Not only does it not do that, but it apparently only scrapes third party resources with little to no manual oversight in whether or not the e.g. code repository even contains a pretrained model. But wait: your plan going forward is to offload the moderation onto users?! So instead of being responsible for the content, the users (who ostensibly came to your site because they couldn't find what they were looking for) are now obligated to do due diligence. What's the difference between this and just searching GitHub for paper titles or keywords? The final issue I have is more meta. I don't really see the value of the site as implemented. Why are you automatically scraping all of these resources? Why don't you curate them yourself and demonstrate that competency to the community? As it stands this is blatantly misleading and seems like a transparent attempt to cash in views for buzzwords, regardless of whether or not the user is ultimately helped by the content. Sorry for being harsh, but this is kind of brazenly inept. I can understand that automatically scraping these resources gives you a lot of leeway to scale up inclusion to make it more viable. However you really can't just turn on a scraper, direct it at a few keywords and tell your users to sort it out. Users will want this site to make their lives easier instead of wading into the complexity themselves. You're not reducing that complexity, you're just adding another layer of abstraction to it.

Erlich_Bachman 8y ago

> I guess a more accurate text for the link would be "view code" or "more info" instead of "get model" It's not about accurate link caption. It's that you make a site with it's whole purpose being getting models, you call it "model zoo", and then you don't link to models and don't check whether models exist in all your links! A site for aggregating models (for the ones that provide it) and code already exists: it's github. Your site simply does not work.

karmakaze 8y ago

> so I did not validate every repo to ensure they actually offer pretrained models You don't have to manually verify each one--that's what machines are for. If you find a file that is recognized as a model list and link to the_model. Obviously a README is not a model.