Methodology

How TradeWave detects seasonal patterns over a lookback you choose - 1 to 99 years, calendar or election cycle - how the ML layer ranks them, and how to audit every number we publish.

Last updated: June 11, 2026

TradeWave is a research engine that analyzes decades of market history to find recurring seasonal patterns - the way an instrument has tended to move at the same time of year, or across the four-year presidential election cycle - and to measure their risk and return. You choose how far back it looks, from 1 to 99 years, and you judge the pattern yourself. We would rather be audited than believed, so every number TradeWave publishes traces back to the rules on this page. This page explains how the patterns are computed, what the machine-learning layer does and does not do, which statistics we display, and the limitations you should keep in mind, in enough detail to survive due diligence and reproduce on your own.

1. What TradeWave does

TradeWave ingests long-term daily price data for stocks, indices, exchange-traded funds, futures, currencies, and crypto across 15 markets. The engine scans these histories for recurring windows where price has shown a consistent tendency to move higher or lower - measured either on the calendar (the same dates each year) or across the four-year presidential election cycle (the same point in the cycle each term). You set how far back to look, from 1 to 99 years; the major indices carry up to roughly a century of actual price history.

Seasonal pattern statistics in TradeWave are fully rules-based. Given an instrument, a start date, a window length, and a lookback period, the result is deterministic: anyone with the same data and the same rules gets the same numbers. There is no curve fitting or discretionary manual adjustment in the pattern calculations. (Machine learning is used in a separate, clearly labeled scoring layer, described in section 5.)

Key principle: calculation is separated from narrative. The engine produces historical statistics from hard market data. Any written commentary that references those results is created afterwards, from the numbers.

2. Data sources and universe

TradeWave uses end-of-day data from established market data vendors and exchange feeds. Coverage includes major United States equities listed on NYSE and Nasdaq, key global stock indices and index-tracking ETFs, and selected futures, commodities, foreign-exchange pairs, and crypto assets. The longest index histories extend back roughly a century.

Price histories are adjusted for splits, reverse splits, and cash dividends where applicable, so historical returns reflect actual investor experience. Before any pattern is calculated the engine corrects pricing anomalies that conflict with exchange data, aligns trading calendars across holidays and closures, and excludes instruments with insufficient history for the requested lookback.

3. How a seasonal pattern is defined

Every TradeWave pattern is defined by four parameters you control: the instrument, the pattern start date, the window length in trading days, and the lookback - 1 to 99 years on the calendar, or aligned to the presidential election cycle. Change any one and the statistics recompute in front of you; there is no fixed, hidden window. For each year in the lookback, the engine simulates entering at the official daily close on the start date and exiting at the close after the specified number of trading days. Long patterns treat rising prices as gains; short patterns invert the return series so that downward moves count as positive returns.

4. The statistics we display

Percent Profitable - the percentage of lookback years that finished with a positive return in the pattern's direction. Always read it together with the number of years: 12 of 15 is evidence, 3 of 4 is an anecdote.

Average Profit - the average return of the winning years only.

Average Profit (All) - the average net return across all years, including the losers. This is the number closest to "what the pattern actually earned per year."

Sharpe Ratio - a risk-adjusted measure: the average yearly return divided by how much those yearly returns scatter around it. Higher means the pattern paid more steadily, not just more.

TradeWave Ratio (TWR) - a proprietary metric reflecting how far price typically travels in the trade direction within the window, incorporating both the final return and the maximum favorable excursion.

Maximum Favorable Excursion (MFE) and Maximum Adverse Excursion (MAE) - the best gain and the worst loss reached at any point inside the window, year by year, before it closed. A pattern can finish positive in every year and still produce uncomfortable drawdowns along the way; MAE is where you see that.

5. The machine-learning layer (what it is, and what it is not)

On top of the deterministic pattern statistics, TradeWave runs a separate machine-learning model whose only job is ranking: of the patterns whose windows are opening now, which have the strongest combination of characteristics that historically preceded a winning year?

The model is a gradient-boosted ensemble, a method that combines many small decision rules into one ranking, using 62 features per candidate, trained on roughly 34.7 million data points of historical pattern outcomes and validated walk-forward on 8 years of out-of-sample data - years the model never saw during training, scored as if it were predicting them in real time. Its output is a win-probability score between 0 and 1. Win rates vary by score band; the daily pick selection draws from the highest bands.

Three things the score is not: it is not a price target, it is not a guarantee, and it is not a substitute for the underlying statistics. The score ranks; the per-year receipts remain the evidence. The model is retrained periodically and its feature set is versioned, so a score shown today reflects the current model generation.

6. How we guard against curve fitting

Scan enough instruments, dates, and window lengths and you will always find patterns that look perfect by coincidence. This is the data-mining problem, and any honest seasonality tool has to answer it. TradeWave's defenses:

Minimum evidence thresholds. Patterns must clear consistency and risk-adjusted floors across many years, not just a high average produced by one outlier.

Full receipts. Every pattern shows its complete per-year history. Losing years are displayed, never trimmed.

The forward track record. The decisive defense: every day the engine publishes one pick, logged publicly before the outcome is known, then tracked to completion, wins and losses alike, on the scorecard. Backtests can fool their authors; a timestamped forward ledger cannot. We do not ask you to trust our backtest - we ask you to check the ledger.

7. How to read a pattern like a professional

Two questions worth asking of any seasonal statistic, ours included:

Is it more than the market? Compare the pattern's window return to simply holding the instrument over the same period. A "seasonal edge" that matches the underlying's drift is beta wearing a costume.

Does it still hold recently? A pattern that was strong decades ago and flat for the last five years deserves more skepticism than its full-history average suggests. The per-year table on every pattern lets you check the recent years directly.

8. Costs and execution

Displayed returns are computed close-to-close and do not include commissions, fees, slippage, or taxes. Real-world results will differ, and short windows on less liquid instruments are the most sensitive to execution costs.

9. Limitations

Seasonal patterns summarize historical behavior, not guaranteed outcomes. Extreme outlier years can affect averages. Market structure changes over multi-decade periods. Drawdowns inside the window can be significant even in years that finish as wins. TradeWave outputs are informational and educational; they are not investment advice. See the full disclaimer.

10. Who builds this

TradeWave is built by Afshin Moshrefi, founder of Tara Data Research LLC, the research shop behind Seasonal Market News, and author of The 100-Year Pattern (2026), after four years of engineering the data pipeline, the pattern engine, and the scoring model described above. Questions about the methodology are welcome at contact.

← Back to home