-
Notifications
You must be signed in to change notification settings - Fork 242
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
Support arbitrary model outputs #556
Conversation
…into ocp2.0_models
@wood-b @mshuaibii @janiceblue Is this PR ready to merge? or is there something still outstanding? |
src/fairchem/core/common/__init__.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these changes relevant to arbitrary model support? I didnt see calculator mentioned elsewhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably was an issue with merge conflicts, as OCPCalculator is in src/fairchem/core/__init__.py
already, will remove
…unami enumeration (#764) * adding new notebook for using fairchem models with NEBs * adding md tutorials * blocking code cells that arent needed or take too long
Part of #520. Provides support for arbitrary model head predictions by leveraging a model's node/edge embeddings.
Specifically:
custom_head
flag in the config controls whether we want the model to create the head or the model architecture was created specifically for that target. IfFalse
, the desired outputs are expected to be hard-coded as part of the model. This is mainly to support existing models energy/force predictions, without changing those underlying models.custom_head=True
, for the model makes the respective prediction depending on whether it isn't an equivariant property (by definingirrep_dim
) or a scalar/list of scalars (shape
).sum[m_st*Y^irrep_dim(r_st)]
).Task tracking:
Baselines