[MITgcm-devel] lab_sea & seaice_evp
Martin Losch
Martin.Losch at awi.de
Fri May 11 10:01:16 EDT 2007
Ooops, how did that happen? I'll fix that in a minute. While look at
this problem I also spotted another bug. Thanks for sticking my nose
back into my own dirt (you do this to dogs and cats to potty train
them, right?) (o:
Martin
On 11 May 2007, at 15:47, Jean-Michel Campin wrote:
> Hi Martin,
>
> I am getting this error when running the testreport with
> ifort v9.1 (+ all checking option on), in lab_sea exp:
>
> forrtl: severe (193): Run-Time Check Failure. The variable
> 'seaice_evp_$E11Z' is being used without being defined
> Image PC Routine Line Source
> mitgcmuv 08C6D7B4 Unknown Unknown Unknown
> mitgcmuv 08C6BF4D Unknown Unknown Unknown
> mitgcmuv 08C404AA Unknown Unknown Unknown
> mitgcmuv 08C092AF Unknown Unknown Unknown
> mitgcmuv 0867C72C Unknown Unknown Unknown
> mitgcmuv 0866DB76 Unknown Unknown Unknown
> mitgcmuv 0875BFDE Unknown Unknown Unknown
> mitgcmuv 08A28811 Unknown Unknown Unknown
> mitgcmuv 08A653F7 Unknown Unknown Unknown
> mitgcmuv 08BC321C Unknown Unknown Unknown
> mitgcmuv 08BC3435 Unknown Unknown Unknown
> mitgcmuv 089A872C Unknown Unknown Unknown
> mitgcmuv 08049A06 Unknown Unknown Unknown
> libc.so.6 00C054E4 Unknown Unknown Unknown
> mitgcmuv 08049941 Unknown Unknown Unknown
> forrtl: error (76): IOT trap signal
>
> It was OK the last time I tried on May 03.
>
> And 2nd test, lab_sea.lsr is running OK.
> Do you have an idea of what variable is not set properly
> (it happens @ the 1rst iteration) in SEAICE_EVP ?
>
> Also, should we update the output_adm.txt of this exp since
> you changed the forward test output ?
>
> Cheers,
> Jean-Michel
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel
More information about the MITgcm-devel
mailing list