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.

Actual application chart

This screenshot shows Waterfall lines running on the application's TSLA daily chart. Price and indicator share the same market history, preserving the curves, bars and markers drawn by the application.

Actual application screenshot of Waterfall lines on the TSLA daily chart
Captured 2026-10-19; market data through 2026-10-16. Only surrounding interface elements were cropped; the indicator was not redrawn.

Compare alignment and compression across periods.

  1. Check the displayed indicator name and parameters against the version currently loaded.
  2. Align price and indicator by time, then compare direction, turning points and marker locations.
  3. After changing settings or timeframe, wait for calculation to finish before saving the same interval for comparison.

The screenshot records a historical chart display, not executed orders, returns or a win rate.

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. Figures show the indicator running on historical market data in the application. They contain no executed 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 are captured from the running application.