Alternative contraction path algorithms about tensornetwork HOT 6 CLOSED

Thanks! We definitely are looking for some advancements on contraction algorithms. If you want to make a PR, we would love to include it! :)

from tensornetwork.

Sure, we can look into it. It might be easiest to add a single algorithm at first to your contractors to see how the implementation goes. What about starting with the "optimal" algorithm?

from tensornetwork.

That would be awesome! Feel free to email me if you need any help.

from tensornetwork.

@dgasmith Out of interest: Are there any plans to do opt_einsum's path optimization in e.g. cython in the future? I am guessing it could make a significant difference to the performance of, say, the optimal path algorithm.

from tensornetwork.

This is something I would love to do and would help our downstream packages. Making an issue on the opt_einsum GitHub would be a good place to get started and we could figure out how we would implement this. My bet that most of the bottlenecks at this point are in the cost evaluations and set logic which could have extremely fast C implementations.

Apologies for not making progress on this issue, my time is a bit swamped at the moment. I should be able to get back to this issue in September (!).

from tensornetwork.

We've added most of the determanistic algorithms from opt_einsum as of #173. Any upgrades to opt_einsum now will be immediately incorporated into this library. ^-^

We had some issues getting the random contractors integrated, as they seem to not exist in the pip package. (See dgasmith/opt_einsum#93) Once that is fixed, integrating them should be one liners.

from tensornetwork.