As a continuation of this topic (viewtopic.php?f=19&t=4423), we decided to output all model variables at the 'problematic' point of model’s explosion (during long-time simulations), in order to investigate why.
It seems, that temperature goes randomly (?) at the next time step after it becomes masked due to WET-DRY subroutine (see the picture below). But, it also seems, that after it becomes the wet-point back, it still has this random temperature value (!). See the picture below: x-axis is the time-step axis, blue/red lines – temperature at the surface/bottom, green – mask (shifts from 1 to 0 and then back around the time step with a number 4080, blue points – sea surface elevation).
![](https://pp.userapi.com/c638225/v638225391/28f86/H5xdWUSBqrQ.jpg)
Here, on the picture below, the model explosion is caught. The temperature value could go as crazy as -40 (usually, it shouldn’t be a reason to explode, but we set an alarm on this). We assume, that if temperature could go down -40, it also could go up to NaN values that will lead to temperature vanishing in the whole domain, like in this topic (viewtopic.php?f=19&t=4423).
![](https://pp.userapi.com/c638225/v638225391/28f90/tts5c9Qi9F8.jpg)
The question is, how the wet-dry points are initialized as wet-points after they were dry-points for a while?
Thanks in advance.