This issue was raised by Francesco Belli
When the minimization is performed without symmetries, the dynamical matrix will break the symmetries present in the beginning.
Then the q star division and the number of irreducible q points is broken. However, now, the code ignores this issue and continues to treat and save the dynamical matrices with the wrong star.
Within the python code, it is trivial to reassemble the dynamical matrix into the correct q star, by just executing the command dyn.AdjustQStar(). However, when should this be called by the code? Before the final dynamical matrix is written? Or after each minimization step?
@ionerrea
@rafbianco
This issue was raised by Francesco Belli
When the minimization is performed without symmetries, the dynamical matrix will break the symmetries present in the beginning.
Then the q star division and the number of irreducible q points is broken. However, now, the code ignores this issue and continues to treat and save the dynamical matrices with the wrong star.
Within the python code, it is trivial to reassemble the dynamical matrix into the correct q star, by just executing the command dyn.AdjustQStar(). However, when should this be called by the code? Before the final dynamical matrix is written? Or after each minimization step?
@ionerrea
@rafbianco