The platform I’ve been using and building on since NT6.5. Setup, troubleshooting, and what makes it work.
Tooltips live in two places in a NinjaScript indicator. The first is the settings dialog — the small hover text that explains what a property does. The second is the chart itself — labels and annotations attached to drawn objects that show context when a trader hovers over them. Both are cheap to add, both…
The prior post built a single-hidden-layer neural network — three inputs, six tanh neurons in one hidden layer, one sigmoid output, 31 parameters. It worked because the hidden layer can compose the raw features into non-linear combinations that a single neuron cannot represent. The post closed with a hint: “add a hidden layer + backprop…
Most SuperTrend variants are deterministic: ATR × multiplier sets the band width and the trend flips when price closes the wrong side. LuxAlgo’s KNN Supertrend Horizon takes a different swing — it runs a k-nearest-neighbors classifier over recent (RSI, ATR%) feature space, votes on the next-bar SuperTrend direction, EMA-smooths the probability, and only flips when…
A polished indicator hides settings that don’t apply to the current state. When a ShowLabels bool is off, the LabelColor, LabelSize, and LabelFont properties should disappear from the grid — they’re irrelevant unless labels are enabled. Standard NinjaScript attributes don’t give you that directly. There’s no [Display(EnabledWhen = “ShowLabels”)]. Three workarounds do it. Each has…
The prior post built a single-neuron model — three weights, a bias, and a sigmoid that turned a weighted sum into P(up). It worked, but its limits were architectural: a single neuron can only carve the feature space with a straight line. Any pattern that requires the features to interact non-linearly — “high distFromMa AND…
Most oscillators give you one line that swings around a midpoint. The Andean Oscillator by alexgrover takes a different approach — it computes two lines, one tracking bull strength and one tracking bear strength, and lets the relationship between them tell you the regime. The math underneath is online recursive envelopes: instead of computing a…
A three-property indicator fits fine in NinjaTrader’s default “Parameters” bucket. A fifteen-property indicator doesn’t. Once an indicator has ATR inputs, confirmation thresholds, display toggles, color choices, and alert settings, the property grid needs real structure — otherwise users scroll past the setting they actually wanted to change. Last week’s post introduced [Display(GroupName, Order)] and [Gui.CategoryOrder]….
The k-Nearest Neighbors post introduced one half of supervised learning: memorizing models that hold onto every historical bar and search through them at prediction time. This post is the other half. Instead of remembering every example, an online-learning model carries a small set of weights — three numbers, plus a bias term, in this case…
Most trend indicators give you a binary answer: up or down, with maybe a third ‘neutral’ state. That’s useful — but it throws away the most actionable piece of information, which is how confident the indicator is in that call. ChartPrime’s Bayesian Trend Indicator reframes the question as a probability: given the last N bars…
A property’s C# identifier isn’t always what you want users to see in the indicator settings dialog. Period reads fine; atrPeriodLookback looks like a raw variable name. The [Display] attribute lets you set a friendlier label, add a tooltip, group related properties together, and control the order they appear. Four parameters cover almost all of…
Notifications
