-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fragments are neither Hermitian nor anti-Hermitian #24
Comments
Hi @max-radin, did the warning appear for a particular value of the |
I was running the LRE script and caught the error messages about fragments for a few associated Hamiltonians. See the attached log. |
@aakunitsa I'm seeing the warning with
|
It sounds like this could be a precision issue. The relevant part of the pyLIQTR code is here: where |
Thank you for investigating @max-radin, @kjm538, and @jp7745! Do we have a sense of whether |
Here's a table showing the effect of the sf threshold on LREs for blue_dimer (the problem instance which the Hamiltonian above belongs to). Decreasing the threshold from 1e-8 and 1e-12 increases the T count a bit (26% in the most extreme case). The increase in number of logical qubits however is negligible. I think the fact that the higher threshold eliminates the warning message but still yields qualitatively similar estimates supports @kjm538's suggestion that this is just some sort of numerical precision issue. I would suggest that we downgrade this issue to low priority. If/when we want to dig more into this, we could look at how far the fragments are from being (anti-)Hermitian, and also use MPS's to estimate the energy error incurred by sf truncation as @aakunitsa suggested. (I think this would require some modification of our old script though because right now I believe it only considers df truncation.)
|
When generating quantum resource estimates, many of the Hamiltonians (for example
fcidump.41_1_ts_noncan_0.2_new.2f0b6ced-7831-4fe0-b95e-ce4d456c9c6b
) give warnings about the double-factorized fragments being neither Hermitian nor anti-Hermitian. Based on discussion with @kjm538 this could potentially indicate a problem with the resource estimates. We should investigate this and make changes as needed.The text was updated successfully, but these errors were encountered: