-
Notifications
You must be signed in to change notification settings - Fork 18
SevenNetModel
does not work with torch.float64
#92
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
Comments
Hi 👋 I am the main developer 7net. We don't currently support double precision. Even if it works somehow, I can't say that the values are reliable. By the way, this project is really great and exactly what I wanted recently. I want to help, especially the sevennet part, if any help is needed. Thanks for releasing this great work as an open source. |
@YutackPark Thank you for your comments. What’s the best way to contact you? |
Here's my email: [email protected] As I'm a PhD. candidate, I may have to CC my supervisor. For simple code maintenance or features, I can help freely on weekends. Just contact me with github in this case. |
Thanks @YutackPark! I am working on a rewrite of our model testing logic and would love your feedback. I'll tag you when I open the PR. I'll also include a modification to the |
@YutackPark One thing that I did here in the implementation/wrapper of SevenNet was that I used the neighbor list implementation from |
@CompRhys , @orionarcher Other than that, the 7net part looks good to me. By the way, do you know why 7net or GemNet shows less speed-up compared to MACE? |
As far as I understand speed up is mainly a function of how much more efficiently we can use GPU memory due to batching at small batch sizes, at larger batch sizes this is more an open question that we are still exploring/profiling. Hopefully sharing the efficient batching implementations here will make it easier for developers like yourself to help identify the bottlenecks and optimizations that can then be applied to all models. In #112 I think I will revert the neighbor list to the default you used just to be on the safe side, we don't want to accidentally impact the model performance if there are subtle differences. |
It's likely due to the higher order terms used in these architectures. The GemNet used here calculates triplets and 7net has lmax of 3 whereas the MACE work has lmax of 1. |
The SevenNetModel currently fails when
float64
is set as the type.The text was updated successfully, but these errors were encountered: