octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #47627] datenum gives wrong result, ignores mo


From: anonymous
Subject: [Octave-bug-tracker] [bug #47627] datenum gives wrong result, ignores month
Date: Tue, 05 Apr 2016 16:36:41 +0000
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0

URL:
  <http://savannah.gnu.org/bugs/?47627>

                 Summary: datenum gives wrong result, ignores month
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 05 Apr 2016 04:36:40 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Ruben Gonzalez
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.1
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

the function datenum for some reason ignores the month

For example, performing a datenum for March 31st 2015 yields

datenum('2015-03-31 0:00','YYYY-MM-DD HH:MM')
ans =  735995

Now for doing it for the next day, April 1st, we get

datenum('2015-04-01 0:00','YYYY-MM-DD HH:MM')
ans =  735965

which is 30 days LOWER than the previous result. Next, use June 1st instead

datenum('2015-05-01 0:00','YYYY-MM-DD HH:MM')
ans =  735965

You get the VERY SAME RESULT, which means that the month is not factored into
datenum at all.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47627>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]