How to convert different timestamp formats?

[python_newbie09]

timestamp has a different encoding compared to the first one and that's what I am trying to figure out now. They are matlab files and it's really painful with these files somehow being saved with different encodings

encoding is something different and it has nothing to do with timestamp format.

Okay, so when I used the script below in matlab, I am getting a more appropriate timestamp

t = datetime(42737.614433,'ConvertFrom','excel')

t =

datetime

02-Jan-2017 14:44:47

So it has something to do with the file being recorded in excel before saving as a matlab file, i guess

---

encoding is something different and it has nothing to do with timestamp format.

Okay, so when I used the script below in matlab, I am getting a more appropriate timestamp

t = datetime(42737.614433,'ConvertFrom','excel')

t =

datetime

02-Jan-2017 14:44:47

So it has something to do with the file being recorded in excel before saving as a matlab file, i guess

in python, i have to use the code below to get the same result.

t = pd.to_datetime('1899-12-30') + pd.to_timedelta(42737.614433,'D')

[buran]

in excel epoch is 1 January 1900, i.e. the whole number is days after 31.12.1899
the reason why you need to add 30 December 1899, not 31st is an known error in excel - Excel incorrectly assumes 1900 is a leap year (actually it was error in Lotus 1-2-3 and was kept in excel for compatibility)
https://support.microsoft.com/en-us/help...-leap-year

so you need to distinguish between the two. If you don't know in advance it makes sense to make conversion, then test if the result year is greater than some year (e.g. 2000) and apply different conversion if not.

[python_newbie09]

in excel epoch is 1 January 1900, i.e. the whole number is days after 31.12.1899
the reason why you need to add 30 December 1899, not 31st is an known error in excel - Excel incorrectly assumes 1900 is a leap year (actually it was error in Lotus 1-2-3 and was kept in excel for compatibility)
https://support.microsoft.com/en-us/help...-leap-year

so you need to distinguish between the two. If you don't know in advance it makes sense to make conversion, then test if the result year is greater than some year (e.g. 2000) and apply different conversion if not.

thanks a lot. I will change it accordingly. thanks for the patience