Specialized modules
Hotspot Scan
Hotspot Scan is a Pro research lab for one question: do this chart's big moves bunch up in particular sky states, more than chance would put them there? Pick the moves, build a list of sky states, and see which states catch more moves than their share of trading days predicts, with every hotspot re-checked on the same moves moved along the calendar.
Where to find it
Open Dashboard → Charts → Analysis → Hotspot Scan. The lab reads the loaded symbol's whole daily history, from 1900 at the earliest (back-adjusted for continuous futures when the chart's B-ADJ is on), and needs at least five years of it. The two panels it paints show on daily and longer intervals.
Pick the big moves
The count below shows how many moves the size finds, and in how many episodes (moves less than 30 days apart). Aim for 30–100 moves. Fewer leave every state nearly empty; more fill the list with everyday noise. When the count is out of range, the lab offers a size that lands inside it. Show dates lists every move with its size.
Build the sky-state list
The list works exactly as in Date Echo: choose the planets, the geocentric and/or heliocentric frame, and any of the families: waxing/waning, sign harmonics, position bands, angle bands, angle zones, ahead/behind, retrograde/direct and sunspot phase. Lists you save are shared by both labs.
Sunspot phase treats the solar activity cycle as an artificial planet: 0° at each sunspot minimum, 180° at each maximum. Pick harmonics H1–H4 and a band width from 10° to 60°. One degree is about 11 days of an average cycle, so 10° ≈ 112 days and 20° ≈ 223 days. The Sunspot phases preset loads H1–H4 in 20° bands, 72 states. That is the lab's starting point.
Scan
Each state gets three numbers:
- Hits: moves that landed on days the state held.
- Expected: the number of moves × the share of trading days the state holds.
- χ² = (hits − expected)² ÷ expected, which scores how far above expected the hits run.
A state is a hotspot when its hits run above expected and pass both filters: Min hits (a tenth of the moves by default) and Min χ² (2.5 by default; 3.8 is the usual 5% bar for a single test).
Press Scan sky states. The lab then repeats the scan on hundreds of copies of the same moves, moved along the calendar era by era. An era is a run of moves with no gap longer than three years (two years, or one, when that would leave fewer than eight eras), so each era keeps its own bunching. The copies are made two ways:
- Random dates: each era slides by a random number of days, never close to a whole number of years.
- Same calendar days, other years: each era moves by a whole number of years, which keeps the Sun (and Mercury and Venus, which stay near it) where it was. "All my moves fall in October" therefore can't pass for a sky pattern.
Read the verdict
As in Date Echo, two checks run against both kinds of copies, each at 2.5%:
- Hotspots: whether the scan finds more hotspots than the moved copies do.
- Strongest: whether the single rarest hotspot is rarer than the rarest of every copy.
On random moves the lab says "beats chance" or "calendar effect" about one time in twenty or less.
Why not trust a big χ² on its own? Big moves bunch. Crash days pile into a few eras such as 1929–33, 2008 and 2020, so whichever state held through one of those eras scores a huge χ², and among dozens of states a few always look lucky. The moved copies keep that bunching, which is why they often find just as many hotspots. Each row shows the hits against expected, χ², the hits ÷ expected ratio, how often the state holds (on), and how often the moved copies passed it too (chance). A stands out badge marks a state that passes the strongest check on its own. A season badge flags states that same-season copies pass far more often.
When nothing is found
If no state passes, or the hotspots read as chance, the Try this box suggests concrete next steps, each with a one-click button:
- Change the move size to land inside 30–100 moves.
- Widen the bands (for example sunspot 10° → 15° → 20°) so each state collects more moves.
- Lower Min hits to what the best state caught, or lower Min χ² a step.
Loosening the filters lists more states, but it cannot turn chance into a pattern: the moved-copies check reruns with the same filters on every scan.
Put it on the chart
- Paint Hotspot Index adds the Hotspot Index panel. For every day it shows the share of the ticked hotspots that hold, continued into the future, with a dashed line at its typical level. Untick a row to leave that state out.
- Tick by chance ticks only the hotspots that the moved copies passed at most 20%, 10% or 5% of the time (All ticks every hotspot again).
- The pin on a row shades the days that state holds through the Sky States panel, past and future.
The Hotspot Index saves the ticked states themselves, so a layout reproduces the line without rescanning; its status line names the symbol, the moves and the years scanned. It can also be opened from Modules → Astrology. Out of the box it stacks the sunspot band just before each solar minimum on all four harmonics.
Use it responsibly
- Fix the moves, the list and the filters before reading results. Each retry is another roll of the dice; a pattern worth acting on should survive without fine-tuning.
- Longer histories test better: they hold more eras, and each era is one real observation however many moves it contains. With fewer than eight eras the lab says so under the move count.
- A rising Hotspot Index marks a period to review, not a predicted move.
Plan access
Hotspot Scan and the Hotspot Index panel require Pro.
Related guides
- Date Echo for the sky states a handful of key dates share
- Event Tester for price behavior around single-day events
- Astro Modules for every astro chart panel