Time in milliseconds: Difference between revisions
Jump to navigation
Jump to search
(→Notes) |
(→Notes) |
||
| Line 4: | Line 4: | ||
==Notes== | ==Notes== | ||
* Items in the {{software}} can store time as an attribute, in which case this number is stored as a double. When interpreted by the {{software}}, this double (decimal) number is first converted to a long number (no decimals, but larger range) before interpreting this as a time offset in milliseconds. Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API. | * Items in the {{software}} can store time as an attribute, in which case this number is stored as a double. | ||
: When interpreted by the {{software}}, this double (decimal) number is first converted to a long number (no decimals, but larger range) before interpreting this as a time offset in milliseconds. Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API. | |||
Revision as of 10:07, 21 July 2020
Time can be stored as a number of milliseconds past a chosen starting point, also known as the epoch.
In the Tygron Platform, a time in milliseconds of 0, corresponds to 00:00:00:000 January 1st, 1970 in the UTC time zone.
Notes
- Items in the Tygron Platform can store time as an attribute, in which case this number is stored as a double.
- When interpreted by the Tygron Platform, this double (decimal) number is first converted to a long number (no decimals, but larger range) before interpreting this as a time offset in milliseconds. Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API.