-
Notifications
You must be signed in to change notification settings - Fork 14
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
update nscf kpoints distance #446
Merged
Merged
Changes from 4 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
fdca1db
update nscf kpoints distance
AndresOrtegaGuerrero 3eb0817
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 3ee79df
adding logic for nscf kpoints_distance
AndresOrtegaGuerrero fad7de6
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] e695659
update nscf logic
AndresOrtegaGuerrero 56861e9
update nscf logic
AndresOrtegaGuerrero 7689506
update
AndresOrtegaGuerrero a287224
update and pre-commit
AndresOrtegaGuerrero ccf939a
Merge branch 'main' into nscf-override-bugfix
AndresOrtegaGuerrero e033ee6
adding logic to workchain pdos plugin
AndresOrtegaGuerrero d32a7ec
removing lines of smearing and degasuss
AndresOrtegaGuerrero c83326c
updating test_builder
AndresOrtegaGuerrero dd2ca25
pdos setting panel to update nscf_kpoints_distance
AndresOrtegaGuerrero 48271c8
fix
AndresOrtegaGuerrero 4480c4f
adding trailets, generic for plugins
AndresOrtegaGuerrero 23ecf10
fixing setting in pdos plugin
AndresOrtegaGuerrero 85d15b9
updating configuration
AndresOrtegaGuerrero 076fe47
Merge branch 'main' into nscf-override-bugfix
AndresOrtegaGuerrero 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 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
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.
Could you explain the logic of how the
nscf
kpoints_distance
is set? The basic idea seems to be that if the user-specified override forkpoints_distance
is smaller than the corresponding protocol value for thenscf
, the value is set to that of the override. But forfast
there is thiskpoints_distance > 0.15
condition. Why is this? If e.g. the user sets protocol tofast
and overrides thekpoints_distance
to 0.1 thenscf
kpoints should not be adjusted?A couple of other notes:
nscf
, they can be extracted from the actual protocol? I thought we already did this elsewhere in the codebase. That way, the logic isn't broken when the protocol is changed inaiida-quantumespresso
.kpoints_distance
for thenscf
to the same one as thescf
. Isn't the point of thenscf
to do a calculation of the electronic states at fixed charge density for a denser mesh to improve the precision?kpoints_distance
override for thenscf
, and e.g. the linearbands
density as well. This will of course further complicate the interface, and maybe we don't want to expose all these inputs to the user.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.
@mbercx I should modify this logic it should be
if protocol == "fast" and kpoints_distance < 0.5
My idea is that is kpoint_distance is set less to 0.5 (protocol) then nscf should be the same the user is setting. (or less but i dont know at what percentage we should decrease)