Add LPDO type #67
Merged
Add LPDO type #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This introduces the LPDO type. Currently it has pretty minimal functionality (see
lpdo.jlfor defined functions), but you can use the MPS/MPO underlying the LPDOLwithL.X.The main useful functions are
ket(L, j)andbra(L, j), which return the bra and ket of thejth site. That means the density matrix on sitejis basicallyket(L, j) * bra(L, j). You can see how it is used in thelognormalize!function, but note that function could have simply been transcribed by usingM = L.Xand nothing would have needed to be changed.The next goal would be to start using the LPDO type anywhere that is appropriate in the code, and add some new functionality where useful.