Methodology version 1.0 - reviewed 8 August 2026

How ParasharaHora calculates and interprets a Kundli

Calculation and interpretation are separate stages. Astronomical positions and Vedic derived values are computed first from the supplied birth data and selected settings. AI is used afterward to explain available chart facts; it does not calculate planetary positions and cannot guarantee predictions or outcomes.

Astronomical foundation

Planetary positions are computed through Swiss Ephemeris using the project's pinned Python integration. Birth date, local birth time, timezone offset, latitude, and longitude are converted to a UTC Julian day before planetary and chart calculations are requested.

Swiss Ephemeris provides astronomical positions. It does not provide the final Parashari interpretation. Results can change when the entered time, timezone, coordinates, or calculation settings change.

Sidereal zodiac and Ayanamsha

ParasharaHora uses a sidereal zodiac. Lahiri (Chitra Paksha) is the default Ayanamsha, and the selected mode is applied before sidereal planetary and house calculations.

  • Lahiri (Chitra Paksha) - default
  • Raman
  • Krishnamurti (KP)
  • Fagan-Bradley
  • Yukteshwar
  • True Chitra

Two calculators can disagree even when both use Swiss Ephemeris if they use different Ayanamshas, coordinates, time handling, or rounding.

Rahu and Ketu node options

The birth form supports True Node and Mean Node. True Node is the default. The chosen setting determines the longitude used for Rahu; Ketu is placed opposite Rahu. The selected node setting is stored with saved chart data so a restored chart can be calculated consistently.

True Node follows the oscillating lunar-node position. Mean Node uses an averaged path. Neither option should be mixed silently when comparing two charts.

Vimshottari Dasha rules

The Vimshottari sequence is Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, and Mercury, totalling 120 years. The birth Mahadasha is selected from the Moon's Nakshatra.

The remaining balance at birth is calculated from the fraction of that Nakshatra still untravelled by the Moon. Period lengths use a sidereal year of 365.25636 days. The timeline can be expanded through Mahadasha, Antardasha, Pratyantardasha, Sookshma, and Prana levels.

Dasha dates are mathematical timing periods. Interpretation also considers house lordship, placement, dignity, aspects, relevant Vargas, and current transits.

Parashari Vargas

Divisional charts assign each sidereal planetary longitude to a divisional sign using chart-specific Parashari rules. The principal Shodasavarga set currently exposed by the report engine is:

  • D1 Rasi
  • D2 Hora
  • D3 Drekkana
  • D4 Chaturthamsha
  • D7 Saptamsha
  • D9 Navamsha
  • D10 Dashamsha
  • D12 Dwadashamsha
  • D16 Shodashamsha
  • D20 Vimshamsha
  • D24 Chaturvimshamsha
  • D27 Saptavimshamsha
  • D30 Trimshamsha
  • D40 Khavedamsha
  • D45 Akshavedamsha
  • D60 Shashtiamsha

Higher divisions are especially sensitive to birth-time accuracy. A D9, D10, or D60 chart should not be treated as dependable when the recorded birth time is uncertain or near a divisional boundary.

Shadbala

Shadbala is calculated for the seven visible planets and aggregates six strength groups in Virupas. Rahu and Ketu are not assigned a standard six-fold total in this implementation.

Sthana Bala:
positional strength, including dignity and divisional support.
Dig Bala:
directional strength relative to the chart.
Kala Bala:
time-related strength factors.
Cheshta Bala:
motional strength for applicable planets.
Naisargika Bala:
natural strength assigned to each planet.
Drik Bala:
strength modified by planetary aspects.

Totals are compared with the implementation's planet-specific minimum requirements and displayed as relative strength percentages. A high percentage means comparatively strong calculated Bala; it does not by itself mean that every result of that planet will be favourable.

Policy & Support

How chart factors are compared

For a focused question or report, the interpretation layer is instructed to combine the relevant D1 house, occupants, received aspects, the house lord's sign, house and dignity, the lord's dispositor when available, relevant Yogas, active Dasha periods, matching Varga facts, and current transits. It should not make a conclusion from a single Karaka or one isolated placement.

1. Computed facts

Positions, houses, Vargas, Dashas, Bala values, Yogas, and transit data available for the selected chart.

2. Topic selection

Career emphasises the 10th house and D10; relationships emphasise the 7th house and D9; other topics select their corresponding houses and Vargas.

3. AI explanation

AI organises supplied facts into natural language. It may still omit context, overstate a conclusion, or produce an error, so important decisions require independent judgment.

Comparing results with another calculator

A meaningful comparison must use the same date, exact local time, timezone and daylight-saving treatment, geographic coordinates, Ayanamsha, node type, zodiac mode, Varga convention, and rounding precision. Compare raw sidereal longitudes first, then signs and houses, and only then derived tables or interpretations.

  1. 1. Confirm the same UTC instant and coordinates.
  2. 2. Match Ayanamsha and True/Mean Node settings.
  3. 3. Compare planetary longitude before chart labels.
  4. 4. Check Varga and Dasha conventions separately.
  5. 5. Record the exact difference rather than calling either output perfect.
  6. 6. Treat interpretive disagreement separately from numerical disagreement.

Review the experience yourself

Generate the free guest preview, inspect the selected settings, and decide whether you want to save or purchase deeper interpretation.