-
Notifications
You must be signed in to change notification settings - Fork 60
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
cleaning up measurestats with mesh iterator #208
Conversation
nickhand
commented
Jul 10, 2016
- this introduces a mesh iterator that can apply a function slab-by-slab, which should help the readability of the code
@rainwoodman -- take a look at the new project_to_basis(). I think this does a pretty good job hiding the details but leaving the general algorithm |
Indeed. I am slightly in more favor of
this way we can avoid defining a temporary object and a temporary function. Yu |
I do feels like the singular can go into the worker/iterator object too, by passing |
that seems reasonable to me -- I think I could go either way. The temporary function is a bit ugly, but I did manage to hide the for loop though :) |
Yes. but the cost is two temporary names. In addition,I have a rather strong opinion against 'worker's... I guess it is because the name is overly generic. |
this was confusing, as shown by the fact that the old keyword actually was supposed to mean the opposite of hermitian symmetric
… values I have now confirmed we obtain the same power results, independent of the choice of `axis` for the SlabIterator
Okay, I've got a new version of the SlabIterator running -- I've confirmed it works with generic axis values now. I've also changed the syntax regarding the "singular plane" in hopes of making it a bit more transparent. Let me know what you think. I just went with a simple |
It looks pretty cool indeed. On Sun, Jul 10, 2016 at 3:31 PM, Nick Hand notifications@github.com wrote:
|