[MITgcm-devel] thsice + seaice

[Dimitris Menemenlis]

Martin and Jean-Michel, the 18-km Arctic domain integration with  
thsice and seaice is completing its second year of integration and I  
am not getting any BBerrs at all since initializing from ice thickness  
only.  I will download the fields later today (when I get to office)  
and take a look to see if they are sensible.  Dimitris

Dimitris Menemenlis <menemenlis at jpl.nasa.gov>
Jet Propulsion Lab, California Institute of Technology
MS 300-323, 4800 Oak Grove Dr, Pasadena CA 91109-8099
tel: 818-354-1656;  cell: 818-625-6498;  fax: 818-393-6720

On May 6, 2008, at 12:00 AM, Martin Losch wrote:

> Hi Jean-Michel,
> with a running, not-exploding model I still get a lot of "errors"  
> like this one
>> BBerr - Bug: IceT(1) > Tmlt 239  32  1  1 -5.376776E-02 -5.400000E-02
> with IceT(1) getting as high as -1.e-2, but never positive. I wonder  
> if this is anything to worry about, or whether is this an occasional  
> non-convergence of the solver (thsice_solve4temp).
>
> BTW, these multiple write statements in thsice_solve4temp make it  
> impossible to vectorize this routine (the other issue are the called  
> routines that have to inlines). Is there a way to get around these  
> write statements, like enclosing them in #ifdef ALLOW_DBUG_THSICE,  
> since they don't do anything but print out warnings. Or is this  
> package still so unstable that we cannot afford the absense of  
> continuous warnings?
>
> Martin
>
> On 6 May 2008, at 01:51, Jean-Michel Campin wrote:
>
>> Dimitris & Martin,
>>
>> Good that it's working for both of you.
>> It seems that there is something strange in the initialisation.
>> Don't have time to look at it now, but will at some point.
>>
>> An other thing:
>> who is supposed to update the output.txt of seaice_obcs ?
>> Otherwise, (since April 26) if something (wrong) happens to this  
>> set-up,
>> we will not be able to catch it.
>>
>> Cheers,
>> Jean-Michel