Sometimes I want to do matrix manipulations that involve using a matrix whose columns are various eigenvectors from the EVP solver. A good example can be found here in calc_ps(), specifically lines 399, 402, and 414. If I just do EP.solver.eigenvectors, then those eigenvectors don't necessarily match up with the eigenvalues in EP.evalues, which are the eigenvalues of EP.hires_solver (assuming reject=True). This can cause unintended behavior.
It would be great if I could just get EP.evectors and have that be the eigenvectors that correspond to EP.evalues whether reject=True or reject=False. And in case it's True, I'm thinking it would be great for EP.evectors to be the higher-resolution eigenvectors, but maybe other users have a reason why they'd also want access to the lower-resolution eigenvectors.
Sometimes I want to do matrix manipulations that involve using a matrix whose columns are various eigenvectors from the EVP solver. A good example can be found here in
calc_ps(), specifically lines 399, 402, and 414. If I just doEP.solver.eigenvectors, then those eigenvectors don't necessarily match up with the eigenvalues inEP.evalues, which are the eigenvalues ofEP.hires_solver(assumingreject=True). This can cause unintended behavior.It would be great if I could just get
EP.evectorsand have that be the eigenvectors that correspond toEP.evalueswhetherreject=Trueorreject=False. And in case it's True, I'm thinking it would be great forEP.evectorsto be the higher-resolution eigenvectors, but maybe other users have a reason why they'd also want access to the lower-resolution eigenvectors.