Tool
Astro Event
interpretor.astro_event
Inputs
The astro-events info bundle from a market.astro_events node, carrying upcoming sky events with their dates and cluster counts.
Outputs
An interpreted astro bundle: the matched true/false signal plus the cluster count and signed days-to-event as reusable numbers.
Astro Event is a gate that fires when a chosen calendar event from the sky, like an eclipse or a planet turning retrograde, is near in time and clustered with enough other events. Alongside the true/false signal it also hands back how many events are clustered and how many days until the event, as numbers you can reuse.
How it works
It reads the info bundle from a market.astro_events node and fires its matched BOOL when the chosen event_type is within within_bars and at least min_cluster events are grouped together. It also passes through the cluster count and the signed days-to-event as SCALARs.
Modes
Fires near the date a planet stations and turns retrograde (appears to start moving backward).
When to use: Use this to gate around the moment a planet flips to retrograde, a watched turning point.
Fires near the date a planet stations and turns direct (resumes forward motion after retrograde).
When to use: Use this to gate around the moment a planet returns to direct motion.
Fires near the date a planet crosses from one zodiac sign into the next (an ingress).
When to use: Use this to gate around a planet changing signs, treated as a shift in tone.
Fires near the date of a solar eclipse, when the new moon blocks the Sun.
When to use: Use this to gate around solar eclipses, the most-watched astro dates.
Fires near the date of a lunar eclipse, when Earth's shadow falls on the full moon.
When to use: Use this to gate around lunar eclipses as a timing window.
Configuration
Which sky event to gate on — a planet stationing retrograde or direct, a sign ingress, or a solar or lunar eclipse.
Fire only when the event is within this many bars in time.
Require at least this many events grouped together before the gate fires.
Connects to
Examples
- Use it as a filter so the strategy only trades within 5 bars of a solar eclipse.
- Require min_cluster of 2 or more so only busy event windows open the gate.
Common mistakes
- Setting within_bars too large, so the gate is almost always open and adds no selectivity.
- Treating an eclipse window as a buy or sell signal rather than just a timing filter.