[MITgcm-devel] calendar checkdate
Hong Zhang
hong.zhang at ucla.edu
Tue Apr 17 12:02:28 EDT 2012
Jean-Michel Campin wrote:
> Hi Martin and others,
>
> One thing that would be nice, when you have time, would be to check
> that you can run your set-up with the current code, with the stops that
> I already added (which I think are necessary); and at the same time, try
> to record the warnings you get from cal_CheckDate, such as:
>
>> cal_CheckDate: Calendar date before predef. reference date
>>
> so that we can figure out (if you send me the relevant part of the
> set-up, I could take a look) what is really needed in term of check & stop.
>
> Dimitris, I am not sure this is what you have in mind when you wrote:
>
>> One question I have is whether it is possible to do the changes that you
>> have in mind while keeping the user interface, the CPP options and the
>> runtime parameters unchanged?
>>
> I did not really change the user interface (neither the argument list
> of pkg/cal subroutines, except for the internal initialisation stage),
> but it might help also if you could go through the same check as mentioned
> above.
>
Hi Jean-Michel,
we tested the new calendar.
For CS510 pure forward run, it's OK, no warning or error message.
For CS510 adjoint run, previously we got warnings of
cal_CheckDate: Calendar date before predef. reference date
in both STDOUT.0000 and STDERR.0000
Now using the new code, the model stopped with
(PID.TID 0000.0001) *** ERROR *** CAL_CHECKDATE: Invalid month in date(1)= 0
(PID.TID 0000.0001) *** ERROR *** CAL_FULLDATE: fatal error from cal_CheckDate
in STDERR.0000
With Matt's help, we provide additional
costIceStart1 = 20080101,
costIceEnd1 = 20120101,
(in data.seaice)
and the model runs OK.
cheers
hong
More information about the MITgcm-devel
mailing list