[WIP] Fix issues with pytorch 1.13 on MacOs

[lsickert]

Description

This PR fixes issues that exist in PyTorch v1.13 on MacOS related to the following issues in PyTorch: 88049 88826

The current workaround is it to revert to PyTorch 1.12.1 and disable the use of the mps device on MacOS, but the issues should be fully resolved in PyTorch 1.13.1 (Release Tracker) which is scheduled to be GA by Dec 15th.

Related Issue

150

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[lsickert]

@gsarti I updated Pytorch 1.13.1 and the installation issues on macOS are now fully resolved. However, not all of the issues with MPS are fixed by 1.13.1 and some of the tests are still failing. So I left the workaround of hardcoding the device to CPU on MPS devices in the code and added a comment about this. I would suggest merging this branch and closing the associated bug ticket and I will open a new issue to track the remaining issues with MPS as I think there is not much we can currently do until newer PyTorch versions might fix the remaining issues.

[gsarti]

Checked the changes, could you justify why setting python3 instead of 3.8 in the pre-commit config? Apart from that, LGTM!

[gsarti]

Good for merging as temporary MPS fix

[lsickert]

Checked the changes, could you justify why setting python3 instead of 3.8 in the pre-commit config? Apart from that, LGTM!

Sorry, that was just meant temporarily to make things more comfortable during development as I am usually not on 3.8 anymore and sometimes forget to switch the version between different projects. I can revert it back to 3.8, but since the code will be checked against the different versions on GitHub anyways maybe we could just leave it like that?