-
-
Notifications
You must be signed in to change notification settings - Fork 0
Take the cutoffs from the input when the pseudo family has none #127
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
Merged
Merged
Changes from 11 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
8c05443
Take the cutoffs from the input when the family has none
elinsc-bot b8939c2
Merge remote-tracking branch 'pr/main' into k2-pseudo-cutoffs
elinsc-bot b1ab107
Merge remote-tracking branch 'pr/main' into k2-pseudo-cutoffs
elinsc-bot 419d6f0
Cover the pseudo pinning on the wannierize and dscf routes
elinsc-bot e2660df
Reject one pw cutoff stated without the other
elinsc-bot 1a87738
Derive the density cutoff from the wavefunction one
elinsc-bot 354cd90
Warn on an off-ratio density cutoff from the kcp block
elinsc-bot ecc12c9
Reject a cutoff of zero or less at parse
elinsc-bot cd50eb7
Reject an input stating two different cutoffs
elinsc-bot 555b7b5
Type the cutoff-shape parameter mypy rejected
elinsc-bot 04dc886
Cut the off-ratio warning to the rule it states
elinsc-bot 5eab827
Move the aiida-quantumespresso pin past the override warning
elinsc-bot 6ab63af
Clone aiida-quantumespresso from the patched branch
elinsc-bot 93444cb
Stop pinning the pseudos of a cutoff-less family
elinsc-bot a3035ef
Say what dropping the DSCF cutoff check does
elinsc-bot 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
Some comments aren't visible on the classic Files Changed page.
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
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.
Why do we need to explicitly provide pseudos in this case? Why doesn't the
pseudo_familywork any more?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.
The family still supplies the pseudos —
get_pseudos_from_family(pseudo_family, structure)is where they come from either way. What changes is who resolves it, and it is a workaround for upstream rather than something koopmans wants.Handed a
pseudo_familyname,get_builder_from_protocollooks up the family's recommended cutoffs before it gets anywhere near the pseudos, and raises when the family has no stringency defined:There is no way to tell it "use this family, take the cutoffs from me". But it has a second branch: given explicit
pseudos, it skips the cutoff lookup entirely. So resolving the family ourselves one step early takes that branch and dodges a lookup whose result we were going to overwrite anyway.Two things worth knowing:
pseudo_family_has_cutoffsreturns early otherwise), so the normal path is untouched.Found unrecognised key in overrides: scf.pw.pseudos.Sion every affected route, about the key its own builder reads. Noise, but a user sees it — flagged in the PR body as worth reporting upstream.Graded code-read, not reproduced: I have read upstream's two branches, and the tests pin that the pseudos arrive and the cutoffs are the input's. I have not separately reproduced the claim that the explicit-
pseudosbranch is why the lookup is skipped.