By Islam BarakaDefinitions
In plain terms
Before an exponential moving average can update recursively, it needs a first value. This policy averages an initial block of observations and uses that average as the starting state.
Technical
For a declared seed length n, the initial EMA state at the nth eligible observation is the arithmetic mean of observations x_1 through x_n; later states use the chosen EMA recurrence.
Scope
This is an explicit implementation policy, not a universal requirement of every EMA or McClellan implementation; eligibility, seed length, and missing-data handling must be declared separately.
Formula
EMA_seed = (x_1 + ... + x_n) / n\operatorname{EMA}_{\mathrm{seed}}=\frac{1}{n}\sum_{i=1}^{n}x_i| Symbol | Meaning | Unit |
|---|---|---|
x_i | Eligible seed observation i | input unit |
n | Declared seed length | observations |
Output unit: same as input
Examples
- With seed observations 8, 10, and 12, the initial EMA state is 10.
Common misconceptions
- SMA seeding does not make every later EMA value a simple moving average.
Concept relationships
Required by
- Ready Point
- Traditional McClellan Oscillator
- Ratio-Adjusted McClellan Oscillator
- McClellan Volume Oscillator
- Force Index
- Raw Force
- Price–Volume Unit
- Force EMA Seed
- Force EMA Update
- Force Index Warm-Up
- Force Index Zero-Change State
- Force Index Zero-Volume State
- Force Index Recursive Revision
- Force Index versus VPT
Where this concept is used
Tutorials planned
These catalogued topics use this concept, but their complete build has not shipped yet.
- D04-F02-A01 Important
- D04-F02-A02 Important
- D04-F02-A03 Important
- D04-F02-A05 Important
- D04-F02-A06 Important
- D07-F01-A02 Important
- D07-F01-A05 Important
- D07-F01-A06 Important
- D07-F02-A01 Important
- D07-F03-A07 Important
Evidence and governance
- McClellan Oscillator StockCharts ChartSchool · secondary methodology
Supports: technical definition, formula, variant distinction
Limits: Platform symbols, displayed thresholds, universe choices, and implementation details are vendor-specific rather than universal methodology requirements.
- Reviewed by
- Islam Baraka
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published