JH 7.4 Features: Quantitative Aspect Evaluation (Any Div×Any Div), Stationary Transit (Planet Speed=0 = Max Power), Antardasha Ordering Variants; Vimshottari Dasha Progression: ONE Physical Zodiac (No Separate Navamsa Zodiac), Progressed Divisional Longitude + Transit Correlation = Events

Jagannatha Hora 7.4 — New Software Features

Feature 1: Planetary Aspect Evaluation

• In the Longitudes window, choose "Planetary Aspect Evaluation". Pick the divisional chart of the aspecting planets and the divisional chart of the aspected positions. The two can differ.
• "Force natal chart" makes it use the natal chart even when a Tithi Pravesha, transit or progression chart is on screen.
• It lists the aspects of the 8 planets, Sun to Rahu, as percentages. Sun to Saturn follow Parashara's formulas strictly. Rahu is an extension Parashara did not give: 5th, 7th, 9th and 2nd aspects, counted anti-clockwise.
• Aspected positions listed: the house cusps (lagna, 2nd from lagna…), the planets, the special lagnas (Bhava, Hora, Ghati and others), the upagrahas, a few sphutas, Arudha Lagna and every arudha with the houses from each (AL, 2nd from AL … A10, 2nd from A10 …), UL and 2nd from UL, Varnadas, and user-defined special points.
• The arudha rows appear only with longitude-based arudhas. A sign-based arudha has no longitude, so an aspect on it is not defined.

How to use it: take A10 and the 2nd from A10 in D10 (Parashara stresses the 2nd and the 7th from an arudha). See who aspects them strongly. In the chart on screen Saturn aspected the 2nd from A10 strongly and Jupiter aspected A10. Then ask what that planet stands for in the Dasamsa. The same can be done for transits — who aspects A10 in Dasamsa, A5 in Siddhamsa, A8 in Vimsamsa.

• The teacher's first pick, D24 planets on D10 positions, he called meaningless — it was only to show the menu.
• The aspects of Rasi planets on D9, D10 and other divisional positions are the important ones.

Feature 2: Antardasha Ordering in Nakshatra Dashas

With mahadashas A, B, C, D, E, F, G, H and F running:

• The software now lets you choose the scheme for each dasha, to test which works.
• The teacher has not researched this. For most of these dashas he just uses the Vimshottari-style order.
• Ashtottari he programmed to end with the mahadasha lord, following the tradition he was taught. People from other traditions complain.

"God knows who is right, because I haven't really made a lot of accurate predictions using Ashtottari."

Feature 3: Stationary Transit

• Make a chart for a date, go to the Mundane tab, press the stationary transit button, pick a planet and "before" or "after".
• Sun and Moon are not offered: they never become stationary. Rahu and Ketu work only with true nodes; mean nodes always move backwards.
• Example shown: Jupiter was stationary on October 12 at 23:28:39 Boston time at 23°11'30" Capricorn, speed 0.000° per day.
• The theory: when a planet turns from direct to retrograde or back, it is absolutely still — like someone who can focus very well. Such a planet is very powerful in transit. Whatever planet or point it conjoins or aspects in any divisional chart, it triggers something important relating to that.

"Not all events happen around stationary transits, but sometimes some really big events happen around stationary transits."

"You can't rely on this to make predictions, but you can get into the ballpark using this, and then you can use other techniques to fine-tune."

• Take the stationary time plus or minus 2–3 weeks; the planet stays very close to that longitude. Open "All divisional longitudes" of the natal chart and see whether any divisional longitude is within a couple of degrees of it. In the chart tried in class nothing stood out.

Longitude-Based Arudha Padas

• The other recent research (padamsa transit): when a transit planet closely conjoins or aspects the divisional longitude of an arudha pada, an event of that pada can come — more so when that planet has a similar signification in the natal chart.
• Turn it on in Preferences: "find arudha padas of houses using exact longitudes". Arudhas can be taken from lagna, Moon, Venus and other planets.
• Marriage: UL from Venus or from lagna. Career: A10 from lagna and from Mercury. Political power: A5 from the Sun or lagna, in D10 or D5.
• These longitudes are exactly as sensitive to birth time as the lagna of that divisional chart. If lagna moves back 1°, Arudha Lagna moves forward 1°. The higher the division, the harder.

---

Vimshottari Dasha Progression — Principle

How a planet is progressed

Shown on a Cancer-lagna chart running Saturn mahadasha, Mercury antardasha:

• The Moon was born in Krittika, so the first dasha, Sun dasha, corresponds to Krittika. All through it the progressed Moon is in Krittika.
• During the 10 years of Moon dasha the progressed Moon crosses Rohini. Then Mrigashira in Mars dasha, and so on.
• Saturn dasha began on 9 September 2005: that day the progressed Moon entered Pushya, at 3°20' Cancer.
• One mahadasha = one nakshatra. One antardasha = one-ninth of a nakshatra. Saturn antardasha ended on 12 September 2008, so one-ninth of 13°20' was done. In Mercury antardasha the 6th pratyantardasha was running, so five-ninths of that ninth was done. Go on down to the deha-antardasha and the position is fixed within a few arc-seconds; inside the last level the division is linear.

Equal arcs, unequal times

• Krishnamurti divides a nakshatra into 9 unequal subs, in proportion to the antardasha lengths (Saturn 19, Mercury 17, Ketu 7, Venus 20).
• The teacher does not. Mahadashas of 20 years and 7 years both cover the same 13°20'. Bharani is not three times as long as Krittika.
• If the nakshatras are equal in length though their dashas differ in time, the antardasha portions should be equal too.

"So my philosophy is the same thing that you do for mahadasha."

• So each antardasha covers the same arc in a different time. The progressed planet moves at a non-uniform speed, set by the dasha, antardasha and lower periods running. (The recording garbles the name of the ratio he cites.)

Sensitivity to birth time

• The error in the progressed position equals the error in the natal position. The Moon moves about half a degree an hour, so a birth time good to 1 minute gives the Moon within half an arc-minute — still only about 20 arc-minutes in D-20 or D-24.

Any planet, not only the Moon

• The teacher first looked at transits against the progressed Moon at important events and found nothing of interest.
• Parashara does not say these dashas run from the Moon. He speaks only of the nakshatra occupied at birth — by whom, he does not say. (One classic names lagna or Moon.)

"It doesn't necessarily have to be Moon. So you can progress Venus, you can progress Jupiter."

• Same chart: natal Mars in Ashlesha, so Mars's first dasha, Mercury, corresponds to Ashlesha. Rahu dasha was running, about the first sixth of it, so progressed Mars was early in Swati: 8°24' Libra (Swati starts at 6°40' Libra). The progressed Moon stood 2°27' into Pushya.
• Rahu and Ketu: the only ones without consistent results. Maybe they must go backwards. He does not use progressed Rahu or Ketu. He does use transit Rahu and Ketu aspecting the progressed positions.
• The software also computes progressions for Yogini and two other dashas. He has studied only one of them and added the rest because they can be calculated.

In the software

• Open the natal chart → Miscellany → Progressions → enter the date of the event → "Vimshottari Dasha Progression".
• The warning it shows matters: only the physical and divisional longitudes of lagna and the 9 planets are valid in a progression chart. It is not a chart of any date. Mandi, Gulika, sphutas and the rest shown with it are fake and must be ignored.

The technique

1. Take the lord of the relevant house in the natal Rasi chart: 7th lord for marriage, 5th lord for childbirth, 6th or 8th lord for an accident, 10th lord for career. For political power the teacher took the 10th lord from Ghati Lagna.
2. Find its progressed longitude for the date of the event.
3. Find the divisional longitude of that progressed position in the chart of the matter: D9 marriage, D7 children, D10 career, D30 evils, D16 vehicles, D5 political power.
4. In the Rasi transits of that date, see who conjoins or aspects that longitude closely — within a couple of degrees, 4° at the most.
5. Check that planet's role in the natal divisional chart for the same matter.

First demonstration: progressed Mars at 8°24' Libra is at 24°05' Sagittarius in D10. Rahu was transiting very close to it. Mars is the natal 10th lord (and 5th lord) for Cancer lagna, so see what Rahu stands for in the natal Dasamsa. If he gives raja yoga there, expect that.

Predicting, when the event is not known

A student asked how to use it forward. Take the key planet — 5th, 7th, 10th lord in Rasi — progress it, and watch who comes into close contact and what that planet stands for natally. Or start from the important planets of the natal divisional chart and see when they closely conjoin or aspect the progressed longitude.

"You cannot predict up to the day, but you can find the ballpark."

• The contact need not be within minutes. 2° away is still significant; statistically, within 3–4° is significant.
• It is one tool among many: Tithi Pravesha, Tithi Ashtottari, padamsa transits.

---

Divisional Longitudes — One Zodiac

The theme behind all the recent research is the divisional longitude. People have long thought a divisional chart has no longitudes.

"There is nothing called Navamsa chart. There is no special Navamsa zodiac. If there is Aries or Taurus in Navamsa, it is the same Aries, Taurus that is physically there."

• There is one chart of 12 rasis. In it sit the physical planets (the Rasi positions), and also Navamsa Moon, Navamsa Mars, Dasamsa Mercury, AL, A2, A3, the A2 of D10, the A3 of Navamsa — all as points. You can plot them all in one chart.
• Navamsa Mars is an abstract, mathematical point, not a physical one. But that point exists in the physical zodiac, so it has a longitude.
• Progressed Mars's Navamsa position at 4°42' Aquarius and transit Saturn at 4°32' Aquarius are in the same Aquarius.

"They are not two different Aquariuses like some people may think."

• When a planet touches one of these points it may trigger something. That important events fall so close to such transits in so many charts is not chance.
• Natal divisional longitudes against transit divisional longitudes gave nothing consistent. Once the progressed positions were taken, things stood up.

"Once you turn the key, suddenly the room has so much light."

Why it matters

• The criteria are objective: a longitude within 2° of another longitude. A computer can check them, and could even graph the likelihood of an event for a house.
• Some judgment remains — which planet matters for the matter in this chart. Ten astrologers asked to pick two or three planets will mostly pick the same ones.
• The teacher sees a way, some years on, to take on skeptics with something 80% automatic and 20% human.
• What is shown so far he calls the tip of the iceberg.

---

Practice, Settings and Rectification

Practice

• The article has 28 examples; four or five were done in class. Enter the data and replicate the rest. Then test your own events — going abroad, marriage, a promotion.
• Bring the examples where things do not add up.
• Three recent techniques rest on divisional longitudes and are to be worked on: padamsa transits, stationary transits, and this one.

"My preferences" in Jagannatha Hora

A student asked about the button in the last Preferences tab. It sets what the teacher uses in his articles: true nodes, geocentric true positions, the ayanamsa without any offset, sunrise taken when the centre of the Sun is truly on the eastern horizon, mixed chara karakas (7 or 8), and arudha padas from exact longitudes.

• The program defaults stay as they are — some are his, some are Sanjay Rath's, some are what the world is used to. People want the same output from every version.
• He does not stand by every one of his own settings; some will change.
• He has offered to add a preset for Sanjay Rath's recommended options, and for any other scholar with a following.
• Settings live in jhora.ini (in the jhcore folder) and can be saved and copied back with the program closed.

Is this good for rectification?

• Not for fine rectification. The progressed position hardly depends on birth time: 5 minutes barely moves natal Saturn, so the dasha dates and the progressed Saturn stay the same.
• A padamsa longitude is as sensitive as the lagna. In Dasamsa, 2 minutes of time moves the lagna and the arudha by about 6°. But the event comes anywhere within about 3° either side of the transit planet, so there is no sharp boundary to fix the time against. A Tithi Pravesha chart creates extra borders; this does not.
• What it can do is choose between two natal lagnas. If the planet aspecting the progressed 10th lord on the day of a layoff is the 8th lord with one lagna and the 9th lord with the other, it is the lagna that makes him 8th lord.

"This is useless for rectification. The only way you can use this to rectify is: 8th lord aspected the progressed 10th lord with this lagna. With this lagna, it is 9th lord, and he lost the job, so probably it is this lagna."

---