Inconsistent documentation in RandomAffine
See original GitHub issueIn [1]: import torchio as tio
tr = t
In [2]: tr = tio.RandomAffine(scales=1.2)
In [3]: tr.scales
Out[3]: (1.2, 1.2)
But the docs say:
If only one value 𝑑 is provided, \s𝑖∼U(0,𝑑).
@GFabien this was introduced in #244. Do you know what’s going on? Also, note that some wrong latex was introduced in that PR, as you can see in that example: the backslash before s in not necessary (https://torchio.readthedocs.io/transforms/augmentation.html#randomaffine). I’ve fixed it in some other places, but some others might still be around.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
RandomAffine — Torchvision main documentation - PyTorch
Random affine transformation of the image keeping center invariant. If the image is torch Tensor, it is expected to have […, H, W]...
Read more >[FEEDBACK] Transforms V2 API #6753 - pytorch/vision - GitHub
It would be straightforward to document this behavior to users – that ... RandomAffine dispatch to when they operate on a Polygon tensor....
Read more >Transforms — MONAI 1.1.0 Documentation
This approach allows you to use transforms from otherwise incompatible libraries with ... RandAffineGrid for the random affine parameters configurations.
Read more >Source code for torchvision.transforms.transforms
[docs]class Compose(object): """Composes several transforms together. ... raise ValueError("tensor and transformation matrix have incompatible shape.
Read more >Changelog — MMDetection 2.26.0 documentation
v2.25.0 (31/5/2022) · Highlights · Backwards incompatible changes · New Features · Bug Fixes · Improvements · Contributors.
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
This makes sense but I fear this would make things too complicated. It is probably clearer to force the user to pass both min and max values…
I think it’s fine to use these smart ranges. They use them in
torchvision
.