TickSig
Indicator guide

Waterfall lines

Combines smoothed prices into waterfall-style tracks.

Purpose and construction

Combines smoothed prices into waterfall-style tracks.

Waterfall lines is applied to the chart series using the local definition below. Each period counts one bar on the active chart. The same period therefore covers a different amount of time on daily and intraday charts.

How to read it

Compare alignment and compression across periods.

Confirm the inputs and settings before comparing the indicator with price. On an open bar, close, extremes and volume can still change, so the reading can update before the bar closes.

Parameters

ParameterDefault
M14
M26
M39
M413
M518
M624

Parameter names match the variables in the calculation. After changing a lookback or smoothing period, recalculate on the same data to compare response speed. Defaults from another platform may not match this definition.

Original illustrated case

This original daily-bar case moves through an advance, a pullback and a wider-range recovery. It does not represent a real security. Where available, outputs are calculated by the project’s formula engine using the defaults above.

Original Waterfall lines simulated case showing price, outputs and three observation points
Original educational figure. The three lettered points correspond to the observations below.

From bar 91 to bar 180, the close rose from 103.4126 to 117.6257. Compare each output below, then use the reading rules above to distinguish direction, momentum, participation or a pattern condition.

PointBarCloseVolumeCalculated outputs
A91103.412614187PBX1: 104.7281PBX2: 105.4977PBX3: 106.1566PBX4: 106.5576PBX5: 106.5841
B131102.746419368PBX1: 102.8601PBX2: 103.4141PBX3: 103.8467PBX4: 104.2705PBX5: 104.7473
C180117.625715024PBX1: 114.4989PBX2: 113.5345PBX3: 112.9423PBX4: 111.9845PBX5: 111.408

To reproduce: retain the same OHLCV series and default settings, then compare outputs bar by bar. Warm-up bars can have no value. The case-generation script and local definition are stored with the project, so plotted curves are calculated rather than hand-drawn.

Local calculation

The local definition is shown below. Display labels can be translated; the case calculation uses original source identifiers. A shared indicator name does not guarantee identical calculations across platforms.

PBX1:(EMA(CLOSE,M1)+MA(CLOSE,M1*2)+MA(CLOSE,M1*4))/3;
PBX2:(EMA(CLOSE,M2)+MA(CLOSE,M2*2)+MA(CLOSE,M2*4))/3;
PBX3:(EMA(CLOSE,M3)+MA(CLOSE,M3*2)+MA(CLOSE,M3*4))/3;
PBX4:(EMA(CLOSE,M4)+MA(CLOSE,M4*2)+MA(CLOSE,M4*4))/3;
PBX5:(EMA(CLOSE,M5)+MA(CLOSE,M5*2)+MA(CLOSE,M5*4))/3;
PBX6:(EMA(CLOSE,M6)+MA(CLOSE,M6*2)+MA(CLOSE,M6*4))/3;

Limitations

  • Compare alignment and compression across periods.
  • Timeframe, adjustments, warm-up length and data units affect results. Align these before comparing charts.

Questions

Why can Waterfall lines differ across platforms?

Compare inputs, default periods, smoothing, offsets and data units before comparing the final value. This guide uses the local source definition rather than assuming that an external example has the same settings.

Does the example show a real trade?

No. The figure and table use simulated data to explain calculations and chart reading. They contain no real orders and make no return or win-rate claim.

References

The calculation comes from the project’s indicator registry. Primary references below provide related conceptual reading. Figures and numerical cases are independently produced for this project.