-
Notifications
You must be signed in to change notification settings - Fork 7.1k
Revamping our semantic segmentation and object detection models docs #5833 #5897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can work on |
Happy to take care of |
I can work on FCOS |
I can take SSD300 |
I will take LRASPP |
I'll take FCN & SSDLite to finish this then :) |
Thanks a lot everyone! |
@NicolasHug Hi I am doing with SSD. Could you wail till today:) |
Oops sorry @puhuk I missed your comment above! Please take your time, no rush :) |
* docs: Added SSD300 to the new doc To resolve #5897 * Minor fixes * ufmt Co-authored-by: Nicolas Hug <[email protected]>
Summary: * docs: Added SSD300 to the new doc To resolve #5897 * Minor fixes * ufmt Reviewed By: YosuaMichael Differential Revision: D36204387 fbshipit-source-id: 57ba33406aa52e62d2dcca3fd73ca96f5440f717 Co-authored-by: Nicolas Hug <[email protected]>
Thank you very much for your help everyone !! |
Sister issue (for classification models): #5833
We're re-writing our models docs to make them clearer, simpler, and to properly document the upcoming multi-weight API. This issue is about adding docs for the detection and segmentation models.
Our latest new docs are currently here (this link is likely outdated by the time you look at it, but it doesn't matter; the skeleton is there). We created a separate section that will eventually be merged into the main one. We have documented a few models, but most of them are still missing. The list of models that still need docs is listed below. If you'd like to participate, please comment below with a message saying "I'm working on XYZ" where XYZ is a model, so that others don't pick the same as you do. To keep things simple, please submit one PR per model, but feel free to contribute more than one model.
How to write docs for a model
Note: below are detailed instructions. This makes it look more complicated than it actually is. Don't be scared!
A great place to start is to look a the changes in this PR that documents SqueezeNet. You'll need to do exactly the same for your model:
.rst
file in https://github.com/pytorch/vision/tree/main/docs/source/models. The file should look like this, with a link to the original paper, and a list of the corresponding model builders. It should also mention the base model class and link to the.py
file where it is defined..rst
suffix). Please keep the list alphabetically sorted**kwargs
parameter. Usually these are passed to the base class, but if they don't do anything, just document them as**kwargs: unsued.
To build the docs locally, please look at our contributing guide. You won't need to worry about the gallery example, so always use
make html-noplot
instead ofmake html
to save time.Please don't hesitate to ping us if you need any help / guidance or if you have any question!
Semantic segmentation:
Object Detection:
The text was updated successfully, but these errors were encountered: