Technical Ratings in Pineify: Weights, Timing, and Display Limits
Pineify's Technical Ratings indicator combines moving-average and oscillator ratings from TradingView's TechnicalRating library. The result summarizes technical conditions. It is not a calibrated probability of a profitable trade or a guarantee that a buy/sell label will predict the next move.
What the wrapper calculates
The implementation imports TradingView/TechnicalRating/3. It obtains separate moving-average and oscillator ratings, then combines them using the selected MA weight. With both groups selected, a weight of 50 gives equal group contribution. That does not mean every individual indicator has an equal contribution across the two groups.
The combined calculation applies zero substitution to unavailable weighted group values. Inspect warmup behavior rather than treating an early displayed value as a complete set of populated inputs.
| Setting | Current default or meaning |
|---|---|
| Rating Uses | 0 for combined, 1 for moving averages, 2 for oscillators |
| Weight of MAs | 50%; affects the combined mode |
| Higher Timeframe | Chart by default |
| Repainting | Enabled by default |
| Rating output | Selected combined or group score |
Keep the MA weight within its intended 0 to 100 range. The function converts it to a fraction without clamping it; values outside that range no longer represent a conventional weighted average. The usual minus-one to plus-one interpretation assumes valid weights and library inputs.
Thresholds are conditions, not forecasts
The wrapper treats a rating above 0.1 as buy bias and below minus 0.1 as sell bias. At exactly either threshold, its respective strict inequality is false. Drawing reference lines also appear at plus/minus 0.5 and zero.
A score above a threshold can persist. A crossover is a separate event that occurs when the series moves through the threshold. Decide which condition your strategy needs; otherwise an apparently simple rating filter can generate a different set of trades than intended.
Verify timeframe timing
With Chart selected and Repainting enabled, the wrapper uses the current requested rating. With Chart selected and Repainting disabled, it uses the prior requested value. The current realtime bar may therefore behave differently between those settings.
Selecting a nonempty timeframe activates a different historical/realtime indexing branch around request.security. The code checks whether the timeframe is nonempty; that alone does not prove it is higher than the chart. Verify the chosen interval and compare live values with the chart after reload. Do not assume every timeframe selection is an interchangeable non-repainting mode.
For the underlying data-request rules, consult TradingView's other-timeframes documentation. A stable display and a timely signal are separate properties: waiting for confirmation changes when information is available.
The current drawing implementation uses columns
The configuration includes Plot Style and Width inputs, but the current drawing function plots columns and takes width from its drawing-line settings. The calculation's plot-style and width arguments do not change that plot. Do not expect selecting the numeric Plot Style input alone to switch the generated chart to a line or area.
The plot color is selected from bullish, bearish, and neutral colors based on the sign of the internal gradient value. It is not a continuous strength scale in this drawing implementation. Inspect the numeric rating rather than inferring a probability from color intensity.
Build and evaluate a filter
Select Technical Ratings in Pineify's Visual Editor, use supported parameters, generate the source, and compile it in TradingView. Compare values and timing before combining the rating with entries and exits.
If you add RSI or a moving average as confirmation, recognize that similar calculations may already contribute to the composite. More conditions do not automatically provide independent evidence or improve returns. Compare the complete strategy with and without the added filter using the same dates, costs, and sizing.
Does 0.5 mean a 50% chance of winning?
No. It is a composite technical score, not an estimated probability of a trade outcome.
Does the MA weight affect oscillator-only mode?
The weight belongs to the combined score. Oscillator-only mode selects the oscillator group directly.
Why does changing Plot Style still produce columns?
The current drawing function explicitly uses columns. The numeric input is not wired to that plotting choice.
