Dear Hans-Juergen, thanks a lot for your hint anyway! I have changed dt to 20 seconds according to your recommendations, however there are no changes in results, model crashed with the same errors. However, the “Conflicting CPU frequencies detected” message is not the only cause for crash, because I have run an other job for base domain, which get the “Conflicting CPU frequencies detected” message, but didn’t crash. The “__libm_error_support” appears by the nested run only.
Push notifications in your browser are not yet configured.
Dear Hans-Juergen, thanks a lot for your hint anyway! I have changed dt to 20 seconds according to your recommendations, however there are no changes in results, model crashed with the same errors. However, the “Conflicting CPU frequencies detected” message is not the only cause for crash, because I have run an other job for base domain, which get the “Conflicting CPU frequencies detected” message, but didn’t crash. The “__libm_error_support” appears by the nested run only.