Skip to content

OCPriceRSI

Ehlers DSP oscillator rsi ehlers momentum

RSI calculated using the average of Open and Close prices to reduce noise.

Visual Example

OCPriceRSI — annotated preview mapping to core implementation

Synthetic ideal per library logic. Generated 2026-06-25 IST via docs/generate_all_previews.py (reproducible; maps to core Next<T> implementation).

Description

The OCPriceRSI indicator is a technical analysis tool that rsi calculated using the average of open and close prices to reduce noise.

This indicator is primarily used for identifying key market conditions. It provides a robust signal that can be easily integrated into both simple strategies and more complex machine learning feature pipelines. Compared to its alternatives, it offers a distinct balance of responsiveness and stability.

Traders often combine this with other metrics to confirm signals and avoid false positives during sideways market regimes. It remains a standard tool for systematic trading models.

Use to measure momentum on the open-to-close price differential rather than close-to-close, capturing intraday directional strength more directly.

Ehlers computes this RSI variant on the difference between the open and close price of each bar rather than on the closing price series. The open-close differential captures the net directional pressure within each bar, producing a momentum oscillator more sensitive to intraday commitment than standard RSI.

QuantWave implements this indicator via the universal Next<T> trait, guaranteeing bit-identical results between Rust streaming, Python streaming, and Polars batch (.ta() / map_batches) surfaces.

Formula / Specification

Implementation (quantwave-core/src/indicators/oc_price_rsi.rs):

[ Input = \frac{Open + Close}{2} ] [ RSI = \text{Wilder's RSI}(Input, Period) ]

Gold-standard parity vectors: quantwave-core/tests/gold_standard/oc_price_rsi.json.

Parameters

Parameter Default Description
period 14 RSI period

Usage Examples

Streaming (Rust)

use quantwave_core::indicators::OC_PRICE_RSI;
use quantwave_core::traits::Next;

let mut ind = OC_PRICE_RSI::new(14);
for price in &prices {
    let value = ind.next(price);
}

Streaming (Python)

from quantwave import OC_PRICE_RSI

ind = OC_PRICE_RSI(14)
for price in prices:
    value = ind.next(price)

Polars Batch (Python)

import polars as pl
import quantwave as qw

def apply_ocpricersi(series: pl.Series) -> pl.Series:
    ind = qw.OC_PRICE_RSI(14)
    return pl.Series([ind.next(float(v)) for v in series.to_list()])

df = (
    pl.read_csv('ohlcv.csv')
    .lazy()
    .with_columns(
        pl.col("close").map_batches(apply_ocpricersi, return_dtype=pl.Float64).alias("ocpricersi")
    )
    .collect()
)

All surfaces are bit-identical via the single Next<T> implementation and proptests.

Edge Cases & Limitations

  • Recursive DSP filters require a warm-up period; first N bars may be unstable or raw-pass-through.
  • Designed for cyclic/mean-reverting regimes; trending markets can produce lag or drift.
  • Parameter period (or equivalent) controls cutoff — too small adds noise, too large adds lag.
  • Prefer chaining with other Ehlers tools (Roofing Filter, SuperSmoother) on noisy inputs.
  • Validated via proptests against gold-standard vectors where available.
  • No look-ahead bias; suitable for live streaming and batch feature pipelines.

Boundary Behavior

Condition Behavior
Warm-up Leading bars return NaN until warmup_bars is satisfied.
period > len When period exceeds series length, output is all NaN.
NaN inputs NaN in input propagates to output (NaN out).
Invalid params Non-positive period or missing required params raise ValueError.
Empty data Empty input returns an empty result series.

Sources & References

Primary Source: https://github.com/lavs9/quantwave/blob/main/references/Ehlers%20Papers/EveryLittleBitHelps.pdf

Implementation: quantwave-core/src/indicators/oc_price_rsi.rs (OC_PRICE_RSI / OC_PRICE_RSI_METADATA). Parity: quantwave-core/tests/gold_standard/oc_price_rsi.json

Provenance: Standards bulk upgrade 2026-06-25 IST — see docs/DOCUMENTATION_STANDARDS.md.