-
Notifications
You must be signed in to change notification settings - Fork 181
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
Handle missing labels #1
Comments
Tomorrow you will get users who have no energy data, only force data. So simply not including missing info in the loss function is quite urgent.
— Gábor
Gabor Csanyi
Professor of Molecular Modelling
Engineering Laboratory
University of Cambridge
…------- Original Message -------
On Tuesday, June 28th, 2022 at 17:58, davkovacs ***@***.***> wrote:
If there are no energy or forces keys defined it should fail by saying missing keys.
Eventually we should implement handling of missing keys as well.
—
Reply to this email directly, [view it on GitHub](#1), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABIANZ5QPY2EY2NUCUD6RWTVRMOKBANCNFSM52CWFQEQ).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
One can now specify |
The models should now be able to handle missing labels on specific config type since #22 and #26. @davkovacs @bernstei How important is to support missing labels within the same config types. If it is important, how is it handled in GAP? It would be a per config weighting? |
What do you mean by missing "labels"? Missing quantities like energy/forces/virial ? |
Yes exactly. |
Per-config weights are supported, and that's how missing data is handled. In GAP I believe that the design matrix construction is not batched, so for every config rows are either added or not depending on what quantities are available. Per-config weights are done in |
Perfect, so I think we need to add that to the readme, and close this issue. |
If there are no energy or forces keys defined it should fail by saying missing keys.
Eventually we should implement handling of missing keys as well.
The text was updated successfully, but these errors were encountered: