Purpose
Optional, non-invasive confidence bands and event flags for UI/interpretation. These do not alter the deterministic evaluator; they only help annotate low-motion zones and near-cusp proximity. Bands are typically derived from an alignment score a_out ∈ (-1,+1) mapped to confidence conf = (a_out + 1)/2.
Official baseline thresholds (per body)
Each row lists the band splits (LOW/HIGH = 0.30/0.70 by default), the speed threshold v_thr (deg/day), and cusp radius d0 (deg) for flagging.
- Jupiter: LOW/HIGH =
0.30 / 0.70,v_thr = 0.06,d0 = 6.0 - Saturn:
0.30 / 0.70,v_thr = 0.03,d0 = 8.0 - Uranus:
0.30 / 0.70,v_thr = 0.010,d0 = 2.0 - Neptune (long-range):
0.35 / 0.65,v_thr = 0.0050,d0 = 0.5 - Sun:
0.30 / 0.70,v_thr = 1.00,d0 = 3.0 - Moon:
0.30 / 0.70,v_thr = 13.0,d0 = 2.0 - Mercury:
0.30 / 0.70,v_thr = 4.00,d0 = 2.0 - Mars:
0.30 / 0.70,v_thr = 0.50,d0 = 4.0 - Rahu/Ketu:
0.30 / 0.70,v_thr = 0.06,d0 = 6.0 - Venus:
0.30 / 0.70,v_thr = 0.20,d0 = 2.0
Usage notes
- Annotation-only. Bands/flags label conditions such as
flag_station := (|v| <= v_thr)andflag_cusp := (dist_to_cusp_deg <= d0); they never modifyL_hat_deg. - Consistency. Keep the same thresholds across train/test/runtime for stable labeling.
- Tuning. If you adjust any threshold, document it with the date span and timestamp used.
- Escalation (optional UI). A conservative advisory is
escalate := (conf < 0.40) or (flag_station and flag_cusp).
Navigation
Back: SSM-JTK – Results to Date — Public-golden CSV checks (3.1)
Next: SSM-JTK – Results to Date — Per-body highlights (3.3)
SHUNYAYA 