Minzhao Liu

Hi, I am also trying to understand the quality of contraction order for cuquantum and cotengra, and I am trying to use cotengra contraction order in cuquantum contraction for fair...

Hi Dmitry, Thank you for the response and the file is attached. [std.log](https://github.com/NVIDIA/cuQuantum/files/12316705/std.log)

[std.log](https://github.com/NVIDIA/cuQuantum/files/12316928/std.log) Hi, I have changed these variables, but I ran it on a single GPU login node of a cluster with compute nodes with multiple GPUs each.

Thank you for the feedback! Yes it's sycamore 53 depth 20 I don't think there are hyperedges. I enabled slicing. When the path is not imported it works perfectly fine...

Hi Ali! Thank you for the feedback. It works after slicing is supplied. I was expecting cuquantum to take the path and find the slices on its own.

> @sss441803 has your issue been addressed? Hi, the answers are sufficient for solving my own issues with the workaround 'CUTENSORNET_CONTRACTION_OPTIMIZER_CONFIG_SIMPLIFICATION_DISABLE_DR'. Azzam did say that a proper fix should come...

I am happy if the issue is closed since the current fix is sufficient for me. I was just expecting some more updates since you mentioned more details will come...