[MITgcm-devel] mon_solution & eedie

[Chris Hill]

JM

 re - MPI_BARRIER, did you also try commenting out MPI_Finalize?

Chris 

> -----Original Message-----
> From: mitgcm-devel-bounces at mitgcm.org 
> [mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of 
> Jean-Michel Campin
> Sent: Saturday, December 13, 2003 6:31 PM
> To: adcroft at mit.edu
> Cc: MITgcm-devel at mitgcm.org
> Subject: [MITgcm-devel] mon_solution & eedie
> 
> 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.
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-devel
> 
> 
> 
>