Fixed the offset_nscf for the case of smooth interpolation grid #230
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.
PR that fixes the problem of using smooth_interpolation together with offset_nscf. The later flag allows the shift of the k-grid so that the grid lies in the [0,1) interval. In principle, offset_nscf allows arbitrary shifts, but in practice, it is only used to shift the grid to non-negative values that some codes (e.g., EPW) require. At some point, one needs to also consider checking if this is how users use this flag. Using the definition of MP grid, one could see that the shift for the grid Nk is:
offset_nscf =$0.5(1-1/Nk)$
The problem arises in the final stage when nscf calculation is performed for the smooth DFT grid. The workflow uses the offset for the smaller grid, whereas you need to use the following ($Nk_{smth}$ = Nk * smth_int_factor):
offset_nscf_smth =$0.5(1-1/Nk_{smth})$
The fix transforms the initial offset to the smooth one using the abovementioned equations.