You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior:
Kaolin modules unrelated to physics should not trigger Warp initialization, allowing for faster import times.
Proposed Solution:
Defer Warp initialization until it is explicitly needed, such as during the first call to a physics function. This ensures that importing Kaolin functions unrelated to Warp remains efficient, as was the case in versions prior to 0.16.
Additional Notes:
This change will improve the usability of Kaolin for non-physics applications, maintaining consistency with the behavior of earlier versions.
The text was updated successfully, but these errors were encountered:
Description:
Starting with Kaolin 0.16, importing Kaolin functions unrelated to the physics module triggers Warp initialization, resulting in increased import time.
Steps to Reproduce:
Cause:
The root cause lies in the
kaolin/__init__.py
file, wherefrom . import physics
is invoked. This cascades into:from . import simplicits
from .losses_warp import *
The final step initializes Warp:
kaolin/kaolin/physics/simplicits/losses_warp.py
Line 27 in ba9824e
Expected Behavior:
Kaolin modules unrelated to physics should not trigger Warp initialization, allowing for faster import times.
Proposed Solution:
Defer Warp initialization until it is explicitly needed, such as during the first call to a physics function. This ensures that importing Kaolin functions unrelated to Warp remains efficient, as was the case in versions prior to 0.16.
Additional Notes:
This change will improve the usability of Kaolin for non-physics applications, maintaining consistency with the behavior of earlier versions.
The text was updated successfully, but these errors were encountered: