01 · Where to find everything
| Page | Purpose and controls |
|---|---|
| Main clock · / | Decimal time, conventional time and date, local Berlin time, a monthly calendar and the ATLAS stardate. Select a zone, sync manually or use full screen. |
| Year calendar · /calendar | All 13 months with a smaller clock and stardate. Years 0001–9999, arrows and ±100/1000 jumps. Select a day to see its Gregorian date; “Today” returns to the current year. |
| History · /history | Convert between Gregorian, Julian and personal calendars. Astronomical years −9999 to 9999 or historical year numbering with an era. Optional time, JDN, a personal event list and JSON backup. |
| Analog · 5 hands | Four separate hands for hour/minute digits and one for seconds. A 57:24:12 example, hand highlighting, second-hand visibility, zone selection and an optional digital readout. |
| Analog · 3 hands | One hand each for the full hour, minute and second values. The same controls, with all three hands moving smoothly. |
| Help · /help | This guide, sources and a server response check. The button at the top opens the print dialog, where your browser may offer Save as PDF. |
Links stay on the same server address. For example: http://localhost:6140/help, if the port and address are the defaults.
English / Srpski
The language selector appears on every page. English is the default. Your browser remembers the choice for one year using a preference cookie. Switching languages reloads the page and keeps the selected calendar year in the URL; complete or save an unfinished event first. Saved event names and notes stay exactly as you wrote them. You can also open a page with ?lang=en or ?lang=sr. Changing the language changes labels, weekday names and number formatting; it does not change time, calendar rules or saved events.
Conventional numeric dates use day.month.year in both languages. Personal dates use year.month.day with three-digit month/day groups. English uses a decimal point and Serbian a decimal comma for the mathematical day number; dots between clock groups remain separators.
02 · How the idea developed
We started with a question: what if we divided the year into 13 equal months? 13 × 28 = 364 days, leaving one extra day in an ordinary year and two in a leap year. We then explored decimal time, where each larger unit contains 100 smaller units.
We had to choose one unit whose duration would stay unchanged. Keeping the conventional minute would make a 100-minute hour last 100 conventional minutes. For the final system, we chose to keep the day at 24 conventional hours and derive the new hours, minutes and seconds from it.
- v1.0 Digital clock, synchronization and a 13-month calendar.
- v1.1 Annual view; extra days placed in the first and last months.
- v1.2 A continuous Monday–Sunday cycle through months and years.
- v1.3 Historical conversion, negative years and year zero.
- v1.4 Stardate: the day count and day fraction as one number.
- v1.5 An analog display with five hands.
- v1.6 An additional analog display with three hands.
- v1.7 This guide and response diagnostics.
- v1.8 The name ATLAS Personal Time and English / Serbian throughout.
This personal system grew out of our conversation. Astronomical conventions provide foundations; the 13-month arrangement and clock design are our own project choices.
03 · Units and digital notation
In a fixed time zone, a day contains 86,400 conventional seconds. In our system, the same day has 100 × 100 × 100 = 1,000,000 new seconds.
| New unit | Contains | Conventional duration |
|---|---|---|
| Day | 100 hours | 24 hours |
| Hour | 100 minutes | 14 minutes 24 seconds |
| Minute | 100 seconds | 8.64 seconds |
| Second | 100 hundredths | 0.0864 seconds |
| Hundredth of a new second | 1/100 new second | 0.864 conventional milliseconds |
057.024.012.009 means 57 new hours, 24 minutes, 12 seconds and 9 hundredths. Every field runs from 000 to 099; the leading zero is a visual choice. The values otherwise need only two decimal digits. Twelve new hours equal 2 conventional hours, 52 minutes and 48 seconds.
new_hours = day_fraction × 100
total_new_minutes = day_fraction × 10000
total_new_seconds = day_fraction × 1000000
We display whole hours, then the remaining minutes, seconds and hundredths. Half a day is 050.000.000.000. The final unit is a “hundredth”; a millisecond means one thousandth of a second.
04 · Months and leap days
The year number stays the same, and the year begins on 1 January in the selected zone. We rearrange only the days within months.
| Year | Month 1 | Months 2–12 | Month 13 | Total |
|---|---|---|---|---|
| Ordinary | 28 days | 28 each | 29 days | 365 |
| Leap | 29 days | 28 each | 29 days | 366 |
2026.011.001 is year 2026, month 11, day 1: 8 October 2026 Gregorian. The final date of the year is 013.029, corresponding to 31 December.
In leap years, the extra day in the first month is 001.029, corresponding to 29 January. That is our chosen position for the day, not Gregorian 29 February. Every real day is still represented exactly once.
except years divisible by 100 but not by 400
Years 2000 and 2400 are leap years; 1900 and 2100 are not. The same mathematical rule extends into the past. Version 1.0 kept extra days outside months; the current version includes them within months.
05 · The week never resets
Our starting point is 1 January 0001 = Monday in the proleptic Gregorian calendar. Each subsequent day advances the weekday by one, including both extra days.
If a year ends on Friday, the next starts on Saturday. For example, 2021.013.029 is Friday and 2022.001.001 is Saturday. An ordinary year shifts the next year’s starting weekday by one; a leap year shifts it by two.
Calendar columns run MON–SUN. Empty cells before a month’s first day align it with its weekday. A 28-day month may occupy more than four displayed rows when it starts in the middle of a week.
06 · Why are there different time zones?
The server sends a single timestamp for an instant. The zone determines which local date and time represent that instant. It neither adjusts the server clock nor changes the rate at which time passes.
| Choice | Behavior | Local day length |
|---|---|---|
| UTC | No offset from the base UTC timestamp. | 24 hours in the application’s model |
| UTC+01 | Always one conventional hour ahead of UTC. Default; matches Berlin’s winter offset. | 24 hours |
| UTC+02 | Always two conventional hours ahead of UTC. Matches Berlin’s summer offset. | 24 hours |
| Europe/Berlin | The browser applies its known daylight saving rules. | 23 or 25 hours at a clock change; otherwise 24 |
Berlin mode skips or repeats part of the displayed day when the offset changes. Choose a fixed zone for equal-length days. The ATLAS stardate always uses UTC, regardless of the other clocks’ zone, so its hours may differ from the large local clock.
The zone is saved in your browser under atlas-clock-zone. The history converter treats its entered date and time separately; it does not reconstruct historical local time zones.
07 · Historical dates and year zero
On the history page, choose the source calendar first, then the year-numbering convention. Traditional numbering has no year 0: 1 BCE is followed by 1 CE. Astronomical numbering calls that preceding year 0. This does not establish the year of Jesus’s birth. [2]
| Historical label | Astronomical year |
|---|---|
| 2 BCE | −1 |
| 1 BCE | 0 |
| 1 CE | 1 |
13 July 1369 is day 194 of the source year, meaning 193 days have elapsed since its start. The conversion depends on the source calendar:
| Input | Gregorian date of the same day | Personal date |
|---|---|---|
| 13 July 1369 Gregorian | 13 July 1369 | 1369.007.026 |
| 13 July 1369 Julian | 21 July 1369 | 1369.008.006 |
We do not convert the day-of-year number alone: the two calendars also start their years on different actual days. First we find the same continuous day, then label it in the target calendar.
In countries that adopted the 1582 reform then, Thursday 4 October Julian was followed by Friday 15 October Gregorian. Labels changed; real days and weekdays did not disappear. Other countries switched later. [1]
The tool applies the chosen rule to every year. It does not establish local reform dates, historical year starts, source authenticity or early Roman irregularities. For old events, check the country, source and whether the date has already been converted.
Time is optional; unknown time remains unknown. If entered, its units are converted within the same time basis, without an automatic historical-zone conversion. Save an event with its name and a source note.
08 · Every day has a number: JDN and our counter
Day counting removes the need to add up varying month lengths when subtracting dates. In this application, 1 January 0001 is day 0, the next day is 1 and the preceding day is −1.
| Gregorian date | Our whole-day number | Civil-date JDN label |
|---|---|---|
| 1 January 0001 | 0 | 1721426 |
| 13 July 1369 | 499845 | 2221271 |
| 26 April 1985 | 724756 | 2446182 |
| 8 October 2026 | 739896 | 2461322 |
739896 − 724756 = 15140 days
JDN and our counter use different epochs. The astronomical Julian Date (JD), including its day fraction, traditionally changes its integer part at noon; our stardate starts each day at midnight UTC. Do not confuse a civil-date JDN label with a precise JD instant. [1]
739896 means that many whole days have elapsed since the epoch. This is not an ordinal count starting at one. For ancient dates, a calendar day number is well-defined under the chosen rule, but it does not by itself establish a physically precise event time.
09 · ATLAS stardate
The stardate joins a continuous day number to a fraction of a day. It appears on the main and annual pages. It always uses UTC, so the same instant produces the same number on devices with synchronized clocks.
739896 + 73/100 + 69/10000 + 73/1000000
= 739896.736973 days
Dots between fields are separators. Each time group is padded to three digits for appearance, but represents 0–99 and occupies two digits in the day fraction. The mathematical number is 739896.736973.
Subtract two numbers to find the difference in days; multiply by 86,400 for conventional seconds or 1,000,000 for new seconds. A difference of 0.5 means 12 conventional hours.
Six decimal places provide steps of one new second, or 0.0864 conventional seconds. The display is rounded down to that step; this small difference does not accumulate from day to day. Negative dates retain the correct sign: day −1 plus half a day is −0.5.
This is our own format inspired by stardates. It is not an official Star Trek convention, a measure of Earth’s orbital position or a continuous atomic time scale such as TAI that counts leap-second intervals.
10 · Two analog ways to read time
Both dials have zero at the top, major marks 0–9, small divisions and clockwise movement. The day still lasts 100 new hours.
Five hands: one for each digit
On the first analog page, green shows hour tens, blue hour units, gold minute tens, purple minute units and red seconds. At 57:24 the first four point exactly to 5, 7, 2 and 4. These digit hands step between marks while the second hand sweeps.
Three hands: a complete value on one scale
On the second analog page, green shows hours, gold minutes and red seconds. Each major mark means ten units: 5 means 50. At 57:24:12 the hour hand is just after small division 57, the minute hand just after 24, and the second hand at 12. Smaller units move the larger hands smoothly.
| Hand on the three-hand clock | One revolution | Conventional duration |
|---|---|---|
| Hour | 100 new hours | 24 hours |
| Minute | 100 new minutes | 14 min 24 s |
| Second | 100 new seconds | 8.64 s |
“Example 57:24” freezes the display at 57:24:12; “Live” restores current time. Click a legend entry to highlight a hand; click again to restore all hands. You can hide the second hand. The supporting digital readout is in a collapsed section below the settings.
11 · How does the clock know the time?
- Atlas’s operating system maintains its system clock. Synchronization to a time source is configured on the host.
- The Python server returns current Unix milliseconds at
/api/time, usingtime.time_ns() // 1000000. The container does not set the host’s clock. - The browser starts with its own clock using
Date.now(), so the display starts at the current time immediately. - Three server samples: it measures each request/response interval and picks the fastest sample. The server timestamp is anchored to the midpoint of that interval.
- Between synchronizations it uses
performance.now()to calculate elapsed time, without counting rendered frames. - Synchronization repeats every 60 seconds and when a hidden tab becomes visible again. On connection failure, a fallback status appears and the clock continues from its current anchor.
midpoint = (request_start + request_end) / 2
time_now = server_time + performance.now() − midpoint
RTT is the whole request/response duration, including some processing. Half the RTT is a rough estimate of one-way delay. The network may be asymmetric, so this is not a precise one-way latency measurement.
Check the connection to Atlas
This is a separate, on-demand check. It does not change settings or the time on other pages.
- Lowest RTT
- Not measured
- RTT / 2 — rough estimate
- Not measured
- Server − this device
- Not measured
- Server UTC timestamp
- Not measured
A difference between device and server does not tell us which clock is correct. That requires an independent, reliable time source.
12 · How accurate is it?
Decimal division introduces no cumulative time loss of its own. We change the units of the same time data. Overall accuracy depends on Atlas’s clock, its synchronization, the network and when the screen refreshes.
| Type of difference | What we know |
|---|---|
| 24/60/60 to 100/100/100 | Mathematically the same interval. No fixed daily error is added. |
| Atlas system-clock error | Not measured against an independent source in this project. |
| Network delay | We measure RTT and use the interval midpoint; asymmetry and processing remain possible error sources. |
| Screen refresh | The digital view targets roughly 30 updates/s, analog up to about 60; the device, tab or screen may be slower. |
| Stardate truncation | Less than 0.0864 s from the display step alone, in addition to other errors. |
| The main clock’s final group | A hundredth is 0.864 ms, faster than the screen. Skipped digits do not mean lost time. |
Clock accuracy and calendar accuracy are different
Our calendar follows the Gregorian rule, averaging 365.2425 days per year. The mean tropical year, following the seasons, is approximately 365.2422 days. The sidereal year, an orbit relative to distant stars, is approximately 365.25636 days. [3] [4]
| Our average calendar compared with… | Per day | Over 28 days | Per average year |
|---|---|---|---|
| The seasonal year | ≈ 0.071 s | ≈ 1.99 s | ≈ 26 s longer |
| The sidereal orbit | ≈ 3.28 s | ≈ 91.8 s | ≈ 19 min 58 s shorter |
These figures follow from the approximate year lengths above and are themselves approximate. The day and 28-day columns distribute the average evenly. They are not daily hand drift; the actual calendar consists of whole days and occasional leap adjustments.
Sidereal difference: (365.25636 − 365.2425) × 86400 ≈ 1197.50 s/year
Earth’s rotation on its axis and its orbit around the Sun are different. Rotation is not perfectly uniform. UTC is an atomic time scale adjusted in relation to Earth’s rotation; our application follows the host’s Unix clock. It does not calculate Earth’s orbital position or separately count leap seconds. [5]
13 · What is it built with?
The application was written through this collaboration with Codex as source files. It was not made in a dedicated clock-design program. You can edit it in a text editor such as VS Code.
| Technology | Role |
|---|---|
| Python 3 | Standard-library HTTP server, pages, time and health endpoint. Docker image: python:3.13-alpine. |
| HTML + CSS | Structure, text, colors, layout and mobile adaptation. |
| JavaScript ES modules | Math, calendars, animation, synchronization and browser interactions. |
| SVG | Vector dials, divisions and hands. Angles change through the transform attribute. |
| Docker + Compose | Packaging and running the service on Atlas. |
| localStorage + JSON | Zone and event storage in the browser, with event import/export. |
| Language preference cookie | English / Serbian choice. Static page translations and shared bilingual interface messages. |
There is no server database or npm build step. Once the Docker image is downloaded, display and calculations work on your private network without an external internet service. Host clock synchronization depends on its own configuration.
14 · Which file calculates what?
Everything is inside the project root (the cloned repository). Paths below are relative to it.
| File / function | Responsibility |
|---|---|
server.py → Handler.do_GET() | Allowed HTTP routes, language selection and pages. /api/time returns unix_ms; /health returns {"ok":true}. |
web/clock.mjs → decimalTime() | Milliseconds since midnight to new hours, minutes, seconds and hundredths. |
wallParts() | Date and time in the selected zone from a timestamp. |
customDate(), gregorianDate(), monthLength(), isLeap(), weekday() | 13-month arrangement, conversion in both directions, month lengths, leap years and continuous weekdays. |
web/app.mjs → syncTime(), render(), frame() | Main/annual clock synchronization, RTT, time anchor and screen updates. |
web/year.mjsweb/calendar-ui.mjs | Annual calendar, date selection, weekday columns and blank cells before each month’s first day. |
web/history-core.mjs → toDay(), fromDay(), convert() | Conversion through an integer day number, calendars, BCE dates and optional time. |
web/history.mjs | History form, results, event storage and JSON import/export. |
web/stardate.mjs → stardate(), fromDayAndMs() | UTC day count and mathematical decimal notation. Formatting uses integer microdays with BigInt. |
web/analog-core.mjs → analogHands() | Five angles: four digits × 36°, plus a circular second-hand angle. |
web/analog3-core.mjs → analogHands() | Three angles from the elapsed fraction of the day, new hour and new minute. |
web/analog.mjsweb/analog3.mjs | sync(), rendering, examples, legend, zone and full screen. |
web/help.html, help.css, help.mjs | This guide, printing and separate RTT diagnostics. |
web/en/*.htmlweb/i18n.mjs | English page text, shared language selection, bilingual messages, weekday/era labels and translated validation errors. Serbian pages are in web/*.html. |
Dockerfile, compose.yaml, start.sh | Image, port, restart policy, health check and startup. |
tests/*.test.mjstests/server_test.py | Calculation checks, language checks and local HTTP service checks. |
Three-hand formulas
hour: m / 86400000 × 360°
minute: (m modulo 864000) / 864000 × 360°
second: (m modulo 8640) / 8640 × 360°
The main clock uses now = anchorEpoch + performance.now() − anchorPerf. Analog modules use the same principle with anchor and anchorPerf. The timestamp determines time; frames only render its current state.
15 · Running, updating and data
The default external port is 6140, the container port is 8080, the Compose project is atlas-time and the service is clock.
Install and update
You need Docker Engine and Docker Compose v2. The code comes from a Git repository; updating means pulling again:
git clone https://github.com/neoartdoo/ATLAS-Time.git
cd ATLAS-Time
cp .env.example .env # optional: port and address
bash start.sh
# update later:
git pull
bash start.shstart.sh runs docker compose up -d --build. Use appropriate host permissions if your account lacks Docker access. .env is not in the repository, so updates never touch it. Without Docker: python3 server.py (port 8080, or the PORT variable).
Check the service and time
docker compose ps
docker compose logs --tail=80
timedatectl status
systemctl is-enabled dockertimedatectl status shows host synchronization status. “Synchronized” is not a numerical error measurement in milliseconds. For a measured offset, inspect the actual time service and its reference source.
The application does not set any clock and does not query time servers itself: it shows the time of the computer that runs the server. Keep that computer synchronised with any NTP server (for example pool.ntp.org or time.windows.com). Windows: w32tm /query /status, and w32tm /resync (as administrator) requests a new synchronisation. Linux: timedatectl status should report the system clock as synchronised. On Windows, the Docker Desktop virtual machine’s clock can lag after sleep or hibernation; restarting Docker Desktop resynchronises it.
Restart with docker compose restart clock. After source changes, rebuild using bash start.sh. The restart: unless-stopped policy brings the container back when Docker starts, unless you stopped the service manually.
Port and network
In .env, set CLOCK_PORT=6142 for another free port, or CLOCK_BIND=0.0.0.0 to make the clock reachable from your whole LAN (or a specific host address). The default is 127.0.0.1:6140, this computer only. CLOCK_EMBED_ORIGINS lists the origins allowed to embed the compact view /?embed=1 in an iframe. This HTTP interface has no login and is intended for a private network.
Where are events saved?
Events live in browser localStorage under atlas-history-events-v1, not in the container. A different browser, port or address can show a different list. A folder backup does not include these entries: use Export JSON on the history page. Import adds entries to the existing list, up to 500 events. The v1.8 language update preserves the existing storage keys and accepts older exports.
16 · Common questions
Why does the clock not start at zero?
It reads the current timestamp rather than time since the container started. Restarting the application does not reset the clock or calendar.
Why do two clocks show different times?
Check whether you are comparing decimal or conventional units, whether both clocks use the same zone and whether the paused example is active. The stardate always uses UTC; Berlin uses UTC+02 in summer.
Does fixed UTC+01 match Berlin all year?
No. It matches Berlin’s winter offset and is one conventional hour behind in summer. Europe/Berlin follows seasonal changes, including 23/25-hour days.
Why are the final digits skipped?
Hundredths of new seconds are faster than the screen refresh. Time is still calculated from the timestamp; those intervals are not lost.
Why does an old date produce different results?
Check its source calendar and era. Gregorian 13 July and Julian 13 July in the same year are different actual days. Astronomical year 0 means 1 BCE.
Does year 0001 reflect the calendar used locally at the time?
It is a mathematical extension of our rules backwards. We do not claim this calendar was in use in any particular country then.
What if the status says “Server unavailable”?
The clock uses its fallback anchor. Check the network, address, port and docker compose ps, then click sync. The /health endpoint checks the service response.
Do extra decimal places provide atomic accuracy?
No. They provide finer notation for the same data. Accuracy depends on the source and measurements. Unmeasured error cannot be claimed to be zero.
Will changing the language translate my events?
No. Only the interface changes. Event names, notes and original date inputs remain your own data. Save an unfinished event before switching, since the page reloads.
17 · Sources and verification
The calculations and program descriptions follow the included source code. Astronomical conventions and approximate year lengths were checked against these sources:
- USNO — Julian Date Converter: continuous days, Julian/Gregorian dates and the 1582 reform.
- NASA — Year Dating Conventions: historical eras and astronomical year zero.
- USNO — Leap Years: leap-year rule, average Gregorian and approximate tropical years.
- NASA/JPL — Astrodynamic Parameters: sidereal year length.
- NIST — Leap Seconds FAQs: atomic time and Earth’s variable rotation.
Automated checks cover calculations, date transitions, leap years, negative years, hand angles, stardates, language selection and HTTP routes. Docker execution and visual browser checks are unavailable in the build environment. Earlier versions were run and viewed by the author on their own server; that is not a laboratory accuracy measurement.
To run the checks locally, install Python and Node.js:
node --test tests/*.test.mjs
python3 tests/server_test.pyThis guide documents v1.8. Time and calendar rules remain the same; this release adds the ATLAS Personal Time name and bilingual pages.
License: PolyForm Noncommercial 1.0.0. Free for noncommercial use; commercial use needs the author’s permission. Author: Marjan Panic.
Back to top ↑