[docs] RandomResizeCrop signature quirks
Open
Nobody has claimed this yet.
module: documentation
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
- Why do we need to have so much precision:
1.333333333333?1.3would suffice and be more readable <InterpolationMode.BILINEAR: 'bilinear'>. It's not clear from this if the enum should be preferred or the constant (and it's also not copy-pastable in the code). It's also not clear which type is used for InterpolationMode, especially given that for a long time only PIL.Image.InterpolationMode was supported, hence even new codebases are using the legacy PIL types: https://github.com/facebookresearch/dino/blob/58aabc0/main_dino.py#L420- Why does
InterpolationModelive in torchvision.transforms.functional whereas the type using it lives in torchvision.transforms? This enum is basic enough to deserve placement in torchvision.transforms directly IMHO. - The doc text mentions
torchvision.transforms.InterpolationMode, but it's incorrect since the type currently lives in transforms.functional: https://pytorch.org/vision/master/transforms.html?highlight=randomresizedcrop#torchvision.transforms.functional.InterpolationMode

Contributor guide
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.
Research direction
Start with the RandomResizeCrop and InterpolationMode entries in the linked torchvision transforms documentation, then inspect the current references to torchvision.transforms.functional and torchvision.transforms. Compare the rendered signature and enum representation with the issue's four concerns. Done means the precision, preferred enum usage, type information, enum location, and documentation link are resolved consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100