-
Notifications
You must be signed in to change notification settings - Fork 8
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
Include WI and WII time evolution MPO constructor in ITensorMPS #101
Comments
Very nice! I think it is better to design it as a separate Julia package built on top of ITensorMPS.jl, analogous to https://github.com/ITensor/ITensorMPOConstruction.jl, and then we could consider moving it into ITensorMPS.jl once it is more developed, tested, etc. We definitely wouldn't incorporate it into ITensorMPS.jl without it having support for QNs. |
Ok, that makes perfect sense! I'll be having a look at the qn conserving construction in https://github.com/ITensor/ITensorMPS.jl/blob/main/src/opsum_to_mpo/opsum_to_mpo_qn.jl and see if I can adjust my code. If I find the time, I can also setup a Julia package. Should I close the issue? |
Note that we are working on a package: https://github.com/ITensor/ITensorPkgSkeleton.jl to make it easier to set up Julia packages living in the ITensor ecosystem. You should be able to call |
Thanks @mtfishman! I'll clean up the code in the near future and test fermionic systems as well. |
Hi,
I've created an implementation of the WI and WII MPO time evolution methods [1] in ITensor, compatible with OpSum Hamiltonians.
The current source code [2] is based on the opsum_to_mpo functionality in without qn conservation.
Is this some functionality that could be included with ITensorMPS.jl?
I'd be willing to spend some time to write an example and relevant unit tests.
Kind regards,
Tim
[1] See, e.g., https://tensornetwork.org/mps/algorithms/timeevo/mpo.html or the paper https://journals.aps.org/prb/abstract/10.1103/PhysRevB.91.165112.
[2] https://gist.github.com/tipfom/89ed4a8acae722466fab2a1b4548e984
The text was updated successfully, but these errors were encountered: