Hi,
Thanks for your help!



 KFrank:

I do recall seeing some github issues that suggest that einsum()
might better at optimizing some index-contractions than others.


Yes, I did some research before posting and saw these issues and some posts on this forum too. Maybe I could reorder the dimensions and time different options.
Your answer is the kind of approach I was looking for. Actually, I already have some reshaping earlier in the code because channels and time are originally interleaved in the data source, so I wonder if chaining all these operations might impact performace.
I will time it for my particular case and see if this speeds things up.
Thanks again!