Specifying the output size in transforms.GaussianBlur
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
📚 The doc issue
The transforms.GaussianBlur constructor takes kernel_size as a parameter. However, it isn't specified whether the convolution will use padding to keep the output image in the same dimension as the input. I think it should be mentioned. Maintaining the original input size is crucial in many cases, like object detection or segmentation, where the GT refers to certain pixels.
Suggest a potential alternative/fix
No response
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 transforms.GaussianBlur API documentation and its kernel_size description; verify the documented output dimensions against the transform behavior. Done means the documentation explicitly states whether padding preserves the input dimensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100