[MITgcm-support] Calculation overflow problem

[Martin Losch]

You should run your model with default debugLevel (=1) and with a montiorFreq that allows you to see which part of the model explodes first. Then the STDOUT.0000 is interesting for debugging.

I would start by turning off the partial cells (hFacMin),
also, use viscAhGrid (<1) instead of viscAh to ensure stability.
Otherwise the information that you provide does not allow further diagnosis. 

Martin

> On 1. Nov 2023, at 13:09, Haoran Xu <xu1jian2wei3 at 163.com> wrote:
> 
> Dear  MITgcm community,
> I am running a model in Luzon strait with open boundary condition t,s,u,v. The model resolution is 500m.The calculation stopped due to overflow.I found the velocity increased in one area (image attached,velocity at level 78).I've tried smoothing the topography in this area(image attached),but it did not help much(overflow only delayed).I want to know if  my configuration is properly(file attached).Or there is anything I can try to deal with this problem?
> 
> Any suggestions would be helpful. Thanks in advance.
> <velocity_at_78.png><topo.png><smooth_topo.png><data>_______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20231101/391cc94e/attachment.html>