Terran computational calendar

Also called the terran calendar or the terran calculator, the terran computational calendar is a simple, efficient, highly accurate, zero-based numbering calendar system.
Containing 13 identical months of 28 days each, this calendar includes an additional short month at the beginning of each year containing a single day plus a leap year day every four () years.
Each year of the terran computational calendar is synchronized with the northern winter solstice and year zero of the calendar occurred on December 22, 1969 00:00:00 UTC in the Gregorian Calendar which is exactly 10 days before the UNIX Epoch. At the time of this writing (2013-12-28 11:23:19 UTC in the gregorian calendar), the terran computational calendar date is 44.1.4.11.23.19 TC .
Purpose
Like any other clock or tool to measure time, this calendar's only true purpose is to measure time efficiently and accurately. It is simple in its design, easy to calculate, easy to convert, and extremely accurate (see the ).
Birth of the Terran Computational Calendar
Year Zero of the terran computational calendar began at the stroke of midnight between the 21st and the 22nd of December in 1969 of the Gregorian Calendar in Coordinated Universal Time (UTC), exactly 10 days before (or -86400 seconds of) the Unix Epoch(UNIX time), exactly 723 terran computational calendar years after the last solstice-perihelion conjunction, and precisely 43 terran computational calendar years before the end of the 13th b'ak'tun (b'ak'tun 12) and start of the 14th b'ak'tun (b'ak'tun 13) of the Mayan long count calendar (December 21, 2012 of the gregorian calendar).
Calendar Notation
Date Representation
When writing the date in the terran computational calendar, write it in the following way: *.0-13.0-27.0-23.0-59.0-59 where * is the current integer year, 0-13 is the month and so on and so forth, with all units separated by a . (period/dot). To see this in action, watch a [http://terrancalendar.com/tick.html#-3125-12-22%2023:59:50%20UTC 10 second countdown to the year -5094]. [http://terrancalendar.com/#date_representation more ›]
Designators
Other than the periods/dots of the terran computational calendar's notation, one of the best ways to distinguish this calendar from others is to append a TC or TCC designator at the end of the terran date (preferably the former). These designators stand for "terran calendar" or "terran computational" and "terran computational calendar". The TC or TCC designator automatically assumes a UTC timezone. For instance, the terran date at the time of this writing ( 2013-12-28 12:4:3 UTC in the gregorian calendar ) is written as 44.1.4.12.4.3 TC (not 44.1.4.12.4.3 TC UTC as the UTC would be redundant). Using timezones and daylight savings time is discouraged for this calendar, though, if daylight savings time or timezone must be included, append after the TC designator. For example, in the US East Coast, 44.0.0.20.31.01 TC could be written as 44.0.0.15.31.01 TC EST or 44.0.0.15.31.01 TC -0500 . [http://terrancalendar.com/#designators more ›]
Time Measurement Units
Zero-based Numbering
The terran computational calendar utilizes a zero-based numbering system for all time measuring units (like years, months, days, hours, minutes, seconds) so that each time measuring unit uses 0 as its initial position. [http://terrancalendar.com/#zero_based_numbering more ›]
Years & Yero Zero
Years in the terran computational calendar function essentially as integers (…, -3, -2, -1, 0, 1, 2, 3, …). This is similar to astronomical year numbering. One might think of Year 0 (Year Zero) as being the 0th year or year zero of the terran computational calendar. [http://terrancalendar.com/#years more ›]
Months
For each year, there are 13 identical months containing 28 days each, in addition to a short 1 or 2 day Zeroth Month preceding the other 13. So, in effect, there are actually 14 months: a single month with 1 or 2 days and 13 months containing 28 days. [http://terrancalendar.com/#months more ›]
Month Zero
At the beginning of each year, the 1 or 2 extra calendar days necessary to complete a full year, consisting of New Year's Day and leap day, are put into Month 0 (Month Zero) which precedes the other 13 normal months in the calendar. [http://terrancalendar.com/#month_zero more ›]
Month Names
It may be eaisest to name each month by its month number. By doing so, we end up with Month 0, Month 1, Month 2, Month 3, Month 4, Month 5, Month 6, Month 7, Month 8, Month 9, Month 10, Month 11, Month 12, and Month 13. [http://terrancalendar.com/#month_names more ›]
Days & Day Zero
As the terran computational calendar utilizes zero-based numbering, the zeroth day (day zero) in each month should is denoted by a 0. Therefore each month (with the exception of month zero) will have days 0 through 27. Month zero will include days 0 and 1.
The Zeroth Day of the Year
The zeroth day of the year is also the day zero (and usually the only day) in . [http://terrancalendar.com/#zeroth_day_of_the_year more ›]
Leap Year Days
Leap year days, if they exist in a given leap year, are day one in the year and also day one in Month Zero. Leap year days will generally recur once every four years during years that are a multiple of 4 with exception to years that are a multiple of 128. [http://terrancalendar.com/#leap_year_days more ›]
Omitted Leap Year Days
Exceptions to the regular 4 year - leap year cycle is that a leap year day will be skipped once every 128 (27) years or 32 (25) leap year cycles starting at and including year zero. [http://terrancalendar.com/#omitted_leap_years more ›]
Hours
Hours in the terran computational calendar function the same as a 24-hour clock and therefore hours range from 0 to 23 and midnight occurs right between hour 23 and hour 0.
Minutes & Seconds
Both minutes and seconds have a range from 0 to 59.
Syncronizations
Solstices
The terran computational calendar follows the tropical year and is synchronized with the winter solstice in the northern hemisphere (summer solstice in the southern hemisphere) so that each northern winter solstice will take place either in or a day or two on either side (see section on ). [http://terrancalendar.com/#solstices more ›]
Unix Time
Though there are many alternatives, the UNIX Epoch is subjectively the best candidate for synchronization with the terran computational calendar in our current information era. But in order to also synchronize the calendar with the solstice, we must start year zero exactly ten days before the unix epoch or at -86400 in UNIX time (1969-12-21 (Gregorian) instead of 1970-1-1 (Gregorian)). [http://terrancalendar.com/#unix_time more ›]
Mayan Calendar
The popular end date of the 13th b'ak'tun (b'ak'tun 12) and start of the 14th b'ak'tun (b'ak'tun 13) of the Mayan long count calendar (December 21, 2012 of the gregorian calendar) falls precisely 43 terran computaional calendar years after the start of the terran computational calendar (at 43.0.0.0.0.0 TC). [http://terrancalendar.com/#mayan_calendar more ›]
Galactic Alignment (Galactic Center - Ecliptic Conjuction)
This most recent astronomical epoch for axial precession happened on December 22, 1998 of the gregorian calendar, and 29.0.0.0.0.0 TC of the terran calendar, whereby the ecliptic (the earth's orbital plane or the apparent orbit of the sun around the earth) passed through the galactic center. [http://terrancalendar.com/#galactic_alignment more ›]
Solstice-perihelion conjunction
The last time the solstice and the perihelion occurred at the same time was on December 22nd, 1246 of the Gregorian Calendar, and -723.0.0.0.0.0 TC of the terran computational calendar, which is exactly 723 terran years before the start of the terran computational calendar. [http://terrancalendar.com/#solstice_perihelion more ›]
Synchronization side note
A few years of trying out different calendar start times have proved NO date to be a good start time for a calendar. [http://terrancalendar.com/#side_note more ›]
Other Info
Yearly Quarters / Seasons / Equinoxes & Solstices
The terran computational calendar is synchronized with the solstice and each quarter or season occurs approximately 13 weeks (or 4 months and one week) after one another. [http://terrancalendar.com/#quarters more ›]
Calendar Accuracy
Omitting leap years every 128 years (see the section on ) creates an extremely efficient time keeping method. [http://terrancalendar.com/#calendar_accuracy more ›]
Code (Converting between calendars)
Here is some code to convert a terran computational date to and from a unix timestamp and to and from the gregorian calendar:
* PHP code for terran computational calendar conversions
* JavaScript code for a ticking terran clock
* current terran date
* converted past terran date
* ticking implementation of the current terran date
* [http://terrancalendar.com/tick.html#9876.5.4.3.2.1%20TC ticking implementation of a future terran date]
* [http://terrancalendar.com/tick.html#-3125-12-22%2023:59:50%20UTC ticking implementation of a negative converted terran date countdown to the year -5094]
Here is a form to [http://terrancalendar.com/#converted convert between the terran computational calendar and the gregorian calendar]

Main Menu

See Also

Main Menu