Wedgepatterns — อินดิเคเตอร์และกลยุทธ์

Breakout Patterns Detector: Triangle & Wedge [Splirus]This indicator identifies Breakout Patterns such as Ascending Triangles , Descending Triangles , Symmetric Triangles , Ascending Wedges , and Descending Wedges , using candlestick charts and Trendlines. It provides visual cues, stop-loss (SL), and take-profit (TP) levels, alongside a detailed dashboard to evaluate performance. The indicator supports two alert modes: Manual Mode for trader notifications and Bot Mode for automated trading signals. To achieve optimal results, users are encouraged to experiment with indicator parameters and analyze the dashboard summary to find the perfect configuration for each timeframe, pair, and market condition. Pattern Identification The indicator detects the following breakout patterns based on pivot highs and lows: Ascending Triangle : Flat upper trendline, rising lower trendline. Descending Triangle : Flat lower trendline, declining upper trendline. Symmetric Triangle : Converging trendlines with similar slopes (within a user-defined threshold). Ascending Wedge : Both trendlines slope upward, converging. Descending Wedge : Both trendlines slope downward, converging. Patterns are identified using configurable left and right bars for small and big patterns, with slope thresholds normalized by ATR. A trend confirmation filter ensures breakouts align with market direction, and users can adjust breakout confirmation bars to validate signals. The goal is to fine-tune these settings to suit specific timeframes and pairs, as each combination may require a unique setup for optimal performance. Stop-Loss Calculation Stop-loss levels are calculated dynamically based on pattern type and breakout direction: Symmetric Triangle : SL is set at the first pivot of the opposite trendline, adjusted by a buffer percentage. Ascending/Descending Triangle : SL is placed at the breakout trendline’s price, plus the buffer. Ascending/Descending Wedge : SL is set at the second pivot of the opposite trendline, adjusted by the buffer.   The indicator calculates leverage based on a user-defined risk tolerance percentage. Users should adjust the SL buffer and risk tolerance to balance risk and reward, monitoring the dashboard to assess how these settings impact performance across different timeframes and pairs. Take-Profit Calculation Three take-profit levels ( TP1 , TP2 , TP3 ) are calculated using pattern height and user-defined multipliers: For Ascending/Descending Triangles, height is the difference between the max and min prices within the pattern. For Symmetric Triangles and Wedges, height is the vertical distance between trendlines at the pattern’s start. TP levels are set as: TP1 = Breakout price ± (Height × TP1 Multiplier). TP2 = Breakout price ± (Height × TP2 Multiplier). TP3 = Breakout price ± (Height × TP3 Multiplier, with a 1.5x adjustment for Wedges).  Experiment with TP multipliers to optimize the risk-reward ratio, using the dashboard to evaluate TP hit rates and overall profitability for each configuration. Symmetric Triangle: Ascending/Descending Wedge: Ascending/Descending Triangles: Finding the Perfect Configuration The indicator’s dashboard provides a comprehensive summary of performance metrics, including total trades, TP1/TP2/TP3 hits, SL hits, profit/loss percentages, and win rates for bullish, bearish, and combined trades. These metrics are crucial for identifying the ideal parameter settings: Timeframe and Pair Variability : Each timeframe (e.g., 15m, 30min, 1H, 4H, Daily) and pair (e.g., BTC/USD, EUR/USD) behaves differently. Adjust parameters like left/right bars, minimum pattern length, and breakout confirmation bars to match the volatility and trend characteristics of the chosen pair and timeframe. Parameter Tuning : Modify slope thresholds, trend confirmation filters, and bars inside the pattern to filter out false breakouts. For example, a higher breakout confirmation bar setting may reduce signals but increase reliability on longer timeframes. Dashboard Analysis : Focus on the dashboard’s win rate, profit/loss ratio, and TP/SL hit frequencies. A “Perfect” win rate (>66%) or high TP hit rate indicates a strong configuration. If the SL hit rate is high, consider tightening the trend confirmation filter or increasing the SL buffer. Iterative Testing : Test different combinations of settings (e.g., small vs. big patterns, aggressive vs. conservative breakout confirmation) and compare dashboard results over time. The goal is to find a balance where the indicator consistently delivers high win rates and profitability for your specific trading setup. Alert Modes The indicator supports two alert modes to suit different trading styles: Manual Mode : Generates alerts for breakouts with entry price, SL, TP1/TP2/TP3, and leverage, tailored for Crypto or Forex markets. Use this mode to manually evaluate signals while refining configurations. Bot Mode : Sends automated trading signals. To avoid conflicts, Bot Mode ensures no short position alert is triggered while a long position is active, and vice versa. This mode is ideal once you’ve identified an optimal configuration via the dashboard. Additional Features Historical Patterns : Displays past trendlines with customizable transparency and extension, helping users analyze how patterns performed under different settings. Customizable Settings : Adjust pattern size, breakout confirmation, trend filters, and visual preferences (colors, dashboard location) to match your trading style. Market Compatibility : Supports Crypto and Forex markets across all timeframes, but requires careful tuning for each market type. Usage Notes Start with default settings and monitor the dashboard to establish a baseline performance for your chosen timeframe and pair. Gradually adjust one parameter at a time (e.g., left/right bars, TP multipliers) and compare dashboard results to identify improvements. Use historical pattern analysis to understand how past breakouts performed under different configurations, guiding your optimization process. Once a high win rate and profitability are achieved, consider automating trades with Bot Mode for consistent execution. Disclaimer This indicator is intended for educational purposes only and should not be considered financial advice. Trading involves significant risk, and past performance is not indicative of future results. Users are strongly advised to thoroughly test and validate the indicator’s signals in a demo environment before using it in live trading. The author is not responsible for any financial losses incurred while using this indicator. Always conduct your own research and consult with a qualified financial advisor before making trading decisions.

divergingchartpattern Library "divergingchartpattern" Library having implementation of converging chart patterns getPatternNameByType(patternType) Returns pattern name based on type Parameters: patternType (int) : integer value representing pattern type Returns: string name of the pattern method find(this, sProperties, dProperties, patterns, ohlcArray) find converging patterns for given zigzag Namespace types: zg.Zigzag Parameters: this (Zigzag type from Trendoscope/ZigzagLite/2) : Current zigzag Object sProperties (ScanProperties) : ScanProperties Object dProperties (DrawingProperties type from Trendoscope/abstractchartpatterns/5) : DrawingProperties Object patterns (array type from Trendoscope/abstractchartpatterns/5) : array of existing patterns to check for duplicates ohlcArray (array type from Trendoscope/ohlc/1) : array of OHLC values for historical reference Returns: string name of the pattern ScanProperties Object containing properties for pattern scanning Fields: baseProperties (ScanProperties type from Trendoscope/abstractchartpatterns/5) : Object of Base Scan Properties convergingDistanceMultiplier (series float)

Three Drive [TradingFinder] 3 Drive Harmonic Pattern Indicator 🔵 Introduction The "Three Drive" pattern is one of the light "RTM" setups suitable for identifying price trend reversals. For this reason, this pattern is considered one of the "Reversal Patterns." 🟣 Bullish 3 Drive At a price bottom, a formation occurs where the negative trend appears to continue, and lower lows are made. However, the second low penetrates the range of the first low, and the third low penetrates the range of the second low, indicating a decrease in selling pressure and an increase in buying pressure. Entry point is issued after the penetration of the third low to the second low, and targets are the highs formed in the "3 Drive." 🟣 Bearish 3 Drive At a price top, a formation occurs where the positive trend appears to continue, and higher highs are made. However, the second high penetrates the range of the first high, and the third high penetrates the range of the second high, indicating a decrease in buyers' strength and an increase in sellers' strength. Entry point is issued after the penetration of the third high to the second high, and targets are the lows formed in the "3 Drive." Importance : This pattern bears a striking resemblance to the some of "Harmonic Pattern" and "Ending Diagonal" in the "Elliott Pattern". 🔵 How to Use There is no need for further confirmation to use this pattern, and you can use it as soon as the pattern forms. However, to reduce errors, it is better to use this pattern when it forms within a "Supply and Demand" or "Support and Resistance" structure. Bullish 3 Drive in Demand Zone : Bearish 3 Drive in Supply Zone : 🔵 Settings You can set your desired "Pivot Period" via settings for the indicator to identify setups based on it.

chartpatterns Library "chartpatterns" Library having complete chart pattern implementation method draw(this) draws pattern on the chart Namespace types: Pattern Parameters: this (Pattern) : Pattern object that needs to be drawn Returns: Current Pattern object method erase(this) erase the given pattern on the chart Namespace types: Pattern Parameters: this (Pattern) : Pattern object that needs to be erased Returns: Current Pattern object method findPattern(this, properties, patterns) Find patterns based on the currect zigzag object and store them in the patterns array Namespace types: zg.Zigzag Parameters: this (Zigzag type from Trendoscope/ZigzagLite/2) : Zigzag object containing pivots properties (PatternProperties) : PatternProperties object patterns (Pattern ) : Array of Pattern objects Returns: Current Pattern object PatternProperties Object containing properties for pattern scanning Fields: offset (series int) : Zigzag pivot offset. Set it to 1 for non repainting scan. numberOfPivots (series int) : Number of pivots to be used in pattern search. Can be either 5 or 6 errorRatio (series float) : Error Threshold to be considered for comparing the slope of lines flatRatio (series float) : Retracement ratio threshold used to determine if the lines are flat checkBarRatio (series bool) : Also check bar ratio are within the limits while scanning the patterns barRatioLimit (series float) : Bar ratio limit used for checking the bars. Used only when checkBarRatio is set to true avoidOverlap (series bool) patternLineWidth (series int) : Line width of the pattern trend lines showZigzag (series bool) : show zigzag associated with pattern zigzagLineWidth (series int) : line width of the zigzag lines. Used only when showZigzag is set to true zigzagLineColor (series color) : color of the zigzag lines. Used only when showZigzag is set to true showPatternLabel (series bool) : display pattern label containing the name patternLabelSize (series string) : size of the pattern label. Used only when showPatternLabel is set to true showPivotLabels (series bool) : Display pivot labels of the patterns marking 1-6 pivotLabelSize (series string) : size of the pivot label. Used only when showPivotLabels is set to true pivotLabelColor (series color) : color of the pivot label outline. chart.bg_color or chart.fg_color are the appropriate values. allowedPatterns (bool ) : array of bool encoding the allowed pattern types. themeColors (color ) : color array of themes to be used. Pattern Object containing Individual Pattern data Fields: pivots (Pivot type from Trendoscope/ZigzagLite/2) : array of Zigzag Pivot points trendLine1 (Line type from Trendoscope/LineWrapper/1) : First trend line joining pivots 1, 3, 5 trendLine2 (Line type from Trendoscope/LineWrapper/1) : Second trend line joining pivots 2, 4 (, 6) properties (PatternProperties) : PatternProperties Object carrying common properties patternColor (series color) : Individual pattern color. Lines and labels will be using this color. ratioDiff (series float) : Difference between trendLine1 and trendLine2 ratios zigzagLine (series polyline) : Internal zigzag line drawing Object pivotLabels (label ) : array containning Pivot labels patternLabel (series label) : pattern label Object patternType (series int) : integer representing the pattern type patternName (series string) : Type of pattern in string

wedges and flags This script identifies chart patterns: wedges, flags, triangles on the chart It has many settings. You can choose by which extremums you want to identify patterns - by the edges of wicks (tails, shadows), or by the edges of candle bodies . You can also adjust the accuracy - how smooth and accurate the shapes must be in order for them to be considered wedges or triangles. You can also customize other parameters of the figure, for example, how long the flagpole should be in order to consider such a figure a wedge, a flag or a triangle. You can also set how large the allowable spread of candles relative to the flagpole can be. The Sensitivity parameter - will allow you to control the number of patterns detected depending on whether you want the patterns to be detected more often, or if they cover more candles and thus be more reliable You can also customize your styles. All key settings are accompanied by tooltips

Wolfe Scanner (Multi - zigzag) [HeWhoMustNotBeNamed]Before getting into the script, I would like to explain bit of history around this project. Wolfe was in the back of my mind for some time and I had several attempts so far. 🎯Initial Attempt When I first developed harmonic patterns, I got many requests from users to develop script to automatically detect Wolfe formation. I thought it would be easy and started boasting everywhere that I am going to attempt this next. However I miserably failed that time and started realising it is not as simple as I thought it would be. I started with Wolfe in mind. But, ran into issues with loops. Soon figured out that finding and drawing wedge is more trickier. I decided will explore trendline first so that it can help find wedge better. Soon, the project turned into something else and resulted in Auto-TrendLines-HeWhoMustNotBeNamed and Wolfe left forgotten. 🎯Using predefined ratios Wolfe also has predefined fib ratios which we can use to calculate the formation. But, upon initial development, it did not convince me that it matches visual inspection of Wolfe all the time. Hence, I decided to fall back on finding wedge first. 🎯 Further exploration in finding wedge This attempt was not too bad. I did not try to jump into Wolfe and nor I bragged anywhere about attempting anything of this sort. My target this time was to find how to derive wedge. I knew then that if I manage to calculate wedge in efficient way, it can help further in finding Wolfe. While doing that, ended up deriving Wedge-and-Flag-Finder-Multi-zigzag - which is not a bad outcome. I got few reminders on Wolfe after this both in comments and in PM. 🎯You never fail until you stop trying!! After 2 back to back hectic 50hr work weeks + other commitments, I thought I will spend some time on this. Took less than half weekend and here we are. I was surprised how much little time it took in this attempt. But, the plan was running in my subconscious for several weeks or even months. Last two days were just putting these plans into an action. Now, let's discuss about the script. 🎲 Wolfe Concept Wolfe concept is simple. Whenever a wedge is formed, draw a line joining pivot 1 and 4 as shown in the chart below: Converging trendline forms the stop loss whereas line joining pivots 1 and 4 form the profit taking points. 🎲 Settings Settings are pretty straightforward. Explained in the chart below.