Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

phase_N <-> kaN "redundancy" #73

Open
kostrzewa opened this issue Feb 17, 2012 · 2 comments
Open

phase_N <-> kaN "redundancy" #73

kostrzewa opened this issue Feb 17, 2012 · 2 comments

Comments

@kostrzewa
Copy link
Member

There is a certain redundancy from boundary.[c,h] in D_psi.c now that c99 complex is being integrated, but I don't know how much of a performance impact, if any, it would make to simply replace instances of phase_N by -kaN (where N = {0,1,2,3} ) Any ideas?

@deuzeman
Copy link

I doubt there is any noticeable performance impact of removing one of the two variables and it certainly makes things more readable, so this has my vote.

@urbach
Copy link
Contributor

urbach commented Mar 19, 2012

The main reason for having both is a sign. In Hopping_Matrix there is a relative sign missing, and to match the definitions in between D_psi and Hopping_Matrix, I introduced the negative phase factors. This one could of probably also fix in the code of D_psi now easily with the new complex implementation, couldn't one? (are the macros a problem there?)

Otherwise, I don't expect performance issues there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants