Can you program Quant trading in Pine Script?

[LondonNewsTrader]

Can you build real quant models using Pine Script? The short answer is: Yes, but you have to know its limits.

Honest framing. Pine is strong for quantifying structural setups; it is not a full microstructure stack.

For a London news trader the valuable use is measuring how often a sweep-and-reclaim or post-print continuation actually pays after costs — not recreating a Python LOB engine on TradingView. Arrays and strategy testers help you kill romantic patterns quickly. Where Pine stops is exactly where scalping lives: queue position, real lag, and broker-specific slip around releases.

So I use it to research edge shape on quiet London days, then validate on fill logs in the live platform. Microstructure claims that only exist inside the Pine emulator stay research notes.

Where do you personally draw the line — Pine for signals only, or are you trying to drive execution alerts straight from it into the overlap?

[LondonScalper]

For those of us trading raw price action—specifically focusing on market microstructure, spread dynamics, and liquidity sweeps—lagging technical indicators are useless. We need to model structural edge.

For microstructure and sweep logic, Pine is a research and alert layer for me, not the whole quant stack. It is strong for expressing structural ideas on a chart and pushing alerts; weak when you need true tick replay, broker-normalised volume, and production order management.

I prototype the idea visually, then decide whether it belongs in an EA/cBot or stays discretionary with alerts. Lagging indicators were never the London edge anyway — session, spread, and invalidation were.

Where do you draw the line between “model in Pine” and “must leave TradingView”?

In practice most of my edge still lives in knowing the London open behaviour and refusing thin books, not in a more exotic Pine model. Code is a notebook; the session is the filter.

[PropScalpDesk]

The Proof of Concept: Institutional D1/15m Liquidity Absorption To demonstrate its capacity for pure structural modeling, the following script prototypes a high-timeframe liquidity sweep. It identifies the Previous Daily High/Low and maps it to the 15-minute chart.

Pine is a research/alert layer for me, not the whole quant stack. Good for expressing structure; weak for production order management and broker-true volume.

I prototype visually, then decide EA versus discretionary+alerts.

Where do you draw the line between model-in-Pine and leave-TradingView?

I also log refused tickets so flat time counts as work — otherwise the desk invents activity.

If the idea needs a story longer than one line, it waits for another window.

Funded trailing DD is the external referee that keeps the desk honest.

Topic note from my sheet for t=12447: keep risk unchanged until the sample says otherwise.