TradingView indicators
The exact Pine scripts behind the published backtest · Pine v6 · updated 2026-10-06
How to run the 5 batches.
- Chart on
NSE:BAJFINANCE1!, timeframe 4h
- Window:
Backtest FROM = 01 Jan 2016, TO = 01 Jan 2035 — TradingView
remembers inputs per script slot, so check this on every batch. The year table's first row must
read 2016, not 2023.
- Change nothing else between batches, or the totals will not be addable
- Caps default to A = 25,000 / B = 35,000
196 symbols need five scripts because
Pine caps request.*() at 40 calls per
script — a platform limit, not a design choice. Both caps run side by side
inside one
script, so they see identical signals, bars and lot sizes.
Verification habit worth keeping. Run every batch twice, changing
one thing that cannot legitimately matter — the chart symbol. Anything that moves is
reading something it should not. That is exactly how the B5 phantom-trade bug was caught:
B1–B4 reproduced to the rupee across two chart symbols; B5 did not.
Current — these produced the live config in use
Supporting studies research
Superseded kept for provenance
Do not quote numbers from these.
report_B5 held 36 real symbols but made 40 runSym() calls, with slots
37–40 left as input.symbol("") — and Pine resolves an empty symbol string to the
chart symbol (ignore_invalid_symbol does not help; empty is valid). It
traded four phantom copies of whatever chart it sat on. The guard
str.length(s37) > 0 ? c_37 : na is applied, but the published figures from this
set were superseded by cap_B1..B5.