Add torchvision.transforms.Resize interpolation and antialias.

[hiyuh]

torchvision.transforms.Resize forced nearest interpolation and no antialias, but shouln't.
Based on my understanding, original torchvision.transforms.Resize calls like;

• torchvision.transforms.Resize
  • torchvision.transforms.functional.resize
    • torchvision.transforms._functional_pil.resize
      • PIL.Image.Image.resize
    • torchvision.transforms._functional_tensor.resize
      • torch.nn.functional.interpolate

Note, this PR still keeps nearest interpolation and no antialias by default for torchvision.transforms.Resize to maximize compatibility for existing code using TorchSharp and results in incompatible to original torchvision.transforms.Resize default, however, it would be up to the upstream decision.
See also;

• https://pytorch.org/vision/main/generated/torchvision.transforms.Resize.html
• https://pytorch.org/vision/main/generated/torchvision.transforms.functional.resize.html
• https://pytorch.org/docs/stable/generated/torch.nn.functional.interpolate.html

[hiyuh]

@dotnet-policy-service agree company="HACARUS"

[alinpahontu2912]

Hey @hiyuh, can you rebase and update releasenotes?

[hiyuh]

@alinpahontu2912
done, please go ahead.

[ozanMSFT]

I added a few more comments.

@hiyuh I have some concerns regarding the compatibility between the current TorchSharp's TorchVision and your changes. Could you specify in which version of TorchVision the antialias parameter was introduced, and whether it is compatible with the current TorchSharp's native dependencies?

[ozanMSFT]

@hiyuh ; if you can give us permission for your branch as following setting, we can also resolve some RELEASENOTES conflicts on behalf of you:

NOTE: We're planning a solution for the releasenotes conflicts.

[hiyuh]

@ozanMSFT

• regarding your review comments on several source codes, let me try to improve, so wait a moment.
• about allowing maintaner's change on pulll request, from my best knowledge, it's unavailble option if the forked branch is under organization.
  • next time, i can work under my account (not my organization) if you guys preferred.

[hiyuh]

@ozanMSFT

Could you specify in which version of TorchVision the antialias parameter was introduced, and whether it is compatible with the current TorchSharp's native dependencies?

• Python torchvision antialias has been mentioned from v0.10, and not in v0.9.
  • https://pytorch.org/vision/0.10/transforms.html?highlight=resize#torchvision.transforms.Resize
  • https://pytorch.org/vision/0.9/transforms.html?highlight=resize#torchvision.transforms.Resize
• according output from following command under pytorch/pytorch,
  i assume antialias option has been available from v1.11.0.

  git tag --contains $(git log -S "options.antialias" --reverse --pretty=format:"%H" | head -n 1) | grep -e '^v' | head -n 1

  • see also pytorch/pytorch@ce9a2f8

[hiyuh]

@ozanMSFT

• rebased onto main, to resolve RELEASENOTES.md conflict as usual.

[ozanMSFT]

@hiyuh , thanks for addressing the all comments. Great contribution!

Currently, I'm observing some build errors but I'm not sure if it is relevant to your PR or there is another error. I'm investigating the issue.

[ozanMSFT]

LGTM

Note for future: We can improve the tests if they fail due to float precision but for now they are working fine.