fix elastic error

[pmeier]

I accidentally removed an error in #7977 (thanks @vfdev-5 for spotting).

Before:

vision/torchvision/transforms/v2/functional/_geometry.py

Lines 1784 to 1794 in 84db2ac

	def elastic(
	inpt: datapoints._InputTypeJIT,
	displacement: torch.Tensor,
	interpolation: Union[InterpolationMode, int] = InterpolationMode.BILINEAR,
	fill: datapoints._FillTypeJIT = None,
	) -> datapoints._InputTypeJIT:
	if not torch.jit.is_scripting():
	_log_api_usage_once(elastic)
	if not isinstance(displacement, torch.Tensor):
	raise TypeError("Argument displacement should be a Tensor")

After:

vision/torchvision/transforms/v2/functional/_geometry.py

Lines 1732 to 1744 in c1592f9

	def elastic(
	inpt: torch.Tensor,
	displacement: torch.Tensor,
	interpolation: Union[InterpolationMode, int] = InterpolationMode.BILINEAR,
	fill: _FillTypeJIT = None,
	) -> torch.Tensor:
	if torch.jit.is_scripting():
	return elastic_image_tensor(inpt, displacement=displacement, interpolation=interpolation, fill=fill)
	_log_api_usage_once(elastic)
	kernel = _get_kernel(elastic, type(inpt))
	return kernel(inpt, displacement=displacement, interpolation=interpolation, fill=fill)

We could put the error back into the functional, but I feel we should raise proper error messages on the kernels as well. Although this means a little code duplication for us, as a user I would be surprised of the functional raises a proper error, but the kernel doesn't. In this case, the duplication is minimal, since all kernels beside the bounding boxes one, call the image kernel.

I've also added tests for elastic.

cc @vfdev-5

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/7838

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 32 New Failures

As of commit 4f44831 with merge base e0e6f7e ():

NEW FAILURES - The following jobs have failed:

• build / linux-job (gh)
• c-source / linux-job (gh)
• linux (linux.12xlarge, cpu) / linux-job (gh)
• linux (linux.g5.4xlarge.nvidia.gpu, cuda, 11.8) / linux-job (gh)
• macos (macos-12) / macos-job (gh)
• macos (macos-m1-12) / macos-job (gh)
• onnx / linux-job (gh)
• python-source-and-configs / linux-job (gh)
• python-types / linux-job (gh)
• unittests-extended / linux-job (gh)
• unittests-linux (3.10, linux.12xlarge, cpu) / linux-job (gh)
• unittests-linux (3.11, linux.12xlarge, cpu) / linux-job (gh)
• unittests-linux (3.8, linux.12xlarge, cpu) / linux-job (gh)
• unittests-linux (3.8, linux.g5.4xlarge.nvidia.gpu, cuda, 11.8) / linux-job (gh)
• unittests-linux (3.9, linux.12xlarge, cpu) / linux-job (gh)
• unittests-macos (3.10, macos-12) / macos-job (gh)
• unittests-macos (3.11, macos-12) / macos-job (gh)
• unittests-macos (3.8, macos-12) / macos-job (gh)
• unittests-macos (3.8, macos-m1-12) / macos-job (gh)
• unittests-macos (3.9, macos-12) / macos-job (gh)
• unittests-prototype (3.10, linux.12xlarge, cpu) / linux-job (gh)
• unittests-prototype (3.11, linux.12xlarge, cpu) / linux-job (gh)
• unittests-prototype (3.8, linux.12xlarge, cpu) / linux-job (gh)
• unittests-prototype (3.8, linux.g5.4xlarge.nvidia.gpu, cuda, 11.8) / linux-job (gh)
• unittests-prototype (3.9, linux.12xlarge, cpu) / linux-job (gh)
• unittests-windows (3.10, windows.4xlarge, cpu) / windows-job (gh)
• unittests-windows (3.11, windows.4xlarge, cpu) / windows-job (gh)
• unittests-windows (3.8, windows.4xlarge, cpu) / windows-job (gh)
• unittests-windows (3.8, windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh)
• unittests-windows (3.9, windows.4xlarge, cpu) / windows-job (gh)
• windows (windows.4xlarge, cpu) / windows-job (gh)
• windows (windows.g5.4xlarge.nvidia.gpu, cuda, 11.8) / windows-job (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[vfdev-5]

Thanks Philip, lgtm!