-
Notifications
You must be signed in to change notification settings - Fork 32
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
Best practice on running cotengra via the opt_einsum API #23
Comments
Hi @rht, to be clear 1 If you have the einsum equation and arrays, you can use E.g.: expr = ctg.contraction_expression(eq, *shapes, optimize=opt)
out = expr(*arrays) |
In dgasmith/opt_einsum#217 (comment), @jcmgray stated that running
cotengra
optimization viaoe.contract_path(expression, *operands, optimize=opt)
(whereopt
is acotengra
optimizer) is slower than doing it viaquimb
. I have to add more detail that the path finding part of theopt_einsum
method alone is much slower than the entirety of the run viaquimb
. As such, the reasoning in that comment applies only to the contraction phase.What is the recommended way to do the path finding via
opt_einsum
, that is performant? The main use case is that most circuits are written in Qiskit/Cirq, and withcuQuantum
'sCircuitToEinsum
, it enables one to do contraction of any Qiskit/Cirq circuits.The text was updated successfully, but these errors were encountered: