You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered a case where the Wannier centers computed by Wannier90 and wannier90-utils are inconsistent. Unfortunately I'm not allowed to share the input files[*], but the root cause is that in
the np.imag(np.log(mii[:, i])) is well-defined only up to multiples of 2π.
This is the same "branch cut" problem that is worked around in Wannier90 by setting the guiding_centres=.true. option.
I'm not sure what the best approach would be here - do you think it would make sense to add a similar option that selects the closest Wannier center to a given "reference"?
[*] I'll try to come up with some other example that reproduces this behavior..
The text was updated successfully, but these errors were encountered:
Hello @greschd. Thanks for reporting this issue. Yes, an option to specify "reference" centers, in order to fix the phases of the logarithm, seems like a reasonable approach. Been looking through the wann_phases routine in wannier90, but cannot quite understand how the phases are determined from the guiding centers. Presumably, for a set of centers, it is straightforward to compute the appropriate phases; and that this may differ from guiding_centres during the spread minimization.
I've encountered a case where the Wannier centers computed by Wannier90 and
wannier90-utils
are inconsistent. Unfortunately I'm not allowed to share the input files[*], but the root cause is that inwannier90-utils/src/w90utils/sprd.py
Line 19 in c22ae92
the
np.imag(np.log(mii[:, i]))
is well-defined only up to multiples of 2π.This is the same "branch cut" problem that is worked around in Wannier90 by setting the
guiding_centres=.true.
option.I'm not sure what the best approach would be here - do you think it would make sense to add a similar option that selects the closest Wannier center to a given "reference"?
[*] I'll try to come up with some other example that reproduces this behavior..
The text was updated successfully, but these errors were encountered: