Pipsgrowth EX16078 Trend

Pipsgrowth EX16078 is a smoothed trend-following EA built around four custom indicators computed in-process rather than fetched through iHandles. The core stack is a Hull Moving Average of period 20 whose slope is fed into a Linear Regression of period 14, the resulting regression slope is normalized by an ATR(14) to dampen volatility noise, and the whole signal is gated by a Choppiness Index(14) that suppresses entries whenever the CI reading is above 61.8. The net effect is an engine that only opens trend positions when price is actually moving directionally and the recent range structure is non-rotational.

The HMA itself is constructed by hand in CalculateHMA(): a WMA of the close over the full period, a second WMA over half the period, a doubled difference (2·WMA_half − WMA_full), and a final WMA over √N of that difference array. The output is a curve that lags price by about half the period of a normal WMA but still smooths enough to suppress whipsaw. CalculateLRSlope() then takes the most recent 14 HMA points and runs a least-squares fit, returning the slope of the regression line. Divide that slope by the current ATR(14) value to get the normalized slope, the only directional feature the engine actually trades on. ATR is rebuilt in CalculateATR() using the high/low and previous-close True Range, then smoothed with a Wilder-style running average.

The Choppiness Index is the regime classifier. Over a 14-bar window it sums the ATR values, captures the high-low range of the same window, and returns 100·log10(ΣATR/range)/log10(period). When CI sits above 61.8, the market is in a chop — neither a clean trend nor a clear range. GetSignal() therefore returns 0 (no trade) in that state, regardless of slope direction. When CI falls back below 61.8 and the normalized slope is positive, the engine returns a buy signal of +1; when slope is negative it returns −1. The shift inside the engine is fixed at 0 because the internal arrays are updated from closed bar[1] data, so the signal is decision-ready on the open of bar[0] and the engine has not bar-snooped.

Each new tick OnTick checks for a new bar and pushes the closed bar[1] close/high/low into the engine's circular buffers via UpdateData(). The HMA, slope and CI values are recomputed and stored at their respective offsets. The trade logic that follows is split into two blocks: a close block and an open block. If the signal flips to −1 and there is at least one open BUY, CloseAllTrades(POSITION_TYPE_BUY) is invoked, which iterates the position list and calls TryClose_EX16078 on each ticket. TryClose_EX16078 wraps trade.PositionClose in a 3-attempt loop that retries on requote, timeout, price-off and price-changed retcodes with a 200ms sleep between attempts. The reverse path runs identically for sell positions when signal flips to +1.

The open block enforces a position cap and an optional pyramiding rule. When the signal is +1 and no BUY is open, OpenTrade(ORDER_TYPE_BUY) fires; the order is sized by CalculateLotSize() to risk exactly 1% of account balance against the fixed 300-point StopLoss_Points distance, snapped to the symbol's lot step. If pyramiding is enabled and the BUY count is below MaxOpenTrades (3 by default), the engine checks the most recent open BUY's profit converted into points; when that profit-in-points exceeds PyramidingStep_Points (200), a second (and eventually third) BUY is layered in. The pyramid rule is the same on the sell side. The open path also runs CheckSpread() at the top, blocking any new order if the symbol spread is above MaxSpread_Points (30) and printing a Spread Filter block message to the Experts log.

The session gate is a string-based filter. The TradingHours input defaults to '08:00-20:00' and is parsed by GetStartHour/GetStartMinute/GetEndHour/GetEndMinute into a minutes-of-day range; IsTradingTime() returns true only when the current server clock is inside that window. When outside the window OnTick returns early after the dashboard update, so the engine still tracks state but does not open or close positions — useful for traders who want to keep the dashboard visible around the clock while letting the EA act only during a defined band. The dashboard itself is a 200x160 black panel anchored at the top-left of the chart, displaying the current signal (WAIT/BUY/SELL in blue or red), the cumulative P/L across all positions on the chart symbol, and the current HMA period. Two buttons labeled [+] and [−] live under the period label: clicking [+] increments g_HMA_Period and calls ReinitializeEngine() to rebuild the engine's buffers from history with the new period; clicking [−] decrements it down to a floor of 2. A red CLOSE ALL button is wired to flatten both sides at once.

What sets EX16078 apart from a vanilla MA-crossover is the dual smoothing on the slope side: the HMA removes the bar-to-bar jitter of a raw price MA, and the regression line over 14 HMA points removes whatever jitter the HMA still carries. The Choppiness Index then acts as a permission gate so the engine does not enter every micro-twitch in a sideways tape. Expect a low trade frequency, frequent small losses in chop, and a sequence of larger winners when a clean H1 or M5 trend develops during the 08:00-20:00 window. The risk per trade is fixed at 1% of equity through a 300-point stop, with a 600-point take-profit giving a 1:2 reward-to-risk on every fresh entry, and the same SL/TP is applied to the pyramid legs. For backtesting, be aware that the engine processes one bar per new-bar tick and updates the dashboard on every tick, so visualizer performance is well within MT5's tolerance; just remember that magic 22216078 is hard-coded into the comment 'Psgrowth.com Expert_16078' which appears on every order.