[MITgcm-devel] two of my favorite packages: exf/cal

[Martin Losch]

Hi there,
thanks, I'll ignore it BUT
> (PID.TID 0041.0001)    Runnoff starts at     ************
it's still strange that this ****** goes away if I put a line print  
the value of runoffstartstate just before this statement. Shouldn't  
that worry me?

Martin

On 8 Feb 2007, at 16:49, Patrick Heimbach wrote:

>
> Martin,
>
> I think I can confirm all of Dimitris' statements.
> I have similar warnings within initializing some
> ECCO-related times/dates. These warnings are benign.
> Essentially, the call_fuldate gets used also to initialize
> fields that carry entries before model start time,
> such as forcing records w.r.t. to an absolute time.
>
> Haven't used the EXF_VERBOSE option in a while
> since it screws up the adjoint.
>
> Cheers
> -p.
>
>
>
> On Feb 8, 2007, at 9:31 AM, Dimitris Menemenlis wrote:
>
>> Martin, I always get this error
>>
>>> cal_CheckDate: Calendar date before predef. reference date
>>
>> and ignore it.  It is because no startdate is needed nor
>> has been specified for runoff in data.exf yet cal_FulDate
>> is called in exf_readparms.F
>>
>> I have just checked in a fix that will remove this spurious
>> warning message, i.e., check for period .gt. 0 before calling  
>> cal_FulDate
>> in exf_readparms.F
>>
>> Your other option is to specify a startdate for runoff in data.exf,
>> even though it will never be used.
>>
>> D.
>> _______________________________________________
>> MITgcm-devel mailing list
>> MITgcm-devel at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
>
> ---
> Dr Patrick Heimbach | heimbach at mit.edu | http://www.mit.edu/~heimbach
> MIT | EAPS, 54-1518 | 77 Massachusetts Ave | Cambridge, MA 02139, USA
> FON: +1-617-253-5259 | FAX: +1-617-253-4464 | SKYPE: patrick.heimbach
>
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel