Hello, I have encountered error termination. But the message files does not specify any reasons for the error. I am suspecting it came from potential instabilities. Is there any good way to troubleshoot to see what caused the error?
Thanks,
JW
Physical anomalies can often be seen in the d3plot.
If nothing appears abnormal at the time of the error termination, the d3hsp file can also provide more info than the messag file into why the simulation failed.
@rybask1 There is only 1 d3plot file which is the initial state. Since the d3hsp file is huge, is there a good way to search for the cause of error termination?
As @NegativeVolume mentioned, try using Ctrl+F and searching the message file and d3hsp for words like error, warning, NaN, out of range, or fail.
best!
@wjy950312 You can also try searching for “NaN” or “out-of-range” and see if that yields anything
@wjy950312 Hello, I think I have the same issue as You did. Did You faced it?
D3hsp shows no error and so the messag file. In dialog window shows up a path to results and then all CPUs are no longer loaded.
Some serious errors, like access violations, are written to the terminal instead of d3hsp or messag. If you're using ls-run, the terminal output is saved to lsrun.out.txt. It may be worth checking that.