[MITgcm-devel] seaice code beyond checkoint61j blows for ECCO-GODAE

Patrick Heimbach heimbach at MIT.EDU
Mon Apr 13 17:07:52 EDT 2009


Hi there,

I've update the seaice code from checkoint61j to latest,
and the ECCO-GODAE production now blows up about 1/3rd into
the calculation (i.e. after roughly 5 years of integration).

I have double-checked that reverting only(!) pkg/seaice back to c61j
gives back stable code.
I have done this for current iter. 73, not yet iter. 0.

(At least) two possibilities:
1.
optimization compensated for some seaice errors that are no longer  
there,
and therefore adjusted forcing causes the blow-up
2.
new seaice code has problems.
3.
Some parameter setting defaults have changed,
which I've missed (if so, we should start a mechanism to document that,
not just for seaice).

What's a bit disconcerting is that it seems the old code was more
stable than the new code(?)

I will try an iter.0 run later.
In the mean time, any suggestions?

Cheers
-p.

---
Patrick Heimbach | heimbach at mit.edu | http://www.mit.edu/~heimbach
MIT | EAPS 54-1518 | 77 Massachusetts Ave | Cambridge MA 02139 USA
FON +1-617-253-5259 | FAX +1-617-253-4464 | SKYPE patrick.heimbach





More information about the MITgcm-devel mailing list