Get started

Search in scripts for "bar"

MSFA_LibraryLibrary "MSFA_library" TODO: add library description here getDecimals()   Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price getPipSize(multiplier)   Calculates the pip size of the current market   Parameters:      multiplier (int) : The mintick point multiplier (1 by default, 10 for FX/Crypto/CFD but can be used to override when certain markets require)   Returns: The pip size for the current market truncate(number, decimalPlaces)   Truncates (cuts) excess decimal places   Parameters:      number (float) : The number to truncate      decimalPlaces (simple float) : (default=2) The number of decimal places to truncate to   Returns: The given number truncated to the given decimalPlaces toWhole(number)   Converts pips into whole numbers   Parameters:      number (float) : The pip number to convert into a whole number   Returns: The converted number toPips(number)   Converts whole numbers back into pips   Parameters:      number (float) : The whole number to convert into pips   Returns: The converted number getPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period   Parameters:      value1 (float) : The first value to reference      value2 (float) : The second value to reference      lookback (int) : The lookback period to analyze   Returns: The percent change over the two values and lookback period random(minRange, maxRange)   Wichmann–Hill Pseudo-Random Number Generator   Parameters:      minRange (float) : The smallest possible number (default: 0)      maxRange (float) : The largest possible number (default: 1)   Returns: A random number between minRange and maxRange bullFib(priceLow, priceHigh, fibRatio)   Calculates a bullish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio)   Calculates a bearish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(length, maType)   Gets a Moving Average based on type (! MUST BE CALLED ON EVERY TICK TO BE ACCURATE, don't place in scopes)   Parameters:      length (simple int) : The MA period      maType (string) : The type of MA   Returns: A moving average with the given parameters barsAboveMA(lookback, ma)   Counts how many candles are above the MA   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(lookback, ma)   Counts how many candles are below the MA   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently (based on closing prices)   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA (based on closing prices) getPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      lookback (int) : The lookback period to look back over      direction (int) : The color of the bar to count (1 = Green, -1 = Red)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize()   Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize()   Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize()   Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent()   Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(fib, colorMatch)   Checks if the current bar is a hammer candle based on the given parameters   Parameters:      fib (float) : (default=0.382) The fib to base candle body on      colorMatch (bool) : (default=false) Does the candle need to be green? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(fib, colorMatch)   Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      fib (float) : (default=0.382) The fib to base candle body on      colorMatch (bool) : (default=false) Does the candle need to be red? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(wickSize, bodySize)   Checks if the current bar is a doji candle based on the given parameters   Parameters:      wickSize (float) : (default=2) The maximum top wick size compared to the bottom (and vice versa)      bodySize (float) : (default=0.05) The maximum body size as a percentage compared to the entire candle size   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bullish engulfing candle   Parameters:      allowance (float) : (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      rejectionWickSize (float) : (default=disabled) The maximum rejection wick size compared to the body as a percentage      engulfWick (bool) : (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bearish engulfing candle   Parameters:      allowance (float) : (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      rejectionWickSize (float) : (default=disabled) The maximum rejection wick size compared to the body as a percentage      engulfWick (bool) : (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar()   Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar()   Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session   Parameters:      sess (simple string) : The session to check      useFilter (bool) : (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session barOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session   Parameters:      sess (simple string) : The session to check      useFilter (bool) : (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range   Parameters:      startTime (int) : The UNIX date timestamp to begin searching from      endTime (int) : the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze   Parameters:      monday (bool) : Should the script analyze this day? (true/false)      tuesday (bool) : Should the script analyze this day? (true/false)      wednesday (bool) : Should the script analyze this day? (true/false)      thursday (bool) : Should the script analyze this day? (true/false)      friday (bool) : Should the script analyze this day? (true/false)      saturday (bool) : Should the script analyze this day? (true/false)      sunday (bool) : Should the script analyze this day? (true/false)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(atrValue, maxSize)   Parameters:      atrValue (float)      maxSize (float) tradeCount()   Calculate total trade count   Returns: Total closed trade count isLong()   Check if we're currently in a long trade   Returns: True if our position size is positive isShort()   Check if we're currently in a short trade   Returns: True if our position size is negative isFlat()   Check if we're currentlyflat   Returns: True if our position size is zero wonTrade()   Check if this bar falls after a winning trade   Returns: True if we just won a trade lostTrade()   Check if this bar falls after a losing trade   Returns: True if we just lost a trade maxDrawdownRealized()   Gets the max drawdown based on closed trades (ie. realized P&L). The strategy tester displays max drawdown as open P&L (unrealized).   Returns: The max drawdown based on closed trades (ie. realized P&L). The strategy tester displays max drawdown as open P&L (unrealized). totalPipReturn()   Gets the total amount of pips won/lost (as a whole number)   Returns: Total amount of pips won/lost (as a whole number) longWinCount()   Count how many winning long trades we've had   Returns: Long win count shortWinCount()   Count how many winning short trades we've had   Returns: Short win count longLossCount()   Count how many losing long trades we've had   Returns: Long loss count shortLossCount()   Count how many losing short trades we've had   Returns: Short loss count breakEvenCount(allowanceTicks)   Count how many break-even trades we've had   Parameters:      allowanceTicks (float) : Optional - how many ticks to allow between entry & exit price (default 0)   Returns: Break-even count longCount()   Count how many long trades we've taken   Returns: Long trade count shortCount()   Count how many short trades we've taken   Returns: Short trade count longWinPercent()   Calculate win rate of long trades   Returns: Long win rate (0-100) shortWinPercent()   Calculate win rate of short trades   Returns: Short win rate (0-100) breakEvenPercent(allowanceTicks)   Calculate break even rate of all trades   Parameters:      allowanceTicks (float) : Optional - how many ticks to allow between entry & exit price (default 0)   Returns: Break-even win rate (0-100) averageRR()   Calculate average risk:reward   Returns: Average winning trade divided by average losing trade unitsToLots(units)   (Forex) Convert the given unit count to lots (multiples of 100,000)   Parameters:      units (float) : The units to convert into lots   Returns: Units converted to nearest lot size (as float) skipTradeMonteCarlo(chance, debug)   Checks to see if trade should be skipped to emulate rudimentary Monte Carlo simulation   Parameters:      chance (float) : The chance to skip a trade (0-1 or 0-100, function will normalize to 0-1)      debug (bool) : Whether or not to display a label informing of the trade skip   Returns: True if the trade is skipped, false if it's not skipped (idea being to include this function in entry condition validation checks) fillCell(tableID, column, row, title, value, bgcolor, txtcolor, tooltip)   This updates the given table's cell with the given values   Parameters:      tableID (table) : The table ID to update      column (int) : The column to update      row (int) : The row to update      title (string) : The title of this cell      value (string) : The value of this cell      bgcolor (color) : The background color of this cell      txtcolor (color) : The text color of this cell      tooltip (string)   Returns: Nothing.
Pine Script® library
by hphuc0212
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
1
MirPapa_Library_ICTLibrary "MirPapa_Library_ICT" GetHTFoffsetToLTFoffset(_offset, _chartTf, _htfTf)   GetHTFoffsetToLTFoffset @description Adjust an HTF offset to an LTF offset by calculating the ratio of timeframes.   Parameters:      _offset (int) : int The HTF bar offset (0 means current HTF bar).      _chartTf (string) : string The current chart’s timeframe (e.g., "5", "15", "1D").      _htfTf (string) : string The High Time Frame string (e.g., "60", "1D"). @return int The corresponding LTF bar index. Returns 0 if the result is negative. IsConditionState(_type, _isBull, _level, _open, _close, _open1, _close1, _low1, _low2, _low3, _low4, _high1, _high2, _high3, _high4)   IsConditionState @description Evaluate a condition state based on type for COB, FVG, or FOB. Overloaded: first signature handles COB, second handles FVG/FOB.   Parameters:      _type (string) : string Condition type ("cob", "fvg", "fob").      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _level (int) : int Swing level (only used for COB).      _open (float) : float Current bar open price (only for COB).      _close (float) : float Current bar close price (only for COB).      _open1 (float) : float Previous bar open price (only for COB).      _close1 (float) : float Previous bar close price (only for COB).      _low1 (float) : float Low 1 bar ago (only for COB).      _low2 (float) : float Low 2 bars ago (only for COB).      _low3 (float) : float Low 3 bars ago (only for COB).      _low4 (float) : float Low 4 bars ago (only for COB).      _high1 (float) : float High 1 bar ago (only for COB).      _high2 (float) : float High 2 bars ago (only for COB).      _high3 (float) : float High 3 bars ago (only for COB).      _high4 (float) : float High 4 bars ago (only for COB). @return bool True if the specified condition is met, false otherwise. IsConditionState(_type, _isBull, _pricePrev, _priceNow)   IsConditionState @description Evaluate FVG or FOB condition based on price movement.   Parameters:      _type (string) : string Condition type ("fvg", "fob").      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _pricePrev (float) : float Previous price (for FVG/FOB).      _priceNow (float) : float Current price (for FVG/FOB). @return bool True if the specified condition is met, false otherwise. IsSwingHighLow(_isBull, _level, _open, _close, _open1, _close1, _low1, _low2, _low3, _low4, _high1, _high2, _high3, _high4)   IsSwingHighLow @description Public wrapper for isSwingHighLow.   Parameters:      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _level (int) : int Swing level (1 or 2).      _open (float) : float Current bar open price.      _close (float) : float Current bar close price.      _open1 (float) : float Previous bar open price.      _close1 (float) : float Previous bar close price.      _low1 (float) : float Low 1 bar ago.      _low2 (float) : float Low 2 bars ago.      _low3 (float) : float Low 3 bars ago.      _low4 (float) : float Low 4 bars ago.      _high1 (float) : float High 1 bar ago.      _high2 (float) : float High 2 bars ago.      _high3 (float) : float High 3 bars ago.      _high4 (float) : float High 4 bars ago. @return bool True if swing condition is met, false otherwise. AddBox(_left, _right, _top, _bot, _xloc, _colorBG, _colorBD)   AddBox @description Draw a rectangular box on the chart with specified coordinates and colors.   Parameters:      _left (int) : int Left bar index for the box.      _right (int) : int Right bar index for the box.      _top (float) : float Top price coordinate for the box.      _bot (float) : float Bottom price coordinate for the box.      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _colorBG (color) : color Background color for the box.      _colorBD (color) : color Border color for the box. @return box Returns the created box object. Addline(_x, _y, _xloc, _color, _width)   Addline @description Draw a vertical or horizontal line at specified coordinates.   Parameters:      _x (int) : int X-coordinate for start (bar index).      _y (int) : float Y-coordinate for start (price).      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _color (color) : color Line color.      _width (int) : int Line width. @return line Returns the created line object. Addline(_x, _y, _xloc, _color, _width)   Parameters:      _x (int)      _y (float)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (int)      _x2 (int)      _y2 (int)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (int)      _x2 (int)      _y2 (float)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (float)      _x2 (int)      _y2 (int)      _xloc (string)      _color (color)      _width (int) Addline(_x1, _y1, _x2, _y2, _xloc, _color, _width)   Parameters:      _x1 (int)      _y1 (float)      _x2 (int)      _y2 (float)      _xloc (string)      _color (color)      _width (int) AddlineMid(_type, _left, _right, _top, _bot, _xloc, _color, _width)   AddlineMid @description Draw a midline between top and bottom for FVG or FOB types.   Parameters:      _type (string) : string Type identifier: "fvg" or "fob".      _left (int) : int Left bar index for midline start.      _right (int) : int Right bar index for midline end.      _top (float) : float Top price of the region.      _bot (float) : float Bottom price of the region.      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _color (color) : color Line color.      _width (int) : int Line width. @return line or na Returns the created line or na if type is not recognized. GetHtfFromLabel(_label)   GetHtfFromLabel @description Convert a Korean HTF label into a Pine Script timeframe string via handler library.   Parameters:      _label (string) : string The Korean label (e.g., "5분", "1시간"). @return string Returns the corresponding Pine Script timeframe (e.g., "5", "60"). IsChartTFcomparisonHTF(_chartTf, _htfTf)   IsChartTFcomparisonHTF @description Determine whether a given HTF is greater than or equal to the current chart timeframe.   Parameters:      _chartTf (string) : string Current chart timeframe (e.g., "5", "15", "1D").      _htfTf (string) : string HTF timeframe (e.g., "60", "1D"). @return bool True if HTF ≥ chartTF, false otherwise. CreateBoxData(_type, _isBull, _useLine, _top, _bot, _xloc, _colorBG, _colorBD, _offset, _htfTf, htfBarIdx, _basePoint)   CreateBoxData @description Create and draw a box and optional midline for given type and parameters. Returns success flag and BoxData.   Parameters:      _type (string) : string Type identifier: "fvg", "fob", "cob", or "sweep".      _isBull (bool) : bool Direction flag: true for bullish, false for bearish.      _useLine (bool) : bool Whether to draw a midline inside the box.      _top (float) : float Top price of the box region.      _bot (float) : float Bottom price of the box region.      _xloc (string) : string X-axis location type (e.g., xloc.bar_index).      _colorBG (color) : color Background color for the box.      _colorBD (color) : color Border color for the box.      _offset (int) : int HTF bar offset (0 means current HTF bar).      _htfTf (string) : string HTF timeframe string (e.g., "60", "1D").      htfBarIdx (int) : int HTF bar_index (passed from HTF request).      _basePoint (float) : float Base point for breakout checks. @return tuple(bool, BoxData) Returns a boolean indicating success and the created BoxData struct. ProcessBoxDatas(_datas, _useMidLine, _closeCount, _colorClose)   ProcessBoxDatas @description Process an array of BoxData structs: extend, record volume, update stage, and finalize boxes.   Parameters:      _datas (array) : array Array of BoxData objects to process.      _useMidLine (bool) : bool Whether to update the midline endpoint.      _closeCount (int) : int Number of touches required to close the box.      _colorClose (color) : color Color to apply when a box closes. @return void No return value; updates are in-place. BoxData   Fields:      _isActive (series bool)      _isBull (series bool)      _box (series box)      _line (series line)      _basePoint (series float)      _boxTop (series float)      _boxBot (series float)      _stage (series int)      _isStay (series bool)      _volBuy (series float)      _volSell (series float)      _result (series string) LineData   Fields:      _isActive (series bool)      _isBull (series bool)      _line (series line)      _basePoint (series float)      _stage (series int)      _isStay (series bool)      _result (series string)
Pine Script® library
by goodia
LinearRegressionLibrary "LinearRegression" Calculates a variety of linear regression and deviation types, with optional emphasis weighting. Additionally, multiple of slope and Pearson’s R calculations. calcSlope(_src, _len, _condition)   Calculates the slope of a linear regression over the specified length.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period for the linear regression.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast for efficiency.   Returns: (float) The slope of the linear regression. calcReg(_src, _len, _condition)   Calculates a basic linear regression, returning y1, y2, slope, and average.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) An array of 4 values: . calcRegStandard(_src, _len, _emphasis, _condition)   Calculates an Standard linear regression with optional emphasis.   Parameters:      _src (float) : (series float) The source data series.      _len (int) : (int) The length of the lookback period.      _emphasis (float) : (float) The emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegRidge(_src, _len, lambda, _emphasis, _condition)   Calculates a ridge regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      lambda (float) : (float) The ridge regularization parameter.      _emphasis (float) : (float) The emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegLasso(_src, _len, lambda, _emphasis, _condition)   Calculates a Lasso regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      lambda (float) : (float) The Lasso regularization parameter.      _emphasis (float) : (float) The emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcElasticNetLinReg(_src, _len, lambda1, lambda2, _emphasis, _condition)   Calculates an Elastic Net regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      lambda1 (float) : (float) L1 regularization parameter (Lasso).      lambda2 (float) : (float) L2 regularization parameter (Ridge).      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegHuber(_src, _len, delta, iterations, _emphasis, _condition)   Calculates a Huber regression using Iteratively Reweighted Least Squares (IRLS).   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      delta (float) : (float) Huber threshold parameter.      iterations (int) : (int) Number of IRLS iterations.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegLAD(_src, _len, iterations, _emphasis, _condition)   Calculates a Least Absolute Deviations (LAD) regression via IRLS.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      iterations (int) : (int) Number of IRLS iterations for LAD.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRegBayesian(_src, _len, priorMean, priorSpan, sigma, _emphasis, _condition)   Calculates a Bayesian linear regression with optional emphasis.   Parameters:      _src (float) : (float) The source data series.      _len (int) : (int) The length of the lookback period.      priorMean (float) : (float) The prior mean for the slope.      priorSpan (float) : (float) The prior variance (or span) for the slope.      sigma (float) : (float) The assumed standard deviation of residuals.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: (float ) . calcRFromLinReg(_src, _len, _slope, _average, _y1, _condition)   Calculates the Pearson correlation coefficient (R) based on linear regression parameters.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _average (float) : (float) The average value of the source data series.      _y1 (float) : (float) The starting point (y-intercept of the oldest bar) for the linear regression.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast for efficiency.   Returns: (float) The Pearson correlation coefficient (R) adjusted for the direction of the slope. calcRFromSource(_src, _len, _condition)   Calculates the correlation coefficient (R) using a specified length and source data.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast for efficiency.   Returns: (float) The correlation coefficient (R). calcSlopeLengthZero(_src, _len, _minLen, _step, _condition)   Identifies the length at which the slope is flattest (closest to zero).   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length to consider (minimum of 2).      _minLen (int) : (int) The minimum length to start from (cannot exceed the max length).      _step (int) : (int) The increment step for lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the slope is flattest. calcSlopeLengthHighest(_src, _len, _minLen, _step, _condition)   Identifies the length at which the slope is highest.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the slope is highest. calcSlopeLengthLowest(_src, _len, _minLen, _step, _condition)   Identifies the length at which the slope is lowest.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the slope is lowest. calcSlopeLengthAbsolute(_src, _len, _minLen, _step, _condition)   Identifies the length at which the absolute slope value is highest.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length at which the absolute slope value is highest. calcRLengthZero(_src, _len, _minLen, _step, _condition)   Identifies the length with the lowest absolute R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the lowest absolute R value. calcRLengthHighest(_src, _len, _minLen, _step, _condition)   Identifies the length with the highest R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the highest R value. calcRLengthLowest(_src, _len, _minLen, _step, _condition)   Identifies the length with the lowest R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the lowest R value. calcRLengthAbsolute(_src, _len, _minLen, _step, _condition)   Identifies the length with the highest absolute R value.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The maximum lookback length (minimum of 2).      _minLen (int) : (int) The minimum length to start from.      _step (int) : (int) The step for incrementing lengths.      _condition (bool) : (bool) Flag to enable calculation. Set to true to calculate on every bar; otherwise, set to barstate.islast.   Returns: (int) The length with the highest absolute R value. calcDevReverse(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the regressive linear deviation in reverse order, with optional emphasis on recent data.   Parameters:      _src (float) : (float) The source data.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevForward(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the progressive linear deviation in forward order (oldest to most recent bar), with optional emphasis.   Parameters:      _src (float) : (float) The source data array, where _src is oldest and _src is most recent.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept of the linear regression (value at the most recent bar, adjusted by slope).      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevBalanced(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the balanced linear deviation with optional emphasis on recent or older data.   Parameters:      _src (float) : (float) Source data array, where _src is the most recent and _src is the oldest.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept of the linear regression (value at the oldest bar).      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevMean(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the mean absolute deviation from a forward-applied linear trend (oldest to most recent), with optional emphasis.   Parameters:      _src (float) : (float) The source data array, where _src is the most recent and _src is the oldest.      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevMedian(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates the median absolute deviation with optional emphasis on recent data.   Parameters:      _src (float) : (float) The source data array (index 0 = oldest, index _len - 1 = most recent).      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: calcDevPercent(_y1, _inputDev, _condition)   Calculates the percent deviation from a given value and a specified percentage.   Parameters:      _y1 (float) : (float) The base value from which to calculate deviation.      _inputDev (float) : (float) The deviation percentage.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevFitted(_len, _slope, _y1, _emphasis, _condition)   Calculates the weighted fitted deviation based on high and low series data, showing max deviation, with optional emphasis.   Parameters:      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The Y-intercept (oldest bar) of the linear regression.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcDevATR(_src, _len, _slope, _y1, _inputDev, _emphasis, _condition)   Calculates an ATR-style deviation with optional emphasis on recent data.   Parameters:      _src (float) : (float) The source data (typically close).      _len (int) : (int) The length of the lookback period.      _slope (float) : (float) The slope of the linear regression.      _y1 (float) : (float) The Y-intercept (oldest bar) of the linear regression.      _inputDev (float) : (float) The input deviation multiplier.      _emphasis (float) : (float) Emphasis factor: 0 for equal weight; >0 emphasizes recent bars; <0 emphasizes older bars.      _condition (bool) : (bool) Flag to enable calculation (true = calculate).   Returns: A 2-element tuple: . calcPricePositionPercent(_top, _bot, _src)   Calculates the percent position of a price within a linear regression channel. Top=100%, Bottom=0%.   Parameters:      _top (float) : (float) The top (positive) deviation, corresponding to 100%.      _bot (float) : (float) The bottom (negative) deviation, corresponding to 0%.      _src (float) : (float) The source price.   Returns: (float) The percent position within the channel. plotLinReg(_len, _y1, _y2, _slope, _devTop, _devBot, _scaleTypeLog, _lineWidth, _extendLines, _channelStyle, _colorFill, _colUpLine, _colDnLine, _colUpFill, _colDnFill)   Plots the linear regression line and its deviations, with configurable styles and fill.   Parameters:      _len (int) : (int) The lookback period for the linear regression.      _y1 (float) : (float) The starting y-value of the regression line.      _y2 (float) : (float) The ending y-value of the regression line.      _slope (float) : (float) The slope of the regression line (used to determine line color).      _devTop (float) : (float) The top deviation to add to the line.      _devBot (float) : (float) The bottom deviation to subtract from the line.      _scaleTypeLog (bool) : (bool) Use a log scale if true; otherwise, linear scale.      _lineWidth (int) : (int) The width of the plotted lines.      _extendLines (string) : (string) How lines should extend (none, left, right, both).      _channelStyle (string) : (string) The style of the channel lines (solid, dashed, dotted).      _colorFill (bool) : (bool) Whether to fill the space between the top and bottom deviation lines.      _colUpLine (color) : (color) Line color when slope is positive.      _colDnLine (color) : (color) Line color when slope is negative.      _colUpFill (color) : (color) Fill color when slope is positive.      _colDnFill (color) : (color) Fill color when slope is negative.
Pine Script® library
by TanHef
2
Exposure Oscillator (Cumulative 0 to ±100%) Exposure Oscillator (Cumulative 0 to ±100%) This Pine Script indicator plots an "Exposure Oscillator" on the chart, which tracks the cumulative market exposure from a range of technical buy and sell signals. The exposure is measured on a scale from -100% (maximum short exposure) to +100% (maximum long exposure), helping traders assess the strength of their position in the market. It provides an intuitive visual cue to aid decision-making for trend-following strategies. Buy Signals (Increase Exposure Score by +10%) Buy Signal 1 (Cross Above 21 EMA): This signal is triggered when the price crosses above the 21-period Exponential Moving Average (EMA), where the current bar closes above the EMA21, and the previous bar closed below the EMA21. This indicates a potential upward price movement as the market shifts into a bullish trend. buySignal1 = ta.crossover(close, ema21) Buy Signal 2 (Trending Above 21 EMA): This signal is triggered when the price closes above the 21-period EMA for each of the last 5 bars, indicating a sustained bullish trend. It confirms that the price is consistently above the EMA21 for a significant period. buySignal2 = ta.barssince(close <= ema21) > 5 Buy Signal 3 (Living Above 21 EMA): This signal is triggered when the price has closed above the 21-period EMA for each of the last 15 bars, demonstrating a strong, prolonged uptrend. buySignal3 = ta.barssince(close <= ema21) > 15 Buy Signal 4 (Cross Above 50 SMA): This signal is triggered when the price crosses above the 50-period Simple Moving Average (SMA), where the current bar closes above the 50 SMA, and the previous bar closed below it. It indicates a shift toward bullish momentum. buySignal4 = ta.crossover(close, sma50) Buy Signal 5 (Cross Above 200 SMA): This signal is triggered when the price crosses above the 200-period Simple Moving Average (SMA), where the current bar closes above the 200 SMA, and the previous bar closed below it. This suggests a long-term bullish trend. buySignal5 = ta.crossover(close, sma200) Buy Signal 6 (Low Above 50 SMA): This signal is true when the lowest price of the current bar is above the 50-period SMA, indicating strong bullish pressure as the price maintains itself above the moving average. buySignal6 = low > sma50 Buy Signal 7 (Accumulation Day): An accumulation day occurs when the closing price is in the upper half of the daily range (greater than 50%) and the volume is larger than the previous bar's volume, suggesting buying pressure and accumulation. buySignal7 = (close - low) / (high - low) > 0.5 and volume > volume Buy Signal 8 (Higher High): This signal occurs when the current bar’s high exceeds the highest high of the previous 14 bars, indicating a breakout or strong upward momentum. buySignal8 = high > ta.highest(high, 14) Buy Signal 9 (Key Reversal Bar): This signal is generated when the stock opens below the low of the previous bar but rallies to close above the previous bar’s high, signaling a potential reversal from bearish to bullish. buySignal9 = open < low and close > high Buy Signal 10 (Distribution Day Fall Off): This signal is triggered when a distribution day (a day with high volume and a close near the low of the range) "falls off" the rolling 25-bar period, indicating the end of a bearish trend or selling pressure. buySignal10 = ta.barssince(close < sma50 and close < sma50) > 25 Sell Signals (Decrease Exposure Score by -10%) Sell Signal 1 (Cross Below 21 EMA): This signal is triggered when the price crosses below the 21-period Exponential Moving Average (EMA), where the current bar closes below the EMA21, and the previous bar closed above it. It suggests that the market may be shifting from a bullish trend to a bearish trend. sellSignal1 = ta.crossunder(close, ema21) Sell Signal 2 (Trending Below 21 EMA): This signal is triggered when the price closes below the 21-period EMA for each of the last 5 bars, indicating a sustained bearish trend. sellSignal2 = ta.barssince(close >= ema21) > 5 Sell Signal 3 (Living Below 21 EMA): This signal is triggered when the price has closed below the 21-period EMA for each of the last 15 bars, suggesting a strong downtrend. sellSignal3 = ta.barssince(close >= ema21) > 15 Sell Signal 4 (Cross Below 50 SMA): This signal is triggered when the price crosses below the 50-period Simple Moving Average (SMA), where the current bar closes below the 50 SMA, and the previous bar closed above it. It indicates the start of a bearish trend. sellSignal4 = ta.crossunder(close, sma50) Sell Signal 5 (Cross Below 200 SMA): This signal is triggered when the price crosses below the 200-period Simple Moving Average (SMA), where the current bar closes below the 200 SMA, and the previous bar closed above it. It indicates a long-term bearish trend. sellSignal5 = ta.crossunder(close, sma200) Sell Signal 6 (High Below 50 SMA): This signal is true when the highest price of the current bar is below the 50-period SMA, indicating weak bullishness or a potential bearish reversal. sellSignal6 = high < sma50 Sell Signal 7 (Distribution Day): A distribution day is identified when the closing range of a bar is less than 50% and the volume is larger than the previous bar's volume, suggesting that selling pressure is increasing. sellSignal7 = (close - low) / (high - low) < 0.5 and volume > volume Sell Signal 8 (Lower Low): This signal occurs when the current bar's low is less than the lowest low of the previous 14 bars, indicating a breakdown or strong downward momentum. sellSignal8 = low < ta.lowest(low, 14) Sell Signal 9 (Downside Reversal Bar): A downside reversal bar occurs when the stock opens above the previous bar's high but falls to close below the previous bar’s low, signaling a reversal from bullish to bearish. sellSignal9 = open > high and close < low Sell Signal 10 (Distribution Cluster): This signal is triggered when a distribution day occurs three times in the rolling 7-bar period, indicating significant selling pressure. sellSignal10 = ta.valuewhen((close < low) and volume > volume , 1, 7) >= 3 Theme Mode: Users can select the theme mode (Auto, Dark, or Light) to match the chart's background or to manually choose a light or dark theme for the oscillator's appearance. Exposure Score Calculation: The script calculates a cumulative exposure score based on a series of buy and sell signals. Buy signals increase the exposure score, while sell signals decrease it. Each signal impacts the score by ±10%. Signal Conditions: The buy and sell signals are derived from multiple conditions, including crossovers with moving averages (EMA21, SMA50, SMA200), trend behavior, and price/volume analysis. Oscillator Visualization: The exposure score is visualized as a line on the chart, changing color based on whether the exposure is positive (long position) or negative (short position). It is limited to the range of -100% to +100%. Position Type: The indicator also indicates the position type based on the exposure score, labeling it as "Long," "Short," or "Neutral." Horizontal Lines: Reference lines at 0%, 100%, and -100% visually mark neutral, increasing long, and increasing short exposure levels. Exposure Table: A table displays the current exposure level (in percentage) and position type ("Long," "Short," or "Neutral"), updated dynamically based on the oscillator’s value. Inputs: Theme Mode: Choose "Auto" to use the default chart theme, or manually select "Dark" or "Light." Usage: This oscillator is designed to help traders track market sentiment, gauge exposure levels, and manage risk. It can be used for long-term trend-following strategies or short-term trades based on moving average crossovers and volume analysis. The oscillator operates in conjunction with the chart’s price action and provides a visual representation of the market’s current trend strength and exposure. Important Considerations: Risk Management: While the exposure score provides valuable insight, it should be combined with other risk management tools and analysis for optimal trading decisions. Signal Sensitivity: The accuracy and effectiveness of the signals depend on market conditions and may require adjustments based on the user’s trading strategy or timeframe. Disclaimer: This script is for educational purposes only. Trading involves significant risk, and users should carefully evaluate all market conditions and apply appropriate risk management strategies before using this tool in live trading environments.
Pine Script® indicator
by starshiptrade
JordanSwindenLibraryLibrary "JordanSwindenLibrary" TODO: add library description here getDecimals()   Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price getPipSize(multiplier)   Calculates the pip size of the current market   Parameters:      multiplier (int) : The mintick point multiplier (1 by default, 10 for FX/Crypto/CFD but can be used to override when certain markets require)   Returns: The pip size for the current market truncate(number, decimalPlaces)   Truncates (cuts) excess decimal places   Parameters:      number (float) : The number to truncate      decimalPlaces (simple float) : (default=2) The number of decimal places to truncate to   Returns: The given number truncated to the given decimalPlaces toWhole(number)   Converts pips into whole numbers   Parameters:      number (float) : The pip number to convert into a whole number   Returns: The converted number toPips(number)   Converts whole numbers back into pips   Parameters:      number (float) : The whole number to convert into pips   Returns: The converted number getPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period   Parameters:      value1 (float) : The first value to reference      value2 (float) : The second value to reference      lookback (int) : The lookback period to analyze   Returns: The percent change over the two values and lookback period random(minRange, maxRange)   Wichmann–Hill Pseudo-Random Number Generator   Parameters:      minRange (float) : The smallest possible number (default: 0)      maxRange (float) : The largest possible number (default: 1)   Returns: A random number between minRange and maxRange bullFib(priceLow, priceHigh, fibRatio)   Calculates a bullish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio)   Calculates a bearish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(length, maType)   Gets a Moving Average based on type (! MUST BE CALLED ON EVERY TICK TO BE ACCURATE, don't place in scopes)   Parameters:      length (simple int) : The MA period      maType (string) : The type of MA   Returns: A moving average with the given parameters barsAboveMA(lookback, ma)   Counts how many candles are above the MA   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(lookback, ma)   Counts how many candles are below the MA   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently (based on closing prices)   Parameters:      lookback (int) : The lookback period to look back over      ma (float) : The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA (based on closing prices) getPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      lookback (int) : The lookback period to look back over      direction (int) : The color of the bar to count (1 = Green, -1 = Red)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize()   Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize()   Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize()   Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent()   Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(fib, colorMatch)   Checks if the current bar is a hammer candle based on the given parameters   Parameters:      fib (float) : (default=0.382) The fib to base candle body on      colorMatch (bool) : (default=false) Does the candle need to be green? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(fib, colorMatch)   Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      fib (float) : (default=0.382) The fib to base candle body on      colorMatch (bool) : (default=false) Does the candle need to be red? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(wickSize, bodySize)   Checks if the current bar is a doji candle based on the given parameters   Parameters:      wickSize (float) : (default=2) The maximum top wick size compared to the bottom (and vice versa)      bodySize (float) : (default=0.05) The maximum body size as a percentage compared to the entire candle size   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bullish engulfing candle   Parameters:      allowance (float) : (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      rejectionWickSize (float) : (default=disabled) The maximum rejection wick size compared to the body as a percentage      engulfWick (bool) : (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bearish engulfing candle   Parameters:      allowance (float) : (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      rejectionWickSize (float) : (default=disabled) The maximum rejection wick size compared to the body as a percentage      engulfWick (bool) : (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar()   Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar()   Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session   Parameters:      sess (simple string) : The session to check      useFilter (bool) : (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session barOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session   Parameters:      sess (simple string) : The session to check      useFilter (bool) : (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range   Parameters:      startTime (int) : The UNIX date timestamp to begin searching from      endTime (int) : the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze   Parameters:      monday (bool) : Should the script analyze this day? (true/false)      tuesday (bool) : Should the script analyze this day? (true/false)      wednesday (bool) : Should the script analyze this day? (true/false)      thursday (bool) : Should the script analyze this day? (true/false)      friday (bool) : Should the script analyze this day? (true/false)      saturday (bool) : Should the script analyze this day? (true/false)      sunday (bool) : Should the script analyze this day? (true/false)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(atrValue, maxSize)   Parameters:      atrValue (float)      maxSize (float) tradeCount()   Calculate total trade count   Returns: Total closed trade count isLong()   Check if we're currently in a long trade   Returns: True if our position size is positive isShort()   Check if we're currently in a short trade   Returns: True if our position size is negative isFlat()   Check if we're currentlyflat   Returns: True if our position size is zero wonTrade()   Check if this bar falls after a winning trade   Returns: True if we just won a trade lostTrade()   Check if this bar falls after a losing trade   Returns: True if we just lost a trade maxDrawdownRealized()   Gets the max drawdown based on closed trades (ie. realized P&L). The strategy tester displays max drawdown as open P&L (unrealized).   Returns: The max drawdown based on closed trades (ie. realized P&L). The strategy tester displays max drawdown as open P&L (unrealized). totalPipReturn()   Gets the total amount of pips won/lost (as a whole number)   Returns: Total amount of pips won/lost (as a whole number) longWinCount()   Count how many winning long trades we've had   Returns: Long win count shortWinCount()   Count how many winning short trades we've had   Returns: Short win count longLossCount()   Count how many losing long trades we've had   Returns: Long loss count shortLossCount()   Count how many losing short trades we've had   Returns: Short loss count breakEvenCount(allowanceTicks)   Count how many break-even trades we've had   Parameters:      allowanceTicks (float) : Optional - how many ticks to allow between entry & exit price (default 0)   Returns: Break-even count longCount()   Count how many long trades we've taken   Returns: Long trade count shortCount()   Count how many short trades we've taken   Returns: Short trade count longWinPercent()   Calculate win rate of long trades   Returns: Long win rate (0-100) shortWinPercent()   Calculate win rate of short trades   Returns: Short win rate (0-100) breakEvenPercent(allowanceTicks)   Calculate break even rate of all trades   Parameters:      allowanceTicks (float) : Optional - how many ticks to allow between entry & exit price (default 0)   Returns: Break-even win rate (0-100) averageRR()   Calculate average risk:reward   Returns: Average winning trade divided by average losing trade unitsToLots(units)   (Forex) Convert the given unit count to lots (multiples of 100,000)   Parameters:      units (float) : The units to convert into lots   Returns: Units converted to nearest lot size (as float) getFxPositionSize(balance, risk, stopLossPips, fxRate, lots)   (Forex) Calculate fixed-fractional position size based on given parameters   Parameters:      balance (float) : The account balance      risk (float) : The % risk (whole number)      stopLossPips (float) : Pip distance to base risk on      fxRate (float) : The conversion currency rate (more info below in library documentation)      lots (bool) : Whether or not to return the position size in lots rather than units (true by default)   Returns: Units/lots to enter into "qty=" parameter of strategy entry function EXAMPLE USAGE: string conversionCurrencyPair = (strategy.account_currency == syminfo.currency ? syminfo.tickerid : strategy.account_currency + syminfo.currency) float fx_rate = request.security(conversionCurrencyPair, timeframe.period, close ) if (longCondition) strategy.entry("Long", strategy.long, qty=zen.getFxPositionSize(strategy.equity, 1, stopLossPipsWholeNumber, fx_rate, true)) skipTradeMonteCarlo(chance, debug)   Checks to see if trade should be skipped to emulate rudimentary Monte Carlo simulation   Parameters:      chance (float) : The chance to skip a trade (0-1 or 0-100, function will normalize to 0-1)      debug (bool) : Whether or not to display a label informing of the trade skip   Returns: True if the trade is skipped, false if it's not skipped (idea being to include this function in entry condition validation checks) fillCell(tableID, column, row, title, value, bgcolor, txtcolor, tooltip)   This updates the given table's cell with the given values   Parameters:      tableID (table) : The table ID to update      column (int) : The column to update      row (int) : The row to update      title (string) : The title of this cell      value (string) : The value of this cell      bgcolor (color) : The background color of this cell      txtcolor (color) : The text color of this cell      tooltip (string)   Returns: Nothing.
Pine Script® library
by jordanswinden
Volume Spread Analysis [TANHEF]Volume Spread Analysis: Understanding Market Intentions through the Interpretation of Volume and Price Movements. █ Simple Explanation: The Volume Spread Analysis (VSA) indicator is a comprehensive tool that helps traders identify key market patterns and trends based on volume and spread data. This indicator highlights significant VSA patterns and provides insights into market behavior through color-coded volume/spread bars and identification of bars indicating strength, weakness, and neutrality between buyers and sellers. It also includes powerful volume and spread forecasting capabilities. █ Laws of Volume Spread Analysis (VSA): The origin of VSA begins with Richard Wyckoff, a pivotal figure in its development. Wyckoff made significant contributions to trading theory, including the formulation of three basic laws: The Law of Supply and Demand: This fundamental law states that supply and demand balance each other over time. High demand and low supply lead to rising prices until demand falls to a level where supply can meet it. Conversely, low demand and high supply cause prices to fall until demand increases enough to absorb the excess supply. The Law of Cause and Effect: This law assumes that a 'cause' will result in an 'effect' proportional to the 'cause'. A strong 'cause' will lead to a strong trend (effect), while a weak 'cause' will lead to a weak trend. The Law of Effort vs. Result: This law asserts that the result should reflect the effort exerted. In trading terms, a large volume should result in a significant price move (spread). If the spread is small, the volume should also be small. Any deviation from this pattern is considered an anomaly. █ Volume and Spread Analysis Bars: Display: Volume and/or spread bars that consist of color coded levels. If both of these are displayed, the number of spread bars can be limited for visual appeal and understanding, with the spread bars scaled to match the volume bars. While automatic calculation of the number of visual bars for auto scaling is possible, it is avoided to prevent the indicator from reloading whenever the number of visual price bars on the chart is adjusted, ensuring uninterrupted analysis. A displayable table (Legend) of bar colors and levels can give context and clarify to each volume/spread bar. Calculation: Levels are calculated using multipliers applied to moving averages to represent key levels based on historical data: low, normal, high, ultra. This method smooths out short-term fluctuations and focuses on longer-term trends. Low Level: Indicates reduced volatility and market interest. Normal Level: Reflects typical market activity and volatility. High Level: Indicates increased activity and volatility. Ultra Level: Identifies extreme levels of activity and volatility. This illustrates the appearance of Volume and Spread bars when scaled and plotted together: █ Forecasting Capabilities: Display: Forecasted volume and spread levels using predictive models. Calculation: Volume and Spread prediction calculations differ as volume is linear and spread is non-linear. Volume Forecast (Linear Forecasting): Predicts future volume based on current volume rate and bar time till close. Spread Forecast (Non-Linear Dynamic Forecasting): Predicts future spread using a dynamic multiplier, less near midpoint (consolidation) and more near low or high (trending), reflecting non-linear expansion. Moving Averages: In forecasting, moving averages utilize forecasted levels instead of actual levels to ensure the correct level is forecasted (low, normal, high, or ultra). The following compares forecasted volume with actual resulting volume, highlighting the power of early identifying increased volume through forecasted levels: █ VSA Patterns: Criteria and descriptions for each VSA pattern are available as tooltips beside them within the indicator’s settings. These tooltips provide explanations of potential developments based on the volume and spread data. Signs of Strength (🟢): Patterns indicating strong buying pressure and potential market upturns. Down Thrust Selling Climax No Effort → Bearish Result Bearish Effort → No Result Inverse Down Thrust Failed Selling Climax Bull Outside Reversal End of Falling Market (Bag Holder) Pseudo Down Thrust No Supply Signs of Weakness (🔴): Patterns indicating strong selling pressure and potential market downturns. Up Thrust Buying Climax No Effort → Bullish Result Bullish Effort → No Result Inverse Up Thrust Failed Buying Climax Bear Outside Reversal End of Rising Market (Bag Seller) Pseudo Up Thrust No Demand Neutral Patterns (🔵): Patterns indicating market indecision and potential for continuation or reversal. Quiet Doji Balanced Doji Strong Doji Quiet Spinning Top Balanced Spinning Top Strong Spinning Top Quiet High Wave Balanced High Wave Strong High Wave Consolidation Bar Patterns (🟡): Common candlestick patterns that offer insights into market sentiment. These are required in some VSA patterns and can also be displayed independently. Bull Pin Bar Bear Pin Bar Doji Spinning Top High Wave Consolidation This demonstrates the acronym and descriptive options for displaying bar patterns, with the ability to hover over text to reveal the descriptive text along with what type of pattern: █ Alerts: VSA Pattern Alerts: Notifications for identified VSA patterns at bar close. Volume and Spread Alerts: Alerts for confirmed and forecasted volume/spread levels (Low, High, Ultra). Forecasted Volume and Spread Alerts: Alerts for forecasted volume/spread levels (High, Ultra) include a minimum percent time elapsed input to reduce false early signals by ensuring sufficient bar time has passed. █ Inputs and Settings: Display Volume and/or Spread: Choose between displaying volume bars, spread bars, or both with different lookback periods. Indicator Bar Color: Select color schemes for bars (Normal, Detail, Levels). Indicator Moving Average Color: Select schemes for bars (Fill, Lines, None). Price Bar Colors: Options to color price bars based on VSA patterns and volume levels. Legend: Display a table of bar colors and levels for context and clarity of volume/spread bars. Forecast: Configure forecast display and prediction details for volume and spread. Average Multipliers: Define multipliers for different levels (Low, High, Ultra) to refine the analysis. Moving Average: Set volume and spread moving average settings. VSA: Select the VSA patterns to be calculated and displayed (Strength, Weakness, Neutral). Bar Patterns: Criteria for bar patterns used in VSA (Doji, Bull Pin Bar, Bear Pin Bar, Spinning Top, Consolidation, High Wave). Colors: Set exact colors used for indicator bars, indicator moving averages, and price bars. More Display Options: Specify how VSA pattern text is displayed (Acronym, Descriptive), positioning, and sizes. Alerts: Configure alerts for VSA patterns, volume, and spread levels, including forecasted levels. █ Usage: The Volume Spread Analysis indicator is a helpful tool for leveraging volume spread analysis to make informed trading decisions. It offers comprehensive visual and textual cues on the chart, making it easier to identify market conditions, potential reversals, and continuations. Whether analyzing historical data or forecasting future trends, this indicator provides insights into the underlying factors driving market movements.
Pine Script® indicator
by TanHef
23
Delta ZigZag [LuxAlgo]The Delta ZigZag indicator is focused on volume analysis during the development of ZigZag lines. Volume data can be retrieved from a Lower timeframe (LTF) or real-time Tick data. Our Delta ZigZag publication can be helpful in detecting indications of a trend reversal or potential weakening/strengthening of the trend. This indicator by its very nature backpaints, meaning that the displayed components are offset in the past. 🔶 USAGE The ZigZag line is formed by connecting Swings , which can be set by adjusting the Left and Right settings. Left is the number of bars for evaluation at the left of the evaluated point. Right is the number of bars for evaluation at the right of the evaluated point. A valid Swing is a value higher or lower than the bars at the left/right . A higher Left or Right set number will generally create broader ZigZag ( ZZ ) lines, while the drawing of the ZZ line will be delayed (especially when Right is set higher). On the other hand, when Right is set at 0, ZZ line are drawn quickly. However, this results in a hyperactive switching of the ZZ direction. To ensure maximum visibility of values, we recommend using " Bars " from the " Bar's style " menu. 🔹 Volume examination The script provides two options for Volume examination : Examination per ZigZag line Examination per bar Bullish Volume is volume associated with a green bar ( close > open ) Bearish Volume is volume associated with a red bar ( close < open ) Neutral Volume (volume on a " close == open" bar) is not included in this publication. 🔹 Examination per ZigZag line As long as the price moves in the same direction, the present ZZ line will continue. When the direction of the price changes, the bull/bear volume of the previous ZZ line is evaluated and drawn on the chart. The ZZ line is divided into two parts: a bullish green line and a bearish red line. The intercept of these two lines will depend on the ratio of bullish/bearish volume This ratio is displayed at the intercept as % bullish volume (Settings -> Show % Bullish Volume) * Note that we cannot draw between 2 bars. Therefore, if a ZZ line is only 1 bar long, the intercept will be at one of those 2 bars and not in between. The percentage can be helpful in interpreting bull/bear volume. In the example above (2 most right labels), you can see that an overlap of 2 labels is prevented, ensuring the ability to evaluate the bullish % volume of the ZZ line . The percentage will be colored green when more than 50%, red otherwise. The color will fade when the direction is contradictory; for example, 40% when the ZZ line goes up or 70% when the ZZ line falls. More details can be visualized by enabling " Show " and choosing 1 of 3 options: Average Volume Delta/bar Average Volume/bar Normalised Volume Delta For both 'averages', the sum of " Volume "/" Volume Delta " of every bar on the ZZ line is divided by the number of bars (per ZZ line ). The " Normalised Volume Delta " is calculated by dividing the sum of " Delta Volume " by the sum of " Volume " (neutral volume not included), which is displayed as a percentage. All three options will display a label at the last point of the ZZ line and be coloured similarly: green when the ratio bullish/bearish volume of the ZZ line is bullish and red otherwise. Here, the colour also fades when it is bullish, but the ZZ line falls or when it is bearish with a rising ZZ line . A tooltip at each label hints at the chosen option. You can pick one of the options or combine them together. 🔹 Examination per bar Besides information about what's happening during the ZZ line , information per bar can be visualized by enabling " Show Details " in Settings . Split Volume per bar : show the sum of bullish (upV) and bearish (dnV) volume per bar Volume (bar) : Total Volume per bar (bullish + bearish volume, neutral volume not included) Δ Volume (bar) : Show Delta Volume (bullish - bearish volume) 🔹 Using Lower Timeframe Data The ZigZag lines using LTF data are colored brighter. Also note the vertical line where the LTF data starts and the gap between ZZ lines with LTF data and without. When " LTF " is chosen for the " Data from: " option in Settings , data is retrieved from Lower Timeframe bars (default 1 minute). When the LTF setting is higher than the current chart timeframe, the LTF period will automatically be adjusted to the current timeframe to prevent errors. As there is a 100K limit to the number of LTF intrabars that can be analyzed by a script, this implies the higher the difference between LTF and current TF; the fewer ZZ lines will be seen. 🔹 Using real-time tick data The principles are mostly the same as those of LTF data. However, in contrast with LTF data, where you already have LTF ZZ lines when loading the script, real-time tick data-based ZZ lines will only start after loading the chart. Changing the settings of a ticker will reset everything. However, returning to the same settings/ticker would show the cached data again. Here, you can see that changing settings reset everything, but returning after 2 minutes to the initial settings shows the cached data. Don't expect it to be cached for hours or days, though. 🔶 DETAILS The timeframe used for LTF data should always be the same or lower than the current TF; otherwise, an error occurs. This snippet prevents the error and adjusts the LTF to the current TF when LTF is too high: res = input.timeframe('1') res := timeframe.from_seconds( math.min( timeframe.in_seconds(timeframe.period), timeframe.in_seconds(res) ) ) 🔶 SETTINGS Data from: LTF (Lower TimeFrame) or Ticks (Real-time ticks) Res: Lower TimeFrame (only applicable when choosing LTF ) Option: choose " high/low " or " close " for Swing detection 🔹 ZigZag Left: Lookback period for Swings Right: Confirmation period after potential Swing 🔹 ZigZag Delta Show % Bullish Volume : % bullish volume against total volume during the ZZ line Show: Average Volume Delta/bar Average Volume/bar Normalised Volume Delta See USAGE for more information 🔹 Bar Data Split Volume per bar: shows the sum of bullish ( upV ) and bearish ( dnV ) volume per bar Volume (bar): Total Volume per bar (bullish + bearish volume, neutral volume not included) Δ Volume (bar): Show Volume Delta (bullish - bearish volume)
Pine Script® indicator
by LuxAlgo
15
LYGLibraryLibrary "LYGLibrary" A collection of custom tools & utility functions commonly used with my scripts getDecimals()   Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price truncate(number, decimalPlaces)   Truncates (cuts) excess decimal places   Parameters:      number (float)      decimalPlaces (simple float)   Returns: The given number truncated to the given decimalPlaces toWhole(number)   Converts pips into whole numbers   Parameters:      number (float)   Returns: The converted number toPips(number)   Converts whole numbers back into pips   Parameters:      number (float)   Returns: The converted number getPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period   Parameters:      value1 (float)      value2 (float)      lookback (int) av_getPositionSize(balance, risk, stopPoints, conversionRate)   Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      balance (float)      risk (float)      stopPoints (float)      conversionRate (float)   Returns: The calculated position size (in units - only compatible with OANDA) bullFib(priceLow, priceHigh, fibRatio)   Calculates a bullish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio)   Calculates a bearish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(length, maType)   Gets a Moving Average based on type (MUST BE CALLED ON EVERY CALCULATION)   Parameters:      length (simple int)      maType (string)   Returns: A moving average with the given parameters getEAP(atr)   Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      atr (float)   Returns: The EAP SL converted ATR size getEAP2(atr)   Performs secondary EAP stop loss size calculation (eg. ATR < 40, add 5 pips, ATR between 40-50, add 10 pips etc)   Parameters:      atr (float)   Returns: The EAP SL converted ATR size barsAboveMA(lookback, ma)   Counts how many candles are above the MA   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are above the MA barsBelowMA(lookback, ma)   Counts how many candles are below the MA   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      lookback (int)      direction (int)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize()   Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize()   Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize()   Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent()   Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(fib, colorMatch)   Checks if the current bar is a hammer candle based on the given parameters   Parameters:      fib (float)      colorMatch (bool)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(fib, colorMatch)   Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      fib (float)      colorMatch (bool)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(wickSize, bodySize)   Checks if the current bar is a doji candle based on the given parameters   Parameters:      wickSize (float)      bodySize (float)   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bullish engulfing candle   Parameters:      allowance (float)      rejectionWickSize (float)      engulfWick (bool)   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bearish engulfing candle   Parameters:      allowance (float)      rejectionWickSize (float)      engulfWick (bool)   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar()   Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar()   Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls within the given time session barOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range   Parameters:      startTime (int)      endTime (int)   Returns: A boolean - true if the current bar falls within the given dates dayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze   Parameters:      monday (bool)      tuesday (bool)      wednesday (bool)      thursday (bool)      friday (bool)      saturday (bool)      sunday (bool)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(atrValue, maxSize)   Parameters:      atrValue (float)      maxSize (float) fillCell(tableID, column, row, title, value, bgcolor, txtcolor)   This updates the given table's cell with the given values   Parameters:      tableID (table)      column (int)      row (int)      title (string)      value (string)      bgcolor (color)      txtcolor (color)   Returns: A boolean - true if the current bar falls within the given dates
Pine Script® library
by liyugen
CVD - Cumulative Volume Delta (Chart)█   OVERVIEW This indicator displays cumulative ​volume delta (​CVD) as an on-chart oscillator. It uses intrabar analysis to obtain more precise ​volume delta information compared to methods that only use the chart's timeframe. The core concepts in this script come from our first ​ CVD indicator , which displays CVD​ values as plot candles in a separate indicator pane. In this script, CV​D values are scaled according to price ranges and represented on the main chart pane. █   CONCEPTS Bar polarity Bar polarity refers to the position of the close price relative to the open price. In other words, bar polarity is the direction of price change. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 bars at the lower timeframe of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This script utilizes a LTF to analyze intrabars, or price changes within a chart bar. The lower the ​LTF, the more intrabars are analyzed, but the less chart bars can display information due to the limited number of intrabars that can be analyzed. Volume delta Volume delta is a measure that separates ​volume​ into "up" and "down" parts, then takes the difference to estimate the net demand for the asset. This approach gives traders a more detailed insight when analyzing volume​ and market sentiment. There are several methods for determining whether an asset's volume​ belongs in the "up" or "down" category. Some indicators, such as On Balance Volume​ and the Klinger Oscillator , use the change in price between bars to assign ​volume​ values to the appropriate category. Others, such as Chaikin Money Flow , make assumptions based on open, high, low, and close prices. The most accurate method involves using tick data to determine whether each transaction occurred at the bid or ask price and assigning the ​volume​ value to the appropriate category accordingly. However, this method requires a large amount of data on historical bars, which can limit the historical depth of charts and the number of symbols for which tick data is available. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. This indicator uses intrabar analysis to achieve a compromise between simplicity and accuracy in calculating ​volume delta on historical bars. Our Volume Profile indicators use it as well. Other ​volume delta indicators in our Community Scripts , such as the Realtime 5D Profile , use real-time chart updates to achieve more precise ​volume delta calculations. However, these indicators aren't suitable for analyzing historical bars since they only work for real-time analysis. This is the logic we use to assign intrabar ​volume to the "up" or "down" category:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars comprising a chart bar are analyzed, we calculate the net difference between "up" and "down" intrabar volume​ to produce the volume​ delta for the chart bar. █   FEATURES CVD resets The "cumulative" part of the indicator's name stems from the fact that calculations accumulate during a period of time. By periodically resetting the volume​ delta accumulation, we can analyze the progression of ​volume delta across manageable chunks, which is often more useful than looking at ​volume delta accumulated from the beginning of a chart's history. You can configure the reset period using the "CVD Resets" input, which offers the following selections:  • None : Calculations do not reset.  • On a fixed higher timeframe : Calculations reset on the higher timeframe you select in the "Fixed higher timeframe" field.  • At a fixed time that you specify.  • At the beginning of the regular session .  • On trend changes : Calculations reset on the direction change of either the Aroon indicator, Parabolic SAR , or Supertrend .  • On a stepped higher timeframe : Calculations reset on a higher timeframe automatically stepped using the chart's timeframe and following these rules: Chart TF ​HTF < 1min 1H < 3H 1D <= 12H 1W < 1W 1M >= 1W 1Y Specifying intrabar precision Ten options are included in the script to control the number of intrabars used per chart bar for calculations. The greater the number of intrabars per chart bar, the fewer chart bars can be analyzed. The first five options allow users to specify the approximate amount of chart bars to be covered:  • Least Precise (Most chart bars) : Covers all chart bars by dividing the current timeframe by four.   This ensures the highest level of intrabar precision while achieving complete coverage for the dataset.  • Less Precise (Some chart bars) & More Precise (Less chart bars) : These options calculate a stepped ​LTF in relation to the current chart's timeframe.  • Very precise (2min intrabars) : Uses the second highest quantity of intrabars possible with the 2min ​LTF.  • Most precise (1min intrabars) : Uses the maximum quantity of intrabars possible with the 1min ​LTF. The stepped lower timeframe for "Less Precise" and "More Precise" options is calculated from the current chart's timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min The last five options allow users to specify an approximate fixed number of intrabars to analyze per chart bar. The available choices are 12, 24, 50, 100, and 250. The script will calculate the LTF​ which most closely approximates the specified number of intrabars per chart bar. Keep in mind that due to factors such as the length of a ticker's sessions and rounding of the LTF​, it is not always possible to produce the exact number specified. However, the script will do its best to get as close to the value as possible. As there is a limit to the number of intrabars that can be analyzed by a script, a tradeoff occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. Display This script displays raw or cumulative volume​ delta values on the chart as either line or histogram oscillator zones scaled according to the price chart, allowing traders to visualize volume​ activity on each bar or cumulatively over time. The indicator's background shows where CVD​ resets occur, demarcating the beginning of new zones. The vertical axis of each oscillator zone is scaled relative to the one with the highest price range, and the oscillator values are scaled relative to the highest volume​ delta. A vertical offset is applied to each oscillator zone so that the highest oscillator value aligns with the lowest price. This method ensures an accurate, intuitive visual comparison of volume​ activity within zones, as the scale is consistent across the chart, and oscillator values sit below prices. The vertical scale of oscillator zones can be adjusted using the "Zone Height" input in the script settings. This script displays labels at the highest and lowest oscillator values in each zone, which can be enabled using the "Hi/Lo Labels" input in the "Visuals" section of the script settings. Additionally, the oscillator's value on a chart bar is displayed as a tooltip when a user hovers over the bar, which can be enabled using the "Value Tooltips" input. Divergences occur when the polarity of ​volume delta does not match that of the chart bar. The script displays divergences as bar colors and background colors that can be enabled using the "Color bars on divergences" and "Color background on divergences" inputs. An information box in the lower-left corner of the indicator displays the HTF used for resets, the ​LTF used for intrabars, the average quantity of intrabars per chart bar, and the number of chart bars for which there is LTF data. This is enabled using the "Show information box" input in the "Visuals" section of the script settings. FOR Pine Script™ CODERS  • This script utilizes `ltf()` and `ltfStats()` from the lower_tf library.   The `ltf()` function determines the appropriate lower timeframe from the selected calculation mode and chart timeframe, and returns it in a format that can be used with request.security_lower_tf() .   The `ltfStats()` function, on the other hand, is used to compute and display statistical information about the lower timeframe in an information box.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • The newly added session.isfirstbar_regular built-in allows for resetting the ​CVD segments at the start of the regular session.  • The VisibleChart library developed by our resident PineCoders team leverages the chart.left_visible_bar_time and chart.right_visible_bar_time variables to optimize the performance of this script.   These variables identify the opening time of the leftmost and rightmost visible bars on the chart, allowing the script to recalculate and draw objects only within the range of visible bars as the user scrolls.   This functionality also enables the scaling of the oscillator zones.   These variables are just a couple of the many new built-ins available in the chart.* namespace.   For more information, check out this blog post or look them up by typing "chart." in the Pine Script™ Reference Manual .  • Our ta library has undergone significant updates recently, including the incorporation of the `aroon()` indicator used as a method for resetting ​CVD segments within this script.   Revisit the library to see more of the newly added content! Look first. Then leap.
Pine Script® indicator
by TradingView
58
Delta Volume Channels [LucF]█  OVERVIEW This indicator displays on-chart visuals aimed at making the most of delta ​volume information. It can color bars and display two channels: one for delta ​volume, another calculated from the price levels of bars where delta ​volume divergences occur. Markers and alerts can also be configured using key conditions, and filtered in many different ways. The indicator caters to traders who prefer chart visuals over raw values. It will work on historical bars and in real time, using intrabar analysis to calculate delta ​volume in both conditions. █  CONCEPTS Delta Volume ​The ​volume delta concept divides a bar's ​volume in "up" and "down" ​volumes. The delta is calculated by subtracting down ​volume from up ​volume. Many calculation techniques exist to isolate up and down ​volume within a bar. The simplest techniques use the polarity of interbar price changes to assign their ​volume to up or down slots, e.g., On Balance Volume or the Klinger Oscillator . Others such as Chaikin Money Flow use assumptions based on a bar's OHLC values. The most precise calculation method uses tick data and assigns the ​volume of each tick to the up or down slot depending on whether the transaction occurs at the bid or ask price. While this technique is ideal, it requires huge amounts of data on historical bars, which usually limits the historical depth of charts and the number of symbols for which tick data is available. This indicator uses intrabar analysis to achieve a compromise between the simplest and most precise methods of calculating ​volume delta. In the context where historical tick data is not yet available on TradingView, intrabar analysis is the most precise technique to calculate ​volume delta on historical bars on our charts. TradingView's Volume Profile built-in indicators use it, as do the CVD - Cumulative ​Volume Delta Candles and CVD - Cumulative Volume Delta (Chart) indicators published from the TradingView account . My Volume Delta Columns Pro indicator also uses intrabar analysis. Other ​volume delta indicators such as my Realtime 5D Profile use realtime chart updates to achieve more precise ​volume delta calculations. Indicators of that type cannot be used on historical bars however; they only work in real time. This is the logic I use to assign intrabar ​volume to up or down slots:  • If the intrabar's open and close values are different, their relative position is used.  • If the intrabar's open and close values are the same, the difference between the intrabar's close and the previous intrabar's close is used.  • As a last resort, when there is no movement during an intrabar and it closes at the same price as the previous intrabar, the last known polarity is used. Once all intrabars making up a chart bar have been analyzed and the up or down property of each intrabar's ​volume determined, the up volumes are added and the down volumes subtracted. The resulting value is ​volume delta for that chart bar, which can be used as an estimate of the buying/selling pressure on an instrument. Delta ​Volume Percent (DV%) This value is the proportion that delta ​volume represents of the total intrabar ​volume in the chart bar. Note that on some symbols/timeframes, the total intrabar ​volume may differ from the chart's ​volume for a bar, but that will not affect our calculations since we use the total intrabar ​volume. Delta ​Volume Channel The ​​DV channel is the space between two moving averages: the reference line and a DV%-weighted version of that reference. The reference line is a moving average of a type, source and length which you select. The DV%-weighted line uses the same settings, but it averages the DV%-weighted price source. The weight applied to the source of the reference line is calculated from two values, which are multiplied: DV% and the relative size of the bar's ​volume in relation to previous bars. The effect of this is that DV% values on bars with higher total ​volume will carry greater weight than those with lesser ​volume. The ​DV channel can be in one of four states, each having its corresponding color:  • Bull (teal): The DV%-weighted line is above the reference line.  • Strong bull (lime): The bull condition is fulfilled and the bar's close is above the reference line and both the reference and the DV%-weighted lines are rising.  • Bear (maroon): The DV%-weighted line is below the reference line.  • Strong bear (pink): The bear condition is fulfilled and the bar's close is below the reference line and both the reference and the DV%-weighted lines are falling. Divergences In the context of this indicator, a divergence is any bar where the slope of the reference line does not match that of the DV%-weighted line. No directional bias is assigned to divergences when they occur. Divergence Channel The divergence channel is the space between two levels (by default, the bar's low and high ) saved when divergences occur. When price has breached a channel and a new divergence occurs, a new channel is created. Until that new channel is breached, bars where additional divergences occur will expand the channel's levels if the bar's price points are outside the channel. Prices breaches of the divergence channel will change its state. Divergence channels can be in one of five different states:  • Bull (teal): Price has breached the channel to the upside.  • Strong bull (lime): The bull condition is fulfilled and the ​DV channel is in the strong bull state.  • Bear (maroon): Price has breached the channel to the downside.  • Strong bear (pink): The bear condition is fulfilled and the ​DV channel is in the strong bear state.  • Neutral (gray): The channel has not been breached. █  HOW TO USE THE INDICATOR Load the indicator on an active chart (see here if you don't know how). The default configuration displays:  • The ​DV channel, without the reference or DV%-weighted lines.  • The Divergence channel, without its level lines.  • Bar colors using the state of the ​DV channel. The default settings use an Arnaud-Legoux moving average on the close and a length of 20 bars. The DV%-weighted version of it uses a combination of DV% and relative ​volume to calculate the ultimate weight applied to the reference. The DV%-weighted line is capped to 5 standard deviations of the reference. The lower timeframe used to access intrabars automatically adjusts to the chart's timeframe and achieves optimal balance between the number of intrabars inspected in each chart bar, and the number of chart bars covered by the script's calculations. The Divergence channel's levels are determined using the high and low of the bars where divergences occur. Breaches of the channel require a bar's low to move above the top of the channel, and the bar's high to move below the channel's bottom. No markers appear on the chart; if you want to create alerts from this script, you will need first to define the conditions that will trigger the markers, then create the alert, which will trigger on those same conditions. To learn more about how to use this indicator, you must understand the concepts it uses and the information it displays, which requires reading this description. There are no videos to explain it. █  FEATURES The script's inputs are divided in four sections: "DV channel", "Divergence channel", "Other Visuals" and "Marker/Alert Conditions". The first setting is the selection method used to determine the intrabar precision, i.e., how many lower timeframe bars (intrabars) are examined in each chart bar. The more intrabars you analyze, the more precise the calculation of DV% results will be, but the less chart coverage can be covered by the script's calculations. DV Channel Here, you control the visibility and colors of the reference line, its weighted version, and the DV channel between them. You also specify what type of moving average you want to use as a reference line, its source and length. This acts as the ​DV channel's baseline. The DV%-weighted line is also a moving average of the same type and length as the reference line, except that it will be calculated from the DV%-weighted source used in the reference line. By default, the DV%-weighted line is capped to five standard deviations of the reference line. You can change that value here. This section is also where you can disable the relative ​volume component of the weight. Divergence Channel This is where you control the appearance of the divergence channel and the key price values used in determining the channel's levels and breaching conditions. These choices have an impact on the behavior of the channel. More generous level prices like the default low and high selection will produce more conservative channels, as will the default choice for breach prices. In this section, you can also enable a mode where an attempt is made to estimate the channel's bias before price breaches the channel. When it is enabled, successive increases/decreases of the channel's top and bottom levels are counted as new divergences occur. When one count is greater than the other, a bull/bear bias is inferred from it. Other Visuals You specify here:  • The method used to color chart bars, if you choose to do so.  • The display of a mark appearing above or below bars when a divergence occurs.  • If you want raw values to appear in tooltips when you hover above chart bars. The default setting does not display them, which makes the script faster.  • If you want to display an information box which by default appears in the lower left of the chart.   It shows which lower timeframe is used for intrabars, and the average number of intrabars per chart bar. Marker/Alert Conditions Here, you specify the conditions that will trigger up or down markers. The trigger conditions can include a combination of state transitions of the ​DV and the divergence channels. The triggering conditions can be filtered using a variety of conditions. Configuring the marker conditions is necessary before creating an alert from this script, as the alert will use the marker conditions to trigger. Markers only appear on bar closes, so they will not repaint. Keep in mind, when looking at markers on historical bars, that they are positioned on the bar when it closes — NOT when it opens. Raw values The raw values calculated by this script can be inspected using a tooltip and the Data Window. The tooltip is visible when you hover over the top of chart bars. It will display on the last 500 bars of the chart, and shows the values of ​DV, DV%, the combined weight, and the intermediary values used to calculate them. █  INTERPRETATION The aim of the ​DV channel is to provide a visual representation of the buying/selling pressure calculated using delta ​volume. The simplest characteristic of the channel is its bull/bear state. One can then distinguish between its bull and strong bull states, as transitions from strong bull to bull states will generally happen when buyers are losing steam. While one should not infer a reversal from such transitions, they can be a good place to tighten stops. Only time will tell if a reversal will occur. One or more divergences will often occur before reversals. The nature of the divergence channel's design makes it particularly adept at identifying consolidation areas if its settings are kept on the conservative side. A gray divergence channel should usually be considered a no-trade zone. More adventurous traders can use the ​DV channel to orient their trade entries if they accept the risk of trading in a neutral divergence channel, which by definition will not have been breached by price. If your charts are already busy with other stuff you want to hold on to, you could consider using only the chart bar coloring component of this indicator: At its simplest, one way to use this indicator would be to look for overlaps of the strong bull/bear colors in both the ​DV channel and a divergence channel, as these identify points where price is breaching the divergence channel when buy/sell pressure is consistent with the direction of the breach. I have highlighted all those points in the chart below. Not all of them would have produced profitable trades, but nothing is perfect in the markets. Also, keep in mind that the circles identify the visual you would be looking for — not the trade's entry level. █  LIMITATIONS  • The script will not work on symbols where no ​volume is available. An error will appear when that is the case.  • Because a maximum of 100K intrabars can be analyzed by a script, a compromise is necessary between the number of intrabars analyzed per chart bar   and chart coverage. The more intrabars you analyze per chart bar, the less coverage you will obtain.   The setting of the "Intrabar precision" field in the "DV channel" section of the script's inputs   is where you control how the lower timeframe is calculated from the chart's timeframe. █  NOTES Volume Quality If you use ​volume, it's important to understand its nature and quality, as it varies with sectors and instruments. My Volume X-ray indicator is one way you can appraise the quality of an instrument's intraday ​volume. For Pine Script™ Coders  • This script uses the new overload of the fill() function which now makes it possible to do vertical gradients in Pine. I use it for both channels displayed by this script.  • I use the new arguments for plot() 's `display` parameter to control where the script plots some of its values,   namely those I only want to appear in the script's status line and in the Data Window.  • I wrote my script using the revised recommendations in the Style Guide from the Pine v5 User Manual. █  THANKS To PineCoders . I have used their lower_tf library in this script, to manage the calculation of the LTF and intrabar stats, and their Time library to convert a timeframe in seconds to a printable form for its display in the Information box. To TradingView's Pine Script™ team. Their innovations and improvements, big and small, constantly expand the boundaries of the language. What this script does would not have been possible just a few months back. And finally, thanks to all the users of my scripts who take the time to comment on my publications and suggest improvements. I do not reply to all but I do read your comments and do my best to implement your suggestions with the limited time that I have.
Pine Script® indicator
by LucF
51
lower_tf█   OVERVIEW This library is a Pine programmer’s tool containing functions to help those who use the request.security_lower_tf() function. Its `ltf()` function helps translate user inputs into a lower timeframe string usable with request.security_lower_tf() . Another function, `ltfStats()`, accumulates statistics on processed chart bars and intrabars. █   CONCEPTS Chart bars Chart bars , as referred to in our publications, are bars that occur at the current chart timeframe, as opposed to those that occur at a timeframe that is higher or lower than that of the chart view. Intrabars Intrabars are chart bars at a lower timeframe than the chart's. Each 1H chart bar of a 24x7 market will, for example, usually contain 60 intrabars at the ​LTF of 1min, provided there was market activity during each minute of the hour. Mining information from intrabars can be useful in that it offers traders visibility on the activity inside a chart bar. Lower timeframes (LTFs) A lower timeframe is a timeframe that is smaller than the chart's timeframe. This framework exemplifies how authors can determine which ​LTF to use by examining the chart's timeframe. The ​LTF determines how many intrabars are examined for each chart bar; the lower the timeframe, the more intrabars are analyzed. Intrabar precision The precision of calculations increases with the number of intrabars analyzed for each chart bar. As there is a 100K limit to the number of intrabars that can be analyzed by a script, a trade-off occurs between the number of intrabars analyzed per chart bar and the chart bars for which calculations are possible. █   `ltf()` This function returns a timeframe string usable with request.security_lower_tf() . It calculates the returned timeframe by taking into account a user selection between eight different calculation modes and the chart's timeframe. You send it the user's selection, along with the text corresponding to the eight choices from which the user has chosen, and the function returns a corresponding ​LTF string. Because the function processes strings and doesn't require recalculation on each bar, using var to declare the variable to which its result is assigned will execute the function only once on bar zero and speed up your script: var string ltfString = ​ltf(ltfModeInput, LTF1, LTF2, LTF3, LTF4, LTF5, LTF6, LTF7, LTF8) The eight choices users can select from are of two types: the first four allow a selection from the desired amount of chart bars to be covered, the last four are choices of a fixed number of intrabars to be analyzed per chart bar. Our example code shows how to structure your input call and then make the call to `ltf()`. By changing the text associated with the `LTF1` to `LTF8` constants, you can tailor it to your preferences while preserving the functionality of `ltf()` because you will be sending those string constants as the function's arguments so it can determine the user's selection. The association between each `LTFx` constant and its calculation mode is fixed, so the order of the arguments is important when you call `ltf()`. These are the first four modes and the `LTFx` constants corresponding to each: Covering most chart bars (least precise) — LTF1 Covers all chart bars. This is accomplished by dividing the current timeframe in seconds by 4 and converting that number back to a string in timeframe.period format using secondsToTfString() . Due to the fact that, on premium subscriptions, the typical historical bar count is between 20-25k bars, dividing the timeframe by 4 ensures the highest level of intrabar precision possible while achieving complete coverage for the entire dataset with the maximum allowed 100K intrabars. Covering some chart bars (less precise) — LTF2 Covering less chart bars (more precise) — LTF3 These levels offer a stepped ​LTF in relation to the chart timeframe with slightly more, or slightly less precision. The stepped lower timeframe tiers are calculated from the chart timeframe as follows: Chart Timeframe Lower Timeframe Less Precise More Precise < 1hr 1min 1min < 1D 15min 1min < 1W ​2hr​ 30min > 1W 1D 60min Covering the least chart bars (most precise) — LTF4 Analyzes the maximum quantity of intrabars possible by using the 1min ​LTF, which also allows the least amount of chart bars to be covered. The last four modes allow the user to specify a fixed number of intrabars to analyze per chart bar. Users can choose from 12, 24, 50 or 100 intrabars, respectively corresponding to the `LTF5`, `LTF6`, `LTF7` and `LTF8` constants. The value is a target; the function will do its best to come up with a ​LTF producing the required number of intrabars. Because of considerations such as the length of a ticker's session, rounding of the ​LTF to the closest allowable timeframe, or the lowest allowable timeframe of 1min intrabars, it is often impossible for the function to find a ​​LTF producing the exact number of intrabars. Requesting 100 intrabars on a 60min chart, for example, can only produce 60 1min intrabars. Higher chart timeframes, tickers with high liquidity or 24x7 markets will produce optimal results. █   `ltfStats()` `ltfStats()` returns statistics that will be useful to programmers using intrabar inspection. By analyzing the arrays returned by request.security_lower_tf() in can determine:  • intrabarsInChartBar : The number of intrabars analyzed for each chart bar.  • chartBarsCovered : The number of chart bars where intrabar information is available.  • avgIntrabars : The average number of intrabars analyzed per chart bar. Events like holidays, market activity, or reduced hours sessions can cause the number of intrabars to vary, bar to bar. The function must be called on each bar to produce reliable results. █   DEMONSTRATION CODE Our example code shows how to provide users with an input from which they can select a ​LTF calculation mode. If you use this library's functions, feel free to reuse our input setup code, including the tooltip providing users with explanations on how it works for them. We make a simple call to request.security_lower_tf() to fetch the close values of intrabars, but we do not use those values. We simply send the returned array to `ltfStats()` and then plot in the indicator's pane the number of intrabars examined on each bar and its average. We also display an information box showing the user's selection of the ​LTF calculation mode, the resulting ​LTF calculated by `ltf()` and some statistics. █   NOTES  • As in several of our recent publications, this script uses secondsToTfString() to produce a timeframe string in timeframe.period format from a timeframe expressed in seconds.  • The script utilizes display.data_window and display.status_line to restrict the display of certain plots.   These new built-ins allow coders to fine-tune where a script’s plot values are displayed.  • We implement a new recommended best practice for tables which works faster and reduces memory consumption.   Using this new method, tables are declared only once with var , as usual. Then, on bar zero only, we use table.cell() calls to populate the table.   Finally, table.set_*() functions are used to update attributes of table cells on the last bar of the dataset.   This greatly reduces the resources required to render tables. We encourage all Pine Script™ programmers to do the same. Look first. Then leap. █   FUNCTIONS The library contains the following functions: ltf(userSelection, choice1, choice2, choice3, choice4, choice5, choice6, choice7, choice8)   Selects a ​LTF from the chart's TF, depending on the `userSelection` input string.   Parameters:      userSelection : (simple string) User-selected input string which must be one of the `choicex` arguments.      choice1 : (simple string) Input selection corresponding to "Least precise, covering most chart bars".      choice2 : (simple string) Input selection corresponding to "Less precise, covering some chart bars".      choice3 : (simple string) Input selection corresponding to "More precise, covering less chart bars".      choice4 : (simple string) Input selection corresponding to "Most precise, 1min intrabars".      choice5 : (simple string) Input selection corresponding to "~12 intrabars per chart bar".      choice6 : (simple string) Input selection corresponding to "~24 intrabars per chart bar".      choice7 : (simple string) Input selection corresponding to "~50 intrabars per chart bar".      choice8 : (simple string) Input selection corresponding to "~100 intrabars per chart bar".   Returns: (simple string) A timeframe string to be used with `request.security_lower_tf()`. ltfStats()   Returns statistics about analyzed intrabars and chart bars covered by calls to `request.security_lower_tf()`.   Parameters:      intrabarValues : (float [ ]) The ID of a float array containing values fetched by a call to `request.security_lower_tf()`.   Returns: A 3-element tuple: [ (series int) intrabarsInChartBar, (series int) chartBarsCovered, (series float) avgIntrabars ].
Pine Script® library
by PineCoders
16
Library CommonLibrary "LibraryCommon" A collection of custom tools & utility functions commonly used with my scripts @description TODO: add library description here getDecimals() Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price truncate(float, float) Truncates (cuts) excess decimal places   Parameters:      float : number The number to truncate      float : decimalPlaces (default=2) The number of decimal places to truncate to   Returns: The given number truncated to the given decimalPlaces toWhole(float) Converts pips into whole numbers   Parameters:      float : number The pip number to convert into a whole number   Returns: The converted number toPips(float) Converts whole numbers back into pips   Parameters:      float : number The whole number to convert into pips   Returns: The converted number getPctChange(float, float, int) Gets the percentage change between 2 float values over a given lookback period   Parameters:      float : value1 The first value to reference      float : value2 The second value to reference      int : lookback The lookback period to analyze av_getPositionSize(float, float, float, float) Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      float : balance The account balance to use      float : risk The risk percentage amount (as a whole number - eg. 1 = 1% risk)      float : stopPoints The stop loss distance in POINTS (not pips)      float : conversionRate The conversion rate of our account balance currency   Returns: The calculated position size (in units - only compatible with OANDA) bullFib(priceLow, priceHigh, fibRatio) Calculates a bullish fibonacci value   Parameters:      priceLow : The lowest price point      priceHigh : The highest price point      fibRatio : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio) Calculates a bearish fibonacci value   Parameters:      priceLow : The lowest price point      priceHigh : The highest price point      fibRatio : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(int, string) Gets a Moving Average based on type (MUST BE CALLED ON EVERY CALCULATION)   Parameters:      int : length The MA period      string : maType The type of MA   Returns: A moving average with the given parameters getEAP(float) Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      float : atr The given ATR to base the EAP SL calculation on   Returns: The EAP SL converted ATR size getEAP2(float) Performs secondary EAP stop loss size calculation (eg. ATR < 40, add 5 pips, ATR between 40-50, add 10 pips etc)   Parameters:      float : atr The given ATR to base the EAP SL calculation on   Returns: The EAP SL converted ATR size barsAboveMA(int, float) Counts how many candles are above the MA   Parameters:      int : lookback The lookback period to look back over      float : ma The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(int, float) Counts how many candles are below the MA   Parameters:      int : lookback The lookback period to look back over      float : ma The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(int, float) Counts how many times the EMA was crossed recently   Parameters:      int : lookback The lookback period to look back over      float : ma The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(int, int) Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      int : lookback The lookback period to look back over      int : direction The color of the bar to count (1 = Green, -1 = Red)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize() Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize() Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize() Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent() Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(float, bool) Checks if the current bar is a hammer candle based on the given parameters   Parameters:      float : fib (default=0.382) The fib to base candle body on      bool : colorMatch (default=false) Does the candle need to be green? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(float, bool) Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      float : fib (default=0.382) The fib to base candle body on      bool : colorMatch (default=false) Does the candle need to be red? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(float, bool) Checks if the current bar is a doji candle based on the given parameters   Parameters:      float : wickSize (default=2) The maximum top wick size compared to the bottom (and vice versa)      bool : bodySize (default=0.05) The maximum body size as a percentage compared to the entire candle size   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(float, float, bool) Checks if the current bar is a bullish engulfing candle   Parameters:      float : allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(float, float, bool) Checks if the current bar is a bearish engulfing candle   Parameters:      float : allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar() Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar() Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(string, bool) Determines if the current price bar falls inside the specified session   Parameters:      string : sess The session to check      bool : useFilter (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session barOutSession(string, bool) Determines if the current price bar falls outside the specified session   Parameters:      string : sess The session to check      bool : useFilter (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(int, int) Determines if this bar's time falls within date filter range   Parameters:      int : startTime The UNIX date timestamp to begin searching from      int : endTime the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(bool, bool, bool, bool, bool, bool, bool) Checks if the current bar's day is in the list of given days to analyze   Parameters:      bool : monday Should the script analyze this day? (true/false)      bool : tuesday Should the script analyze this day? (true/false)      bool : wednesday Should the script analyze this day? (true/false)      bool : thursday Should the script analyze this day? (true/false)      bool : friday Should the script analyze this day? (true/false)      bool : saturday Should the script analyze this day? (true/false)      bool : sunday Should the script analyze this day? (true/false)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter() fillCell()
Pine Script® library
by Wheeelman
2
CVD Zones & Divergence [Pro]# CVD Zones & Divergence **Complete CVD order flow toolkit** - Divergences, POC, Profile, and Supply/Demand zones all in one professional indicator. ## 🎯 What It Does Combines **four powerful order flow tools** into a single, cohesive indicator: 1. **CVD Divergences** - Early warnings + confirmed signals 2. **Point of Control (POC)** - Fair value equilibrium line 3. **CVD Profile** - Visual distribution histogram 4. **Supply/Demand Zones** - Real absorption-based S/R levels All based on **Cumulative Volume Delta (CVD)** - actual buying/selling pressure, not approximations. ## ✨ Key Features ### 🔄 CVD Divergences (Dual Mode) **Confirmed Divergences** (High Accuracy) - Solid lines (customizable colors) - 🔻 Bear / 🔺 Bull labels - Win rate: ~70-80% - Best for swing traders **Early Warning Mode** ⚡ (Fast Signals) - Dashed lines (default purple) - ⚠️ Early Bear / ⚠️ Early Bull labels - Fires 6+ bars earlier - Win rate: ~55-65% - Best for scalpers/day traders ### 🎯 Point of Control (POC) - **Independent lookback** (300 bars default) - Yellow line showing fair value - Where most CVD activity occurred - Acts as dynamic support/resistance - Resets and recalculates continuously ### 📊 CVD Profile Histogram - **Visual CVD distribution** over lookback period - **Split buy/sell** (blue/orange bars) - **Value Area** (70% CVD zone highlighted) - Position: Right/Left/Current (your choice) - Shows where actual order flow happened ### 📦 Supply/Demand Zones - **Absorption-based** detection (not guesses!) - Green = Demand (buyers absorbed 2:1+) - Red = Supply (sellers absorbed 2:1+) - Shows **real** institutional levels - Auto-sorted by strength - Displays top 8 zones ## 📊 What You See on Chart ``` Your Chart: ├─ 🔴 Red lines (bearish divergences) ├─ 🟢 Green lines (bullish divergences) ├─ 🟣 Purple dashed (early warnings) ├─ 🟡 Yellow POC line (fair value) ├─ 📊 Blue/Orange profile (right side) ├─ 🟢 Green boxes (demand zones) └─ 🔴 Red boxes (supply zones) ``` ## ⚙️ Recommended Settings ### 15m Day Trading (Most Popular) ``` 📊 Profile: - Lookback: 150 bars - Profile Rows: 24 - Position: Right 🎯 POC: - POC Lookback: 300 bars - Show POC: ON 📦 Zones: - Min Absorption Ratio: 2.0 - HVN Threshold: 1.5 - Max Zones: 8 🔄 Divergences: - Pivot L/R: 9 - Early Warning: ON - Early Right Bars: 3 - Min Bars Between: 40 - Min CVD Diff: 5% ``` ### 5m Scalping ``` Profile Lookback: 100 POC Lookback: 200 Pivot L/R: 7 Early Warning Right: 2 Min Bars Between: 60 ``` ### 1H Swing Trading ``` Profile Lookback: 200 POC Lookback: 400-500 Pivot L/R: 12-14 Early Warning Right: 4-5 Min Bars Between: 30 Min CVD Diff: 8% ``` ## 💡 How to Trade ### Setup 1: Divergence at Zone ⭐ (BEST - 75%+ win rate) **Entry:** - Price hits demand/supply zone - Divergence appears (early or confirmed) - Double confluence = high probability **Example (Long):** ``` 1. Price drops into green demand zone 2. ⚠️ Early bullish divergence fires 3. Enter long with tight stop below zone 4. Target: POC or next supply zone ``` **Risk/Reward:** 1:3 to 1:5 --- ### Setup 2: POC Bounce/Rejection **Entry:** - Price approaches POC line - Wait for reaction (bounce or rejection) - Enter in direction of reaction **Long Setup:** ``` 1. Price pulls back to POC from above 2. POC acts as support 3. Bullish divergence appears (confirmation) 4. Enter long, stop below POC ``` **Short Setup:** ``` 1. Price rallies to POC from below 2. POC acts as resistance 3. Bearish divergence appears 4. Enter short, stop above POC ``` **Risk/Reward:** 1:2 to 1:4 --- ### Setup 3: Zone + Profile Confluence **Entry:** - Supply/demand zone aligns with thick profile bar - Shows high CVD activity at that level - Triple confluence = very high probability **Example:** ``` 1. Supply zone at 26,100 2. Profile shows heavy selling at 26,100 3. Price rallies to 26,100 4. Bearish divergence appears 5. Enter short ``` **Risk/Reward:** 1:4 to 1:6 --- ### Setup 4: Early Warning Scalp ⚡ **Entry (Aggressive):** - ⚠️ Early warning fires - Price at zone or POC - Enter immediately - Tight stop (1-2 ATR) **Management:** ``` - Take 50% profit at 1:1 - Move stop to breakeven - 🔻 Confirmed signal → Trail stop - Exit rest at target ``` **Risk/Reward:** 1:1.5 to 1:2 **Trades/day:** 3-8 --- ### Setup 5: Multi-Timeframe (Advanced) **Confirmation Required:** ``` Higher TF (1H): - Confirmed divergence - At major POC or zone Lower TF (15m): - Early warning triggers - Entry with better timing ``` **Benefits:** - HTF gives direction - LTF gives entry - Best of both worlds **Risk/Reward:** 1:3 to 1:5 --- ## 📊 Component Details ### CVD Profile **What the colors mean:** - **Blue bars** = Buying CVD (demand) - **Orange bars** = Selling CVD (supply) - **Lighter shade** = Value Area (70% CVD) - **Thicker bar** = More volume at that price **How to use:** - Thick bars = Support/Resistance - Profile shape shows market structure - Balanced profile = range - Skewed profile = trend --- ### Supply/Demand Zones **How they're detected:** 1. High Volume Node (1.5x average) 2. CVD buy/sell ratio calculated 3. Ratio ≥ 2.0 → Zone created 4. Sorted by strength (top 8 shown) **Zone labels show:** - Type: "Demand" or "Supply" - Ratio: "2.8:1" = strength **Not like other indicators:** - ❌ Other tools use price action alone - ✅ This uses actual CVD absorption - Shows WHERE limit orders defended levels --- ### Point of Control (POC) **What it shows:** - Price with highest CVD activity - Market's "fair value" - Dynamic S/R level **How to use:** - Price above POC = bullish bias - Price below POC = bearish bias - POC retest = trading opportunity - POC cross = trend change signal **Independent lookback:** - Profile: 150 bars (short-term) - POC: 300 bars (longer-term context) - Gives stable, relevant POC --- ## 🔧 Settings Explained ### 📊 Profile Settings **Lookback Bars** (150 default) - How many bars for profile calculation - Lower = more recent, reactive - Higher = more historical, stable **Profile Rows** (24 default) - Granularity of distribution - Lower = coarser (faster) - Higher = finer detail (slower) **Profile Position** - Right: After current price - Left: Before lookback period - Current: At lookback start **Value Area** (70% default) - Highlights main CVD concentration - 70% is standard - Higher % = wider zone --- ### 🎯 POC Settings **POC Lookback** (300 default) - Independent from profile - Longer = more stable POC - Shorter = more reactive POC **Show POC Line/Label** - Toggle visibility - Customize color/width --- ### 📦 Zone Settings **Min Absorption Ratio** (2.0 default) - Buy/Sell threshold for zones - 2.0 = 2:1 ratio minimum - Higher = fewer, stronger zones **HVN Threshold** (1.5 default) - Volume must be 1.5x average - Higher = stricter filtering - Lower = more zones **Max Zones** (8 default) - Limits display clutter - Shows strongest N zones only --- ### 🔄 Divergence Settings **Pivot Left/Right** (9/9 default) - Bars to confirm pivot - Higher = slower, more confirmed - Lower = faster, less confirmed **Early Warning** - ON = Show early signals - Early Right Bars (3 default) - 3 = 6 bars faster than confirmed **Filters:** - Min Bars Between (40): Prevents spam - Min CVD Diff % (5): Filters weak signals **Visual:** - Line styles: Solid/Dashed/Dotted - Colors: Customize all 4 types - Labels: Toggle ON/OFF --- ## 🎨 Color Customization **Divergences:** - Bullish Confirmed: Green (default) - Bearish Confirmed: Red (default) - Early Bullish: Purple (default) - Early Bearish: Purple (default) **Zones & Profile:** - Bull/Demand: Green - Bear/Supply: Red - Buy CVD Profile: Blue - Sell CVD Profile: Orange - Value Area Up/Down: Lighter blue/orange **POC:** - POC Color: Yellow (default) All customizable to your preference! --- ## 🔔 Alerts Available **6 Alert Types:** 1. 🔻 Bearish Divergence (confirmed) 2. 🔺 Bullish Divergence (confirmed) 3. ⚠️ Early Bearish Warning 4. ⚠️ Early Bullish Warning 5. (Manual: POC cross) 6. (Manual: Zone touch) **Setup:** 1. Click Alert (⏰) 2. Choose "CVD Zones & Divergence" 3. Select alert type 4. Configure notification 5. Create! --- ## 💎 Pro Tips ### From Experienced Traders: **"Use zones with divergences for best setups"** - Zone alone: 60% win rate - Divergence alone: 65% win rate - Both together: 75%+ win rate **"POC is your friend"** - Price tends to revert to POC - Great target for counter-trend trades - POC cross = potential trend change **"Profile tells the story"** - Thick bars = institutional levels - Balanced profile = range-bound - Skewed high = distribution (top) - Skewed low = accumulation (bottom) **"Early warnings for entries, confirmed for confidence"** - Early = better entry price - Confirmed = validation - Use both in scale-in strategy **"Filter by timeframe"** - 1m-5m: Very fast, many signals - 15m: Sweet spot for most traders - 1H-4H: High quality, fewer signals --- ## 🔧 Tuning Guide ### Too Cluttered? **Simplify:** ``` ✅ Show Divergences: ON ✅ Show POC: ON ❌ Show Zones: OFF (or reduce to 4-5) ❌ Show Value Area: OFF ❌ Divergence Labels: OFF → Clean chart with just lines + POC ``` ### Missing Opportunities? **More Signals:** ``` ↓ Pivot Right: 6-7 ↓ Early Warning Right: 2 ↓ Min Bars Between: 25-30 ↓ Min CVD Diff: 2-3% ↓ Min Absorption Ratio: 1.8 ``` ### Too Many False Signals? **Stricter Filters:** ``` ↑ Pivot Right: 12-15 ↑ Min Bars Between: 60 ↑ Min CVD Diff: 8-10% ↑ Min Absorption Ratio: 2.5 ↓ Max Zones: 4-5 ``` ### POC Not Making Sense? **Adjust POC Lookback:** ``` If too high: Increase to 400-500 If too low: Increase to 400-500 If jumping around: Increase to 500+ → Longer lookback = more stable POC ``` --- ## ❓ FAQ **Q: Difference from CVD Divergence (standalone)?** A: This is the **complete package**: - Divergence tool = divergences only - This = divergences + POC + profile + zones - Use divergence tool for clean charts - Use this for full analysis **Q: Too slow/laggy?** A: Reduce computational load: ``` Profile Rows: 18 (from 24) Lookback: 100 (from 150) Max Zones: 5 (from 8) ``` **Q: No volume data error?** A: Symbol has no volume - Works: Futures, stocks, crypto - Maybe: Forex (broker-dependent) - Doesn't work: Some forex pairs **Q: Can I use just some features?** A: Absolutely! Toggle what you want: ``` Zones only: Turn off divergences + POC POC only: Turn off zones + divergences Divergences only: Turn off zones + POC + profile Mix and match as needed! ``` **Q: Best timeframe?** A: - **1m-5m**: Scalping (busy, many signals) - **15m**: Day trading ⭐ (recommended) - **1H-4H**: Swing trading (quality signals) - **Daily**: Position trading (very selective) **Q: Works on crypto/forex/stocks?** A: - ✅ Futures: Excellent - ✅ Stocks: Excellent - ✅ Crypto: Very good (major pairs) - ⚠️ Forex: Depends on broker volume --- ## 📈 Performance Expectations ### Realistic Win Rates | Strategy | Win Rate | Avg R/R | Trades/Week | |----------|----------|---------|-------------| | Early warnings only | 55-65% | 1:1.5 | 15-30 | | Confirmed only | 70-80% | 1:2 | 8-15 | | Divergence + Zone | 75-85% | 1:3 | 5-12 | | Full confluence (all 4) | 80-90% | 1:4+ | 3-8 | **Keys to success:** - Don't trade every signal - Wait for confluence - Proper risk management - Trade what you see, not what you think --- ## 🚀 Quick Start **New User (5 minutes):** 1. ✅ Add to 15m chart 2. ✅ Default settings work well 3. ✅ Watch for 1 week (don't trade yet!) 4. ✅ Note which setups work best 5. ✅ Backtest on 50+ signals 6. ✅ Start with small size 7. ✅ Scale up slowly **First Trade Checklist:** - Divergence + Zone/POC = confluence - Clear S/R level nearby - Risk/reward minimum 1:2 - Position size = 1% risk max - Stop loss placed - Target identified - Journal entry ready --- ## 📊 What Makes This Special? **Most indicators:** - Use RSI/MACD divergences (lagging) - Guess at S/R zones (subjective) - Don't show actual order flow **This indicator:** - Uses real CVD (actual volume delta) - Absorption-based zones (real orders) - Profile shows distribution (real activity) - POC shows equilibrium (real fair value) - All from one data source (coherent) **Result:** - Everything aligns - No conflicting signals - True order flow analysis - Professional-grade toolkit --- ## 🎯 Trading Philosophy **Remember:** - Indicator shows you WHERE to look - YOU decide whether to trade - Quality over quantity always - Risk management is #1 - Patience beats aggression **Best trades have:** - ✅ Multiple confluences - ✅ Clear risk/reward - ✅ Obvious invalidation point - ✅ Aligned with trend/context **Worst trades have:** - ❌ Single signal only - ❌ Poor location (middle of nowhere) - ❌ Unclear stop placement - ❌ Counter to all context --- ## ⚠️ Risk Disclaimer **Important:** - Past performance ≠ future results - All trading involves risk - Only risk what you can afford to lose - This is a tool, not financial advice - Use proper position sizing - Keep a trading journal - Consider professional advice **Your responsibility:** - Which setups to trade - Position size - Entry/exit timing - Risk management - Emotional control **Success = Tool + Strategy + Discipline + Risk Management** --- ## 📝 Version History **v1.0** - Current Release - CVD divergences (confirmed + early warning) - Point of Control (independent lookback) - CVD profile histogram - Supply/demand absorption zones - Value area visualization - 6 alert types - Full customization --- ## 💬 Community **Questions?** Drop a comment below **Success story?** Share with the community **Feature request?** Let me know **Bug report?** Provide details in comments --- **Happy Trading! 🚀📊** *Professional order flow analysis in one indicator.* **Like this?** ⭐ Follow for more quality tools!
Pine Script® indicator
by kb1ath
Iridescent Liquidity Prism [JOAT]Iridescent Liquidity Prism | Peer Momentum HUD A multi-layered order-flow indicator that combines microstructure analysis, smart-money footprint detection, and intermarket momentum signals. The script uses dynamic color-shifting themes to visualize liquidity patterns, structure, and peer momentum data directly on the chart. There is so much to choose from inside the settings, if you think it's a mess on the chart it's because you have to personally customize it based on your needs... Core Functionality The indicator calculates and displays several analytical layers simultaneously: Order-Flow Imbalance (OFI): Calculates buy vs. sell volume pressure using volume-weighted price distribution within each bar. Uses an EMA filter (default: 55 periods) to smooth the signal. Values are normalized using standard deviation to identify significant imbalances. Smart Money Footprints: Detects accumulation and distribution zones by comparing volume rate of change (ROC) against price ROC. When volume ROC exceeds a threshold (default: 65%) and price ROC is positive, accumulation is detected. When volume ROC is high but price ROC is negative, distribution is detected. Fractal Structure Mapping: Identifies pivot highs and lows using a fractal detection algorithm (default: 5-bar period). Maintains a rolling window of recent structure points (default: 4 levels) and draws connecting lines to show trend structure. Fair Value Gap (FVG) Detection: Automatically detects price gaps where three consecutive candles create an imbalance. Bullish FVGs occur when the current low exceeds the high two bars ago. Bearish FVGs occur when the current high is below the low two bars ago. Gaps persist for a configurable duration (default: 320 bars) and fade when price fills the gap. Liquidity Void Detection: Identifies candles where the high-low range exceeds an ATR threshold (default: 1.7x ATR) while volume is below average (default: 65% of 20-bar average). These conditions suggest areas where liquidity may be thin. Price/Volume Divergence: Uses linear regression to detect when price trend direction disagrees with volume trend direction. A divergence alert appears when price is trending up while volume is trending down, or vice versa. Peer Momentum Heatmap (PMH): Calculates composite momentum scores for up to 6 symbols across 4 timeframes. Each score combines RSI (default: 14 periods) and StochRSI (default: 14 periods, 3-bar smooth) to create a momentum composite between -1 and +1. The highest absolute momentum score across all combinations is displayed in the HUD. Custom settings using Fractal Pivots, Skeleton Structure, Pulse Liquidity Voids, Bottom Colorful HeatMaps, and Iridescent Field. --- Visual Components Spectrum Aura Glow: ATR-weighted bands (default: 0.25x ATR) that expand and contract around price action, indicating volatility conditions. The thickness adapts to market volatility. Chromatic Flow Trail: A blended line combining EMA and WMA of price (default: 8-period EMA blended with WMA at 65% ratio). The trail uses gradient colors that shift based on a phase oscillator, creating an iridescent effect. Volume Heat Projection: Creates horizontal volume profile bands at price levels (default: 14 levels). Scans recent bars (default: 150 bars) to calculate volume concentration. Each level is colored based on its volume density relative to the maximum volume level. Structure Skeleton: Dashed lines connecting fractal pivot points. Uses two layers: a primary line (2-3px width) and an optional glow overlay (4-5px width) for enhanced visibility. Fractal Markers: Diamond shapes placed at pivot high and low points. Color-coded: primary color for highs, secondary color for lows. Iridescent Color Themes: Five color themes available: Iridescent (default), Pearlescent, Prismatic, ColorShift, and Metallic. Colors shift dynamically using a phase oscillator that cycles through the color spectrum based on bar index and a speed multiplier (default: 0.35). --- HUD Console Metrics The right-side HUD displays seven key metrics: Flow: Shows OFI status: ▲ FLOW BUY when normalized OFI exceeds imbalance threshold (default: 2.2), ▼ FLOW SELL when below -2.2, or ◆ FLOW BAL when balanced. Struct: Structure trend bias: ▲ STRUCT BULL when microtrend > 2, ▼ STRUCT BEAR when < -2, or ◆ STRUCT RANGE when neutral. Smart$: Institutional activity: ◈ ACCUM when smart money index = 1, ◈ DISTRIB when = -1, or ○ IDLE when inactive. Liquid: Liquidity state: ⚡ VOID when a liquidity void is detected, or ● NORMAL otherwise. Diverg: Divergence status: ⚠ ALERT when price/volume divergence detected, or ✓ CLEAR when aligned. PMH: Peer Momentum Heatmap status: Shows dominant timeframe and momentum score. Displays 🪩 for bull surge (above 0.55 threshold) or 🧨 for bear surge (below -0.55). FVG: Fair Value Gap status: Shows active gap count or CLEAR when no gaps exist. Displays GAP LONG when bullish gap detected, GAP SHORT when bearish gap detected. Pearlscent Color with Volume Heatmap. Parameters and Settings Microstructure Engine: Analysis Depth: 20-250 bars (default: 55) - Controls OFI smoothing period Liquidity Threshold ATR: 1.0-4.0 (default: 1.7) - Multiplier for void detection Imbalance Ratio: 1.5-6.0 (default: 2.2) - Standard deviations for OFI significance Smart Money Layer: Smart Money Window: 10-150 bars (default: 24) - Period for ROC calculations Accumulation Threshold: 40-95% (default: 65%) - Volume ROC threshold Structural Mapping: Fractal Pivot Period: 3-15 bars (default: 5) - Period for pivot detection Structure Memory: 2-8 levels (default: 4) - Number of structure points to track Volume Heat Projection: Heat Map Lookback: 60-400 bars (default: 150) - Bars to analyze for volume profile Heat Map Levels: 5-30 levels (default: 14) - Number of price level bands Heat Map Opacity: 40-100% (default: 92%) - Transparency of heat map boxes Heat Map Width Limit: 6-80 bars (default: 26) - Maximum width of heat map boxes Heat Map Visibility Threshold: 0.0-0.5 (default: 0.08) - Minimum density to display Iridescent Enhancements: Visual Theme: Iridescent, Pearlescent, Prismatic, ColorShift, or Metallic Color Shift Speed: 0.05-1.00 (default: 0.35) - Speed of color phase oscillation Aura Thickness (ATR): 0.05-1.0 (default: 0.25) - Multiplier for aura band width Chromatic Trail Length: 2-50 bars (default: 8) - Period for trail calculation Trail Blend Ratio: 0.1-0.95 (default: 0.65) - EMA/WMA blend percentage FVG Persistence: 50-600 bars (default: 320) - Bars to keep FVG boxes active Max Active FVG Boxes: 10-200 (default: 40) - Maximum boxes on chart FVG Base Opacity: 20-95% (default: 80%) - Transparency of FVG boxes Peer Momentum Heatmap: Peer Symbols: Comma-separated list of up to 6 symbols (e.g., "BTCUSD,ETHUSD") Peer Timeframes: Comma-separated list of up to 4 timeframes (default: "60,240,D") PMH RSI Length: 5-50 periods (default: 14) PMH StochRSI Length: 5-50 periods (default: 14) PMH StochRSI Smooth: 1-10 periods (default: 3) Super Momentum Threshold: 0.2-0.95 (default: 0.55) - Threshold for surge detection Clarity & Readability: Liquidity Void Opacity: 5-90% (default: 30%) Smart Money Footprint Opacity: 5-90% (default: 35%) HUD Background Opacity: 40-95% (default: 70%) Iridescent Field: Field Opacity: 20-100% (default: 86%) - Background color intensity Field Smooth Length: 10-200 bars (default: 34) - Smoothing for background gradient --- Alerts The indicator provides seven alert conditions: Liquidity Void Detected - Triggers when void conditions are met Strong Order Flow - Triggers when normalized OFI exceeds imbalance ratio Smart Money Activity - Triggers when accumulation or distribution detected Price/Volume Divergence - Triggers when divergence conditions occur Structure Shift - Triggers when structure polarity changes significantly PMH Bull Surge - Triggers when PMH exceeds positive threshold (if enabled) PMH Bear Surge - Triggers when PMH exceeds negative threshold (if enabled) Bull/Bear Prismatic FVG - Triggers when new FVG is detected (if FVG display enabled) --- Usage Considerations Performance may vary on lower timeframes due to the volume heat map calculations scanning multiple bars. Consider reducing heat map lookback or levels if experiencing slowdowns. The PMH feature requires data requests to other symbols/timeframes, which may impact performance. Limit the number of peer symbols and timeframes for optimal performance. FVG boxes automatically expire after the persistence period to prevent chart clutter. The maximum box limit (default: 40) prevents excessive memory usage. Color themes affect all visual elements. Choose a theme that provides good contrast with your chart background. The indicator is designed for overlay display. All visual elements are positioned relative to price action. Structure lines are drawn dynamically as new pivots form. On fast-moving markets, structure may update frequently. Volume calculations assume typical volume data availability. Symbols without volume may show incomplete data for volume-dependent features. --- Technical Notes Built on Pine Script v6 with dynamic request capability for PMH functionality. Uses exponential moving averages (EMA) and weighted moving averages (WMA) for trail calculations to balance responsiveness and smoothness. Volume profile calculation uses price level buckets. Higher levels provide finer granularity but require more computation. Iridescent color engine uses a phase oscillator with sine wave calculations for smooth color transitions. Box management includes automatic cleanup of expired boxes to maintain performance. All visual elements use color gradients and transparency for smooth blending with price action. --- Customization Examples Intraday Scalping Setup: Analysis Depth: 30 bars Heat Map Lookback: 100 bars FVG Persistence: 150 bars PMH Window: 15 bars Fast color shift speed: 0.5+ Macro Structure Tracking: Analysis Depth: 100+ bars Heat Map Lookback: 300+ bars FVG Persistence: 500+ bars Structure Memory: 6-8 levels Slower color shift speed: 0.2 --- Limitations Volume heat map calculations may be computationally intensive on lower timeframes with high lookback values. PMH requires valid symbol names and accessible timeframes. Invalid symbols or timeframes will return no data. FVG detection requires at least 3 bars of history. Early bars may not show FVG boxes. Structure lines connect points but do not predict future structure. They reflect historical pivot relationships. Color themes are aesthetic choices and do not affect calculation logic. The indicator does not provide trading signals. All visual elements are analytical tools that require interpretation in context of market conditions. Open Source This indicator is open source and available for modification and distribution. The code is published with Pine Script v6 compliance. Users are free to customize parameters, modify calculations, and adapt the visual elements to their trading needs. For questions, suggestions, or anything please talk to me in private messages or comments below! Would love to help! - officialjackofalltrades
Pine Script® indicator
by officialjackofalltrades
1
Simple Candle Strategy# Candle Pattern Strategy - Pine Script V6 ## Overview A TradingView trading strategy script (Pine Script V6) that identifies candlestick patterns over a configurable lookback period and generates trading signals based on pattern recognition rules. ## Strategy Logic The strategy analyzes the most recent N candlesticks (default: 5) and classifies their patterns into three categories, then generates buy/sell signals based on specific pattern combinations. ### Candlestick Pattern Classification Each candlestick is classified as one of three types: | Pattern | Definition | Formula | |---------|-----------|---------| | **Close at High** | Close price near the highest price of the candle | `(high - close) / (high - low) ≤ (1 - threshold)` | | **Close at Low** | Close price near the lowest price of the candle | `(close - low) / (high - low) ≤ (1 - threshold)` | | **Doji** | Opening and closing prices very close; long upper/lower wicks | `abs(close - open) / (high - low) ≤ threshold` | ### Trading Rules | Condition | Action | Signal | |-----------|--------|--------| | Number of Doji candles ≥ 3 | **SKIP** - Market is too chaotic | No trade | | "Close at High" count ≥ 2 + Last candle closes at high | **LONG** - Bullish confirmation | Buy Signal | | "Close at Low" count ≥ 2 + Last candle closes at low | **SHORT** - Bearish confirmation | Sell Signal | ## Configuration Parameters All parameters are adjustable in TradingView's "Settings/Inputs" tab: | Parameter | Default | Range | Description | |-----------|---------|-------|-------------| | **K-line Lookback Period** | 5 | 3-20 | Number of candlesticks to analyze | | **Doji Threshold** | 0.1 | 0.0-1.0 | Body size / Total range ratio for doji identification | | **Doji Count Limit** | 3 | 1-10 | Number of dojis that triggers skip signal | | **Close at High Proximity** | 0.9 | 0.5-1.0 | Required proximity to highest price (0.9 = 90%) | | **Close at Low Proximity** | 0.9 | 0.5-1.0 | Required proximity to lowest price (0.9 = 90%) | ### Parameter Tuning Guide #### Proximity Thresholds (Close at High/Low) - **0.95 or higher**: Stricter - only very strong candles qualify - **0.90 (default)**: Balanced - good for most market conditions - **0.80 or lower**: Looser - catches more patterns, higher false signals #### Doji Threshold - **0.05-0.10**: Strict doji identification - **0.10-0.15**: Standard doji detection - **0.15+**: Includes near-doji patterns #### Lookback Period - **3-5 bars**: Fast, sensitive to recent patterns - **5-10 bars**: Balanced approach - **10-20 bars**: Slower, filters out noise ## Visual Indicators ### Chart Markers - **Green Up Arrow** ▲: Long entry signal triggered - **Red Down Arrow** ▼: Short entry signal triggered - **Gray X**: Skip signal (too many dojis detected) ### Statistics Table Located at top-right corner, displays real-time pattern counts: - **Close at High**: Count of candles closing near the high - **Close at Low**: Count of candles closing near the low - **Doji**: Count of doji/near-doji patterns ### Signal Labels - Green label: "✓ Long condition met" - below entry bar - Red label: "✓ Short condition met" - above entry bar - Gray label: "⊠ Too many dojis, skip" - trade skipped ## Risk Management ### Exit Strategy The strategy includes built-in exit rules based on ATR (Average True Range): - **Stop Loss**: ATR × 2 - **Take Profit**: ATR × 3 Example: If ATR is $10, stop loss is at -$20 and take profit is at +$30 ### Position Sizing Default: 100% of equity per trade (adjustable in strategy properties) **Recommendation**: Reduce to 10-25% of equity for safer capital allocation ## How to Use ### 1. Copy the Script 1. Open TradingView 2. Go to Pine Script Editor 3. Create a new indicator 4. Copy the entire `candle_pattern_strategy.pine` content 5. Click "Add to Chart" ### 2. Apply to Chart - Select your preferred timeframe (1m, 5m, 15m, 1h, 4h, 1d) - Choose a trading symbol (stocks, forex, crypto, etc.) - The strategy will generate signals on all historical bars and in real-time ### 3. Configure Parameters 1. Right-click the strategy on chart → "Settings" 2. Adjust parameters in the "Inputs" tab 3. Strategy will recalculate automatically 4. Backtest results appear in the Strategy Tester panel ### 4. Backtesting 1. Click "Strategy Tester" (bottom panel) 2. Set date range for historical testing 3. Review performance metrics: - Win rate - Profit factor - Drawdown - Total returns ## Key Features ✅ **Execution Model Compliant** - Follows official Pine Script V6 standards ✅ **Global Scope** - All historical references in global scope for consistency ✅ **Adjustable Sensitivity** - Fine-tune all pattern detection thresholds ✅ **Real-time Updates** - Works on both historical and real-time bars ✅ **Visual Feedback** - Clear signals with labels and statistics table ✅ **Risk Management** - Built-in ATR-based stop loss and take profit ✅ **No Repainting** - Signals remain consistent after bar closes ## Important Notes ### Before Trading Live 1. **Backtest thoroughly**: Test on at least 6-12 months of historical data 2. **Paper trading first**: Practice with simulated trades 3. **Optimize parameters**: Find the best settings for your trading instrument 4. **Manage risk**: Never risk more than 1-2% per trade 5. **Monitor performance**: Review trades regularly and adjust as needed ### Market Conditions The strategy works best in: - Trending markets with clear directional bias - Range-bound markets with defined support/resistance - Markets with moderate volatility The strategy may underperform in: - Highly choppy/noisy markets (many false signals) - Markets with gaps or overnight gaps - Low liquidity periods ### Limitations - Works on chart timeframes only (not intrabar analysis) - Requires at least 5 bars of history (configurable) - Fixed exit rules may not suit all trading styles - No trend filtering (will trade both directions) ## Technical Details ### Historical Buffer Management The strategy declares maximum bars back to ensure enough historical data: ```pine max_bars_back(close, 20) max_bars_back(open, 20) max_bars_back(high, 20) max_bars_back(low, 20) ``` This prevents runtime errors when accessing historical candlestick data. ### Pattern Detection Algorithm ``` For each bar in lookback period: 1. Calculate (high - close) / (high - low) → close_to_high_ratio 2. If close_to_high_ratio ≤ (1 - threshold) → count as "Close at High" 3. Calculate (close - low) / (high - low) → close_to_low_ratio 4. If close_to_low_ratio ≤ (1 - threshold) → count as "Close at Low" 5. Calculate abs(close - open) / (high - low) → body_ratio 6. If body_ratio ≤ doji_threshold → count as "Doji" Signal Generation: 7. If doji_count ≥ cross_count_limit → SKIP_SIGNAL 8. If close_at_high_count ≥ 2 AND last_close_at_high → LONG_SIGNAL 9. If close_at_low_count ≥ 2 AND last_close_at_low → SHORT_SIGNAL ``` ## Example Scenarios ### Scenario 1: Bullish Signal ``` Last 5 bars pattern: Bar 1: Closes at high (95%) ✓ Bar 2: Closes at high (92%) ✓ Bar 3: Closes at mid (50%) Bar 4: Closes at low (10%) Bar 5: Closes at high (96%) ✓ (last bar) Result: - Close at high count: 3 (≥ 2) ✓ - Last closes at high: ✓ - Doji count: 0 (< 3) ✓ → LONG SIGNAL ✓ ``` ### Scenario 2: Skip Signal ``` Last 5 bars pattern: Bar 1: Doji pattern ✓ Bar 2: Doji pattern ✓ Bar 3: Closes at mid Bar 4: Doji pattern ✓ Bar 5: Closes at high Result: - Doji count: 3 (≥ 3) → SKIP SIGNAL - Market too chaotic ``` ## Performance Optimization ### Tips for Better Results 1. **Use Higher Timeframes**: 15m or higher reduces false signals 2. **Combine with Indicators**: Add volume or trend filters 3. **Seasonal Adjustment**: Different parameters for different seasons 4. **Instrument Selection**: Test on liquid, high-volume instruments 5. **Regular Rebalancing**: Adjust parameters quarterly based on performance ## Troubleshooting ### No Signals Generated - Check if lookback period is too large - Verify proximity thresholds aren't too strict (try 0.85 instead of 0.95) - Ensure doji limit allows for trading (try 4-5 instead of 3) ### Too Many False Signals - Increase proximity thresholds to 0.95+ - Reduce lookback period to 3-4 bars - Increase doji limit to 3-4 - Test on higher timeframes ### Strategy Tester Shows Losses - Review individual trades to identify patterns - Adjust stop loss and take profit ratios - Change lookback period and thresholds - Test on different market conditions ## References - (www.tradingview.com) - (www.tradingview.com) - (www.investopedia.com) - (www.investopedia.com) ## Disclaimer **This strategy is provided for educational and research purposes only.** - Not financial advice - Past performance does not guarantee future results - Always conduct thorough backtesting before live trading - Trading involves significant risk of loss - Use proper risk management and position sizing ## License Created: December 15, 2025 Version: 1.0 --- **For updates and modifications, refer to the accompanying documentation files.**
Pine Script® strategy
by masteraux101
Luxy VWAP Magic - MTF Projection EngineThis indicator transforms the classic VWAP into a comprehensive trading system. Instead of switching between multiple indicators, you get everything in one place: multi-timeframe analysis, statistical bands, momentum detection, volume profiling, session tracking, and divergence signals. What Makes This Different Traditional VWAP indicators show a single line. This tool treats VWAP as a foundation for complete market analysis. The indicator automatically detects your asset type (stocks, crypto, forex, futures) and adjusts its behavior accordingly. Crypto traders get 24/7 session tracking. Stock traders get proper market hours handling. Everyone gets institutional-grade analytics. Anchor Period Options The anchor period determines when VWAP resets and recalculates. You have three categories of options: Time-Based Anchors: Session - Resets at market open. Best for intraday stock trading where you want fresh VWAP each day. Day - Resets at midnight UTC. Standard option for most traders. Week / Month / Quarter / Year - Longer reset periods for swing traders and position traders who want broader context. Rolling Window Anchors: Rolling 5D - A sliding 5-day window that never resets. Solves the Monday problem where weekly VWAP equals daily VWAP on first day of week. Rolling 21D - Approximately one month of trading data in continuous calculation. Excellent for crypto and forex markets that trade 24/7 without clear session breaks. Event-Based Anchors: Dividends - Resets on ex-dividend dates. Track institutional cost basis from dividend events. Splits - Resets on stock split dates. Useful for analyzing post-split trading behavior. Earnings - Resets on earnings report dates. See where volume-weighted trading occurred since last quarterly report. Standard Deviation Bands Three sets of bands surround the main VWAP line: Band 1 (Aqua) - Plus and minus one standard deviation. Approximately 68% of price action occurs within this range under normal distribution. Touches suggest minor extension. Band 2 (Fuchsia) - Plus and minus two standard deviations. Only 5% of trading should occur outside this range statistically. Touches here indicate significant overextension and high probability of mean reversion. Band 3 (Purple) - Plus and minus three standard deviations. Touches are rare (0.3% probability) and represent extreme conditions. Often marks climax moves or panic selling/buying. Each band can be toggled independently. Most traders show Band 1 by default and add Band 2 and 3 for specific setups or volatile instruments. Multi-Timeframe VWAP System The MTF section plots previous period VWAPs as horizontal support and resistance levels: Daily VWAP - Previous day's final VWAP value. Key intraday reference level. Weekly VWAP - Previous week's final VWAP. Important for swing traders. Monthly VWAP - Previous month's final VWAP. Institutional benchmark level. Quarterly VWAP - Previous quarter's final VWAP. Major support/resistance for position traders. Previous Day VWAP - Yesterday's closing VWAP specifically, separate from current daily calculation. The Confluence Zone percentage setting determines how close multiple VWAPs must be to trigger a confluence alert. When two or more timeframe VWAPs converge within this threshold, you get a high-probability support/resistance zone. Session VWAPs for Global Markets For forex, crypto, and futures traders who operate in 24/7 markets, the indicator tracks three major global sessions: Asia Session - UTC 21:00 to 08:00. Gold colored line. Typically lower volatility, range-bound action that sets overnight levels. London Session - UTC 08:00 to 17:00. Orange colored line. Often determines daily direction with high volume European participation. New York Session - UTC 13:00 to 22:00. Blue colored line. Highest volume session globally. Sharp directional moves common. Previous session VWAP values display as horizontal lines when each session closes, acting as intraday support and resistance. The table shows which sessions are currently active with checkmarks. On-Chart Labels and Signals The indicator plots several types of labels directly on price action when significant events occur: Volume Spike Labels Fire when current bar volume exceeds configurable thresholds relative to both the previous bar and the 20-bar average. Default settings require 300% of previous bar AND 200% of average volume. Green labels indicate bullish candles. Red labels indicate bearish candles. These spikes often mark institutional entry points. Momentum Shift Labels Appear when VWAP acceleration changes direction. The Slowing label warns when an active trend loses steam, often preceding reversal. The Accelerating label confirms trend continuation or potential bottom during downtrends. Filters available to show only reversal signals in existing trends. VWAP Squeeze Labels Detect when standard deviation bands contract relative to ATR (Average True Range). Low volatility compression often precedes explosive breakout moves. When the squeeze fires (releases), a label appears with directional prediction based on VWAP slope. Divergence Labels Mark price/volume divergences using CVD (Cumulative Volume Delta) analysis: Bullish divergence: Price makes lower low, but CVD makes higher low. Hidden accumulation despite price weakness. Bearish divergence: Price makes higher high, but CVD makes lower high. Hidden distribution despite price strength. Dynamic VWAP Coloring The main VWAP line changes color based on its slope direction: Green - VWAP is rising. Institutional buying pressure. Volume-weighted price increasing. Red - VWAP is falling. Institutional selling pressure. Volume-weighted price decreasing. Gray - VWAP is flat. Consolidation or balance between buyers and sellers. This coloring can be disabled for a static blue line if you prefer cleaner visuals. The VWAP label next to the line shows the current trend direction and delta percentage. Calculated Projection Cone One of the most powerful features is the Calculated Projection Cone. Unlike traditional extrapolation methods that simply extend a trend line forward, this system analyzes what actually happened in similar market conditions throughout the chart's history. How It Works: The system classifies each bar into one of 27 unique market states: Z-Score Level - LOW (oversold), MID (fair value), or HIGH (overbought) based on configurable thresholds Trend Direction - DOWN, FLAT, or UP based on VWAP slope Volume Profile - LOW (below 80%), NORMAL (80-150%), or HIGH (above 150%) relative volume When you look at the current bar, the indicator: 1. Identifies the current market state (e.g., LOW Z-Score + UP Trend + HIGH Volume) 2. Searches through all historical bars on the chart that had the same state 3. Calculates what happened in those bars X bars later (where X is your projection horizon) 4. Shows you the probability of up/down and the average move size Visual Elements: Probability Cone - Colored green (bullish probability above 55%), red (bearish below 45%), or gold (neutral). The cone width represents the historical range of outcomes (roughly the 20th to 80th percentile). Center Line - Shows the average expected price based on historical outcomes in similar conditions. Probability Label - Displays direction probability and average move. Example: "67% UP (+0.8%)" means 67% of similar past cases moved up, averaging 0.8% gain. Fallback System: When the exact 27-state match has insufficient historical data: First fallback: Uses Z-Score plus Trend only (9 broader states, ignoring volume) Second fallback: Uses Z-Score only (3 states) When fallback is active, confidence automatically adjusts Settings: Projection Horizon - How many bars forward to analyze outcomes (5, 10, 15, or 20 bars, default 10) Lookback Period - Historical data window in days (30-252, default 60) Minimum Samples - Cases needed before using fallback (5-30, default 10) Z-Score Threshold - Bucket boundary for LOW/MID/HIGH classification (1.0, 1.5, or 2.0 sigma) Cloud Transparency - Adjust visibility (50-95%) Colors - Customize bullish, bearish, and neutral cone colors Confidence Levels: HIGH - 30 or more similar historical cases found MEDIUM - 15-29 similar cases LOW - Fewer than 15 cases (more uncertainty) IMPORTANT DISCLAIMER: The Calculated Projection is based on past patterns only. It is NOT a price prediction or financial advice. Similar market states in the past do not guarantee similar outcomes in the future. The probability shown is historical frequency, not a guarantee. Always combine with other analysis and never rely solely on projections for trading decisions. Alert Conditions The indicator includes over 20 pre-built alert conditions: Price vs VWAP: Price crosses above VWAP Price crosses below VWAP Band Touches: Price touches plus or minus one sigma band Price touches plus or minus two sigma band (extreme) Price touches plus or minus three sigma band (very extreme) Z-Score Extremes: Z-Score crosses above plus two (overbought extreme) Z-Score crosses below minus two (oversold extreme) Momentum and Trend: Momentum slowing Momentum accelerating Trend turns bullish/bearish/neutral Volume: Volume spike detected CVD Direction: Buyers take control Sellers take control High Probability Signals: Bullish reversal signal (oversold plus accelerating momentum) Bearish reversal signal (overbought plus slowing momentum) MTF and Special: MTF confluence zone entry VWAP squeeze fired Bullish/Bearish divergence detected Any significant signal (catch-all) All signals use confirmed bar data to prevent false alerts from incomplete candles. Settings Overview Settings are organized into logical groups: VWAP Settings Anchor Period selection Show/Hide VWAP line Dynamic coloring toggle VWAP label visibility Bands Visibility Toggle each of three bands independently Info Table Show/Hide table Table position (9 options) Text size Volume spike label settings with adjustable thresholds Momentum label settings with filters Signal labels limited to 5 most recent (auto-managed) Probability engine lookback period Multi-Timeframe VWAP Enable/Disable MTF system Show MTF in table Show MTF lines on chart Individual timeframe toggles Confluence zone threshold Squeeze detection toggle Session VWAPs Enable/Disable session tracking Apply to all assets option Show session labels Divergence Detection Enable/Disable divergence Pivot lookback period Show divergence labels Calculated Projection Enable/Disable projection cone Projection horizon (5, 10, 15, or 20 bars) Lookback period in days (30-252) Minimum samples threshold Z-Score classification threshold (1.0, 1.5, or 2.0 sigma) Cloud transparency adjustment Bullish, bearish, and neutral colors The Info Table - Your Trading Dashboard The right side of your chart displays a compact table with up to twelve metrics. Row-by-Row Breakdown: Asset and Period - Shows what the indicator detected (US Stock, Crypto, Forex, etc.) and your selected anchor period. The detection happens automatically based on exchange data, so VWAP resets and calculations match your actual trading instrument. Delta Percentage - How far current price sits from VWAP, expressed as a percentage. Positive means price trades above fair value. Negative means below. Large delta values (beyond 1-2%) often precede mean reversion moves. Day traders watch this for overextension. Z-Score - Statistical deviation from VWAP measured in standard deviations. Unlike raw delta, Z-Score accounts for volatility. A 2% move in a volatile biotech stock differs from 2% in a stable utility. Z-Score normalizes this. Values beyond plus or minus two sigma occur only 5% of the time statistically. Trend Direction - Whether VWAP itself is rising, falling, or flat. Rising VWAP means the volume-weighted average price is increasing, which indicates institutional accumulation. Falling VWAP suggests distribution. This differs from price trend since it weights by volume. Momentum State - Is the trend accelerating or slowing down? This measures the rate of change in VWAP slope. When an uptrend shows slowing momentum, it often precedes reversal. Accelerating momentum in a downtrend can signal capitulation and potential bottom. Relative Volume - Current bar volume compared to the 20-bar average, shown as percentage. Values above 150% indicate above-average activity. Spikes above 200-300% often mark institutional involvement. Low volume (below 80%) warns of potential fake moves. MTF Bias - Four checkmarks or X marks showing whether price sits above or below Daily, Weekly, Monthly, and Quarterly VWAP. Four checkmarks means strong bullish alignment across all timeframes. Four X marks indicates bearish alignment. Mixed readings suggest consolidation or transition. Band Probabilities - Historical statistics showing how often price touched each standard deviation band over your lookback period. This helps you understand if mean reversion or trend following works better for your specific instrument. Session Status - Which global trading sessions are currently active (Asia, London, New York). Shows checkmarks for active sessions. Important for forex and crypto traders who need to know when major liquidity windows open and close. Divergence State - Whether the indicator detects bullish or bearish divergence between price and cumulative volume delta. Bullish divergence occurs when price makes lower lows but buying pressure (CVD) makes higher lows, suggesting hidden accumulation. Confidence Score - A weighted composite of all factors displayed as a progress bar and percentage. Combines MTF alignment, Z-Score, trend direction, volume delta, momentum, and relative volume into a single 0-100 score. Higher scores indicate stronger conviction setups. Calculated Projection - When the Projection Cone is enabled, shows the historical probability of price direction and expected move. For example: "▲ 67% (+0.8%)" means in similar market states historically, price moved up 67% of the time with an average gain of 0.8%. The system analyzes 27 unique market states based on Z-Score, Trend, and Volume conditions. Recommended Use Cases Day Trading Stocks: Use Session anchor with Band 1 visible. Watch for price returning to VWAP after morning move. Volume spikes near VWAP often mark institutional accumulation zones. Swing Trading: Use Weekly or Rolling 21D anchor. Enable MTF lines for Daily and Weekly levels. Trade pullbacks to these levels in direction of MTF bias. Crypto and Forex: Enable Session VWAPs. Use Rolling anchors to avoid artificial resets. Monitor session transitions for breakout opportunities. Mean Reversion: Focus on Z-Score reaching plus or minus two. Add Band 2 visibility. Combine with slowing momentum for highest probability reversals. Trend Following: Watch MTF bias alignment. Four checkmarks plus accelerating momentum plus high volume confirms trend continuation setups. Projection Planning: Enable the Calculated Projection to see what happened historically in similar market conditions. Use 5-10 bars for intraday setups, 15-20 bars for swing trade planning. Focus on high probability readings (above 60%) with HIGH confidence (30 or more samples). The cone shows the probable range of outcomes based on actual historical data. Combine with other factors like MTF alignment and volume for higher conviction setups. Important Notes The indicator does not repaint. MTF values use previous period's confirmed data. Rolling VWAP works best on 15-minute timeframes and above due to bar lookback requirements. Session VWAPs apply to global markets by default (forex, crypto, futures). Enable the all-assets option for stocks if desired. Volume data for forex represents tick volume, not actual traded volume. All alert conditions fire only on confirmed (closed) bars to prevent false signals. The Calculated Projection updates each bar as market state changes. This is expected behavior. The projection shows probabilities based on similar past conditions, not a fixed prediction. Q AND A Q: Does this indicator repaint? A: No. The main VWAP calculation uses standard TradingView VWAP methodology. Multi-timeframe values use previous period's confirmed data with appropriate lookahead settings. All alert signals require bar confirmation. Q: Why does my Rolling VWAP look different on 1-minute versus 15-minute charts? A: Rolling VWAP calculates across a fixed number of trading days. On very short timeframes, the bar lookback may hit TradingView limits. For best Rolling VWAP accuracy, use 15-minute or higher timeframes. Q: Can I use this on any instrument? A: Yes. The indicator automatically detects asset type and adjusts behavior. Stocks use standard market hours. Crypto uses 24/7 calculations. Forex uses tick volume. Everything adapts automatically. Q: What does the Confidence Score actually measure? A: The score combines six weighted factors: MTF alignment (25%), Z-Score position (20%), Trend direction (20%), CVD pressure (15%), Momentum state (10%), and Relative volume (10%). Higher scores indicate more factors aligned in one direction. Q: Why are Session VWAPs not showing on my stock chart? A: Session VWAPs apply to 24-hour markets by default (forex, crypto, futures). For stocks, enable the Use for All Assets option in Session VWAP settings. Q: The Divergence labels appear delayed. Is this a bug? A: Divergence detection requires pivot confirmation, which needs bars on both sides of the pivot point. The label appears at the actual pivot location (several bars back) once confirmed. This is intentional and prevents false signals. Q: Can I change the band colors? A: Yes. Each of the three bands has its own color input setting. You can customize Band 1, Band 2, and Band 3 colors to match your preferences. The defaults are Aqua, Fuchsia, and Purple. The main VWAP line color adapts dynamically based on slope direction or can be set to static blue. Q: How do I set up alerts? A: Right-click on the chart, select Add Alert, choose this indicator, and select your desired condition from the dropdown. All conditions include descriptive alert messages with relevant data. Q: What is the Probability Engine lookback period? A: This setting determines how many trading days the indicator analyzes to calculate band touch rates and mean reversion statistics. Default is 60 days (approximately 3 months). Longer periods provide more stable statistics but may miss recent behavior changes. Q: Why do I see fewer labels than expected? A: Signal labels (Volume, Momentum, Squeeze, Divergence) are limited to 5 most recent labels on the chart to keep it clean. When a new label appears, the oldest one is automatically removed. Additionally, momentum labels have several filters: check the slope multiplier setting (higher values require stronger trends) and the Only Reversal Signals option (when enabled, labels only appear for potential reversals, not trend confirmations). Q: What is the Calculated Projection and how accurate is it? A: The Calculated Projection analyzes what happened in past market conditions similar to the current state. It classifies each bar by Z-Score level, Trend direction, and Volume profile (27 unique states), then shows the historical probability of up vs down and the average move size. It is NOT a price prediction or guarantee. The probability shown is how often similar conditions led to up/down moves historically, not a future guarantee. Always use it as one input among many. Q: Why does the Projection probability change? A: The projection updates on each bar as market state changes. If Z-Score moves from LOW to MID, or trend shifts from UP to FLAT, the system looks up a different historical category. This is expected behavior. The projection shows what happened in similar past conditions to the current bar's state. Q: The Projection shows LOW confidence. What does that mean? A: Confidence levels indicate sample size: HIGH means 30 or more historical cases found, MEDIUM means 15-29 cases, LOW means fewer than 15 cases. When sample size is low, the system uses a fallback: first aggregating by Z-Score plus Trend only (ignoring volume), then by Z-Score only. LOW confidence means less statistical reliability, so weight other factors more heavily in your decision. Q: Why does the cone sometimes show 50/50 probability? A: A 50/50 reading means that in similar past market states, price moved up roughly half the time and down half the time. This indicates a neutral or balanced condition where historical patterns provide no directional edge. Consider waiting for a higher probability setup or using other analysis methods. CREDITS AND ACKNOWLEDGMENTS Methodology Foundation: VWAP (Volume Weighted Average Price) - Standard institutional benchmark calculation, widely used since the 1980s for algorithmic execution and fair value assessment Standard Deviation Bands - Statistical volatility measurement applying normal distribution principles to price deviation from mean Z-Score Analysis - Classic statistical normalization technique for comparing values across different volatility regimes Cumulative Volume Delta (CVD) - Order flow analysis concept measuring aggressive buying versus selling pressure Concept Integration: Mean reversion probability engine - Custom historical statistics tracking for band touch rates Momentum acceleration detection - Second derivative analysis of VWAP slope changes VWAP Squeeze - Volatility compression concept adapted from TTM Squeeze methodology applied to VWAP bands versus ATR Confidence scoring system - Weighted composite scoring combining multiple technical factors Calculated Projection Cone - Probability-based projection using 27-state market classification (Z-Score, Trend, Volume) with historical outcome analysis and weighted fallback system All calculations use standard public domain formulas and TradingView built-in functions. No proprietary third-party code was used. For questions, feedback, or feature requests, please comment below or send a private message. Happy Trading!
Pine Script® indicator
by orenluxy
11
PoC Migration Map [BackQuant]PoC Migration Map A volume structure tool that builds a side volume profile, extracts rolling Points of Control (PoCs), and maps how those PoCs migrate through time so you can see where value is moving, how volume clusters shift, and how that aligns with trend regime. What this is This indicator combines a classic volume profile with a segmented PoC trail. It looks back over a configurable window, splits that window into bins by price, and shows you where volume has concentrated. On top of that, it slices the lookback into fixed bar segments, finds the local PoC in each segment, and plots those PoCs as a chain of nodes across the chart. The result is a "migration map" of value: A side volume profile that shows how volume is distributed over the recent price range. A sequence of PoC nodes that show where local value has been accepted over time. Lines that connect those PoCs to reveal the path of value migration. Optional trend coloring based on EMA 12 and EMA 21, so each PoC also encodes trend regime. Used together, this gives you a structural read on where the market has actually traded size, how "value" is moving, and whether that movement is aligned or fighting the current trend. Core components Lookback volume profile - a side histogram built from all closes and volumes in the chosen lookback window. Segmented PoC trail - rolling PoCs computed over fixed bar segments, plotted as nodes in time. Trend heatmap - optional color mapping of PoC nodes using EMA 12 versus EMA 21. PoC labels - optional labels on every Nth PoC for easier reading and referencing. How it works 1) Global lookback and binning You choose: Lookback Bars - how far back to collect data. Number of Bins - how finely to split the price range. The script: Finds the highest high and lowest low in the lookback. Computes the total price range and divides it into equal binCount slices. Assigns each bar's close and volume into the appropriate price bin. This creates a discretized volume distribution across the entire lookback. 2) Side volume profile If "Show Side Profile" is enabled, a right-hand volume profile is drawn: Each bin becomes a horizontal bar anchored at a configurable "Right Offset" from the current bar. The horizontal width of each bar is proportional to that bin's volume relative to the maximum volume bin. Optionally, volume values and percentages are printed inside the profile bars. Color and transparency are controlled by: Base Profile Color and its transparency. A gradient that uses relative volume to modulate opacity between lower volume and higher volume bins. Profile Width (%) - how wide the maximum bin can extend in bars. This gives you an at-a-glance view of the volume landscape for the chosen lookback window. 3) Segmenting for PoC migration To build the PoC trail, the lookback is divided into segments: Bars per Segment - bars in each local cluster. Number of Segments - how many segments you want to see back in time. For each segment: The script uses the same price bins and accumulates volume only from bars in that segment. It finds the bin with the highest volume in that segment, which is the local PoC for that segment. It sets the PoC price to the center of that bin. It finds the "mid bar" of the segment and places the PoC node at that time on the chart. This is repeated for each segment from older to newer, so you get a chain of PoCs that shows how local value has migrated over time. 4) Trend regime and color coding The indicator precomputes: EMA 12 (Fast). EMA 21 (Slow). For each PoC: It samples EMA 12 and EMA 21 at the mid bar of that segment. It computes a simple trend score as fast EMA minus slow EMA. If trend heatmap is enabled, PoC nodes (and the lines between them) are colored by: Trend Up Color if EMA 12 is above EMA 21. Trend Down Color if EMA 12 is below EMA 21. Trend Flat Color if they are roughly equal. If the trend heatmap is disabled, PoC color is instead based on PoC migration: If the current PoC is above the previous PoC, use the Up PoC Color. If the current PoC is below the previous PoC, use the Down PoC Color. If unchanged, use the Flat PoC Color. 5) Connecting PoCs and labels Once PoC prices and times are known: Each PoC is connected to the previous one with a dotted line, using the PoC's color. Optional labels are placed next to every Nth PoC: Label text uses a simple "PoC N" scheme. Label background uses a configurable label background color. Label border is colored by the PoC's own color for visual consistency. This turns the PoCs into a visual path that can be read like a "value trajectory" across the chart. What it plots When fully enabled, you will see: A right-sided volume profile for the chosen lookback window, built from volume by price. Colored horizontal bars representing each price bin's relative volume. Optional volume text showing each bin's volume and its percentage of the profile maximum. A series of PoC nodes spaced across the chart at the mid point of each segment. Dotted lines connecting those PoCs to show the migration path of value. Optional PoC labels at each Nth node for easier reference. Color-coding of PoCs and lines either by EMA 12 / 21 trend regime or by up/down PoC drift. Reading PoC migration and market pressure Side profile as a pressure map The side profile shows where trading has been most active: Thick, opaque bars represent high volume zones and possible high interest or acceptance areas. Thin, faint bars represent low volume zones, potential rejection or transition areas. When price trades near a high volume bin, the market is sitting on an area of prior acceptance and size. When price moves quickly through low volume bins, it often does so with less friction. This gives you a static map of where the market has been willing to do business within your lookback. PoC trail as a value migration map The PoC chain represents "where value has lived" over time: An upward sloping PoC trail indicates value migrating higher. Buyers have been willing to transact at increasingly higher prices. A downward sloping trail indicates value migrating lower and sellers pushing the center of mass down. A flat or oscillating trail indicates balance or rotational behaviour, with no clear directional acceptance. Taken together, you can interpret: Side profile as "where the volume mass sits", a static pressure field. PoC trail as "how that mass has moved", the dynamic path of value. Trend heatmap as a regime overlay When PoCs are colored by the EMA 12 / 21 spread: Green PoCs mark segments where the faster EMA is above the slower EMA, that is, a local uptrend regime. Red PoCs mark segments where the faster EMA is below the slower EMA, that is, a local downtrend regime. Gray PoCs mark flat or ambiguous trend segments. This lets you answer questions like: "Is value migrating higher while the trend regime is also up?" (trend confirming value). "Is value migrating higher but most PoCs are red?" (value against the prevailing trend). "Has value started to roll over just as PoCs flip from green to red?" (early regime transition). Key settings General Settings Lookback Bars - how many bars back to use for both the global volume profile and segment profiles. Number of Bins - how many price bins to split the high to low range into. Profile Settings Show Side Profile - toggle the right-hand volume profile on or off. Profile Width (%) - how wide the largest volume bar is allowed to be in terms of bars. Base Profile Color - the starting color for profile bars, with transparency. Show Volume Values - if enabled, print volume and percent for each non-zero bin. Profile Text Color - color for volume text inside the profile. PoC Migration Settings Show PoC Migration - toggle the PoC trail plotting. Bars per Segment - the number of bars contained in each segment. Number of Segments - how many segments to build backwards from the current bar. Horizontal Spacing (bars) - spacing between PoC nodes when drawn. (Used to separate PoCs horizontally.) Label Every Nth PoC - draw labels at every Nth PoC (0 or 1 to suppress labels). Right Offset (bars) - horizontal offset to anchor the side profile on the right. Up PoC Color - color used when a PoC is higher than the previous one, if trend heatmap is off. Down PoC Color - color used when a PoC is lower than the previous one, if trend heatmap is off. Flat PoC Color - color used when the PoC is unchanged, if trend heatmap is off. PoC Label Background - background color for PoC labels. Trend Heatmap Settings Color PoCs By Trend (EMA 12 / 21) - when enabled, overrides simple up/down coloring and uses EMA-based trend colors. Fast EMA - length for the fast EMA. Slow EMA - length for the slow EMA. Trend Up Color - color for PoCs in a bullish EMA regime. Trend Down Color - color for PoCs in a bearish EMA regime. Trend Flat Color - color for neutral or flat EMA regimes. Trading applications 1) Value migration and trend confirmation Use the PoC path to see if value is following price or lagging it: In a healthy uptrend, price, PoCs, and trend regime should all lean higher. In a weakening trend, price may still move up, but PoCs flatten or start drifting lower, suggesting fewer participants are accepting the new highs. In a downtrend, persistent downward PoC migration confirms that sellers are winning the value battle. 2) Identifying acceptance and rejection zones Combine the side profile with PoC locations: High volume bins near clustered PoCs mark strong acceptance zones, good areas to watch for re-tests and decision points. PoCs that quickly jump across low volume areas can indicate rejection and fast repricing between value zones. High volume zones with mixed PoC colors may signal balance or prolonged negotiation. 3) Structuring entries and exits Use the map to refine trade location: Fade trades against value migration are higher risk unless you see clear signs of exhaustion or regime change. Pullbacks into prior PoC zones in the direction of the current PoC slope can offer higher quality entries. Stops placed beyond major accepted zones (clusters of PoCs and high volume bins) are less likely to be hit by random noise. 4) Regime transitions Watch how PoCs behave as the EMA regime changes: A flip in EMA 12 versus EMA 21, coupled with a turn in PoC slope, is a strong signal that value is beginning to move with the new trend. If EMAs flip but PoC migration does not follow, the trend signal may be early or false. A weakening PoC path (lower highs in PoCs) while trend colors are still green can warn of a late-stage trend. Best practices Start with a moderate lookback such as 200 to 300 bars and a moderate bin count such as 20 to 40. Too many bins can make the profile overly granular and sparse. Align "Bars per Segment" with your trading horizon. For example, 5 to 10 bars for intraday, 10 to 20 bars for swing. Use the profile and PoC trail as structural context rather than as a direct buy or sell signal. Combine with your existing setups for timing. Pay attention to clusters of PoCs at similar prices. Those are areas where the market has repeatedly accepted value, and they often matter on future tests. Notes This is a structural volume tool, not a complete trading system. It does not manage execution, position sizing or risk management. Use it to understand: Where the bulk of trading has occurred in your chosen window. How the center of volume has migrated over time. Whether that migration is aligned with or fighting the current trend regime. By turning PoC evolution into a visible path and adding a trend-aware heatmap, the PoC Migration Map makes it easier to see how value has been moving, where the market is likely to feel "heavy" or "light", and how that structure fits into your trading decisions.
Pine Script® indicator
by BackQuant
Time-Decay Liquidity Zones [BackQuant]Time-Decay Liquidity Zones A dynamic liquidity map that turns single-bar exhaustion events into fading, color-graded zones, so you can see where trapped traders and unfinished business still matter, and when those areas have finally stopped pulling price. What this is This indicator detects unusually strong impulsive moves into wicks, converts them into supply or demand “zones,” then lets those zones decay over time. Each zone carries a strength score that fades bar by bar. Zones that stop attracting or rejecting price are gradually de-emphasized and eventually removed, while the most relevant areas stay bright and obvious. Instead of static rectangles that live forever, you get a living liquidity map where: Zones are born from objective criteria: volatility, wick size, and optional volume spikes. Zones “age” using a configurable decay factor and maximum lifetime. Zone color and opacity reflect current relative strength on a unified clear → green → red gradient. Zones freeze when broken, so you can distinguish “active reaction areas” from “historical levels that have already given way”. Conceptual idea Large wicks with strong volatility often mark areas where aggressive orders met hidden liquidity and got absorbed. Price may revisit these areas to test leftover interest or to relieve trapped positions. However, not every wick matters for long. As time passes and more bars print, the market “forgets” some areas. Time-Decay Liquidity Zones turns that idea into a rule-based system: Find bars that likely reflect strong aggressive flows into liquidity. Mark a zone around the wick using ATR-based thickness. Assign a strength score of 1.0 at birth. Each bar, reduce that score by a decay factor and remove zones that fall below a threshold or live too long. Color all surviving zones from weak to strong using a single gradient scale and a visual legend. How events are detected Detection lives in the Event Detection group. The script combines range, wick size, and optional volume filters into simple rules. Volatility filter ATR Length — computes a rolling ATR over your chosen window. This is the volatility baseline. Min range in ATRs — bar range (High–Low) must exceed this multiple of ATR for an event to be considered. This avoids tiny bars triggering zones. Wick filters For each bar, the script splits the candle into body and wicks: Upper wick = High minus the max(Open, Close). Lower wick = min(Open, Close) minus Low. Then it tests: Upper wick condition — upper wick must be larger than Min wick size in ATRs × ATR. Lower wick condition — lower wick must be larger than Min wick size in ATRs × ATR. Only bars with a sufficiently long wick relative to volatility qualify as candidate “liquidity events”. Volume filter Optionally, the script requires a volume spike: Use volume filter — if enabled, volume must exceed a rolling volume SMA by a configurable multiplier. Volume SMA length — period for the volume average. Volume spike multiplier — how many times above the SMA current volume needs to be. This lets you focus only on “heavy” tests of liquidity and ignore quiet bars. Event types Putting it together: Upper event (potential supply / long liquidation, etc.) Occurs when: Upper wick is large in ATR terms. Full bar range is large in ATR terms. Volume is above the spike threshold (if enabled). Lower event (potential demand / short liquidation, etc.) Symmetric conditions using the lower wick. How zones are constructed Zone geometry lives in Zone Geometry . When an event is detected, the script builds a rectangular box that anchors to the wick and extends in the appropriate direction by an ATR-based thickness. For upper (supply-type) zones Bottom of the zone = event bar high. Top of the zone = event bar high + Zone thickness in ATRs × ATR. The zone initially spans only the event bar on the x-axis, but is extended to the right as new bars appear while the zone is active. For lower (demand-type) zones Top of the zone = event bar low. Bottom of the zone = event bar low − Zone thickness in ATRs × ATR. Same extension logic: box starts on the event bar and grows rightward while alive. The result is a band around the wick that scales with volatility. On high-ATR charts, zones are thicker. On calm charts, they are narrower and more precise. Zone lifecycle, decay, and removal All lifecycle logic is controlled by the Decay & Lifetime group. Each zone carries: Score — a floating-point “importance” measure, starting at 1.0 when created. Direction — +1 for upper zones, −1 for lower zones. Birth index — bar index at creation time. Active flag — whether the zone is still considered unbroken and extendable. 1) Active vs broken Each confirmed bar, the script checks: For an upper zone , the zone is counted as “broken” when the close moves above the top of the zone. For a lower zone , the zone is counted as “broken” when the close moves below the bottom of the zone. When a zone breaks: Its right edge is frozen at the previous bar (no further extension). The zone remains on the chart, but is no longer updated by price interaction. It still decays in score until removal. This lets you see where a major level was overrun, while naturally fading its influence over time. 2) Time decay At each confirmed bar: Score := Score × Score decay per bar . A decay value close to 1.0 means very slow decay and long-lived zones. Lower values (closer to 0.9) mean faster forgetting and more current-focused zones. You are controlling how quickly the market “forgets” past events. 3) Age and score-based removal Zones are removed when either: Age in bars exceeds Max bars a zone can live . This is a hard lifetime cap. Score falls below Minimum score before removal . This trims zones that have decayed into irrelevance even if their age is still within bounds. When a zone is removed, its box is deleted and all associated state is freed to keep performance and visuals clean. Unified gradient and color logic Color control lives in Gradient & Color . The indicator uses a single continuous gradient for all zones, above and below price, so you can read strength at a glance without guessing what palette means what. Base colors You set: Mid strength color (green) — used for mid-level strength zones and as the “anchor” in the gradient. High strength color (red) — used for the strongest zones. Max opacity — the maximum visual opacity for the solid part of the gradient. Lower values here mean more solid; higher values mean more transparent. The script then defines three internal points: Clear end — same as mid color, but with a high alpha (close to transparent). Mid end — mid color at the strongest allowed opacity. High end — high color at the strongest allowed opacity. Strength normalization Within each update: The script finds the maximum score among all existing zones. Each zone’s strength is computed as its score divided by this maximum. Strength is clamped into . This means a zone with strength 1.0 is currently the strongest zone on the chart. Other zones are colored relative to that. Piecewise gradient Color is assigned in two stages: For strength between 0.0 and 0.5: interpolate from “clear” green to solid green. Weak zones are barely visible, mid-strength zones appear as solid green. For strength between 0.5 and 1.0: interpolate from solid green to solid red. The strongest zones shift toward the red anchor, clearly separating them from everything else. Strength scale legend To make the gradient readable, the indicator draws a vertical legend on the right side of the chart: About 15 cells from top (Strong) to bottom (Weak). Each cell uses the same gradient function as the zones themselves. Top cell is labeled “Strong”; bottom cell is labeled “Weak”. This legend acts as a fixed reference so you can instantly map a zone’s color to its approximate strength rank. What it plots At a glance, the indicator produces: Upper liquidity zones above price, built from large upper wick events. Lower liquidity zones below price, built from large lower wick events. All zones colored by relative strength using the same gradient. Zones that freeze when price breaks them, then fade out via decay and removal. A strength scale legend on the right to interpret the gradient. There are no extra lines, labels, or clutter. The focus is the evolving structure of liquidity zones and their visual strength. How to read the zones Bright red / bright green zones These are your current “major” liquidity areas. They have high scores relative to other zones and have not yet decayed. Expect meaningful reactions, absorption attempts, or spillover moves when price interacts with them. Faded zones Pale, nearly transparent zones are either old, decayed, or minor. They can still matter, but priority is lower. If these are in the middle of a long consolidation, they often become background noise. Broken but still visible zones Zones whose extension has stopped have been overrun by closing price. They show where a key level gave way. You can use them as context for regime shifts or failed attempts. Absence of zones A chart with few or no zones means that, under your current thresholds, there have not been strong enough liquidity events recently. Either tighten the filters or accept that recent price action has been relatively balanced. Use cases 1) Intraday liquidity hunting Run the indicator on lower timeframes (e.g., 1–15 minute) with moderately fast decay. Use the upper zones as potential sell reaction areas, the lower zones as potential buy reaction areas. Combine with order flow, CVD, or footprint tools to see whether price is absorbing or rejecting at each zone. 2) Swing trading context Increase ATR length and range/wick multipliers to focus only on major spikes. Set slower decay and higher max lifetime so zones persist across multiple sessions. Use these zones as swing inflection areas for larger setups, for example anticipating re-tests after breakouts. 3) Stop placement and invalidation For longs, place invalidation beyond a decaying lower zone rather than in the middle of noise. For shorts, place invalidation beyond strong upper zones. If price closes through a strong zone and it freezes, treat that as additional evidence your prior bias may be wrong. 4) Identifying trapped flows Upper zones formed after violent spikes up that quickly fail can mark trapped longs. Lower zones formed after violent spikes down that quickly reverse can mark trapped shorts. Watching how price behaves on the next touch of those zones can hint at whether those participants are being rescued or squeezed. Settings overview Event Detection Use volume filter — enable or disable the volume spike requirement. Volume SMA length — rolling window for average volume. Volume spike multiplier — how aggressive the volume spike filter is. ATR length — period for ATR, used in all size comparisons. Min wick size in ATRs — minimum wick size threshold. Min range in ATRs — minimum bar range threshold. Zone Geometry Zone thickness in ATRs — vertical size of each liquidity zone, scaled by ATR. Decay & Lifetime Score decay per bar — multiplicative decay factor for each zone score per bar. Max bars a zone can live — hard cap on lifetime. Minimum score before removal — score cut-off at which zones are deleted. Gradient & Color Mid strength color (green) — base color for mid-level zones and the lower half of the gradient. High strength color (red) — target color for the strongest zones. Max opacity — controls the most solid end of the gradient (0 = fully solid, 100 = fully invisible). Tuning guidance Fast, session-only liquidity Shorter ATR length (e.g., 20–50). Higher wick and range multipliers to focus only on extreme events. Decay per bar closer to 0.95–0.98 and moderate max lifetime. Volume filter enabled with a decent multiplier (e.g., 1.5–2.0). Slow, structural zones Longer ATR length (e.g., 100+). Moderate wick and range thresholds. Decay per bar very close to 1.0 for slow fading. Higher max lifetime and slightly higher min score threshold so only very weak zones disappear. Noisy, high-volatility instruments Increase wick and range ATR multipliers to avoid over-triggering. Consider enabling the volume filter with stronger settings. Keep decay moderate to avoid the chart getting overloaded with old zones. Notes This is a structural and contextual tool, not a complete trading system. It does not account for transaction costs, execution slippage, or your specific strategy rules. Use it to: Highlight where liquidity has recently been tested hard. Rank these areas by decaying strength. Guide your attention when layering in separate entry signals, risk management, and higher-timeframe context. Time-Decay Liquidity Zones is designed to keep your chart focused on where the market has most recently “cared” about price, and to gradually forget what no longer matters. Adjust the detection, geometry, decay, and gradient to fit your product and timeframe, and let the zones show you which parts of the tape still have unfinished business.
Pine Script® indicator
by BackQuant
Liquidity Void Zone Detector [PhenLabs]📊 Liquidity Void Zone Detector Version: PineScript™v6 📌 Description The Liquidity Void Zone Detector is a sophisticated technical indicator designed to identify and visualize areas where price moved with abnormally low volume or rapid momentum, creating "voids" in market liquidity. These zones represent areas where insufficient trading activity occurred during price movement, often acting as magnets for future price action as the market seeks to fill these gaps. Built on PineScript v6, this indicator employs a dual-detection methodology that analyzes both volume depletion patterns and price movement intensity relative to ATR. The revolutionary 3D visualization system uses three-layer polyline rendering with adaptive transparency and vertical offsets, creating genuine depth perception where low liquidity zones visually recede and high liquidity zones protrude forward. This makes critical market structure immediately apparent without cluttering your chart. 🚀 Points of Innovation Dual detection algorithm combining volume threshold analysis and ATR-normalized price movement sensitivity for comprehensive void identification Three-layer 3D visualization system with progressive transparency gradients (85%, 78%, 70%) and calculated vertical offsets for authentic depth perception Intelligent state machine logic that tracks consecutive void bars and only renders zones meeting minimum qualification requirements Dynamic strength scoring system (0-100 scale) that combines inverted volume ratios with movement intensity for accurate void characterization Adaptive ATR-based spacing calculation that automatically adjusts 3D layering depth to match instrument volatility Efficient memory management system supporting up to 100 simultaneous void visualizations with automatic array-based cleanup 🔧 Core Components Volume Analysis Engine: Calculates rolling volume averages and compares current bar volume against dynamic thresholds to detect abnormally thin trading conditions Price Movement Analyzer: Normalizes bar range against ATR to identify rapid price movements that indicate liquidity exhaustion regardless of instrument or timeframe Void Tracking State Machine: Maintains persistent tracking of void start bars, price boundaries, consecutive bar counts, and cumulative strength across multiple bars 3D Polyline Renderer: Generates three-layer rectangular polylines with precise timestamp-to-bar index conversion and progressive offset calculations Strength Calculation System: Combines volume component (inverted ratio capped at 100) with movement component (ATR intensity × 30) for comprehensive void scoring 🔥 Key Features Automatic Void Detection: Continuously scans price action for low volume conditions or rapid movements, triggering void tracking when thresholds are exceeded Real-Time Visualization: Creates 3D rectangular zones spanning from void initiation to termination, with color-coded depth indicating liquidity type Adjustable Sensitivity: Configure volume threshold multiplier (0.1-2.0x), price movement sensitivity (0.5-5.0x), and minimum qualifying bars (1-10) for customized detection Dual Color Coding: Separate visual treatment for low liquidity voids (receding red) and high liquidity zones (protruding green) based on 50-point strength threshold Optional Compact Labels: Toggle LV (Low Volume) or HV (High Volume) circular labels at void centers for quick identification without visual clutter Lookback Period Control: Adjust analysis window from 5 to 100 bars to match your trading timeframe and market volatility characteristics Memory-Efficient Design: Automatically manages polyline and label arrays, deleting oldest elements when user-defined maximum is reached Data Window Integration: Plots void detection binary, current strength score, and average volume for detailed analysis in TradingView's data window 🎨 Visualization Three-Layer Depth System: Each void is rendered as three stacked polylines with progressive transparency (85%, 78%, 70%) and calculated vertical offsets creating authentic 3D appearance Directional Depth Perception: Low liquidity zones recede with back layer most transparent; high liquidity zones protrude with front layer most transparent for instant visual differentiation Adaptive Offset Spacing: Vertical separation between layers calculated as ATR(14) × 0.001, ensuring consistent 3D effect across different instruments and volatility regimes Color Customization: Fully configurable base colors for both low liquidity zones (default: red with 80 transparency) and high liquidity zones (default: green with 80 transparency) Minimal Chart Clutter: Closed polylines with matching line and fill colors create clean rectangular zones without unnecessary borders or visual noise Background Highlight: Subtle yellow background (96% transparency) marks bars where void conditions are actively detected in real-time Compact Labeling: Optional tiny circular labels with 60% transparent backgrounds positioned at void center points for quick reference 📖 Usage Guidelines Detection Settings Lookback Period: Default: 10 | Range: 5-100 | Number of bars analyzed for volume averaging and void detection. Lower values increase sensitivity to recent changes; higher values smooth detection across longer timeframes. Adjust based on your trading timeframe: short-term traders use 5-15, swing traders use 20-50, position traders use 50-100. Volume Threshold: Default: 1.0 | Range: 0.1-2.0 (step 0.1) | Multiplier applied to average volume. Bars with volume below (average × threshold) trigger void conditions. Lower values detect only extreme volume depletion; higher values capture more moderate low-volume situations. Start with 1.0 and decrease to 0.5-0.7 for stricter detection. Price Movement Sensitivity: Default: 1.5 | Range: 0.5-5.0 (step 0.1) | Multiplier for ATR-normalized price movement detection. Values above this threshold indicate rapid price changes suggesting liquidity voids. Increase to 2.0-3.0 for volatile instruments; decrease to 0.8-1.2 for ranging or low-volatility conditions. Minimum Void Bars: Default: 10 | Range: 1-10 | Minimum consecutive bars exhibiting void conditions required before visualization is created. Filters out brief anomalies and ensures only sustained voids are displayed. Use 1-3 for scalping, 5-10 for intraday trading, 10+ for swing trading to match your time horizon. Visual Settings Low Liquidity Color: Default: Red (80% transparent) | Base color for zones where volume depletion or rapid movement indicates thin liquidity. These zones recede visually (back layer most transparent). Choose colors that contrast with your chart theme for optimal visibility. High Liquidity Color: Default: Green (80% transparent) | Base color for zones with relatively higher liquidity compared to void threshold. These zones protrude visually (front layer most transparent). Ensure clear differentiation from low liquidity color. Show Void Labels: Default: True | Toggle display of compact LV/HV labels at void centers. Disable for cleaner charts when trading; enable for analysis and review to quickly identify void types across your chart. Max Visible Voids: Default: 50 | Range: 10-100 | Maximum number of void visualizations kept on chart. Each void uses 3 polylines, so setting of 50 maintains 150 total polylines. Higher values preserve more history but may impact performance on lower-end systems. ✅ Best Use Cases Gap Fill Trading: Identify unfilled liquidity voids that price frequently returns to, providing high-probability retest and reversal opportunities when price approaches these zones Breakout Validation: Distinguish genuine breakouts through established liquidity from false breaks into void zones that lack sustainable volume support Support/Resistance Confluence: Layer void detection over key horizontal levels to validate structural integrity—levels within high liquidity zones are stronger than those in voids Trend Continuation: Monitor for new void formation in trend direction as potential continuation zones where price may accelerate due to reduced resistance Range Trading: Identify void zones within consolidation ranges that price tends to traverse quickly, helping to avoid getting caught in rapid moves through thin areas Entry Timing: Wait for price to reach void boundaries rather than entering mid-void, as voids tend to be traversed quickly with limited profit-taking opportunities ⚠️ Limitations Historical Pattern Indicator: Identifies past liquidity voids but cannot predict whether price will return to fill them or when filling might occur No Volume on Forex: Indicator uses tick volume for forex pairs, which approximates but doesn't represent true trading volume, potentially affecting detection accuracy Lagging Confirmation: Requires minimum consecutive bars (default 10) before void is visualized, meaning detection occurs after void formation begins Trending Market Behavior: Strong trends driven by fundamental catalysts may create voids that remain unfilled for extended periods or permanently Timeframe Dependency: Detection sensitivity varies significantly across timeframes; settings optimized for one timeframe may not perform well on others No Directional Bias: Indicator identifies liquidity characteristics but provides no predictive signal for price direction after void detection Performance Considerations: Higher max visible void settings combined with small minimum void bars can generate numerous visualizations impacting chart rendering speed 💡 What Makes This Unique Industry-First 3D Visualization: Unlike flat volume or liquidity indicators, the three-layer rendering with directional depth perception provides instant visual hierarchy of liquidity quality Dual-Mode Detection: Combines both volume-based and movement-based detection methodologies, capturing voids that single-approach indicators miss Intelligent Qualification System: State machine logic prevents premature visualization by requiring sustained void conditions, reducing false signals and chart clutter ATR-Normalized Analysis: All detection thresholds adapt to instrument volatility, ensuring consistent performance across stocks, forex, crypto, and futures without constant recalibration Transparency-Based Depth: Uses progressive transparency gradients rather than colors or patterns to create depth, maintaining visual clarity while conveying information hierarchy Comprehensive Strength Metrics: 0-100 void strength calculation considers both the degree of volume depletion and the magnitude of price movement for nuanced zone characterization 🔬 How It Works Phase 1: Real-Time Detection On each bar close, the indicator calculates average volume over the lookback period and compares current bar volume against the volume threshold multiplier Simultaneously measures current bar's high-low range and normalizes it against ATR, comparing the result to price movement sensitivity parameter If either volume falls below threshold OR movement exceeds sensitivity threshold, the bar is flagged as exhibiting void characteristics Phase 2: Void Tracking & Qualification When void conditions first appear, state machine initializes tracking variables: start bar index, initial top/bottom prices, consecutive bar counter, and cumulative strength accumulator Each subsequent bar with void conditions extends the tracking, updating price boundaries to envelope all bars and accumulating strength scores When void conditions cease, system checks if consecutive bar count meets minimum threshold; if yes, proceeds to visualization; if no, discards the tracking and resets Phase 3: 3D Visualization Construction Calculates average void strength by dividing cumulative strength by number of bars, then determines if void is low liquidity (>50 strength) or high liquidity (≤50 strength) Generates three polyline layers spanning from start bar to end bar and from top price to bottom price, each with calculated vertical offset based on ATR Applies progressive transparency (85%, 78%, 70%) with layer ordering creating recession effect for low liquidity zones and protrusion effect for high liquidity zones Creates optional center label and pushes all visual elements into arrays for memory management Phase 4: Memory Management & Display Continuously monitors polyline array size (each void creates 3 polylines); when total exceeds max visible voids × 3, deletes oldest polylines via array.shift() Similarly manages label array, removing oldest labels when count exceeds maximum to prevent memory accumulation over extended chart history Plots diagnostic data to TradingView’s data window (void detection binary, current strength, average volume) for detailed analysis without cluttering main chart 💡 Note: This indicator is designed to enhance your market structure analysis by revealing liquidity characteristics that aren’t visible through standard price and volume displays. For best results, combine void detection with your existing support/resistance analysis, trend identification, and risk management framework. Liquidity voids are descriptive of past market behavior and should inform positioning decisions rather than serve as standalone entry/exit signals. Experiment with detection parameters across different timeframes to find settings that align with your trading style and instrument characteristics.
Pine Script® indicator
by PhenLabs
SP500 Session Gap Fade StrategySummary in one paragraph SPX Session Gap Fade is an intraday gap fade strategy for index futures, designed around regular cash sessions on five minute charts. It helps you participate only when there is a full overnight or pre session gap and a valid intraday session window, instead of trading every open. The original part is the gap distance engine which anchors both stop and optional target to the previous session reference close at a configurable flat time, so every trade’s risk scales with the actual gap size rather than a fixed tick stop. Scope and intent • Markets. Primarily index futures such as ES, NQ, YM, and liquid index CFDs that exhibit overnight gaps and regular cash hours. • Timeframes. Intraday timeframes from one minute to fifteen minutes. Default usage is five minute bars. • Default demo used in the publication. Symbol CME:ES1! on a five minute chart. • Purpose. Provide a simple, transparent way to trade opening gaps with a session anchored risk model and forced flat exit so you are not holding into the last part of the session. • Limits. This is a strategy. Orders are simulated on standard candles only. Originality and usefulness • Unique concept or fusion. The core novelty is the combination of a strict “full gap” entry condition with a session anchored reference close and a gap distance based TP and SL engine. The stop and optional target are symmetric multiples of the actual gap distance from the previous session’s flat close, rather than fixed ticks. • Failure mode it addresses. Fixed sized stops do not scale when gaps are unusually small or unusually large, which can either under risk or over risk the account. The session flat logic also reduces the chance of holding residual positions into late session liquidity and news. • Testability. All key pieces are explicit in the Inputs: session window, minutes before session end, whether to use gap exits, whether TP or SL are active, and whether to allow candle based closes and forced flat. You can toggle each component and see how it changes entries and exits. • Portable yardstick. The main unit is the absolute price gap between the entry bar open and the previous session reference close. tp_mult and sl_mult are multiples of that gap, which makes the risk model portable across contracts and volatility regimes. Method overview in plain language The strategy first defines a trading session using exchange time, for example 08:30 to 15:30 for ES day hours. It also defines a “flat” time a fixed number of minutes before session end. At the flat bar, any open position is closed and the bar’s close price is stored as the reference close for the next session. Inside the session, the strategy looks for a full gap bar relative to the prior bar: a gap down where today’s high is below yesterday’s low, or a gap up where today’s low is above yesterday’s high. A full gap down generates a long entry; a full gap up generates a short entry. If the gap risk engine is enabled and a valid reference close exists, the strategy measures the distance between the entry bar open and that reference close. It then sets a stop and optional target as configurable multiples of that gap distance and manages them with strategy.exit. Additional exits can be triggered by a candle color flip or by the forced flat time. Base measures • Range basis. The main unit is the absolute difference between the current entry bar open and the stored reference close from the previous session flat bar. That value is used as a “gap unit” and scaled by tp_mult and sl_mult to build the target and stop. Components • Component one: Gap Direction. Detects full gap up or full gap down by comparing the current high and low to the previous bar’s high and low. Gap down signals a long fade, gap up signals a short fade. There is no smoothing; it is a strict structural condition. • Component two: Session Window. Only allows entries when the current time is within the configured session window. It also defines a flat time before the session end where positions are forced flat and the reference close is updated. • Component three: Gap Distance Risk Engine. Computes the absolute distance between the entry open and the stored reference close. The stop and optional target are placed as entry ± gap_distance × multiplier so that risk scales with gap size. • Optional component: Candle Exit. If enabled, a bullish bar closes short positions and a bearish bar closes long positions, which can shorten holding time when price reverses quickly inside the session. • Session windows. Session logic uses the exchange time of the chart symbol. When changing symbols or venues, verify that the session time string still matches the new instrument’s cash hours. Fusion rule All gates are hard conditions rather than weighted scores. A trade can only open if the session window is active and the full gap condition is true. The gap distance engine only activates if a valid reference close exists and use_gap_risk is on. TP and SL are controlled by separate booleans so you can use SL only, TP only, or both. Long and short are symmetric by construction: long trades fade full gap downs, short trades fade full gap ups with mirrored TP and SL logic. Signal rule • Long entry. Inside the active session, when the current bar shows a full gap down relative to the previous bar (current high below prior low), the strategy opens a long position. If the gap risk engine is active, it places a gap based stop below the entry and an optional target above it. • Short entry. Inside the active session, when the current bar shows a full gap up relative to the previous bar (current low above prior high), the strategy opens a short position. If the gap risk engine is active, it places a gap based stop above the entry and an optional target below it. • Forced flat. At the configured flat time before session end, any open position is closed and the close price of that bar becomes the new reference close for the following session. • Candle based exit. If enabled, a bearish bar closes longs, and a bullish bar closes shorts, regardless of where TP or SL sit, as long as a position is open. What you will see on the chart • Markers on entry bars. Standard strategy entry markers labeled “long” and “short” on the gap bars where trades open. • Exit markers. Standard exit markers on bars where either the gap stop or target are hit, or where a candle exit or forced flat close occurs. Exit IDs “long_gap” and “short_gap” label gap based exits. • Reference levels. Horizontal lines for the current long TP, long SL, short TP, and short SL while a position is open and the gap engine is enabled. They update when a new trade opens and disappear when flat. • Session background. This version does not add background shading for the session; session logic runs internally based on time. • No on chart table. All decisions are visible through orders and exit levels. Use the Strategy Tester for performance metrics. Inputs with guidance Session Settings • Trading session (sess). Session window in exchange time. Typical value uses the regular cash session for each contract, for example “0830-1530” for ES. Adjust if your broker or symbol uses different hours. • Minutes before session end to force exit (flat_before_min). Minutes before the session end where positions are forced flat and the reference close is stored. Typical range is 15 to 120. Raising it closes trades earlier in the day; lowering it allows trades later in the session. Gap Risk • Enable gap based TP/SL (use_gap_risk). Master switch for the gap distance exit engine. Turning it off keeps entries and forced flat logic but removes automatic TP and SL placement. • Use TP limit from gap (use_gap_tp). Enables gap based profit targets. Typical values are true for structured exits or false if you want to manage exits manually and only keep a stop. • Use SL stop from gap (use_gap_sl). Enables gap based stop losses. This should normally remain true so that each trade has a defined initial risk in ticks. • TP multiplier of gap distance (tp_mult). Multiplier applied to the gap distance for the target. Typical range is 0.5 to 2.0. Raising it places the target further away and reduces hit frequency. • SL multiplier of gap distance (sl_mult). Multiplier applied to the gap distance for the stop. Typical range is 0.5 to 2.0. Raising it widens the stop and increases risk per trade; lowering it tightens the stop and may increase the number of small losses. Exit Controls • Exit with candle logic (use_candle_exit). If true, closes shorts on bullish candles and longs on bearish candles. Useful when you want to react to intraday reversal bars even if TP or SL have not been reached. • Force flat before session end (use_forced_flat). If true, guarantees you are flat by the configured flat time and updates the reference close. Turn this off only if you understand the impact on overnight risk. Filters There is no separate trend or volatility filter in this version. All trades depend on the presence of a full gap bar inside the session. If you need extra filtering such as ATR, volume, or higher timeframe bias, they should be added explicitly and documented in your own fork. Usage recipes Intraday conservative gap fade • Timeframe. Five minute chart on ES regular session. • Gap risk. use_gap_risk = true, use_gap_tp = true, use_gap_sl = true. • Multipliers. tp_mult around 0.7 to 1.0 and sl_mult around 1.0. • Exits. use_candle_exit = false, use_forced_flat = true. Focus on the structured TP and SL around the gap. Intraday aggressive gap fade • Timeframe. Five minute chart. • Gap risk. use_gap_risk = true, use_gap_tp = false, use_gap_sl = true. • Multipliers. sl_mult around 0.7 to 1.0. • Exits. use_candle_exit = true, use_forced_flat = true. Entries fade full gaps, stops are tight, and candle color flips flatten trades early. Higher timeframe gap tests • Timeframe. Fifteen minute or sixty minute charts on instruments with regular gaps. • Gap risk. Keep use_gap_risk = true. Consider slightly higher sl_mult if gaps are structurally wider on the higher timeframe. • Note. Expect fewer trades and be careful with sample size; multi year data is recommended. Properties visible in this publication • On average our risk for each position over the last 200 trades is 0.4% with a max intraday loss of 1.5% of the total equity in this case of 100k $ with 1 contract ES. For other assets, recalculations and customizations has to be applied. • Initial capital. 100 000. • Base currency. USD. • Default order size method. Fixed with size 1 contract. • Pyramiding. 0. • Commission. Flat 2 USD per order in the Strategy Tester Properties. (2$ buying + 2$selling) • Slippage. One tick in the Strategy Tester Properties. • Process orders on close. ON. Realism and responsible publication • No performance claims are made. Past results do not guarantee future outcomes. • Costs use a realistic flat commission and one tick of slippage per trade for ES class futures. • Default sizing with one contract on a 100 000 reference account targets modest per trade risk. In practice, extreme slippage or gap through events can exceed this, so treat the one and a half percent risk target as a design goal, not a guarantee. • All orders are simulated on standard candles. Shapes can move while a bar is forming and settle on bar close. Honest limitations and failure modes • Economic releases, thin liquidity, and limit conditions can break the assumptions behind the simple gap model and lead to slippage or skipped fills. • Symbols with very frequent or very large gaps may require adjusted multipliers or alternative risk handling, especially in high volatility regimes. • Very quiet periods without clean gaps will produce few or no trades. This is expected behavior, not a bug. • Session windows follow the exchange time of the chart. Always confirm that the configured session matches the symbol. • When both the stop and target lie inside the same bar’s range, the TradingView engine decides which is hit first based on its internal intrabar assumptions. Without bar magnifier, tie handling is approximate. Legal Education and research only. This strategy is not investment advice. You remain responsible for all trading decisions. Always test on historical data and in simulation with realistic costs before considering any live use.
Pine Script® strategy
by exlux
2
Sigma Trinity ModelAbstract Sigma Trinity Model is an educational framework that studies how three layers of market behavior interact within the same trend: (1) structural momentum (Rasta), (2) internal strength (RSI), and (3) continuation/compounding structure (Pyramid). The model deliberately combines bar-close momentum logic with intrabar, wick-aware strength checks to help users see how reversals form, confirm, and extend. It is not a signal service or automation tool; it is a transparent learning instrument for chart study and backtesting. Why this is not “just a mashup” Many scripts merge indicators without explaining the purpose. Sigma Trinity is a coordinated, three-engine study designed for a specific learning goal: Rasta (structure): defines when momentum actually flips using a dual-line EMA vs smoothed EMA. It gives the entry/exit framework on bar close for clean historical study. RSI (energy): measures internal strength with wick-aware triggers. It uses RSI of LOW (for bottom touches/reclaims) and RSI of HIGH (for top touches/exhaustion) so users can see intrabar strength/weakness that the close can hide. Pyramid (progression): demonstrates how continuation behaves once momentum and strength align. It shows the logic of adds (compounding) as a didactic layer, also on bar close to keep historical alignment consistent. These three roles are complementary, not redundant: structure → strength → progression. Architecture Overview Execution model Rasta & Pyramid: bar close only by default (historically stable, easy to audit). RSI: per tick (realtime) with bar-close backup by default, using RSI of LOW for entries and RSI of HIGH for exits. This makes the module sensitive to intra-bar wicks while still giving a close-based safety net for backtests. Stops (optional in strategy builds): wick-accurate: trail arms/ratchets on HIGH; stop hit checks with LOW (or Close if selected) with a small undershoot buffer to avoid micro-noise hits. Visual model Dual lines (EMA vs smoothed EMA) for Rasta + color fog to see direction and compression/expansion. Rungs (small vertical lines) drawn between the two Rasta lines to visualize wave spacing and rhythm. Clean labels for Entry/Exit/Pyramid Add/RSI events. Everything is state-locked to avoid spamming. Module 1 — Rasta (Structural Momentum Layer) Goal: Identify structural momentum reversals and maintain a consistent, replayable backbone for study. Method: Compute an EMA of a chosen price source (default Close), and a smoothed version (SMA/EMA/RMA/WMA/None selectable). Flip points occur when the EMA line crosses the smoothed line. Optional EMA 8/21 trend filter can gate entries (long-bias when EMA8 > EMA21). A small “adaptive on flip” option lets an entry fire when the filter itself flips to ON and the EMA is already above the smoothed line—useful for trend resumption. Why bar close only? Bar-close Rasta gives a stable, auditable timeline for the structure of the trend. It teaches users to separate “structure” (close-resolved) from “energy” (intrabar, via RSI). Visuals: Fog between the lines (green/red) to show regime. Rungs between lines to show spread (compression vs expansion). Optional plotting of EMA8/EMA21 so users can see the gating effect. Module 2 — RSI (Internal Strength / Energy Layer) Goal: Reveal the intrabar strength/weakness that often precedes or confirms structural flips. Method: Standard RSI with adjustable length and signal smoothing for the panel view. Logic uses wick-aware sources: Entry trigger: RSI of LOW (same RSI length) touching or below a lower band (default 15). Think of it as intraband reactivation from the bottom, using the candle’s deepest excursion. Exit trigger: RSI of HIGH touching or above an upper band (default 85). Think of it as exhaustion at the top, using the candle’s highest excursion. Realtime + Close Backup: fires intrabar on tick, but if the realtime event was missed, the close backup will note it at bar end. Cooldown control: optional bars-between-signals to avoid rapid re-triggers on choppy sequences. Why wick-aware RSI? A close-only RSI can miss the true micro-extremes that cause reversals. Using LOW/HIGH for triggers captures the behavior that traders actually react to during the bar, while the bar-close backup preserves historical reproducibility. Module 3 — Pyramid (Continuation / Compounding Layer) Goal: Teach how continuation behaves once a trend is underway, and how adds can be structured. Method: Same dual-line logic as Rasta (EMA vs smoothed EMA), but only fires when already in a position (or after prior entry conditions). Supports the same EMA 8/21 filter and optional adaptive-on-flip behavior. Bar close only to maintain historical cohesion. What it teaches: Adds tend to cluster when momentum persists. Students can experiment with add spacing and compare “one-shot entries” vs “laddered adds” during strong regimes. How the Pieces Work Together Rasta establishes the structural frame (when the wave flip is real enough to record at close). RSI validates or challenges that structure by tracking intrabar energy at the extremes (low/high touches). Pyramid shows what sustained continuation looks like once (1) and (2) align. This produces a layered view: Structure → Energy → Progression. Users can see when all three line up (strongest phases) and when they diverge (riskier phases or transitions). How to Use It (Step-by-Step) Quick Start Apply script to any symbol/timeframe. In Strategy/Indicator Properties: Enable On every tick (recommended). If available, enable Using bar magnifier and choose a lower resolution (e.g., 1m) to simulate intrabar fills more realistically. Keep On bar close unchecked if you want to observe realtime logic in live charts (strategies still place orders on close by platform design). Default behavior: Rasta & Pyramid = bar close; RSI = per tick with close backup. Reading the Chart Watch for Rasta Entry/Exit labels: they define clean structural turns on close. Watch RSI Entry (LOW touch at/below lower band) and RSI Exit (HIGH touch at/above upper band) to gauge internal energy extremes. Pyramid Add labels reveal continuation phases once a move is already in progress. Tuning Rasta smoothing: choose SMA/EMA/RMA/WMA or None. Higher smoothing → later but cleaner flips; lower smoothing → earlier but choppier. RSI bands: a common educational setting is 15/85 for strong extremes; 20/80 is a bit looser. Cooldown: increase if you see too many RSI re-fires in chop. EMA 8/21 filter: toggle ON to study “trend-gated” entries, OFF to study raw momentum flips. Backtesting Notes (for Strategy Builds) Stops (optional): trail is armed when price advances by a trigger (default D–F₀), ratchets only upward from HIGH, and hits from LOW (or Close if chosen) with a tiny undershoot buffer to avoid micro-wicks. Order sequencing per bar (mirrors the script’s code comments): Trail ratchet via HIGH Intrabar stop hit via LOW/CLOSE → immediate close If still in position at bar close: process exits (Rasta/RSI) If still in position at bar close: process Pyramid Add If flat at bar close: process entries (Rasta/RSI) Platform reality: strategies place orders at bar close in historical testing; the intrabar logic improves realism for stops and event marking but final order timestamps are still close-resolved. Inputs Reference (common) Modules: enable/disable RSI and Pyramid learning layers. Rasta: EMA length, smoothing type/length, EMA8/21 filter & adaptive flip, fog opacity, rungs on/off & limit. RSI: RSI length, signal MA length (panel), Entry band (LOW), Exit band (HIGH), cooldown bars, labels. Pyramid: EMA length, smoothing, EMA8/21 filter & adaptive adds. Execution: toggle Bar Close Only for Rasta/Pyramid; toggle Realtime + Close Backup for RSI. Stops (strategy): Fixed Stop % (first), Fixed Stop % (add), Trail Distance %, Trigger rule (auto D–F₀ or custom), undershoot buffer %, and hit source (LOW/CLOSE). What to Study With It Convergence: how often RSI-LOW entry touches precede the next Rasta flip. Divergence: cases where RSI screams exhaustion (HIGH >= upper band) but Rasta hasn’t flipped yet—often transition zones. Continuation: how Pyramid adds cluster in strong moves; how spacing changes with smoothing/filter choices. Regime changes: use EMA8/21 filter toggles to see what happens at macro turns vs chop. Limitations & Scope This is a learning tool, not a trade copier. It does not provide financial advice or automated execution. Intrabar results depend on data granularity; bar magnifier (when available) can help simulate lower-resolution ticks, but true tick-by-tick fills are a platform-level feature and not guaranteed across all symbols. Suggested Publication Settings (Strategy) Initial capital: 100 Order size: 100 USD (cash) Pyramiding: 10 Commission: 0.25% Slippage: 3 ticks Recalculate: ✓ On every tick Fill orders: ✓ Using bar magnifier (choose 1m or similar); leave On bar close unchecked for live viewing. Educational License Released under the Michael Culpepper Gratitude License (2025). Use and modify freely for education and research with attribution. No resale. No promises of profitability. Purpose is understanding, not signals.
Pine Script® strategy
by mikeyc747
1
LibTmFrLibrary "LibTmFr" This is a utility library for handling timeframes and multi-timeframe (MTF) analysis in Pine Script. It provides a collection of functions designed to handle common tasks related to period detection, session alignment, timeframe construction, and time calculations, forming a foundation for MTF indicators. Key Capabilities: 1. **MTF Period Engine:** The library includes functions for managing higher-timeframe (HTF) periods. - **Period Detection (`isNewPeriod`):** Detects the first bar of a given timeframe. It includes custom logic to handle multi-month and multi-year intervals where `timeframe.change()` may not be sufficient. - **Bar Counting (`sinceNewPeriod`):** Counts the number of bars that have passed in the current HTF period or returns the final count for a completed historical period. 2. **Automatic Timeframe Selection:** Offers functions for building a top-down analysis framework: - **Automatic HTF (`autoHTF`):** Suggests a higher timeframe (HTF) for broader context based on the current timeframe. - **Automatic LTF (`autoLTF`):** Suggests an appropriate lower timeframe (LTF) for granular intra-bar analysis. 3. **Timeframe Manipulation and Comparison:** Includes tools for working with timeframe strings: - **Build & Split (`buildTF`, `splitTF`):** Functions to programmatically construct valid Pine Script timeframe strings (e.g., "4H") and parse them back into their numeric and unit components. - **Comparison (`isHigherTF`, `isActiveTF`, `isLowerTF`):** A set of functions to check if a given timeframe is higher, lower, or the same as the script's active timeframe. - **Multiple Validation (`isMultipleTF`):** Checks if a higher timeframe is a practical multiple of the current timeframe. This is based on the assumption that checking if recent, completed HTF periods contained more than one bar is a valid proxy for preventing data gaps. 4. **Timestamp Interpolation:** Contains an `interpTimestamp()` function that calculates an absolute timestamp by interpolating at a given percentage across a specified range of bars (e.g., 50% of the way through the last 20 bars), enabling time calculations at a resolution finer than the chart's native bars. --- **DISCLAIMER** This library is provided "AS IS" and for informational and educational purposes only. It does not constitute financial, investment, or trading advice. The author assumes no liability for any errors, inaccuracies, or omissions in the code. Using this library to build trading indicators or strategies is entirely at your own risk. As a developer using this library, you are solely responsible for the rigorous testing, validation, and performance of any scripts you create based on these functions. The author shall not be held liable for any financial losses incurred directly or indirectly from the use of this library or any scripts derived from it. buildTF(quantity, unit)   Builds a Pine Script timeframe string from a numeric quantity and a unit enum. The resulting string can be used with `request.security()` or `input.timeframe`.   Parameters:      quantity (int) : series int Number to specifie how many `unit` the timeframe spans.      unit (series TFUnit) : series TFUnit The size category for the bars.   Returns: series string A Pine-style timeframe identifier, e.g. "5S" → 5-seconds bars "30" → 30-minute bars "120" → 2-hour bars "1D" → daily bars "3M" → 3-month bars "24M" → 2-year bars splitTF(tf)   Splits a Pine‑timeframe identifier into numeric quantity and unit (TFUnit).   Parameters:      tf (string) : series string Timeframe string, e.g. "5S", "30", "120", "1D", "3M", "24M".   Returns: quantity series int The numeric value of the timeframe (e.g., 15 for "15", 3 for "3M"). unit series TFUnit The unit of the timeframe (e.g., TFUnit.minutes, TFUnit.months). Notes on strings without a suffix: • Pure digits are minutes; if divisible by 60, they are treated as hours. • An "M" suffix is months; if divisible by 12, it is converted to years. autoHTF(tf)   Picks an appropriate **higher timeframe (HTF)** relative to the selected timeframe. It steps up along a coarse ladder to produce sensible jumps for top‑down analysis. Mapping → chosen HTF: ≤ 1 min → 60 (1h) ≈ ×60 ≤ 3 min → 180 (3h) ≈ ×60 ≤ 5 min → 240 (4h) ≈ ×48 ≤ 15 min → D (1 day) ≈ ×26–×32 (regular session 6.5–8 h) > 15 min → W (1 week) ≈ ×64–×80 for 30m; varies with input ≤ 1 h → W (1 week) ≈ ×32–×40 ≤ 4 h → M (1 month) ≈ ×36–×44 (~22 trading days / month) > 4 h → 3M (3 months) ≈ ×36–×66 (e.g., 12h→×36–×44; 8h→×53–×66) ≤ 1 day → 3M (3 months) ≈ ×60–×66 (~20–22 trading days / month) > 1 day → 12M (1 year) ≈ ×(252–264)/quantity ≤ 1 week → 12M (1 year) ≈ ×52 > 1 week → 48M (4 years) ≈ ×(208)/quantity = 1 M → 48M (4 years) ≈ ×48 > 1 M → error ("HTF too big") any → error ("HTF too big") Notes: • Inputs in months or years are restricted: only 1M is allowed; larger months/any years throw. • Returns a Pine timeframe string usable in `request.security()` and `input.timeframe`.   Parameters:      tf (string) : series string Selected timeframe (e.g., "D", "240", or `timeframe.period`).   Returns: series string Suggested higher timeframe. autoLTF(tf)   Selects an appropriate **lower timeframe LTF)** for intra‑bar evaluation based on the selected timeframe. The goal is to keep intra‑bar loops performant while providing enough granularity. Mapping → chosen LTF: ≤ 1 min → 1S ≈ ×60 ≤ 5 min → 5S ≈ ×60 ≤ 15 min → 15S ≈ ×60 ≤ 30 min → 30S ≈ ×60 > 30 min → 60S (1m) ≈ ×31–×59 (for 31–59 minute charts) ≤ 1 h → 1 (1m) ≈ ×60 ≤ 2 h → 2 (2m) ≈ ×60 ≤ 4 h → 5 (5m) ≈ ×48 > 4 h → 15 (15m) ≈ ×24–×48 (e.g., 6h→×24, 8h→×32, 12h→×48) ≤ 1 day → 15 (15m) ≈ ×26–×32 (regular sessions ~6.5–8h) > 1 day → 60 (60m) ≈ ×(26–32) per day × quantity ≤ 1 week → 60 (60m) ≈ ×32–×40 (≈5 sessions of ~6.5–8h) > 1 week → 240 (4h) ≈ ×(8–10) per week × quantity ≤ 1 M → 240 (4h) ≈ ×33–×44 (~20–22 sessions × 6.5–8h / 4h) ≤ 3 M → D (1d) ≈ ×(20–22) per month × quantity > 3 M → W (1w) ≈ ×(4–5) per month × quantity ≤ 1 Y → W (1w) ≈ ×52 > 1 Y → M (1M) ≈ ×12 per year × quantity Notes: • Ratios for D/W/M are given as ranges because they depend on **regular session length** (typically ~6.5–8h, not 24h). • Returned strings can be used with `request.security()` and `input.timeframe`.   Parameters:      tf (string) : series string Selected timeframe (e.g., "D", "240", or timeframe.period).   Returns: series string Suggested lower TF to use for intra‑bar work. isNewPeriod(tf, offset)   Returns `true` when a new session-aligned period begins, or on the Nth bar of that period.   Parameters:      tf (string) : series string Target higher timeframe (e.g., "D", "W", "M").      offset (simple int) : simple int 0 → checks for the first bar of the new period. 1+ → checks for the N-th bar of the period.   Returns: series bool `true` if the condition is met. sinceNewPeriod(tf, offset)   Counts how many bars have passed within a higher timeframe (HTF) period. For daily, weekly, and monthly resolutions, the period is aligned with the trading session.   Parameters:      tf (string) : series string Target parent timeframe (e.g., "60", "D").      offset (simple int) : simple int 0 → Running count for the current period. 1+ → Finalized count for the Nth most recent *completed* period.   Returns: series int Number of bars. isHigherTF(tf, main)   Returns `true` when the selected timeframe represents a higher resolution than the active timeframe.   Parameters:      tf (string) : series string Selected timeframe.      main (bool) : series bool When `true`, the comparison is made against the chart's main timeframe instead of the script's active timeframe. Optional. Defaults to `false`.   Returns: series bool `true` if `tf` > active TF; otherwise `false`. isActiveTF(tf, main)   Returns `true` when the selected timeframe represents the exact resolution of the active timeframe.   Parameters:      tf (string) : series string Selected timeframe.      main (bool) : series bool When `true`, the comparison is made against the chart's main timeframe instead of the script's active timeframe. Optional. Defaults to `false`.   Returns: series bool `true` if `tf` == active TF; otherwise `false`. isLowerTF(tf, main)   Returns `true` when the selected timeframe represents a lower resolution than the active timeframe.   Parameters:      tf (string) : series string Selected timeframe.      main (bool) : series bool When `true`, the comparison is made against the chart's main timeframe instead of the script's active timeframe. Optional. Defaults to `false`.   Returns: series bool `true` if `tf` < active TF; otherwise `false`. isMultipleTF(tf)   Returns `true` if the selected timeframe (`tf`) is a practical multiple of the active skript's timeframe. It verifies this by checking if `tf` is a higher timeframe that has consistently contained more than one bar of the skript's timeframe in recent periods. The period detection is session-aware.   Parameters:      tf (string) : series string The higher timeframe to check.   Returns: series bool `true` if `tf` is a practical multiple; otherwise `false`. interpTimestamp(offStart, offEnd, pct)   Calculates a precise absolute timestamp by interpolating within a bar range based on a percentage. This version works with RELATIVE bar offsets from the current bar.   Parameters:      offStart (int) : series int The relative offset of the starting bar (e.g., 10 for 10 bars ago).      offEnd (int) : series int The relative offset of the ending bar (e.g., 1 for 1 bar ago). Must be <= offStart.      pct (float) : series float The percentage of the bar range to measure (e.g., 50.5 for 50.5%). Values are clamped to the range.   Returns: series int The calculated, interpolated absolute Unix timestamp in milliseconds.
Pine Script® library
by AustrianTradingMachine