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
# If we wanted swap the sign here, we'd likely have to swap t₀ in the check
# for ray-representations in `check_multtable_vs_ir(::MultTable, ::LGIrrep)`
# to account for this difference. It is not enough just to swap the sign
# - I checked (⇒ 172 failures in test/multtable.jl) - you would have
# to account for the fact that it would be -β⁻¹τ that appears in the
# inverse operation, not just τ. Same applies here, if you want to
# adopt the other convention, it should probably not just be a swap
# to -τ, but to -β⁻¹τ. Probably best to stick with Inui's definition.
The problem, I think, is becoming more urgent, since I suspect there's a disagreement between the current phase convention, i.e. exp(ikr) and the way we calculate the symmetry eigenvalues in MPB (i.e. by acting inversely on the position arguments of functions, such as fields).
It might be worth it to consult some of the recent papers on DFT-centric symmetry eigenvalue calculations to see what they do.
The text was updated successfully, but these errors were encountered:
and they suggest that converting between active (what we want) and passive notions of operators (what the operators here are listed for, in some sense) could be done via:
This problem/uncertainty has existed for a very long time. There's already a good discussion of the issue in
src/types.jl
:Crystalline.jl/src/types.jl
Lines 470 to 495 in 0919b4a
The problem, I think, is becoming more urgent, since I suspect there's a disagreement between the current phase convention, i.e. exp(ikr) and the way we calculate the symmetry eigenvalues in MPB (i.e. by acting inversely on the position arguments of functions, such as fields).
It might be worth it to consult some of the recent papers on DFT-centric symmetry eigenvalue calculations to see what they do.
The text was updated successfully, but these errors were encountered: