[MITgcm-devel] Re: [MITgcm-support] obcs_apply_ptracer

Dimitris Menemenlis menemenlis at sbcglobal.net
Mon Apr 14 09:32:09 EDT 2008


Martin, thank you for catching the staggertimestep problem.  I will fix.
This will require modifying:
MITgcm/verification/lab_sea/results/output.salt_plume.txt
MITgcm/verification/seaice_obcs/results/output.txt

> PS. it turns out, that it is not trivial to correct the topography along the
> boundaries, because the obcs information is not yet available at the time
> r_low is read. This is a problem as it is probably dangerous to change hfacc
> after this grid initialisation phase, isn't it? I would need to call
> obcs_init_fixed  (or at least the first part where OB_Jn/s, and OB_Ie/w are
> set) before ini_depth (or from within ini_depth).

Would it be easier to provide a matlab routine that takes care of this digging 
offline?  Also, will this digging require sensible initial T/S/ETAN values, or 
are they not needed because they are outside the open boundaries?

D.



More information about the MITgcm-devel mailing list