Why a Manually Calculated ATR May Differ from a Platform ATR

Summary

The example compares two daily stock volatility features: a manual calculation that takes the maximum of the day’s high-low range and the two gaps from the previous close, then applies a 14-period simple moving average; and the platform’s built-in ATR function using the same high, low, close, and period inputs. The author reports that the resulting values differ and shows a feature-extraction workflow over a January date range, with additional historical data requested before the start.

The post does not include the observed values, a platform response, or a resolution, so it does not establish which calculation convention caused the mismatch. It raises a useful validation question: matching the true-range definition and nominal period may not by itself ensure equivalent indicator outputs. Initialization, smoothing convention, history available to the calculation, or data handling would need to be checked, but the document does not confirm any of these as the cause.

Key ideas

• True range is described as the maximum of the high-low range and the gaps from the previous close.
• The example compares a 14-period simple moving average of true range with a built-in ATR function.
• The two calculated features reportedly do not match, but no values or explanation are supplied.
• Indicator validation may require checking calculation conventions and historical data handling.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.