Re: Q about clmDayTLL

Thanks, Dennis. It is, in fact, the day_of_year function that I'm using to
create the yyyyddd array that is causing the issue, since it seems to
translate the noleap calendar to a gregorian calendar.

On Mon, Apr 26, 2010 at 10:36 AM, Dennis Shea <shea@ucar.edu> wrote:

> The function is hard wired to return (366,:,:)
>
> The input time array is ' yyyyddd '. If the yyyyddd
> is correct for the 365 or 360 day calendars, then
>
>
>
> x366 = clmDayTLL(yyyyddd, x)
>
> xNew = x366(0:364,:,:) ; 365 day year
>
> xNew = x366(0:359,:,:) ; 360 day year
>
> Good luck
>
>
> On 4/26/10 11:18 AM, Bridget Thrasher wrote:
>
>> I have 5 files, each with 10 years worth of daily data on a "noleap"
>> calendar (3650 days total). I am using clmDayTLL to create the daily
>> climatology from these files. The function is creating an array of 366
>> days even though I have no leap days in my data. Is this the way it's
>> supposed to work? Would it do the same with data on a 360-day calendar?
>>
>> -Bridget
>>
>> --
>> Bridget Thrasher, PhD
>> Postdoctoral Researcher
>> Climate Central
>> www.climatecentral.org <http://www.climatecentral.org>
>>
>>
>>
>>
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>

-- 
Bridget Thrasher, PhD
Postdoctoral Researcher
Climate Central
www.climatecentral.org

_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Mon Apr 26 11:42:39 2010