[MITgcm-devel] other problem in recent check-in

[Martin Losch]

Yes, and the reason for these unexpected numbers is, that  
exf_getffieldsrec does not know about the model calendar. Somewhere  
it sets secondsInYear=31536000. or 31622400 if it's a leap year, but  
that's only correct for a gregorian calendar, when I set them to  
31104000, I get 0.5. I can fix that tomorrow, if you want, but it may  
break global_ocean.cs32x15 (but maybe not, because that one is not  
using yearlyFields).

Martin

On 30 Jan 2008, at 18:02, Dimitris Menemenlis wrote:

> Martin, is the test below with useExfYearlyFields?
>
>> I have tried this in global_with_exf: I set startdate in data.cal  
>> to Jan01,
>> 0:00h with a 'model'-calendar, so 30day months, 360day years. I set
>> startdates for the forcing fields in data.exf to Jan16, 0:00h,  
>> which is
>> exactly the middle of the month a full 15*24h have passed, a full  
>> 15*24h to
>> go till the end of the month at 30th, 24:00h. Now I expect the fac  
>> for
>> myiter=0 to be 0.5, but it's 0.42857143 (which is 12.857143/30,
>> incidentially). When I set them to Jan15, 0:00h, the first weight  
>> is 0.4
>> (12/30). I don't understand this package.
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel