torch==1.13.1 link

[TotalDay]

Describe the issue

Where is the link of patched torch==1.13.1 for XPU ?

[TotalDay]

python -m pip install torch==1.13.1+xpu -f https://developer.intel.com/ipex-whl-stable-xpu

where is it?

[gujinghui]

torch-1.13.0a0%2Bgit6c9b55e-cp37-cp37m-linux_x86_64.whl
torch-1.13.0a0%2Bgit6c9b55e-cp38-cp38-linux_x86_64.whl
torch-1.13.0a0%2Bgit6c9b55e-cp39-cp39-linux_x86_64.whl
torch-1.13.0a0%2Bgit6c9b55e-cp310-cp310-linux_x86_64.whl

[mikekasprzak]

That's not 1.13.1+xpu.

The xpu master branch README says PyTorch was updated to 1.13.1 (see below), but as @TotalDay mentioned there's no actual file matching that name.

GPU version

You can install Intel® Extension for PyTorch* for GPU via command below.

python -m pip install torch==1.13.1+xpu -f https://developer.intel.com/ipex-whl-stable-xpu
python -m pip install intel_extension_for_pytorch==1.13.120+xpu -f https://developer.intel.com/ipex-whl-stable-xpu

Note: The patched PyTorch 1.13.1 is required to work with Intel® Extension for PyTorch* on Intel® graphics card for now.

https://developer.intel.com/ipex-whl-stable-xpu

I nearly opened a similar issue myself since Intel Extensions for PyTorch 1.13.120+xpu was also missing as well, but that appears to have been fixed.

That said, no PyTorch 1.13.1-xpu builds exist in that folder.

[gujinghui]

Thanks for comments.

It's a bug in README of our master branch.
We updated the release branch, but missed the master branch.
https://github.com/intel/intel-extension-for-pytorch/tree/release/xpu/1.13.120

Meta uplifted the release package version to 1.13.1, but not change the version in code.
Below packages are totally aligned with PyTorch 1.13.1 code base.
Please try it with IPEX 1.13.120 release.

torch-1.13.0a0%2Bgit6c9b55e-cp37-cp37m-linux_x86_64.whl
torch-1.13.0a0%2Bgit6c9b55e-cp38-cp38-linux_x86_64.whl
torch-1.13.0a0%2Bgit6c9b55e-cp39-cp39-linux_x86_64.whl
torch-1.13.0a0%2Bgit6c9b55e-cp310-cp310-linux_x86_64.whl

[tye1]

Thanks for capturing this. We just updated our xpu-master branch and resolved this document issue.