I switched to use datenum(clock) in now.
I think the problem was that the offset from the current time zone to
coordinated universal time changes throughout the year and I was using
a constant offset from GMT to the current time zone.
Thanks,
- Paul
On Oct 4, 2005, at 6:25 PM, Keith Goodman wrote:
> The octave-forge function 'now' is (for me) off by an hour:
>
>>> datestr(now)
> ans = 04-Oct-2005 14:20:59
>>> system('date')
> Tue Oct 4 15:21:03 PDT 2005
> ans = 0
>
> But the octave function 'clock' works:
>
>>> datestr(datenum(clock))
> ans = 04-Oct-2005 15:21:09
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>
|
