Add cuML KNN for graph construction, better handling of non-PBC systems#69
Merged
Add cuML KNN for graph construction, better handling of non-PBC systems#69
Conversation
Contributor
Author
|
On that note, should we perhaps set the default such that the default method would be chosen dynamically: orb-models/orb_models/forcefield/featurization_utilities.py Lines 38 to 54 in 385e091 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ase.Atoms.pbcandase.Atoms.cellrather than justase.Atoms.cell.I've added a note to the README regarding optionally installing cuML.
I've tried adding cuml as an optional dependency in poetry such that users can
pip install orb-models[cuml-cu11]orpip install orb-materials[cuml-cu12]depending on their system. But poetry tries to resolve dependencies between the two optional packagescuml-cu11(for cuda 11) andcuml-cu12(for cuda 12) and fails since they require different sub-dependencies. I don't think there is currently a way to specify mutually-exclusive optional dependencies in pip/poetry right now. So it's probably best to just have it in the README.