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
Hello! Thank you for the great kernel package. I am attempting to benchmark MACE with cuE v0.2 (there are some breaking changes related to the constraint that all inputs must have 2 dimensions, but I patched them so that MACE runs as expected without torch.compile).
With torch.compile and cuE involved (with force prediction enabled), the backward pass does not appear to run (silently, without raising an error). The predicted force tensor does not appear to change from zero, and profiling with torch.profile reveals that only kernels expected in the forward pass are dispatched.
Perhaps this is a question for the MACE repository, but I am posting it here since the backward pass runs fine if any of the following conditions are satisfied:
a) The model uses cuE, but is NOT compiled; then the predicted force tensor fills, and I see all kernels in the profiler
b) The model uses the default e3nn backend
which leads me to believe that cuE might possibly have an issue. Code is below, and I can provide the data file if needed.
Hello! Thank you for the great kernel package. I am attempting to benchmark MACE with cuE v0.2 (there are some breaking changes related to the constraint that all inputs must have 2 dimensions, but I patched them so that MACE runs as expected without torch.compile).
With torch.compile and cuE involved (with force prediction enabled), the backward pass does not appear to run (silently, without raising an error). The predicted force tensor does not appear to change from zero, and profiling with
torch.profile
reveals that only kernels expected in the forward pass are dispatched.Perhaps this is a question for the MACE repository, but I am posting it here since the backward pass runs fine if any of the following conditions are satisfied:
a) The model uses cuE, but is NOT compiled; then the predicted force tensor fills, and I see all kernels in the profiler
b) The model uses the default e3nn backend
which leads me to believe that cuE might possibly have an issue. Code is below, and I can provide the data file if needed.
@ilyes319 for visibility.
The text was updated successfully, but these errors were encountered: