-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add DumpRegister #1173
Add DumpRegister #1173
Conversation
This change adds an implementation of `DumpRegister` as an intrinsic in the standard library with matching implementation in the evaluator. It works by getting a full state dump and calculating if the state corresponding to the given qubits is separable from the rest, returning an error if it is not. Fixes #1138
Change in memory usage detected by benchmark. |
Change in memory usage detected by benchmark. |
Benchmark for 15d1487Click to view benchmark
|
Change in memory usage detected by benchmark. |
Benchmark for d4516b4Click to view benchmark
|
Change in memory usage detected by benchmark. |
Benchmark for 8230bceClick to view benchmark
|
Should we add some sample code for this? In |
I noticed in #1173 that the formatting for the memory benchmark is broken. This PR fixes that. See below comment for updated formatting.
Change in memory usage detected by benchmark. Memory Report for 89f5ace
|
Benchmark for 89f5aceClick to view benchmark
|
Probably, though likely not until we have actually released a version with |
Change in memory usage detected by benchmark. Memory Report for ef5a9e2
|
Benchmark for ef5a9e2Click to view benchmark
|
This change adds an implementation of
DumpRegister
as an intrinsic in the standard library with matching implementation in the evaluator. It works by getting a full state dump and calculating if the state corresponding to the given qubits is separable from the rest, returning an error if it is not.Fixes #1138