A paran pairs local angular events
In current practitioner usage, a paran is a relationship in which two bodies reach named local angles at the same time or within a stated tolerance: rising, upper meridian transit (culmination), setting, or lower meridian transit. This is a local time-and-place question. It is not a zodiacal conjunction or any other longitude aspect. Skyscript describes the practitioner criterion as bodies becoming angular together, while Zyntara describes rotating a chart through a full 24 hours so that every body can rise, culminate, set, and reach lower culmination.
The word is conventionally treated as a shortened form of Greek paranatellonta, often glossed “rising together.” That gloss supports the older rising-alongside idea; it does not by itself prove that every historical author used the exact four-angle rule offered by a modern program. Here “paran” is therefore a labelled modern practice, with its event definition and tolerance shown in the result.
Deborah Houlding, Skyscript Glossary: Paran ↗Zyntara: Paran request ↗
Keep the sky geometry separate from the reading
Physically, Earth’s rotation carries a body across an observer’s local horizon and meridian. A rise or set is a horizon crossing; a meridian transit is the instant the body’s center crosses the observer’s north–south meridian. These are reproducible geometric event labels when the observer, ephemeris, time scale, horizon convention, and body point are declared. A body can transit while below the horizon, and a high-latitude body can lack a rise or set in the selected interval.
A symbolic statement that a paired event signifies a theme belongs to a named practitioner tradition, not to the geometry. The explorer can report event names, timestamps, separation, and selected bodies. It must not manufacture a fixed-star meaning, a personality claim, or a prediction when no sourced interpretive rule has been supplied. Atmospheric visibility is also outside this selected convention: geometric horizon crossings are not claims that an object was seen through refraction, terrain, twilight, or clouds.
U.S. Naval Observatory: Rise, Set, and Twilight Definitions ↗Skyfield: Almanac Computation — Meridian Transits ↗
The Atlas selected-window convention
Choose one of three window conventions. Fixed 24 hours begins at the exact entered local date-time, resolving a repeated clock time with its selected occurrence. Local calendar day includes the contiguous instants of the chosen date in the selected IANA zone, including missing or repeated midnight handling. Sunrise to sunrise begins at that date’s first geometric sunrise and ends at the next one within 48 hours.
All three presets use actual moving bodies, topocentric apparent positions, body centres and a geometric altitude of 0° without atmospheric refraction. They return actual rise, set and upper/lower meridian events. A skipped or fragmented civil date, or an unavailable solar boundary, produces an explicit explanation without a substitute window.
Pairing uses full event timestamps, a tolerance from 0 to 30 minutes and a half-open window: the start is included, the end excluded. At least one event must belong to the window; the other may be in the declared padding. The timeline uses the actual duration. Downloaded UTC clock durations follow JavaScript date timestamps and do not count inserted leap seconds; Julian-day fields preserve the astronomical time convention.
IANA: theory and scope of the time-zone database ↗Zyntara: day conventions and actual moving bodies ↗Swiss Ephemeris: rise and transit functions ↗
Worked synthetic example · retain the next-day timestamps
This is deliberately synthetic tool-shaped output, not an ephemeris claim for a real city or date. Suppose the location and local zone are already selected and the window begins 2031-04-18 18:00:00 +02:00. The window ends 2031-04-19 18:00:00 +02:00. With 30 minutes allowed, the event search returns Body A rising at 2031-04-18 23:53:20 +02:00 and Body B at upper transit at 2031-04-19 00:11:04 +02:00. The absolute difference is 17 minutes 44 seconds, so the pair qualifies. Both actual timestamps are retained; calling the second one “00:11 on the start date” would change the event by almost a day.
A near-end example is also valid: Body C sets at 2031-04-19 17:52:10 +02:00, inside the window, and Body D reaches lower transit at 2031-04-19 18:07:40 +02:00, in the padding after the window. Their difference is 15 minutes 30 seconds, so the pair can be shown with an “in-window: Body C set” marker. A separation of 30 minutes exactly is included; 30 minutes and one second is excluded. These examples demonstrate selection and timestamp handling only. They do not assign meanings to Bodies A–D.
Read the result as an auditable prompt
Choose the location, local start date-time, bodies, and event settings; then inspect the two full event timestamps, event kinds, elapsed separation, and whether the pair crossed midnight or used padding. Preserve those facts when exporting or comparing a second location. A different location can change the local angular-event times even when the ephemeris date is unchanged.
If you use symbolic interpretation, attach only a cited rule from the chosen fixed-star or planetary practice and keep it separate from the event record. Do not equate an Atlas daily local-event pair with an astrocartography world-line crossing: a map line represents a different spatial question, while this tool pairs angular events at one selected location and time window.
Deborah Houlding, Skyscript Glossary: Paran ↗U.S. Naval Observatory: Rise, Set, and Twilight Definitions ↗
Compare interpretation frameworks
The explorer offers three reading views. Event geometry describes the selected crossings. Ptolemy’s historical lens compares the selected bodies with the planetary qualities in Tetrabiblos I.4 and the named-star comparisons in I.9. Brady’s star-angle view shows the lifecycle category associated with the star’s angle in Zyntara’s sample report.
For example, in a Sun–Sirius pair, the historical view compares the Sun’s heating and drying qualities with Sirius’s Jupiter and lesser Mars attribution. The modern angle view follows Sirius’s event: rising gives a youth category; lower-meridian passage gives a foundational category. Changing which body rises therefore matters. A planet–planet or star–star pair receives no star–planet lifecycle category.
These are separate reading frameworks. The selected view is included in the event-reading download together with the exact events and sources. A complete natal-star reading additionally needs verified day and horizon conventions, visibility phases and star-specific delineation.
Ptolemy, Tetrabiblos I.4 and I.9 ↗Zyntara, Starlight sample report, p. 5: star angles ↗
Independent event checks and their limits
The event solver is compared with 215 independently computed Skyfield events across London, the equator and 80° north, using JPL DE421 and six Hipparcos catalogue stars. Matching tests use body-centre altitude zero, no refraction, apparent topocentric directions and actual upper/lower meridian crossings. All 260 body/angle event counts match, including missing crossings and a Moon day with two sets.
This comparison found and corrected duplicate lunar meridian estimates. Refined roots are now compared as individual physical crossings. The largest time difference in these fixtures is under 0.34 seconds, within the preset five-second test tolerance; this is a result for the sampled cases, not a universal accuracy guarantee.
The Sun, Moon, Mercury, Venus and Mars use independent centre references. Jupiter and Saturn use system-barycentre proxies, which are tracked separately. Star comparisons omit binary orbital motion and assume zero radial velocity; frozen Earth-rotation tables and grazing crossings limit wider accuracy claims.
Skyfield: almanac event search ↗ESA Hipparcos catalogue, CDS I/239 ↗JPL DE421 planetary ephemeris ↗
Word origin · etymology
Modern practitioner shortening of Greek-derived paranatellonta.
Skyscript glosses paranatellonta as “rising together.” This supports the word history and older co-rising idea. The claim that a modern paran may pair rise, upper transit, set, or lower transit is a practitioner convention, not an etymological consequence.
How we know · epistemology
Simultaneous angular-event criterion
A topocentric geometric event search can reproduce declared horizon and meridian timestamps when location, time scale, ephemeris, body point, event kinds, and tolerance are retained. Traditional symbolic meaning is separately attributed; correct event arithmetic does not validate a personal claim. Geometric 0° horizon events with no refraction are not observations of visibility through weather, terrain, twilight, or atmospheric refraction.
Deborah Houlding, Skyscript Glossary: Paran ↗Zyntara: Paran request ↗U.S. Naval Observatory: Rise, Set, and Twilight Definitions ↗
Explore it in your atlas
Connected concepts
Read alongside this entry
Terms used in this explanation
Mentioned in 4 other entries
These links connect subjects and terminology. They do not establish a shared historical origin.
Sources & provenance
Use the citations beside each section to distinguish a calculation convention, a historical teaching and an editorial example.
Find these sources across the wiki →
- Deborah Houlding, Skyscript Glossary: Paran ↗
- Zyntara: day conventions and actual moving bodies ↗
- U.S. Naval Observatory: Rise, Set, and Twilight Definitions ↗
- Skyfield: almanac event search ↗
- IANA: theory and scope of the time-zone database ↗
- Swiss Ephemeris: rise and transit functions ↗
- Ptolemy, Tetrabiblos I.4 and I.9 ↗
- Zyntara, Starlight sample report, p. 5: star angles ↗
- ESA Hipparcos catalogue, CDS I/239 ↗
- JPL DE421 planetary ephemeris ↗