[MITgcm-devel] more seaice

Chris Hill cnh at mit.edu
Thu Apr 29 14:02:47 EDT 2004


All,

 Quick comment - sorry if I have misunderstood, I haven't been reading this
thread that carefully.

 We should have a separate sea-ice time step. In many cases, including
high-res cube, we may want to call sea-ice every n thermodynmics time steps.

 From Martin's description it sounds like the default for deltatseaice
should be deltattracer.

BTW - Alistair and I still find it hard to believe sea-ice can't just return
tendencies. Martin, if you can show it could work with just tendencies that
would be great!

Chris 

> -----Original Message-----
> From: mitgcm-devel-bounces at mitgcm.org 
> [mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Jinlun Zhang
> Sent: Thursday, April 29, 2004 1:54 PM
> To: Martin Losch
> Cc: MITgcm-devel at mitgcm.org
> Subject: Re: [MITgcm-devel] more seaice
> 
> 
> 
> Hi Martin,
> 
> Martin Losch wrote:
> 
> >
> > The timestep issue, I am not that clear about. I have made 
> all changes 
> > in growth, but I think all deltaT should replaced by either 
> deltaTmom, 
> > deltaTfreesurf or deltaTtracers. What do the code czars think?
> > (I won't have time to do this until next week, anyway)
> 
> I would prefer keeping DELTAT for sea ice in case we want 
> asyncronized runs.
> 
> >
> >
> > > Forgot to mention, NPSEUDO is only used for ADI, and as I 
> said ADI 
> > > does not work properly.  Jinlun, should we just get rid 
> of it from 
> > > the main branch of the code to avoid confusion?
> > > It will still be there in the CVS archive.
> >
> > What does npseudo do for lsr, because I noticed that if 
> npseudo > 1, 
> > lsr will be called npseudo times, and the "error"-print out 
> in stdout 
> > reduces with each call.
> 
> npseudo is generally used for ADI solver. Since LSR is more 
> suitable for MITgcm, we can just get rid of it.
> Jinlun
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel
> 




More information about the MITgcm-devel mailing list