Relative Vigor Index Trading Strategy: Define and Test an RVI Crossover
An RVI trading strategy needs more than a crossover screenshot. Define the calculation, the moment a signal is available, the order rules, and the evaluation sample before drawing a performance conclusion. This guide provides a research protocol; it does not report a verified winning strategy.
Fix the indicator definition first
Relative Vigor Index compares smoothed close-minus-open movement with smoothed high-minus-low range. It is centered around zero. A positive reading describes the smoothed numerator's sign, not a guarantee that the next close will be higher.
Pineify's RVGI implementation uses four-bar symmetrical weights of 1, 2, 2, and 1 for each series, then divides their rolling sums over the selected length. Its signal is another four-bar symmetrically weighted average of RVI. The default length is 10. Do not silently replace that signal with an ordinary SMA and compare the results as if they were the same strategy.
The official TradingView explanation covers the indicator's definition. The indicator setup guide describes Pineify's outputs and calculation boundaries in more detail.
Write a baseline that another person can reproduce
A useful baseline specification could require a confirmed-bar RVI crossover above Signal for a long entry and a cross below Signal for an exit. This is an illustrative rule to test, not a recommendation or a reported profitable result.
Before implementation, fill in every remaining choice:
| Decision | Information to record |
|---|---|
| Market data | Symbol, feed, timeframe, session, adjustment settings, and dates |
| Indicator | Length, zero display offset, warmup, and missing-value handling |
| Entry | Closed-bar condition and first eligible execution time |
| Position | Sizing, pyramiding, and whether short positions are allowed |
| Exit | Crossover, stop, target, time exit, or a precisely defined combination |
| Costs | Commission, slippage, spread assumptions, and any financing cost relevant to the instrument |
A strategy that reverses on every opposite crossover is different from a long-only strategy that exits to cash. A stop evaluated intrabar is different from a close-only exit. TradingView's strategy documentation explains its broker emulator and execution settings; inspect individual fills before trusting aggregate results.
Compare filters with the same baseline
You might investigate requiring positive RVI for a long entry or a separate price-trend condition. Evaluate each addition separately while holding costs, dates, and exit logic fixed. Report the resulting trade count as well as returns and drawdown. A filter that removes losing trades in one sample can also remove future winners.
Do not infer that two indicators provide independent confirmation merely because their names differ. Both may be transformations of the same prices. Also avoid declaring a particular daily setting, instrument, or market regime best without a reproducible comparison.
Handle divergence timing explicitly
A regular bullish divergence compares a lower price low with a higher oscillator low; the bearish counterpart compares a higher price high with a lower oscillator high. The hard part is specifying the pivot rule and when each pivot is confirmed.
If a pivot requires later bars, the strategy must wait for those bars. Backdating a marker on the chart must not backdate the order. Decide how far apart pivots may be, which series selects them, and whether an additional trigger is required. Those choices can change results more than a small length adjustment.
Separate development from evaluation
Use one period to define and refine the rule. Freeze the final rule before evaluating a separate period. Record all settings tried, not just the best combination. If you subsequently use the evaluation results to tune the rule, that period has become part of development.
Inspect average wins and losses, costs, exposure, drawdown duration, and concentration in a few trades. Results depend on the sample and assumptions; a higher win rate alone does not establish better risk-adjusted performance. The earlier unsupported EUR/USD, SPY, and BTC examples are not used as evidence here.
Pineify's Visual Editor can help configure indicator conditions for a script. Review the generated source and validate its behavior in TradingView. Compilation establishes neither realistic fills nor a profitable strategy.
Does this article provide an RVI win rate?
No. It provides a reproducible testing protocol. A meaningful win-rate claim needs the exact rule, dataset, costs, and complete results.
Should a trend filter always improve RVI?
No. Treat it as a separate hypothesis and compare it against an unchanged baseline on independent data.
Can I enter at the historical divergence pivot?
Not if later bars were needed to confirm it. Signal availability must match what was knowable at the trading decision time.
