embedding layer in nequip #360
-
Dear developers, P.S. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @mesonepigreco , Thanks for your interest in our code!
Exactly. At a code level, https://github.com/mir-group/nequip-example-extension might be helpful in understanding these things as well.
Yes, in general they should. However this is a very early part of the network, and these embeddings can be processed further quite a bit throughout the network, so one can't assume that, for example, distances between early embeddings mean something definitive about the difference between later features or final predictions. We have done some work on using the final features (rather than these features at the very beginning) for UQ: https://pubs.aip.org/aip/jcp/article/158/16/164111/2886901. |
Beta Was this translation helpful? Give feedback.
Hi @mesonepigreco ,
Thanks for your interest in our code!
Exactly. At a code level,
nequip
has modules that make up the pieces of the model, and model builders, which put them together. You can see the module that does the one hot embedding as the node features here:https://github.com/mir-group/nequip/blob/main/nequip/nn/embedding/_one_hot.py#L12. And the model builder for the NequIP model that uses that module here:
https://github.com/mir-group/nequip/blob/main/nequip/model/_eng.py#L103. You can see later that is followed by an
At…