<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">If you are running multicore the default MITgcm setup isn’t exactly reproducible due to round-off differences amplified by the intrinsic ocean chaos. So it will blow up at slightly different time-steps. <div class=""><br class=""></div><div class="">The restart should be the <i class="">exact</i> same at the start of the run though and for at least a few timesteps. </div><div class=""><br class=""></div><div class="">Matt</div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 22, 2021, at 7:00 AM, 赤羽蓝 <<a href="mailto:lanchiyu12@gmail.com" class="">lanchiyu12@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Dear all,<br class=""><br class="">I am running a regional ocean circulation model. Something strange happened. I use the pickup to restart the model after it blows up. However, the restart is not exactly the same as the previous one. I use the last pickup before the blow-up time, then restarted model can run even longer than the previous blow-up time.<br class=""><br class="">By the way, I use “pickupStrictlyMatch=.TRUE.” in the data file. I mainly use the KPP, the EXF (with surface SSS and SST relaxation), and OBCS packages.<br class=""><br class="">Any ideas will be grateful.<br class=""><br class="">Lambert<br class=""></div>
_______________________________________________<br class="">MITgcm-support mailing list<br class=""><a href="mailto:MITgcm-support@mitgcm.org" class="">MITgcm-support@mitgcm.org</a><br class="">https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!TtnbfvDUJ17oFrdLe6p3qPJjafPypLrULpTymiJfcwzwpa-6kFpBqCF1F9UgM3BHqw$ <br class=""></div></blockquote></div><br class=""></div></body></html>