I see - that’s good that the code ran on other machines you have. I wish I knew what the reason was, but it’s hard for me to know or even to guess based on this information. I think the only way I could find out would be to reproduce the bug myself (though I would need to have access to the same version of MKL most likely). Then what I would do is to look at the state of the ITensor part of the code before it goes into the MKL LAPACK call happening there to see if it looks sensible, or otherwise use a debugger to look at the stack trace to get any clues.
Guessing at a high level, here are the only possibilities I can think of:
- it could be the version of MKL you have has a bug in it or some other issue, and you could fix things by using a different version
- it could be that the ITensor part of the code is running differently on this new machine somehow (different input file? computer has less memory?) and that’s causing an error that’s just showing up as an MKL error but could really have a different underlying reason
Please check how much memory the program is using and other things like that, because sometimes if a computer runs out of memory it can result in errors that are very confusing and look like they are to do with something else. But for this tutorial code I doubt it would come close to using a lot of memory unless you input very extreme parameters into it (very long times or large system sizes, cutoff of zero, etc.)