Conversation
This branch has not been deployed
This file contains hidden or 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.
Hi all, this is a follow-up to #212 that updates
PauliPropagation.jltov0.9.0. The following timings are on the same AMD Ryzen AI 7 350 CPU, still single-threaded.One notable change is that the unexported
Performancemodule is now almost fully ported intoVectorPauliSum's default propagation. If you ever do multi-threaded benchmarks, I suggest you useMultiPauliSum{VectorPauliSum}even though the vector-backend could thread.TFIM (
STEPS=10 DT=0.1 J=1 h=1 ATOL=1e-6), time in seconds:Heisenberg (same parameters), time in seconds: