Include better versions of a model when they are available in the model doc pages
See original GitHub issue@NielsRogge provided a great suggestion.
We could add a banner on top of Swin’s docs (and other models where this is applicable), to indicate we have a better model now, SwinV2. The same could be done for DETR, as Conditional DETR and Deformable DETR greatly improve the convergence and AP metrics.
We can start with the following:
- Swin
- DETR
And then expand to the other models. Or else, we can start with five such models (feel free to suggest more). When reviewing model PRs to transformers
, we would just need to be mindful about this a bit so that we can suggest it accordingly to the contributors.
Cc: @osanseviero @nateraw
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Apply a model to a document library in Microsoft Syntex
You can apply a model to different places, including the model home page or from the list of available models. To apply your...
Read more >Pages User Guide for Mac
All documents begin with a template—a model you can use as a starting point. ... (To see which version of Pages you have,...
Read more >About documentation
The documentation for your project includes: Information about your project: including model code, a DAG of your project, any tests you've added ...
Read more >Register and Deploy Models with Model Registry
Deploy models to production. Automate model deployment with CI/CD. Catalog models by creating model package groups that contain different versions of a model....
Read more >Change a document's page setup: pages or pageless
Pages : Set up your Google Doc with pages and page breaks. In this setting, you can add elements like headers and footers,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am very wary about this. If you start telling on the page of a model that have been developed by Org 1 that there is a better model developed by Org 2, they will get mad and we will then have unnecessary conflicts to handle.
For the same reason we stay away from benchmarks between frameworks/hardware, I would stay away from this.
Sure, why not 😃 for those scenarios I think it’s ok to open small PRs updating the corresponding docstrings