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

[Dimitris Menemenlis]

you can use useExfCheckRange=.FALSE. in data.exf EXF_NML_01
so the model runs and dumps something.  with forcing like that it will  
crash right away
so at best you will be able to obtain one or two time steps.

I'd run twice for a couple of time steps, once with monitorfreq set to  
0 so model does not stop with crazy values

and once with debulevel=3 and monitorfreq=1, so you dump as much as  
possible to look see where anomaly originates.

I assume you are using bulk formulae so anomaly could also come from  
your initial conditions.

good luck, D.

On Jun 3, 2009, at 11:33 AM, Nico Wienders wrote:

>
> On Jun 3, 2009, at 1:04 PM, Dimitris Menemenlis wrote:
>
>> 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?
>
> Yes. This was one of my last recourse. But exf_check_range.F
> stops the execution before we can get the first diagnostic
> dump. The problem occurs when the forcing fields are first read.
>
> I re-re-re-re-re checked again this morning, all the forcing fields
> are good: format (real*8), dimensions (lon,lat, time), values ....
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support