[MITgcm-support] cal, exf, obcs: problem at the tile boundaries

[Dimitris Menemenlis]

Nico, does problem occur during first time step or later on?
Have you tried dumping all the EXF* fields using
data.diagnostics to see what they look like?
D.

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, USA
tel: 818-354-1656;  cell: 818-625-6498;  fax: 818-393-6720

On Jun 3, 2009, at 9:29 AM, Nico Wienders wrote:

> My apologies for insisting on this matter, but i still haven't been
> able to find what
> is the problem here. The errors i am getting through exf_check_range.F
> are very localized.
>
> My domain is as said 400*801.
>
> 	If i use 12 proc, NPx=4 Npy=3
> 	The error are localized on the western side of the first tile (1,1),
> at three different locations
> 	in longitude. (cf. 4x3.jpg).
>
>
> 	if i use 10 procs, NPx=10 Npy=3
> 	The error is still localized on the western side of the first tile
> (1,1) but now at several locations
> 	(cf. 10x1.jpg).
>
> 	if i use 9 procs, NPx=1 Npy=9
> 	The error is localized on the western side of the first tile (1,1) at
> one location.
> 	(cf. 1*9.jpg)
> 	
>
> Curiously the spreading of this error becomes bigger in longitude if i
> reduce the number of forcing fields.
> Thank you.
>
>
>
>
> <4x3.jpg><10x1.jpg><1x9.jpg><ATT00001.txt><ATT00002.txt>