Implement Liten, So3krates and EquiformerV2 #39
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.
These are two relatively fast models. LiTEN performs as well as Visnet on Spice2 (force MAE=14meV), while So3krates performs poorly (force MAE=29meV). But its parameter count is small and its speed is fast (600k parameters, speed improvement of about 2-3 times), and So3krates perform well on some small datasets (such as md17 reported in their paper).
You can choose whether to accept these models or not. If not, perhaps you can use an archive branch to store these models for others to compare or use on specific small datasets?
Here are the hyperparameters I use (maybe not the best):
src/mlip/models/radial_basis.pyandsrc/mlip/models/cutoff.pyare collections of all radial bases and cutoffs that may be used.