[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20041019: Bug in ut_calendar?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20041019: Bug in ut_calendar?
  • Date: Tue, 19 Oct 2004 11:26:35 -0600
Mary,

>Date: Tue, 19 Oct 2004 11:21:18 -0600 (MDT)
>From: Mary Haley <address@hidden>
>Organization: UCAR
>To: address@hidden (Steve Emmerson)
>Subject: Re: 20041015: Bug in ut_calendar?

The above message contained the following:

...
> Perhaps I am.  I got the same above results too (which were actually
> reported to me by another user), and was thinking that for time=1,
> this would be one month later, ie:
> 
>      units = 'months since 1870-1-1'
>      time  = 1
>      year  = 1870
>      month = 2
>      day   = 0
>      hour  = 0
>      second= 0
> 
> However, I guess this all depends on what a "month" is, and I'm
> guessing from this program, it's a fixed 30 days?

Not exactly.  30 days is 2592000 seconds; a "month" is defined as 1/12
of a tropical year or 2629743.831225 seconds.

Regards,
Steve Emmerson