[MITgcm-devel] calendar checkdate

Jean-Michel Campin jmc at ocean.mit.edu
Tue Apr 17 13:39:33 EDT 2012


Hi Hang and Matt,

Thanks for checking this and sorry for the effort and time you spent 
tracking these unvalid date.
Talked briefly with Patrick, and it could be that (some of) these
dates are not really used (the reason why it's was not a problem
to have them set to zero). Would need to check this.
But if it's the case, we could change their default to a valid date,
similar to smrareastartdate1,2 settings in seaice_readparms.F

Cheers,
Jean-Michel

On Tue, Apr 17, 2012 at 09:02:28AM -0700, Hong Zhang wrote:
> 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
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel



More information about the MITgcm-devel mailing list