[MITgcm-devel] Problem in yersterday changes

[Jean-Michel Campin]

Some update:
I can reproduce the problem on my laptop with ifort and without MPI,
and the problem is still there with seaice_growth.F v.1.89 from
Oct.15 (looks like Gael's changes are not the problem).

Here is what I get when I run the noseaice test with idb:
> Program received signal SIGFPE
> cal_timeinterval (timeint=-9.2559631349317831e+61, timeunit=(...), date=(...), mythid=1, .tmp.TIMEUNIT.len_V$10=4) at /home/jmc/mitgcm/gcm_ifc/verification/lab_sea/bld_ad1p/cal_timeinterval.f:628
> 628         date(1) = int(timeint/float(secondsperday))
I guess timeint/secondsperday is too big to fit into an integer.

Jean-Michel

On Sun, Oct 17, 2010 at 10:51:41AM -0400, Jean-Michel Campin wrote:
> Hi,
> 
> Looks like there is a problem with all lab_sea AD tests
> as seen on aces with ifort+mpi:
> http://mitgcm.org/testing/results/2010_10/tr_aces-adm_20101017_0/summary.txt
> 
> My impression is that it's not directly related to mpi (to be confirmed).
> 
> This was before Martin's lates changes in seaice-solve4temp.F 
> and caused by one of yesterday modifs. 
> 
> I propose to hold on changes until this is fixed.
> 
> Cheers,
> Jean-Michel
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel