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

[Martin Losch]

Dimitris,

forgot the advection scheme:
>> (also is has some advection/timestepping options that lead to a  
>> warning, also
>> not a good example, unless you want to test this check).
>
> Ooops!  What exactly is the advection/timestepping problem?  I need  
> to make sure that I am not using it for our ongoing Arctic tests  
> (sigh!) or for the cubed-sphere integrations.
>
This is what STDERR gives:
csysl4::run> cat STDERR.0000
(PID.TID 0000.0001) ** WARNING ** GAD_CHECK: potentially unstable  
time-stepping (Internal Wave)
(PID.TID 0000.0001) ** WARNING ** GAD_CHECK: need  
"staggerTimeStep=.TRUE." in "data", nml PARM01
because in data:
  tempAdvScheme=7,
  saltAdvScheme=7,
without staggertimestep=true

Martin

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).