[MITgcm-devel] mon_solution & eedie

Jean-Michel Campin jmc at ocean.mit.edu
Sat Dec 13 18:30:56 EST 2003


Hi Alistair,

I don't like too much this "mon_solution.F" :
a) the name does not tell that this is "checking"
 the solution. but this is more a matter of personal taste.
b) the error message that is printed:
> MON_SOLUTION: STOPPED DUE TO EXTREME VALUES OF SOLUTION
 does not tell that the temperature is wrong.
c) the eedie generate a strange message (Stephanie was 
 wandering what was going on the first time it happened).
d) the eedie prevent the coupled-model to stop (all the processor
 are waiting for something that does not come).

I fixed the point (d) simply not calling eedie when using the coupler, 
but I wander if we cannot simply remove the "call eedie" from 
mon_solution.F, if it's too difficult to print a different 
error message.

See you,

Jean-Michel

PS: Chris, I commented out the MPI_BARRIER in eedie.F but this
does not change anything. When the temperature is out of range,
the eedie (called from mon_solution) continue to wait.



More information about the MITgcm-devel mailing list