Cut sparse state vector #1018
Merged
Cut sparse state vector #1018
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.
Per discussion in issue #1017, our official recommendation for sparse state vector simulation is simply to use quantum binary decision diagram (QBDD) techniques, with
QBdtsimulation layer. Both are CPU-only methods, the original non-QBDD sparse simulation algorithm is bugged, and it offers no obvious advantage that QBDD does not cover. (If any amplitude is 0-valued, it will be removed from the QBDD tree anyway, hence QBDD is expected to cover the full domain of applicability for sparse state vector, without any obvious drawback, exception, or limitation.)