WAE Waddah Attar Explosion Scanner Multi Pair TF
- 指标
- 版本: 1.0
- 激活: 5
Overview and Architectural Design of the Dashboard Utility
The WAE Scanner Dashboard is a highly advanced, multi-dimensional technical analysis utility and graphical dashboard explicitly engineered for the MetaTrader 5 terminal. Its primary operational objective is to conduct simultaneous, parallel scanning of multiple financial instruments across various timeframes to identify, calculate, and project potential momentum breakout zones. The core analytical engine is strictly based on the Waddah Attar Explosion (WAE) mathematical algorithm, which cross-references momentum acceleration against market volatility bandwidths. Unlike conventional single-chart indicators, this utility aggregates market data arrays into a centralized, interactive graphical user interface, allowing technical analysts to monitor structural market shifts without transitioning between dozens of individual chart windows. To ensure the highest level of signal integrity and to prevent premature market entries, the dashboard is equipped with an architectural layer of 17 distinct technical validation filters, dynamic Average True Range (ATR) volatility risk management calculations, and a robust notification distribution system. The software functions exclusively as an analytical data processing tool and does not execute automated trading operations.
Operating Principle and Core Mathematical Algorithm
The fundamental mathematical algorithm driving this utility is the Waddah Attar Explosion logic. The system continuously evaluates two primary market forces: Trend Power (Directional Momentum) and Explosion Power (Volatility Bandwidth). The Trend Power is calculated by extracting the differential between the current and previous values of a Moving Average Convergence Divergence (MACD) main line, scaled by a user-defined sensitivity multiplier. The Explosion Power is derived by calculating the absolute distance between the upper and lower limits of the Bollinger Bands indicator. A baseline filter, known as the DeadZone, is also projected to filter out periods of market consolidation or low liquidity. For a signal to be mathematically valid, the MACD momentum differential must physically exceed the Bollinger Band width expansion, and both values must independently clear the minimum point threshold established by the DeadZone limit. The system also calculates historical percentage acceleration to measure momentum bursts, comparing the rate of change between consecutive bars to satisfy minimum threshold requirements.
Signal Validity, Entry Logic, and Strict Non-Repaint Characteristics
Transparency regarding signal calculation is a mandatory operational standard. All momentum cross calculations, filter validations, and signal generations executed by this dashboard are evaluated strictly on closed historical data, specifically targeting Bar index 1 (the last fully closed candlestick). The internal engine does not process intra-bar fluctuations (Open Bar 0) to trigger preliminary alerts. Consequently, the signals generated by this software are strictly categorized as 100% Non-Repainting. Once a signal is projected onto the dashboard matrix and the corresponding visual artifacts (arrows and projection lines) are rendered on the chart, their coordinates, timestamps, and directional biases are permanently locked and will not recalculate, shift, disappear, or modify their position regardless of subsequent market volatility.
The precise Entry Logic dictates that a BUY signal is formally registered when the MACD differential returns a positive value, mathematically exceeds the current Bollinger Band differential, clears the DeadZone threshold, and simultaneously passes all active auxiliary technical filters. Conversely, a SELL signal is formally registered when the MACD differential returns a negative value, its absolute numerical value mathematically exceeds the Bollinger Band differential, it clears the DeadZone, and validates against the active bearish filter conditions.
Technical Specifications and Execution Environment Recommendations
To maintain optimal terminal stability, users must configure the hardware resource allocation appropriately. The utility continuously loops through data arrays utilizing functions like CopyBuffer and CopyRates. Recommended deployment pairs include major liquid symbols such as EURUSD, GBPUSD, USDJPY, AUDUSD, USDCAD, USDCHF, NZDUSD, EURJPY, GBPJPY, and XAUUSD. The software mathematically supports all standard timeframes, though analytical reliability increases on M15, M30, H1, H4, and D1 periods. Users operating on hardware with limited CPU thread counts or restricted RAM capacities must strictly control the matrix size by limiting the maximum allowed symbols and reducing the historical bar copying depth to prevent terminal unresponsiveness. The software is compatible with both Hedging and Netting account structures. Standard ECN environments with minimal spread variations are highly recommended to ensure the mathematical accuracy of the dynamic Stop Loss and Take Profit projections.
Comprehensive Documentation of Input Parameters and System Configuration
[=== Scanner Settings ===]
This parameter group dictates the overarching data handling and memory allocation framework of the scanning engine. The parameter [InpSymbols] accepts a comma-separated string array of financial instruments (e.g., EURUSD,GBPUSD) dictating exactly which pairs the engine will initialize. The [InpTimeframes] variable requires a comma-separated format (e.g., M5,M15,H1) to specify the periodic charts loaded into the matrix. Setting [InpUseWatch] to true forces the algorithm to bypass the manual string input and dynamically extract all visible symbols currently active in the MetaTrader Market Watch window. To prevent critical memory overload during this dynamic extraction, [InpMaxSymbols] establishes a hard coded limitation on the maximum number of pairs processed simultaneously (defaulted at 10). The [InpScanSec] variable dictates the frequency of the main scanning loop in seconds, throttling CPU utilization. [InpBarsCopy] manages memory footprint by defining the exact integer of historical candlesticks loaded into RAM per symbol, per timeframe. [InpLookback] specifies the specific bar depth the algorithm will analyze to locate a recent Waddah Attar momentum cross. The [InpDirection] variable allows users to physically lock the engine to scan for bidirectional signals (0), strictly bullish conditions (1), or strictly bearish conditions (2).
[=== WAE Core Settings ===]
This module houses the variables that formulate the baseline mathematical equation of the Waddah Attar Explosion algorithm. [Fast_MA] and [Slow_MA] define the exponential moving average periods utilized by the internal MACD engine to compute the histogram's directional bias. [BBPeriod] and [BBDeviation] construct the volatility envelope, establishing the baseline period and the standard deviation multiplier applied to the closing prices. The [Sensetive] multiplier is a scalar integer (default 150) applied directly to the MACD histogram differential to align its scale with the Bollinger Band pricing format. [DeadZonePip] represents a physical point barrier (converted from pips) that both trend and explosion variables must exceed, effectively eliminating low-volatility flat markets. [UsePowerFilter] activates a strict percentage-based acceleration check. When active, [ExplosionPower] sets the minimum percentage increase required for the Bollinger bandwidth compared to the previous bar, while [TrendPower] dictates the minimum percentage growth required for the MACD momentum differential, ensuring entries only occur during periods of expanding volatility.
[=== ATR SL & TP Settings ===]
Risk management levels are not static; they are dynamically projected using Average True Range arrays. [InpATRPeriod] sets the baseline evaluation length for measuring recent bar volatility. [InpATRMultSL] acts as a mathematical multiplier against the current ATR value, establishing the defensive Stop Loss distance from the execution coordinate. [InpTP1_RR] and [InpTP2_RR] define the risk-to-reward ratios for the first and second profit targets. For example, a value of 2.0 projects a Take Profit zone exactly twice the distance of the calculated Stop Loss zone.
[=== Detailed Mechanics of the 17 Auxiliary Validation Filters ===]
The architecture contains 17 independent algorithmic filters. When activated, a signal must pass the Boolean true/false evaluation of EVERY active filter simultaneously to be printed on the dashboard.
Filter 1: RSI Cross. Activated by [Use_RSI_Cross_Filter]. It calculates Relative Strength Index based on [RSI_Length] and [RSI_Price_Source]. A bullish condition requires the RSI at bar 1 to be greater than the [Oversold] limit while bar 2 was below it, signaling an upward cross. Bearish conditions require a downward cross of the [Overbought] limit.
Filter 2: Average Directional Movement (ADX). Activated by [Use_ADX_Filter], utilizing [ADX_Period]. It acts as a pure trend strength confirmation, requiring the main ADX line to physically exceed the numerical value of [ADX_Min_Level] for both buy and sell directions.
Filter 3: Single Moving Average. Activated by [Use_MA_Filter]. Uses [MA_Period], [MA_Method], [MA_Applied], and [MA_Shift] to plot a trend line. Bullish validity requires the closing price to remain strictly above this calculated average, whereas bearish validity requires the closing price to remain below it.
Filter 4: Ichimoku Kinko Hyo. Activated by [Use_Ichimoku_Filter]. It calculates the structural baseline using [Ichimoku_SenkouB] and [Ichimoku_Kijun]. The system validates long bias only if the current price is projected above the Senkou Span B cloud line, and short bias if positioned below it.
Filter 5: Long-Term RSI Bias. Activated by [Use_RSI75_Filter] using [RSI_Filter_Period] and [RSI_Filter_Price]. Unlike the crossover filter, this simply measures structural momentum bias, demanding RSI to hold above 50.0 for buys and below 50.0 for sells.
Filter 6: Double Moving Average Alignment. Activated by [Use_DoubleMA_Filter]. Requires two separate MAs defined by [MA_A_Period] and [MA_B_Period], along with their respective method and price variables. Validates bullish conditions exclusively when MA 'A' is numerically greater than MA 'B', representing an upward momentum alignment.
Filter 7: Awesome Oscillator Dynamics. Activated by [Use_AO_Filter]. Contains sub-modules. [Use_AO_Volume_Filter] demands AO values clear [AO_Buy_Min] or drop below [AO_Sell_Max]. [Use_AO_Color_Filter] strictly requires the AO histogram to show an increase in absolute momentum compared to the previous bar. [Use_AO_Zero_Filter] restricts validation to signals where the AO histogram is located on the correct side of the zero median line.
Filter 8: Parabolic SAR Acceleration. Activated by [Use_SAR_Filter]. Utilizes [SAR_Step] and [SAR_Maximum] to plot acceleration dots. Bullish entries demand the closing price remain above the SAR coordinate, while bearish entries require price to drop below it.
Filter 9: Heiken Ashi Structural Smoothing. Activated by [Use_HeikenAshi_Filter]. The algorithm mathematically recalculates standard candlesticks into smoothed data where the Close is the average of Open, High, Low, and Close, and the Open is the midpoint of the previous bar. It validates bullish momentum if the smoothed Close is higher than the smoothed Open.
Filter 10 and 11: Commodity Channel Index (CCI) Variations. [Use_CCI_Filter] establishes a long-term directional bias using [CCI_Period] and [CCI_Applied], filtering for values strictly above or below zero. Concurrently, [Use_CCI_OBOS_Filter] measures short-term exhaustion using [CCI_OBOS_Period], demanding the value exceeds [CCI_Overbought] or drops past [CCI_Oversold] to validate momentum entries.
Filter 12 and 13: Relative Vigor Index (RVI) Validation. [Use_RVI_Filter] uses [RVI_Period] to ensure the primary index resides above or below the zero axis. [Use_RVI_Signal_Filter] utilizes [RVI_Signal_Period] to enforce a strict crossover requirement between the primary index line and its calculated signal line.
Filter 14 and 15: Standard MACD Confirmation. [Use_MACD_Filter] uses [MACD_FastEMA], [MACD_SlowEMA], and [MACD_SignalSMA] with [MACD_Applied] to calculate a secondary MACD. It checks if the primary line is greater than the signal line. [Use_MACD_Zero_Filter] enforces a strict rule where the primary MACD line must be structurally positioned above or below the zero equilibrium level.
Filter 16: Dynamic Support and Resistance Validation. Activated by [Use_SR_Filter]. It scans a historical window defined by [SR_Period] to calculate extreme high and low swing coordinates. If the current price action touches these boundaries within a variance defined by [SR_Zone_Points], the directional signal is validated as a legitimate structural bounce.
Filter 17: Fibonacci Retracement Confluence. Activated by [Use_Fib_Filter]. This complex module uses ZigZag logic defined by [ZigZag_Depth], [ZigZag_Deviation], and [ZigZag_Backstep] to calculate primary swing nodes. It measures the vector distance between these nodes and projects mathematical zones at [Fib_Level_1] and [Fib_Level_2]. Signals are only approved if the current candlestick intersects this calculated golden ratio zone.
[=== Alerts System Configuration ===]
The notification routing framework distributes alert data across multiple protocols. [InpAlertPopup] triggers the native MetaTrader dialog box upon signal validation. [InpAlertSound] triggers local audio hardware to play the file specified in [InpSoundFile]. [InpAlertPush] routes the data array to mobile devices registered with a MetaQuotes ID via the network server. [InpAlertEmail] uses the terminal's SMTP configuration to dispatch messages prefixed with the [InpEmailSubject] string. [InpAlertOnlyNew] is a crucial rate-limiting Boolean; when active, it forces the engine to log the timestamp of the last alert and blocks subsequent notifications for the same symbol and timeframe until a new historical bar is formed, preventing alert flooding during volatile sideways ranges.
[=== Display, Layout, and Sorting Mechanics ===]
The graphical user interface is constructed using dynamic object rendering. [InpX] and [InpY] define the absolute origin coordinates in pixels on the chart canvas. [InpScale] provides responsive resizing capabilities (restricted between 70 and 180 percent) for high-resolution displays. Structural dimensions are defined by [InpRowH] for row height and [InpFont] for typographic scaling. The horizontal matrix spacing is rigidly defined by specific width integers including [InpWPair], [InpWTF], [InpWArah], [InpWTime], [InpWEntry], [InpWSL], [InpWTP1], [InpWTP2], [InpWWAE], [InpWUmur], and [InpWOpen], which calculate the bounding box for each data column. [InpShowEmpty] is a Boolean parameter that decides whether the dashboard retains empty rows for pairs currently lacking mathematical validation, or dynamically collapses them to save screen real estate. [InpMaxRows] acts as a vertical boundary, terminating rendering loops once the integer limit is reached. The internal sorting algorithm is governed by [InpSortBy], allowing data alignment based on Time, Pair, Timeframe, or Direction hierarchies, while [InpSortNewest] dictates whether the array is parsed in ascending or descending mathematical order. Global variables are utilized to cache GUI coordinate states during terminal reinitialization.
[=== Chart Signal Visuals & UI Color Arrays ===]
This module handles the projection of artifacts onto the active chart window. [InpDrawOnChart] grants permission to render mathematical objects. [InpShowArrow] plots graphical vectors indicating the precise entry bar, utilizing Wingdings typographic codes defined in [InpArrowCodeBuy] and [InpArrowCodeSell], spaced from the wick by a multiplier in [InpArrowDistance] and sized by [InpArrowSize]. [InpShowLevels] forces the mathematical rendering of horizontal trendlines projecting the Entry, Stop Loss, and Take Profit coordinates forward in time by a bar length defined in [InpExtendBars]. The aesthetic color palette of the entire utility is fully exposed to user modification. The hexadecimal or predefined color constants are injected into parameters such as [InpColBg] for the application background, [InpColHead] for structural headers, [InpColRow] and [InpColRow2] for alternating row visibility, [InpColText] for typographic elements, [InpColBull] and [InpColBear] for directional bias formatting, [InpColMute] for deactivated elements, [InpColAccent] for primary interactive highlights, and [InpColEntry], [InpColSL], [InpColTP1], [InpColTP2] for the respective on-chart visual trendlines and data coordinates.
Risk Disclaimer
Trading foreign exchange, commodities, derivatives, and other leveraged financial instruments involves substantial potential for capital loss and is mathematically not suitable for all investors or capital profiles. Past historical performance, including computational backtesting data generated by analytical indicators, fundamentally does not guarantee, predict, or mathematically secure future financial results. This specific software architecture is strictly an analytical, mathematical, and operational data processing tool designed exclusively to assist technical analysts in visualizing market calculations; it does not serve as direct financial advice, nor does it guarantee any form of financial profit or capital protection. Users must accept all associated market risks and are strictly instructed to thoroughly test the product's algorithmic functionality, parameter sensitivity, and latency performance exclusively on a simulated demonstration account environment to fully comprehend its operational behavior before evaluating any consideration for deployment in live, capitalized trading environments.
