-
Notifications
You must be signed in to change notification settings - Fork 31
compatibility follow up with metatensor 0.9.0rc6 + metatomic 0.1.12rc2 + featomic 0.6.6 #1128
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
Closed
sofiia-chorna
wants to merge
7
commits into
metatensor:main
from
sofiia-chorna:fix-use-targetinfo-quantity
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
2da11ce
Use targetinfo quantity as modeloutput quantity was deprecated
sofiia-chorna 903841e
is_auxiliary_output - also match singular "feature"
sofiia-chorna a66b3f5
gap: recreate tensorblocks
sofiia-chorna f0d92ea
copy blocks
sofiia-chorna 3098dfd
update tests for stricter validation
sofiia-chorna ecb59c2
scaler: copy block before second tensormap
sofiia-chorna 74c798f
revert regex for backward compat with current metatomic
sofiia-chorna File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Is this intended to match on
energy,energy_ensemble, andenergy_uncertaintyoutputs, or onlyenergy`?in the second case, this could be done better using
i.e. checking the output name, handling both
energyandenergy/pbe0. This way we could also remove the quantity field from metatrainThere 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.
yes but i am wondering that the custom energy names will be missed in this case, like
mtt::U0There 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.
There really should not be a point to use something like this nowadays =) This kind of naming was used before we got variants on the models outputs.
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.
Hmmmmm if we remove quantity, old
options.yamlwill sometimes not work as Sofiia says for example when you pass a target calledmtt::U0(which is what the tutorials do).Although I agree that the default behavior is a bit strange, everything by default is
quantity: "energy"(even spherical targets), it is set here:metatrain/src/metatrain/utils/omegaconf.py
Lines 118 to 130 in cf1b015
which makes
quantity: "energy"by itself quite useless, and the code needs to perform further checks to know that it is dealing with an energy, like here:metatrain/src/metatrain/utils/data/dataset.py
Lines 793 to 798 in cf1b015
So yeah I agree this should go away but I'm a bit scared of touching it tbh