Avoid adding adding exact zeros in TaylorCluster implementation
#229
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
|
lkdvos
approved these changes
Jan 20, 2025
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.
The addition of
SparseBlockTensorMapslices in theTaylorClusterimplementation lead to the explicit instantiation and subsequent purging of explicit zero blocks due to thegetindex-setindex!interplay in expressions likeslice[linds[s_c], 1, 1, :] += slice[c_lin, 1, 1, :]. This PR circumvents this by explicitly restricting to the nonzero keys of the right hand side. It's not the cleanest solution, but it gives a big performance increase for Hamiltonians with a lot of channels.