Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
sanity check all pickled non-interacting Hamiltonians in h0 directory #52
sanity check all pickled non-interacting Hamiltonians in h0 directory #52
Changes from 34 commits
cd98d68
99eae10
84bb9cd
279ec77
c17494f
a41d0db
ceb574b
78dd4a1
e164afb
fd120a1
32621f2
812f632
90fcb49
a733919
0fce41d
93f07d0
be2e228
efdb6ca
da733ba
d58bd68
7c426dc
4b04f57
d1f7e9f
e52300b
3ec341e
e794715
80e2bdd
bc383c1
eaac5bf
8b8109f
fcda47f
fcd732d
185cd51
114a836
86d2d2f
0d5b4d6
9ef052d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
assert_allclose
will already print the maximum absolute diff.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true. I'll remove the print statement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need to check events in any particular order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The order does not matter in this for-loop. But when a process is used for real, i.e. applied on a product state, the order matters.
The order is chosen such that$c_i^\dagger c_j \ket{\Psi}$ is implemented as process $\ket{\Psi}$ (with
((i, 'c'), (j, 'a'))
operating on the state'c'
denoting creation and'a'
annihilation). So the right-most "event" is first applied, and finally the left-most "event", just like the math expression.Relevant documentation e.g. https://github.com/JohanSchott/impurityModel/blob/master/impurityModel/ed/finite.py#L1320
https://github.com/JohanSchott/impurityModel/blob/master/impurityModel/ed/finite.py#L1395
And in the same way is the Coulomb interaction process between two electrons:
$c_i^\dagger c_j^\dagger c_k c_l$ implemented as
((i, 'c'), (j, 'c'), (k, 'a'), (l, 'a'))
https://github.com/JohanSchott/impurityModel/blob/master/impurityModel/ed/finite.py#L1322
Because of this I think it might be good to consistently loop over events "from right to left" in this repo.