Personal Astrology Calendar Calculation Layer Validated
The calculation and classification infrastructure of the Numji Personal Astrology Calendar was examined through comparative and independent software controls across 250 test cases generated from different birth dates, analysis dates, date ranges, geographical locations, time zones, and orb options. A total of 26,029 results were checked.
Local time–UTC conversions, transit planetary positions, natal house placements, Transit–Natal major aspects, orb values, applying–separating differentiation, period merging, exact time of culmination, effect type, significance level, life domain, and repeat consistency passed the designated controls. No failed or erroneous results were found.
Validated Personal Astrology Calendar calculations
The primary calculation groups forming the astronomical and rule-based foundation of the personal calendar result.
TIME AND PLANETARY POSITIONS
The UTC equivalents of birth and analysis times, along with transit planetary longitudes, daily speeds, and direct/retrograde motion statuses, were directly compared with engine results.
NATAL HOUSE PLACEMENTS
The house placements of transit planets in the natal chart were recalculated and checked against the twelve house cusps.
TRANSIT–NATAL ASPECTS
Conjunction, sextile, square, trine, and opposition aspects underwent independent geometric controls at the level of true angular distance, orb, and applying–separating status.
PERIOD AND CLASSIFICATION
Merging the same active effect into a single period throughout its duration; the consistency of exact culmination times alongside supportive, challenging, and intensifying effect types, significance levels, and life domains was examined.
Validation results
The general outcome of each tested calculation and behavior group.
| Control Group | Scope | Evaluation | Result |
|---|---|---|---|
| Local time and UTC conversion | Birth and analysis moments | Compatible with expected UTC values | Passed |
| Transit body data | Longitude, speed, and motion direction | Compatible with direct engine results | Passed |
| Natal house placements | 1st–12th house distribution of transits | Compatible with house cusps | Passed |
| Transit–Natal aspects | Aspect type, orb, and motion status | Compatible with independent geometry | Passed |
| Period merging and daily summaries | Start, end, and exact culmination moments | Compatible with defined time rules | Passed |
| Classification and output protections | Effect type, significance level, and life domain | Compatible with defined rules | Passed |
| Repeatability and orb monotonicity | Same request and tight/wide orb relationship | Consistent and deterministic | Passed |
| Input and high-latitude protections | Invalid inputs and Reykjavík regression | Expected behavior verified | Passed |
| Total | 250 cases · 26,029 comparisons | 26,029 compatible · 0 errors | Passed |
High-latitude regression
The boundary scenario captured during validation has been included in the permanent test scope.
REYKJAVÍK CASE
The generation of Placidus house cusps for Reykjavík at 64.1466° north latitude was additionally tested. The scenario where the valid root could fall outside the initial search interval was successfully resolved.
BACKWARD COMPATIBILITY
The calculation path for previously successful Placidus cases has been preserved; the expanded search is activated only when the initial phase fails to produce results.
Test methodology
Time, location, date range, orb, and boundary behaviors were diversified to ensure the results do not depend on a single individual or date.
SCOPE
- 250 distinct test cases
- Dates between 1900–2100
- A wide range of latitudes, longitudes, and UTC offsets
- A wide range of date spans, orb settings, and Moon transit options
- Total of 26,029 comparisons
INDEPENDENT CONTROLS
- Recalculation of aspect and orb geometry
- Re-finding house placements from house cusps
- Ensuring tight orb results fall within wide orb results
- Ensuring the same input produces the same result
INPUT PROTECTIONS
Checked that invalid latitude, longitude, orb, and date range values are rejected, while supported inputs produce the expected result structure.
PRODUCTION-INDEPENDENT TEST
The validation tool was executed as a separate console application. Results were recorded using JSON, Markdown, and CSV reports.
What does this result mean for the user and the astrologer?
The time conversions, transit degrees, natal house placements, aspects, transit periods, exact culmination times, and effect classifications utilized by the Personal Astrology Calendar have undergone an extensive software validation set. This demonstrates that the presented calendar results consistently rely on defined calculation rules.