Caelus3,462 checksGitHubv0.25.0MIT
Instrument I-01

Sky dating

Search historical dates for intervals matching a partial sky description. For example, you can date an undated horoscope or literary passage by matching planetary signs, lunar phases, or first and last visibility events from a specific location across up to 6,000 years.

INConstraints4 set

Span: 801 BCE to 2 BCE. Years use astronomical numbering (0 = 1 BCE, -409 = 410 BCE). The four planetary signs quoted from the oldest surviving Babylonian horoscope tablet, dated by A. Sachs to April 29, 410 BCE.

OUTWindows that fit
0windows fit801 BCE to 2 BCE
caelus 0.25.0, embedded tier
800 BCE600 BCE400 BCE200 BCE
TBLMatchespositions at the middle of each window

No window fits every constraint in this span.

CUTFilter funnel by constraintslowest body first
ConstraintWindowsDays
TSTypeScript example
import { Engine, dateSky, julianDay, calendarDate } from "caelus";
import { embeddedData } from "caelus/data-embedded";

const engine = new Engine(embeddedData);

const { windows, funnel } = dateSky(engine, [
  { body: "saturn", sign: "Cancer" },
  { body: "jupiter", sign: "Pisces" },
  { body: "mars", sign: "Gemini" },
  { body: "venus", sign: "Taurus" },
], julianDay(-800, 1, 1, 0, 0, 0, "julian"), julianDay(0, 1, 1, 0, 0, 0, "julian"));

windows.map((w) => calendarDate(w.start, "julian"));
RETReturn valueUT Julian Days
[
]
M-1Search order and pruning

The solver evaluates constraints from the slowest-moving body to the fastest. It first identifies windows where Saturn occupies its target sign, searches only those intervals for Jupiter, and continues down to the Moon. Each row in the funnel shows the candidates remaining after applying that filter. Because first and last visibility constraints are discrete events rather than continuous curves, they run last inside each surviving window. Use the First Visibility instrument to inspect individual events in detail, or read First and last visibility for the underlying atmospheric model.

M-2Ephemeris tier

These results run client-side on the bundled embedded tier. It agrees with the full ephemeris packs within 0.02° after 1 CE and within 0.09° back to 1000 BCE (at 3000 BCE Saturn differs by up to 0.7°). For both horoscope presets, this finds the exact same date windows, with boundary edges shifted by about 6 minutes for the Babylonian tablet and 27 minutes for Hadrian's horoscope. Switch Data to Full packs to download exact JPL fits in the browser.

M-3Calendars and scope

Dates before October 15, 1582 use the Julian calendar. Each output window marks a continuous interval of Universal Time during which all constraints hold simultaneously, so queries including the Moon typically span two or three days. Visibility constraints span whole local calendar days at the observer's location, running from the clearer-sky earliest date through the hazier-sky latest date. When a visibility constraint is active, the Window column displays local calendar days at that location while Opens shows the corresponding Universal Time. Signs for the two horoscope presets reflect standard secondary translations rather than newly verified critical editions.