Appearance

Personalize your experience

Mode
Accent Color
Direction
Analysis Marketplace
QuaScript

Pressure Wave

NewFree

Signed volume pressure as a gradient wave with tide line and divergences

WebGPU StudioOwn pane WebGPU CanvasHybridDashboardSignalsAlerts
quascriptgpuwebgpuorder-flowpressuredivergence

Favourites and Admin's Choice analyses are listed in the terminal's indicators window under Analysis Marketplace.

Language
QuaScript
Engine
Native C++, incremental on live ticks
Rendering
WebGPU + Canvas
Placement
Own pane
Settings
4
Plots
5
Lines of code
73
Source
presets/analysis/gpu/pressure_wave.qs
Pressure Waveengine result
Loading the engine result…
quatick-charts · QuaScript engine on synthetic 1-minute bars · drag to pan · scroll to zoom · Run executes the script on the engine (⌘/Ctrl+Enter while editing)

About

Buying and selling pressure as a glowing wave. Each bar's buy and sell volume (exchange order flow when the chart has it, otherwise a bulk-volume estimate) gives a signed pressure between -1 and +1; a fast and a slow volume-weighted average of it form the wave. The area under the fast wave is filled with a per-bar gradient on a profit-and-loss ramp, the slow wave is the tide line, and the histogram is their difference. Reading: a wave above the tide and rising = buyers pressing; a wave that rolls over while price still makes highs is a pressure divergence, the early warning of a top (mirror for bottoms). Signals: tide crosses, bullish and bearish pressure divergences at confirmed swings.

5
Plotted series
4
Signal marks
1
Drawings
2
Alert rules
4
Settings
63
Lines of code

What it draws

Own pane · counted from the engine's plot table and the script's draw calls

Series

  • Line3 visible · 1 helper
    ZeroWaveTide
  • Histogram1
    Wave minus tide
  • Band fills (render.band calls)1
Legend
Zero Wave Tide Wave minus tide

Signal marks

Bullish pressure divergenceBearish pressure divergenceWave over tideWave under tide

Drawings and chart effects

  • Dashboard tables1 created

How it runs

From source to the live chart, for this script

  1. 1
    Compile

    The QuaScript compiler checks the 73-line script (63 lines of code) and lowers it for the native C++ engine. Compile errors point at the exact line and column.

  2. 2
    Place

    The header sets pane = hpane with height = 0.26 (26% of the chart), so the output gets its own pane under the price with its own scale.

  3. 3
    Compute

    The script runs once per bar, oldest to newest. 7 persist variables keep state (objects, counters) across bars.

  4. 4
    Stay live

    On the terminal the script keeps one live engine session: a tick rolls the forming bar back to its checkpoint and re-executes only that bar, and new bars are appended, so history is never rerun while the market moves. The live result is identical to a full run.

  5. 5
    Render

    The results are handed to the chart: series on WebGPU, drawings on the Canvas 2D QuaScript layer.

  6. 6
    Tune

    4 settings in 2 groups appear in the chart's settings dialog. Changing one reruns the engine with the new value.

Rendering

Hybrid: this script draws on 2 surfaces at once

WebGPUSeries renderer

The browser's modern GPU API. The chart uploads every line, band and mark of the script as GPU buffers and draws them in one pass, so dense heatmaps and dozens of series stay smooth while you pan and zoom. Without WebGPU support the chart's GPU layer falls back to WebGL 2, then Canvas 2D.

In this script
  • • 5 plotted series
  • • 1 band fill call
  • • 4 signal mark types

Chosen by render = webgpu in the header.

WebGLNot used

GPU drawing through WebGL 2, available in every current browser. Used for chart-native profiles and for series that ask for it with backend = "webgl". Fast for large numbers of bars and wide fills.

CanvasUsed

The browser's 2D drawing API. Text-heavy and object-style output (dashboard tables, zones, tags, segments), candle colors and backgrounds are painted by the QuaScript layer, a Canvas 2D surface over the chart. Series use Canvas when the script's header does not ask for a GPU.

In this script
  • • 1 dashboard tables (QuaScript layer)

Alerts

2 alert rules declared with alert.rule

Bullish pressure divergence

Lower price low with a higher pressure low

Bearish pressure divergence

Higher price high with a lower pressure high

Settings

4 settings, grouped as in the chart's settings dialog

Wave
SettingTypeDefaultRange / optionsId
Wave lengthInteger82 – 200wave_length
Tide lengthInteger345 – 500tide_length
Divergence
SettingTypeDefaultRange / optionsId
Swing barsInteger52 – 30swing_bars
Divergence reach (bars)Integer6010 – 500divergence_reach_bars

Script

packages/quascript/presets/analysis/gpu/pressure_wave.qs

Header

analysis "Pressure Wave" {
    pane = hpane
    height = 0.26
    render = webgpu
    short_title = PWV
    precision = 2
}
Total lines
73
Code lines
63
Comment lines
9
Helper functions
0
Loops
0
Persistent variables
7
Higher-interval feeds
0
Engine plots
5

Built with

Technical analysis (ta.*)
ta.bars_sinceta.cross_downta.cross_upta.emata.pivot_highta.pivot_low
Microstructure kernels (hft.*)
hft.flow
Math (math.*)
math.clampmath.coalescemath.is_namath.max
Imported modules
viz/premium

Discussion

Sign in to join the discussion. Your posts and replies show up on your profile.