Get started

Search in scripts for "low"

TR_HighLow_LibLibrary "TR_HighLow_Lib" TODO: add library description here ShowLabel(_Text, _X, _Y, _Style, _Size, _Yloc, _Color)   TODO: Function to display labels   Parameters:      _Text : TODO: text (series string) Label text.      _X : TODO: x (series int) Bar index.      _Y : TODO: y (series int/float) Price of the label position.      _Style : TODO: style (series string) Label style.      _Size : TODO: size (series string) Label size.      _Yloc : TODO: yloc (series string) Possible values are yloc.price, yloc.abovebar, yloc.belowbar.      _Color : TODO: color (series color) Color of the label border and arrow   Returns: TODO: No return values GetColor(_Index)   TODO: Function to take out 12 colors in order   Parameters:      _Index : TODO: color number.   Returns: TODO: color code Tbl_position(_Pos)   TODO: Table display position function   Parameters:      _Pos : TODO: position.   Returns: TODO: Table position DeleteLine()   TODO: Delete Line   Parameters:      : TODO: No parameter   Returns: TODO: No return value DeleteLabel()   TODO: Delete Label   Parameters:      : TODO: No parameter   Returns: TODO: No return value ZigZag(_a_PHiLo, _a_IHiLo, _a_FHiLo, _a_DHiLo, _Histories, _Provisional_PHiLo, _Provisional_IHiLo, _Color1, _Width1, _Color2, _Width2, _ShowLabel, _ShowHighLowBar, _HighLowBarWidth, _HighLow_LabelSize)   TODO: Draw a zig-zag line.   Parameters:      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _a_FHiLo : TODO: High-Low flag array sequence 1:High 2:Low      _a_DHiLo : TODO: High-Low Price Differential Array      _Histories : TODO: Array size (High-Low length)      _Provisional_PHiLo : TODO: Provisional High-Low Price      _Provisional_IHiLo : TODO: Provisional High-Low INDEX      _Color1 : TODO: Normal High-Low color      _Width1 : TODO: Normal High-Low width      _Color2 : TODO: Provisional High-Low color      _Width2 : TODO: Provisional High-Low width      _ShowLabel : TODO: Label display flag True: Displayed False: Not displayed      _ShowHighLowBar : TODO: High-Low bar display flag True:Show False:Hide      _HighLowBarWidth : TODO: High-Low bar width      _HighLow_LabelSize : TODO: Label Size   Returns: TODO: No return value TrendLine(_a_PHiLo, _a_IHiLo, _Histories, _MultiLine, _StartWidth, _EndWidth, _IncreWidth, _StartTrans, _EndTrans, _IncreTrans, _ColorMode, _Color1_1, _Color1_2, _Color2_1, _Color2_2, _Top_High, _Top_Low, _Bottom_High, _Bottom_Low)   TODO: Draw a Trend Line   Parameters:      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _Histories : TODO: Array size (High-Low length)      _MultiLine : TODO: Draw a multiple Line.      _StartWidth : TODO: Line width start value      _EndWidth : TODO: Line width end value      _IncreWidth : TODO: Line width increment value      _StartTrans : TODO: Transparent rate start value      _EndTrans : TODO: Transparent rate finally      _IncreTrans : TODO: Transparent rate increase value      _ColorMode : TODO: 0:Nomal 1:Gradation      _Color1_1 : TODO: Gradation Color 1_1      _Color1_2 : TODO: Gradation Color 1_2      _Color2_1 : TODO: Gradation Color 2_1      _Color2_2 : TODO: Gradation Color 2_2      _Top_High : TODO: _Top_High Value for Gradation      _Top_Low : TODO: _Top_Low Value for Gradation      _Bottom_High : TODO: _Bottom_High Value for Gradation      _Bottom_Low : TODO: _Bottom_Low Value for Gradation   Returns: TODO: No return value Fibonacci(_a_Fibonacci, _a_PHiLo, _Provisional_PHiLo, _Index, _FrontMargin, _BackMargin)   TODO: Draw a Fibonacci line   Parameters:      _a_Fibonacci : TODO: Fibonacci Percentage Array      _a_PHiLo : TODO: High-Low price array      _Provisional_PHiLo : TODO: Provisional High-Low price (when _Index is 0)      _Index : TODO: Where to draw the Fibonacci line      _FrontMargin : TODO: Fibonacci line front-margin      _BackMargin : TODO: Fibonacci line back-margin   Returns: TODO: No return value Fibonacci(_a_Fibonacci, _a_PHiLo, _Provisional_PHiLo, _Index1, _FrontMargin1, _BackMargin1, _Transparent1, _Index2, _FrontMargin2, _BackMargin2, _Transparent2)   TODO: Draw a Fibonacci line   Parameters:      _a_Fibonacci : TODO: Fibonacci Percentage Array      _a_PHiLo : TODO: High-Low price array      _Provisional_PHiLo : TODO: Provisional High-Low price (when _Index is 0)      _Index1 : TODO: Where to draw the Fibonacci line 1      _FrontMargin1 : TODO: Fibonacci line front-margin 1      _BackMargin1 : TODO: Fibonacci line back-margin 1      _Transparent1 : TODO: Transparent rate 1      _Index2 : TODO: Where to draw the Fibonacci line 2      _FrontMargin2 : TODO: Fibonacci line front-margin 2      _BackMargin2 : TODO: Fibonacci line back-margin 2      _Transparent2 : TODO: Transparent rate 2   Returns: TODO: No return value High_Low_Judgment(_Length, _Extension, _Difference)   TODO: Judges High-Low   Parameters:      _Length : TODO: High-Low Confirmation Length      _Extension : TODO: Length of extension when the difference did not open      _Difference : TODO: Difference size   Returns: TODO: _HiLo=High-Low flag 0:Neither high nor low、1:High、2:Low、3:High-Low _PHi=high price、_PLo=low price、_IHi=High Price Index、_ILo=Low Price Index、 _Cnt=count、_ECnt=Extension count、 _DiffHi=Difference from Start(High)、_DiffLo=Difference from Start(Low)、 _StartHi=Start value(High)、_StartLo=Start value(Low) High_Low_Data_AddedAndUpdated(_HiLo, _Histories, _PHi, _PLo, _IHi, _ILo, _DiffHi, _DiffLo, _a_PHiLo, _a_IHiLo, _a_FHiLo, _a_DHiLo)   TODO: Adds and updates High-Low related arrays from given parameters   Parameters:      _HiLo : TODO: High-Low flag      _Histories : TODO: Array size (High-Low length)      _PHi : TODO: Price Hi      _PLo : TODO: Price Lo      _IHi : TODO: Index Hi      _ILo : TODO: Index Lo      _DiffHi : TODO: Difference in High      _DiffLo : TODO: Difference in Low      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _a_FHiLo : TODO: High-Low flag array 1:High 2:Low      _a_DHiLo : TODO: High-Low Price Differential Array   Returns: TODO: _PHiLo price array、_IHiLo indexed array、_FHiLo flag array、_DHiLo price-matching array、 Provisional_PHiLo Provisional price、Provisional_IHiLo 暫定インデックス High_Low(_a_PHiLo, _a_IHiLo, _a_FHiLo, _a_DHiLo, _a_Fibonacci, _Length, _Extension, _Difference, _Histories, _ShowZigZag, _ZigZagColor1, _ZigZagWidth1, _ZigZagColor2, _ZigZagWidth2, _ShowZigZagLabel, _ShowHighLowBar, _ShowTrendLine, _TrendMultiLine, _TrendStartWidth, _TrendEndWidth, _TrendIncreWidth, _TrendStartTrans, _TrendEndTrans, _TrendIncreTrans, _TrendColorMode, _TrendColor1_1, _TrendColor1_2, _TrendColor2_1, _TrendColor2_2, _ShowFibonacci1, _FibIndex1, _FibFrontMargin1, _FibBackMargin1, _FibTransparent1, _ShowFibonacci2, _FibIndex2, _FibFrontMargin2, _FibBackMargin2, _FibTransparent2, _ShowInfoTable1, _TablePosition1, _ShowInfoTable2, _TablePosition2)   TODO: Draw the contents of the High-Low array.   Parameters:      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _a_FHiLo : TODO: High-Low flag sequence 1:High 2:Low      _a_DHiLo : TODO: High-Low Price Differential Array      _a_Fibonacci : TODO: Fibonacci Gnar Matching      _Length : TODO: Length of confirmation      _Extension : TODO: Extension Length of extension when the difference did not open      _Difference : TODO: Difference size      _Histories : TODO: High-Low Length      _ShowZigZag : TODO: ZigZag Display      _ZigZagColor1 : TODO: Colors of ZigZag1      _ZigZagWidth1 : TODO: Width of ZigZag1      _ZigZagColor2 : TODO: Colors of ZigZag2      _ZigZagWidth2 : TODO: Width of ZigZag2      _ShowZigZagLabel : TODO: ZigZagLabel Display      _ShowHighLowBar : TODO: High-Low Bar Display      _ShowTrendLine : TODO: Trend Line Display      _TrendMultiLine : TODO: Trend Multi Line Display      _TrendStartWidth : TODO: Line width start value      _TrendEndWidth : TODO: Line width end value      _TrendIncreWidth : TODO: Line width increment value      _TrendStartTrans : TODO: Starting transmittance value      _TrendEndTrans : TODO: Transmittance End Value      _TrendIncreTrans : TODO: Increased transmittance value      _TrendColorMode : TODO: color mode      _TrendColor1_1 : TODO: Trend Color 1_1      _TrendColor1_2 : TODO: Trend Color 1_2      _TrendColor2_1 : TODO: Trend Color 2_1      _TrendColor2_2 : TODO: Trend Color 2_2      _ShowFibonacci1 : TODO: Fibonacci1 Display      _FibIndex1 : TODO: Fibonacci1 Index No.      _FibFrontMargin1 : TODO: Fibonacci1 Front margin      _FibBackMargin1 : TODO: Fibonacci1 Back Margin      _FibTransparent1 : TODO: Fibonacci1 Transmittance      _ShowFibonacci2 : TODO: Fibonacci2 Display      _FibIndex2 : TODO: Fibonacci2 Index No.      _FibFrontMargin2 : TODO: Fibonacci2 Front margin      _FibBackMargin2 : TODO: Fibonacci2 Back Margin      _FibTransparent2 : TODO: Fibonacci2 Transmittance      _ShowInfoTable1 : TODO: InfoTable1 Display      _TablePosition1 : TODO: InfoTable1 position      _ShowInfoTable2 : TODO: InfoTable2 Display      _TablePosition2 : TODO: InfoTable2 position   Returns: TODO: 無し
Pine Script® library
by Tommy_Rich
1
TR_HighLowLibrary "TR_HighLow" TODO: add library description here ShowLabel(_Text, _X, _Y, _Style, _Size, _Yloc, _Color)   TODO: Function to display labels   Parameters:      _Text : TODO: text (series string) Label text.      _X : TODO: x (series int) Bar index.      _Y : TODO: y (series int/float) Price of the label position.      _Style : TODO: style (series string) Label style.      _Size : TODO: size (series string) Label size.      _Yloc : TODO: yloc (series string) Possible values are yloc.price, yloc.abovebar, yloc.belowbar.      _Color : TODO: color (series color) Color of the label border and arrow   Returns: TODO: No return values GetColor(_Index)   TODO: Function to take out 12 colors in order   Parameters:      _Index : TODO: color number.   Returns: TODO: color code Tbl_position(_Pos)   TODO: Table display position function   Parameters:      _Pos : TODO: position.   Returns: TODO: Table position DeleteLine()   TODO: Delete Line   Parameters:      : TODO: No parameter   Returns: TODO: No return value DeleteLabel()   TODO: Delete Label   Parameters:      : TODO: No parameter   Returns: TODO: No return value ZigZag(_a_PHiLo, _a_IHiLo, _a_FHiLo, _a_DHiLo, _Histories, _Provisional_PHiLo, _Provisional_IHiLo, _Color1, _Width1, _Color2, _Width2, _ShowLabel, _ShowHighLowBar, _HighLowBarWidth, _HighLow_LabelSize)   TODO: Draw a zig-zag line.   Parameters:      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _a_FHiLo : TODO: High-Low flag array sequence 1:High 2:Low      _a_DHiLo : TODO: High-Low Price Differential Array      _Histories : TODO: Array size (High-Low length)      _Provisional_PHiLo : TODO: Provisional High-Low Price      _Provisional_IHiLo : TODO: Provisional High-Low INDEX      _Color1 : TODO: Normal High-Low color      _Width1 : TODO: Normal High-Low width      _Color2 : TODO: Provisional High-Low color      _Width2 : TODO: Provisional High-Low width      _ShowLabel : TODO: Label display flag True: Displayed False: Not displayed      _ShowHighLowBar : TODO: High-Low bar display flag True:Show False:Hide      _HighLowBarWidth : TODO: High-Low bar width      _HighLow_LabelSize : TODO: Label Size   Returns: TODO: No return value TrendLine(_a_PHiLo, _a_IHiLo, _Histories, _MultiLine, _StartWidth, _EndWidth, _IncreWidth, _StartTrans, _EndTrans, _IncreTrans, _ColorMode, _Color1_1, _Color1_2, _Color2_1, _Color2_2, _Top_High, _Top_Low, _Bottom_High, _Bottom_Low)   TODO: Draw a Trend Line   Parameters:      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _Histories : TODO: Array size (High-Low length)      _MultiLine : TODO: Draw a multiple Line.      _StartWidth : TODO: Line width start value      _EndWidth : TODO: Line width end value      _IncreWidth : TODO: Line width increment value      _StartTrans : TODO: Transparent rate start value      _EndTrans : TODO: Transparent rate finally      _IncreTrans : TODO: Transparent rate increase value      _ColorMode : TODO: 0:Nomal 1:Gradation      _Color1_1 : TODO: Gradation Color 1_1      _Color1_2 : TODO: Gradation Color 1_2      _Color2_1 : TODO: Gradation Color 2_1      _Color2_2 : TODO: Gradation Color 2_2      _Top_High : TODO: _Top_High Value for Gradation      _Top_Low : TODO: _Top_Low Value for Gradation      _Bottom_High : TODO: _Bottom_High Value for Gradation      _Bottom_Low : TODO: _Bottom_Low Value for Gradation   Returns: TODO: No return value Fibonacci(_a_Fibonacci, _a_PHiLo, _Provisional_PHiLo, _Index, _FrontMargin, _BackMargin)   TODO: Draw a Fibonacci line   Parameters:      _a_Fibonacci : TODO: Fibonacci Percentage Array      _a_PHiLo : TODO: High-Low price array      _Provisional_PHiLo : TODO: Provisional High-Low price (when _Index is 0)      _Index : TODO: Where to draw the Fibonacci line      _FrontMargin : TODO: Fibonacci line front-margin      _BackMargin : TODO: Fibonacci line back-margin   Returns: TODO: No return value Fibonacci(_a_Fibonacci, _a_PHiLo, _Provisional_PHiLo, _Index1, _FrontMargin1, _BackMargin1, _Transparent1, _Index2, _FrontMargin2, _BackMargin2, _Transparent2)   TODO: Draw a Fibonacci line   Parameters:      _a_Fibonacci : TODO: Fibonacci Percentage Array      _a_PHiLo : TODO: High-Low price array      _Provisional_PHiLo : TODO: Provisional High-Low price (when _Index is 0)      _Index1 : TODO: Where to draw the Fibonacci line 1      _FrontMargin1 : TODO: Fibonacci line front-margin 1      _BackMargin1 : TODO: Fibonacci line back-margin 1      _Transparent1 : TODO: Transparent rate 1      _Index2 : TODO: Where to draw the Fibonacci line 2      _FrontMargin2 : TODO: Fibonacci line front-margin 2      _BackMargin2 : TODO: Fibonacci line back-margin 2      _Transparent2 : TODO: Transparent rate 2   Returns: TODO: No return value High_Low_Judgment(_Length, _Extension, _Difference)   TODO: Judges High-Low   Parameters:      _Length : TODO: High-Low Confirmation Length      _Extension : TODO: Length of extension when the difference did not open      _Difference : TODO: Difference size   Returns: TODO: _HiLo=High-Low flag 0:Neither high nor low、1:High、2:Low、3:High-Low _PHi=high price、_PLo=low price、_IHi=High Price Index、_ILo=Low Price Index、 _Cnt=count、_ECnt=Extension count、 _DiffHi=Difference from Start(High)、_DiffLo=Difference from Start(Low)、 _StartHi=Start value(High)、_StartLo=Start value(Low) High_Low_Data_AddedAndUpdated(_HiLo, _Histories, _PHi, _PLo, _IHi, _ILo, _DiffHi, _DiffLo, _a_PHiLo, _a_IHiLo, _a_FHiLo, _a_DHiLo)   TODO: Adds and updates High-Low related arrays from given parameters   Parameters:      _HiLo : TODO: High-Low flag      _Histories : TODO: Array size (High-Low length)      _PHi : TODO: Price Hi      _PLo : TODO: Price Lo      _IHi : TODO: Index Hi      _ILo : TODO: Index Lo      _DiffHi : TODO: Difference in High      _DiffLo : TODO: Difference in Low      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _a_FHiLo : TODO: High-Low flag array 1:High 2:Low      _a_DHiLo : TODO: High-Low Price Differential Array   Returns: TODO: _PHiLo price array、_IHiLo indexed array、_FHiLo flag array、_DHiLo price-matching array、 Provisional_PHiLo Provisional price、Provisional_IHiLo 暫定インデックス High_Low(_a_PHiLo, _a_IHiLo, _a_FHiLo, _a_DHiLo, _a_Fibonacci, _Length, _Extension, _Difference, _Histories, _ShowZigZag, _ZigZagColor1, _ZigZagWidth1, _ZigZagColor2, _ZigZagWidth2, _ShowZigZagLabel, _ShowHighLowBar, _ShowTrendLine, _TrendMultiLine, _TrendStartWidth, _TrendEndWidth, _TrendIncreWidth, _TrendStartTrans, _TrendEndTrans, _TrendIncreTrans, _TrendColorMode, _TrendColor1_1, _TrendColor1_2, _TrendColor2_1, _TrendColor2_2, _ShowFibonacci1, _FibIndex1, _FibFrontMargin1, _FibBackMargin1, _FibTransparent1, _ShowFibonacci2, _FibIndex2, _FibFrontMargin2, _FibBackMargin2, _FibTransparent2, _ShowInfoTable1, _TablePosition1, _ShowInfoTable2, _TablePosition2)   TODO: Draw the contents of the High-Low array.   Parameters:      _a_PHiLo : TODO: High-Low price array      _a_IHiLo : TODO: High-Low INDEX array      _a_FHiLo : TODO: High-Low flag sequence 1:High 2:Low      _a_DHiLo : TODO: High-Low Price Differential Array      _a_Fibonacci : TODO: Fibonacci Gnar Matching      _Length : TODO: Length of confirmation      _Extension : TODO: Extension Length of extension when the difference did not open      _Difference : TODO: Difference size      _Histories : TODO: High-Low Length      _ShowZigZag : TODO: ZigZag Display      _ZigZagColor1 : TODO: Colors of ZigZag1      _ZigZagWidth1 : TODO: Width of ZigZag1      _ZigZagColor2 : TODO: Colors of ZigZag2      _ZigZagWidth2 : TODO: Width of ZigZag2      _ShowZigZagLabel : TODO: ZigZagLabel Display      _ShowHighLowBar : TODO: High-Low Bar Display      _ShowTrendLine : TODO: Trend Line Display      _TrendMultiLine : TODO: Trend Multi Line Display      _TrendStartWidth : TODO: Line width start value      _TrendEndWidth : TODO: Line width end value      _TrendIncreWidth : TODO: Line width increment value      _TrendStartTrans : TODO: Starting transmittance value      _TrendEndTrans : TODO: Transmittance End Value      _TrendIncreTrans : TODO: Increased transmittance value      _TrendColorMode : TODO: color mode      _TrendColor1_1 : TODO: Trend Color 1_1      _TrendColor1_2 : TODO: Trend Color 1_2      _TrendColor2_1 : TODO: Trend Color 2_1      _TrendColor2_2 : TODO: Trend Color 2_2      _ShowFibonacci1 : TODO: Fibonacci1 Display      _FibIndex1 : TODO: Fibonacci1 Index No.      _FibFrontMargin1 : TODO: Fibonacci1 Front margin      _FibBackMargin1 : TODO: Fibonacci1 Back Margin      _FibTransparent1 : TODO: Fibonacci1 Transmittance      _ShowFibonacci2 : TODO: Fibonacci2 Display      _FibIndex2 : TODO: Fibonacci2 Index No.      _FibFrontMargin2 : TODO: Fibonacci2 Front margin      _FibBackMargin2 : TODO: Fibonacci2 Back Margin      _FibTransparent2 : TODO: Fibonacci2 Transmittance      _ShowInfoTable1 : TODO: InfoTable1 Display      _TablePosition1 : TODO: InfoTable1 position      _ShowInfoTable2 : TODO: InfoTable2 Display      _TablePosition2 : TODO: InfoTable2 position   Returns: TODO: 無し
Pine Script® library
by Tommy_Rich
Chart Patterns [ActiveQuants]The Chart Patterns indicator is a comprehensive tool designed to automatically identify a variety of common chart patterns directly on your price chart. By detecting sequences of pivot highs and lows , this indicator helps traders spot potential trend continuations , reversals , and key market structures such as Double Tops and Double Bottoms . Enhance your technical analysis by quickly recognizing these formations as they emerge. How It Works The indicator operates in a two-stage process: Pivot Point Detection: It first identifies significant swing highs and swing lows (pivot points) based on a user-defined Period . These pivots form the fundamental building blocks for pattern recognition. Pattern Recognition: Using the sequence of these detected pivot points, the script then applies logical rules to identify the following patterns: Lower Low (LL) Lower Low & Lower High (LL & LH) Higher High (HH) Higher High & Higher Low (HH & HL) Double Tops Double Bottoms Patterns are drawn on the chart with connecting lines and labeled for easy identification. Double Tops and Double Bottoms also feature a status system: " Active " while forming, " Confirmed " upon neckline breakout, or " Invalid " if specific conditions negate the pattern before confirmation. █ KEY FEATURES Comprehensive Pattern Detection: Identifies six distinct types of chart patterns, offering insights into both trend continuation and potential reversals. Pivot-Based Analysis: Uses a robust method of identifying pivot highs and lows as the foundation for pattern formation. Pattern Status for Double Tops/Bottoms: - Active: A Double Top or Double Bottom pattern has formed its two peaks/troughs and the intervening neckline point, but the price has not yet broken beyond the neckline. The pattern is developing . - Confirmed: The price has decisively closed beyond the neckline (below for Double Top, above for Double Bottom), signaling a potential entry or validation of the pattern. - Invalid: An " Active " Double Top or Double Bottom pattern can be invalidated if, before a neckline breakout occurs, a new pivot point forms that negates the pattern’s structural integrity. For example, if a new pivot low forms above or at the neckline of an Active Double Top, the pattern is considered invalid because the market failed to break down and instead showed relative strength. Customizable Visuals: Allows users to define colors for bullish and bearish patterns, line widths, and the visibility of pivot points. Selective Pattern Display: Users can choose to display all patterns or filter by status (Active, Confirmed, Invalid) for Double Tops/Bottoms. Individual pattern types can also be toggled on or off. Historical Analysis Control: The Show Last History (Bars) input allows users to specify how far back the indicator should plot patterns, optimizing performance and chart readability. Clear Labeling: Patterns are clearly labeled on the chart, with Double Tops/Bottoms also showing " Top 1 ," " Top 2 ," or " Bottom 1 ," " Bottom 2 " labels. █ PATTERNS DETECTED Lower Low (LL): Indicates a potential bearish continuation or the start of a downtrend. Forms when price makes a lower low during an uptrend. Lower Low & Lower High (LL & LH): A stronger confirmation of a bearish trend, where the market forms a lower low followed by a lower high . Higher High (HH): Signals a potential bullish continuation or the start of an uptrend. Forms when price makes a higher high during a downtrend. Higher High & Higher Low (HH & HL): A stronger confirmation of a bullish trend, where the market forms a higher high followed by a higher low . Double Top: A bearish reversal pattern characterized by two distinct peaks at roughly the same price level, separated by a trough (neckline). Confirmation occurs when price breaks below the neckline. Double Bottom: A bullish reversal pattern featuring two distinct troughs at roughly the same price level, separated by a peak (neckline). Confirmation occurs when price breaks above the neckline. █ EXAMPLE: DOUBLE TOP INVALIDATION Understanding how a Double Top or Double Bottom can be invalidated is crucial. Here's an example for a Double Top: Formation: The indicator identifies two peaks (Top 1, Top 2) at a similar price level, with a corrective trough (Neckline Pivot P5) in between. The pattern is labeled " Double Top " and is in an " Active " state. ( Imagine points P4 and P6 are the two tops, and P5 is the low point of the neckline between them ). Pre-Breakout Condition: The price action continues, but before it breaks decisively below the P5 neckline level, a new significant swing low (a new pivot low) forms. Invalidation Check: The indicator checks the price level of this new pivot low. If this new pivot low occurs at a price equal to or higher than the P5 neckline level, the " Active " Double Top pattern is re-labeled as " Invalid Double Top ". ( See image below for a visual representation of this scenario ) In this example, the Double Top formed with Top 1 (P4) and Top 2 (P6). The neckline is at P5. Before price broke below P5, a new pivot low formed at the red circle. Since this new pivot low is above the P5 neckline, the Double Top is marked " Invalid ". The logic is that the market failed to break the neckline support and instead established a higher low (or a low at the support level), suggesting that the immediate bearish pressure has waned, thus invalidating the bearish reversal implication of the Double Top before it could confirm. A similar logic applies to Double Bottoms (a new pivot high forming below or at the neckline before an upside breakout). █ USER INPUTS Visibility and Common Styling - Show Last History (Bars): Specifies the number of recent bars the indicator will analyze and plot patterns on. Default: 3000 bars. Min: 10. - Patterns: Filters which patterns are displayed based on their status. Options: All, Active, Confirmed, Invalid. Default: All. - Pattern Line Width: Sets the thickness of the lines used to draw the patterns. Default: 1. Min: 1, Max: 10. - Bearish Color: Color for bearish patterns (LL, LL & LH, Double Tops). Default: Red. - Bullish Color: Color for bullish patterns (HH, HH & HL, Double Bottoms). Default: Green. Pivot Points - Period: The lookback period on either side of a bar to qualify it as a pivot high or low. Higher values detect more significant pivots. Default: 10 bars. Min: 2. - Show Pivot Highs: Toggles the visibility of detected pivot high markers. Default: Enabled. - Show Pivot Lows: Toggles the visibility of detected pivot low markers. Default: Enabled. - Pivot Highs Color: Color for the pivot high markers. Default: #ff5252 (Reddish). - Pivot Lows Color: Color for the pivot low markers. Default: #089981 (Greenish). Patterns (Toggles) - Lower Low: Enable/disable detection and display of Lower Low patterns. Default: Enabled. - Lower Low & Lower High: Enable/disable detection and display of Lower Low & Lower High patterns. Default: Enabled. - Higher High: Enable/disable detection and display of Higher High patterns. Default: Enabled. - Higher High & Higher Low: Enable/disable detection and display of Higher High & Higher Low patterns. Default: Enabled. - Double Tops: Enable/disable detection and display of Double Top patterns. Default: Enabled. - Double Bottoms: Enable/disable detection and display of Double Bottom patterns. Default: Enabled. █ CONCLUSION The Chart Patterns indicator is a versatile and powerful assistant for traders who utilize classical chart pattern analysis. By automating the detection of key formations and providing clear visual cues along with status updates for patterns like Double Tops and Bottoms, it allows traders to focus on strategy development and execution. With its customizable settings, it can be adapted to various instruments and timeframes, making it a valuable addition to any technical trader's toolkit. █ IMPORTANT NOTES ⚠ Pivot Period Sensitivity: The Period setting for pivot detection is crucial. A shorter period will identify more frequent, smaller swings, while a longer period will focus on more significant turning points. Adjust this setting based on the asset's volatility, the timeframe you are trading and your trading style. ⚠ Confirmation is Key: While the indicator identifies patterns, always wait for pattern confirmation (e.g., neckline breaks for Double Tops/Bottoms) and consider other factors like volume and market context before making trading decisions. ⚠ Confirmed Bars for Detection: Patterns are identified based on confirmed pivot points, which means a pivot is recognized period bars after it has formed. Status updates for Double Tops/Bottoms (Active, Confirmed, Invalid) also occur on confirmed bars. This approach enhances reliability and reduces the likelihood of repainting based on intra-bar price fluctuations. ⚠ Not a Standalone System: Chart patterns provide valuable insights, but they should be used in conjunction with other technical analysis tools (e.g., trendlines, moving averages, oscillators) and a sound risk management plan. ⚠ Lagging Nature: By their very definition, chart patterns are lagging indicators as they require a sequence of price action and several pivot points to complete their formation. █ RISK DISCLAIMER Trading involves a substantial risk of loss and is not suitable for every investor. The information provided by the Chart Patterns indicator is for educational and informational purposes only. It should not be considered as financial advice or a recommendation to buy or sell any security. Chart patterns indicate potential price movements but do not guarantee future results. Always perform your own due diligence and consult with a qualified financial advisor before making any investment decisions. Past performance is not indicative of future results.   📈 Happy trading! 🚀
Pine Script® indicator
by ActiveQuants
4
[Defaust] Fractals Fractals Indicator Overview The Fractals Indicator is a technical analysis tool designed to help traders identify potential reversal points in the market by detecting fractal patterns. This indicator is a fork of the original fractals indicator, with adjustments made to the plotting for enhanced visual clarity and usability. What Are Fractals? In trading, a fractal is a pattern consisting of five consecutive bars (candlesticks) that meet specific conditions: Up Fractal (Potential Sell Signal): Occurs when a high point is surrounded by two lower highs on each side. Down Fractal (Potential Buy Signal): Occurs when a low point is surrounded by two higher lows on each side. Fractals help traders identify potential tops and bottoms in the market, signaling possible entry or exit points. Features of the Indicator Customizable Periods (n): Allows you to define the number of periods to consider when detecting fractals, offering flexibility to adapt to different trading strategies and timeframes. Enhanced Plotting Adjustments: This fork introduces adjustments to the plotting of fractal signals for better visual representation on the chart. Visual Signals: Plots up and down triangles on the chart to signify down fractals (potential bullish signals) and up fractals (potential bearish signals), respectively. Overlay on Chart: The fractal signals are overlaid directly on the price chart for immediate visualization. Adjustable Precision: You can set the precision of the plotted values according to your needs. Pine Script Code Explanation Below is the Pine Script code for the Fractals Indicator: //@version=5 indicator(" Fractals", shorttitle=" Fractals", format=format.price, precision=0, overlay=true) // User input for the number of periods to consider for fractal detection n = input.int(title="Periods", defval=2, minval=2) // Initialize flags for up fractal detection bool upflagDownFrontier = true bool upflagUpFrontier0 = true bool upflagUpFrontier1 = true bool upflagUpFrontier2 = true bool upflagUpFrontier3 = true bool upflagUpFrontier4 = true // Loop through previous and future bars to check conditions for up fractals for i = 1 to n // Check if the highs of previous bars are less than the current bar's high upflagDownFrontier := upflagDownFrontier and (high < high ) // Check various conditions for future bars upflagUpFrontier0 := upflagUpFrontier0 and (high < high ) upflagUpFrontier1 := upflagUpFrontier1 and (high <= high and high < high ) upflagUpFrontier2 := upflagUpFrontier2 and (high <= high and high <= high and high < high ) upflagUpFrontier3 := upflagUpFrontier3 and (high <= high and high <= high and high <= high and high < high ) upflagUpFrontier4 := upflagUpFrontier4 and (high <= high and high <= high and high <= high and high <= high and high < high ) // Combine the flags to determine if an up fractal exists flagUpFrontier = upflagUpFrontier0 or upflagUpFrontier1 or upflagUpFrontier2 or upflagUpFrontier3 or upflagUpFrontier4 upFractal = (upflagDownFrontier and flagUpFrontier) // Initialize flags for down fractal detection bool downflagDownFrontier = true bool downflagUpFrontier0 = true bool downflagUpFrontier1 = true bool downflagUpFrontier2 = true bool downflagUpFrontier3 = true bool downflagUpFrontier4 = true // Loop through previous and future bars to check conditions for down fractals for i = 1 to n // Check if the lows of previous bars are greater than the current bar's low downflagDownFrontier := downflagDownFrontier and (low > low ) // Check various conditions for future bars downflagUpFrontier0 := downflagUpFrontier0 and (low > low ) downflagUpFrontier1 := downflagUpFrontier1 and (low >= low and low > low ) downflagUpFrontier2 := downflagUpFrontier2 and (low >= low and low >= low and low > low ) downflagUpFrontier3 := downflagUpFrontier3 and (low >= low and low >= low and low >= low and low > low ) downflagUpFrontier4 := downflagUpFrontier4 and (low >= low and low >= low and low >= low and low >= low and low > low ) // Combine the flags to determine if a down fractal exists flagDownFrontier = downflagUpFrontier0 or downflagUpFrontier1 or downflagUpFrontier2 or downflagUpFrontier3 or downflagUpFrontier4 downFractal = (downflagDownFrontier and flagDownFrontier) // Plot the fractal symbols on the chart with adjusted plotting plotshape(downFractal, style=shape.triangleup, location=location.belowbar, offset=-n, color=color.gray, size=size.auto) plotshape(upFractal, style=shape.triangledown, location=location.abovebar, offset=-n, color=color.gray, size=size.auto) Explanation: Input Parameter (n): Sets the number of periods for fractal detection. The default value is 2, and it must be at least 2 to ensure valid fractal patterns. Flag Initialization: Boolean variables are used to store intermediate conditions during fractal detection. Loops: Iterate through the specified number of periods to evaluate the conditions for fractal formation. Conditions: Up Fractals: Checks if the current high is greater than previous highs and if future highs are lower or equal to the current high. Down Fractals: Checks if the current low is lower than previous lows and if future lows are higher or equal to the current low. Flag Combination: Logical and and or operations are used to combine the flags and determine if a fractal exists. Adjusted Plotting: The plotting of fractal symbols has been adjusted for better alignment and visual clarity. The offset parameter is set to -n to align the plotted symbols with the correct bars. The color and size have been fine-tuned for better visibility. How to Use the Indicator Adding the Indicator to Your Chart Open TradingView: Go to TradingView. Access the Chart: Click on "Chart" to open the main charting interface. Add the Indicator: Click on the "Indicators" button at the top. Search for " Fractals". Select the indicator from the list to add it to your chart. Configuring the Indicator Periods (n): Default value is 2. Adjust this parameter based on your preferred timeframe and sensitivity. A higher value of n considers more bars for fractal detection, potentially reducing the number of signals but increasing their significance. Interpreting the Signals – Up Fractal (Downward Triangle): Indicates a potential price reversal to the downside. May be used as a signal to consider exiting long positions or tightening stop-loss orders. – Down Fractal (Upward Triangle): Indicates a potential price reversal to the upside. May be used as a signal to consider entering long positions or setting stop-loss orders for short positions. Trading Strategy Suggestions Up Fractal Detection: The high of the current bar (n) is higher than the highs of the previous two bars (n - 1, n - 2). The highs of the next bars meet certain conditions to confirm the fractal pattern. An up fractal symbol (downward triangle) is plotted above the bar at position n - n (due to the offset). Down Fractal Detection: The low of the current bar (n) is lower than the lows of the previous two bars (n - 1, n - 2). The lows of the next bars meet certain conditions to confirm the fractal pattern. A down fractal symbol (upward triangle) is plotted below the bar at position n - n. Benefits of Using the Fractals Indicator Early Signals: Helps in identifying potential reversal points in price movements. Customizable Sensitivity: Adjusting the n parameter allows you to fine-tune the indicator based on different market conditions. Enhanced Visuals: Adjustments to plotting improve the clarity and readability of fractal signals on the chart. Limitations and Considerations Lagging Indicator: Fractals require future bars to confirm the pattern, which may introduce a delay in the signals. False Signals: In volatile or ranging markets, fractals may produce false signals. It's advisable to use them in conjunction with other analysis tools. Not a Standalone Tool: Fractals should be part of a broader trading strategy that includes other indicators and fundamental analysis. Best Practices for Using This Indicator Combine with Other Indicators: Use in combination with trend indicators, oscillators, or volume analysis to confirm signals. Backtesting: Before applying the indicator in live trading, backtest it on historical data to understand its performance. Adjust Periods Accordingly: Experiment with different values of n to find the optimal setting for the specific asset and timeframe you are trading. Disclaimer The Fractals Indicator is intended for educational and informational purposes only. Trading involves significant risk, and you should be aware of the risks involved before proceeding. Past performance is not indicative of future results. Always conduct your own analysis and consult with a professional financial advisor before making any investment decisions. Credits This indicator is a fork of the original fractals indicator, with adjustments made to the plotting for improved visual representation. It is based on standard fractal patterns commonly used in technical analysis and has been developed to provide traders with an effective tool for detecting potential reversal points in the market.
Pine Script® indicator
by defaustofficial
Trading IQ - ICT LibraryLibrary "ICTlibrary" Used to calculate various ICT related price levels and strategies. An ongoing project. Hello Coders! This library is meant for sourcing ICT related concepts. While some functions might generate more output than you require, you can specify "Lite Mode" as "true" in applicable functions to slim down necessary inputs. isLastBar(userTF)   Identifies the last bar on the chart before a timeframe change   Parameters:      userTF (simple int) : the timeframe you wish to calculate the last bar for, must be converted to integer using 'timeframe.in_seconds()'   Returns: bool true if bar on chart is last bar of higher TF, dalse if bar on chart is not last bar of higher TF necessaryData(atrTF)   returns necessaryData UDT for historical data access   Parameters:      atrTF (float) : user-selected timeframe ATR value.   Returns: logZ. log return Z score, used for calculating order blocks. method gradBoxes(gradientBoxes, idColor, timeStart, bottom, top, rightCoordinate)   creates neon like effect for box drawings   Namespace types: array   Parameters:      gradientBoxes (array) : an array.new() to store the gradient boxes      idColor (color)      timeStart (int) : left point of box      bottom (float) : bottom of box price point      top (float) : top of box price point      rightCoordinate (int) : right point of box   Returns: void checkIfTraded(tradeName)   checks if recent trade is of specific name   Parameters:      tradeName (string)   Returns: bool true if recent trade id matches target name, false otherwise checkIfClosed(tradeName)   checks if recent closed trade is of specific name   Parameters:      tradeName (string)   Returns: bool true if recent closed trade id matches target name, false otherwise IQZZ(atrMult, finalTF)   custom ZZ to quickly determine market direction.   Parameters:      atrMult (float) : an atr multiplier used to determine the required price move for a ZZ direction change      finalTF (string) : the timeframe used for the atr calcuation   Returns: dir market direction. Up => 1, down => -1 method drawBos(id, startPoint, getKeyPointTime, getKeyPointPrice, col, showBOS, isUp)   calculates and draws Break Of Structure   Namespace types: array   Parameters:      id (array)      startPoint (chart.point)      getKeyPointTime (int) : the actual time of startPoint, simplystartPoint.time      getKeyPointPrice (float) : the actual time of startPoint, simplystartPoint.price      col (color) : color of the BoS line / label      showBOS (bool) : whether to show label/line. This function still calculates internally for other ICT related concepts even if not drawn.      isUp (bool) : whether BoS happened during price increase or price decrease.   Returns: void method drawMSS(id, startPoint, getKeyPointTime, getKeyPointPrice, col, showMSS, isUp, upRejections, dnRejections, highArr, lowArr, timeArr, closeArr, openArr, atrTFarr, upRejectionsPrices, dnRejectionsPrices)   calculates and draws Market Structure Shift. This data is also used to calculate Rejection Blocks.   Namespace types: array   Parameters:      id (array)      startPoint (chart.point)      getKeyPointTime (int) : the actual time of startPoint, simplystartPoint.time      getKeyPointPrice (float) : the actual time of startPoint, simplystartPoint.price      col (color) : color of the MSS line / label      showMSS (bool) : whether to show label/line. This function still calculates internally for other ICT related concepts even if not drawn.      isUp (bool) : whether MSS happened during price increase or price decrease.      upRejections (array)      dnRejections (array)      highArr (array) : array containing historical highs, should be taken from the UDT "necessaryData" defined above      lowArr (array) : array containing historical lows, should be taken from the UDT "necessaryData" defined above      timeArr (array) : array containing historical times, should be taken from the UDT "necessaryData" defined above      closeArr (array) : array containing historical closes, should be taken from the UDT "necessaryData" defined above      openArr (array) : array containing historical opens, should be taken from the UDT "necessaryData" defined above      atrTFarr (array) : array containing historical atr values (of user-selected TF), should be taken from the UDT "necessaryData" defined above      upRejectionsPrices (array) : array containing up rejections prices. Is sorted and used to determine selective looping for invalidations.      dnRejectionsPrices (array) : array containing down rejections prices. Is sorted and used to determine selective looping for invalidations.   Returns: void method getTime(id, compare, timeArr)   gets time of inputted price (compare) in an array of data this is useful when the user-selected timeframe for ICT concepts is greater than the chart's timeframe   Namespace types: array   Parameters:      id (array) : the array of data to search through, to find which index has the same value as "compare"      compare (float) : the target data point to find in the array      timeArr (array) : array of historical times   Returns: the time that the data point in the array was recorded method OB(id, highArr, signArr, lowArr, timeArr, sign)   store bullish orderblock data   Namespace types: array   Parameters:      id (array)      highArr (array) : array of historical highs      signArr (array) : array of historical price direction "math.sign(close - open)"      lowArr (array) : array of historical lows      timeArr (array) : array of historical times      sign (int) : orderblock direction, -1 => bullish, 1 => bearish   Returns: void OTEstrat(OTEstart, future, closeArr, highArr, lowArr, timeArr, longOTEPT, longOTESL, longOTElevel, shortOTEPT, shortOTESL, shortOTElevel, structureDirection, oteLongs, atrTF, oteShorts)   executes the OTE strategy   Parameters:      OTEstart (chart.point)      future (int) : future time point for drawings      closeArr (array) : array of historical closes      highArr (array) : array of historical highs      lowArr (array) : array of historical lows      timeArr (array) : array of historical times      longOTEPT (string) : user-selected long OTE profit target, please create an input.string() for this using the example below      longOTESL (int) : user-selected long OTE stop loss, please create an input.string() for this using the example below      longOTElevel (float) : long entry price of selected retracement ratio for OTE      shortOTEPT (string) : user-selected short OTE profit target, please create an input.string() for this using the example below      shortOTESL (int) : user-selected short OTE stop loss, please create an input.string() for this using the example below      shortOTElevel (float) : short entry price of selected retracement ratio for OTE      structureDirection (string) : current market structure direction, this should be "Up" or "Down". This is used to cancel pending orders if market structure changes      oteLongs (bool) : input.bool() for whether OTE longs can be executed      atrTF (float) : atr of the user-seleceted TF      oteShorts (bool) : input.bool() for whether OTE shorts can be executed @exampleInputs oteLongs = input.bool(defval = false, title = "OTE Longs", group = "Optimal Trade Entry") longOTElevel = input.float(defval = 0.79, title = "Long Entry Retracement Level", options = , group = "Optimal Trade Entry") longOTEPT = input.string(defval = "-0.5", title = "Long TP", options = , group = "Optimal Trade Entry") longOTESL = input.int(defval = 0, title = "How Many Ticks Below Swing Low For Stop Loss", group = "Optimal Trade Entry") oteShorts = input.bool(defval = false, title = "OTE Shorts", group = "Optimal Trade Entry") shortOTElevel = input.float(defval = 0.79, title = "Short Entry Retracement Level", options = , group = "Optimal Trade Entry") shortOTEPT = input.string(defval = "-0.5", title = "Short TP", options = , group = "Optimal Trade Entry") shortOTESL = input.int(defval = 0, title = "How Many Ticks Above Swing Low For Stop Loss", group = "Optimal Trade Entry")   Returns: void (0) displacement(logZ, atrTFreg, highArr, timeArr, lowArr, upDispShow, dnDispShow, masterCoords, labelLevels, dispUpcol, rightCoordinate, dispDncol, noBorders)   calculates and draws dispacements   Parameters:      logZ (float) : log return of current price, used to determine a "significant price move" for a displacement      atrTFreg (float) : atr of user-seleceted timeframe      highArr (array) : array of historical highs      timeArr (array) : array of historical times      lowArr (array) : array of historical lows      upDispShow (int) : amount of historical upside displacements to show      dnDispShow (int) : amount of historical downside displacements to show      masterCoords (map) : a map to push the most recent displacement prices into, useful for having key levels in one data structure      labelLevels (string) : used to determine label placement for the displacement, can be inside box, outside box, or none, example below      dispUpcol (color) : upside displacement color      rightCoordinate (int) : future time for displacement drawing, best is "last_bar_time"      dispDncol (color) : downside displacement color      noBorders (bool) : input.bool() to remove box borders, example below @exampleInputs labelLevels = input.string(defval = "Inside" , title = "Box Label Placement", options = ) noBorders = input.bool(defval = false, title = "No Borders On Levels")   Returns: void method getStrongLow(id, startIndex, timeArr, lowArr, strongLowPoints)   unshift strong low data to array id   Namespace types: array   Parameters:      id (array)      startIndex (int) : the starting index for the timeArr array of the UDT "necessaryData". this point should start from at least 1 pivot prior to find the low before an upside BoS      timeArr (array) : array of historical times      lowArr (array) : array of historical lows      strongLowPoints (array) : array of strong low prices. Used to retrieve highest strong low price and see if need for removal of invalidated strong lows   Returns: void method getStrongHigh(id, startIndex, timeArr, highArr, strongHighPoints)   unshift strong high data to array id   Namespace types: array   Parameters:      id (array)      startIndex (int) : the starting index for the timeArr array of the UDT "necessaryData". this point should start from at least 1 pivot prior to find the high before a downside BoS      timeArr (array) : array of historical times      highArr (array) : array of historical highs      strongHighPoints (array)   Returns: void equalLevels(highArr, lowArr, timeArr, rightCoordinate, equalHighsCol, equalLowsCol, liteMode)   used to calculate recent equal highs or equal lows   Parameters:      highArr (array) : array of historical highs      lowArr (array) : array of historical lows      timeArr (array) : array of historical times      rightCoordinate (int) : a future time (right for boxes, x2 for lines)      equalHighsCol (color) : user-selected color for equal highs drawings      equalLowsCol (color) : user-selected color for equal lows drawings      liteMode (bool) : optional for a lite mode version of an ICT strategy. For more control over drawings leave as "True", "False" will apply neon effects   Returns: void quickTime(timeString)   used to quickly determine if a user-inputted time range is currently active in NYT time   Parameters:      timeString (string) : a time range   Returns: true if session is active, false if session is inactive macros(showMacros, noBorders)   used to calculate and draw session macros   Parameters:      showMacros (bool) : an input.bool() or simple bool to determine whether to activate the function      noBorders (bool) : an input.bool() to determine whether the box anchored to the session should have borders   Returns: void po3(tf, left, right, show)   use to calculate HTF po3 candle @tip only call this function on "barstate.islast"   Parameters:      tf (simple string)      left (int) : the left point of the candle, calculated as bar_index + left,      right (int) : :the right point of the candle, calculated as bar_index + right,      show (bool) : input.bool() whether to show the po3 candle or not   Returns: void silverBullet(silverBulletStratLong, silverBulletStratShort, future, userTF, H, L, H2, L2, noBorders, silverBulletLongTP, historicalPoints, historicalData, silverBulletLongSL, silverBulletShortTP, silverBulletShortSL)   used to execute the Silver Bullet Strategy   Parameters:      silverBulletStratLong (simple bool)      silverBulletStratShort (simple bool)      future (int) : a future time, used for drawings, example "last_bar_time"      userTF (simple int)      H (float) : the high price of the user-selected TF      L (float) : the low price of the user-selected TF      H2 (float) : the high price of the user-selected TF      L2 (float) : the low price of the user-selected TF      noBorders (bool) : an input.bool() used to remove the borders from box drawings      silverBulletLongTP (series silverBulletLevels)      historicalPoints (array)      historicalData (necessaryData)      silverBulletLongSL (series silverBulletLevels)      silverBulletShortTP (series silverBulletLevels)      silverBulletShortSL (series silverBulletLevels)   Returns: void method invalidFVGcheck(FVGarr, upFVGpricesSorted, dnFVGpricesSorted)   check if existing FVGs are still valid   Namespace types: array   Parameters:      FVGarr (array)      upFVGpricesSorted (array) : an array of bullish FVG prices, used to selective search through FVG array to remove invalidated levels      dnFVGpricesSorted (array) : an array of bearish FVG prices, used to selective search through FVG array to remove invalidated levels   Returns: void (0) method drawFVG(counter, FVGshow, FVGname, FVGcol, data, masterCoords, labelLevels, borderTransp, liteMode, rightCoordinate)   draws FVGs on last bar   Namespace types: map   Parameters:      counter (map) : a counter, as map, keeping count of the number of FVGs drawn, makes sure that there aren't more FVGs drawn than int FVGshow      FVGshow (int) : the number of FVGs to show. There should be a bullish FVG show and bearish FVG show. This function "drawFVG" is used separately for bearish FVG and bullish FVG.      FVGname (string) : the name of the FVG, "FVG Up" or "FVG Down"      FVGcol (color) : desired FVG color      data (FVG)      masterCoords (map) : a map containing the names and price points of key levels. Used to define price ranges.      labelLevels (string) : an input.string with options "Inside", "Outside", "Remove". Determines whether FVG labels should be inside box, outside, or na.      borderTransp (int)      liteMode (bool)      rightCoordinate (int) : the right coordinate of any drawings. Must be a time point.   Returns: void invalidBlockCheck(bullishOBbox, bearishOBbox, userTF)   check if existing order blocks are still valid   Parameters:      bullishOBbox (array) : an array declared using the UDT orderBlock that contains bullish order block related data      bearishOBbox (array) : an array declared using the UDT orderBlock that contains bearish order block related data      userTF (simple int)   Returns: void (0) method lastBarRejections(id, rejectionColor, idShow, rejectionString, labelLevels, borderTransp, liteMode, rightCoordinate, masterCoords)   draws rejectionBlocks on last bar   Namespace types: array   Parameters:      id (array) : the array, an array of rejection block data declared using the UDT rejection block      rejectionColor (color) : the desired color of the rejection box      idShow (int)      rejectionString (string) : the desired name of the rejection blocks      labelLevels (string) : an input.string() to determine if labels for the block should be inside the box, outside, or none.      borderTransp (int)      liteMode (bool) : an input.bool(). True = neon effect, false = no neon.      rightCoordinate (int) : atime for the right coordinate of the box      masterCoords (map) : a map that stores the price of key levels and assigns them a name, used to determine price ranges   Returns: void method OBdraw(id, OBshow, BBshow, OBcol, BBcol, bullishString, bearishString, isBullish, labelLevels, borderTransp, liteMode, rightCoordinate, masterCoords)   draws orderblocks and breaker blocks for data stored in UDT array()   Namespace types: array   Parameters:      id (array) : the array, an array of order block data declared using the UDT orderblock      OBshow (int) : the number of order blocks to show      BBshow (int) : the number of breaker blocks to show      OBcol (color) : color of order blocks      BBcol (color) : color of breaker blocks      bullishString (string) : the title of bullish blocks, which is a regular bullish orderblock or a bearish orderblock that's converted to breakerblock      bearishString (string) : the title of bearish blocks, which is a regular bearish orderblock or a bullish orderblock that's converted to breakerblock      isBullish (bool) : whether the array contains bullish orderblocks or bearish orderblocks. If bullish orderblocks, the array will naturally contain bearish BB, and if bearish OB, the array will naturally contain bullish BB      labelLevels (string) : an input.string() to determine if labels for the block should be inside the box, outside, or none.      borderTransp (int)      liteMode (bool) : an input.bool(). True = neon effect, false = no neon.      rightCoordinate (int) : atime for the right coordinate of the box      masterCoords (map) : a map that stores the price of key levels and assigns them a name, used to determine price ranges   Returns: void FVG   UDT for FVG calcualtions   Fields:      H (series float) : high price of user-selected timeframe      L (series float) : low price of user-selected timeframe      direction (series string) : FVG direction => "Up" or "Down"      T (series int) : => time of bar on user-selected timeframe where FVG was created      fvgLabel (series label) : optional label for FVG      fvgLineTop (series line) : optional line for top of FVG      fvgLineBot (series line) : optional line for bottom of FVG      fvgBox (series box) : optional box for FVG labelLine   quickly pair a line and label together as UDT   Fields:      lin (series line) : Line you wish to pair with label      lab (series label) : Label you wish to pair with line orderBlock   UDT for order block calculations   Fields:      orderBlockData (array) : array containing order block x and y points      orderBlockBox (series box) : optional order block box      vioCount (series int) : = 0 violation count of the order block. 0 = Order Block, 1 = Breaker Block      traded (series bool)      status (series string) : = "OB" status == "OB" => Level is order block. status == "BB" => Level is breaker block.      orderBlockLab (series label) : options label for the order block / breaker block. strongPoints   UDT for strong highs and strong lows   Fields:      price (series float) : price of the strong high or strong low      timeAtprice (series int) : time of the strong high or strong low      strongPointLabel (series label) : optional label for strong point      strongPointLine (series line) : optional line for strong point      overlayLine (series line) : optional lines for strong point to enhance visibility      overlayLine2 (series line) : optional lines for strong point to enhance visibility displacement   UDT for dispacements   Fields:      highPrice (series float) : high price of displacement      lowPrice (series float) : low price of displacement      timeAtPrice (series int) : time of bar where displacement occurred      displacementBox (series box) : optional box to draw displacement      displacementLab (series label) : optional label for displacement po3data   UDT for po3 calculations   Fields:      dHigh (series float) : higher timeframe high price      dLow (series float) : higher timeframe low price      dOpen (series float) : higher timeframe open price      dClose (series float) : higher timeframe close price      po3box (series box) : box to draw po3 candle body      po3line (array) : line array to draw po3 wicks      po3Labels (array) : label array to label price points of po3 candle macros   UDT for session macros   Fields:      sessions (array) : Array of sessions, you can populate this array using the "quickTime" function located above "export macros".      prices (matrix) : Matrix of session data -> open, high, low, close, time      sessionTimes (array) : Array of session names. Pairs with array sessions.      sessionLines (matrix) : Optional array for sesion drawings. OTEtimes   UDT for data storage and drawings associated with OTE strategy   Fields:      upTimes (array) : time of highest point before trade is taken      dnTimes (array) : time of lowest point before trade is taken      tpLineLong (series line) : line to mark tp level long      tpLabelLong (series label) : label to mark tp level long      slLineLong (series line) : line to mark sl level long      slLabelLong (series label) : label to mark sl level long      tpLineShort (series line) : line to mark tp level short      tpLabelShort (series label) : label to mark tp level short      slLineShort (series line) : line to mark sl level short      slLabelShort (series label) : label to mark sl level short sweeps   UDT for data storage and drawings associated with liquidity sweeps   Fields:      upSweeps (matrix) : matrix containing liquidity sweep price points and time points for up sweeps      dnSweeps (matrix) : matrix containing liquidity sweep price points and time points for down sweeps      upSweepDrawings (array) : optional up sweep box array. Pair the size of this array with the rows or columns,      dnSweepDrawings (array) : optional up sweep box array. Pair the size of this array with the rows or columns, raidExitDrawings   UDT for drawings associated with the Liquidity Raid Strategy   Fields:      tpLine (series line) : tp line for the liquidity raid entry      tpLabel (series label) : tp label for the liquidity raid entry      slLine (series line) : sl line for the liquidity raid entry      slLabel (series label) : sl label for the liquidity raid entry m2022   UDT for data storage and drawings associated with the Model 2022 Strategy   Fields:      mTime (series int) : time of the FVG where entry limit order is placed      mIndex (series int) : array index of FVG where entry limit order is placed. This requires an array of FVG data, which is defined above.      mEntryDistance (series float) : the distance of the FVG to the 50% range. M2022 looks for the fvg closest to 50% mark of range.      mEntry (series float) : the entry price for the most eligible fvg      fvgHigh (series float) : the high point of the eligible fvg      fvgLow (series float) : the low point of the eligible fvg      longFVGentryBox (series box) : long FVG box, used to draw the eligible FVG      shortFVGentryBox (series box) : short FVG box, used to draw the eligible FVG      line50P (series line) : line used to mark 50% of the range      line100P (series line) : line used to mark 100% (top) of the range      line0P (series line) : line used to mark 0% (bottom) of the range      label50P (series label) : label used to mark 50% of the range      label100P (series label) : label used to mark 100% (top) of the range      label0P (series label) : label used to mark 0% (bottom) of the range      sweepData (array) silverBullet   UDT for data storage and drawings associated with the Silver Bullet Strategy   Fields:      session (series bool)      sessionStr (series string) : name of the session for silver bullet      sessionBias (series string)      sessionHigh (series float) : = high high of session // use math.max(silverBullet.sessionHigh, high)      sessionLow (series float) : = low low of session // use math.min(silverBullet.sessionLow, low)      sessionFVG (series float) : if applicable, the FVG created during the session      sessionFVGdraw (series box) : if applicable, draw the FVG created during the session      traded (series bool)      tp (series float) : tp of trade entered at the session FVG      sl (series float) : sl of trade entered at the session FVG      sessionDraw (series box) : optional draw session with box      sessionDrawLabel (series label) : optional label session with label silverBulletDrawings   UDT for trade exit drawings associated with the Silver Bullet Strategy   Fields:      tpLine (series line) : tp line drawing for strategy      tpLabel (series label) : tp label drawing for strategy      slLine (series line) : sl line drawing for strategy      slLabel (series label) : sl label drawing for strategy unicornModel   UDT for data storage and drawings associated with the Unicorn Model Strategy   Fields:      hPoint (chart.point)      hPoint2 (chart.point)      hPoint3 (chart.point)      breakerBlock (series box) : used to draw the breaker block required for the Unicorn Model      FVG (series box) : used to draw the FVG required for the Unicorn model      topBlock (series float) : price of top of breaker block, can be used to detail trade entry      botBlock (series float) : price of bottom of breaker block, can be used to detail trade entry      startBlock (series int) : start time of the breaker block, used to set the "left = " param for the box      includes (array) : used to store the time of the breaker block, or FVG, or the chart point sequence that setup the Unicorn Model.      entry (series float) : // eligible entry price, for longs"math.max(topBlock, FVG.get_top())",      tpLine (series line) : optional line to mark PT      tpLabel (series label) : optional label to mark PT      slLine (series line) : optional line to mark SL      slLabel (series label) : optional label to mark SL rejectionBlocks   UDT for data storage and drawings associated with rejection blocks   Fields:      rejectionPoint (chart.point)      bodyPrice (series float) : candle body price closest to the rejection point, for "Up" rejections => math.max(open, close),      rejectionBox (series box) : optional box drawing of the rejection block      rejectionLabel (series label) : optional label for the rejection block equalLevelsDraw   UDT for data storage and drawings associated with equal highs / equal lows   Fields:      connector (series line) : single line placed at the first high or low, y = avgerage of distinguished equal highs/lows      connectorLab (series label) : optional label to be placed at the highs or lows      levels (array) : array containing the equal highs or lows prices      times (array) : array containing the equal highs or lows individual times      startTime (series int) : the time of the first high or low that forms a sequence of equal highs or lows      radiate (array) : options label to "radiate" the label in connector lab. Can be used for anything necessaryData   UDT for data storage of historical price points.   Fields:      highArr (array) : array containing historical high points      lowArr (array) : array containing historical low points      timeArr (array) : array containing historical time points      logArr (array) : array containing historical log returns      signArr (array) : array containing historical price directions      closeArr (array) : array containing historical close points      binaryTimeArr (array) : array containing historical time points, uses "push" instead of "unshift" to allow for binary search      binaryCloseArr (array) : array containing historical close points, uses "push" instead of "unshift" to allow the correct      binaryOpenArr (array) : array containing historical optn points, uses "push" instead of "unshift" to allow the correct      atrTFarr (array) : array containing historical user-selected TF atr points      openArr (array) : array containing historical open points
Pine Script® library
by Trading-IQ
Smart Market Structure and Swing Points, version 1.0Smart Market Structure and Swing Points, Version 1.0 Overview The Smart Market Structure and Swing Points script is designed to provide advanced insights into market structure and key swing points. This script helps identify important highs and lows, trend direction changes (structure breaks), and swing points, enhancing decision-making for both trend-following and reversal strategies. See below for detail presentation and why it has unique features. Unique Features of the New Script Market Structure Identification : Analyzes and marks key highs and lows to determine market structure, including higher highs, lower highs, higher lows, and lower lows. Customizable Detection Length : Allows users to set the length for detecting highs and lows, providing flexibility to adapt to different market conditions and timeframes. Default value is 5 bars, but can be changed if needed. Visual Signal Indicators (Labels) : Plots labels on the chart to indicate higher highs (HH), lower highs (LH), higher lows (HL), and lower lows (LL), along with corresponding RSI values, offering clear visual cues for market structure analysis. The indication of RSI values directly on high and low points enables to better judge whether the points are strong references (extreme RSI values) or weak references (middle RSI values) Dynamic Trend Lines : Draws solid and dotted lines to connect significant highs and lows, visually representing the current trend direction and potential trend changes. Dashed lines indicates structure breaks. Swing High and Swing Low Detection : Identifies and marks the most recent swing highs and swing lows, helping traders spot potential reversal points and key levels for setting stop losses or take profit targets . Originality and Usefulness This script combines market structure, trend breaks and RSI to provide a more robust view of market dynamic by indicating the strength or weakness of swing points , in that way the script is unique. Signal Description The script includes various signal features that highlight potential trading opportunities based on market structure: Higher Highs (HH) and Higher Lows (HL) : These labels are plotted when new highs or lows are formed, indicating a continuation of an uptrend. The labels are positioned with consideration of the Average True Range (ATR) for better visibility. Lower Highs (LH) and Lower Lows (LL) : These labels are plotted when new highs or lows are formed, indicating a continuation of a downtrend. The labels include RSI values to provide additional information on the strength or weakness of the points. Trend Direction Change : Dotted lines are drawn to indicate potential trend direction changes when the script detects significant shifts in market structure. Swing Highs and Swing Lows : These are identified based on a customizable swing length, marking recent significant highs and lows to highlight potential reversal points. These signals help identify high-probability turning points and confirm trend direction by ensuring that the market structure aligns with the trading strategy. Detailed Description Input Variables Length for High/Low Detection (`length`) : Defines the range to check for highs and lows. Default is 5. RSI Length (`rsilength`) : The number of periods to calculate the RSI. Default is 14. Functionality Market Structure Calculation : The script determines the highest high and lowest low within the specified range to identify key points in market structure. ```pine h = ta.highest(high, length * 2 + 1) l = ta.lowest(low, length * 2 + 1) ``` Directional Logic : Variables and functions manage the state of the indicator, updating highs and lows based on the current trend direction. ```pine var bool dirUp = false var float lastLow = high * 100 var float lastHigh = 0.0 // Additional variables for tracking state ``` Drawing Lines and Labels : Functions draw lines and labels on the chart to visualize market structure and trend changes. ```pine f_drawLine() => _li_color = dirUp ? color.red : color.lime line.new(x1=timeHigh - length, y1=lastHigh, x2=timeLow - length, y2=lastLow, color=_li_color, width=3, style=line.style_solid, xloc=xloc.bar_index) f_drawLastLine() => _li_color = dirUp ? color.blue : color.blue if timeHigh > timeLow line.new(x1=timeHigh - length, y1=lastHigh, x2=bar_index, y2=low, color=_li_color, width=2, style=line.style_dotted, xloc=xloc.bar_index) else line.new(x1=timeLow - length, y1=lastLow, x2=bar_index, y2=high, color=_li_color, width=2, style=line.style_dotted, xloc=xloc.bar_index) ``` Updating Highs and Lows : The main logic updates highs and lows based on the current trend direction, adding labels for new higher highs, lower highs, higher lows, and lower lows. ```pine if dirUp if f_isMin(length) lastLow := low // Additional logic for updating lows and labels if f_isMax(length) and high > lastLow lastHigh := high // Additional logic for updating highs and labels dirUp := false li := f_drawLine() ``` Swing Highs and Lows : The script identifies recent swing highs and swing lows based on a customizable swing length, drawing lines to mark these points. ```pine swingLength = 3 * length isSwingHigh = ta.highestbars(high, swingLength) == 0 isSwingLow = ta.lowestbars(low, swingLength) == 0 if (isSwingHigh) if (na(highLine)) highLine := line.new(bar_index, high, bar_index, high, color=color.green, style=line.style_solid, width=1) else line.set_xy1(highLine, bar_index, high) line.set_xy2(highLine, bar_index + swingLength, high) if (isSwingLow) if (na(lowLine)) lowLine := line.new(bar_index, low, bar_index, low, color=color.red, style=line.style_solid, width=1) else line.set_xy1(lowLine, bar_index, low) line.set_xy2(lowLine, bar_index + swingLength, low) ``` How to Use Configuring Inputs : Adjust the detection length and RSI length as needed. Modify the lookback periods to suit your trading strategy. The indicator is adaptable and can be used on any timeframe. Interpreting the Indicator : Use the labels and lines to gauge market structure and trend direction. Look for higher highs, lower highs, higher lows, and lower lows to confirm market structure. Signal Confirmation : Pay attention to the labels and lines that provide signals for potential trend changes and swing points. Use these signals to better time entries and exits. This script provides a detailed view of market structure and swing points, helping make more informed decisions by considering key highs and lows, trend direction changes, and the strength or weakness of swing points.
Pine Script® indicator
by adridem
3
MarketStructureLibrary "MarketStructure" This library contains functions for identifying Lows and Highs in a rule-based way, and deriving useful information from them. f_simpleLowHigh() This function finds Local Lows and Highs, but NOT in order. A Local High is any candle that has its Low taken out on close by a subsequent candle (and vice-versa for Local Lows). The Local High does NOT have to be the candle with the highest High out of recent candles. It does NOT have to be a Williams High. It is not necessarily a swing high or a reversal or anything else. It doesn't have to be "the" high, so don't be confused. By the rules, Local Lows and Highs must alternate. In this function they do not, so I'm calling them Simple Lows and Highs. Simple Highs and Lows, by the above definition, can be useful for entries and stops. Because I intend to use them for stops, I want them all, not just the ones that alternate in strict order. @param - there are no parameters. The function uses the chart OHLC. @returns boolean values for whether this bar confirms a Simple Low/High, and ints for the bar_index of that Low/High. f_localLowHigh() This function finds Local Lows and Highs, in order. A Local High is any candle that has its Low taken out on close by a subsequent candle (and vice-versa for Local Lows). The Local High does NOT have to be the candle with the highest High out of recent candles. It does NOT have to be a Williams High. It is not necessarily a swing high or a reversal or anything else. By the rules, Local Lows and Highs must alternate, and in this function they do. @param - there are no parameters. The function uses the chart OHLC. @returns boolean values for whether this bar confirms a Local Low/High, and ints for the bar_index of that Low/High. f_enhancedSimpleLowHigh() This function finds Local Lows and Highs, but NOT in order. A Local High is any candle that has its Low taken out on close by a subsequent candle (and vice-versa for Local Lows). The Local High does NOT have to be the candle with the highest High out of recent candles. It does NOT have to be a Williams High. It is not necessarily a swing high or a reversal or anything else. By the rules, Local Lows and Highs must alternate. In this function they do not, so I'm calling them Simple Lows and Highs. Simple Highs and Lows, by the above definition, can be useful for entries and stops. Because I intend to use them for trailing stops, I want them all, not just the ones that alternate in strict order. The difference between this function and f_simpleLowHigh() is that it also tracks the lowest/highest recent level. This level can be useful for trailing stops. In effect, these are like more "normal" highs and lows that you would pick by eye, but confirmed faster in many cases than by waiting for the low/high of that particular candle to be taken out on close, because they are instead confirmed by ANY subsequent candle having its low/high exceeded. Hence, I call these Enhanced Simple Lows/Highs. The levels are taken from the extreme highs/lows, but the bar indexes are given for the candles that were actually used to confirm the Low/High. This is by design, because it might be misleading to label the extreme, since we didn't use that candle to confirm the Low/High.. @param - there are no parameters. The function uses the chart OHLC. @returns - boolean values for whether this bar confirms an Enhanced Simple Low/High ints for the bar_index of that Low/High floats for the values of the recent high/low levels floats for the trailing high/low levels (for debug/post-processing) bools for market structure bias f_trueLowHigh() This function finds True Lows and Highs. A True High is the candle with the highest recent high, which then has its low taken out on close by a subsequent candle (and vice-versa for True Lows). The difference between this and an Enhanced High is that confirmation requires not just any Simple High, but confirmation of the very candle that has the highest high. Because of this, confirmation is often later, and multiple Simple Highs and Lows can develop within ranges formed by a single big candle without any of them being confirmed. This is by design. A True High looks like the intuitive "real high" when you look at the chart. True Lows and Highs must alternate. @param - there are no parameters. The function uses the chart OHLC. @returns - boolean values for whether this bar confirms an Enhanced Simple Low/High ints for the bar_index of that Low/High floats for the values of the recent high/low levels floats for the trailing high/low levels (for debug/post-processing) bools for market structure bias
Pine Script® library
by SimpleCryptoLife
13
ATAI Volume analysis with price action V 1.00ATAI Volume Analysis with Price Action 1. Introduction 1.1 Overview ATAI Volume Analysis with Price Action is a composite indicator designed for TradingView. It combines per‑side volume data —that is, how much buying and selling occurs during each bar—with standard price‑structure elements such as swings, trend lines and support/resistance. By blending these elements the script aims to help a trader understand which side is in control, whether a breakout is genuine, when markets are potentially exhausted and where liquidity providers might be active. The indicator is built around TradingView’s up/down volume feed accessed via the TradingView/ta/10 library. The following excerpt from the script illustrates how this feed is configured: import TradingView/ta/10 as tvta // Determine lower timeframe string based on user choice and chart resolution string lower_tf_breakout = use_custom_tf_input ? custom_tf_input : timeframe.isseconds ? "1S" : timeframe.isintraday ? "1" : timeframe.isdaily ? "5" : "60" // Request up/down volume (both positive) = tvta.requestUpAndDownVolume(lower_tf_breakout) Lower‑timeframe selection. If you do not specify a custom lower timeframe, the script chooses a default based on your chart resolution: 1 second for second charts, 1 minute for intraday charts, 5 minutes for daily charts and 60 minutes for anything longer. Smaller intervals provide a more precise view of buyer and seller flow but cover fewer bars. Larger intervals cover more history at the cost of granularity. Tick vs. time bars. Many trading platforms offer a tick / intrabar calculation mode that updates an indicator on every trade rather than only on bar close. Turning on one‑tick calculation will give the most accurate split between buy and sell volume on the current bar, but it typically reduces the amount of historical data available. For the highest fidelity in live trading you can enable this mode; for studying longer histories you might prefer to disable it. When volume data is completely unavailable (some instruments and crypto pairs), all modules that rely on it will remain silent and only the price‑structure backbone will operate. Figure caption, Each panel shows the indicator’s info table for a different volume sampling interval. In the left chart, the parentheses “(5)” beside the buy‑volume figure denote that the script is aggregating volume over five‑minute bars; the center chart uses “(1)” for one‑minute bars; and the right chart uses “(1T)” for a one‑tick interval. These notations tell you which lower timeframe is driving the volume calculations. Shorter intervals such as 1 minute or 1 tick provide finer detail on buyer and seller flow, but they cover fewer bars; longer intervals like five‑minute bars smooth the data and give more history. Figure caption, The values in parentheses inside the info table come directly from the Breakout — Settings. The first row shows the custom lower-timeframe used for volume calculations (e.g., “(1)”, “(5)”, or “(1T)”) 2. Price‑Structure Backbone Even without volume, the indicator draws structural features that underpin all other modules. These features are always on and serve as the reference levels for subsequent calculations. 2.1 What it draws • Pivots: Swing highs and lows are detected using the pivot_left_input and pivot_right_input settings. A pivot high is identified when the high recorded pivot_right_input bars ago exceeds the highs of the preceding pivot_left_input bars and is also higher than (or equal to) the highs of the subsequent pivot_right_input bars; pivot lows follow the inverse logic. The indicator retains only a fixed number of such pivot points per side, as defined by point_count_input, discarding the oldest ones when the limit is exceeded. • Trend lines: For each side, the indicator connects the earliest stored pivot and the most recent pivot (oldest high to newest high, and oldest low to newest low). When a new pivot is added or an old one drops out of the lookback window, the line’s endpoints—and therefore its slope—are recalculated accordingly. • Horizontal support/resistance: The highest high and lowest low within the lookback window defined by length_input are plotted as horizontal dashed lines. These serve as short‑term support and resistance levels. • Ranked labels: If showPivotLabels is enabled the indicator prints labels such as “HH1”, “HH2”, “LL1” and “LL2” near each pivot. The ranking is determined by comparing the price of each stored pivot: HH1 is the highest high, HH2 is the second highest, and so on; LL1 is the lowest low, LL2 is the second lowest. In the case of equal prices the newer pivot gets the better rank. Labels are offset from price using ½ × ATR × label_atr_multiplier, with the ATR length defined by label_atr_len_input. A dotted connector links each label to the candle’s wick. 2.2 Key settings • length_input: Window length for finding the highest and lowest values and for determining trend line endpoints. A larger value considers more history and will generate longer trend lines and S/R levels. • pivot_left_input, pivot_right_input: Strictness of swing confirmation. Higher values require more bars on either side to form a pivot; lower values create more pivots but may include minor swings. • point_count_input: How many pivots are kept in memory on each side. When new pivots exceed this number the oldest ones are discarded. • label_atr_len_input and label_atr_multiplier: Determine how far pivot labels are offset from the bar using ATR. Increasing the multiplier moves labels further away from price. • Styling inputs for trend lines, horizontal lines and labels (color, width and line style). Figure caption, The chart illustrates how the indicator’s price‑structure backbone operates. In this daily example, the script scans for bars where the high (or low) pivot_right_input bars back is higher (or lower) than the preceding pivot_left_input bars and higher or lower than the subsequent pivot_right_input bars; only those bars are marked as pivots. These pivot points are stored and ranked: the highest high is labelled “HH1”, the second‑highest “HH2”, and so on, while lows are marked “LL1”, “LL2”, etc. Each label is offset from the price by half of an ATR‑based distance to keep the chart clear, and a dotted connector links the label to the actual candle. The red diagonal line connects the earliest and latest stored high pivots, and the green line does the same for low pivots; when a new pivot is added or an old one drops out of the lookback window, the end‑points and slopes adjust accordingly. Dashed horizontal lines mark the highest high and lowest low within the current lookback window, providing visual support and resistance levels. Together, these elements form the structural backbone that other modules reference, even when volume data is unavailable. 3. Breakout Module 3.1 Concept This module confirms that a price break beyond a recent high or low is supported by a genuine shift in buying or selling pressure. It requires price to clear the highest high (“HH1”) or lowest low (“LL1”) and, simultaneously, that the winning side shows a significant volume spike, dominance and ranking. Only when all volume and price conditions pass is a breakout labelled. 3.2 Inputs • lookback_break_input : This controls the number of bars used to compute moving averages and percentiles for volume. A larger value smooths the averages and percentiles but makes the indicator respond more slowly. • vol_mult_input : The “spike” multiplier; the current buy or sell volume must be at least this multiple of its moving average over the lookback window to qualify as a breakout. • rank_threshold_input (0–100) : Defines a volume percentile cutoff: the current buyer/seller volume must be in the top (100−threshold)%(100−threshold)% of all volumes within the lookback window. For example, if set to 80, the current volume must be in the top 20 % of the lookback distribution. • ratio_threshold_input (0–1) : Specifies the minimum share of total volume that the buyer (for a bullish breakout) or seller (for bearish) must hold on the current bar; the code also requires that the cumulative buyer volume over the lookback window exceeds the seller volume (and vice versa for bearish cases). • use_custom_tf_input / custom_tf_input : When enabled, these inputs override the automatic choice of lower timeframe for up/down volume; otherwise the script selects a sensible default based on the chart’s timeframe. • Label appearance settings : Separate options control the ATR-based offset length, offset multiplier, label size and colors for bullish and bearish breakout labels, as well as the connector style and width. 3.3 Detection logic 1. Data preparation : Retrieve per‑side volume from the lower timeframe and take absolute values. Build rolling arrays of the last lookback_break_input values to compute simple moving averages (SMAs), cumulative sums and percentile ranks for buy and sell volume. 2. Volume spike: A spike is flagged when the current buy (or, in the bearish case, sell) volume is at least vol_mult_input times its SMA over the lookback window. 3. Dominance test: The buyer’s (or seller’s) share of total volume on the current bar must meet or exceed ratio_threshold_input. In addition, the cumulative sum of buyer volume over the window must exceed the cumulative sum of seller volume for a bullish breakout (and vice versa for bearish). A separate requirement checks the sign of delta: for bullish breakouts delta_breakout must be non‑negative; for bearish breakouts it must be non‑positive. 4. Percentile rank: The current volume must fall within the top (100 – rank_threshold_input) percent of the lookback distribution—ensuring that the spike is unusually large relative to recent history. 5. Price test: For a bullish signal, the closing price must close above the highest pivot (HH1); for a bearish signal, the close must be below the lowest pivot (LL1). 6. Labeling: When all conditions above are satisfied, the indicator prints “Breakout ↑” above the bar (bullish) or “Breakout ↓” below the bar (bearish). Labels are offset using half of an ATR‑based distance and linked to the candle with a dotted connector. Figure caption, (Breakout ↑ example) , On this daily chart, price pushes above the red trendline and the highest prior pivot (HH1). The indicator recognizes this as a valid breakout because the buyer‑side volume on the lower timeframe spikes above its recent moving average and buyers dominate the volume statistics over the lookback period; when combined with a close above HH1, this satisfies the breakout conditions. The “Breakout ↑” label appears above the candle, and the info table highlights that up‑volume is elevated relative to its 11‑bar average, buyer share exceeds the dominance threshold and money‑flow metrics support the move. Figure caption, In this daily example, price breaks below the lowest pivot (LL1) and the lower green trendline. The indicator identifies this as a bearish breakout because sell‑side volume is sharply elevated—about twice its 11‑bar average—and sellers dominate both the bar and the lookback window. With the close falling below LL1, the script triggers a Breakout ↓ label and marks the corresponding row in the info table, which shows strong down volume, negative delta and a seller share comfortably above the dominance threshold. 4. Market Phase Module (Volume Only) 4.1 Concept Not all markets trend; many cycle between periods of accumulation (buying pressure building up), distribution (selling pressure dominating) and neutral behavior. This module classifies the current bar into one of these phases without using ATR , relying solely on buyer and seller volume statistics. It looks at net flows, ratio changes and an OBV‑like cumulative line with dual‑reference (1‑ and 2‑bar) trends. The result is displayed both as on‑chart labels and in a dedicated row of the info table. 4.2 Inputs • phase_period_len: Number of bars over which to compute sums and ratios for phase detection. • phase_ratio_thresh : Minimum buyer share (for accumulation) or minimum seller share (for distribution, derived as 1 − phase_ratio_thresh) of the total volume. • strict_mode: When enabled, both the 1‑bar and 2‑bar changes in each statistic must agree on the direction (strict confirmation); when disabled, only one of the two references needs to agree (looser confirmation). • Color customisation for info table cells and label styling for accumulation and distribution phases, including ATR length, multiplier, label size, colors and connector styles. • show_phase_module: Toggles the entire phase detection subsystem. • show_phase_labels: Controls whether on‑chart labels are drawn when accumulation or distribution is detected. 4.3 Detection logic The module computes three families of statistics over the volume window defined by phase_period_len: 1. Net sum (buyers minus sellers): net_sum_phase = Σ(buy) − Σ(sell). A positive value indicates a predominance of buyers. The code also computes the differences between the current value and the values 1 and 2 bars ago (d_net_1, d_net_2) to derive up/down trends. 2. Buyer ratio: The instantaneous ratio TF_buy_breakout / TF_tot_breakout and the window ratio Σ(buy) / Σ(total). The current ratio must exceed phase_ratio_thresh for accumulation or fall below 1 − phase_ratio_thresh for distribution. The first and second differences of the window ratio (d_ratio_1, d_ratio_2) determine trend direction. 3. OBV‑like cumulative net flow: An on‑balance volume analogue obv_net_phase increments by TF_buy_breakout − TF_sell_breakout each bar. Its differences over the last 1 and 2 bars (d_obv_1, d_obv_2) provide trend clues. The algorithm then combines these signals: • For strict mode , accumulation requires: (a) current ratio ≥ threshold, (b) cumulative ratio ≥ threshold, (c) both ratio differences ≥ 0, (d) net sum differences ≥ 0, and (e) OBV differences ≥ 0. Distribution is the mirror case. • For loose mode , it relaxes the directional tests: either the 1‑ or the 2‑bar difference needs to agree in each category. If all conditions for accumulation are satisfied, the phase is labelled “Accumulation” ; if all conditions for distribution are satisfied, it’s labelled “Distribution” ; otherwise the phase is “Neutral” . 4.4 Outputs • Info table row : Row 8 displays “Market Phase (Vol)” on the left and the detected phase (Accumulation, Distribution or Neutral) on the right. The text colour of both cells matches a user‑selectable palette (typically green for accumulation, red for distribution and grey for neutral). • On‑chart labels : When show_phase_labels is enabled and a phase persists for at least one bar, the module prints a label above the bar ( “Accum” ) or below the bar ( “Dist” ) with a dashed or dotted connector. The label is offset using ATR based on phase_label_atr_len_input and phase_label_multiplier and is styled according to user preferences. Figure caption, The chart displays a red “Dist” label above a particular bar, indicating that the accumulation/distribution module identified a distribution phase at that point. The detection is based on seller dominance: during that bar, the net buyer-minus-seller flow and the OBV‑style cumulative flow were trending down, and the buyer ratio had dropped below the preset threshold. These conditions satisfy the distribution criteria in strict mode. The label is placed above the bar using an ATR‑based offset and a dashed connector. By the time of the current bar in the screenshot, the phase indicator shows “Neutral” in the info table—signaling that neither accumulation nor distribution conditions are currently met—yet the historical “Dist” label remains to mark where the prior distribution phase began. Figure caption, In this example the market phase module has signaled an Accumulation phase. Three bars before the current candle, the algorithm detected a shift toward buyers: up‑volume exceeded its moving average, down‑volume was below average, and the buyer share of total volume climbed above the threshold while the on‑balance net flow and cumulative ratios were trending upwards. The blue “Accum” label anchored below that bar marks the start of the phase; it remains on the chart because successive bars continue to satisfy the accumulation conditions. The info table confirms this: the “Market Phase (Vol)” row still reads Accumulation, and the ratio and sum rows show buyers dominating both on the current bar and across the lookback window. 5. OB/OS Spike Module 5.1 What overbought/oversold means here In many markets, a rapid extension up or down is often followed by a period of consolidation or reversal. The indicator interprets overbought (OB) conditions as abnormally strong selling risk at or after a price rally and oversold (OS) conditions as unusually strong buying risk after a decline. Importantly, these are not direct trade signals; rather they flag areas where caution or contrarian setups may be appropriate. 5.2 Inputs • minHits_obos (1–7): Minimum number of oscillators that must agree on an overbought or oversold condition for a label to print. • syncWin_obos: Length of a small sliding window over which oscillator votes are smoothed by taking the maximum count observed. This helps filter out choppy signals. • Volume spike criteria: kVolRatio_obos (ratio of current volume to its SMA) and zVolThr_obos (Z‑score threshold) across volLen_obos. Either threshold can trigger a spike. • Oscillator toggles and periods: Each of RSI, Stochastic (K and D), Williams %R, CCI, MFI, DeMarker and Stochastic RSI can be independently enabled; their periods are adjustable. • Label appearance: ATR‑based offset, size, colors for OB and OS labels, plus connector style and width. 5.3 Detection logic 1. Directional volume spikes: Volume spikes are computed separately for buyer and seller volumes. A sell volume spike (sellVolSpike) flags a potential OverBought bar, while a buy volume spike (buyVolSpike) flags a potential OverSold bar. A spike occurs when the respective volume exceeds kVolRatio_obos times its simple moving average over the window or when its Z‑score exceeds zVolThr_obos. 2. Oscillator votes: For each enabled oscillator, calculate its overbought and oversold state using standard thresholds (e.g., RSI ≥ 70 for OB and ≤ 30 for OS; Stochastic %K/%D ≥ 80 for OB and ≤ 20 for OS; etc.). Count how many oscillators vote for OB and how many vote for OS. 3. Minimum hits: Apply the smoothing window syncWin_obos to the vote counts using a maximum‑of‑last‑N approach. A candidate bar is only considered if the smoothed OB hit count ≥ minHits_obos (for OverBought) or the smoothed OS hit count ≥ minHits_obos (for OverSold). 4. Tie‑breaking: If both OverBought and OverSold spike conditions are present on the same bar, compare the smoothed hit counts: the side with the higher count is selected; ties default to OverBought. 5. Label printing: When conditions are met, the bar is labelled as “OverBought X/7” above the candle or “OverSold X/7” below it. “X” is the number of oscillators confirming, and the bracket lists the abbreviations of contributing oscillators. Labels are offset from price using half of an ATR‑scaled distance and can optionally include a dotted or dashed connector line. Figure caption, In this chart the overbought/oversold module has flagged an OverSold signal. A sell‑off from the prior highs brought price down to the lower trend‑line, where the bar marked “OverSold 3/7 DeM” appears. This label indicates that on that bar the module detected a buy‑side volume spike and that at least three of the seven enabled oscillators—in this case including the DeMarker—were in oversold territory. The label is printed below the candle with a dotted connector, signaling that the market may be temporarily exhausted on the downside. After this oversold print, price begins to rebound towards the upper red trend‑line and higher pivot levels. Figure caption, This example shows the overbought/oversold module in action. In the left‑hand panel you can see the OB/OS settings where each oscillator (RSI, Stochastic, Williams %R, CCI, MFI, DeMarker and Stochastic RSI) can be enabled or disabled, and the ATR length and label offset multiplier adjusted. On the chart itself, price has pushed up to the descending red trendline and triggered an “OverBought 3/7” label. That means the sell‑side volume spiked relative to its average and three out of the seven enabled oscillators were in overbought territory. The label is offset above the candle by half of an ATR and connected with a dashed line, signaling that upside momentum may be overextended and a pause or pullback could follow. 6. Buyer/Seller Trap Module 6.1 Concept A bull trap occurs when price appears to break above resistance, attracting buyers, but fails to sustain the move and quickly reverses, leaving a long upper wick and trapping late entrants. A bear trap is the opposite: price breaks below support, lures in sellers, then snaps back, leaving a long lower wick and trapping shorts. This module detects such traps by looking for price structure sweeps, order‑flow mismatches and dominance reversals. It uses a scoring system to differentiate risk from confirmed traps. 6.2 Inputs • trap_lookback_len: Window length used to rank extremes and detect sweeps. • trap_wick_threshold: Minimum proportion of a bar’s range that must be wick (upper for bull traps, lower for bear traps) to qualify as a sweep. • trap_score_risk: Minimum aggregated score required to flag a trap risk. (The code defines a trap_score_confirm input, but confirmation is actually based on price reversal rather than a separate score threshold.) • trap_confirm_bars: Maximum number of bars allowed for price to reverse and confirm the trap. If price does not reverse in this window, the risk label will expire or remain unconfirmed. • Label settings: ATR length and multiplier for offsetting, size, colours for risk and confirmed labels, and connector style and width. Separate settings exist for bull and bear traps. • Toggle inputs: show_trap_module and show_trap_labels enable the module and control whether labels are drawn on the chart. 6.3 Scoring logic The module assigns points to several conditions and sums them to determine whether a trap risk is present. For bull traps, the score is built from the following (bear traps mirror the logic with highs and lows swapped): 1. Sweep (2 points): Price trades above the high pivot (HH1) but fails to close above it and leaves a long upper wick at least trap_wick_threshold × range. For bear traps, price dips below the low pivot (LL1), fails to close below and leaves a long lower wick. 2. Close break (1 point): Price closes beyond HH1 or LL1 without leaving a long wick. 3. Candle/delta mismatch (2 points): The candle closes bullish yet the order flow delta is negative or the seller ratio exceeds 50%, indicating hidden supply. Conversely, a bearish close with positive delta or buyer dominance suggests hidden demand. 4. Dominance inversion (2 points): The current bar’s buyer volume has the highest rank in the lookback window while cumulative sums favor sellers, or vice versa. 5. Low‑volume break (1 point): Price crosses the pivot but total volume is below its moving average. The total score for each side is compared to trap_score_risk. If the score is high enough, a “Bull Trap Risk” or “Bear Trap Risk” label is drawn, offset from the candle by half of an ATR‑scaled distance using a dashed outline. If, within trap_confirm_bars, price reverses beyond the opposite level—drops back below the high pivot for bull traps or rises above the low pivot for bear traps—the label is upgraded to a solid “Bull Trap” or “Bear Trap” . In this version of the code, there is no separate score threshold for confirmation: the variable trap_score_confirm is unused; confirmation depends solely on a successful price reversal within the specified number of bars. Figure caption, In this example the trap module has flagged a Bear Trap Risk. Price initially breaks below the most recent low pivot (LL1), but the bar closes back above that level and leaves a long lower wick, suggesting a failed push lower. Combined with a mismatch between the candle direction and the order flow (buyers regain control) and a reversal in volume dominance, the aggregate score exceeds the risk threshold, so a dashed “Bear Trap Risk” label prints beneath the bar. The green and red trend lines mark the current low and high pivot trajectories, while the horizontal dashed lines show the highest and lowest values in the lookback window. If, within the next few bars, price closes decisively above the support, the risk label would upgrade to a solid “Bear Trap” label. Figure caption, In this example the trap module has identified both ends of a price range. Near the highs, price briefly pushes above the descending red trendline and the recent pivot high, but fails to close there and leaves a noticeable upper wick. That combination of a sweep above resistance and order‑flow mismatch generates a Bull Trap Risk label with a dashed outline, warning that the upside break may not hold. At the opposite extreme, price later dips below the green trendline and the labelled low pivot, then quickly snaps back and closes higher. The long lower wick and subsequent price reversal upgrade the previous bear‑trap risk into a confirmed Bear Trap (solid label), indicating that sellers were caught on a false breakdown. Horizontal dashed lines mark the highest high and lowest low of the lookback window, while the red and green diagonals connect the earliest and latest pivot highs and lows to visualize the range. 7. Sharp Move Module 7.1 Concept Markets sometimes display absorption or climax behavior—periods when one side steadily gains the upper hand before price breaks out with a sharp move. This module evaluates several order‑flow and volume conditions to anticipate such moves. Users can choose how many conditions must be met to flag a risk and how many (plus a price break) are required for confirmation. 7.2 Inputs • sharp Lookback: Number of bars in the window used to compute moving averages, sums, percentile ranks and reference levels. • sharpPercentile: Minimum percentile rank for the current side’s volume; the current buy (or sell) volume must be greater than or equal to this percentile of historical volumes over the lookback window. • sharpVolMult: Multiplier used in the volume climax check. The current side’s volume must exceed this multiple of its average to count as a climax. • sharpRatioThr: Minimum dominance ratio (current side’s volume relative to the opposite side) used in both the instant and cumulative dominance checks. • sharpChurnThr: Maximum ratio of a bar’s range to its ATR for absorption/churn detection; lower values indicate more absorption (large volume in a small range). • sharpScoreRisk: Minimum number of conditions that must be true to print a risk label. • sharpScoreConfirm: Minimum number of conditions plus a price break required for confirmation. • sharpCvdThr: Threshold for cumulative delta divergence versus price change (positive for bullish accumulation, negative for bearish distribution). • Label settings: ATR length (sharpATRlen) and multiplier (sharpLabelMult) for positioning labels, label size, colors and connector styles for bullish and bearish sharp moves. • Toggles: enableSharp activates the module; show_sharp_labels controls whether labels are drawn. 7.3 Conditions (six per side) For each side, the indicator computes six boolean conditions and sums them to form a score: 1. Dominance (instant and cumulative): – Instant dominance: current buy volume ≥ sharpRatioThr × current sell volume. – Cumulative dominance: sum of buy volumes over the window ≥ sharpRatioThr × sum of sell volumes (and vice versa for bearish checks). 2. Accumulation/Distribution divergence: Over the lookback window, cumulative delta rises by at least sharpCvdThr while price fails to rise (bullish), or cumulative delta falls by at least sharpCvdThr while price fails to fall (bearish). 3. Volume climax: The current side’s volume is ≥ sharpVolMult × its average and the product of volume and bar range is the highest in the lookback window. 4. Absorption/Churn: The current side’s volume divided by the bar’s range equals the highest value in the window and the bar’s range divided by ATR ≤ sharpChurnThr (indicating large volume within a small range). 5. Percentile rank: The current side’s volume percentile rank is ≥ sharp Percentile. 6. Mirror logic for sellers: The above checks are repeated with buyer and seller roles swapped and the price break levels reversed. Each condition that passes contributes one point to the corresponding side’s score (0 or 1). Risk and confirmation thresholds are then applied to these scores. 7.4 Scoring and labels • Risk: If scoreBull ≥ sharpScoreRisk, a “Sharp ↑ Risk” label is drawn above the bar. If scoreBear ≥ sharpScoreRisk, a “Sharp ↓ Risk” label is drawn below the bar. • Confirmation: A risk label is upgraded to “Sharp ↑” when scoreBull ≥ sharpScoreConfirm and the bar closes above the highest recent pivot (HH1); for bearish cases, confirmation requires scoreBear ≥ sharpScoreConfirm and a close below the lowest pivot (LL1). • Label positioning: Labels are offset from the candle by ATR × sharpLabelMult (full ATR times multiplier), not half, and may include a dashed or dotted connector line if enabled. Figure caption, In this chart both bullish and bearish sharp‑move setups have been flagged. Earlier in the range, a “Sharp ↓ Risk” label appears beneath a candle: the sell‑side score met the risk threshold, signaling that the combination of strong sell volume, dominance and absorption within a narrow range suggested a potential sharp decline. The price did not close below the lower pivot, so this label remains a “risk” and no confirmation occurred. Later, as the market recovered and volume shifted back to the buy side, a “Sharp ↑ Risk” label prints above a candle near the top of the channel. Here, buy‑side dominance, cumulative delta divergence and a volume climax aligned, but price has not yet closed above the upper pivot (HH1), so the alert is still a risk rather than a confirmed sharp‑up move. Figure caption, In this chart a Sharp ↑ label is displayed above a candle, indicating that the sharp move module has confirmed a bullish breakout. Prior bars satisfied the risk threshold — showing buy‑side dominance, positive cumulative delta divergence, a volume climax and strong absorption in a narrow range — and this candle closes above the highest recent pivot, upgrading the earlier “Sharp ↑ Risk” alert to a full Sharp ↑ signal. The green label is offset from the candle with a dashed connector, while the red and green trend lines trace the high and low pivot trajectories and the dashed horizontals mark the highest and lowest values of the lookback window. 8. Market‑Maker / Spread‑Capture Module 8.1 Concept Liquidity providers often “capture the spread” by buying and selling in almost equal amounts within a very narrow price range. These bars can signal temporary congestion before a move or reflect algorithmic activity. This module flags bars where both buyer and seller volumes are high, the price range is only a few ticks and the buy/sell split remains close to 50%. It helps traders spot potential liquidity pockets. 8.2 Inputs • scalpLookback: Window length used to compute volume averages. • scalpVolMult: Multiplier applied to each side’s average volume; both buy and sell volumes must exceed this multiple. • scalpTickCount: Maximum allowed number of ticks in a bar’s range (calculated as (high − low) / minTick). A value of 1 or 2 captures ultra‑small bars; increasing it relaxes the range requirement. • scalpDeltaRatio: Maximum deviation from a perfect 50/50 split. For example, 0.05 means the buyer share must be between 45% and 55%. • Label settings: ATR length, multiplier, size, colors, connector style and width. • Toggles : show_scalp_module and show_scalp_labels to enable the module and its labels. 8.3 Signal When, on the current bar, both TF_buy_breakout and TF_sell_breakout exceed scalpVolMult times their respective averages and (high − low)/minTick ≤ scalpTickCount and the buyer share is within scalpDeltaRatio of 50%, the module prints a “Spread ↔” label above the bar. The label uses the same ATR offset logic as other modules and draws a connector if enabled. Figure caption, In this chart the spread‑capture module has identified a potential liquidity pocket. Buyer and seller volumes both spiked above their recent averages, yet the candle’s range measured only a couple of ticks and the buy/sell split stayed close to 50 %. This combination met the module’s criteria, so it printed a grey “Spread ↔” label above the bar. The red and green trend lines link the earliest and latest high and low pivots, and the dashed horizontals mark the highest high and lowest low within the current lookback window. 9. Money Flow Module 9.1 Concept To translate volume into a monetary measure, this module multiplies each side’s volume by the closing price. It tracks buying and selling system money default currency on a per-bar basis and sums them over a chosen period. The difference between buy and sell currencies (Δ$) shows net inflow or outflow. 9.2 Inputs • mf_period_len_mf: Number of bars used for summing buy and sell dollars. • Label appearance settings: ATR length, multiplier, size, colors for up/down labels, and connector style and width. • Toggles: Use enableMoneyFlowLabel_mf and showMFLabels to control whether the module and its labels are displayed. 9.3 Calculations • Per-bar money: Buy $ = TF_buy_breakout × close; Sell $ = TF_sell_breakout × close. Their difference is Δ$ = Buy $ − Sell $. • Summations: Over mf_period_len_mf bars, compute Σ Buy $, Σ Sell $ and ΣΔ$ using math.sum(). • Info table entries: Rows 9–13 display these values as texts like “↑ USD 1234 (1M)” or “ΣΔ USD −5678 (14)”, with colors reflecting whether buyers or sellers dominate. • Money flow status: If Δ$ is positive the bar is marked “Money flow in” ; if negative, “Money flow out” ; if zero, “Neutral”. The cumulative status is similarly derived from ΣΔ.Labels print at the bar that changes the sign of ΣΔ, offset using ATR × label multiplier and styled per user preferences. Figure caption, The chart illustrates a steady rise toward the highest recent pivot (HH1) with price riding between a rising green trend‑line and a red trend‑line drawn through earlier pivot highs. A green Money flow in label appears above the bar near the top of the channel, signaling that net dollar flow turned positive on this bar: buy‑side dollar volume exceeded sell‑side dollar volume, pushing the cumulative sum ΣΔ$ above zero. In the info table, the “Money flow (bar)” and “Money flow Σ” rows both read In, confirming that the indicator’s money‑flow module has detected an inflow at both bar and aggregate levels, while other modules (pivots, trend lines and support/resistance) remain active to provide structural context. In this example the Money Flow module signals a net outflow. Price has been trending downward: successive high pivots form a falling red trend‑line and the low pivots form a descending green support line. When the latest bar broke below the previous low pivot (LL1), both the bar‑level and cumulative net dollar flow turned negative—selling volume at the close exceeded buying volume and pushed the cumulative Δ$ below zero. The module reacts by printing a red “Money flow out” label beneath the candle; the info table confirms that the “Money flow (bar)” and “Money flow Σ” rows both show Out, indicating sustained dominance of sellers in this period. 10. Info Table 10.1 Purpose When enabled, the Info Table appears in the lower right of your chart. It summarises key values computed by the indicator—such as buy and sell volume, delta, total volume, breakout status, market phase, and money flow—so you can see at a glance which side is dominant and which signals are active. 10.2 Symbols • ↑ / ↓ — Up (↑) denotes buy volume or money; down (↓) denotes sell volume or money. • MA — Moving average. In the table it shows the average value of a series over the lookback period. • Σ (Sigma) — Cumulative sum over the chosen lookback period. • Δ (Delta) — Difference between buy and sell values. • B / S — Buyer and seller share of total volume, expressed as percentages. • Ref. Price — Reference price for breakout calculations, based on the latest pivot. • Status — Indicates whether a breakout condition is currently active (True) or has failed. 10.3 Row definitions 1. Up volume / MA up volume – Displays current buy volume on the lower timeframe and its moving average over the lookback period. 2. Down volume / MA down volume – Shows current sell volume and its moving average; sell values are formatted in red for clarity. 3. Δ / ΣΔ – Lists the difference between buy and sell volume for the current bar and the cumulative delta volume over the lookback period. 4. Σ / MA Σ (Vol/MA) – Total volume (buy + sell) for the bar, with the ratio of this volume to its moving average; the right cell shows the average total volume. 5. B/S ratio – Buy and sell share of the total volume: current bar percentages and the average percentages across the lookback period. 6. Buyer Rank / Seller Rank – Ranks the bar’s buy and sell volumes among the last (n) bars; lower rank numbers indicate higher relative volume. 7. Σ Buy / Σ Sell – Sum of buy and sell volumes over the lookback window, indicating which side has traded more. 8. Breakout UP / DOWN – Shows the breakout thresholds (Ref. Price) and whether the breakout condition is active (True) or has failed. 9. Market Phase (Vol) – Reports the current volume‑only phase: Accumulation, Distribution or Neutral. 10. Money Flow – The final rows display dollar amounts and status: – ↑ USD / Σ↑ USD – Buy dollars for the current bar and the cumulative sum over the money‑flow period. – ↓ USD / Σ↓ USD – Sell dollars and their cumulative sum. – Δ USD / ΣΔ USD – Net dollar difference (buy minus sell) for the bar and cumulatively. – Money flow (bar) – Indicates whether the bar’s net dollar flow is positive (In), negative (Out) or neutral. – Money flow Σ – Shows whether the cumulative net dollar flow across the chosen period is positive, negative or neutral. The chart above shows a sequence of different signals from the indicator. A Bull Trap Risk appears after price briefly pushes above resistance but fails to hold, then a green Accum label identifies an accumulation phase. An upward breakout follows, confirmed by a Money flow in print. Later, a Sharp ↓ Risk warns of a possible sharp downturn; after price dips below support but quickly recovers, a Bear Trap label marks a false breakdown. The highlighted info table in the center summarizes key metrics at that moment, including current and average buy/sell volumes, net delta, total volume versus its moving average, breakout status (up and down), market phase (volume), and bar‑level and cumulative money flow (In/Out). 11. Conclusion & Final Remarks This indicator was developed as a holistic study of market structure and order flow. It brings together several well‑known concepts from technical analysis—breakouts, accumulation and distribution phases, overbought and oversold extremes, bull and bear traps, sharp directional moves, market‑maker spread bars and money flow—into a single Pine Script tool. Each module is based on widely recognized trading ideas and was implemented after consulting reference materials and example strategies, so you can see in real time how these concepts interact on your chart. A distinctive feature of this indicator is its reliance on per‑side volume: instead of tallying only total volume, it separately measures buy and sell transactions on a lower time frame. This approach gives a clearer view of who is in control—buyers or sellers—and helps filter breakouts, detect phases of accumulation or distribution, recognize potential traps, anticipate sharp moves and gauge whether liquidity providers are active. The money‑flow module extends this analysis by converting volume into currency values and tracking net inflow or outflow across a chosen window. Although comprehensive, this indicator is intended solely as a guide. It highlights conditions and statistics that many traders find useful, but it does not generate trading signals or guarantee results. Ultimately, you remain responsible for your positions. Use the information presented here to inform your analysis, combine it with other tools and risk‑management techniques, and always make your own decisions when trading.
Pine Script® indicator
by ata_sabanci
16
MERV: Market Entropy & Rhythm Visualizer [BullByte]The MERV (Market Entropy & Rhythm Visualizer) indicator analyzes market conditions by measuring entropy (randomness vs. trend), tradeability (volatility/momentum), and cyclical rhythm. It provides traders with an easy-to-read dashboard and oscillator to understand when markets are structured or choppy, and when trading conditions are optimal. Purpose of the Indicator MERV’s goal is to help traders identify different market regimes. It quantifies how structured or random recent price action is (entropy), how strong and volatile the movement is (tradeability), and whether a repeating cycle exists. By visualizing these together, MERV highlights trending vs. choppy environments and flags when conditions are favorable for entering trades. For example, a low entropy value means prices are following a clear trend line, whereas high entropy indicates a lot of noise or sideways action. The indicator’s combination of measures is original: it fuses statistical trend-fit (entropy), volatility trends (ATR and slope), and cycle analysis to give a comprehensive view of market behavior. Why a Trader Should Use It Traders often need to know when a market trend is reliable vs. when it is just noise. MERV helps in several ways: it shows when the market has a strong direction (low entropy, high tradeability) and when it’s ranging (high entropy). This can prevent entering trend-following strategies during choppy periods, or help catch breakouts early. The “Optimal Regime” marker (a star) highlights moments when entropy is very low and tradeability is very high, typically the best conditions for trend trades. By using MERV, a trader gains an empirical “go/no-go” signal based on price history, rather than guessing from price alone. It’s also adaptable: you can apply it to stocks, forex, crypto, etc., on any timeframe. For example, during a bullish phase of a stock, MERV will turn green (Trending Mode) and often show a star, signaling good follow-through. If the market later grinds sideways, MERV will shift to magenta (Choppy Mode), warning you that trend-following is now risky. Why These Components Were Chosen Market Entropy (via R²) : This measures how well recent prices fit a straight line. We compute a linear regression on the last len_entropy bars and calculate R². Entropy = 1 - R², so entropy is low when prices follow a trend (R² near 1) and high when price action is erratic (R² near 0). This single number captures trend strength vs noise. Tradeability (ATR + Slope) : We combine two familiar measures: the Average True Range (ATR) (normalized by price) and the absolute slope of the regression line (scaled by ATR). Together they reflect how active and directional the market is. A high ATR or strong slope means big moves, making a trend more “tradeable.” We take a simple average of the normalized ATR and slope to get tradeability_raw. Then we convert it to a percentile rank over the lookback window so it’s stable between 0 and 1. Percentile Ranks : To make entropy and tradeability values easy to interpret, we convert each to a 0–100 rank based on the past len_entropy periods. This turns raw metrics into a consistent scale. (For example, an entropy rank of 90 means current entropy is higher than 90% of recent values.) We then divide by 100 to plot them on a 0–1 scale. Market Mode (Regime) : Based on those ranks, MERV classifies the market: Trending (Green) : Low entropy rank (<40%) and high tradeability rank (>60%). This means the market is structurally trending with high activity. Choppy (Magenta) : High entropy rank (>60%) and low tradeability rank (<40%). This is a mostly random, low-momentum market. Neutral (Cyan) : All other cases. This covers mixed regimes not strongly trending or choppy. The mode is shown as a colored bar at the bottom: green for trending, magenta for choppy, cyan for neutral. Optimal Regime Signal : Separately, we mark an “optimal” condition when entropy_norm < 0.3 and tradeability > 0.7 (both normalized 0–1). When this is true, a ★ star appears on the bottom line. This star is colored white when truly optimal, gold when only tradeability is high (but entropy not quite low enough), and black when neither condition holds. This gives a quick visual cue for very favorable conditions. What Makes MERV Stand Out Holistic View : Unlike a single-oscillator, MERV combines trend, volatility, and cycle analysis in one tool. This multi-faceted approach is unique. Visual Dashboard : The fixed on-chart dashboard (shown at your chosen corner) summarizes all metrics in bar/gauge form. Even a non-technical user can glance at it: more “█” blocks = a higher value, colors match the plots. This is more intuitive than raw numbers. Adaptive Thresholds : Using percentile ranks means MERV auto-adjusts to each market’s character, rather than requiring fixed thresholds. Cycle Insight : The rhythm plot adds information rarely found in indicators – it shows if there’s a repeating cycle (and its period in bars) and how strong it is. This can hint at natural bounce or reversal intervals. Modern Look : The neon color scheme and glow effects make the lines easy to distinguish (blue/pink for entropy, green/orange for tradeability, etc.) and the filled area between them highlights when one dominates the other. Recommended Timeframes MERV can be applied to any timeframe, but it will be more reliable on higher timeframes. The default len_entropy = 50 and len_rhythm = 30 mean we use 30–50 bars of history, so on a daily chart that’s ~2–3 months of data; on a 1-hour chart it’s about 2–3 days. In practice: Swing/Position traders might prefer Daily or 4H charts, where the calculations smooth out small noise. Entropy and cycles are more meaningful on longer trends. Day trader s could use 15m or 1H charts if they adjust the inputs (e.g. shorter windows). This provides more sensitivity to intraday cycles. Scalpers might find MERV too “slow” unless input lengths are set very low. In summary, the indicator works anywhere, but the defaults are tuned for capturing medium-term trends. Users can adjust len_entropy and len_rhythm to match their chart’s volatility. The dashboard position can also be moved (top-left, bottom-right, etc.) so it doesn’t cover important chart areas. How the Scoring/Logic Works (Step-by-Step) Compute Entropy : A linear regression line is fit to the last len_entropy closes. We compute R² (goodness of fit). Entropy = 1 – R². So a strong straight-line trend gives low entropy; a flat/noisy set of points gives high entropy. Compute Tradeability : We get ATR over len_entropy bars, normalize it by price (so it’s a fraction of price). We also calculate the regression slope (difference between the predicted close and last close). We scale |slope| by ATR to get a dimensionless measure. We average these (ATR% and slope%) to get tradeability_raw. This represents how big and directional price moves are. Convert to Percentiles : Each new entropy and tradeability value is inserted into a rolling array of the last 50 values. We then compute the percentile rank of the current value in that array (0–100%) using a simple loop. This tells us where the current bar stands relative to history. We then divide by 100 to plot on . Determine Modes and Signal : Based on these normalized metrics: if entropy < 0.4 and tradeability > 0.6 (40% and 60% thresholds), we set mode = Trending (1). If entropy > 0.6 and tradeability < 0.4, mode = Choppy (-1). Otherwise mode = Neutral (0). Separately, if entropy_norm < 0.3 and tradeability > 0.7, we set an optimal flag. These conditions trigger the colored mode bars and the star line. Rhythm Detection : Every bar, if we have enough data, we take the last len_rhythm closes and compute the mean and standard deviation. Then for lags from 5 up to len_rhythm, we calculate a normalized autocorrelation coefficient. We track the lag that gives the maximum correlation (best match). This “best lag” divided by len_rhythm is plotted (a value between 0 and 1). Its color changes with the correlation strength. We also smooth the best correlation value over 5 bars to plot as “Cycle Strength” (also 0 to 1). This shows if there is a consistent cycle length in recent price action. Heatmap (Optional) : The background color behind the oscillator panel can change with entropy. If “Neon Rainbow” style is on, low entropy is blue and high entropy is pink (via a custom color function), otherwise a classic green-to-red gradient can be used. This visually reinforces the entropy value. Volume Regime (Dashboard Only) : We compute vol_norm = volume / sma(volume, len_entropy). If this is above 1.5, it’s considered high volume (neon orange); below 0.7 is low (blue); otherwise normal (green). The dashboard shows this as a bar gauge and percentage. This is for context only. Oscillator Plot – How to Read It The main panel (oscillator) has multiple colored lines on a 0–1 vertical scale, with horizontal markers at 0.2 (Low), 0.5 (Mid), and 0.8 (High). Here’s each element: Entropy Line (Blue→Pink) : This line (and its glow) shows normalized entropy (0 = very low, 1 = very high). It is blue/green when entropy is low (strong trend) and pink/purple when entropy is high (choppy). A value near 0.0 (below 0.2 line) indicates a very well-defined trend. A value near 1.0 (above 0.8 line) means the market is very random. Watch for it dipping near 0: that suggests a strong trend has formed. Tradeability Line (Green→Yellow) : This represents normalized tradeability. It is colored bright green when tradeability is low, transitioning to yellow as tradeability increases. Higher values (approaching 1) mean big moves and strong slopes. Typically in a market rally or crash, this line will rise. A crossing above ~0.7 often coincides with good trend strength. Filled Area (Orange Shade) : The orange-ish fill between the entropy and tradeability lines highlights when one dominates the other. If the area is large, the two metrics diverge; if small, they are similar. This is mostly aesthetic but can catch the eye when the lines cross over or remain close. Rhythm (Cycle) Line : This is plotted as (best_lag / len_rhythm). It indicates the relative period of the strongest cycle. For example, a value of 0.5 means the strongest cycle was about half the window length. The line’s color (green, orange, or pink) reflects how strong that cycle is (green = strong). If no clear cycle is found, this line may be flat or near zero. Cycle Strength Line : Plotted on the same scale, this shows the autocorrelation strength (0–1). A high value (e.g. above 0.7, shown in green) means the cycle is very pronounced. Low values (pink) mean any cycle is weak and unreliable. Mode Bars (Bottom) : Below the main oscillator, thick colored bars appear: a green bar means Trending Mode, magenta means Choppy Mode, and cyan means Neutral. These bars all have a fixed height (–0.1) and make it very easy to see the current regime. Optimal Regime Line (Bottom) : Just below the mode bars is a thick horizontal line at –0.18. Its color indicates regime quality: White (★) means “Optimal Regime” (very low entropy and high tradeability). Gold (★) means not quite optimal (high tradeability but entropy not low enough). Black means neither condition. This star line quickly tells you when conditions are ideal (white star) or simply good (gold star). Horizontal Guides : The dotted lines at 0.2 (Low), 0.5 (Mid), and 0.8 (High) serve as reference lines. For example, an entropy or tradeability reading above 0.8 is “High,” and below 0.2 is “Low,” as labeled on the chart. These help you gauge values at a glance. Dashboard (Fixed Corner Panel) MERV also includes a compact table (dashboard) that can be positioned in any corner. It summarizes key values each bar. Here is how to read its rows: Entropy : Shows a bar of blocks (█ and ░). More █ blocks = higher entropy. It also gives a percentage (rounded). A full bar (10 blocks) with a high % means very chaotic market. The text is colored similarly (blue-green for low, pink for high). Rhythm : Shows the best cycle period in bars (e.g. “15 bars”). If no calculation yet, it shows “n/a.” The text color matches the rhythm line. Cycle Strength : Gives the cycle correlation as a percentage (smoothed, as shown on chart). Higher % (green) means a strong cycle. Tradeability : Displays a 10-block gauge for tradeability. More blocks = more tradeable market. It also shows “gauge” text colored green→yellow accordingly. Market Mode : Simply shows “Trending”, “Choppy”, or “Neutral” (cyan text) to match the mode bar color. Volume Regime : Similar to tradeability, shows blocks for current volume vs. average. Above-average volume gives orange blocks, below-average gives blue blocks. A % value indicates current volume relative to average. This row helps see if volume is abnormally high or low. Optimal Status (Large Row) : In bold, either “★ Optimal Regime” (white text) if the star condition is met, “★ High Tradeability” (gold text) if tradeability alone is high, or “— Not Optimal” (gray text) otherwise. This large row catches your eye when conditions are ripe. In short, the dashboard turns the numeric state into an easy read: filled bars, colors, and text let you see current conditions without reading the plot. For instance, five blue blocks under Entropy and “25%” tells you entropy is low (good), and a row showing “Trending” in green confirms a trend state. Real-Life Example Example : Consider a daily chart of a trending stock (e.g. “AAPL, 1D”). During a strong uptrend, recent prices fit a clear upward line, so Entropy would be low (blue line near bottom, perhaps below the 0.2 line). Volatility and slope are high, so Tradeability is high (green-yellow line near top). In the dashboard, Entropy might show only 1–2 blocks (e.g. 10%) and Tradeability nearly full (e.g. 90%). The Market Mode bar turns green (Trending), and you might see a white ★ on the optimal line if conditions are very good. The Volume row might light orange if volume is above average during the rally. In contrast, imagine the same stock later in a tight range: Entropy will rise (pink line up, more blocks in dashboard), Tradeability falls (fewer blocks), and the Mode bar turns magenta (Choppy). No star appears in that case. Consolidated Use Case : Suppose on XYZ stock the dashboard reads “Entropy: █░░░░░░░░ 20%”, “Tradeability: ██████████ 80%”, Mode = Trending (green), and “★ Optimal Regime.” This tells the trader that the market is in a strong, low-noise trend, and it might be a good time to follow the trend (with appropriate risk controls). If instead it reads “Entropy: ████████░░ 80%”, “Tradeability: ███▒▒▒▒▒▒ 30%”, Mode = Choppy (magenta), the trader knows the market is random and low-momentum—likely best to sit out until conditions improve. Example: How It Looks in Action Screenshot 1: Trending Market with High Tradeability (SOLUSD, 30m) What it means: The market is in a clear, strong trend with excellent conditions for trading. Both trend-following and active strategies are favored, supported by high tradeability and strong volume. Screenshot 2: Optimal Regime, Strong Trend (ETHUSD, 1h) What it means: This is an ideal environment for trend trading. The market is highly organized, tradeability is excellent, and volume supports the move. This is when the indicator signals the highest probability for success. Screenshot 3: Choppy Market with High Volume (BTC Perpetual, 5m) What it means: The market is highly random and choppy, despite a surge in volume. This is a high-risk, low-reward environment, avoid trend strategies, and be cautious even with mean-reversion or scalping. Settings and Inputs The script is fully open-source; here are key inputs the user can adjust: Entropy Window (len_entropy) : Number of bars used for entropy and tradeability (default 50). Larger = smoother, more lag; smaller = more sensitivity. Rhythm Window (len_rhythm ): Bars used for cycle detection (default 30). This limits the longest cycle we detect. Dashboard Position : Choose any corner (Top Right default) so it doesn’t cover chart action. Show Heatmap : Toggles the entropy background coloring on/off. Heatmap Style : “Neon Rainbow” (colorful) or “Classic” (green→red). Show Mode Bar : Turn the bottom mode bar on/off. Show Dashboard : Turn the fixed table panel on/off. Each setting has a tooltip explaining its effect. In the description we will mention typical settings (e.g. default window sizes) and that the user can move the dashboard corner as desired. Oscillator Interpretation (Recap) Lines : Blue/Pink = Entropy (low=trend, high=chop); Green/Yellow = Tradeability (low=quiet, high=volatile). Fill : Orange tinted area between them (for visual emphasis). Bars : Green=Trending, Magenta=Choppy, Cyan=Neutral (at bottom). Star Line : White star = ideal conditions, Gold = good but not ideal. Horizontal Guides : 0.2 and 0.8 lines mark low/high thresholds for each metric. Using the chart, a coder or trader can see exactly what each output represents and make decisions accordingly. Disclaimer This indicator is provided as-is for educational and analytical purposes only. It does not guarantee any particular trading outcome. Past market patterns may not repeat in the future. Users should apply their own judgment and risk management; do not rely solely on this tool for trading decisions. Remember, TradingView scripts are tools for market analysis, not personalized financial advice. We encourage users to test and combine MERV with other analysis and to trade responsibly. -BullByte
Pine Script® indicator
by BullByte
6
Market Zone Analyzer[BullByte]Understanding the Market Zone Analyzer --- 1. Purpose of the Indicator The Market Zone Analyzer is a Pine Script™ (version 6) indicator designed to streamline market analysis on TradingView. Rather than scanning multiple separate tools, it unifies four core dimensions—trend strength, momentum, price action, and market activity—into a single, consolidated view. By doing so, it helps traders: • Save time by avoiding manual cross-referencing of disparate signals. • Reduce decision-making errors that can arise from juggling multiple indicators. • Gain a clear, reliable read on whether the market is in a bullish, bearish, or sideways phase, so they can more confidently decide to enter, exit, or hold a position. --- 2. Why a Trader Should Use It • Unified View: Combines all essential market dimensions into one easy-to-read score and dashboard, eliminating the need to piece together signals manually. • Adaptability: Automatically adjusts its internal weighting for trend, momentum, and price action based on current volatility. Whether markets are choppy or calm, the indicator remains relevant. • Ease of Interpretation: Outputs a simple “BULLISH,” “BEARISH,” or “SIDEWAYS” label, supplemented by an intuitive on-chart dashboard and an oscillator plot that visually highlights market direction. • Reliability Features: Built-in smoothing of the net score and hysteresis logic (requiring consecutive confirmations before flips) minimize false signals during noisy or range-bound phases. --- 3. Why These Specific Indicators? This script relies on a curated set of well-established technical tools, each chosen for its particular strength in measuring one of the four core dimensions: 1. Trend Strength: • ADX/DMI (Average Directional Index / Directional Movement Index): Measures how strong a trend is, and whether the +DI line is above the –DI line (bullish) or vice versa (bearish). • Moving Average Slope (Fast MA vs. Slow MA): Compares a shorter-period SMA to a longer-period SMA; if the fast MA sits above the slow MA, it confirms an uptrend, and vice versa for a downtrend. • Ichimoku Cloud Differential (Senkou A vs. Senkou B): Provides a forward-looking view of trend direction; Senkou A above Senkou B signals bullishness, and the opposite signals bearishness. 2. Momentum: • Relative Strength Index (RSI): Identifies overbought (above its dynamically calculated upper bound) or oversold (below its lower bound) conditions; changes in RSI often precede price reversals. • Stochastic %K: Highlights shifts in short-term momentum by comparing closing price to the recent high/low range; values above its upper band signal bullish momentum, below its lower band signal bearish momentum. • MACD Histogram: Measures the difference between the MACD line and its signal line; a positive histogram indicates upward momentum, a negative histogram indicates downward momentum. 3. Price Action: • Highest High / Lowest Low (HH/LL) Range: Over a defined lookback period, this captures breakout or breakdown levels. A closing price near the recent highs (with a positive MA slope) yields a bullish score, and near the lows (with a negative MA slope) yields a bearish score. • Heikin-Ashi Doji Detection: Uses Heikin-Ashi candles to identify indecision or continuation patterns. A small Heikin-Ashi body (doji) relative to recent volatility is scored as neutral; a larger body in the direction of the MA slope is scored bullish or bearish. • Candle Range Measurement: Compares each candle’s high-low range against its own dynamic band (average range ± standard deviation). Large candles aligning with the prevailing trend score bullish or bearish accordingly; unusually small candles can indicate exhaustion or consolidation. 4. Market Activity: • Bollinger Bands Width (BBW): Measures the distance between BB upper and lower bands; wide bands indicate high volatility, narrow bands indicate low volatility. • Average True Range (ATR): Quantifies average price movement (volatility). A sudden spike in ATR suggests a volatile environment, while a contraction suggests calm. • Keltner Channels Width (KCW): Similar to BBW but uses ATR around an EMA. Provides a second layer of volatility context, confirming or contrasting BBW readings. • Volume (with Moving Average): Compares current volume to its moving average ± standard deviation. High volume validates strong moves; low volume signals potential lack of conviction. By combining these tools, the indicator captures trend direction, momentum strength, price-action nuances, and overall market energy, yielding a more balanced and comprehensive assessment than any single tool alone. --- 4. What Makes This Indicator Stand Out • Multi-Dimensional Analysis: Rather than relying on a lone oscillator or moving average crossover, it simultaneously evaluates trend, momentum, price action, and activity. • Dynamic Weighting: The relative importance of trend, momentum, and price action adjusts automatically based on real-time volatility (Market Activity State). For example, in highly volatile conditions, trend and momentum signals carry more weight; in calm markets, price action signals are prioritized. • Stability Mechanisms: • Smoothing: The net score is passed through a short moving average, filtering out noise, especially on lower timeframes. • Hysteresis: Both Market Activity State and the final bullish/bearish/sideways zone require two consecutive confirmations before flipping, reducing whipsaw. • Visual Interpretation: A fully customizable on-chart dashboard displays each sub-indicator’s value, regime, score, and comment, all color-coded. The oscillator plot changes color to reflect the current market zone (green for bullish, red for bearish, gray for sideways) and shows horizontal threshold lines at +2, 0, and –2. --- 5. Recommended Timeframes • Short-Term (5 min, 15 min): Day traders and scalpers can benefit from rapid signals, but should enable smoothing (and possibly disable hysteresis) to reduce false whipsaws. • Medium-Term (1 h, 4 h): Swing traders find a balance between responsiveness and reliability. Less smoothing is required here, and the default parameters (e.g., ADX length = 14, RSI length = 14) perform well. • Long-Term (Daily, Weekly): Position traders tracking major trends can disable smoothing for immediate raw readings, since higher-timeframe noise is minimal. Adjust lookback lengths (e.g., increase adxLength, rsiLength) if desired for slower signals. Tip: If you keep smoothing off, stick to timeframes of 1 h or higher to avoid excessive signal “chatter.” --- 6. How Scoring Works A. Individual Indicator Scores Each sub-indicator is assigned one of three discrete scores: • +1 if it indicates a bullish condition (e.g., RSI above its dynamically calculated upper bound). • 0 if it is neutral (e.g., RSI between upper and lower bounds). • –1 if it indicates a bearish condition (e.g., RSI below its dynamically calculated lower bound). Examples of individual score assignments: • ADX/DMI: • +1 if ADX ≥ adxThreshold and +DI > –DI (strong bullish trend) • –1 if ADX ≥ adxThreshold and –DI > +DI (strong bearish trend) • 0 if ADX < adxThreshold (trend strength below threshold) • RSI: • +1 if RSI > RSI_upperBound • –1 if RSI < RSI_lowerBound • 0 otherwise • ATR (as part of Market Activity): • +1 if ATR > (ATR_MA + stdev(ATR)) • –1 if ATR < (ATR_MA – stdev(ATR)) • 0 otherwise Each of the four main categories shares this same +1/0/–1 logic across their sub-components. B. Category Scores Once each sub-indicator reports +1, 0, or –1, these are summed within their categories as follows: • Trend Score = (ADX score) + (MA slope score) + (Ichimoku differential score) • Momentum Score = (RSI score) + (Stochastic %K score) + (MACD histogram score) • Price Action Score = (Highest-High/Lowest-Low score) + (Heikin-Ashi doji score) + (Candle range score) • Market Activity Raw Score = (BBW score) + (ATR score) + (KC width score) + (Volume score) Each category’s summed value can range between –3 and +3 (for Trend, Momentum, and Price Action), and between –4 and +4 for Market Activity raw. C. Market Activity State and Dynamic Weight Adjustments Rather than contributing directly to the netScore like the other three categories, Market Activity determines how much weight to assign to Trend, Momentum, and Price Action: 1. Compute Market Activity Raw Score by summing BBW, ATR, KCW, and Volume individual scores (each +1/0/–1). 2. Bucket into High, Medium, or Low Activity: • High if raw Score ≥ 2 (volatile market). • Low if raw Score ≤ –2 (calm market). • Medium otherwise. 3. Apply Hysteresis (if enabled): The state only flips after two consecutive bars register the same high/low/medium label. 4. Set Category Weights: • High Activity: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Low Activity: Trend = 25 %, Momentum = 20 %, Price Action = 55 %. • Medium Activity: Use the trader’s base weight inputs (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 % by default). D. Calculating the Net Score 5. Normalize Base Weights (so that the sum of Trend + Momentum + Price Action always equals 100 %). 6. Determine Current Weights based on the Market Activity State (High/Medium/Low). 7. Compute Each Category’s Contribution: Multiply (categoryScore) × (currentWeight). 8. Sum Contributions to get the raw netScore (a floating-point value that can exceed ±3 when scores are strong). 9. Smooth the netScore over two bars (if smoothing is enabled) to reduce noise. 10. Apply Hysteresis to the Final Zone: • If the smoothed netScore ≥ +2, the bar is classified as “Bullish.” • If the smoothed netScore ≤ –2, the bar is classified as “Bearish.” • Otherwise, it is “Sideways.” • To prevent rapid flips, the script requires two consecutive bars in the new zone before officially changing the displayed zone (if hysteresis is on). E. Thresholds for Zone Classification • BULLISH: netScore ≥ +2 • BEARISH: netScore ≤ –2 • SIDEWAYS: –2 < netScore < +2 --- 7. Role of Volatility (Market Activity State) in Scoring Volatility acts as a dynamic switch that shifts which category carries the most influence: 1. High Activity (Volatile): • Detected when at least two sub-scores out of BBW, ATR, KCW, and Volume equal +1. • The script sets Trend weight = 50 % and Momentum weight = 35 %. Price Action weight is minimized at 15 %. • Rationale: In volatile markets, strong trending moves and momentum surges dominate, so those signals are more reliable than nuanced candle patterns. 2. Low Activity (Calm): • Detected when at least two sub-scores out of BBW, ATR, KCW, and Volume equal –1. • The script sets Price Action weight = 55 %, Trend = 25 %, and Momentum = 20 %. • Rationale: In quiet, sideways markets, subtle price-action signals (breakouts, doji patterns, small-range candles) are often the best early indicators of a new move. 3. Medium Activity (Balanced): • Raw Score between –1 and +1 from the four volatility metrics. • Uses whatever base weights the trader has specified (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 %). Because volatility can fluctuate rapidly, the script employs hysteresis on Market Activity State: a new High or Low state must occur on two consecutive bars before weights actually shift. This avoids constant back-and-forth weight changes and provides more stability. --- 8. Scoring Example (Hypothetical Scenario) • Symbol: Bitcoin on a 1-hour chart. • Market Activity: Raw volatility sub-scores show BBW (+1), ATR (+1), KCW (0), Volume (+1) → Total raw Score = +3 → High Activity. • Weights Selected: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Trend Signals: • ADX strong and +DI > –DI → +1 • Fast MA above Slow MA → +1 • Ichimoku Senkou A > Senkou B → +1 → Trend Score = +3 • Momentum Signals: • RSI above upper bound → +1 • MACD histogram positive → +1 • Stochastic %K within neutral zone → 0 → Momentum Score = +2 • Price Action Signals: • Highest High/Lowest Low check yields 0 (close not near extremes) • Heikin-Ashi doji reading is neutral → 0 • Candle range slightly above upper bound but trend is strong, so → +1 → Price Action Score = +1 • Compute Net Score (before smoothing): • Trend contribution = 3 × 0.50 = 1.50 • Momentum contribution = 2 × 0.35 = 0.70 • Price Action contribution = 1 × 0.15 = 0.15 • Raw netScore = 1.50 + 0.70 + 0.15 = 2.35 • Since 2.35 ≥ +2 and hysteresis is met, the final zone is “Bullish.” Although the netScore lands at 2.35 (Bullish), smoothing might bring it slightly below 2.00 on the first bar (e.g., 1.90), in which case the script would wait for a second consecutive reading above +2 before officially classifying the zone as Bullish (if hysteresis is enabled). --- 9. Correlation Between Categories The four categories—Trend Strength, Momentum, Price Action, and Market Activity—often reinforce or offset one another. The script takes advantage of these natural correlations: • Bullish Alignment: If ADX is strong and pointed upward, fast MA is above slow MA, and Ichimoku is positive, that usually coincides with RSI climbing above its upper bound and the MACD histogram turning positive. In such cases, both Trend and Momentum categories generate +1 or +2. Because the Market Activity State is likely High (given the accompanying volatility), Trend and Momentum weights are at their peak, so the netScore quickly crosses into Bullish territory. • Sideways/Consolidation: During a low-volatility, sideways phase, ADX may fall below its threshold, MAs may flatten, and RSI might hover in the neutral band. However, subtle price-action signals (like a small breakout candle or a Heikin-Ashi candle with a slight bias) can still produce a +1 in the Price Action category. If Market Activity is Low, Price Action’s weight (55 %) can carry enough influence—even if Trend and Momentum are neutral—to push the netScore out of “Sideways” into a mild bullish or bearish bias. • Opposing Signals: When Trend is bullish but Momentum turns negative (for example, price continues up but RSI rolls over), the two scores can partially cancel. Market Activity may remain Medium, in which case the netScore lingers near zero (Sideways). The trader can then wait for either a clearer momentum shift or a fresh price-action breakout before committing. By dynamically recognizing these correlations and adjusting weights, the indicator ensures that: • When Trend and Momentum align (and volatility supports it), the netScore leaps strongly into Bullish or Bearish. • When Trend is neutral but Price Action shows an early move in a low-volatility environment, Price Action’s extra weight in the Low Activity State can still produce actionable signals. --- 10. Market Activity State & Its Role (Detailed) The Market Activity State is not a direct category score—it is an overarching context setter for how heavily to trust Trend, Momentum, or Price Action. Here’s how it is derived and applied: 1. Calculate Four Volatility Sub-Scores: • BBW: Compare the current band width to its own moving average ± standard deviation. If BBW > (BBW_MA + stdev), assign +1 (high volatility); if BBW < (BBW_MA × 0.5), assign –1 (low volatility); else 0. • ATR: Compare ATR to its moving average ± standard deviation. A spike above the upper threshold is +1; a contraction below the lower threshold is –1; otherwise 0. • KCW: Same logic as ATR but around the KCW mean. • Volume: Compare current volume to its volume MA ± standard deviation. Above the upper threshold is +1; below the lower threshold is –1; else 0. 2. Sum Sub-Scores → Raw Market Activity Score: Range between –4 and +4. 3. Assign Market Activity State: • High Activity: Raw Score ≥ +2 (at least two volatility metrics are strongly spiking). • Low Activity: Raw Score ≤ –2 (at least two metrics signal unusually low volatility or thin volume). • Medium Activity: Raw Score is between –1 and +1 inclusive. 4. Hysteresis for Stability: • If hysteresis is enabled, a new state only takes hold after two consecutive bars confirm the same High, Medium, or Low label. • This prevents the Market Activity State from bouncing around when volatility is on the fence. 5. Set Category Weights Based on Activity State: • High Activity: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Low Activity: Trend = 25 %, Momentum = 20 %, Price Action = 55 %. • Medium Activity: Use trader’s base weights (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 %). 6. Impact on netScore: Because category scores (–3 to +3) multiply by these weights, High Activity amplifies the effect of strong Trend and Momentum scores; Low Activity amplifies the effect of Price Action. 7. Market Context Tooltip: The dashboard includes a tooltip summarizing the current state—e.g., “High activity, trend and momentum prioritized,” “Low activity, price action prioritized,” or “Balanced market, all categories considered.” --- 11. Category Weights: Base vs. Dynamic Traders begin by specifying base weights for Trend Strength, Momentum, and Price Action that sum to 100 %. These apply only when volatility is in the Medium band. Once volatility shifts: • High Volatility Overrides: • Trend jumps from its base (e.g., 40 %) to 50 %. • Momentum jumps from its base (e.g., 30 %) to 35 %. • Price Action is reduced to 15 %. Example: If base weights were Trend = 40 %, Momentum = 30 %, Price Action = 30 %, then in High Activity they become 50/35/15. A Trend score of +3 now contributes 3 × 0.50 = +1.50 to netScore; a Momentum +2 contributes 2 × 0.35 = +0.70. In total, Trend + Momentum can easily push netScore above the +2 threshold on its own. • Low Volatility Overrides: • Price Action leaps from its base (30 %) to 55 %. • Trend falls to 25 %, Momentum falls to 20 %. Why? When markets are quiet, subtle candle breakouts, doji patterns, and small-range expansions tend to foreshadow the next swing more effectively than raw trend readings. A Price Action score of +3 in this state contributes 3 × 0.55 = +1.65, which can carry the netScore toward +2—even if Trend and Momentum are neutral or only mildly positive. Because these weight shifts happen only after two consecutive bars confirm a High or Low state (if hysteresis is on), the indicator avoids constantly flipping its emphasis during borderline volatility phases. --- 12. Dominant Category Explained Within the dashboard, a label such as “Trend Dominant,” “Momentum Dominant,” or “Price Action Dominant” appears when one category’s absolute weighted contribution to netScore is the largest. Concretely: • Compute each category’s weighted contribution = (raw category score) × (current weight). • Compare the absolute values of those three contributions. • The category with the highest absolute value is flagged as Dominant for that bar. Why It Matters: • Momentum Dominant: Indicates that the combined force of RSI, Stochastic, and MACD (after weighting) is pushing netScore farther than either Trend or Price Action. In practice, it means that short-term sentiment and speed of change are the primary drivers right now, so traders should watch for continued momentum signals before committing to a trade. • Trend Dominant: Means ADX, MA slope, and Ichimoku (once weighted) outweigh the other categories. This suggests a strong directional move is in place; trend-following entries or confirming pullbacks are likely to succeed. • Price Action Dominant: Occurs when breakout/breakdown patterns, Heikin-Ashi candle readings, and range expansions (after weighting) are the most influential. This often happens in calmer markets, where subtle shifts in candle structure can foreshadow bigger moves. By explicitly calling out which category is carrying the most weight at any moment, the dashboard gives traders immediate insight into why the netScore is tilting toward bullish, bearish, or sideways. --- 13. Oscillator Plot: How to Read It The “Net Score” oscillator sits below the dashboard and visually displays the smoothed netScore as a line graph. Key features: 1. Value Range: In normal conditions it oscillates roughly between –3 and +3, but extreme confluences can push it outside that range. 2. Horizontal Threshold Lines: • +2 Line (Bullish threshold) • 0 Line (Neutral midline) • –2 Line (Bearish threshold) 3. Zone Coloring: • Green Background (Bullish Zone): When netScore ≥ +2. • Red Background (Bearish Zone): When netScore ≤ –2. • Gray Background (Sideways Zone): When –2 < netScore < +2. 4. Dynamic Line Color: • The plotted netScore line itself is colored green in a Bullish Zone, red in a Bearish Zone, or gray in a Sideways Zone, creating an immediate visual cue. Interpretation Tips: • Crossing Above +2: Signals a strong enough combined trend/momentum/price-action reading to classify as Bullish. Many traders wait for a clear crossing plus a confirmation candle before entering a long position. • Crossing Below –2: Indicates a strong Bearish signal. Traders may consider short or exit strategies. • Rising Slope, Even Below +2: If netScore climbs steadily from neutral toward +2, it demonstrates building bullish momentum. • Divergence: If price makes a higher high but the oscillator fails to reach a new high, it can warn of weakening momentum and a potential reversal. --- 14. Comments and Their Necessity Every sub-indicator (ADX, MA slope, Ichimoku, RSI, Stochastic, MACD, HH/LL, Heikin-Ashi, Candle Range, BBW, ATR, KCW, Volume) generates a short comment that appears in the detailed dashboard. Examples: • “Strong bullish trend” or “Strong bearish trend” for ADX/DMI • “Fast MA above slow MA” or “Fast MA below slow MA” for MA slope • “RSI above dynamic threshold” or “RSI below dynamic threshold” for RSI • “MACD histogram positive” or “MACD histogram negative” for MACD Hist • “Price near highs” or “Price near lows” for HH/LL checks • “Bullish Heikin Ashi” or “Bearish Heikin Ashi” for HA Doji scoring • “Large range, trend confirmed” or “Small range, trend contradicted” for Candle Range Additionally, the top-row comment for each category is: • Trend: “Highly Bullish,” “Highly Bearish,” or “Neutral Trend.” • Momentum: “Strong Momentum,” “Weak Momentum,” or “Neutral Momentum.” • Price Action: “Bullish Action,” “Bearish Action,” or “Neutral Action.” • Market Activity: “Volatile Market,” “Calm Market,” or “Stable Market.” Reasons for These Comments: • Transparency: Shows exactly how each sub-indicator contributed to its category score. • Education: Helps traders learn why a category is labeled bullish, bearish, or neutral, building intuition over time. • Customization: If, for example, the RSI comment says “RSI neutral” despite an impending trend shift, a trader might choose to adjust RSI length or thresholds. In the detailed dashboard, hovering over each comment cell also reveals a tooltip with additional context (e.g., “Fast MA above slow MA” or “Senkou A above Senkou B”), helping traders understand the precise rule behind that +1, 0, or –1 assignment. --- 15. Real-Life Example (Consolidated) • Instrument & Timeframe: Bitcoin (BTCUSD), 1-hour chart. • Current Market Activity: BBW and ATR both spike (+1 each), KCW is moderately high (+1), but volume is only neutral (0) → Raw Market Activity Score = +2 → State = High Activity (after two bars, if hysteresis is on). • Category Weights Applied: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Trend Sub-Scores: 1. ADX = 25 (above threshold 20) with +DI > –DI → +1. 2. Fast MA (20-period) sits above Slow MA (50-period) → +1. 3. Ichimoku: Senkou A > Senkou B → +1. → Trend Score = +3. • Momentum Sub-Scores: 4. RSI = 75 (above its moving average +1 stdev) → +1. 5. MACD histogram = +0.15 → +1. 6. Stochastic %K = 50 (mid-range) → 0. → Momentum Score = +2. • Price Action Sub-Scores: 7. Price is not within 1 % of the 20-period high/low and slope = positive → 0. 8. Heikin-Ashi body is slightly larger than stdev over last 5 bars with haClose > haOpen → +1. 9. Candle range is just above its dynamic upper bound but trend is already captured, so → +1. → Price Action Score = +2. • Calculate netScore (before smoothing): • Trend contribution = 3 × 0.50 = 1.50 • Momentum contribution = 2 × 0.35 = 0.70 • Price Action contribution = 2 × 0.15 = 0.30 • Raw netScore = 1.50 + 0.70 + 0.30 = 2.50 → Immediately classified as Bullish. • Oscillator & Dashboard Output: • The oscillator line crosses above +2 and turns green. • Dashboard displays: • Trend Regime “BULLISH,” Trend Score = 3, Comment = “Highly Bullish.” • Momentum Regime “BULLISH,” Momentum Score = 2, Comment = “Strong Momentum.” • Price Action Regime “BULLISH,” Price Action Score = 2, Comment = “Bullish Action.” • Market Activity State “High,” Comment = “Volatile Market.” • Weights: Trend 50 %, Momentum 35 %, Price Action 15 %. • Dominant Category: Trend (because 1.50 > 0.70 > 0.30). • Overall Score: 2.50, posCount = (three +1s in Trend) + (two +1s in Momentum) + (two +1s in Price Action) = 7 bullish signals, negCount = 0. • Final Zone = “BULLISH.” • The trader sees that both Trend and Momentum are reinforcing each other under high volatility. They might wait one more candle for confirmation but already have strong evidence to consider a long. --- • . --- Disclaimer This indicator is strictly a technical analysis tool and does not constitute financial advice. All trading involves risk, including potential loss of capital. Past performance is not indicative of future results. Traders should: • Always backtest the “Market Zone Analyzer ” on their chosen symbols and timeframes before committing real capital. • Combine this tool with sound risk management, position sizing, and, if possible, fundamental analysis. • Understand that no indicator is foolproof; always be prepared for unexpected market moves. Goodluck -BullByte! ---
Pine Script® indicator
by BullByte
2
Dow waveform analyzerDow Waveform Analyzer 1. Overview and Features of the Indicator This indicator is a tool designed to analyze chart waveforms based on Dow Theory, identifying swing lows (support) and swing highs (resistance). It allows users to quickly and consistently determine trend direction. Compared to manual analysis, it provides more efficient and accurate results. By using swing lows and swing highs, the indicator offers a more detailed understanding of trends than simple updates to highs and lows, aiding in the creation of effective trading strategies. 2. Identifying Wave Lows and Highs Stock prices do not move in straight lines; instead, they rise and fall in waves. This indicator starts by identifying the wave lows and wave highs. - Wave Low: The lowest point during a temporary price decline. - Wave High: The highest point during a temporary price increase. These are automatically identified using Pine Script’s built-in functions `pivotlow` and `pivothigh`. 3. Drawing the Waveform The identified wave lows and highs are alternately connected to draw the waveform. However, there are cases where wave lows or highs occur consecutively: - Consecutive Wave Lows: The lower low is used for drawing the waveform. - Consecutive Wave Highs: The higher high is used for drawing the waveform. 4. Tracking Swing Lows/Highs and Trend Determination Swing lows and swing highs are crucial markers that indicate the state of wave progression: - Swing Low: The starting point of a wave (wave low) when the closing price exceeds the previous wave high. - Swing High: The starting point of a wave (wave high) when the closing price falls below the previous wave low. The changes in swing lows and swing highs as the waves progress allow for trend state determination. 5. Examples of Trend States During an Uptrend: - When the price surpasses a wave high, the swing low is updated, confirming the continuation of the uptrend. End of an Uptrend: - When the price falls below the swing low, the swing low disappears, and a swing high appears, signaling the end of the uptrend. Sideways Movement: - Swing lows and swing highs alternately appear, indicating a sideways trend. Start of a Downtrend: - When the price breaks below a wave low for the first time, the swing high is updated, confirming the start of the downtrend. During a Downtrend: - When the price breaks below a wave low, the swing high is updated, confirming the continuation of the downtrend. End of a Downtrend: - When the price surpasses a wave high, the swing high disappears, and a swing low reappears, signaling the end of the downtrend. Restart of an Uptrend: - When the swing low is updated, the uptrend resumes. The uptrend begins when the price surpasses a wave high, and the swing low is updated for the first time. 6. Applications Trade Entries and Exits: - Set stop orders for entry at the price level where a trend starts. - Set stop orders for exit at the price level where a trend ends. Trend Filtering: - Use the indicator to confirm whether market conditions are suitable for entry based on the trend state. Analyze waveforms to aid trading strategies. Guide for Drawing Trendlines: - Utilize wave lows and highs as starting and ending points when drawing trendlines with drawing tools. 7. Parameters and Display Items Pivot Points: - Wave lows are marked with circles below the candlestick’s low, and wave highs are marked with circles above the candlestick’s high. Number of Bars for Pivot Calculation: - Specify the number of bars on either side used to identify highs (default: 2). Waveform: - Specify the color (default: blue) or toggle its visibility (default: visible). Swing Lows/Highs: - Displayed as large circles. The rightmost large circle on the chart indicates the current swing low or swing high. Historical swing points are also displayed to show the progression of state changes. Specify the color (default: green) or toggle visibility (default: visible). 1. インジケーターの概要と特徴 このインジケーターは、ダウ理論を基にチャートの波形を分析し、押し安値や戻り高値を特定するツールです。これにより、トレンドの方向を迅速かつ一貫して判断できます。手動での分析と比較して、効率的かつ精度の高い結果が得られる点が特徴です。 押し安値や戻り高値を利用することで、単純な高値・安値の更新よりも詳細にトレンドの状況を把握し、効果的な取引戦略の構築に役立ちます。 2. 波の谷と波の頂の特定 株価は直線的に動くのではなく、波を描きながら上昇や下落を繰り返します。このインジケーターは、まず波の谷と波の頂を特定するところから始まります。 波の谷: 一時的な下落の最安値 波の頂: 一時的な上昇の最高値 これらを Pine Script の内蔵関数（ピボットローとピボットハイ）を用いて自動的に特定しています。 3. 波形の描画方法 特定した波の谷と波の頂を交互に結んで波形を描画します。ただし、波の谷や頂が連続する場合があります。 波の谷が連続する場合: より低い谷を採用して波形を描く 波の頂が連続する場合: より高い頂を採用して波形を描く 4. 押し安値・戻り高値の追跡とトレンド判断 押し安値と戻り高値は、波の進行状況を示す重要な指標です。 押し安値: 終値が前回の高値を超えた際の波の谷 戻り高値: 終値が前回の安値を割り込んだ際の波の頂 波の進行に伴う押し安値・戻り高値の変化から、トレンドの状態を判断します。 5. トレンド状態の具体例 上昇トレンド中: 波の頂を株価が上抜け押し安値が更新され続けることで上昇トレンドを継続。 上昇トレンドの終了: 株価が押し安値を割ると、押し安値が消え、戻り高値が新たに出現して、上昇トレンドを終了。 横ばい状態: 押し安値と戻り高値が交互に切り替わる。 下降トレンドの開始: 波の谷を株価が下抜け戻り高値がはじめて更新されることで下降トレンド開始を確認。 下降トレンド中: 波の谷を株価が下抜け戻り高値が更新され続けることで下降トレンドを継続。 下降トレンドの終了: 株価が波の頂を超えると、戻り高値が消え、押し安値が再び出現して、下降トレンドを終了。 横ばい状態: 押し安値と戻り高値が交互に切り替わる。 上昇トレンドの再開: 押し安値が更新されることで上昇トレンドを確認。 波の頂を株価が上抜け押し安値がはじめて更新されることで上昇トレンド開始を確認。 6. 応用例 トレードのエントリーとエグジット: トレンド発生の価格に逆指値を設定してエントリー。 トレンド終了の価格に逆指値を設定してエグジット。 トレンドフィルターとして活用: エントリーに適したトレンド状況かを確認。波形を分析してトレード戦略の参考に。 トレンドラインを描く時の参考として活用: 波の谷と頂を描画ツールを使ってトレンドラインを描く時の起点や終点として活用。 7. パラメーターと表示項目 ピボット: 波の谷はローソク足の安値にサークルを表示、波の頂はローソク足の高値にサークルを表示。 ピボット計算用のバーの数: 高値を特定するために左右何本のローソク足を使用するかを設定（初期値: 2）。 波形: 色（初期値: 青）や表示（初期値: 表示）の指定。 押し安値・戻り高値: 大きなサークルで表示。チャートの一番右の大きなサークルが現在のもの。過去のものも状態変化の経緯を示すために表示。色（初期値: 緑）や表示（初期値: 表示）の指定。
Pine Script® indicator
by fightpm
1
Alligator + Fractals + Divergent & Squat Bars + Signal AlertsThe indicator includes Williams Alligator, Williams Fractals, Divergent Bars, Market Facilitation Index, Highest and Lowest Bars, maximum and minimum peak of Awesome Oscillator, and signal alerts based on Bill Williams' Profitunity strategy. MFI and Awesome Oscillator According to the Market Facilitation Index Oscillator, the Squat bar is colored blue, all other bars are colored according to the Awesome Oscillator color, except for the Fake bars, colored with a lighter AO color. In the indicator settings, you can enable the display of "Green" bars (in the "Green Bars > Show" field). In the indicator style settings, you can disable changing the color of bars in accordance with the AO color (in the "AO bars" field), including changing the color for Fake bars (in the "Fake AO bars" field). MFI is calculated using the formula: (high - low) / volume. A Squat bar means that, compared to the previous bar, its MFI has decreased and at the same time its volume has increased, i.e. MFI < previous bar and volume > previous bar. A sign of a possible price reversal, so this is a particularly important signal. A Fake bar is the opposite of a Squat bar and means that, compared to the previous bar, its MFI has increased and at the same time its volume has decreased, i.e. MFI > previous bar and volume < previous bar. A "Green" bar means that, compared to the previous bar, its MFI has increased and at the same time its volume has increased, i.e. MFI > previous bar and volume > previous bar. A sign of trend continuation. But a more significant trend confirmation or warning of a possible reversal is the Awesome Oscillator, which measures market momentum by calculating the difference between the 5 Period and 34 Period Simple Moving Averages (SMA 5 - SMA 34) based on the midpoints of the bars (hl2). Therefore, by default, the "Green" bars and their opposite "Fade" bars are colored according to the color of the Awesome Oscillator. According to Bill Williams' Profitunity strategy, using the Awesome Oscillator, the third Elliott wave is determined by the maximum peak of AO in the range from 100 to 140 bars. The presence of divergence between the maximum AO peak and the subsequent lower AO peak in this interval also warns of a possible correction, especially if the AO crosses the zero line between these AO peaks. Therefore, the chart additionally displays the prices of the highest and lowest bars, as well as the maximum or minimum peak of AO in the interval of 140 bars from the last bar. In the indicator settings, you can hide labels, lines, change the number of bars and any parameters for the AO indicator - method (SMA, Smoothed SMA, EMA and others), length, source (open, high, low, close, hl2 and others). Bullish Divergent bar 🟢 A buy signal (Long) is a Bullish Divergent bar with a green circle displayed above it if such a bar simultaneously meets all of the following conditions: The high of the bar is below all lines of the Alligator indicator. The closing price of the bar is above its middle, i.e. close > (high + low) / 2. The low of the bar is below the low of 2 previous bars or below the low of one previous bar, and the low of the second previous bar is a lower fractal (▼). By default, Divergent bars are not displayed, the low of which is lower than the low of only one previous bar and the low of the 2nd previous bar is not a lower fractal (▼), but you can enable the display of any Divergent bars in the indicator settings (by setting the value "no" in the " field Divergent Bars > Filtration"). The following conditions strengthen the Bullish Divergent bar signal: The opening price of the bar, as well as the closing price, is higher than its middle, i.e. Open > (high + low) / 2. The high of the bar is below all lines of the open Alligator indicator, i.e. the green line (Lips) is below the red line (Teeth) and the red line is below the blue line (Jaw). In this case, the color of the circle above the Bullish Divergent bar is dark green. Squat Divergent bar. The bar following the Bullish Divergent bar corresponds to the green color of the Awesome Oscillator. Divergence on Awesome Oscillator. Formation of the lower fractal (▼), in which the low of the Divergent bar is the peak of the fractal. Bearish Divergent bar 🔴 A signal to sell (Short) is a Bearish Divergent bar under which a red circle is displayed if such a bar simultaneously meets all the following conditions: The low of the bar is above all lines of the Alligator indicator. The closing price of the bar is below its middle, i.e. close < (high + low) / 2. The high of the bar is higher than the high of 2 previous bars or higher than the high of one previous bar, and the high of the second previous bar is an upper fractal (▲). By default, Divergent bars are not displayed, the high of which is higher than the high of only one previous bar and the high of the 2nd previous bar is not an upper fractal (▲), but you can enable the display of any Divergent bars in the indicator settings (by setting the value "no" in the " field Divergent Bars > Filtration"). The following conditions strengthen the Bearish Divergent bar signal: The opening price of the bar, as well as the closing price, is below its middle, i.e. open < (high + low) / 2. The low of the bar is above all lines of the open Alligator indicator, i.e. the green line (Lips) is above the red line (Teeth) and the red line is above the blue line (Jaw). In this case, the color of the circle under the Bearish Divergent bar is dark red. Squat Divergent bar. The bar following the Bearish Divergent bar corresponds to the red color of the Awesome Oscillator. Divergence on Awesome Oscillator. Formation of the upper fractal (▲), in which the high of the Divergent bar is the peak of the fractal. Alligator lines crossing Bars crossing the green line (Lips) of the open Alligator indicator is the first warning of a possible correction (price rollback) if one of the following conditions is met: If the bar closed below the Lips line, which is above the Teeth line, and the Teeth line is above the Jaw line, while the closing price of the previous bar is above the Lips line. If the bar closed above the Lips line, which is below the Teeth line, and the Teeth line is below the Jaw line, while the closing price of the previous bar is below the Lips line. The intersection of all open Alligator lines by bars is a sign of a deep correction and a warning of a possible trend change. Frequent intersection of Alligator lines with each other is a sign of a sideways trend (flat). Signal Alerts To receive notifications about signals when creating an alert, you must select the condition "Any alert() function is call", in which case notifications will arrive in the following format: D — timeframe, for example: D, 4H, 15m. 🟢 BDB⎾ - a signal for a Bullish Divergent bar to buy (Long), triggers once after the bar closes and includes additional signals: /// — if Alligator is open. ⏉ — if the opening price of the bar, as well as the closing price, is above its middle. + Squat 🔷 - Squat bar or + Green ↑ - "Green" bar or + Fake ↓ - Fake bar. + AO 🟩 - if after the Divergent bar closes, the oscillator color change for the next bar corresponds the green color of the Awesome Oscillator. ┴/┬ — AO above/below the zero line. ∇ — if there is divergence on AO in the interval of 140 bars from the last bar. 🔴 BDB⎿ - a signal for a Bearish Divergent bar to sell (Short), triggers once after the bar closes and includes additional signals: /// — if Alligator is open. ⏊ — if the opening price of the bar, as well as the closing price, is below its middle. + Squat 🔷 - Squat bar or + Green ↑ - "Green" bar or + Fake ↓ - Fake bar. + AO 🟥 - if after the Divergent bar closes, the oscillator color change for the next bar corresponds to the red color of the Awesome Oscillator. ┴/┬ — AO above/below the zero line. ∇ — if there is divergence on AO in the interval of 140 bars from the last bar. Alert for bars crossing the green line (Lips) of the open Alligator indicator (can be disabled in the indicator settings in the "Alligator > Enable crossing lips alerts" field): 🔴 Crossing Lips ↓ - if the bar closed below the Lips line, which is above than the other lines, while the closing price of the previous bar is above the Lips line. 🟢 Crossing Lips ↑ - if the bar closed above the Lips line, which is below the other lines, while the closing price of the previous bar is below the Lips line. The fractal signal is triggered after the second bar closes, completing the formation of the fractal, if alerts about fractals are enabled in the indicator settings (the "Fractals > Enable alerts" field): 🟢 Fractal ▲ - upper (Bearish) fractal. 🔴 Fractal ▼ — lower (Bullish) fractal. ⚪️ Fractal ▲/▼ - both upper and lower fractal. ↳ (H=high - L=low) = difference. If you redirect notifications to a webhook URL, for example, to a Telegram bot, then you need to set the notification template for the webhook in the indicator settings in the "Webhook > Message" field (contains a tooltip with an example), in which you just need to specify the text {{message}}, which will be automatically replaced with the alert text with a ticker and a link to TradingView. ‼️ A signal is not a call to action, but only a reason to analyze the chart to make a decision based on the rules of your strategy. *** Индикатор включает в себя Williams Alligator, Williams Fractals, Дивергентные бары, Market Facilitation Index, самый высокий и самый низкий бары, максимальный и минимальный пик Awesome Oscillator, а также оповещения о сигналах на основе стратегии Profitunity Билла Вильямса. MFI и Awesome Oscillator В соответствии с осциллятором Market Facilitation Index Приседающий бар окрашен в синий цвет, все остальные бары окрашены в соответствии с цветом Awesome Oscillator, кроме Фальшивых баров, которые окрашены более светлым цветом AO. В настройках индикатора вы можете включить отображение "Зеленых" баров (в поле "Green Bars > Show"). В настройках стиля индикатора вы можете выключить изменение цвета баров в соответствии с цветом AO (в поле "AO bars"), в том числе изменить цвет для Фальшивых баров (в поле "Fake AO bars"). MFI рассчитывается по формуле: (high - low) / volume. Приседающий бар означает, что по сравнению с предыдущим баром его MFI снизился и в тоже время вырос его объем, т.е. MFI < предыдущего бара и объем > предыдущего бара. Признак возможного разворота цены, поэтому это особенно важный сигнал. Фальшивый бар является противоположностью Приседающему бару и означает, что по сравнению с предыдущим баром его MFI увеличился и в тоже время снизился его объем, т.е. MFI > предыдущего бара и объем < предыдущего бара. "Зеленый" бар означает, что по сравнению с предыдущим баром его MFI увеличился и в тоже время вырос его объем, т.е. MFI > предыдущего бара и объем > предыдущего бара. Признак продолжения тренда. Но более значимым подтверждением тренда или предупреждением о возможном развороте является Awesome Oscillator, который измеряет движущую силу рынка путем вычисления разницы между 5 Периодной и 34 Периодной Простыми Скользящими Средними (SMA 5 - SMA 34) по средним точкам баров (hl2). Поэтому по умолчанию "Зеленые" бары и противоположные им "Увядающие" бары окрашены в соответствии с цветом Awesome Oscillator. По стратегии Profitunity Билла Вильямса с помощью осциллятора Awesome Oscillator определяется третья волна Эллиота по максимальному пику AO в интервале от 100 до 140 баров. Наличие дивергенции между максимальным пиком AO и следующим за ним более низким пиком AO в этом интервале также предупреждает о возможной коррекции, особенно если AO переходит через нулевую линию между этими пиками AO. Поэтому на графике дополнительно отображаются цены самого высокого и самого низкого баров, а также максимальный или минимальный пик АО в интервале 140 баров от последнего бара. В настройках индикатора вы можете скрыть метки, линии, изменить количество баров и любые параметры для индикатора AO – метод (SMA, Smoothed SMA, EMA и другие), длину, источник (open, high, low, close, hl2 и другие). Бычий Дивергентный бар 🟢 Сигналом на покупку (Long) является Бычий Дивергентный бар над которым отображается зеленый круг, если такой бар соответствует одновременно всем следующим условиям: Максимум бара ниже всех линий индикатора Alligator. Цена закрытия бара выше его середины, т.е. close > (high + low) / 2. Минимум бара ниже минимума 2-х предыдущих баров или ниже минимума одного предыдущего бара, а минимум второго предыдущего бара является нижним фракталом (▼). По умолчанию не отображаются Дивергентные бары, минимум которых ниже минимума только одного предыдущего бара и минимум 2-го предыдущего бара не является нижним фракталом (▼), но вы можете включить отображение любых Дивергентных баров в настройках индикатора (установив значение "no" в поле "Divergent Bars > Filtration"). Усилением сигнала Бычьего Дивергентного бара являются следующие условия: Цена открытия бара, как и цена закрытия, выше его середины, т.е. Open > (high + low) / 2. Максимум бара ниже всех линий открытого индикатора Alligator, т.е. зеленая линия (Lips) ниже красной линии (Teeth) и красная линия ниже синей линии (Jaw). В этом случае цвет круга над Бычьим Дивергентным баром окрашен в темно-зеленый цвет. Приседающий Дивергентный бар. Бар, следующий за Бычьим Дивергентным баром, соответствует зеленому цвету Awesome Oscillator. Дивергенция на Awesome Oscillator. Образование нижнего фрактала (▼), у которого минимум Дивергентного бара является пиком фрактала. Медвежий Дивергентный бар 🔴 Сигналом на продажу (Short) является Медвежий Дивергентный бар под которым отображается красный круг, если такой бар соответствует одновременно всем следующим условиям: Минимум бара выше всех линий индикатора Alligator. Цена закрытия бара ниже его середины, т.е. close < (high + low) / 2. Максимум бара выше маскимума 2-х предыдущих баров или выше максимума одного предыдущего бара, а максимум второго предыдущего бара является верхним фракталом (▲). По умолчанию не отображаются Дивергентные бары, максимум которых выше максимума только одного предыдущего бара и максимум 2-го предыдущего бара не является верхним фракталом (▲), но вы можете включить отображение любых Дивергентных баров в настройках индикатора (установив значение "no" в поле "Divergent Bars > Filtration"). Усилением сигнала Медвежьего Дивергентного бара являются следующие условия: Цена открытия бара, как и цена закрытия, ниже его середины, т.е. open < (high + low) / 2. Минимум бара выше всех линий открытого индикатора Alligator, т.е. зеленая линия (Lips) выше красной линии (Teeth) и красная линия выше синей линии (Jaw). В этом случае цвет круга под Медвежьим Дивергентным Баром окрашен в темно-красный цвет. Приседающий Дивергентный бар. Бар, следующий за Медвежьим Дивергентным баром, соответствует красному цвету Awesome Oscillator. Дивергенция на Awesome Oscillator. Образование верхнего фрактала (▲), у которого максимум Дивергентного бара является пиком фрактала. Пересечение линий Alligator Пересечение барами зеленой линии (Lips) открытого индикатора Alligator является первым предупреждением о возможной коррекции (откате цены) при выполнении одного из следующих условий: Если бар закрылся ниже линии Lips, которая выше линии Teeth, а линия Teeth выше линии Jaw, при этом цена закрытия предыдущего бара находится выше линии Lips. Если бар закрылся выше линии Lips, которая ниже линии Teeth, а линия Teeth ниже линии Jaw, при этом цена закрытия предыдущего бара находится ниже линии Lips. Пересечение барами всех линий открытого Alligator является признаком глубокой коррекции и предупреждением о возможной смене тренда. Частое пересечение линий Alligator между собой является признаком бокового тренда (флэт). Оповещения о сигналах Для получения уведомлений о сигналах при создании оповещения необходимо выбрать условие "При любом вызове функции alert()", в таком случае уведомления будут приходить в следующем формате: D — таймфрейм, например: D, 4H, 15m. 🟢 BDB⎾ — сигнал Бычьего Дивергентного бара на покупку (Long), срабатывает один раз после закрытия бара и включает дополнительные сигналы: /// — если Alligator открыт. ⏉ — если цена открытия бара, как и цена закрытия, выше его середины. + Squat 🔷 — Приседающий бар или + Green ↑ — "Зеленый" бар или + Fake ↓ — Фальшивый бар. + AO 🟩 — если после закрытия Дивергентного бара, изменение цвета осциллятора для следующего бара соответствует зеленому цвету Awesome Oscillator. ┴/┬ — AO выше/ниже нулевой линии. ∇ — если есть дивергенция на AO в интервале 140 баров от последнего бара. 🔴 BDB⎿ — сигнал Медвежьего Дивергентного бара на продажу (Short), срабатывает один раз после закрытия бара и включает дополнительные сигналы: /// — если Alligator открыт. ⏊ — если цена открытия бара, как и цена закрытия, ниже его середины. + Squat 🔷 — Приседающий бар или + Green ↑ — "Зеленый" бар или + Fake ↓ — Фальшивый бар. + AO 🟥 — если после закрытия Дивергентного бара, изменение цвета осциллятора для следующего бара соответствует красному цвету Awesome Oscillator. ┴/┬ — AO выше/ниже нулевой линии. ∇ — если есть дивергенция на AO в интервале 140 баров от последнего бара. Сигнал пересечения барами зеленой линии (Lips) открытого индикатора Alligator (можно отключить в настройках индикатора в поле "Alligator > Enable crossing lips alerts"): 🔴 Crossing Lips ↓ — если бар закрылся ниже линии Lips, которая выше остальных линий, при этом цена закрытия предыдущего бара находится выше линии Lips. 🟢 Crossing Lips ↑ — если бар закрылся выше линии Lips, которая ниже остальных линий, при этом цена закрытия предыдущего бара находится ниже линии Lips. Сигнал фрактала срабатывает после закрытия второго бара, завершающего формирование фрактала, если оповещения о фракталах включены в настройках индикатора (поле "Fractals > Enable alerts"): 🟢 Fractal ▲ — верхний (Медвежий) фрактал. 🔴 Fractal ▼ — нижний (Бычий) фрактал. ⚪️ Fractal ▲/▼ — одновременно верхний и нижний фрактал. ↳ (H=high - L=low) = разница. Если вы перенаправляете оповещения на URL вебхука, например, в бота Telegram, то вам необходимо установить шаблон оповещения для вебхука в настройках индикатора в поле "Webhook > Message" (содержит подсказку с примером), в котором в качестве текста сообщения достаточно указать текст {{message}}, который будет автоматически заменен на текст оповещения с тикером и ссылкой на TradingView. ‼️ Сигнал — это не призыв к действию, а лишь повод проанализировать график для принятия решения на основе правил вашей стратегии.
Pine Script® indicator
by grigorykov
45
YD_Divergence_RSI+CMFThe ‘YD_Divergence_RSI+CMF’ indicator can find divergence using RSI (Relative Strength Index) and CMF (Chaikin Money Flow) indicators. 📌 Key functions 1. Search pivot high and pivot low points in a certain length of price. 2. Connect pivot high to pivot high , pivot low to pivot low , forming two standards for divergence in result. The marker then plots only the higher high, lower low lines. (higher low and lower high in prices are referred to hidden divergence, which are not considered in this indicator) 3. Compare the two standards with RSI and CMF indicators, send an alert if there is a divergence. As a result, the indicator will find four combination of divergence. A. Higher high price / Lower RSI (Bearish RSI Divergence) B. Lower low price / Higher RSI (Bullish RSI Divergence) C. Higher high price / Lower CMF (Bearish CMF Divergence) D. Lower low price / Higher CMF (Bullish CMF Divergence) 📌 Details Developing the indicators, we put a lot of effort in making a customizable and user-friendly interface. #1. Pivot Setting Users can set the length to find the pivot high / pivot low in ‘Pivot Settings – Pivot Length.’ Increased pivot Length takes more candles to interpret the chart but reduce false signals since the it uses only the most certain pivot high / pivot low values. Obviously, decreased pivot length will act the opposite. Users can choose whether to use ‘High/Low’ or ‘Close’ in ‘Pivot Reference’ to set the swing point of prices. Users can also choose whether to display the pivot high / pivot low marker on the chart. #2 RSI & CMF Settings Users can adjust the length of RSI & CMF separately. (The default values are set to 14 and 20 each.) #3 Label Setting Users can adjust the text displayed on the chart label. (The default values is set to ‘Bullish / Bearish’, ‘RSI/CMF’, ‘Divergence’.) Users can reduce the length of text label or simply turn the label off. Just click the ‘Bull/Bear’ or ‘None’ button. ‘Divergence’ works the same. Users can decide whether to display the ‘Divergence Line and Label’, set custom settings for the label and line. (color, thickness, style, etc) 📌 Alert Alert are provided as a combination of the chart's symbol and the set label text. For example, ‘BINANCE:BTCUSDT.P, Bullish RSI Divergence’ ==================================================== "YD_Divergence_RSI+CMF" 지표 는 RSI와 CMF 지표를 이용해서 Divergence 를 찾아낼 수 있습니다. 📌 주요 기능 1. 정해진 가격 움직임 안에서 pivot high와 pivot low 포인트 를 찾아냅니다. 2. Pivot high로만 이어진 라인과, Pivot low로만 이어진 두 라인을 작도한 뒤 divergence의 기준으로 삼습니다. 이 지표에서는 normal divergence만 사용하기 때문에 차트에 higher high와 lower low만 표기 합니다. (higher low와 lower high는 hidden divergence로 정의되며, 이 지표에서는 다루지 않습니다. 3. 두 기준선과 RSI, CMF 지표를 각각 비교하고, 결과적으로 4개의 조합을 구할 수 있습니다. A. Higher high price / Lower RSI (Bearish RSI Divergence) B. Lower low price / Higher RSI (Bullish RSI Divergence) C. Higher high price / Lower CMF (Bearish CMF Divergence) D. Lower low price / Higher CMF (Bullish CMF Divergence) 📌 세부 사항 지표를 개발하며 사용자들이 원하는 방향으로 지표를 설정할 수 있게 작업에 많은 공을 들였습니다. 굉장히 다양한 옵션을 선택할 수 있으며, 원하는 방식으로 지표를 사용할 수 있습니다. #1 Pivot Setting Pivot setting에서는 Pivot Length를 변경할 수 있습니다. Pivot Length를 늘릴 경우, 보다 확실한 Swing High와 Swing Low만을 사용하게 되므로, False signal이 줄어들 수 있습니다. 하지만 Swing High/ Low를 판정하는 데에 더 긴 시간이 걸리게 되므로, Signal이 다소 늦게 발생하는 단점이 생기게 됩니다. Pivot Length를 줄일 경우, 반대로 Swing High/Low의 판정이 더 빨리 일어나기 때문에, Signal을 거래에 이용하기는 좋을 수 있습니다. 다만, Swing High와 Low가 훨씬 더 잦은 빈도로 발생하기 때문에 False Signal을 줄 가능성이 높아집니다. Pivot Reference에서는 가격의 Swing Point를 설정함에 있어, High/Low(고가/저가)를 이용할 지 Close (종가)를 이용할 지 선택할 수 있습니다. Pivot High/Low Marker를 선택할 경우 Pivot High/ Low에 Marker가 찍히게 됩니다. #2 RSI와 CMF Setting RSI와 CMF Setting에서는 RSI와 CMF의 길이를 각각 설정할 수 있습니다. 기본값은 14와 20으로 설정되어 있습니다. #3 Label Setting Label Setting에서는 Label에 표시되는 글자를 선택할 수 있습니다. 기본값은 "Bullish / Bearish", "RSI/CMF", "Divergence"로 선택되어 있으며, 너무 길다고 느껴질 경우 "Bull/Bear" 혹은 "None"을 클릭하여 길이를 줄일 수 있습니다. 마찬가지로 Divergence의 경우도 생략이 가능합니다. 하단에서는 Divergence Line과 Label을 켜고 끌 수 있으며, 선의 색깔, 굵기, 종류, 그리고 Label의 색깔, 크기, 종류를 선택할 수 있습니다. Label의 Text 색 역시 변경이 가능합니다. 📌 얼러트 얼러트는 자신이 설정한 차트의 심볼과 Label의 문구의 조합으로 제공되며 예를 들면 다음과 같습니다. "BINANCE:BTCUSDT.P, Bullish RSI Divergence"
Pine Script® indicator
by Yonsei_dent
4
SMC Structures and FVGสวัสดีครับ! ผมจะอธิบายอินดิเคเตอร์ "SMC Structures and FVG + MACD" ที่คุณให้มาอย่างละเอียดในแต่ละส่วน เพื่อให้คุณเข้าใจการทำงานของมันอย่างถ่องแท้ครับ อินดิเคเตอร์นี้เป็นการผสมผสานแนวคิดของ Smart Money Concept (SMC) ซึ่งเน้นการวิเคราะห์โครงสร้างตลาด (Market Structure) และ Fair Value Gap (FVG) เข้ากับอินดิเคเตอร์ MACD เพื่อใช้เป็นตัวกรองหรือตัวยืนยันสัญญาณ Choch/BoS (Change of Character / Break of Structure) 1. ภาพรวมอินดิเคเตอร์ (Overall Purpose) อินดิเคเตอร์นี้มีจุดประสงค์หลักคือ: ระบุโครงสร้างตลาด: ตีเส้นและป้ายกำกับ Choch (Change of Character) และ BoS (Break of Structure) บนกราฟโดยอัตโนมัติ ผสานการยืนยันด้วย MACD: สัญญาณ Choch/BoS จะถูกพิจารณาก็ต่อเมื่อ MACD Histogram เกิดการตัดขึ้นหรือลง (Zero Cross) ในทิศทางที่สอดคล้องกัน แสดง Fair Value Gap (FVG): หากเปิดใช้งาน จะมีการตีกล่อง FVG บนกราฟ แสดงระดับ Fibonacci: คำนวณและแสดงระดับ Fibonacci ที่สำคัญตามโครงสร้างตลาดปัจจุบัน ปรับตาม Timeframe: การคำนวณและการแสดงผลทั้งหมดจะปรับตาม Timeframe ที่คุณกำลังใช้งานอยู่โดยอัตโนมัติ 2. ส่วนประกอบหลักของโค้ด (Code Breakdown) โค้ดนี้สามารถแบ่งออกเป็นส่วนหลัก ๆ ได้ดังนี้: 2.1 Inputs (การตั้งค่า) ส่วนนี้คือตัวแปรที่คุณสามารถปรับแต่งได้ในหน้าต่างการตั้งค่าของอินดิเคเตอร์ (คลิกที่รูปฟันเฟืองข้างชื่ออินดิเคเตอร์บนกราฟ) MACD Settings (ตั้งค่า MACD): fast_len: ความยาวของ Fast EMA สำหรับ MACD (ค่าเริ่มต้น 12) slow_len: ความยาวของ Slow EMA สำหรับ MACD (ค่าเริ่มต้น 26) signal_len: ความยาวของ Signal Line สำหรับ MACD (ค่าเริ่มต้น 9) = ta.macd(close, fast_len, slow_len, signal_len): คำนวณค่า MACD Line, Signal Line และ Histogram โดยใช้ราคาปิด (close) และค่าความยาวที่กำหนด is_bullish_macd_cross: ตรวจสอบว่า MACD Histogram ตัดขึ้นเหนือเส้น 0 (จากค่าลบเป็นบวก) is_bearish_macd_cross: ตรวจสอบว่า MACD Histogram ตัดลงใต้เส้น 0 (จากค่าบวกเป็นลบ) Fear Value Gap (FVG) Settings: isFvgToShow: (Boolean) เปิด/ปิดการแสดง FVG บนกราฟ bullishFvgColor: สีสำหรับ Bullish FVG bearishFvgColor: สีสำหรับ Bearish FVG mitigatedFvgColor: สีสำหรับ FVG ที่ถูก Mitigate (ลดทอน) แล้ว fvgHistoryNbr: จำนวน FVG ย้อนหลังที่จะแสดง isMitigatedFvgToReduce: (Boolean) เปิด/ปิดการลดขนาด FVG เมื่อถูก Mitigate Structures (โครงสร้างตลาด) Settings: isStructBodyCandleBreak: (Boolean) หากเป็น true การ Break จะต้องเกิดขึ้นด้วย เนื้อเทียน ที่ปิดเหนือ/ใต้ Swing High/Low หากเป็น false แค่ไส้เทียนทะลุก็ถือว่า Break isCurrentStructToShow: (Boolean) เปิด/ปิดการแสดงเส้นโครงสร้างตลาดปัจจุบัน (เส้นสีน้ำเงินในภาพตัวอย่าง) pivot_len: ความยาวของแท่งเทียนที่ใช้ในการมองหาจุด Pivot (Swing High/Low) ยิ่งค่าน้อยยิ่งจับ Swing เล็กๆ ได้, ยิ่งค่ามากยิ่งจับ Swing ใหญ่ๆ ได้ bullishBosColor, bearishBosColor: สีสำหรับเส้นและป้าย BOS ขาขึ้น/ขาลง bosLineStyleOption, bosLineWidth: สไตล์ (Solid, Dotted, Dashed) และความหนาของเส้น BOS bullishChochColor, bearishChochColor: สีสำหรับเส้นและป้าย CHoCH ขาขึ้น/ขาลง chochLineStyleOption, chochLineWidth: สไตล์ (Solid, Dotted, Dashed) และความหนาของเส้น CHoCH currentStructColor, currentStructLineStyleOption, currentStructLineWidth: สี, สไตล์ และความหนาของเส้นโครงสร้างตลาดปัจจุบัน structHistoryNbr: จำนวนการ Break (Choch/BoS) ย้อนหลังที่จะแสดง Structure Fibonacci (จากโค้ดต้นฉบับ): เป็นชุด Input สำหรับเปิด/ปิด, กำหนดค่า, สี, สไตล์ และความหนาของเส้น Fibonacci Levels ต่างๆ (0.786, 0.705, 0.618, 0.5, 0.382) ที่จะถูกคำนวณจากโครงสร้างตลาดปัจจุบัน 2.2 Helper Functions (ฟังก์ชันช่วยทำงาน) getLineStyle(lineOption): ฟังก์ชันนี้ใช้แปลงค่า String ที่เลือกจาก Input (เช่น "─", "┈", "╌") ให้เป็นรูปแบบ line.style_ ที่ Pine Script เข้าใจ get_structure_highest_bar(lookback): ฟังก์ชันนี้พยายามหา Bar Index ของแท่งเทียนที่ทำ Swing High ภายในช่วง lookback ที่กำหนด get_structure_lowest_bar(lookback): ฟังก์ชันนี้พยายามหา Bar Index ของแท่งเทียนที่ทำ Swing Low ภายในช่วง lookback ที่กำหนด is_structure_high_broken(...): ฟังก์ชันนี้ตรวจสอบว่าราคาปัจจุบันได้ Break เหนือ _structureHigh (Swing High) หรือไม่ โดยพิจารณาจาก _highStructBreakPrice (ราคาปิดหรือราคา High ขึ้นอยู่กับการตั้งค่า isStructBodyCandleBreak) FVGDraw(...): ฟังก์ชันนี้รับ Arrays ของ FVG Boxes, Types, Mitigation Status และ Labels มาประมวลผล เพื่ออัปเดตสถานะของ FVG (เช่น ถูก Mitigate หรือไม่) และปรับขนาด/ตำแหน่งของ FVG Box และ Label บนกราฟ 2.3 Global Variables (ตัวแปรทั่วทั้งอินดิเคเตอร์) เป็นตัวแปรที่ประกาศด้วย var ซึ่งหมายความว่าค่าของมันจะถูกเก็บไว้และอัปเดตในแต่ละแท่งเทียน (persists across bars) structureLines, structureLabels: Arrays สำหรับเก็บอ็อบเจกต์ line และ label ของเส้น Choch/BoS ที่วาดบนกราฟ fvgBoxes, fvgTypes, fvgLabels, isFvgMitigated: Arrays สำหรับเก็บข้อมูลของ FVG Boxes และสถานะต่างๆ structureHigh, structureLow: เก็บราคาของ Swing High/Low ที่สำคัญของโครงสร้างตลาดปัจจุบัน structureHighStartIndex, structureLowStartIndex: เก็บ Bar Index ของจุดเริ่มต้นของ Swing High/Low ที่สำคัญ structureDirection: เก็บสถานะของทิศทางโครงสร้างตลาด (1 = Bullish, 2 = Bearish, 0 = Undefined) fiboXPrice, fiboXStartIndex, fiboXLine, fiboXLabel: ตัวแปรสำหรับเก็บข้อมูลและอ็อบเจกต์ของเส้น Fibonacci Levels isBOSAlert, isCHOCHAlert: (Boolean) ใช้สำหรับส่งสัญญาณ Alert (หากมีการตั้งค่า Alert ไว้) 2.4 FVG Processing (การประมวลผล FVG) ส่วนนี้จะตรวจสอบเงื่อนไขการเกิด FVG (Bullish FVG: high < low , Bearish FVG: low > high ) หากเกิด FVG และ isFvgToShow เป็น true จะมีการสร้าง box และ label ใหม่เพื่อแสดง FVG บนกราฟ มีการจัดการ fvgBoxes และ fvgLabels เพื่อจำกัดจำนวน FVG ที่แสดงตาม fvgHistoryNbr และลบ FVG เก่าออก ฟังก์ชัน FVGDraw จะถูกเรียกเพื่ออัปเดตสถานะของ FVG (เช่น การถูก Mitigate) และปรับการแสดงผล 2.5 Structures Processing (การประมวลผลโครงสร้างตลาด) Initialization: ที่ bar_index == 0 (แท่งเทียนแรกของกราฟ) จะมีการกำหนดค่าเริ่มต้นให้กับ structureHigh, structureLow, structureHighStartIndex, structureLowStartIndex Finding Current High/Low: highest, highestBar, lowest, lowestBar ถูกใช้เพื่อหา High/Low ที่สุดและ Bar Index ของมันใน 10 แท่งล่าสุด (หรือทั้งหมดหากกราฟสั้นกว่า 10 แท่ง) Calculating Structure Max/Min Bar: structureMaxBar และ structureMinBar ใช้ฟังก์ชัน get_structure_highest_bar และ get_structure_lowest_bar เพื่อหา Bar Index ของ Swing High/Low ที่แท้จริง (ไม่ใช่แค่ High/Low ที่สุดใน lookback แต่เป็นจุด Pivot ที่สมบูรณ์) Break Price: lowStructBreakPrice และ highStructBreakPrice จะเป็นราคาปิด (close) หรือราคา Low/High ขึ้นอยู่กับ isStructBodyCandleBreak isStuctureLowBroken / isStructureHighBroken: เงื่อนไขเหล่านี้ตรวจสอบว่าราคาได้ทำลาย structureLow หรือ structureHigh หรือไม่ โดยพิจารณาจากราคา Break, ราคาแท่งก่อนหน้า และ Bar Index ของจุดเริ่มต้นโครงสร้าง Choch/BoS Logic (ส่วนสำคัญที่ถูกผสานกับ MACD): if(isStuctureLowBroken and is_bearish_macd_cross): นี่คือจุดที่ MACD เข้ามามีบทบาท หากราคาทำลาย structureLow (สัญญาณขาลง) และ MACD Histogram เกิด Bearish Zero Cross (is_bearish_macd_cross เป็น true) อินดิเคเตอร์จะพิจารณาว่าเป็น Choch หรือ BoS หาก structureDirection == 1 (เดิมเป็นขาขึ้น) หรือ 0 (ยังไม่กำหนด) จะตีเป็น "CHoCH" (เปลี่ยนทิศทางโครงสร้างเป็นขาลง) หาก structureDirection == 2 (เดิมเป็นขาลง) จะตีเป็น "BOS" (ยืนยันโครงสร้างขาลง) มีการสร้าง line.new และ label.new เพื่อวาดเส้นและป้ายกำกับ structureDirection จะถูกอัปเดตเป็น 1 (Bullish) structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow จะถูกอัปเดตเพื่อกำหนดโครงสร้างใหม่ else if(isStructureHighBroken and is_bullish_macd_cross): เช่นกันสำหรับขาขึ้น หากราคาทำลาย structureHigh (สัญญาณขาขึ้น) และ MACD Histogram เกิด Bullish Zero Cross (is_bullish_macd_cross เป็น true) อินดิเคเตอร์จะพิจารณาว่าเป็น Choch หรือ BoS หาก structureDirection == 2 (เดิมเป็นขาลง) หรือ 0 (ยังไม่กำหนด) จะตีเป็น "CHoCH" (เปลี่ยนทิศทางโครงสร้างเป็นขาขึ้น) หาก structureDirection == 1 (เดิมเป็นขาขึ้น) จะตีเป็น "BOS" (ยืนยันโครงสร้างขาขึ้น) มีการสร้าง line.new และ label.new เพื่อวาดเส้นและป้ายกำกับ structureDirection จะถูกอัปเดตเป็น 2 (Bearish) structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow จะถูกอัปเดตเพื่อกำหนดโครงสร้างใหม่ การลบเส้นเก่า: d.delete_line (หากไลบรารีทำงาน) จะถูกเรียกเพื่อลบเส้นและป้ายกำกับเก่าออกเมื่อจำนวนเกิน structHistoryNbr Updating Structure High/Low (else block): หากไม่มีการ Break เกิดขึ้น แต่ราคาปัจจุบันสูงกว่า structureHigh หรือต่ำกว่า structureLow ในทิศทางที่สอดคล้องกัน (เช่น ยังคงเป็นขาขึ้นและทำ High ใหม่) structureHigh หรือ structureLow จะถูกอัปเดตเพื่อติดตาม High/Low ที่สุดของโครงสร้างปัจจุบัน Current Structure Display: หาก isCurrentStructToShow เป็น true อินดิเคเตอร์จะวาดเส้น structureHighLine และ structureLowLine เพื่อแสดงขอบเขตของโครงสร้างตลาดปัจจุบัน Fibonacci Display: หาก isFiboXToShow เป็น true อินดิเคเตอร์จะคำนวณและวาดเส้น Fibonacci Levels ต่างๆ (0.786, 0.705, 0.618, 0.5, 0.382) โดยอิงจาก structureHigh และ structureLow ของโครงสร้างตลาดปัจจุบัน Alerts: alertcondition: ใช้สำหรับตั้งค่า Alert ใน TradingView เมื่อเกิดสัญญาณ BOS หรือ CHOCH plot(na): plot(na) เป็นคำสั่งที่สำคัญในอินดิเคเตอร์ที่ไม่ได้ต้องการพล็อต Series ของข้อมูลบนกราฟ (เช่น ไม่ได้พล็อตเส้น EMA หรือ RSI) แต่ใช้วาดอ็อบเจกต์ (Line, Label, Box) โดยตรง การมี plot(na) ช่วยให้ Pine Script รู้ว่าอินดิเคเตอร์นี้มีเอาต์พุตที่แสดงผลบนกราฟ แม้ว่าจะไม่ได้เป็น Series ที่พล็อตตามปกติก็ตาม 3. วิธีใช้งาน คัดลอกโค้ดทั้งหมด ที่อยู่ในบล็อก immersive ด้านบน ไปที่ TradingView และเปิดกราฟที่คุณต้องการ คลิกที่เมนู "Pine Editor" ที่อยู่ด้านล่างของหน้าจอ ลบโค้ดเดิมที่มีอยู่ และ วางโค้ดที่คัดลอกมา ลงไปแทน คลิกที่ปุ่ม "Add to Chart" อินดิเคเตอร์จะถูกเพิ่มลงในกราฟของคุณโดยอัตโนมัติ คุณสามารถคลิกที่รูปฟันเฟืองข้างชื่ออินดิเคเตอร์บนกราฟเพื่อเข้าถึงหน้าต่างการตั้งค่าและปรับแต่งตามความต้องการของคุณได้ Hello! I will explain the "SMC Structures and FVG + MACD" indicator you provided in detail, section by section, so you can fully understand how it works.This indicator combines the concepts of Smart Money Concept (SMC), which focuses on analyzing Market Structure and Fair Value Gaps (FVG), with the MACD indicator to serve as a filter or confirmation for Choch (Change of Character) and BoS (Break of Structure) signals.1. Overall PurposeThe main purposes of this indicator are:Identify Market Structure: Automatically draw lines and label Choch (Change of Character) and BoS (Break of Structure) on the chart.Integrate MACD Confirmation: Choch/BoS signals will only be considered when the MACD Histogram performs a cross (Zero Cross) in the corresponding direction.Display Fair Value Gap (FVG): If enabled, FVG boxes will be drawn on the chart.Display Fibonacci Levels: Calculate and display important Fibonacci levels based on the current market structure.Adapt to Timeframe: All calculations and displays will automatically adjust to the timeframe you are currently using.2. Code BreakdownThis code can be divided into the following main sections:2.1 Inputs (Settings)This section contains variables that you can adjust in the indicator's settings window (click the gear icon next to the indicator's name on the chart).MACD Settings:fast_len: Length of the Fast EMA for MACD (default 12)slow_len: Length of the Slow EMA for MACD (default 26)signal_len: Length of the Signal Line for MACD (default 9) = ta.macd(close, fast_len, slow_len, signal_len): Calculates the MACD Line, Signal Line, and Histogram using the closing price (close) and the specified lengths.is_bullish_macd_cross: Checks if the MACD Histogram crosses above the 0 line (from negative to positive).is_bearish_macd_cross: Checks if the MACD Histogram crosses below the 0 line (from positive to negative).Fear Value Gap (FVG) Settings:isFvgToShow: (Boolean) Enables/disables the display of FVG on the chart.bullishFvgColor: Color for Bullish FVG.bearishFvgColor: Color for Bearish FVG.mitigatedFvgColor: Color for FVG that has been mitigated.fvgHistoryNbr: Number of historical FVG to display.isMitigatedFvgToReduce: (Boolean) Enables/disables reducing the size of FVG when mitigated.Structures (โครงสร้างตลาด) Settings:isStructBodyCandleBreak: (Boolean) If true, the break must occur with the candle body closing above/below the Swing High/Low. If false, a wick break is sufficient.isCurrentStructToShow: (Boolean) Enables/disables the display of the current market structure lines (blue lines in the example image).pivot_len: Lookback length for identifying Pivot points (Swing High/Low). A smaller value captures smaller, more frequent swings; a larger value captures larger, more significant swings.bullishBosColor, bearishBosColor: Colors for bullish/bearish BOS lines and labels.bosLineStyleOption, bosLineWidth: Style (Solid, Dotted, Dashed) and width of BOS lines.bullishChochColor, bearishChochColor: Colors for bullish/bearish CHoCH lines and labels.chochLineStyleOption, chochLineWidth: Style (Solid, Dotted, Dashed) and width of CHoCH lines.currentStructColor, currentStructLineStyleOption, currentStructLineWidth: Color, style, and width of the current market structure lines.structHistoryNbr: Number of historical breaks (Choch/BoS) to display.Structure Fibonacci (from original code):A set of inputs to enable/disable, define values, colors, styles, and widths for various Fibonacci Levels (0.786, 0.705, 0.618, 0.5, 0.382) that will be calculated from the current market structure.2.2 Helper FunctionsgetLineStyle(lineOption): This function converts the selected string input (e.g., "─", "┈", "╌") into a line.style_ format understood by Pine Script.get_structure_highest_bar(lookback): This function attempts to find the Bar Index of the Swing High within the specified lookback period.get_structure_lowest_bar(lookback): This function attempts to find the Bar Index of the Swing Low within the specified lookback period.is_structure_high_broken(...): This function checks if the current price has broken above _structureHigh (Swing High), considering _highStructBreakPrice (closing price or high price depending on isStructBodyCandleBreak setting).FVGDraw(...): This function takes arrays of FVG Boxes, Types, Mitigation Status, and Labels to process and update the status of FVG (e.g., whether it's mitigated) and adjust the size/position of FVG Boxes and Labels on the chart.2.3 Global VariablesThese are variables declared with var, meaning their values are stored and updated on each bar (persists across bars).structureLines, structureLabels: Arrays to store line and label objects for Choch/BoS lines drawn on the chart.fvgBoxes, fvgTypes, fvgLabels, isFvgMitigated: Arrays to store FVG box data and their respective statuses.structureHigh, structureLow: Stores the price of the significant Swing High/Low of the current market structure.structureHighStartIndex, structureLowStartIndex: Stores the Bar Index of the start point of the significant Swing High/Low.structureDirection: Stores the status of the market structure direction (1 = Bullish, 2 = Bearish, 0 = Undefined).fiboXPrice, fiboXStartIndex, fiboXLine, fiboXLabel: Variables to store data and objects for Fibonacci Levels.isBOSAlert, isCHOCHAlert: (Boolean) Used to trigger alerts in TradingView (if alerts are configured).2.4 FVG ProcessingThis section checks the conditions for FVG formation (Bullish FVG: high < low , Bearish FVG: low > high ).If FVG occurs and isFvgToShow is true, a new box and label are created to display the FVG on the chart.fvgBoxes and fvgLabels are managed to limit the number of FVG displayed according to fvgHistoryNbr and remove older FVG.The FVGDraw function is called to update the FVG status (e.g., whether it's mitigated) and adjust its display.2.5 Structures ProcessingInitialization: At bar_index == 0 (the first bar of the chart), structureHigh, structureLow, structureHighStartIndex, and structureLowStartIndex are initialized.Finding Current High/Low: highest, highestBar, lowest, lowestBar are used to find the highest/lowest price and its Bar Index of it in the last 10 bars (or all bars if the chart is shorter than 10 bars).Calculating Structure Max/Min Bar: structureMaxBar and structureMinBar use get_structure_highest_bar and get_structure_lowest_bar functions to find the Bar Index of the true Swing High/Low (not just the highest/lowest in the lookback but a complete Pivot point).Break Price: lowStructBreakPrice and highStructBreakPrice will be the closing price (close) or the Low/High price, depending on the isStructBodyCandleBreak setting.isStuctureLowBroken / isStructureHighBroken: These conditions check if the price has broken structureLow or structureHigh, considering the break price, previous bar prices, and the Bar Index of the structure's starting point.Choch/BoS Logic (Key Integration with MACD):if(isStuctureLowBroken and is_bearish_macd_cross): This is where MACD plays a role. If the price breaks structureLow (bearish signal) AND the MACD Histogram performs a Bearish Zero Cross (is_bearish_macd_cross is true), the indicator will consider it a Choch or BoS.If structureDirection == 1 (previously bullish) or 0 (undefined), it will be labeled "CHoCH" (changing structure direction to bearish).If structureDirection == 2 (already bearish), it will be labeled "BOS" (confirming bearish structure).line.new and label.new are used to draw the line and label.structureDirection will be updated to 1 (Bullish).structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow will be updated to define the new structure.else if(isStructureHighBroken and is_bullish_macd_cross): Similarly for bullish breaks. If the price breaks structureHigh (bullish signal) AND the MACD Histogram performs a Bullish Zero Cross (is_bullish_macd_cross is true), the indicator will consider it a Choch or BoS.If structureDirection == 2 (previously bearish) or 0 (undefined), it will be labeled "CHoCH" (changing structure direction to bullish).If structureDirection == 1 (already bullish), it will be labeled "BOS" (confirming bullish structure).line.new and label.new are used to draw the line and label.structureDirection will be updated to 2 (Bearish).structureHighStartIndex, structureLowStartIndex, structureHigh, structureLow will be updated to define the new structure.Deleting Old Lines: d.delete_line (if the library works) will be called to delete old lines and labels when their number exceeds structHistoryNbr.Updating Structure High/Low (else block): If no break occurs, but the current price is higher than structureHigh or lower than structureLow in the corresponding direction (e.g., still bullish and making a new high), structureHigh or structureLow will be updated to track the highest/lowest point of the current structure.Current Structure Display:If isCurrentStructToShow is true, the indicator draws structureHighLine and structureLowLine to show the boundaries of the current market structure.Fibonacci Display:If isFiboXToShow is true, the indicator calculates and draws various Fibonacci Levels (0.786, 0.705, 0.618, 0.5, 0.382) based on the structureHigh and structureLow of the current market structure.Alerts:alertcondition: Used to set up alerts in TradingView when BOS or CHOCH signals occur.plot(na):plot(na) is an important statement in indicators that do not plot data series directly on the chart (e.g., not plotting EMA or RSI lines) but instead draw objects (Line, Label, Box).Having plot(na) helps Pine Script recognize that this indicator has an output displayed on the chart, even if it's not a regularly plotted series.3. How to UseCopy all the code in the immersive block above.Go to TradingView and open your desired chart.Click on the "Pine Editor" menu at the bottom of the screen.Delete any existing code and paste the copied code in its place.Click the "Add to Chart" button.The indicator will be added to your chart automatically. You can click the gear icon next to the indicator's name on the chart to access the settings window and customize it to your needs.I hope this explanation helps you understand this indicator in detail. If anything is unclear, or you need further adjustments, please let me know.
Pine Script® indicator
by Mr-7TRILL
Fibonacci Retracement levels Automatically D/W/MIndicator Description: Fibonacci Retracement levels Automatically Fibonacci retracement levels based on the day, week, month High Low range and Fibonacci retracement levels draws automatically .This Pine Script indicator is designed to plot Fibonacci retracement levels based on the high and low prices of a user-selected timeframe (Daily, Weekly, or Monthly). It identifies bullish or bearish candles in the chosen timeframe, draws key price levels, and overlays Fibonacci retracement lines and semi-transparent colored boxes to highlight potential support and resistance zones. The indicator dynamically updates with each new period and extends lines, labels, and boxes to the current bar for real-time visualization. Key Features 1. Timeframe Selection: Users can choose the timeframe for analysis: Daily, Weekly, or Monthly via an input dropdown. The indicator retrieves the open, high, low, and close prices for the selected timeframe using `request.security`. 2. High and Low Tracking : Tracks the highest high and lowest low within the selected timeframe. Stores these values and their corresponding bar indices in arrays (`whigh`, `wlow`, `whighIdx`,`wlowIdx`). Limits the array size to the most recent period to optimize performance. 3. Bullish and Bearish Candle Detection : Identifies whether the previous period’s candle is bullish (`close > open`) or bearish (`close < open`). Uses this to determine the direction for Fibonacci retracement calculations. Bullish candle: Fibonacci levels are drawn from low to high Bearish candle: Fibonacci levels are drawn from high to low 4. Fibonacci Retracement Levels : Plots Fibonacci levels at 0.236, 0.382, 0.5, 0.618, and 0.786 between the high and low of the period. For bullish candles, levels are calculated from the low (support) to the high (resistance). For bearish candles, levels are calculated from the high (resistance) to the low (support). Each Fibonacci level is drawn as a horizontal line with a unique color: - 0.236: Blue - 0.382: Purple - 0.5: Yellow - 0.618: Teal - 0.786: Fuchsia 5. Visual Elements: - High/Low Lines and Labels: Draws a red line and label for the previous period’s high. Draws a green line and label for the previous period’s low. Fibonacci Lines and Labels: Each Fibonacci level has a horizontal line and a label displaying the ratio. Colored Boxes: Semi-transparent boxes are drawn between consecutive Fibonacci levels (including high and low) to highlight zones. 6. Dynamic Updates: - At the start of a new period (e.g., new week for Weekly timeframe), the indicator: - Clears previous Fibonacci lines, labels, and boxes. - Recalculates the high and low for the new period. - Redraws lines, labels, and boxes based on the new data. - Extends all lines, labels, and boxes to the current bar index for real-time tracking. 7. Performance Optimization: - Deletes old lines, labels, and boxes to prevent clutter. - Limits the storage of highs and lows to the most recent period. How It Works 1. Initialization: Defines variables for tracking bullish/bearish candles, lines, labels, and arrays for Fibonacci levels and boxes. Sets up color arrays for Fibonacci lines and boxes with distinct, semi-transparent colors. 2. Data Collection: Fetches the previous period’s OHLC (open, high, low, close) using `request.security`. Detects new periods (e.g., new week or month) using `ta.change(time(tf))`. 3. Fibonacci Calculation: On a new period, stores the high and low prices and their bar indices. - Identifies the maximum high and minimum low from the stored data. - Calculates Fibonacci levels based on the range (`maxHigh - minLow`) and the direction (bullish or bearish). 4. Drawing: - Draws high/low lines and labels at the identified price levels. Plots Fibonacci retracement lines and labels for each ratio. Creates semi-transparent boxes between Fibonacci levels to visually distinguish zones. 5. Updates: - Extends all lines, labels, and boxes to the current bar index when a new period is detected. Clears old Fibonacci elements to avoid overlap and ensure clarity. Usage - Purpose: This indicator is useful for traders who use Fibonacci retracement levels to identify potential support and resistance zones in financial markets. - Application: - Select the desired timeframe (Daily, Weekly, Monthly) via the input settings. - The indicator automatically plots the previous period’s high/low and Fibonacci levels on the chart. - Use the labeled Fibonacci levels and colored boxes to identify key price zones for trading decisions. - Customization: - Modify the `timeframe` input to switch between Daily, Weekly, or Monthly analysis. - Adjust the `fibLineColors` and `fibFillColors` arrays to change the visual appearance of lines and boxes. - The indicator is designed for use on TradingView with Pine Script. - The maximum array size for highs/lows is limited to 1 period in this version (can be adjusted by modifying the `array.shift` logic). - The indicator dynamically updates with each new period, ensuring real-time relevance. This indicator make educational purpose use only
Pine Script® indicator
by Trend_MyFrend
5
GEEKSDOBYTE IFVG w/ Buy/Sell Signals1. Inputs & Configuration Swing Lookback (swingLen) Controls how many bars on each side are checked to mark a swing high or swing low (default = 5). Booleans to Toggle Plotting showSwings – Show small triangle markers at swing highs/lows showFVG – Show Fair Value Gap zones showSignals – Show “BUY”/“SELL” labels when price inverts an FVG showDDLine – Show a yellow “DD” line at the close of the inversion bar showCE – Show an orange dashed “CE” line at the midpoint of the gap area 2. Swing High / Low Detection isSwingHigh = ta.pivothigh(high, swingLen, swingLen) Marks a bar as a swing high if its high is higher than the highs of the previous swingLen bars and the next swingLen bars. isSwingLow = ta.pivotlow(low, swingLen, swingLen) Marks a bar as a swing low if its low is lower than the lows of the previous and next swingLen bars. Plotting If showSwings is true, small red downward triangles appear above swing highs, and green upward triangles below swing lows. 3. Fair Value Gap (3‐Bar) Identification A Fair Value Gap (FVG) is defined here using a simple three‐bar logic (sometimes called an “inefficiency” in price): Bullish FVG (bullFVG) Checks if, two bars ago, the low of that bar (low ) is strictly greater than the current bar’s high (high). In other words: bullFVG = low > high Bearish FVG (bearFVG) Checks if, two bars ago, the high of that bar (high ) is strictly less than the current bar’s low (low). In other words: bearFVG = high < low When either condition is true, it identifies a three‐bar “gap” or unfilled imbalance in the market. 4. Drawing FVG Zones If showFVG is enabled, each time a bullish or bearish FVG is detected: Bullish FVG Zone Draws a semi‐transparent green box from the bar two bars ago (where the gap began) at low up to the current bar’s high. Bearish FVG Zone Draws a semi‐transparent red box from the bar two bars ago at high down to the current bar’s low. These colored boxes visually highlight the “fair value imbalance” area on the chart. 5. Inversion (Fill) Detection & Entry Signals An inversion is defined as the price “closing through” that previously drawn FVG: Bullish Inversion (bullInversion) Occurs when a bullish FVG was identified on bar-2 (bullFVG), and on the current bar the close is greater than that old bar-2 low: bullInversion = bullFVG and close > low Bearish Inversion (bearInversion) Occurs when a bearish FVG was identified on bar-2 (bearFVG), and on the current bar the close is lower than that old bar-2 high: bearInversion = bearFVG and close < high When an inversion is true, the indicator optionally draws two lines and a label (depending on input toggles): Draw “DD” Line (yellow, solid) Plots a horizontal yellow line from the current bar’s close price extending five bars forward (bar_index + 5). This is often referred to as a “Demand/Daily Demand” line, marking where price inverted the gap. Draw “CE” Line (orange, dashed) Calculates the midpoint (ce) of the original FVG zone. For a bullish inversion: ce = (low + high) / 2 For a bearish inversion: ce = (high + low) / 2 Plots a horizontal dashed orange line at that midpoint for five bars forward. Plot Label (“BUY” / “SELL”) If showSignals is true, a green “BUY” label is placed at the low of the current bar when a bullish inversion occurs. Likewise, a red “SELL” label at the high of the current bar when a bearish inversion happens. 6. Putting It All Together Swing Markers (Optional): Visually confirm recent swing highs and swing lows with small triangles. FVG Zones (Optional): Highlight areas where price left a 3-bar gap (bullish in green, bearish in red). Inversion Confirmation: Wait for price to close beyond the old FVG boundary. Once that happens, draw the yellow “DD” line at the close, the orange dashed “CE” line at the zone’s midpoint, and place a “BUY” or “SELL” label exactly on that bar. User Controls: All of the above elements can be individually toggled on/off (showSwings, showFVG, showSignals, showDDLine, showCE). In Practice A bullish FVG forms whenever a strong drop leaves a gap in liquidity (three bars ago low > current high). When price later “fills” that gap by closing above the old low, the script signals a potential long entry (BUY), draws a demand line at the closing price, and marks the midpoint of that gap. Conversely, a bearish FVG marks a potential short zone (three bars ago high < current low). When price closes below that gap’s high, it signals a SELL, with similar lines drawn. By combining these elements, the indicator helps users visually identify inefficiencies (FVGs), confirm when price inverts/fills them, and place straightforward buy/sell labels alongside reference lines for trade management.
Pine Script® indicator
by RayenGeeksdoByte
FvgCalculations█ OVERVIEW This library provides the core calculation engine for identifying Fair Value Gaps (FVGs) across different timeframes and for processing their interaction with price. It includes functions to detect FVGs on both the current chart and higher timeframes, as well as to check for their full or partial mitigation. █ CONCEPTS The library's primary functions revolve around the concept of Fair Value Gaps and their lifecycle. Fair Value Gap (FVG) Identification An FVG, or imbalance, represents a price range where buying or selling pressure was significant enough to cause a rapid price movement, leaving an "inefficiency" in the market. This library identifies FVGs based on three-bar patterns: Bullish FVG: Forms when the low of the current bar (bar 3) is higher than the high of the bar two periods prior (bar 1). The FVG is the space between the high of bar 1 and the low of bar 3. Bearish FVG: Forms when the high of the current bar (bar 3) is lower than the low of the bar two periods prior (bar 1). The FVG is the space between the low of bar 1 and the high of bar 3. The library provides distinct functions for detecting FVGs on the current (Low Timeframe - LTF) and specified higher timeframes (Medium Timeframe - MTF / High Timeframe - HTF). FVG Mitigation Mitigation refers to price revisiting an FVG. Full Mitigation: An FVG is considered fully mitigated when price completely closes the gap. For a bullish FVG, this occurs if the current low price moves below or touches the FVG's bottom. For a bearish FVG, it occurs if the current high price moves above or touches the FVG's top. Partial Mitigation (Entry/Fill): An FVG is partially mitigated when price enters the FVG's range but does not fully close it. The library tracks the extent of this fill. For a bullish FVG, if the current low price enters the FVG from above, that low becomes the new effective top of the remaining FVG. For a bearish FVG, if the current high price enters the FVG from below, that high becomes the new effective bottom of the remaining FVG. FVG Interaction This refers to any instance where the current bar's price range (high to low) touches or crosses into the currently unfilled portion of an active (visible and not fully mitigated) FVG. Multi-Timeframe Data Acquisition To detect FVGs on higher timeframes, specific historical bar data (high, low, and time of bars at indices and relative to the higher timeframe's last completed bar) is required. The requestMultiTFBarData function is designed to fetch this data efficiently. █ CALCULATIONS AND USE The functions in this library are typically used in a sequence to manage FVGs: 1. Data Retrieval (for MTF/HTF FVGs): Call requestMultiTFBarData() with the desired higher timeframe string (e.g., "60", "D"). This returns a tuple of htfHigh1, htfLow1, htfTime1, htfHigh3, htfLow3, htfTime3. 2. FVG Detection: For LTF FVGs: Call detectFvg() on each confirmed bar. It uses high , low, low , and high along with barstate.isconfirmed. For MTF/HTF FVGs: Call detectMultiTFFvg() using the data obtained from requestMultiTFBarData(). Both detection functions return an fvgObject (defined in FvgTypes) if an FVG is found, otherwise na. They also can classify FVGs as "Large Volume" (LV) if classifyLV is true and the FVG size (top - bottom) relative to the tfAtr (Average True Range of the respective timeframe) meets the lvAtrMultiplier. 3. FVG State Updates (on each new bar for existing FVGs): First, check for overall price interaction using fvgInteractionCheck(). This function determines if the current bar's high/low has touched or entered the FVG's currentTop or currentBottom. If interaction occurs and the FVG is not already mitigated: Call checkMitigation() to determine if the FVG has been fully mitigated by the current bar's currentHigh and currentLow. If true, the FVG's isMitigated status is updated. If not fully mitigated, call checkPartialMitigation() to see if the price has further entered the FVG. This function returns the newLevel to which the FVG has been filled (e.g., currentLow for a bullish FVG, currentHigh for bearish). This newLevel is then used to update the FVG's currentTop or currentBottom. The calling script (e.g., fvgMain.c) is responsible for storing and managing the array of fvgObject instances and passing them to these update functions. █ NOTES Bar State for LTF Detection: The detectFvg() function relies on barstate.isconfirmed to ensure FVG detection is based on closed bars, preventing FVGs from being detected prematurely on the currently forming bar. Higher Timeframe Data (lookahead): The requestMultiTFBarData() function uses lookahead = barmerge.lookahead_on. This means it can access historical data from the higher timeframe that corresponds to the current bar on the chart, even if the higher timeframe bar has not officially closed. This is standard for multi-timeframe analysis aiming to plot historical HTF data accurately on a lower timeframe chart. Parameter Typing: Functions like detectMultiTFFvg and detectFvg infer the type for boolean (classifyLV) and numeric (lvAtrMultiplier) parameters passed from the main script, while explicitly typed series parameters (like htfHigh1, currentAtr) expect series data. fvgObject Dependency: The FVG detection functions return fvgObject instances, and fvgInteractionCheck takes an fvgObject as a parameter. This UDT is defined in the FvgTypes library, making it a dependency for using FvgCalculations. ATR for LV Classification: The tfAtr (for MTF/HTF) and currentAtr (for LTF) parameters are expected to be the Average True Range values for the respective timeframes. These are used, if classifyLV is enabled, to determine if an FVG's size qualifies it as a "Large Volume" FVG based on the lvAtrMultiplier. MTF/HTF FVG Appearance Timing: When displaying FVGs from a higher timeframe (MTF/HTF) on a lower timeframe (LTF) chart, users might observe that the most recent MTF/HTF FVG appears one LTF bar later compared to its appearance on a native MTF/HTF chart. This is an expected behavior due to the detection mechanism in `detectMultiTFFvg`. This function uses historical bar data from the MTF/HTF (specifically, data equivalent to `HTF_bar ` and `HTF_bar `) to identify an FVG. Therefore, all three bars forming the FVG on the MTF/HTF must be fully closed and have shifted into these historical index positions relative to the `request.security` call from the LTF chart before the FVG can be detected and displayed on the LTF. This ensures that the MTF/HTF FVG is identified based on confirmed, closed bars from the higher timeframe. █ EXPORTED FUNCTIONS requestMultiTFBarData(timeframe)   Requests historical bar data for specific previous bars from a specified higher timeframe.   It fetches H , L , T (for the bar before last) and H , L , T (for the bar three periods prior) from the requested timeframe.   This is typically used to identify FVG patterns on MTF/HTF.   Parameters:      timeframe (simple string) : The higher timeframe to request data from (e.g., "60" for 1-hour, "D" for Daily).   Returns: A tuple containing: .   - htfHigh1 (series float): High of the bar at index 1 (one bar before the last completed bar on timeframe).   - htfLow1 (series float): Low of the bar at index 1.   - htfTime1 (series int) : Time of the bar at index 1.   - htfHigh3 (series float): High of the bar at index 3 (three bars before the last completed bar on timeframe).   - htfLow3 (series float): Low of the bar at index 3.   - htfTime3 (series int) : Time of the bar at index 3. detectMultiTFFvg(htfHigh1, htfLow1, htfTime1, htfHigh3, htfLow3, htfTime3, tfAtr, classifyLV, lvAtrMultiplier, tfType)   Detects a Fair Value Gap (FVG) on a higher timeframe (MTF/HTF) using pre-fetched bar data.   Parameters:      htfHigh1 (float) : High of the first relevant bar (typically high ) from the higher timeframe.      htfLow1 (float) : Low of the first relevant bar (typically low ) from the higher timeframe.      htfTime1 (int) : Time of the first relevant bar (typically time ) from the higher timeframe.      htfHigh3 (float) : High of the third relevant bar (typically high ) from the higher timeframe.      htfLow3 (float) : Low of the third relevant bar (typically low ) from the higher timeframe.      htfTime3 (int) : Time of the third relevant bar (typically time ) from the higher timeframe.      tfAtr (float) : ATR value for the higher timeframe, used for Large Volume (LV) FVG classification.      classifyLV (bool) : If true, FVGs will be assessed to see if they qualify as Large Volume.      lvAtrMultiplier (float) : The ATR multiplier used to define if an FVG is Large Volume.      tfType (series tfType enum from no1x/FvgTypes/1) : The timeframe type (e.g., types.tfType.MTF, types.tfType.HTF) of the FVG being detected.   Returns: An fvgObject instance if an FVG is detected, otherwise na. detectFvg(classifyLV, lvAtrMultiplier, currentAtr)   Detects a Fair Value Gap (FVG) on the current (LTF - Low Timeframe) chart.   Parameters:      classifyLV (bool) : If true, FVGs will be assessed to see if they qualify as Large Volume.      lvAtrMultiplier (float) : The ATR multiplier used to define if an FVG is Large Volume.      currentAtr (float) : ATR value for the current timeframe, used for LV FVG classification.   Returns: An fvgObject instance if an FVG is detected, otherwise na. checkMitigation(isBullish, fvgTop, fvgBottom, currentHigh, currentLow)   Checks if an FVG has been fully mitigated by the current bar's price action.   Parameters:      isBullish (bool) : True if the FVG being checked is bullish, false if bearish.      fvgTop (float) : The top price level of the FVG.      fvgBottom (float) : The bottom price level of the FVG.      currentHigh (float) : The high price of the current bar.      currentLow (float) : The low price of the current bar.   Returns: True if the FVG is considered fully mitigated, false otherwise. checkPartialMitigation(isBullish, currentBoxTop, currentBoxBottom, currentHigh, currentLow)   Checks for partial mitigation of an FVG by the current bar's price action.   It determines if the price has entered the FVG and returns the new fill level.   Parameters:      isBullish (bool) : True if the FVG being checked is bullish, false if bearish.      currentBoxTop (float) : The current top of the FVG box (this might have been adjusted by previous partial fills).      currentBoxBottom (float) : The current bottom of the FVG box (similarly, might be adjusted).      currentHigh (float) : The high price of the current bar.      currentLow (float) : The low price of the current bar.   Returns: The new price level to which the FVG has been filled (e.g., currentLow for a bullish FVG).   Returns na if no new partial fill occurred on this bar. fvgInteractionCheck(fvg, highVal, lowVal)   Checks if the current bar's price interacts with the given FVG.   Interaction means the price touches or crosses into the FVG's current (possibly partially filled) range.   Parameters:      fvg (fvgObject type from no1x/FvgTypes/1) : The FVG object to check.     Its isMitigated, isVisible, isBullish, currentTop, and currentBottom fields are used.      highVal (float) : The high price of the current bar.      lowVal (float) : The low price of the current bar.   Returns: True if price interacts with the FVG, false otherwise.
Pine Script® library
by no1x
Enigma Sniper 369The "Enigma Sniper 369" is a custom-built Pine Script indicator designed for TradingView, tailored specifically for forex traders seeking high-probability entries during high-volatility market sessions. Unlike generic trend-following or scalping tools, this indicator uniquely combines session-based "kill zones" (London and US sessions), momentum-based candle analysis, and an optional EMA trend filter to pinpoint liquidity grabs and reversal opportunities. Its originality lies in its focus on liquidity hunting—identifying levels where stop losses are likely clustered (around swing highs/lows and wick midpoints)—and providing visual entry zones that are dynamically removed once price breaches them, reducing clutter and focusing on actionable signals. The name "369" reflects the structured approach of three key components (session timing, candle logic, and trend filter) working in harmony to snipe precise entries. What It Does "Enigma Sniper 369" identifies potential buy and sell opportunities by drawing two types of horizontal lines on the chart during user-defined London and US session kill zones: Solid Lines: Mark the swing low (for buys) or swing high (for sells) of a trigger candle, indicating a potential entry point where stop losses might be clustered. Dotted Lines: Mark the 50% level of the candle’s wick (lower wick for buys, upper wick for sells), serving as a secondary confirmation zone for entries or tighter stop-loss placement. These lines are plotted only when specific candle conditions are met within the kill zones, and they are automatically deleted once the price crosses them, signaling that the liquidity at that level has likely been grabbed. The indicator also includes an optional EMA filter to ensure trades align with the broader trend, reducing false signals in choppy markets. How It Works The indicator’s logic is built on a multi-layered approach: Kill Zone Timing: Trades are only considered during user-defined London and US session hours (e.g., London from 02:00 to 12:00 UTC, as seen in the screenshots). These sessions are known for high volatility and liquidity, making them ideal for capturing institutional moves. Candle-Based Momentum Logic: Buy Signal: A candle must close above its midpoint (indicating bullish momentum) and have a lower low than the previous candle (suggesting a potential liquidity grab below the previous swing low). This is expressed as close > (high + low) / 2 and low < low . Sell Signal: A candle must close below its midpoint (bearish momentum) and have a higher high than the previous candle (indicating a potential liquidity grab above the previous swing high), expressed as close < (high + low) / 2 and high > high . These conditions ensure the indicator targets candles that break recent structure to hunt stop losses while showing directional momentum. Optional EMA Filter: A 50-period EMA (customizable) can be enabled to filter signals based on trend direction. Buy signals are only generated if the EMA is trending upward (ema_value > ema_value ), and sell signals require a downward EMA trend (ema_value < ema_value ). This reduces noise by aligning entries with the broader market trend. Liquidity Levels and Deletion Logic: For a buy signal, a solid green line is drawn at the candle’s low, and a dotted green line at the 50% level of the lower wick (from the candle body’s bottom to the low). For a sell signal, a solid red line is drawn at the candle’s high, and a dotted red line at the 50% level of the upper wick (from the body’s top to the high). These lines extend to the right until the price crosses them, at which point they are deleted, indicating the liquidity at that level has been taken (e.g., stop losses triggered). Alerts: The indicator includes alert conditions for buy and sell signals, notifying traders when a new setup is identified. Underlying Concepts The indicator is grounded in the concept of liquidity hunting, a strategy often employed by institutional traders. Markets frequently move to levels where stop losses are clustered—typically just beyond swing highs or lows—before reversing in the opposite direction. The "Enigma Sniper 369" targets these moves by identifying candles that break structure (e.g., a lower low or higher high) during high-volatility sessions, suggesting a potential sweep of stop losses. The 50% wick level acts as a secondary confirmation, as this midpoint often represents a zone where tighter stop losses are placed by retail traders. The optional EMA filter adds a trend-following element, ensuring entries are taken in the direction of the broader market momentum, which is particularly useful on lower timeframes like the 15-minute chart shown in the screenshots. How to Use It Here’s a step-by-step guide based on the provided usage example on the GBP/USD 15-minute chart: Setup the Indicator: Add "Enigma Sniper 369" to your TradingView chart. Adjust the London and US session hours to match your timezone (e.g., London from 02:00 to 12:00 UTC, US from 13:00 to 22:00 UTC). Customize the EMA period (default 50) and line styles/colors if desired. Identify Kill Zones: The indicator highlights the London session in light green and the US session in light purple, as seen in the screenshots. Focus on these periods for signals, as they are the most volatile and likely to produce liquidity grabs. Wait for a Signal: Look for solid and dotted lines to appear during the kill zones: Buy Setup: A solid green line at the swing low and a dotted green line at the 50% lower wick level indicate a potential buy. This suggests the market may have grabbed liquidity below the swing low and is now poised to move higher. Sell Setup: A solid red line at the swing high and a dotted red line at the 50% upper wick level indicate a potential sell, suggesting liquidity was taken above the swing high. Place Your Trade: For a buy, set a buy limit order at the dotted green line (50% wick level), as this is a more conservative entry point. Place your stop loss just below the solid green line (swing low) to cover the full swing. For example, in the screenshots, the market retraces to the dotted line at 1.32980 after a liquidity grab below the swing low, triggering a buy limit order. For a sell, set a sell limit order at the dotted red line, with a stop loss just above the solid red line. Monitor Price Action: Once the price crosses a line, it is deleted, indicating the liquidity at that level has been taken. In the screenshots, after the buy limit is triggered, the market moves higher, confirming the setup. The caption notes, “The market returns and tags us in long with a buy limit,” highlighting this retracement strategy. Additional Context: Use the indicator to identify liquidity levels that may be targeted later. For example, the screenshot notes, “If a new session is about to open I will wait for the grab liquidity to go long,” showing how the indicator can be used to anticipate future moves at session opens (e.g., London open at 1.32980). Risk Management: Always set a stop loss below the swing low (for buys) or above the swing high (for sells) to protect against adverse moves. The 50% wick level helps tighten entries, improving the risk-reward ratio. Practical Example On the GBP/USD 15-minute chart, during the London session (02:00 UTC), the indicator identifies a buy setup with a solid green line at 1.32901 (swing low) and a dotted green line at 1.32980 (50% wick level). The market initially dips below the swing low, grabbing liquidity, then retraces to the dotted line, triggering a buy limit order. The price subsequently rises to 1.33404, yielding a profitable trade. The user notes, “The logic is in the last candle it provides new level to go long,” emphasizing the indicator’s ability to identify fresh levels after a liquidity sweep. Customization Tips Adjust the EMA period to suit your timeframe (e.g., a shorter period like 20 for faster signals on lower timeframes). Modify the session hours to align with your broker’s timezone or specific market conditions. Use the alert feature to get notified of new setups without constantly monitoring the chart. Why It’s Useful for Traders The "Enigma Sniper 369" stands out by combining session timing, momentum-based candle analysis, and liquidity hunting into a single tool. It provides clear, actionable levels for entries and stop losses, removes invalid signals dynamically, and aligns trades with high-probability market conditions. Whether you’re a scalper looking for quick moves during London open or a swing trader targeting session-based reversals, this indicator offers a structured, data-driven approach to trading.
Pine Script® indicator
by Niko-picasso369
8
OBV by readCrypto ------------------------------------- OBV is used as a leading indicator to predict stock price movements by measuring changes in trading volume. Reflecting the cumulative value of trading volume, - When the price rises, if the trading volume increases, OBV rises, - When the price falls, if the trading volume decreases, OBV falls. Therefore, the movement of the OBV indicator must be checked along with the price movement, and it has the disadvantage of being unreliable for coins (tokens) with low trading volume. --------------------------------------- (First interpretation method) By adding a signal line for the OBV indicator, - If the OBV indicator moves above the signal line, it is likely to show an upward trend, - If the OBV indicator moves beyond the signal line, it is likely to show a downward trend. This interpretation method is difficult to use in actual trading strategies because the OBV indicator often moves up and down repeatedly based on the signal line. Therefore, it is recommended to use this interpretation method as reference when analyzing charts. ------------------------------- (Second interpretation method) Draw support and resistance lines based on the high and low points of the OBV indicator - If the OBV indicator breaks through the previous high point, it is likely to show an upward trend, - If the OBV indicator breaks through the previous low point, it is likely to show a downward trend. This interpretation method is a bit more reliable than the first interpretation method, but it has the disadvantage of having to consider support and resistance lines separately based on the high and low points. - To compensate for this, a High line for the high point and a Low line for the low point were added. - If the OBV indicator shows an upward breakout of each line (Low, HL2, High), the price is likely to rise, - If the OBV indicator shows a downward breakout of each line (Low, HL2, High), the price is likely to fall. - Also, the Low and High lines can be interpreted like Bollinger Bands. That is, if the Low and High lines show a contraction, the price is likely to move sideways, and if they show an expansion, the price is likely to show a trend. Therefore, if the High line breaks upward in a contracted state, - It is likely to show an upward trend, - If the Low line breaks downward, it is likely to show a downward trend. In an expanded state, you should focus on finding the point to realize profits rather than conducting new transactions. -------------------------------- It is not easy to interpret the change in actual transaction volume and use it to create a trading strategy. In particular, it is more difficult in the coin market where multiple exchanges are linked to show movements for one coin (token). Therefore, the coin market is actively conducting transactions without referring to trading volume at all by following trends. However, I think that if you interpret the change in trading volume and use it to find a trading point, it can help you find a more accurate trading point. In that sense, I think that an indicator that adds the High and Low lines of the OBV indicator can be used as meaningful reference material. ----------------------------------------------------------------- ------------------------------------- OBV는 거래량의 변화를 측정하여 주가 움직임을 예측하는 선행 지표로 활용됩니다. 거래량의 누적값을 반영하여 - 가격이 상승할 때 거래량이 증가면 OBV가 상승하고, - 가격이 하락할 때 거래량이 줄면 OBV가 하락하게 됩니다. 따라서, 가격의 움직임과 함께 OBV 지표의 움직임을 확인하여야 하고 거래량이 적은 코인(토큰)에서는 신뢰성이 떨어지는 단점도 가지고 있습니다. --------------------------------------- (첫번째 해석 방법) OBV 지표에 대한 Signal선을 추가하여 - OBV 지표가 Signal선 이상에서 이동하게 되면 상승세를 보일 가능성이 높고, - OBV 지표가 Signal선 이항에서 이동하게 되면 하락세를 보일 가능성이 높습니다. 이러한 해석 방법은 Signal선을 기준으로 OBV 지표가 반복적으로 위아래로 움직임을 보이는 경우가 많기 때문에 실제 거래 전략에 활용되기가 어려운 면이 있습니다. 따라서, 이러한 해설 방법은 차트 분석을 할 때 참고 자료로 활용하는 것이 좋습니다. ------------------------------- (두번째 해석 방법) OBV 지표의 고점과 저점을 기준하여 지지와 저항선을 그려 - OBV 지표가 이전 고점을 상향 돌파하면 상승세를 보일 가능성이 높고, - OBV 지표가 이전 저점을 하향 돌파하면 하락세를 보일 가능성이 높습니다. 이러한 해석 방법은 첫번째 해석 방법보다 좀 더 신뢰성이 있는 방법이지만, 고점과 저점을 기준으로 지지와 저항선을 나누어 생각해야 하는 단점이 있습니다. - 이를 보완하고자 고점에 대한 High선과 저점에 대한 Low선을 추가하였습니다. - OBV 지표가 각 선(Low, HL2, High)을 상향 돌파하는 모습을 보이면 가격이 상승할 가능성이 높고, - OBV 지표가 각 선(Low, HL2, High)을 하향 돌파하는 모습을 보이면 가격이 하락할 가능성이 높습니다. - 또한, Low선과 High선을 볼린저밴드와 같이 해석할 수 있습니다. 즉, Low선과 High선이 수축하는 모습을 보이면 가격은 횡보할 가능성이 높고, 확장하는 모습을 보이면 가격은 추세를 나타낼 가능성이 높습니다. 따라서, 수축한 상태에서 - High선을 상향 돌파하게 되면 상승세를 나타낼 가능성이 높고, - Low선을 하향 돌파하게 되면 하락세를 나타낼 가능성이 높습니다. 확장된 상태에서는 신규 거래를 진행하기 보다 수익 실현할 시점을 찾는데 집중해야 합니다. -------------------------------- 실제 거래량의 변화를 해석하여 거래 전략을 만드는데 활용하기가 쉽지 않습니다. 특히, 하나의 코인(토큰)에 대해서 여러 개의 거래소가 연동되어 움직임을 나타내는 코인 시장에서는 더욱 어려움이 있습니다. 따라서, 코인 시장은 추세 추종으로 아예 거래량을 참고하지 않고 거래를 진행하는 방법이 활성화되어 있기도 합니다. 하지만, 거래량의 변화를 해석하여 거래 시점을 찾는데 활용한다면 보다 정확한 거래 시점을 찾는데 도움을 받을 수 있다고 생각합니다. 그러한 의미에서 OBV 지표의 High선과 Low선을 추가한 지표가 의미 있는 참고 자료로 활용될 수 있다고 생각합니다. -------------------------------------------------------------------
Pine Script® indicator
by readCrypto
2
HH-HL-HH and LL-LH-LL Screener with AlertsAh, it seems you're referring to "Higher Low Higher High" in the context of **trading signals**! In trading, especially in technical analysis, these terms could be describing patterns or movements of price action that traders use to make decisions. Let’s break down the terms you mentioned: ### 1. **Higher Low (HL)**: - A **Higher Low** occurs when the price forms a low point that is higher than the previous low. It indicates upward momentum and suggests that the market may be in an uptrend or reversing to an uptrend. For example: - The price hits a low at $50, then rises to $60, then drops to $55. The **$55 low** is higher than the previous $50 low, indicating a potential uptrend. ### 2. **Higher High (HH)**: - A **Higher High** happens when the price forms a high that is higher than the previous high. This is a strong bullish signal and is typical in an uptrend. For example: - The price reaches a peak of $70, drops to $60, then rises to $75. The **$75 high** is higher than the previous $70 high, indicating upward momentum. ### The Sequence: **Higher Low, Higher High (HL-HH)** - This sequence (HL-HH) suggests that the market is in a **bullish trend**, with each subsequent low being higher than the previous low and each high being higher than the previous high. It’s a confirmation that the price is generally trending upwards, and traders might look for **buying opportunities**. ### 3. **Lower Low (LL)**: - A **Lower Low** is when the price forms a low that is lower than the previous low, which is typically a sign of downward momentum. Traders may interpret this as a bearish signal. For example: - If the price drops from $60 to $55, then falls to $50, the **$50 low** is lower than the previous $55 low, indicating a potential downtrend. ### 4. **Lower High (LH)**: - A **Lower High** occurs when the price forms a high that is lower than the previous high. This can indicate a weakening uptrend or the start of a downtrend. For example: - The price peaks at $70, then drops to $60, and later rises to $65. The **$65 high** is lower than the previous $70 high, suggesting bearish pressure. ### The Sequence: **Lower Low, Lower High (LL-LH)** - The **LL-LH** pattern suggests a **bearish trend**, where the price forms lower lows and lower highs. This could signal to traders that the price is in a downward movement, and they might look for **selling opportunities**. --- ### Using This in Trading: Traders often look for **higher highs** and **higher lows** in an uptrend (HL-HH), or **lower lows** and **lower highs** in a downtrend (LL-LH) to gauge market direction and make decisions. - **Bullish Sign**: Higher Low, Higher High (HL-HH) = Look for buying signals or long positions. - **Bearish Sign**: Lower Low, Lower High (LL-LH) = Look for selling signals or short positions. Is this the type of trading signal you’re referring to? Let me know if you'd like to explore how to apply these signals in specific trading strategies!
Pine Script® indicator
by Mikeramzee
V Pattern TrendDESCRIPTION: The V Pattern Trend Indicator is designed to identify and highlight V-shaped reversal patterns in price action. It detects both bullish and bearish V formations using a five-candle structure, helping traders recognize potential trend reversal points. The indicator filters out insignificant patterns by using customizable settings based on ATR, percentage, or points, ensuring that only meaningful V patterns are displayed. CALCULATION METHOD The user can choose how the minimum length of a V pattern is determined. The available options are: - ATR (Average True Range) – Filters V patterns based on ATR, making the detection adaptive to market volatility. - Percentage (%) – Considers V patterns where the absolute price difference between the V low and V high is greater than a user-defined percentage of the V high. - Points – Uses a fixed number of points to filter valid V patterns, making it useful for assets with consistent price ranges. ATR SETTINGS - ATR Length – Defines the number of periods for ATR calculation. - ATR Multiplier – Determines the minimum V length as a multiple of ATR. PERCENTAGE THRESHOLD - Sets a minimum percentage difference between the V high and V low for a pattern to be considered valid. POINTS THRESHOLD - Defines the minimum price movement (in points) required for a V pattern to be considered significant. PATTERN VISUALIZATION - A bullish V pattern is plotted using two upward-sloping lines, with a filled green region to highlight the formation. - A bearish V pattern is plotted using two downward-sloping lines, with a filled red region to indicate the reversal. - The indicator dynamically updates and marks only the most recent valid patterns. UNDERSTANDING V PATTERNS A V pattern is a sharp reversal formation where price moves strongly in one direction and then rapidly reverses in the opposite direction, forming a "V" shape on the chart. BULLISH V PATTERN - A bullish V pattern is formed when the price makes three consecutive lower lows, followed by two consecutive higher lows. - The pattern is confirmed when the highest high of the formation is greater than the previous highs within the structure. - This pattern suggests a potential trend reversal from bearish to bullish. - The lowest point of the pattern represents the V low, which acts as a support level. bull_five_candle_v = low > low and low > low and low > low and low > low and high > math.max(high , high , high ) and high > math.max(high , high , high ) BEARISH V PATTERN - A bearish V pattern is detected when the price makes three consecutive higher highs, followed by two consecutive lower highs. - The pattern is confirmed when the lowest low of the formation is lower than the previous lows within the structure. - This pattern signals a possible trend reversal from bullish to bearish. - The highest point of the pattern represents the V high, which acts as a resistance level. bear_five_candle_v = high < high and high < high and high < high and high < high and low < math.min(low , low , low ) and low < math.min(low , low , low ) HOW THIS IS UNIQUE - Advanced Filtering Mechanism – Unlike basic reversal indicators, this tool provides customizable filtering based on ATR, percentage, or points, ensuring that only significant V patterns are displayed. - Enhanced Visual Clarity – The indicator uses color-coded fills and structured plotting to make reversal patterns easy to recognize. - Works Across Market Conditions – Adaptable to different market environments, filtering out weak or insignificant price fluctuations. - Multi-Timeframe Usability – Can be applied across different timeframes and asset classes, making it useful for both intraday and swing trading. HOW TRADERS CAN USE THIS INDICATOR - Identify potential trend reversals early based on structured price action. - Filter out weak or insignificant reversals to focus only on strong V formations. - Use the V pattern’s highs and lows as key support and resistance zones for trade entries and exits. - Combine with other indicators like moving averages, trendlines, or momentum oscillators for confirmation.
Pine Script® indicator
by Shivam_Mandrai
SCE Price Action SuiteThis is an indicator designed to use past market data to mark key price action levels as well as provide a different kind of insight. There are 8 different features in the script that users can turn on and off. This description will go in depth on all 8 with chart examples. #1 Absorption Zones I defined Absorption Zones as follows. //---------------------------------------------- //---------------Absorption--------------------- //---------------------------------------------- box absorptionBox = na absorptionBar = ta.highest(bodySize, absorptionLkb) bsab = ta.barssince(bool(ta.change(absorptionBar))) if bsab == 0 and upBar and showAbsorption absorptionBox := box.new(left = bar_index - 1, top = close, right = bar_index + az_strcuture, bottom = open, border_color = color.rgb(0, 80, 75), border_width = boxLineSize, bgcolor = color.rgb(0, 80, 75)) absorptionBox else if bsab == 0 and downBar and showAbsorption absorptionBox := box.new(left = bar_index - 1, top = close, right = bar_index + az_strcuture, bottom = open, border_color = color.rgb(105, 15, 15), border_width = boxLineSize, bgcolor = color.rgb(105, 15, 15)) absorptionBox What this means is that absorption bars are defined as the bars with the largest bodies over a selected lookback period. Those large bodies represent areas where price may react. I was inspired by the concept of a Fair Value Gap for this concept. In that body price may enter to be a point of support or resistance, market participants get “absorbed” in the area so price can continue in whichever direction. #2 Candle Wick Theory/Strategy I defined Candle Wick Theory/Strategy as follows. //---------------------------------------------- //---------------Candle Wick-------------------- //---------------------------------------------- highWick = upBar ? high - close : downBar ? high - open : na lowWick = upBar ? open - low : downBar ? close - low : na upWick = upBar ? close + highWick : downBar ? open + highWick : na downWick = upBar ? open - lowWick : downBar ? close - lowWick : na downDelivery = upBar and downBar and high > upWick and highWick > lowWick and totalSize > totalSize and barstate.isconfirmed and session.ismarket upDelivery = downBar and upBar and low < downWick and highWick < lowWick and totalSize > totalSize and barstate.isconfirmed and session.ismarket line lG = na line lE = na line lR = na bodyMidpoint = math.abs(body) / 2 upWickMidpoint = math.abs(upWickSize) / 2 downWickkMidpoint = math.abs(downWickSize) / 2 if upDelivery and showCdTheory cpE = chart.point.new(time, bar_index - 1, downWickkMidpoint) cpE2 = chart.point.new(time, bar_index + bl, downWickkMidpoint) cpG = chart.point.new(time, bar_index + bl, downWickkMidpoint * (1 + tp)) cpR = chart.point.new(time, bar_index + bl, downWickkMidpoint * (1 - sl)) cpG1 = chart.point.new(time, bar_index - 1, downWickkMidpoint * (1 + tp)) cpR1 = chart.point.new(time, bar_index - 1, downWickkMidpoint * (1 - sl)) lG := line.new(cpG1, cpG, xloc.bar_index, extend.none, color.green, line.style_solid, 1) lE := line.new(cpE, cpE2, xloc.bar_index, extend.none, color.white, line.style_solid, 1) lR := line.new(cpR1, cpR, xloc.bar_index, extend.none, color.red, line.style_solid, 1) lR else if downDelivery and showCdTheory cpE = chart.point.new(time, bar_index - 1, upWickMidpoint) cpE2 = chart.point.new(time, bar_index + bl, upWickMidpoint) cpG = chart.point.new(time, bar_index + bl, upWickMidpoint * (1 - tp)) cpR = chart.point.new(time, bar_index + bl, upWickMidpoint * (1 + sl)) cpG1 = chart.point.new(time, bar_index - 1, upWickMidpoint * (1 - tp)) cpR1 = chart.point.new(time, bar_index - 1, upWickMidpoint * (1 + sl)) lG := line.new(cpG1, cpG, xloc.bar_index, extend.none, color.green, line.style_solid, 1) lE := line.new(cpE, cpE2, xloc.bar_index, extend.none, color.white, line.style_solid, 1) lR := line.new(cpR1, cpR, xloc.bar_index, extend.none, color.red, line.style_solid, 1) lR First I get the size of the wicks for the top and bottoms of the candles. This depends on if the bar is red or green. If the bar is green the wick is the high minus the close, if red the high minus the open, and so on. Next, the script defines the upper and lower bounds of the wicks for further comparison. If the candle is green, it's the open price minus the bottom wick. If the candle is red, it's the close price minus the bottom wick, and so on. Next we have the condition for when this strategy is present. Down delivery: Occurs when the previous candle is green, the current candle is red, and: The high of the current candle is above the upper wick of the previous candle. The size of the current candle's top wick is greater than its bottom wick. The total size of the previous candle is greater than the total size of the current candle. The current bar is confirmed (barstate.isconfirmed). The session is during market hours (session.ismarket). Up delivery: Occurs when the previous candle is red, the current candle is green, and: The low of the current candle is below the lower wick of the previous candle. The size of the current candle's bottom wick is greater than its top wick. The total size of the previous candle is greater than the total size of the current candle. The current bar is confirmed. The session is during market hours Then risk is plotted from the percentage that users can input from an ideal entry spot. #3 Candle Size Theory I defined Candle Size Theory as follows. //---------------------------------------------- //---------------Candle displacement------------ //---------------------------------------------- line lECD = na notableDown = bodySize > bodySize * candle_size_sensitivity and downBar and session.ismarket and barstate.isconfirmed notableUp = bodySize > bodySize * candle_size_sensitivity and upBar and session.ismarket and barstate.isconfirmed if notableUp and showCdSizeTheory cpE = chart.point.new(time, bar_index - 1, close) cpE2 = chart.point.new(time, bar_index + bl_strcuture, close) lECD := line.new(cpE, cpE2, xloc.bar_index, extend.none, color.rgb(0, 80, 75), line.style_solid, 3) lECD else if notableDown and showCdSizeTheory cpE = chart.point.new(time, bar_index - 1, close) cpE2 = chart.point.new(time, bar_index + bl_strcuture, close) lECD := line.new(cpE, cpE2, xloc.bar_index, extend.none, color.rgb(105, 15, 15), line.style_solid, 3) lECD This plots candles that are “notable” or out of the ordinary. Candles that are larger than the last by a value users get to specify. These candles' highs or lows, if they are green or red, act as levels for support or resistance. #4 Candle Structure Theory I defined Candle Structure Theory as follows. //---------------------------------------------- //---------------Structure---------------------- //---------------------------------------------- breakDownStructure = low < low and low < low and high > high and upBar and downBar and upBar and downBar and session.ismarket and barstate.isconfirmed breakUpStructure = low > low and low > low and high < high and downBar and upBar and downBar and upBar and session.ismarket and barstate.isconfirmed if breakUpStructure and showStructureTheory cpE = chart.point.new(time, bar_index - 1, close) cpE2 = chart.point.new(time, bar_index + bl_strcuture, close) lE := line.new(cpE, cpE2, xloc.bar_index, extend.none, color.teal, line.style_solid, 3) lE else if breakDownStructure and showStructureTheory cpE = chart.point.new(time, bar_index - 1, open) cpE2 = chart.point.new(time, bar_index + bl_strcuture, open) lE := line.new(cpE, cpE2, xloc.bar_index, extend.none, color.red, line.style_solid, 3) lE It is a series of candles to create a notable event. 2 lower lows in a row, a lower high, then green bar, red bar, green bar is a structure for a breakdown. 2 higher lows in a row, a higher high, red bar, green bar, red bar for a break up. #5 Candle Swing Structure Theory I defined Candle Swing Structure Theory as follows. //---------------------------------------------- //---------------Swing Structure---------------- //---------------------------------------------- line htb = na line ltb = na if totalSize * swing_struct_sense < totalSize and upBar and downBar and high > high and showSwingSturcture and session.ismarket and barstate.isconfirmed cpS = chart.point.new(time, bar_index - 1, high) cpE = chart.point.new(time, bar_index + bl_strcuture, high) htb := line.new(cpS, cpE, xloc.bar_index, color = color.red, style = line.style_dashed) htb else if totalSize * swing_struct_sense < totalSize and downBar and upBar and low > low and showSwingSturcture and session.ismarket and barstate.isconfirmed cpS = chart.point.new(time, bar_index - 1, low) cpE = chart.point.new(time, bar_index + bl_strcuture, low) ltb := line.new(cpS, cpE, xloc.bar_index, color = color.teal, style = line.style_dashed) ltb A bearish swing structure is defined as the last candle’s total size, times a scalar that the user can input, is less than the current candles. Like a size imbalance. The last bar must be green and this one red. The last high should also be less than this high. For a bullish swing structure the same size imbalance must be present, but we need a red bar then a green bar, and the last low higher than the current low. #6 Fractal Boxes I define the Fractal Boxes as follows //---------------------------------------------- //---------------Fractal Boxes------------------ //---------------------------------------------- box b = na int indexx = na if bar_index % (n * 2) == 0 and session.ismarket and showBoxes b := box.new(left = bar_index, top = topBox, right = bar_index + n, bottom = bottomBox, border_color = color.rgb(105, 15, 15), border_width = boxLineSize, bgcolor = na) indexx := bar_index + 1 indexx The idea of this strategy is that the market is fractal. It is considered impossible to be able to tell apart two different time frames from just the chart. So inside the chart there are many many breakouts and breakdowns happening as price bounces around. The boxes are there to give you the view from your timeframe if the market is in a range from a time frame that would be higher than it. Like if we are inside what a larger time frame candle’s range. If we break out or down from this, we might be able to trade it. Users can specify a lookback period and the box is that period’s, as an interval, high and low. I say as an interval because it is plotted every n * 2 bars. So we get a box, price moves, then a new box. #7 Potential Move Width I define the Potential Move Width as follows //---------------------------------------------- //---------------Move width--------------------- //---------------------------------------------- velocity = V(n) line lC = na line l = na line l2 = na line l3 = na line l4 = na line l5 = na line l6 = na line l7 = na line l8 = na line lGFractal = na line lRFractal = na cp2 = chart.point.new(time, bar_index + n, close + velocity) cp3 = chart.point.new(time, bar_index + n, close - velocity) cp4 = chart.point.new(time, bar_index + n, close + velocity * 5) cp5 = chart.point.new(time, bar_index + n, close - velocity * 5) cp6 = chart.point.new(time, bar_index + n, close + velocity * 10) cp7 = chart.point.new(time, bar_index + n, close - velocity * 10) cp8 = chart.point.new(time, bar_index + n, close + velocity * 15) cp9 = chart.point.new(time, bar_index + n, close - velocity * 15) cpG = chart.point.new(time, bar_index + n, close + R) cpR = chart.point.new(time, bar_index + n, close - R) if ((bar_index + n) * 2 - bar_index) % n == 0 and session.ismarket and barstate.isconfirmed and showPredictionWidtn cp = chart.point.new(time, bar_index, close) cpG1 = chart.point.new(time, bar_index, close + R) cpR1 = chart.point.new(time, bar_index, close - R) l := line.new(cp, cp2, xloc.bar_index, extend.none, color.aqua, line.style_solid, 1) l2 := line.new(cp, cp3, xloc.bar_index, extend.none, color.aqua, line.style_solid, 1) l3 := line.new(cp, cp4, xloc.bar_index, extend.none, color.red, line.style_solid, 1) l4 := line.new(cp, cp5, xloc.bar_index, extend.none, color.red, line.style_solid, 1) l5 := line.new(cp, cp6, xloc.bar_index, extend.none, color.teal, line.style_solid, 1) l6 := line.new(cp, cp7, xloc.bar_index, extend.none, color.teal, line.style_solid, 1) l7 := line.new(cp, cp8, xloc.bar_index, extend.none, color.blue, line.style_solid, 1) l8 := line.new(cp, cp9, xloc.bar_index, extend.none, color.blue, line.style_solid, 1) l8 By using the past n bar’s velocity, or directional speed, every n * 2 bars. I can use it to scale the close value and get an estimate for how wide the next moves might be. #8 Linear regression //---------------------------------------------- //---------------Linear Regression-------------- //---------------------------------------------- lr = showLR ? ta.linreg(close, n, 0) : na plot(lr, 'Linear Regression', color.blue) I used TradingView’s built in linear regression to not reinvent the wheel. This is present to see past market strength of weakness from a different perspective. User input Users can control a lot about this script. For the strategy based plots you can enter what you want the risk to be in percentages. So the default 0.01 is 1%. You can also control how far forward the line goes. Look back at where it is needed as well as line width for the Fractal Boxes are controllable. Also users can check on and off what they would like to see on the charts. No indicator is 100% reliable, do not follow this one blindly. I encourage traders to make their own decisions and not trade solely based on technical indicators. I encourage constructive criticism in the comments below. Thank you.
Pine Script® indicator
by ScorsoneEnterprises
lib_smcLibrary "lib_smc" This is an adaptation of LuxAlgo's Smart Money Concepts indicator with numerous changes. Main changes include integration of object based plotting, plenty of performance improvements, live tracking of Order Blocks, integration of volume profiles to refine Order Blocks, and many more. This is a library for developers, if you want this converted into a working strategy, let me know. buffer(item, len, force_rotate)   Parameters:      item (float)      len (int)      force_rotate (bool) buffer(item, len, force_rotate)   Parameters:      item (int)      len (int)      force_rotate (bool) buffer(item, len, force_rotate)   Parameters:      item (Profile type from robbatt/lib_profile/32)      len (int)      force_rotate (bool) swings(len)   INTERNAL: detect swing points (HH and LL) in given range   Parameters:      len (simple int) : range to check for new swing points   Returns: values are the price level where and if a new HH or LL was detected, else na method init(this)   Namespace types: OrderBlockConfig   Parameters:      this (OrderBlockConfig) method delete(this)   Namespace types: OrderBlock   Parameters:      this (OrderBlock) method clear_broken(this, broken_buffer)   INTERNAL: delete internal order blocks box coordinates if top/bottom is broken   Namespace types: map   Parameters:      this (map)      broken_buffer (map)   Returns: any_bull_ob_broken, any_bear_ob_broken, broken signals are true if an according order block was broken/mitigated, broken contains the broken block(s) create_ob(id, mode, start_t, start_i, top, end_t, end_i, bottom, break_price, early_confirmation_price, config, init_plot, force_overlay)   INTERNAL: set internal order block coordinates   Parameters:      id (int)      mode (int) : 1: bullish, -1 bearish block      start_t (int)      start_i (int)      top (float)      end_t (int)      end_i (int)      bottom (float)      break_price (float)      early_confirmation_price (float)      config (OrderBlockConfig)      init_plot (bool)      force_overlay (bool)   Returns: signals are true if an according order block was broken/mitigated method align_to_profile(block, align_edge, align_break_price)   Namespace types: OrderBlock   Parameters:      block (OrderBlock)      align_edge (bool)      align_break_price (bool) method create_profile(block, opens, tops, bottoms, closes, values, resolution, vah_pc, val_pc, args, init_calculated, init_plot, force_overlay)   Namespace types: OrderBlock   Parameters:      block (OrderBlock)      opens (array)      tops (array)      bottoms (array)      closes (array)      values (array)      resolution (int)      vah_pc (float)      val_pc (float)      args (ProfileArgs type from robbatt/lib_profile/32)      init_calculated (bool)      init_plot (bool)      force_overlay (bool) method create_profile(block, resolution, vah_pc, val_pc, args, init_calculated, init_plot, force_overlay)   Namespace types: OrderBlock   Parameters:      block (OrderBlock)      resolution (int)      vah_pc (float)      val_pc (float)      args (ProfileArgs type from robbatt/lib_profile/32)      init_calculated (bool)      init_plot (bool)      force_overlay (bool) track_obs(swing_len, hh, ll, top, btm, bull_bos_alert, bull_choch_alert, bear_bos_alert, bear_choch_alert, min_block_size, max_block_size, config_bull, config_bear, init_plot, force_overlay, enabled, extend_blocks, clear_broken_buffer_before, align_edge_to_value_area, align_break_price_to_poc, profile_args_bull, profile_args_bear, use_soft_confirm, soft_confirm_offset, use_retracements_with_FVG_out)   Parameters:      swing_len (int)      hh (float)      ll (float)      top (float)      btm (float)      bull_bos_alert (bool)      bull_choch_alert (bool)      bear_bos_alert (bool)      bear_choch_alert (bool)      min_block_size (float)      max_block_size (float)      config_bull (OrderBlockConfig)      config_bear (OrderBlockConfig)      init_plot (bool)      force_overlay (bool)      enabled (bool)      extend_blocks (simple bool)      clear_broken_buffer_before (simple bool)      align_edge_to_value_area (simple bool)      align_break_price_to_poc (simple bool)      profile_args_bull (ProfileArgs type from robbatt/lib_profile/32)      profile_args_bear (ProfileArgs type from robbatt/lib_profile/32)      use_soft_confirm (simple bool)      soft_confirm_offset (float)      use_retracements_with_FVG_out (simple bool) method draw(this, config, extend_only)   Namespace types: OrderBlock   Parameters:      this (OrderBlock)      config (OrderBlockConfig)      extend_only (bool) method draw(blocks, config)   INTERNAL: plot order blocks   Namespace types: array   Parameters:      blocks (array)      config (OrderBlockConfig) method draw(blocks, config)   INTERNAL: plot order blocks   Namespace types: map   Parameters:      blocks (map)      config (OrderBlockConfig) method cleanup(this, ob_bull, ob_bear)   removes all Profiles that are older than the latest OrderBlock from this profile buffer   Namespace types: array   Parameters:      this (array type from robbatt/lib_profile/32)      ob_bull (OrderBlock)      ob_bear (OrderBlock) _plot_swing_points(mode, x, y, show_swing_points, linecolor_swings, keep_history, show_latest_swings_levels, trail_x, trail_y, trend)   INTERNAL: plot swing points   Parameters:      mode (int) : 1: bullish, -1 bearish block      x (int) : x-coordingate of swing point to plot (bar_index)      y (float) : y-coordingate of swing point to plot (price)      show_swing_points (bool) : switch to enable/disable plotting of swing point labels      linecolor_swings (color) : color for swing point labels and lates level lines      keep_history (bool) : weater to remove older swing point labels and only keep the most recent      show_latest_swings_levels (bool)      trail_x (int) : x-coordinate for latest swing point (bar_index)      trail_y (float) : y-coordinate for latest swing point (price)      trend (int) : the current trend 1: bullish, -1: bearish, to determine Strong/Weak Low/Highs _pivot_lvl(mode, trend, hhll_x, hhll, super_hhll, filter_insignificant_internal_breaks)   INTERNAL: detect whether a structural level has been broken and if it was in trend direction (BoS) or against trend direction (ChoCh), also track the latest high and low swing points   Parameters:      mode (simple int) : detect 1: bullish, -1 bearish pivot points      trend (int) : current trend direction      hhll_x (int) : x-coordinate of newly detected hh/ll (bar_index)      hhll (float) : y-coordinate of newly detected hh/ll (price)      super_hhll (float) : level/y-coordinate of superior hhll (if this is an internal structure pivot level)      filter_insignificant_internal_breaks (bool) : if true pivot points / internal structure will be ignored where the wick in trend direction is longer than the opposite (likely to push further in direction of main trend)   Returns: coordinates of internal structure that has been broken (x,y): start of structure, (trail_x, trail_y): tracking hh/ll after structure break, (bos_alert, choch_alert): signal whether a structural level has been broken _plot_structure(x, y, is_bos, is_choch, line_color, line_style, label_style, label_size, keep_history)   INTERNAL: plot structural breaks (BoS/ChoCh)   Parameters:      x (int) : x-coordinate of newly broken structure (bar_index)      y (float) : y-coordinate of newly broken structure (price)      is_bos (bool) : whether this structural break was in trend direction      is_choch (bool) : whether this structural break was against trend direction      line_color (color) : color for the line connecting the structural level and the breaking candle      line_style (string) : style (line.style_dashed/solid) for the line connecting the structural level and the breaking candle      label_style (string) : style (label.style_label_down/up) for the label above/below the line connecting the structural level and the breaking candle      label_size (string) : size (size.small/tiny) for the label above/below the line connecting the structural level and the breaking candle      keep_history (bool) : weater to remove older swing point labels and only keep the most recent structure_values(length, super_hh, super_ll, filter_insignificant_internal_breaks)   detect (and plot) structural breaks and the resulting new trend   Parameters:      length (simple int) : lookback period for swing point detection      super_hh (float) : level/y-coordinate of superior hh (for internal structure detection)      super_ll (float) : level/y-coordinate of superior ll (for internal structure detection)      filter_insignificant_internal_breaks (bool) : if true pivot points / internal structure will be ignored where the wick in trend direction is longer than the opposite (likely to push further in direction of main trend)   Returns: trend: direction 1:bullish -1:bearish, (bull_bos_alert, bull_choch_alert, top_x, top_y, trail_up_x, trail_up): whether and which level broke in a bullish direction, trailing high, (bbear_bos_alert, bear_choch_alert, tm_x, btm_y, trail_dn_x, trail_dn): same in bearish direction structure_plot(trend, bull_bos_alert, bull_choch_alert, top_x, top_y, trail_up_x, trail_up, hh, bear_bos_alert, bear_choch_alert, btm_x, btm_y, trail_dn_x, trail_dn, ll, color_bull, color_bear, show_swing_points, show_latest_swings_levels, show_bos, show_choch, line_style, label_size, keep_history)   detect (and plot) structural breaks and the resulting new trend   Parameters:      trend (int) : crrent trend 1: bullish, -1: bearish      bull_bos_alert (bool) : if there was a bullish bos alert -> plot it      bull_choch_alert (bool) : if there was a bullish choch alert -> plot it      top_x (int) : latest shwing high x      top_y (float) : latest swing high y      trail_up_x (int) : trailing high x      trail_up (float) : trailing high y      hh (float) : if there was a higher high      bear_bos_alert (bool) : if there was a bearish bos alert -> plot it      bear_choch_alert (bool) : if there was a bearish chock alert -> plot it      btm_x (int) : latest swing low x      btm_y (float) : latest swing low y      trail_dn_x (int) : trailing low x      trail_dn (float) : trailing low y      ll (float) : if there was a lower low      color_bull (color) : color for bullish BoS/ChoCh levels      color_bear (color) : color for bearish BoS/ChoCh levels      show_swing_points (bool) : whether to plot swing point labels      show_latest_swings_levels (bool) : whether to track and plot latest swing point levels with lines      show_bos (bool) : whether to plot BoS levels      show_choch (bool) : whether to plot ChoCh levels      line_style (string) : whether to plot BoS levels      label_size (string) : label size of plotted BoS/ChoCh levels      keep_history (bool) : weater to remove older swing point labels and only keep the most recent structure(length, color_bull, color_bear, super_hh, super_ll, filter_insignificant_internal_breaks, show_swing_points, show_latest_swings_levels, show_bos, show_choch, line_style, label_size, keep_history, enabled)   detect (and plot) structural breaks and the resulting new trend   Parameters:      length (simple int) : lookback period for swing point detection      color_bull (color) : color for bullish BoS/ChoCh levels      color_bear (color) : color for bearish BoS/ChoCh levels      super_hh (float) : level/y-coordinate of superior hh (for internal structure detection)      super_ll (float) : level/y-coordinate of superior ll (for internal structure detection)      filter_insignificant_internal_breaks (bool) : if true pivot points / internal structure will be ignored where the wick in trend direction is longer than the opposite (likely to push further in direction of main trend)      show_swing_points (bool) : whether to plot swing point labels      show_latest_swings_levels (bool) : whether to track and plot latest swing point levels with lines      show_bos (bool) : whether to plot BoS levels      show_choch (bool) : whether to plot ChoCh levels      line_style (string) : whether to plot BoS levels      label_size (string) : label size of plotted BoS/ChoCh levels      keep_history (bool) : weater to remove older swing point labels and only keep the most recent      enabled (bool) _check_equal_level(mode, len, eq_threshold, enabled)   INTERNAL: detect equal levels (double top/bottom)   Parameters:      mode (int) : detect 1: bullish/high, -1 bearish/low pivot points      len (int) : lookback period for equal level (swing point) detection      eq_threshold (float) : maximum price offset for a level to be considered equal      enabled (bool)   Returns: eq_alert whether an equal level was detected and coordinates of the first and the second level/swing point _plot_equal_level(show_eq, x1, y1, x2, y2, label_txt, label_style, label_size, line_color, line_style, keep_history)   INTERNAL: plot equal levels (double top/bottom)   Parameters:      show_eq (bool) : whether to plot the level or not      x1 (int) : x-coordinate of the first level / swing point      y1 (float) : y-coordinate of the first level / swing point      x2 (int) : x-coordinate of the second level / swing point      y2 (float) : y-coordinate of the second level / swing point      label_txt (string) : text for the label above/below the line connecting the equal levels      label_style (string) : style (label.style_label_down/up) for the label above/below the line connecting the equal levels      label_size (string) : size (size.tiny) for the label above/below the line connecting the equal levels      line_color (color) : color for the line connecting the equal levels (and it's label)      line_style (string) : style (line.style_dotted) for the line connecting the equal levels      keep_history (bool) : weater to remove older swing point labels and only keep the most recent equal_levels_values(len, threshold, enabled)   detect (and plot) equal levels (double top/bottom), returns coordinates   Parameters:      len (int) : lookback period for equal level (swing point) detection      threshold (float) : maximum price offset for a level to be considered equal      enabled (bool) : whether detection is enabled   Returns: (eqh_alert, eqh_x1, eqh_y1, eqh_x2, eqh_y2) whether an equal high was detected and coordinates of the first and the second level/swing point, (eql_alert, eql_x1, eql_y1, eql_x2, eql_y2) same for equal lows equal_levels_plot(eqh_x1, eqh_y1, eqh_x2, eqh_y2, eql_x1, eql_y1, eql_x2, eql_y2, color_eqh, color_eql, show, keep_history)   detect (and plot) equal levels (double top/bottom), returns coordinates   Parameters:      eqh_x1 (int) : coordinates of first point of equal high      eqh_y1 (float) : coordinates of first point of equal high      eqh_x2 (int) : coordinates of second point of equal high      eqh_y2 (float) : coordinates of second point of equal high      eql_x1 (int) : coordinates of first point of equal low      eql_y1 (float) : coordinates of first point of equal low      eql_x2 (int) : coordinates of second point of equal low      eql_y2 (float) : coordinates of second point of equal low      color_eqh (color) : color for the line connecting the equal highs (and it's label)      color_eql (color) : color for the line connecting the equal lows (and it's label)      show (bool) : whether plotting is enabled      keep_history (bool) : weater to remove older swing point labels and only keep the most recent   Returns: (eqh_alert, eqh_x1, eqh_y1, eqh_x2, eqh_y2) whether an equal high was detected and coordinates of the first and the second level/swing point, (eql_alert, eql_x1, eql_y1, eql_x2, eql_y2) same for equal lows equal_levels(len, threshold, color_eqh, color_eql, enabled, show, keep_history)   detect (and plot) equal levels (double top/bottom)   Parameters:      len (int) : lookback period for equal level (swing point) detection      threshold (float) : maximum price offset for a level to be considered equal      color_eqh (color) : color for the line connecting the equal highs (and it's label)      color_eql (color) : color for the line connecting the equal lows (and it's label)      enabled (bool) : whether detection is enabled      show (bool) : whether plotting is enabled      keep_history (bool) : weater to remove older swing point labels and only keep the most recent   Returns: (eqh_alert) whether an equal high was detected, (eql_alert) same for equal lows _detect_fvg(mode, enabled, o, h, l, c, filter_insignificant_fvgs, change_tf)   INTERNAL: detect FVG (fair value gap)   Parameters:      mode (int) : detect 1: bullish, -1 bearish gaps      enabled (bool) : whether detection is enabled      o (float) : reference source open      h (float) : reference source high      l (float) : reference source low      c (float) : reference source close      filter_insignificant_fvgs (bool) : whether to calculate and filter small/insignificant gaps      change_tf (bool) : signal when the previous reference timeframe closed, triggers new calculation   Returns: whether a new FVG was detected and its top/mid/bottom levels _clear_broken_fvg(mode, upper_boxes, lower_boxes)   INTERNAL: clear mitigated FVGs (fair value gaps)   Parameters:      mode (int) : detect 1: bullish, -1 bearish gaps      upper_boxes (array) : array that stores the upper parts of the FVG boxes      lower_boxes (array) : array that stores the lower parts of the FVG boxes _plot_fvg(mode, show, top, mid, btm, border_color, extend_box)   INTERNAL: plot (and clear broken) FVG (fair value gap)   Parameters:      mode (int) : plot 1: bullish, -1 bearish gap      show (bool) : whether plotting is enabled      top (float) : top level of fvg      mid (float) : center level of fvg      btm (float) : bottom level of fvg      border_color (color) : color for the FVG box      extend_box (int) : how many bars into the future the FVG box should be extended after detection fvgs_values(o, h, l, c, filter_insignificant_fvgs, change_tf, enabled)   detect (and plot / clear broken) FVGs (fair value gaps), and return alerts and level values   Parameters:      o (float) : reference source open      h (float) : reference source high      l (float) : reference source low      c (float) : reference source close      filter_insignificant_fvgs (bool) : whether to calculate and filter small/insignificant gaps      change_tf (bool) : signal when the previous reference timeframe closed, triggers new calculation      enabled (bool) : whether detection is enabled   Returns: (bullish_fvg_alert, bull_top, bull_mid, bull_btm): whether a new bullish FVG was detected and its top/mid/bottom levels, (bearish_fvg_alert, bear_top, bear_mid, bear_btm): same for bearish FVGs fvgs_plot(bullish_fvg_alert, bull_top, bull_mid, bull_btm, bearish_fvg_alert, bear_top, bear_mid, bear_btm, color_bull, color_bear, extend_box, show)   Parameters:      bullish_fvg_alert (bool)      bull_top (float)      bull_mid (float)      bull_btm (float)      bearish_fvg_alert (bool)      bear_top (float)      bear_mid (float)      bear_btm (float)      color_bull (color) : color for bullish FVG boxes      color_bear (color) : color for bearish FVG boxes      extend_box (int) : how many bars into the future the FVG box should be extended after detection      show (bool) : whether plotting is enabled   Returns: (bullish_fvg_alert, bull_top, bull_mid, bull_btm): whether a new bullish FVG was detected and its top/mid/bottom levels, (bearish_fvg_alert, bear_top, bear_mid, bear_btm): same for bearish FVGs fvgs(o, h, l, c, filter_insignificant_fvgs, change_tf, color_bull, color_bear, extend_box, enabled, show)   detect (and plot / clear broken) FVGs (fair value gaps)   Parameters:      o (float) : reference source open      h (float) : reference source high      l (float) : reference source low      c (float) : reference source close      filter_insignificant_fvgs (bool) : whether to calculate and filter small/insignificant gaps      change_tf (bool) : signal when the previous reference timeframe closed, triggers new calculation      color_bull (color) : color for bullish FVG boxes      color_bear (color) : color for bearish FVG boxes      extend_box (int) : how many bars into the future the FVG box should be extended after detection      enabled (bool) : whether detection is enabled      show (bool) : whether plotting is enabled   Returns: (bullish_fvg_alert): whether a new bullish FVG was detected, (bearish_fvg_alert): same for bearish FVGs OrderBlock   Fields:      id (series int)      dir (series int)      left_top (chart.point)      right_bottom (chart.point)      break_price (series float)      early_confirmation_price (series float)      ltf_high (array)      ltf_low (array)      ltf_volume (array)      plot (Box type from robbatt/lib_plot_objects/49)      profile (Profile type from robbatt/lib_profile/32)      trailing (series bool)      extending (series bool)      awaiting_confirmation (series bool)      touched_break_price_before_confirmation (series bool)      soft_confirmed (series bool)      has_fvg_out (series bool)      hidden (series bool)      broken (series bool) OrderBlockConfig   Fields:      show (series bool)      show_last (series int)      show_id (series bool)      show_profile (series bool)      args (BoxArgs type from robbatt/lib_plot_objects/49)      txt (series string)      txt_args (BoxTextArgs type from robbatt/lib_plot_objects/49)      delete_when_broken (series bool)      broken_args (BoxArgs type from robbatt/lib_plot_objects/49)      broken_txt (series string)      broken_txt_args (BoxTextArgs type from robbatt/lib_plot_objects/49)      broken_profile_args (ProfileArgs type from robbatt/lib_profile/32)      use_profile (series bool)      profile_args (ProfileArgs type from robbatt/lib_profile/32)
Pine Script® library
by robbatt
15