-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update is_mlu_available #1537
Update is_mlu_available #1537
Conversation
to adapt torch_mlu main, the torch.is_mlu_available method is removed
@zhouzaida Can you help review this pr? |
Please sign the CLA first |
@HAOCHENYE I have signed the CLA |
mmengine/device/utils.py
Outdated
@@ -16,6 +16,12 @@ | |||
except Exception: | |||
IS_NPU_AVAILABLE = False | |||
|
|||
try: | |||
import torch_mlu # noqa: F401 | |||
IS_MLU_AVAILABLE = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change to
IS_MLU_AVAILABLE = torch.mlu.is_available()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
to adapt torch_mlu main, the torch.is_mlu_available method is removed
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers. By the way, if you're not familiar with how to use pre-commit to fix lint issues or add unit tests, please refer to Contributing to OpenMMLab.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist