Aroon Up, Down, and Oscillator: Measure Extreme Recency

Two markets can make the same price change while differing in whether the move created a fresh extreme. Aroon isolates that recency structure and makes the high-side and low-side clocks visible.

Aroon measures how recently a rolling window produced its highest high and lowest low. It does not measure the distance price traveled; it maps the age of each extreme onto a 0–100 scale. By the end of this tutorial, you will be able to calculate the line, audit its hidden state, reproduce its warm-up and boundary conventions, and explain why another platform can disagree.

Data note: every chart and number in this article uses deterministic synthetic teaching data. No historical return or investment-performance claim is made.

Start with the question the indicator actually answers

A trend system is useful only when its output has a precise meaning. The current package asks one bounded measurement question and refuses to turn a chart state into a forecast.

Aroon measures how recently a rolling window produced its highest high and lowest low. It does not measure the distance price traveled; it maps the age of each extreme onto a 0–100 scale.

Aroon mechanism map

The map is the implementation checklist: validate the bar, calculate the intermediate state, apply the exact boundary rule, then publish an aligned output with its diagnostic evidence.

Formula and selected convention

For row $t$ , inspect the inclusive window $t-n,\ldots,t$ . If $h_t^\*$ and $l_t^\*$ are the most recent indexes of its highest high and lowest low:

A^\uparrow_t=100\frac{n-(t-h_t^\*)}{n},\qquad A^\downarrow_t=100\frac{n-(t-l_t^\*)}{n}

O_t=A^\uparrow_t-A^\downarrow_t

The window contains period + 1 observations and the first output is at index period. Equal extremes select the most recent occurrence.

Defaults are teaching choices rather than universal laws:

Parameter	Package default
`period`	`25`

Worked numerical example

For period 5, if the highest high occurred now and the lowest low occurred four bars ago, Aroon Up is 100, Aroon Down is 20, and the oscillator is 80.

The hand result is deliberately small enough to recalculate without either implementation. The canonical fixture then extends the same rules across five long, topic-specific paths.

Aroon exact canonical trace

From data contract to executable state

Use finalized, chronological observations with one declared source field, session calendar, time zone, and adjustment basis. Reject non-finite values, malformed high/low geometry, and invalid parameters. Do not sort inside the numeric kernel, fill missing bars with zero, or splice adjusted and unadjusted history.

The implementation returns one aligned entry per input row. Warm-up stays None in Python and null in TypeScript. A revision to historical input invalidates the recursive or rolling suffix from the earliest changed row.

Rendering system map…

Implementation walkthrough

The Python and TypeScript files favor direct state variables over clever vectorization. That makes seed, tie, clamp, displacement, and reversal behavior reviewable. Both languages read the same fixture and preserve the same null, numeric, string, and boolean semantics.

Complexity is linear in the number of observations. The reference code is optimized for readability; a production streaming implementation can retain only the active rolling/recursive state after validating parity.

Reconcile a platform disagreement systematically

Dimension	This package	Maintained-platform context	What to compare
Teaching period	25	Current TA-Lib documentation lists 14 as its default	A default is a convention, not the formula.
Window	Inclusive t−period through t	TA-Lib documents the same index range	An implementation using period rows will be one bar early.
Equal extreme	Most recent tie wins	Platform tie handling must be checked	Repeated equal highs/lows are a required reconciliation case.

Start at the first row where the two outputs diverge. Compare source fields and parameters first, then the previous intermediate state, and only then the published line. This avoids treating a documented convention difference as a numerical defect.

Explore the exact state

Open the guided Aroon playground. The initial state is already informative. Choose a scenario, scrub or step to a named checkpoint, compare the visible diagnostics, and inspect the last 12 published rows.

The lab uses 180 observations in each of five scenarios, not a tiny decorative sample. A recent-60, recent-120, or complete-history focus keeps the denser path readable. Reduced-motion Play advances one observation without starting a timer.

Use the five-scenario atlas

Lesson	Scenario ID	What the controlled path isolates
Fresh-extreme ladder	`fresh-extreme-ladder`	Successive highs and later lows show each recency clock jumping to 100 and then decaying.
Most-recent tie policy	`most-recent-ties`	Repeated equal highs and lows make the package's most-recent tie rule visible.
Rolling-window expiry	`window-expiry`	An early extreme ages out of the inclusive period-plus-one window without a large new price move.
Distance versus recency	`distance-recency-contrast`	Large and small price moves share similar extreme ages, proving Aroon measures when rather than how far.
Fourteen-period comparison	`short-window-sensitivity`	A shorter period resets the recency clocks faster and is explicitly separated from the package's 25-period teaching default.

Each path contains five checkpoints: first guided state, transition, boundary, platform reconciliation, and mature-state audit. These labels explain deterministic calculation state; they do not classify future market behavior.

A production debugging ladder

Verify finalized input fields, chronological order, calendar, time zone, and adjustment basis.
Verify parameter values and the first-ready index.
Track the winning high/low indexes, their ages, the inclusive window start, and the most-recent tie rule.
Compare the shared fixture at the first divergent row.
Recalculate one checkpoint independently before changing code.
Record the convention version with every persisted output.

Boundaries that cause real implementation drift

Aroon records the age of an extreme, not its amplitude or slope.
Tie policy matters: this package chooses the most recent equal high or low.
The inclusive period-plus-one window is easy to implement one bar too short.

Aroon boundary map

The strongest reconciliation workflow compares the first valid index, a steady-state row, an equality boundary, a reversal or reset, and the complete aligned suffix—not merely the last visible chart point.

Compare the family question, not the chart color

PPO measures relative separation between smoothed price levels. Aroon ignores that distance and measures when the most recent high and low occurred.

Neighboring indicators can display a similar bullish/bearish state while measuring different inputs. Agreement is not independent confirmation when the systems reuse the same prices and smoothing primitives.

Testing proves calculation, not profitability

The release checks cover:

all-five-scenario Python/TypeScript parity;
exact first-ready behavior;
invalid values and parameters;
equality, zero, tie, displacement, clamp, or reversal semantics;
SVG accessibility and fixture-derived values;
deterministic playground controls and reduced motion;
responsive reader and standalone rendering.

None of those checks estimates future returns. A strategy study would still need point-in-time constituents, execution clocks, fees, slippage, survivorship controls, and out-of-sample evaluation.

Historical-example decision

A named historical chart is not useful for this mechanism lesson. It would introduce vendor data, adjustment, identifier, session, licensing, and hindsight ambiguity without strengthening the arithmetic. The synthetic paths isolate the causal rule and can be redistributed with the package.

Common questions

Is Aroon a prediction?

No. It is a deterministic transformation of observed bars under the selected convention.

Can I compare values across platforms?

Only after aligning the source field, price basis, windows, seed, boundary rules, and display displacement.

What should I log in production?

Log the parameters, first-ready index, current intermediate state, input revision identifier, and the exact convention version.

What is the next tutorial?

Continue to Directional Movement, which changes the trend-system question and makes a different state or normalization visible.

Workflows

Rendered from the canonical Mermaid sources linked by this article.

Aroon calculation flow

Rendering system map…

Takeaway: the displayed line is reproducible only when the hidden state and its boundary convention are preserved.

References5 primary sources and evidence notes

Expand the source trail, evidence role, and limitations behind the engineering choices.

Access date for web sources: 2026-07-26. Public artifacts use only deterministic synthetic data.

R1 — Tushar Chande's 1995 Aroon article

Organization or authors: Tushar Chande's 1995 Aroon article
Source type: Original or origin-attribution publication record
Publication or effective date: See catalog record
Version: Bibliographic record accessed 2026-07-26
URL or DOI: https://traders.com/documentation/feedbk_docs/1995/09/Abstracts_new/Chande/Chande.html
Accessed: 2026-07-26
Jurisdiction: General technical analysis; no regulatory jurisdiction
Evidence role: Origin and historical-definition context
Supports: Authorship/origin and the conceptual purpose of the method.
Limitations: The public record does not by itself freeze every modern platform seed, tie, plotting, or rounding convention.
Publication decision: Cite for origin; use maintained documentation and the package contract for executable semantics.

R2 — TA-Lib AROON

Organization or authors: TA-Lib project or TradingView, as identified by the linked page
Source type: Maintained official technical documentation
Publication or effective date: Current page
Version: Page accessed 2026-07-26
URL or DOI: https://ta-lib.org/functions/aroon
Accessed: 2026-07-26
Jurisdiction: General technical analysis; platform applicability stated in the package
Evidence role: Formula and maintained implementation-context evidence
Supports: Aroon measures how recently a rolling window produced its highest high and lowest low. It does not measure the distance price traveled; it maps the age of each extreme onto a 0–100 scale.
Limitations: Documentation cannot establish predictive power, profitability, or universal platform parity.
Publication decision: Publish formula facts with the package's selected conventions visibly separated.

R3 — Pinned TA-Lib ta_AROON.c implementation

Organization or authors: TA-Lib project or TradingView
Source type: Pinned maintained source or maintained calculation guide
Publication or effective date: Repository commit or current guide
Version: e203f7c436a9c21fd08246661971cfcb7ee37517
URL or DOI: https://github.com/TA-Lib/ta-lib/blob/e203f7c436a9c21fd08246661971cfcb7ee37517/src/ta_func/ta_AROON.c
Accessed: 2026-07-26
Jurisdiction: General technical analysis
Evidence role: Executable or platform-convention evidence
Supports: Executable loop order, warm-up behavior, and maintained reference semantics used to compare the package convention.
Limitations: Source parity is not claimed where this package explicitly selects a clearer seed or zero-state convention.
Publication decision: Use to regression-check semantics; document intentional differences instead of implying universal equivalence.

R4 — Canonical synthetic fixture and independent arithmetic

Organization or authors: The Fintech Builder
Source type: Author-derived calculation from synthetic teaching inputs
Publication or effective date: 2026-07-26
Version: Fixture schema 2.0
URL or DOI: datasets/aroon-fixtures.json
Accessed: 2026-07-26
Jurisdiction: Not applicable
Evidence role: Reproducibility and Python/TypeScript parity
Supports: Published worked values, warm-up, equality, reset, and scenario behavior.
Limitations: Synthetic observations prove calculation behavior only; they are not market evidence.
Publication decision: Redistributable with the package; label every use synthetic.

R5 â€” TA-Lib AROONOSC function documentation

Organization or authors: TA-Lib project or TradingView
Source type: Maintained official technical documentation
Publication or effective date: Current page
Version: Page accessed 2026-07-26
URL or DOI: https://ta-lib.org/functions/aroonosc
Accessed: 2026-07-26
Jurisdiction: General technical analysis; platform applicability stated in the package
Evidence role: Neighboring-function and platform-reconciliation evidence
Supports: Maintained oscillator relationship and platform comparison.
Limitations: A maintained platform record documents its own convention and does not make the package convention universal.
Publication decision: Use in the reconciliation matrix; retain package choices and intentional differences explicitly.

Implementation

Full dependency-light reference implementations in both supported languages.

aroon.ts

export type Numeric = number | null;

    function validateSeries(values: number[], name: string): void {
      if (!Array.isArray(values) || values.length === 0) throw new RangeError(`${name} must be a non-empty array`);
      if (values.some((value) => typeof value !== "number" || !Number.isFinite(value))) {
throw new TypeError(`${name} must contain only finite numbers`);
      }
    }

    function validateHL(high: number[], low: number[]): void {
      validateSeries(high, "high");
      validateSeries(low, "low");
      if (high.length !== low.length) throw new RangeError("high and low lengths must match");
      if (high.some((value, index) => value < low[index])) throw new RangeError("high must be >= low");
    }

    function validateHLC(high: number[], low: number[], close: number[]): void {
      validateHL(high, low);
      validateSeries(close, "close");
      if (close.length !== high.length) throw new RangeError("high, low, and close lengths must match");
      if (close.some((value, index) => value < low[index] || value > high[index])) {
throw new RangeError("close must lie inside each high-low range");
      }
    }
export function aroon(high: number[], low: number[], period = 25) {
  validateHL(high, low);
  if (!Number.isInteger(period) || period < 1) throw new RangeError("period must be a positive integer");
  const aroon_up: Numeric[] = Array(high.length).fill(null);
  const aroon_down: Numeric[] = Array(high.length).fill(null);
  const oscillator: Numeric[] = Array(high.length).fill(null);
  for (let index = period; index < high.length; index += 1) {
    const start = index - period;
    let highIndex = start;
    let lowIndex = start;
    for (let candidate = start + 1; candidate <= index; candidate += 1) {
      if (high[candidate] >= high[highIndex]) highIndex = candidate;
      if (low[candidate] <= low[lowIndex]) lowIndex = candidate;
    }
    aroon_up[index] = (100 * (period - (index - highIndex))) / period;
    aroon_down[index] = (100 * (period - (index - lowIndex))) / period;
    oscillator[index] = (aroon_up[index] as number) - (aroon_down[index] as number);
  }
  return { aroon_up, aroon_down, oscillator };
}

Playground

The embedded lab now expands to its full document height, keeping the article as the only scroll surface.

Full-height labaroon labOpen full screen