Começar

Pesquisar nos scripts por "mtf"

Price Action Concepts [RUDYINDICATOR]/// This work is licensed under a Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) creativecommons.org // © RUDYBANK INDICATOR - formerly know as RUDY INDICATOR //@version=5 indicator("Price Action Concepts ", shorttitle = "RUDYINDICATOR-V1 - Price Action RUDYINDICATOR ", overlay = true, max_lines_count = 500, max_labels_count = 500, max_boxes_count = 500, max_bars_back = 500, max_polylines_count = 100) //-----------------------------------------------------------------------------{ //Boolean set //-----------------------------------------------------------------------------{ s_BOS = 0 s_CHoCH = 1 i_BOS = 2 i_CHoCH = 3 i_pp_CHoCH = 4 green_candle = 5 red_candle = 6 s_CHoCHP = 7 i_CHoCHP = 8 boolean = array.from( false , false , false , false , false , false , false , false , false ) //-----------------------------------------------------------------------------{ // User inputs //-----------------------------------------------------------------------------{ show_swing_ms = input.string ("All" , "Swing        " , inline = "1", group = "MARKET STRUCTURE" , options = ) show_internal_ms = input.string ("All" , "Internal     " , inline = "2", group = "MARKET STRUCTURE" , options = ) internal_r_lookback = input.int (5 , "" , inline = "2", group = "MARKET STRUCTURE" , minval = 2) swing_r_lookback = input.int (50 , "" , inline = "1", group = "MARKET STRUCTURE" , minval = 2) ms_mode = input.string ("Manual" , "Market Structure Mode" , inline = "a", group = "MARKET STRUCTURE" , tooltip = " Use selected lenght\n Use automatic lenght" ,options = ) show_mtf_str = input.bool (true , "MTF Scanner" , inline = "9", group = "MARKET STRUCTURE" , tooltip = "Display Multi-Timeframe Market Structure Trend Directions. Green = Bullish. Red = Bearish") show_eql = input.bool (false , "Show EQH/EQL" , inline = "6", group = "MARKET STRUCTURE") plotcandle_bool = input.bool (false , "Plotcandle" , inline = "3", group = "MARKET STRUCTURE" , tooltip = "Displays a cleaner colored candlestick chart in place of the default candles. (requires hiding the current ticker candles)") barcolor_bool = input.bool (false , "Bar Color" , inline = "4", group = "MARKET STRUCTURE" , tooltip = "Color the candle bodies according to market strucutre trend") i_ms_up_BOS = input.color (#089981 , "" , inline = "2", group = "MARKET STRUCTURE") i_ms_dn_BOS = input.color (#f23645 , "" , inline = "2", group = "MARKET STRUCTURE") s_ms_up_BOS = input.color (#089981 , "" , inline = "1", group = "MARKET STRUCTURE") s_ms_dn_BOS = input.color (#f23645 , "" , inline = "1", group = "MARKET STRUCTURE") lvl_daily = input.bool (false , "Day   " , inline = "1", group = "HIGHS & LOWS MTF") lvl_weekly = input.bool (false , "Week " , inline = "2", group = "HIGHS & LOWS MTF") lvl_monthly = input.bool (false , "Month" , inline = "3", group = "HIGHS & LOWS MTF") lvl_yearly = input.bool (false , "Year  " , inline = "4", group = "HIGHS & LOWS MTF") css_d = input.color (color.blue , "" , inline = "1", group = "HIGHS & LOWS MTF") css_w = input.color (color.blue , "" , inline = "2", group = "HIGHS & LOWS MTF") css_m = input.color (color.blue , "" , inline = "3", group = "HIGHS & LOWS MTF") css_y = input.color (color.blue , "" , inline = "4", group = "HIGHS & LOWS MTF") s_d = input.string ('⎯⎯⎯' , '' , inline = '1', group = 'HIGHS & LOWS MTF' , options = ) s_w = input.string ('⎯⎯⎯' , '' , inline = '2', group = 'HIGHS & LOWS MTF' , options = ) s_m = input.string ('⎯⎯⎯' , '' , inline = '3', group = 'HIGHS & LOWS MTF' , options = ) s_y = input.string ('⎯⎯⎯' , '' , inline = '4', group = 'HIGHS & LOWS MTF' , options = ) ob_show = input.bool (true , "Show Last    " , inline = "1", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Display volumetric order blocks on the chart \n\n Ammount of volumetric order blocks to show") ob_num = input.int (5 , "" , inline = "1", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Orderblocks number", minval = 1, maxval = 10) ob_metrics_show = input.bool (true , "Internal Buy/Sell Activity" , inline = "2", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Display volume metrics that have formed the orderblock") css_metric_up = input.color (color.new(#089981, 50) , "         " , inline = "2", group = "VOLUMETRIC ORDER BLOCKS") css_metric_dn = input.color (color.new(#f23645 , 50) , "" , inline = "2", group = "VOLUMETRIC ORDER BLOCKS") ob_swings = input.bool (false , "Swing Order Blocks" , inline = "a", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Display swing volumetric order blocks") css_swing_up = input.color (color.new(color.gray , 90) , "                 " , inline = "a", group = "VOLUMETRIC ORDER BLOCKS") css_swing_dn = input.color (color.new(color.silver, 90) , "" , inline = "a", group = "VOLUMETRIC ORDER BLOCKS") ob_filter = input.string ("None" , "Filtering             " , inline = "d", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Filter out volumetric order blocks by BOS/CHoCH/CHoCH+", options = ) ob_mitigation = input.string ("Absolute" , "Mitigation           " , inline = "4", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Trigger to remove volumetric order blocks", options = ) ob_pos = input.string ("Precise" , "Positioning          " , inline = "k", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Position of the Order Block\n Cover the whole candle\n Cover half candle\n Adjust to volatility\n Same as Accurate but more precise", options = ) use_grayscale = input.bool (false , "Grayscale" , inline = "6", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Use gray as basic order blocks color") use_show_metric = input.bool (true , "Show Metrics" , inline = "7", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Show volume associated with the orderblock and his relevance") use_middle_line = input.bool (true , "Show Middle-Line" , inline = "8", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Show mid-line order blocks") use_overlap = input.bool (true , "Hide Overlap" , inline = "9", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = "Hide overlapping order blocks") use_overlap_method = input.string ("Previous" , "Overlap Method    " , inline = "Z", group = "VOLUMETRIC ORDER BLOCKS" , tooltip = " Preserve the most recent volumetric order blocks\n\n Preserve the previous volumetric order blocks", options = ) ob_bull_css = input.color (color.new(#089981 , 90) , "" , inline = "1", group = "VOLUMETRIC ORDER BLOCKS") ob_bear_css = input.color (color.new(#f23645 , 90) , "" , inline = "1", group = "VOLUMETRIC ORDER BLOCKS") show_acc_dist_zone = input.bool (false , "" , inline = "1", group = "Accumulation And Distribution") zone_mode = input.string ("Fast" , "" , inline = "1", group = "Accumulation And Distribution" , tooltip = " Find small zone pattern formation\n Find bigger zone pattern formation" ,options = ) acc_css = input.color (color.new(#089981 , 60) , "" , inline = "1", group = "Accumulation And Distribution") dist_css = input.color (color.new(#f23645 , 60) , "" , inline = "1", group = "Accumulation And Distribution") show_lbl = input.bool (false , "Show swing point" , inline = "1", group = "High and Low" , tooltip = "Display swing point") show_mtb = input.bool (false , "Show High/Low/Equilibrium" , inline = "2", group = "High and Low" , tooltip = "Display Strong/Weak High And Low and Equilibrium") toplvl = input.color (color.red , "Premium Zone   " , inline = "3", group = "High and Low") midlvl = input.color (color.gray , "Equilibrium Zone" , inline = "4", group = "High and Low") btmlvl = input.color (#089981 , "Discount Zone    " , inline = "5", group = "High and Low") fvg_enable = input.bool (false , "        " , inline = "1", group = "FAIR VALUE GAP" , tooltip = "Display fair value gap") what_fvg = input.string ("FVG" , "" , inline = "1", group = "FAIR VALUE GAP" , tooltip = "Display fair value gap", options = ) fvg_num = input.int (5 , "Show Last  " , inline = "1a", group = "FAIR VALUE GAP" , tooltip = "Number of fvg to show") fvg_upcss = input.color (color.new(#089981, 80) , "" , inline = "1", group = "FAIR VALUE GAP") fvg_dncss = input.color (color.new(color.red , 80) , "" , inline = "1", group = "FAIR VALUE GAP") fvg_extend = input.int (10 , "Extend FVG" , inline = "2", group = "FAIR VALUE GAP" , tooltip = "Extend the display of the FVG.") fvg_src = input.string ("Close" , "Mitigation  " , inline = "3", group = "FAIR VALUE GAP" , tooltip = " Use the close of the body as trigger\n\n Use the extreme point of the body as trigger", options = ) fvg_tf = input.timeframe ("" , "Timeframe " , inline = "4", group = "FAIR VALUE GAP" , tooltip = "Timeframe of the fair value gap") t = color.t (ob_bull_css) invcol = color.new (color.white , 100) //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - UDT } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} type bar float o = open float c = close float h = high float l = low float v = volume int n = bar_index int t = time type Zphl line top line bottom label top_label label bottom_label bool stopcross bool sbottomcross bool itopcross bool ibottomcross string txtup string txtdn float topy float bottomy float topx float bottomx float tup float tdn int tupx int tdnx float itopy float itopx float ibottomy float ibottomx float uV float dV type FVG box box line ln bool bull float top float btm int left int right type ms float p int n float l type msDraw int n float p color css string txt bool bull type obC float top float btm int left float avg float dV float cV int wM int blVP int brVP int dir float h float l int n type obD box ob box eOB box blB box brB line mL type zone chart.point points float p int c int t type hqlzone box pbx box ebx box lbx label plb label elb label lbl type ehl float pt int t float pb int b type pattern string found = "None" bool isfound = false int period = 0 bool bull = false type alerts bool chochswing = false bool chochplusswing = false bool swingbos = false bool chochplus = false bool choch = false bool bos = false bool equal = false bool ob = false bool swingob = false bool zone = false bool fvg = false bool obtouch = false //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - End } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - General Setup } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} bar b = bar.new() var pattern p = pattern.new() alerts blalert = alerts.new() alerts bralert = alerts.new() if p.isfound p.period += 1 if p.period == 50 p.period := 0 p.found := "None" p.isfound := false p.bull := na switch b.c > b.o => boolean.set(green_candle, true) b.c < b.o => boolean.set(red_candle , true) f_zscore(src, lookback) => (src - ta.sma(src, lookback)) / ta.stdev(src, lookback) var int iLen = internal_r_lookback var int sLen = swing_r_lookback vv = f_zscore(((close - close ) / close ) * 100,iLen) if ms_mode == "Dynamic" switch vv >= 1.5 or vv <= -1.5 => iLen := 10 vv >= 1.6 or vv <= -1.6 => iLen := 9 vv >= 1.7 or vv <= -1.7 => iLen := 8 vv >= 1.8 or vv <= -1.8 => iLen := 7 vv >= 1.9 or vv <= -1.9 => iLen := 6 vv >= 2.0 or vv <= -2.0 => iLen := 5 => iLen var msline = array.new(0) iH = ta.pivothigh(high, iLen, iLen) sH = ta.pivothigh(high, sLen, sLen) iL = ta.pivotlow (low , iLen, iLen) sL = ta.pivotlow (low , sLen, sLen) //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - End } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - ARRAYS } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} hl () => = request.security(syminfo.tickerid , 'D' , hl() , lookahead = barmerge.lookahead_on) = request.security(syminfo.tickerid , 'W' , hl() , lookahead = barmerge.lookahead_on) = request.security(syminfo.tickerid , 'M' , hl() , lookahead = barmerge.lookahead_on) = request.security(syminfo.tickerid , '12M', hl() , lookahead = barmerge.lookahead_on) lstyle(style) => out = switch style '⎯⎯⎯' => line.style_solid '----' => line.style_dashed '····' => line.style_dotted mtfphl(h, l ,tf ,css, pdhl_style) => var line hl = line.new( na , na , na , na , xloc = xloc.bar_time , color = css , style = lstyle(pdhl_style) ) var line ll = line.new( na , na , na , na , xloc = xloc.bar_time , color = css , style = lstyle(pdhl_style) ) var label lbl = label.new( na , na , xloc = xloc.bar_time , text = str.format('P{0}L', tf) , color = invcol , textcolor = css , size = size.small , style = label.style_label_left ) var label hlb = label.new( na , na , xloc = xloc.bar_time , text = str.format('P{0}H', tf) , color = invcol , textcolor = css , size = size.small , style = label.style_label_left ) hy = ta.valuewhen(h != h , h , 1) hx = ta.valuewhen(h == high , time , 1) ly = ta.valuewhen(l != l , l , 1) lx = ta.valuewhen(l == low , time , 1) if barstate.islast extension = time + (time - time ) * 50 line.set_xy1(hl , hx , hy) line.set_xy2(hl , extension , hy) label.set_xy(hlb, extension , hy) line.set_xy1(ll , lx , ly) line.set_xy2(ll , extension , ly) label.set_xy(lbl, extension , ly) if lvl_daily mtfphl(pdh , pdl , 'D' , css_d, s_d) if lvl_weekly mtfphl(pwh , pwl , 'W' , css_w, s_w) if lvl_monthly mtfphl(pmh , pml, 'M' , css_m, s_m) if lvl_yearly mtfphl(pyh , pyl , '12M', css_y, s_y) //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - End } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - Market Structure } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} method darkcss(color css, float factor, bool bull) => blue = color.b(css) * (1 - factor) red = color.r(css) * (1 - factor) green = color.g(css) * (1 - factor) color.rgb(red, green, blue, 0) method f_line(msDraw d, size, style) => var line id = na var label lbl = na id := line.new( d.n , d.p , b.n , d.p , color = d.css , width = 1 , style = style ) if msline.size() >= 250 line.delete(msline.shift()) msline.push(id) lbl := label.new( int(math.avg(d.n, b.n)) , d.p , d.txt , color = invcol , textcolor = d.css , style = d.bull ? label.style_label_down : label.style_label_up , size = size , text_font_family = font.family_monospace ) structure(bool mtf) => msDraw drw = na bool isdrw = false bool isdrwS = false var color css = na var color icss = na var int itrend = 0 var int trend = 0 bool bull_ob = false bool bear_ob = false bool s_bull_ob = false bool s_bear_ob = false n = bar_index var ms up = ms.new( array.new() , array.new< int >() , array.new() ) var ms dn = ms.new( array.new() , array.new< int >() , array.new() ) var ms sup = ms.new( array.new() , array.new< int >() , array.new() ) var ms sdn = ms.new( array.new() , array.new< int >() , array.new() ) switch show_swing_ms "All" => boolean.set(s_BOS , true ), boolean.set(s_CHoCH, true ) , boolean.set(s_CHoCHP, true ) "CHoCH" => boolean.set(s_BOS , false), boolean.set(s_CHoCH, true ) , boolean.set(s_CHoCHP, false ) "CHoCH+" => boolean.set(s_BOS , false), boolean.set(s_CHoCH, false) , boolean.set(s_CHoCHP, true ) "BOS" => boolean.set(s_BOS , true ), boolean.set(s_CHoCH, false) , boolean.set(s_CHoCHP, false ) "None" => boolean.set(s_BOS , false), boolean.set(s_CHoCH, false) , boolean.set(s_CHoCHP, false ) => na switch show_internal_ms "All" => boolean.set(i_BOS, true ), boolean.set(i_CHoCH, true ), boolean.set(i_CHoCHP, true ) "CHoCH" => boolean.set(i_BOS, false), boolean.set(i_CHoCH, true ), boolean.set(i_CHoCHP, false) "CHoCH+" => boolean.set(i_BOS, false), boolean.set(i_CHoCH, false ), boolean.set(i_CHoCHP, true ) "BOS" => boolean.set(i_BOS, true ), boolean.set(i_CHoCH, false ), boolean.set(i_CHoCHP, false) "None" => boolean.set(i_BOS, false), boolean.set(i_CHoCH, false ), boolean.set(i_CHoCHP, false) => na switch iH => up.p.unshift(b.h ) up.l.unshift(b.h ) up.n.unshift(n ) iL => dn.p.unshift(b.l ) dn.l.unshift(b.l ) dn.n.unshift(n ) sL => sdn.p.unshift(b.l ) sdn.l.unshift(b.l ) sdn.n.unshift(n ) sH => sup.p.unshift(b.h ) sup.l.unshift(b.h ) sup.n.unshift(n ) // INTERNAL BULLISH STRUCTURE if up.p.size() > 0 and dn.l.size() > 1 if ta.crossover(b.c, up.p.first()) bool CHoCH = na string txt = na if itrend < 0 CHoCH := true switch not CHoCH => txt := "BOS" css := i_ms_up_BOS blalert.bos := true if boolean.get(i_BOS) and mtf == false and na(drw) isdrw := true drw := msDraw.new( up.n.first() , up.p.first() , i_ms_up_BOS , txt , true ) CHoCH => dn.l.first() > dn.l.get(1) ? blalert.chochplus : blalert.choch txt := dn.l.first() > dn.l.get(1) ? "CHoCH+" : "CHoCH" css := i_ms_up_BOS.darkcss(0.25, true) if (dn.l.first() > dn.l.get(1) ? boolean.get(i_CHoCHP) : boolean.get(i_CHoCH)) and mtf == false and na(drw) isdrw := true drw := msDraw.new( up.n.first() , up.p.first() , i_ms_up_BOS.darkcss(0.25, true) , txt , true ) if mtf == false switch ob_filter == "None" => bull_ob := true ob_filter == "BOS" and txt == "BOS" => bull_ob := true ob_filter == "CHoCH" and txt == "CHoCH" => bull_ob := true ob_filter == "CHoCH+" and txt == "CHoCH+" => bull_ob := true itrend := 1 up.n.clear() up.p.clear() // INTERNAL BEARISH STRUCTURE if dn.p.size() > 0 and up.l.size() > 1 if ta.crossunder(b.c, dn.p.first()) bool CHoCH = na string txt = na if itrend > 0 CHoCH := true switch not CHoCH => bralert.bos := true txt := "BOS" css := i_ms_dn_BOS if boolean.get(i_BOS) and mtf == false and na(drw) isdrw := true drw := msDraw.new( dn.n.first() , dn.p.first() , i_ms_dn_BOS , txt , false ) CHoCH => if up.l.first() < up.l.get(1) bralert.chochplus := true else bralert.choch := true txt := up.l.first() < up.l.get(1) ? "CHoCH+" : "CHoCH" css := i_ms_dn_BOS.darkcss(0.25, false) if (up.l.first() < up.l.get(1) ? boolean.get(i_CHoCHP) : boolean.get(i_CHoCH)) and mtf == false and na(drw) isdrw := true drw := msDraw.new( dn.n.first() , dn.p.first() , i_ms_dn_BOS.darkcss(0.25, false) , txt , false ) if mtf == false switch ob_filter == "None" => bear_ob := true ob_filter == "BOS" and txt == "BOS" => bear_ob := true ob_filter == "CHoCH" and txt == "CHoCH" => bear_ob := true ob_filter == "CHoCH+" and txt == "CHoCH+" => bear_ob := true itrend := -1 dn.n.clear() dn.p.clear() // SWING BULLISH STRUCTURE if sup.p.size() > 0 and sdn.l.size() > 1 if ta.crossover(b.c, sup.p.first()) bool CHoCH = na string txt = na if trend < 0 CHoCH := true switch not CHoCH => blalert.swingbos := true txt := "BOS" icss := s_ms_up_BOS if boolean.get(s_BOS) and mtf == false and na(drw) isdrwS := true drw := msDraw.new( sup.n.first() , sup.p.first() , s_ms_up_BOS , txt , true ) CHoCH => if sdn.l.first() > sdn.l.get(1) blalert.chochplusswing := true else blalert.chochswing := true txt := sdn.l.first() > sdn.l.get(1) ? "CHoCH+" : "CHoCH" icss := s_ms_up_BOS.darkcss(0.25, true) if (sdn.l.first() > sdn.l.get(1) ? boolean.get(s_CHoCHP) : boolean.get(s_CHoCH)) and mtf == false and na(drw) isdrwS := true drw := msDraw.new( sup.n.first() , sup.p.first() , s_ms_up_BOS.darkcss(0.25, true) , txt , true ) if mtf == false switch ob_filter == "None" => s_bull_ob := true ob_filter == "BOS" and txt == "BOS" => s_bull_ob := true ob_filter == "CHoCH" and txt == "CHoCH" => s_bull_ob := true ob_filter == "CHoCH+" and txt == "CHoCH+" => s_bull_ob := true trend := 1 sup.n.clear() sup.p.clear() // SWING BEARISH STRUCTURE if sdn.p.size() > 0 and sup.l.size() > 1 if ta.crossunder(b.c, sdn.p.first()) bool CHoCH = na string txt = na if trend > 0 CHoCH := true switch not CHoCH => bralert.swingbos := true txt := "BOS" icss := s_ms_dn_BOS if boolean.get(s_BOS) and mtf == false and na(drw) isdrwS := true drw := msDraw.new( sdn.n.first() , sdn.p.first() , s_ms_dn_BOS , txt , false ) CHoCH => if sup.l.first() < sup.l.get(1) bralert.chochplusswing := true else bralert.chochswing := true txt := sup.l.first() < sup.l.get(1) ? "CHoCH+" : "CHoCH" icss := s_ms_dn_BOS.darkcss(0.25, false) if (sup.l.first() < sup.l.get(1) ? boolean.get(s_CHoCHP) : boolean.get(s_CHoCH)) and mtf == false and na(drw) isdrwS := true drw := msDraw.new( sdn.n.first() , sdn.p.first() , s_ms_dn_BOS.darkcss(0.25, false) , txt , false ) if mtf == false switch ob_filter == "None" => s_bear_ob := true ob_filter == "BOS" and txt == "BOS" => s_bear_ob := true ob_filter == "CHoCH" and txt == "CHoCH" => s_bear_ob := true ob_filter == "CHoCH+" and txt == "CHoCH+" => s_bear_ob := true trend := -1 sdn.n.clear() sdn.p.clear() = structure(false) if isdrw f_line(drw, size.small, line.style_dashed) if isdrwS f_line(drw, size.small, line.style_solid) = request.security("", "15" , structure(true)) = request.security("", "60" , structure(true)) = request.security("", "240" , structure(true)) = request.security("", "1440" , structure(true)) if show_mtf_str var tab = table.new(position = position.top_right, columns = 10, rows = 10, bgcolor = na, frame_color = color.rgb(54, 58, 69, 0), frame_width = 1, border_color = color.rgb(54, 58, 69, 100), border_width = 1) table.cell(tab, 0, 1, text = "15" , text_color = color.silver, text_halign = text.align_center, text_size = size.normal, bgcolor = chart.bg_color, text_font_family = font.family_monospace, width = 2) table.cell(tab, 0, 2, text = "1H" , text_color = color.silver, text_halign = text.align_center, text_size = size.normal, bgcolor = chart.bg_color, text_font_family = font.family_monospace, width = 2) table.cell(tab, 0, 3, text = "4H" , text_color = color.silver, text_halign = text.align_center, text_size = size.normal, bgcolor = chart.bg_color, text_font_family = font.family_monospace, width = 2) table.cell(tab, 0, 4, text = "1D" , text_color = color.silver, text_halign = text.align_center, text_size = size.normal, bgcolor = chart.bg_color, text_font_family = font.family_monospace, width = 2) table.cell(tab, 1, 1, text = itrend15 == 1 ? "BULLISH" : itrend15 == -1 ? "BEARISH" : na , text_halign = text.align_center, text_size = size.normal, text_color = itrend15 == 1 ? i_ms_up_BOS.darkcss(-0.25, true) : itrend15 == -1 ? i_ms_dn_BOS.darkcss(0.25, false) : color.gray, bgcolor = chart.bg_color, text_font_family = font.family_monospace) table.cell(tab, 1, 2, text = itrend1H == 1 ? "BULLISH" : itrend1H == -1 ? "BEARISH" : na , text_halign = text.align_center, text_size = size.normal, text_color = itrend1H == 1 ? i_ms_up_BOS.darkcss(-0.25, true) : itrend1H == -1 ? i_ms_dn_BOS.darkcss(0.25, false) : color.gray, bgcolor = chart.bg_color, text_font_family = font.family_monospace) table.cell(tab, 1, 3, text = itrend4H == 1 ? "BULLISH" : itrend4H == -1 ? "BEARISH" : na , text_halign = text.align_center, text_size = size.normal, text_color = itrend4H == 1 ? i_ms_up_BOS.darkcss(-0.25, true) : itrend4H == -1 ? i_ms_dn_BOS.darkcss(0.25, false) : color.gray, bgcolor = chart.bg_color, text_font_family = font.family_monospace) table.cell(tab, 1, 4, text = itrend1D == 1 ? "BULLISH" : itrend1D == -1 ? "BEARISH" : na , text_halign = text.align_center, text_size = size.normal, text_color = itrend1D == 1 ? i_ms_up_BOS.darkcss(-0.25, true) : itrend1D == -1 ? i_ms_dn_BOS.darkcss(0.25, false) : color.gray, bgcolor = chart.bg_color, text_font_family = font.family_monospace) table.cell(tab, 0, 5, text = "Detected Pattern", text_halign = text.align_center, text_size = size.normal, text_color = color.silver, bgcolor = chart.bg_color, text_font_family = font.family_monospace) table.cell(tab, 0, 6, text = p.found, text_halign = text.align_center, text_size = size.normal, text_color = na(p.bull) ? color.white : p.bull ? i_ms_up_BOS.darkcss(-0.25, true) : p.bull == false ? i_ms_dn_BOS.darkcss(0.25, false) : na, bgcolor = chart.bg_color, text_font_family = font.family_monospace) table.merge_cells(tab, 0, 5, 1, 5) table.merge_cells(tab, 0, 6, 1, 6) //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - End } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - Strong/Weak High/Low And Equilibrium } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} var phl = Zphl.new( na , na , label.new(na , na , color = invcol , textcolor = i_ms_dn_BOS , style = label.style_label_down , size = size.tiny , text = "") , label.new(na , na , color = invcol , textcolor = i_ms_up_BOS , style = label.style_label_up , size = size.tiny , text = "") , true , true , true , true , "" , "" , 0 , 0 , 0 , 0 , high , low , 0 , 0 , 0 , 0 , 0 , 0 , na , na ) zhl(len)=> upper = ta.highest(len) lower = ta.lowest(len) var float out = 0 out := b.h > upper ? 0 : b.l < lower ? 1 : out top = out == 0 and out != 0 ? b.h : 0 btm = out == 1 and out != 1 ? b.l : 0 = zhl(sLen) = zhl(iLen) upphl(trend) => var label lbl = label.new( na , na , color = invcol , textcolor = toplvl , style = label.style_label_down , size = size.small ) if top phl.stopcross := true phl.txtup := top > phl.topy ? "HH" : "HL" if show_lbl topl = label.new( b.n - swing_r_lookback , top , phl.txtup , color = invcol , textcolor = toplvl , style = label.style_label_down , size = size.small ) line.delete(phl.top ) phl.top := line.new( b.n - sLen , top , b.n , top , color = toplvl) phl.topy := top phl.topx := b.n - sLen phl.tup := top phl.tupx := b.n - sLen if itop phl.itopcross := true phl.itopy := itop phl.itopx := b.n - iLen phl.tup := math.max(high, phl.tup) phl.tupx := phl.tup == high ? b.n : phl.tupx phl.uV := phl.tup != phl.tup ? b.v : phl.uV if barstate.islast line.set_xy1( phl.top , phl.tupx , phl.tup ) line.set_xy2( phl.top , b.n + 50 , phl.tup ) label.set_x( lbl , b.n + 50 ) label.set_y( lbl , phl.tup ) dist = math.abs(phl.uV / (phl.uV + phl.dV)) * 100 label.set_text (lbl, trend < 0 ? "Strong High | " + str.tostring(phl.uV, format.volume) + " (" + str.tostring(math.round(dist,0)) + "%)" : "Weak High | " + str.tostring(phl.uV, format.volume) + " (" + str.tostring(math.round(dist,0)) + "%)") dnphl(trend) => var label lbl = label.new( na , na , color = invcol , textcolor = btmlvl , style = label.style_label_up , size = size.small ) if btm phl.sbottomcross := true phl.txtdn := btm > phl.bottomy ? "LH" : "LL" if show_lbl btml = label.new( b.n - swing_r_lookback , btm, phl.txtdn , color = invcol , textcolor = btmlvl , style = label.style_label_up , size = size.small ) line.delete(phl.bottom ) phl.bottom := line.new( b.n - sLen , btm , b.n , btm , color = btmlvl ) phl.bottomy := btm phl.bottomx := b.n - sLen phl.tdn := btm phl.tdnx := b.n - sLen if ibtm phl.ibottomcross := true phl.ibottomy := ibtm phl.ibottomx := b.n - iLen phl.tdn := math.min(low, phl.tdn) phl.tdnx := phl.tdn == low ? b.n : phl.tdnx phl.dV := phl.tdn != phl.tdn ? b.v : phl.dV if barstate.islast line.set_xy1( phl.bottom , phl.tdnx , phl.tdn ) line.set_xy2( phl.bottom , b.n + 50 , phl.tdn ) label.set_x( lbl , b.n + 50 ) label.set_y( lbl , phl.tdn ) dist = math.abs(phl.dV / (phl.uV + phl.dV)) * 100 label.set_text (lbl, trend > 0 ? "Strong Low | " + str.tostring(phl.dV, format.volume) + " (" + str.tostring(math.round(dist,0)) + "%)" : "Weak Low | " + str.tostring(phl.uV, format.volume) + " (" + str.tostring(math.round(dist,0)) + "%)") midphl() => avg = math.avg(phl.bottom.get_y2(), phl.top.get_y2()) var line l = line.new( y1 = avg , y2 = avg , x1 = b.n - sLen , x2 = b.n + 50 , color = midlvl , style = line.style_solid ) var label lbl = label.new( x = b.n + 50 , y = avg , text = "Equilibrium" , style = label.style_label_left , color = invcol , textcolor = midlvl , size = size.small ) if barstate.islast more = (phl.bottom.get_x1() + phl.bottom.get_x2()) > (phl.top.get_x1() + phl.top.get_x2()) ? phl.top.get_x1() : phl.bottom.get_x1() line.set_xy1(l , more , avg) line.set_xy2(l , b.n + 50, avg) label.set_x (lbl , b.n + 50 ) label.set_y (lbl , avg ) dist = math.abs((l.get_y2() - close) / close) * 100 label.set_text (lbl, "Equilibrium (" + str.tostring(math.round(dist,0)) + "%)") hqlzone() => if barstate.islast var hqlzone dZone = hqlzone.new( box.new( na , na , na , na , bgcolor = color.new(toplvl, 70) , border_color = na ) , box.new( na , na , na , na , bgcolor = color.new(midlvl, 70) , border_color = na ) , box.new( na , na , na , na , bgcolor = color.new(btmlvl, 70) , border_color = na ) , label.new(na, na, text = "Premium" , color = invcol, textcolor = toplvl, style = label.style_label_down, size = size.small) , label.new(na, na, text = "Equilibrium", color = invcol, textcolor = midlvl, style = label.style_label_left, size = size.small) , label.new(na, na, text = "Discount" , color = invcol, textcolor = btmlvl, style = label.style_label_up , size = size.small) ) dZone.pbx.set_lefttop(int(math.max(phl.topx, phl.bottomx)) , phl.tup) dZone.pbx.set_rightbottom(b.n + 50 , 0.95 * phl.tup + 0.05 * phl.tdn) dZone.ebx.set_lefttop(int(math.max(phl.topx, phl.bottomx)), 0.525 * phl.tup + 0.475 * phl.tdn) dZone.ebx.set_rightbottom(b.n + 50 , 0.525 * phl.tdn + 0.475 * phl.tup) dZone.lbx.set_lefttop(int(math.max(phl.topx, phl.bottomx)), 0.95 * phl.tdn + 0.05 * phl.tup) dZone.lbx.set_rightbottom(b.n + 50 , phl.tdn) dZone.plb.set_xy( int(math.avg(math.max(phl.topx, phl.bottomx), int(b.n + 50))) , phl.tup) dZone.elb.set_xy( int(b.n + 50) , math.avg(phl.tup, phl.tdn)) dZone.lbl.set_xy( int(math.avg(math.max(phl.topx, phl.bottomx), int(b.n + 50))) , phl.tdn) if show_mtb upphl (trend) dnphl (trend) hqlzone() //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - End } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - Volumetric Order Block } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} method eB(box b, bool ext, color css, bool swing) => b.unshift( box.new( na , na , na , na , xloc = xloc.bar_time , text_font_family = font.family_monospace , extend = ext ? extend.right : extend.none , border_color = swing ? color.new(css, 0) : color.new(color.white,100) , bgcolor = css , border_width = 1 ) ) method eL(line l, bool ext, bool solid, color css) => l.unshift( line.new( na , na , na , na , width = 1 , color = css , xloc = xloc.bar_time , extend = ext ? extend.right : extend.none , style = solid ? line.style_solid : line.style_dashed ) ) method drawVOB(bool cdn, bool bull, color css, int loc, bool swing) => = request.security( syminfo.tickerid , "" , , lookahead = barmerge.lookahead_off ) var obC obj = obC.new( array.new() , array.new() , array.new< int >() , array.new() , array.new() , array.new() , array.new< int >() , array.new< int >() , array.new< int >() , array.new< int >() , array.new() , array.new() , array.new< int >() ) var obD draw = obD.new( array.new() , array.new() , array.new() , array.new() , array.new() ) if barstate.isfirst for i = 0 to ob_num - 1 draw.mL .eL(false, false, use_grayscale ? color.new(color.gray, 0) : color.new(css,0)) draw.ob .eB(false, use_grayscale ? color.new(color.gray, 90) : css, swing) draw.blB.eB(false, css_metric_up , swing) draw.brB.eB(false, css_metric_dn , swing) draw.eOB.eB(true , use_grayscale ? color.new(color.gray, 90) : css, swing) float pos = ob_pos == "Full" ? (bull ? high : low) : ob_pos == "Middle" ? ohlc4 : ob_pos == "Accurate" ? hl2 : hl2 if cdn obj.h.clear() obj.l.clear() obj.n.clear() for i = 0 to math.abs((loc - b.n)) - 1 obj.h.push(hH ) obj.l.push(lL ) obj.n.push(b.t ) // obj.h.reverse() // obj.l.reverse() int iU = obj.l.indexof(obj.l.min()) + 1 int iD = obj.h.indexof(obj.h.max()) + 1 obj.dir.unshift( bull ? (b.c > b.o ? 1 : -1) : (b.c > b.o ? 1 : -1) ) obj.top.unshift( bull ? pos : obj.h.max() ) obj.btm.unshift( bull ? obj.l.min() : pos ) obj.left.unshift( bull ? obj.n.get(obj.l.indexof(obj.l.min())) : obj.n.get(obj.h.indexof(obj.h.max())) ) obj.avg.unshift( math.avg(obj.top.first(), obj.btm.first()) ) obj.cV.unshift( bull ? b.v : b.v ) if ob_pos == "Precise" switch bull true => if obj.avg.get(0) < (b.c < b.o ? b.c : b.o ) and obj.top.get(0) > hlcc4 obj.top.set(0, obj.avg.get(0)) obj.avg.set(0, math.avg(obj.top.first(), obj.btm.first())) false => if obj.avg.get(0) > (b.c < b.o ? b.o : b.c ) and obj.btm.get(0) < hlcc4 obj.btm.set(0, obj.avg.get(0)) obj.avg.set(0, math.avg(obj.top.first(), obj.btm.first())) obj.blVP.unshift ( 0 ) obj.brVP.unshift ( 0 ) obj.wM .unshift ( 1 ) if use_overlap int rmP = use_overlap_method == "Recent" ? 1 : 0 if obj.avg.size() > 1 if bull ? obj.btm.first() < obj.top.get(1) : obj.top.first() > obj.btm.get(1) obj.wM .remove(rmP) obj.cV .remove(rmP) obj.dir .remove(rmP) obj.top .remove(rmP) obj.avg .remove(rmP) obj.btm .remove(rmP) obj.left .remove(rmP) obj.blVP .remove(rmP) obj.brVP .remove(rmP) if barstate.isconfirmed for x = 0 to ob_num - 1 tg = switch ob_mitigation "Middle" => obj.avg "Absolute" => bull ? obj.btm : obj.top for in tg if (bull ? cC < pt : cC > pt) obj.wM .remove(idx) obj.cV .remove(idx) obj.dir .remove(idx) obj.top .remove(idx) obj.avg .remove(idx) obj.btm .remove(idx) obj.left .remove(idx) obj.blVP .remove(idx) obj.brVP .remove(idx) if barstate.islast if obj.avg.size() > 0 // Alert if bull ? ta.crossunder(low , obj.top.get(0)) : ta.crossover (high, obj.btm.get(0)) switch bull true => blalert.obtouch := true false => bralert.obtouch := true float tV = 0 obj.dV.clear() seq = math.min(ob_num - 1, obj.avg.size() - 1) for j = 0 to seq tV += obj.cV.get(j) if j == seq for y = 0 to seq obj.dV.unshift( math.floor( (obj.cV.get(y) / tV) * 100) ) obj.dV.reverse() for i = 0 to math.min(ob_num - 1, obj.avg.size() - 1) dmL = draw.mL .get(i) dOB = draw.ob .get(i) dblB = draw.blB.get(i) dbrB = draw.brB.get(i) deOB = draw.eOB.get(i) dOB.set_lefttop (obj.left .get(i) , obj.top.get(i)) deOB.set_lefttop (b.t , obj.top.get(i)) dOB.set_rightbottom (b.t , obj.btm.get(i)) deOB.set_rightbottom(b.t + (b.t - b.t ) * 100 , obj.btm.get(i)) if use_middle_line dmL.set_xy1(obj.left.get(i), obj.avg.get(i)) dmL.set_xy2(b.t , obj.avg.get(i)) if ob_metrics_show dblB.set_lefttop (obj.left.get(i), obj.top.get(i)) dbrB.set_lefttop (obj.left.get(i), obj.avg.get(i)) dblB.set_rightbottom(obj.left.get(i), obj.avg.get(i)) dbrB.set_rightbottom(obj.left.get(i), obj.btm.get(i)) rpBL = dblB.get_right() rpBR = dbrB.get_right() dbrB.set_right(rpBR + (b.t - b.t ) * obj.brVP.get(i)) dblB.set_right(rpBL + (b.t - b.t ) * obj.blVP.get(i)) if use_show_metric txt = switch obj.cV.get(i) >= 1000000000 => str.tostring(math.round(obj.cV.get(i) / 1000000000,3)) + "B" obj.cV.get(i) >= 1000000 => str.tostring(math.round(obj.cV.get(i) / 1000000,3)) + "M" obj.cV.get(i) >= 1000 => str.tostring(math.round(obj.cV.get(i) / 1000,3)) + "K" obj.cV.get(i) < 1000 => str.tostring(math.round(obj.cV.get(i))) deOB.set_text( str.tostring( txt + " (" + str.tostring(obj.dV.get(i)) + "%)") ) deOB.set_text_size (size.auto) deOB.set_text_halign(text.align_left) deOB.set_text_color (use_grayscale ? color.silver : color.new(css, 0)) if ob_metrics_show and barstate.isconfirmed if obj.wM.size() > 0 for i = 0 to obj.avg.size() - 1 switch obj.dir.get(i) 1 => switch obj.wM.get(i) 1 => obj.blVP.set(i, obj.blVP.get(i) + 1), obj.wM.set(i, 2) 2 => obj.blVP.set(i, obj.blVP.get(i) + 1), obj.wM.set(i, 3) 3 => obj.brVP.set(i, obj.brVP.get(i) + 1), obj.wM.set(i, 1) -1 => switch obj.wM.get(i) 1 => obj.brVP.set(i, obj.brVP.get(i) + 1), obj.wM.set(i, 2) 2 => obj.brVP.set(i, obj.brVP.get(i) + 1), obj.wM.set(i, 3) 3 => obj.blVP.set(i, obj.blVP.get(i) + 1), obj.wM.set(i, 1) var hN = array.new(1, b.n) var lN = array.new(1, b.n) var hS = array.new(1, b.n) var lS = array.new(1, b.n) if iH hN.pop() hN.unshift(int(b.n )) if iL lN.pop() lN.unshift(int(b.n )) if sH hS.pop() hS.unshift(int(b.n )) if sL lS.pop() lS.unshift(int(b.n )) if ob_show bull_ob.drawVOB(true , ob_bull_css, hN.first(), false) bear_ob.drawVOB(false, ob_bear_css, lN.first(), false) if ob_swings s_bull_ob.drawVOB(true , css_swing_up, hS.first(), true) s_bear_ob.drawVOB(false, css_swing_dn, lS.first(), true) if bull_ob blalert.ob := true if bear_ob bralert.ob := true if s_bull_ob blalert.swingob := true if s_bear_ob blalert.swingob := true //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - End } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{ - FVG | VI | OG } //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} //{----------------------------------------------------------------------------------------------------------------------------------------------} ghl() => request.security(syminfo.tickerid, fvg_tf, [high , low , close , open ]) tfG() => request.security(syminfo.tickerid, fvg_tf, ) cG(bool bull) => = ghl() = tfG() var FVG draw = FVG.new( array.new() , array.new() ) var FVG cords = array.new() float pup = na float pdn = na bool cdn = na int pos = 2 cc = timeframe.change(fvg_tf) if barstate.isfirst for i = 0 to fvg_num - 1 draw.box.unshift(box.new (na, na, na, na, border_color = color.new(color.white, 100), xloc = xloc.bar_time)) draw.ln.unshift (line.new(na, na, na, na, xloc = xloc.bar_time, width = 1, style = line.style_solid)) switch what_fvg "FVG" => pup := bull ? gl : l pdn := bull ? h : gh cdn := bull ? gl > h and cc : gh < l and cc pos := 2 "VI" => pup := bull ? (gc > go ? go : gc) : (gc > go ? go : gc ) pdn := bull ? (gc > go ? gc : go ) : (gc > go ? gc : go) cdn := bull ? go > gc and gh >
Indicador Pine Script®
por UldanayKulmurzayeva
1
Multi-Fibonacci Trend Average[FibonacciFlux]Multi-Fibonacci Trend Average (MFTA): An Institutional-Grade Trend Confluence Indicator for Discerning Market Participants My original indicator/Strategy: Engineered for the sophisticated demands of institutional and advanced traders, the Multi-Fibonacci Trend Average (MFTA) indicator represents a paradigm shift in technical analysis. This meticulously crafted tool is designed to furnish high-definition trend signals within the complexities of modern financial markets. Anchored in the rigorous principles of Fibonacci ratios and augmented by advanced averaging methodologies, MFTA delivers a granular perspective on trend dynamics. Its integration of Multi-Timeframe (MTF) filters provides unparalleled signal robustness, empowering strategic decision-making with a heightened degree of confidence. MFTA indicator on BTCUSDT 15min chart with 1min RSI and MACD filters enabled. Note the refined signal generation with reduced noise. MFTA indicator on BTCUSDT 15min chart without MTF filters. While capturing more potential trading opportunities, it also generates a higher frequency of signals, including potential false positives. Core Innovation: Proprietary Fibonacci-Enhanced Supertrend Averaging Engine The MFTA indicator’s core innovation lies in its proprietary implementation of Supertrend analysis, strategically fortified by Fibonacci ratios to construct a truly dynamic volatility envelope. Departing from conventional Supertrend methodologies, MFTA autonomously computes not one, but three distinct Supertrend lines. Each of these lines is uniquely parameterized by a specific Fibonacci factor: 0.618 (Weak), 1.618 (Medium/Golden Ratio), and 2.618 (Strong/Extended Fibonacci). // Fibonacci-based factors for multiple Supertrend calculations factor1 = input.float(0.618, 'Factor 1 (Weak/Fibonacci)', minval=0.01, step=0.01, tooltip='Factor 1 (Weak/Fibonacci)', group="Fibonacci Supertrend") factor2 = input.float(1.618, 'Factor 2 (Medium/Golden Ratio)', minval=0.01, step=0.01, tooltip='Factor 2 (Medium/Golden Ratio)', group="Fibonacci Supertrend") factor3 = input.float(2.618, 'Factor 3 (Strong/Extended Fib)', minval=0.01, step=0.01, tooltip='Factor 3 (Strong/Extended Fib)', group="Fibonacci Supertrend") This multi-faceted architecture adeptly captures a spectrum of market volatility sensitivities, ensuring a comprehensive assessment of prevailing conditions. Subsequently, the indicator algorithmically synthesizes these disparate Supertrend lines through arithmetic averaging. To achieve optimal signal fidelity and mitigate inherent market noise, this composite average is further refined utilizing an Exponential Moving Average (EMA). // Calculate average of the three supertends and a smoothed version superlength = input.int(21, 'Smoothing Length', tooltip='Smoothing Length for Average Supertrend', group="Fibonacci Supertrend") average_trend = (supertrend1 + supertrend2 + supertrend3) / 3 smoothed_trend = ta.ema(average_trend, superlength) The resultant ‘Smoothed Trend’ line emerges as a remarkably responsive yet stable trend demarcation, offering demonstrably superior clarity and precision compared to singular Supertrend implementations, particularly within the turbulent dynamics of high-volatility markets. Elevated Signal Confluence: Integrated Multi-Timeframe (MTF) Validation Suite MFTA transcends the limitations of conventional trend indicators by incorporating an advanced suite of three independent MTF filters: RSI, MACD, and Volume. These filters function as sophisticated validation protocols, rigorously ensuring that only signals exhibiting a confluence of high-probability factors are brought to the forefront. 1. Granular Lower Timeframe RSI Momentum Filter The Relative Strength Index (RSI) filter, computed from a user-defined lower timeframe, furnishes critical momentum-based signal validation. By meticulously monitoring RSI dynamics on an accelerated timeframe, traders gain the capacity to evaluate underlying momentum strength with precision, prior to committing to signal execution on the primary chart timeframe. // --- Lower Timeframe RSI Filter --- ltf_rsi_filter_enable = input.bool(false, title="Enable RSI Filter", group="MTF Filters", tooltip="Use RSI from lower timeframe as a filter") ltf_rsi_timeframe = input.timeframe("1", title="RSI Timeframe", group="MTF Filters", tooltip="Timeframe for RSI calculation") ltf_rsi_length = input.int(14, title="RSI Length", minval=1, group="MTF Filters", tooltip="Length for RSI calculation") ltf_rsi_threshold = input.int(30, title="RSI Threshold", minval=0, maxval=100, group="MTF Filters", tooltip="RSI value threshold for filtering signals") 2. Convergent Lower Timeframe MACD Trend-Momentum Filter The Moving Average Convergence Divergence (MACD) filter, also calculated on a lower timeframe basis, introduces a critical layer of trend-momentum convergence confirmation. The bullish signal configuration rigorously mandates that the MACD line be definitively positioned above the Signal line on the designated lower timeframe. This stringent condition ensures a robust indication of converging momentum that aligns synergistically with the prevailing trend identified on the primary timeframe. // --- Lower Timeframe MACD Filter --- ltf_macd_filter_enable = input.bool(false, title="Enable MACD Filter", group="MTF Filters", tooltip="Use MACD from lower timeframe as a filter") ltf_macd_timeframe = input.timeframe("1", title="MACD Timeframe", group="MTF Filters", tooltip="Timeframe for MACD calculation") ltf_macd_fast_length = input.int(12, title="MACD Fast Length", minval=1, group="MTF Filters", tooltip="Fast EMA length for MACD") ltf_macd_slow_length = input.int(26, title="MACD Slow Length", minval=1, group="MTF Filters", tooltip="Slow EMA length for MACD") ltf_macd_signal_length = input.int(9, title="MACD Signal Length", minval=1, group="MTF Filters", tooltip="Signal SMA length for MACD") 3. Definitive Volume Confirmation Filter The Volume Filter functions as an indispensable arbiter of trade conviction. By establishing a dynamic volume threshold, defined as a percentage relative to the average volume over a user-specified lookback period, traders can effectively ensure that all generated signals are rigorously validated by demonstrably increased trading activity. This pivotal validation step signifies robust market participation, substantially diminishing the potential for spurious or false breakout signals. // --- Volume Filter --- volume_filter_enable = input.bool(false, title="Enable Volume Filter", group="MTF Filters", tooltip="Use volume level as a filter") volume_threshold_percent = input.int(title="Volume Threshold (%)", defval=150, minval=100, group="MTF Filters", tooltip="Minimum volume percentage compared to average volume to allow signal (100% = average)") These meticulously engineered filters operate in synergistic confluence, requiring all enabled filters to definitively satisfy their pre-defined conditions before a Buy or Sell signal is generated. This stringent multi-layered validation process drastically minimizes the incidence of false positive signals, thereby significantly enhancing entry precision and overall signal reliability. Intuitive Visual Architecture & Actionable Intelligence MFTA provides a demonstrably intuitive and visually rich charting environment, meticulously delineating trend direction and momentum through precisely color-coded plots: Average Supertrend: Thin line, green/red for uptrend/downtrend, immediate directional bias. Smoothed Supertrend: Bold line, teal/purple for uptrend/downtrend, cleaner, institutionally robust trend. Dynamic Trend Fill: Green/red fill between Supertrends quantifies trend strength and momentum. Adaptive Background Coloring: Light green/red background mirrors Smoothed Supertrend direction, holistic trend perspective. Precision Buy/Sell Signals: ‘BUY’/‘SELL’ labels appear on chart when trend touch and MTF filter confluence are satisfied, facilitating high-conviction trade action. MFTA indicator applied to BTCUSDT 4-hour chart, showcasing its effectiveness on higher timeframes. The Smoothed Length parameter is increased to 200 for enhanced smoothness on this timeframe, coupled with 1min RSI and Volume filters for signal refinement. This illustrates the indicator's adaptability across different timeframes and market conditions. Strategic Applications for Institutional Mandates MFTA’s sophisticated design provides distinct advantages for advanced trading operations and institutional investment mandates. Key strategic applications include: High-Probability Trend Identification: Fibonacci-averaged Supertrend with MTF filters robustly identifies high-probability trend continuations and reversals, enhancing alpha generation. Precision Entry/Exit Signals: Volume and momentum-filtered signals enable institutional-grade precision for optimized risk-adjusted returns. Algorithmic Trading Integration: Clear signal logic facilitates seamless integration into automated trading systems for scalable strategy deployment. Multi-Asset/Timeframe Versatility: Adaptable parameters ensure applicability across diverse asset classes and timeframes, catering to varied trading mandates. Enhanced Risk Management: Superior signal fidelity from MTF filters inherently reduces false signals, supporting robust risk management protocols. Granular Customization and Parameterized Control MFTA offers unparalleled customization, empowering users to fine-tune parameters for precise alignment with specific trading styles and market conditions. Key adjustable parameters include: Fibonacci Factors: Adjust Supertrend sensitivity to volatility regimes. ATR Length: Control volatility responsiveness in Supertrend calculations. Smoothing Length: Refine Smoothed Trend line responsiveness and noise reduction. MTF Filter Parameters: Independently configure timeframes, lookback periods, and thresholds for RSI, MACD, and Volume filters for optimal signal filtering. Disclaimer MFTA is meticulously engineered for high-quality trend signals; however, no indicator guarantees profit. Market conditions are unpredictable, and trading involves substantial risk. Rigorous backtesting and forward testing across diverse datasets, alongside a comprehensive understanding of the indicator's logic, are essential before live deployment. Past performance is not indicative of future results. MFTA is for informational and analytical purposes only and is not financial or investment advice.
Indicador Pine Script®
por FibonacciFlux
4
cd_HTF_bias_CxOverview: No matter our trading style or model, to increase our success rate, we must move in the direction of the trend and align with the Higher Time Frame (HTF). Trading "gurus" call this the HTF bias. While we small fish tend to swim in all directions, the smart way is to flow with the big wave and the current. This indicator is designed to help us anticipate that major wave. ________________________________________ Details and Usage: This indicator observes HTF price action across preferably seven different pairs, following specific rules. It confirms potential directional moves using CISD levels on a Medium Time Frame (MTF). In short, it forecasts the likely direction (HTF bias). The user can then search for trade opportunities aligned with this bias on a Lower Time Frame (LTF), using their preferred pair, entry model, and style. ________________________________________ Timeframe Alignment: The commonly accepted LTF/MTF/HTF combinations include: • 1m – 15m – H4 • 3m – H1 – Daily / 3m – 30m – Daily • 5m – H1 – Daily • 15m – H4 – Weekly • H1 – Daily – Monthly • H4 – Weekly – Quarterly Example: If you're trading with a 3m model on a 30m/3m setup, you should seek trades in the direction of the H1/Daily bias. ________________________________________ How It Works: The indicator first looks for sweeps on the selected HTF — when any of the last four candles are swept, the first condition is met. The second step is confirmation with a CISD close on the MTF — once a candle closes above/below the CISD level, the second condition is fulfilled. This suggests the price has made its directional decision. Example: If a previous HTF candle is swept and we receive a bearish CISD confirmation on H1, the HTF bias becomes bearish. After this, you may switch to a more granular setup like HTF: 30m and MTF: 3m to look for trade entries aligned with the bias (e.g., 30m sweep + 3m CISD). ________________________________________ How Is Bias Determined? • HTF Sweep + MTF CISD = SC (Sweep & CISD) • Latest Bullish SC → Bias: Bullish • Latest Bearish SC → Bias: Bearish • Price closes above the last Bearish SC → Bias: Strong Bullish • Price closes below the last Bullish SC → Bias: Strong Bearish • Strong Bullish bias + Bearish CISD (without HTF sweep) → Bias: Bullish • Strong Bearish bias + Bullish CISD (without HTF sweep) → Bias: Bearish • Bearish price violates SC high, but Bullish SC is untouched → Bias: Bullish • Bullish price violates SC low, but Bearish SC is untouched → Bias: Bearish • If neither side generates SC → Bias: No Bias The logic is built on the idea that a price overcoming resistance is stronger, and encountering resistance is weaker. This model is based on the well-known “Daily Bias” structure, but with personal refinements. ________________________________________ What’s on the Screen? • Classic HTF zones (boxes) • Potential MTF CISD levels • Confirmed MTF lines • Sweep zones when HTF sweeps occur • Result table showing current bias status ________________________________________ Usage: • Select HTF and MTF timeframes aligned with your trading timeframe. • Adjust color and position settings as needed. • Enter up to seven pairs to track via the menu. • Use the checkbox next to each pair to enable/disable them. • If “Ignore these assets” is checked, all pairs will be disabled, and only the currently open chart pair will be tracked. ________________________________________ Alerts: You can choose alerts for Bullish, Bearish, Strong Bullish, or Strong Bearish conditions. There are two types of alert sources: 1. From the indicator’s internal list 2. From TradingView’s watchlist Visual example: ________________________________________ How I Use It: • For spot trades, I use HTF: Weekly and MTF: H4 and look for Bullish or Strong Bullish pairs. • For scalping, I follow bias from HTF: Daily and MTF: H1. Example: If the indicator shows a Bearish HTF Bias, I switch to HTF: 30m and MTF: 3m and enter trades once bearish conditions are met (timeframe alignment). ________________________________________ Important Notes: • The indicator defines CISD levels only at HTF high and low levels. • If your chart is on a higher timeframe than your selected HTF/MTF, no data will appear. Example: If HTF = H1 and MTF = 5m, opening a chart on H4 will result in a blank screen. • The drawn CISD level on screen is the MTF CISD level. • Not every alert should be traded. Always confirm with personal experience and visual validation. • Receiving multiple Strong Bullish/Bearish alerts is intentional. (Trick 😊) • Please share your feedback and suggestions! ________________________________________ And Most Importantly: Don't leave street animals without water and food! Happy trading!
Indicador Pine Script®
por cdikici71
17
EvoTrend-X Indicator — Evolutionary Trend Learner ExperimentalEvoTrend-X Indicator — Evolutionary Trend Learner NOTE: This is an experimental Pine Script v6 port of a Python prototype. Pine wasn’t the original research language, so there may be small quirks—your feedback and bug reports are very welcome. The model is non-repainting, MTF-safe (lookahead_off + gaps_on), and features an adaptive (fitness-based) candidate selector, confidence gating, and a volatility filter. ⸻ What it is EvoTrend-X is adaptive trend indicator that learns which moving-average length best fits the current market. It maintains a small “population” of fast EMA candidates, rewards those that align with price momentum, and continuously selects the best performer. Signals are gated by a multi-factor Confidence score (fitness, strength vs. ATR, MTF agreement) and a volatility filter (ATR%). You get a clean Fast/Slow pair (for the currently best candidate), optional HTF filter, a fitness ribbon for transparency, and a themed info panel with a one-glance STATUS readout. Core outputs • Selected Fast/Slow EMAs (auto-chosen from candidates via fitness learning) • Spread cross (Fast – Slow) → visual BUY/SELL markers + alert hooks • Confidence % (0–100): Fitness ⊕ Distance vs. ATR ⊕ MTF agreement • Gates: Trend regime (Kaufman ER), Volatility (ATR%), MTF filter (optional) • Candidate Fitness Ribbon: shows which lengths the learner currently prefers • Export plot: hidden series “EvoTrend-X Export (spread)” for downstream use ⸻ Why it’s different • Evolutionary learning (on-chart): Each candidate EMA length gets rewarded if its slope matches price change and penalized otherwise, with a gentle decay so the model forgets stale regimes. The best fitness wins the right to define the displayed Fast/Slow pair. • Confidence gate: Signals don’t light up unless multiple conditions concur: learned fitness, spread strength vs. volatility, and (optionally) higher-timeframe trend. • Volatility awareness: ATR% filter blocks low-energy environments that cause death-by-a-thousand-whipsaws. Your “why no signal?” answer is always visible in the STATUS. • Preset discipline, Custom freedom: Presets set reasonable baselines for FX, equities, and crypto; Custom exposes all knobs and honors your inputs one-to-one. • Non-repainting rigor: All MTF calls use lookahead_off + gaps_on. Decisions use confirmed bars. No forward refs. No conditional ta.* pitfalls. ⸻ Presets (and what they do) • FX 1H (Conservative): Medium candidates, slightly higher MinConf, modest ATR% floor. Good for macro sessions and cleaner swings. • FX 15m (Active): Shorter candidates, looser MinConf, higher ATR% floor. Designed for intraday velocity and decisive sessions. • Equities 1D: Longer candidates, gentler volatility floor. Suits index/large-cap trend waves. • Crypto 1H: Mid-short candidates, higher ATR% floor for 24/7 chop, stronger MinConf to avoid noise. • Custom: Your inputs are used directly (no override). Ideal for systematic tuning or bespoke assets. ⸻ How the learning works (at a glance) 1. Candidates: A small set of fast EMA lengths (e.g., 8/12/16/20/26/34). Slow = Fast × multiplier (default ×2.0). 2. Reward/decay: If price change and the candidate’s Fast slope agree (both up or both down), its fitness increases; otherwise decreases. A decay constant slowly forgets the distant past. 3. Selection: The candidate with highest fitness defines the displayed Fast/Slow pair. 4. Signal engine: Crosses of the spread (Fast − Slow) across zero mark potential regime shifts. A Confidence score and gates decide whether to surface them. ⸻ Controls & what they mean Learning / Regime • Slow length = Fast ×: scales the Slow EMA relative to each Fast candidate. Larger multiplier = smoother regime detection, fewer whipsaws. • ER length / threshold: Kaufman Efficiency Ratio; above threshold = “Trending” background. • Learning step, Decay: Larger step reacts faster to new behavior; decay sets how quickly the past is forgotten. Confidence / Volatility gate • Min Confidence (%): Minimum score to show signals (and fire alerts). Raising it filters noise; lowering it increases frequency. • ATR length: The ATR window for both the ATR% filter and strength normalization. Shorter = faster, but choppier. • Min ATR% (percent): ATR as a percentage of price. If ATR% < Min ATR% → status shows BLOCK: low vola. MTF Trend Filter • Use HTF filter / Timeframe / Fast & Slow: HTF Fast>Slow for longs, Fast threshold; exit when spread flips or Confidence decays below your comfort zone. 2) FX index/majors, 15m (active intraday) • Preset: FX 15m (Active). • Gate: MinConf 60–70; Min ATR% 0.15–0.30. • Flow: Focus on session opens (LDN/NY). The ribbon should heat up on shorter candidates before valid crosses appear—good early warning. 3) SPY / Index futures, 1D (positioning) • Preset: Equities 1D. • Gate: MinConf 55–65; Min ATR% 0.05–0.12. • Flow: Use spread crosses as regime flags; add timing from price structure. For adds, wait for ER to remain trending across several bars. 4) BTCUSD, 1H (24/7) • Preset: Crypto 1H. • Gate: MinConf 70–80; Min ATR% 0.20–0.35. • Flow: Crypto chops—volatility filter is your friend. When ribbon and HTF OK agree, favor continuation entries; otherwise stand down. ⸻ Reading the Info Panel (and fixing “no signals”) The panel is your self-diagnostic: • HTF OK? False means the higher-timeframe EMAs disagree with your intended side. • Regime: If “Chop”, ER < threshold. Consider raising the threshold or waiting. • Confidence: Heat-colored; if below MinConf, the gate blocks signals. • ATR% vs. Min ATR%: If ATR% < Min ATR%, status shows BLOCK: low vola. • STATUS (composite): • BLOCK: low vola → increase Min ATR% down (i.e., allow lower vol) or wait for expansion. • BLOCK: HTF filter → disable HTF or align with the HTF tide. • BLOCK: confidence → lower MinConf slightly or wait for stronger alignment. • OK → you’ll see markers on valid crosses. ⸻ Alerts Two static alert hooks: • BUY cross — spread crosses up and all gates (ER, Vol, MTF, Confidence) are open. • SELL cross — mirror of the above. Create them once from “Add Alert” → choose the condition by name. ⸻ Exporting to other scripts In your other Pine indicators/strategies, add an input.source and select EvoTrend-X → “EvoTrend-X Export (spread)”. Common uses: • Build a rule: only trade when exported spread > 0 (trend filter). • Combine with your oscillator: oscillator oversold and spread > 0 → buy bias. ⸻ Best practices • Let it learn: Keep Learning step moderate (0.4–0.6) and Decay close to 1.0 (e.g., 0.99–0.997) for smooth regime memory. • Respect volatility: Tune Min ATR% by asset and timeframe. FX 1H ≈ 0.10–0.20; crypto 1H ≈ 0.20–0.35; equities 1D ≈ 0.05–0.12. • MTF discipline: HTF filter removes lots of “almost” trades. If you prefer aggressive entries, turn it off and rely more on Confidence. • Confidence as throttle: • 40–60%: exploratory; expect more signals. • 60–75%: balanced; good daily driver. • 75–90%: selective; catch the clean stuff. • 90–100%: only A-setups; patient mode. • Watch the ribbon: When shorter candidates heat up before a cross, momentum is forming. If long candidates dominate, you’re in a slower trend cycle. ⸻ Non-repainting & safety notes • All request.security() calls use lookahead=barmerge.lookahead_off, gaps=barmerge.gaps_on. • No forward references; decisions rely on confirmed bar data. • EMA lengths are simple ints (no series-length errors). • Confidence components are computed every bar (no conditional ta.* traps). ⸻ Limitations & tips • Chop happens: ER helps, but sideways microstructure can still flicker—use Confidence + Vol filter as brakes. • Presets ≠ oracle: They’re sensible baselines; always tune MinConf and Min ATR% to your venue and session. • Theme “Auto”: Pine cannot read chart theme; “Auto” defaults to a Dark-friendly palette. ⸻ Publisher’s Screenshots Checklist 1) FX swing — EURUSD 1H • Preset: FX 1H (Conservative) • Params: MinConf=70, ATR Len=14, Min ATR%=0.12, MTF ON (TF=4H, 20/50) • Show: Clear BUY cross, STATUS=OK, green regime background; Fitness Ribbon visible. 2) FX intraday — GBPUSD 15m • Preset: FX 15m (Active) • Params: MinConf=60, ATR Len=14, Min ATR%=0.20, MTF ON (TF=60m) • Show: SELL cross near London session open. HTF lines enabled (translucent). • Caption: “GBPUSD 15m • Active session sell with MTF alignment.” 3) Indices — SPY 1D • Preset: Equities 1D • Params: MinConf=60, ATR Len=14, Min ATR%=0.08, MTF ON (TF=1W, 20/50) • Show: Longer trend run after BUY cross; regime shading shows persistence. • Caption: “SPY 1D • Trend run after BUY cross; weekly filter aligned.” 4) Crypto — BINANCE:BTCUSDT 1H • Preset: Crypto 1H • Params: MinConf=75, ATR Len=14, Min ATR%=0.25, MTF ON (TF=4H) • Show: BUY cross + quick follow-through; Ribbon warming (reds/yellows → greens). • Caption: “BTCUSDT 1H • Momentum break with high confidence and ribbon turning.”
Indicador Pine Script®
por ACTradeFIN
ATR%指標概要 / Overview ATR Percentage (MTF)：把 ATR 轉為百分比（ATR%）或保留為絕對值，並在該「波動序列」上套用布林帶。支援多週期（MTF）計算：例如在 5 分圖顯示 4H / D1 的 ATR%。內建白色點狀水平線作為固定門檻（預設 1%）。 ATR Percentage (MTF): Converts ATR to a percentage of price (ATR%) or keeps it as absolute ATR, then applies Bollinger Bands on this volatility series. Supports multi-timeframe (MTF) calculation (e.g., show 4H/D1 ATR% on a 5-min chart). Includes a configurable white dotted horizontal threshold line (default 1%). ⸻ 設計目的 / Purpose • 以 ATR% 衡量相對波動，利於跨品種比較。 Use ATR% for relative volatility to compare across markets. • 以 布林帶 標示「高/低波動區」，觀察擴張與壓縮。 Use Bollinger Bands on volatility to highlight expansion/squeeze. • 提供 固定閾值（1%） 作為策略濾網或告警門檻。 Provide a fixed threshold (1%) for filters/alerts. • 以 MTF 方式，讓低週期策略用高週期波動做濾網。 MTF lets lower-TF strategies filter by higher-TF volatility. ⸻ 參數說明 / Inputs • Use ATR as % of Close：切換 ATR（絕對值）/ ATR%（建議）。 Toggle between absolute ATR and ATR% (recommended). • ATR Periods：ATR 計算長度（預設 22）。 ATR lookback (default 22). • Show Bollinger Bands / BB Periods / StdDev：布林帶開關、長度與倍數（預設 20 / 2）。 Bollinger Bands on/off, length, and deviation (default 20 / 2). • Source Timeframe：計算用週期（如 60、240、D、W；留空/Chart ＝ 跟隨圖表）。 Timeframe used for calculations (e.g., 60, 240, D, W; empty/“Chart” = current). • Threshold Line (%)：白色點線門檻，預設 1.0（即 1%）。 White dotted threshold line, default 1.0 (1%). 提醒：當 非 ATR% 模式時，Threshold 值代表「價格單位」而非百分比。 Note: In non-ATR% mode, the threshold is in price units, not percent. ⸻ 訊號解讀 / How to Read • ATR% > 上軌：波動顯著擴張（趨勢啟動或加速常見）。 ATR% above upper band: significant expansion; often trend ignition/acceleration. • ATR% < 下軌：波動明顯壓縮（常見於突破前）。 ATR% below lower band: volatility squeeze; often precedes breakouts. • ATR% 穿越 Threshold（1%）：達到固定波動標準，可作策略開關或風控分水嶺。 ATR% crossing the 1% threshold: fixed volatility bar for filters/risk gates. ⸻ 內建告警 / Built-in Alerts • Volatility Breakout (MTF)：ATR/ATR% 向上穿越上軌。 Triggers when ATR/ATR% crosses above the upper band. • Volatility Squeeze (MTF)：ATR/ATR% 向下穿越下軌。 Triggers when ATR/ATR% crosses below the lower band. ⸻ 使用建議 / Suggested Uses • 當沖濾網：於 1–5 分圖選擇 4H / D1 作為 Source Timeframe；僅在 ATR% > 1% 且位於中線以上時允許趨勢進場。 Intraday filter: on 1–5m charts, set 4H/D1 as source TF; allow trend entries only when ATR% > 1% and above the midline. • 突破前偵測：ATR% 長時間貼近下軌 → 留意可能的波動擴張。 Pre-breakout scan: prolonged ATR% near lower band can foreshadow expansion. • 跨品種比較：用 ATR% 統一指數、外匯、商品的波動刻度。 Cross-asset comparison: ATR% normalizes volatility across indices/FX/commodities. ⸻ 已知限制 / Notes • MTF 對齊：使用 request.security() 對映高週期資料到當前圖表；在歷史回補與即時邊界棒可能略有差異。 MTF alignment: request.security() maps higher-TF data; boundary bars may differ slightly between historical and realtime. • 百分比分母：ATR% 的分母為同一週期的 close；若需更平滑可改 ATR / SMA(close, N) × 100。 Denominator: ATR% uses same-TF close; for smoother values consider ATR / SMA(close, N) × 100. • 風險聲明：僅供研究/教育用途，非投資建議，請自行控管風險。 Disclaimer: For research/education only. Not investment advice. ⸻ 版本與更新 / Version & Updates • v1.0：ATR/ATR% + BB（MTF）、1% 白色點線、兩組告警。 v1.0: ATR/ATR% + BB (MTF), 1% white dotted line, two alert conditions.
Indicador Pine Script®
por ShawE
`security()` revisited [PineCoders]NOTE The non-repainting technique in this publication that relies on bar states is now deprecated, as we have identified inconsistencies that undermine its credibility as a universal solution. The outputs that use the technique are still available for reference in this publication. However, we do not endorse its usage. See this publication for more information about the current best practices for requesting HTF data and why they work. █  OVERVIEW This script presents a new function to help coders use security() in both repainting and non-repainting modes. We revisit this often misunderstood and misused function, and explain its behavior in different contexts, in the hope of dispelling some of the coder lure surrounding it. The function is incredibly powerful, yet misused, it can become a dangerous WMD and an instrument of deception, for both coders and traders. We will discuss:  • How to use our new `f_security()` function.  • The behavior of Pine code and security() on the three very different types of bars that make up any chart.  • Why what you see on a chart is a simulation, and should be taken with a grain of salt.  • Why we are presenting a new version of a function handling security() calls.  • Other topics of interest to coders using higher timeframe (HTF) data. █  WARNING We have tried to deliver a function that is simple to use and will, in non-repainting mode, produce reliable results for both experienced and novice coders. If you are a novice coder, stick to our recommendations to avoid getting into trouble, and DO NOT change our `f_security()` function when using it. Use `false` as the function's last argument and refrain from using your script at smaller timeframes than the chart's. To call our function to fetch a non-repainting value of close from the 1D timeframe, use: f_security(_sym, _res, _src, _rep) => security(_sym, _res, _src ) previousDayClose = f_security(syminfo.tickerid, "D", close, false) If that's all you're interested in, you are done. If you choose to ignore our recommendation and use the function in repainting mode by changing the `false` in there for `true`, we sincerely hope you read the rest of our ramblings before you do so, to understand the consequences of your choice. Let's now have a look at what security() is showing you. There is a lot to cover, so buckle up! But before we dig in, one last thing. What is a chart? A chart is a graphic representation of events that occur in markets. As any representation, it is not reality, but rather a model of reality. As Scott Page eloquently states in The Model Thinker : "All models are wrong; many are useful". Having in mind that both chart bars and plots on our charts are imperfect and incomplete renderings of what actually occurred in realtime markets puts us coders in a place from where we can better understand the nature of, and the causes underlying the inevitable compromises necessary to build the data series our code uses, and print chart bars. Traders or coders complaining that charts do not reflect reality act like someone who would complain that the word "dog" is not a real dog. Let's recognize that we are dealing with models here, and try to understand them the best we can. Sure, models can be improved; TradingView is constantly improving the quality of the information displayed on charts, but charts nevertheless remain mere translations. Plots of data fetched through security() being modelized renderings of what occurs at higher timeframes, coders will build more useful and reliable tools for both themselves and traders if they endeavor to perfect their understanding of the abstractions they are working with. We hope this publication helps you in this pursuit. █  FEATURES This script's "Inputs" tab has four settings:  • Repaint : Determines whether the functions will use their repainting or non-repainting mode.   Note that the setting will not affect the behavior of the yellow plot, as it always repaints.  • Source : The source fetched by the security() calls.  • Timeframe : The timeframe used for the security() calls. If it is lower than the chart's timeframe, a warning appears.  • Show timeframe reminder : Displays a reminder of the timeframe after the last bar. █  THE CHART The chart shows two different pieces of information and we want to discuss other topics in this section, so we will be covering:  A — The type of chart bars we are looking at, indicated by the colored band at the top.  B — The plots resulting of calling security() with the close price in different ways.  C — Points of interest on the chart. A — Chart bars The colored band at the top shows the three types of bars that any chart on a live market will print. It is critical for coders to understand the important distinctions between each type of bar:  1 — Gray : Historical bars, which are bars that were already closed when the script was run on them.  2 — Red : Elapsed realtime bars, i.e., realtime bars that have run their course and closed.    The state of script calculations showing on those bars is that of the last time they were made, when the realtime bar closed.  3 — Green : The realtime bar. Only the rightmost bar on the chart can be the realtime bar at any given time, and only when the chart's market is active. Refer to the Pine User Manual's Execution model page for a more detailed explanation of these types of bars. B — Plots The chart shows the result of letting our 5sec chart run for a few minutes with the following settings: "Repaint" = "On" (the default is "Off"), "Source" = `close` and "Timeframe" = 1min. The five lines plotted are the following. They have progressively thinner widths:  1 — Yellow : A normal, repainting security() call.  2 — Silver : Our recommended security() function.  3 — Fuchsia : Our recommended way of achieving the same result as our security() function, for cases when the source used is a function returning a tuple.  4 — White : The method we previously recommended in our MTF Selection Framework , which uses two distinct security() calls.  5 — Black : A lame attempt at fooling traders that MUST be avoided. All lines except the first one in yellow will vary depending on the "Repaint" setting in the script's inputs. The first plot does not change because, contrary to all other plots, it contains no conditional code to adapt to repainting/no-repainting modes; it is a simple security() call showing its default behavior. C — Points of interest on the chart Historical bars do not show actual repainting behavior To appreciate what a repainting security()  call will plot in realtime, one must look at the realtime bar and at elapsed realtime bars, the bars where the top line is green or red on the chart at the top of this page. There you can see how the plots go up and down, following the close value of each successive chart bar making up a single bar of the higher timeframe. You would see the same behavior in "Replay" mode. In the realtime bar, the movement of repainting plots will vary with the source you are fetching: open will not move after a new timeframe opens, low and high will change when a new low or high are found, close will follow the last feed update. If you are fetching a value calculated by a function, it may also change on each update. Now notice how different the plots are on historical bars. There, the plot shows the close of the previously completed timeframe for the whole duration of the current timeframe, until on its last bar the price updates to the current timeframe's close when it is confirmed (if the timeframe's last bar is missing, the plot will only update on the next timeframe's first bar). That last bar is the only one showing where the plot would end if that timeframe's bars had elapsed in realtime. If one doesn't understand this, one cannot properly visualize how his script will calculate in realtime when using repainting. Additionally, as published scripts typically show charts where the script has only run on historical bars, they are, in fact, misleading traders who will naturally assume the script will behave the same way on realtime bars. Non-repainting plots are more accurate on historical bars Now consider this chart, where we are using the same settings as on the chart used to publish this script, except that we have turned "Repainting" off this time: The yellow line here is our reference, repainting line, so although repainting is turned off, it is still repainting, as expected. Because repainting is now off, however, plots on historical bars show the previous timeframe's close until the first bar of a new timeframe, at which point the plot updates. This correctly reflects the behavior of the script in the realtime bar, where because we are offsetting the series by one, we are always showing the previously calculated—and thus confirmed—higher timeframe value. This means that in realtime, we will only get the previous timeframe's values one bar after the timeframe's last bar has elapsed, at the open of the first bar of a new timeframe. Historical and elapsed realtime bars will not actually show this nuance because they reflect the state of calculations made on their close , but we can see the plot update on that bar nonetheless. ► This more accurate representation on historical bars of what will happen in the realtime bar is one of the two key reasons why using non-repainting data is preferable.    The other is that in realtime, your script will be using more reliable data and behave more consistently. Misleading plots Valiant attempts by coders to show non-repainting, higher timeframe data updating earlier than on our chart are futile. If updates occur one bar earlier because coders use the repainting version of the function, then so be it, but they must then also accept that their historical bars are not displaying information that is as accurate. Not informing script users of this is to mislead them. Coders should also be aware that if they choose to use repainting data in realtime, they are sacrificing reliability to speed and may be running a strategy that behaves very differently from the one they backtested, thus invalidating their tests. When, however, coders make what are supposed to be non-repainting plots plot artificially early on historical bars, as in examples "c4" and "c5" of our script, they would want us to believe they have achieved the miracle of time travel. Our understanding of the current state of science dictates that for now, this is impossible. Using such techniques in scripts is plainly misleading, and public scripts using them will be moderated. We are coding trading tools here—not video games. Elementary ethics prescribe that we should not mislead traders, even if it means not being able to show sexy plots. As the great Feynman said: You should not fool the layman when you're talking as a scientist. You can readily appreciate the fantasy plot of "c4", the thinnest line in black, by comparing its supposedly non-repainting behavior between historical bars and realtime bars. After updating—by miracle—as early as the wide yellow line that is repainting, it suddenly moves in a more realistic place when the script is running in realtime, in synch with our non-repainting lines. The "c5" version does not plot on the chart, but it displays in the Data Window. It is even worse than "c4" in that it also updates magically early on historical bars, but goes on to evaluate like the repainting yellow line in realtime, except one bar late. Data Window The Data Window shows the values of the chart's plots, then the values of both the inside and outside offsets used in our calculations, so you can see them change bar by bar. Notice their differences between historical and elapsed realtime bars, and the realtime bar itself. If you do not know about the Data Window, have a look at this essential tool for Pine coders in the Pine User Manual's page on Debugging . The conditional expressions used to calculate the offsets may seem tortuous but their objective is quite simple. When repainting is on, we use this form, so with no offset on all bars: security(ticker, i_timeframe, i_source ) // which is equivalent to: security(ticker, i_timeframe, i_source) When repainting is off, we use two different and inverted offsets on historical bars and the realtime bar: // Historical bars: security(ticker, i_timeframe, i_source ) // Realtime bar (and thus, elapsed realtime bars): security(ticker, i_timeframe, i_source ) The offsets in the first line show how we prevent repainting on historical bars without the need for the `lookahead` parameter. We use the value of the function call on the chart's previous bar. Since values between the repainting and non-repainting versions only differ on the timeframe's last bar, we can use the previous value so that the update only occurs on the timeframe's first bar, as it will in realtime when not repainting. In the realtime bar, we use the second call, where the offsets are inverted. This is because if we used the first call in realtime, we would be fetching the value of the repainting function on the previous bar, so the close of the last bar. What we want, instead, is the data from the previous, higher timeframe bar , which has elapsed and is confirmed, and thus will not change throughout realtime bars, except on the first constituent chart bar belonging to a new higher timeframe. After the offsets, the Data Window shows values for the `barstate.*` variables we use in our calculations. █  NOTES Why are we revisiting security()  ? For four reasons:  1 — We were seeing coders misuse our `f_secureSecurity()` function presented in How to avoid repainting when using security() .    Some novice coders were modifying the offset used with the history-referencing operator in the function, making it zero instead of one,    which to our horror, caused look-ahead bias when used with `lookahead = barmerge.lookahead_on`.    We wanted to present a safer function which avoids introducing the dreaded "lookahead" in the scripts of unsuspecting coders.  2 — The popularity of security() in screener-type scripts where coders need to use the full 40 calls allowed per script made us want to propose    a solid method of allowing coders to offer a repainting/no-repainting choice to their script users with only one security() call.  3 — We wanted to explain why some alternatives we see circulating are inadequate and produce misleading behavior.  4 — Our previous publication on security() focused on how to avoid repainting, yet many other considerations worthy of attention are not related to repainting. Handling tuples When sending function calls that return tuples with security() , our `f_security()` function will not work because Pine does not allow us to use the history-referencing operator with tuple return values. The solution is to integrate the inside offset to your function's arguments, use it to offset the results the function is returning, and then add the outside offset in a reassignment of the tuple variables, after security() returns its values to the script, as we do in our "c2" example. Does it repaint? We're pretty sure Wilder was not asked very often if RSI repainted. Why? Because it wasn't in fashion—and largely unnecessary—to ask that sort of question in the 80's. Many traders back then used daily charts only, and indicator values were calculated at the day's close, so everybody knew what they were getting. Additionally, indicator values were calculated by generally reputable outfits or traders themselves, so data was pretty reliable. Today, almost anybody can write a simple indicator, and the programming languages used to write them are complex enough for some coders lacking the caution, know-how or ethics of the best professional coders, to get in over their heads and produce code that does not work the way they think it does. As we hope to have clearly demonstrated, traders do have legitimate cause to ask if MTF scripts repaint or not when authors do not specify it in their script's description. ► We recommend that authors always use our `f_security()` with `false` as the last argument to avoid repainting when fetching data dependent on OHLCV information. This is the only way to obtain reliable HTF data. If you want to offer users a choice, make non-repainting mode the default, so that if users choose repainting, it will be their responsibility. Non-repainting security() calls are also the only way for scripts to show historical behavior that matches the script's realtime behavior, so you are not misleading traders. Additionally, non-repainting HTF data is the only way that non-repainting alerts can be configured on MTF scripts, as users of MTF scripts cannot prevent their alerts from repainting by simply configuring them to trigger on the bar's close. Data feeds A chart at one timeframe is made up of multiple feeds that mesh seamlessly to form one chart. Historical bars can use one feed, and the realtime bar another, which brokers/exchanges can sometimes update retroactively so that elapsed realtime bars will reappear with very slight modifications when the browser's tab is refreshed. Intraday and daily chart prices also very often originate from different feeds supplied by brokers/exchanges. That is why security() calls at higher timeframes may be using a completely different feed than the chart, and explains why the daily high value, for example, can vary between timeframes. Volume information can also vary considerably between intraday and daily feeds in markets like stocks, because more volume information becomes available at the end of day. It is thus expected behavior—and not a bug—to see data variations between timeframes. Another point to keep in mind concerning feeds it that when you are using a repainting security() plot in realtime, you will sometimes see discrepancies between its plot and the realtime bars. An artefact revealing these inconsistencies can be seen when security() plots sometimes skip a realtime chart bar during periods of high market activity. This occurs because of races between the chart and the security() feeds, which are being monitored by independent, concurrent processes. A blue arrow on the chart indicates such an occurrence. This is another cause of repainting, where realtime bar-building logic can produce different outcomes on one closing price. It is also another argument supporting our recommendation to use non-repainting data. Alternatives There is an alternative to using security() in some conditions. If all you need are OHLC prices of a higher timeframe, you can use a technique like the one Duyck demonstrates in his security free MTF example - JD script. It has the great advantage of displaying actual repainting values on historical bars, which mimic the code's behavior in the realtime bar—or at least on elapsed realtime bars, contrary to a repainting security() plot. It has the disadvantage of using the current chart's TF data feed prices, whereas higher timeframe data feeds may contain different and more reliable prices when they are compiled at the end of the day. In its current state, it also does not allow for a repainting/no-repainting choice. When `lookahead` is useful When retrieving non-price data, or in special cases, for experiments, it can be useful to use `lookahead`. One example is our Backtesting on Non-Standard Charts: Caution! script where we are fetching prices of standard chart bars from non-standard charts. Warning users Normal use of security() dictates that it only be used at timeframes equal to or higher than the chart's. To prevent users from inadvertently using your script in contexts where it will not produce expected behavior, it is good practice to warn them when their chart is on a higher timeframe than the one in the script's "Timeframe" field. Our `f_tfReminderAndErrorCheck()` function in this script does that. It can also print a reminder of the higher timeframe. It uses one security() call. Intrabar timeframes security() is not supported by TradingView when used with timeframes lower than the chart's. While it is still possible to use security() at intrabar timeframes, it then behaves differently. If no care is taken to send a function specifically written to handle the successive intrabars, security() will return the value of the last intrabar in the chart's timeframe, so the last 1H bar in the current 1D bar, if called at "60" from a "D" chart timeframe. If you are an advanced coder, see our FAQ entry on the techniques involved in processing intrabar timeframes. Using intrabar timeframes comes with important limitations, which you must understand and explain to traders if you choose to make scripts using the technique available to others. Special care should also be taken to thoroughly test this type of script. Novice coders should refrain from getting involved in this. █  TERMINOLOGY Timeframe Timeframe , interval and resolution are all being used to name the concept of timeframe. We have, in the past, used "timeframe" and "resolution" more or less interchangeably. Recently, members from the Pine and PineCoders team have decided to settle on "timeframe", so from hereon we will be sticking to that term. Multi-timeframe (MTF) Some coders use "multi-timeframe" or "MTF" to name what are in fact "multi-period" calculations, as when they use MAs of progressively longer periods. We consider that a misleading use of "multi-timeframe", which should be reserved for code using calculations actually made from another timeframe's context and using security() , safe for scripts like Duyck's one mentioned earlier, or TradingView's Relative  Volume  at  Time , which use a user-selected timeframe as an anchor to reset calculations. Calculations made at the chart's timeframe by varying the period of MAs or other rolling window calculations should be called "multi-period", and "MTF-anchored" could be used for scripts that reset calculations on timeframe boundaries. Colophon Our script was written using the PineCoders Coding Conventions for Pine . The description was formatted using the techniques explained in the How We Write and Format Script Descriptions PineCoders publication. Snippets were lifted from our MTF Selection Framework , then massaged to create the `f_tfReminderAndErrorCheck()` function. █  THANKS Thanks to apozdnyakov for his help with the innards of security() . Thanks to bmistiaen for proofreading our description. Look first. Then leap.
Indicador Pine Script®
por PineCoders
61
FvgPanel█ OVERVIEW This library provides functionalities for creating and managing a display panel within a Pine Script™ indicator. Its primary purpose is to offer a structured way to present Fair Value Gap (FVG) information, specifically the nearest bullish and bearish FVG levels across different timeframes (Current, MTF, HTF), directly on the chart. The library handles the table's structure, header initialization, and dynamic cell content updates. █ CONCEPTS The core of this library revolves around presenting summarized FVG data in a clear, tabular format. Key concepts include: FVG Data Aggregation and Display The panel is designed to show at-a-glance information about the closest active FVG mitigation levels. It doesn't calculate these FVGs itself but relies on the main script to provide this data. The panel is structured with columns for timeframes (TF), Bullish FVGs, and Bearish FVGs, and rows for "Current" (LTF), "MTF" (Medium Timeframe), and "HTF" (High Timeframe). The `panelData` User-Defined Type (UDT) To facilitate the transfer of information to be displayed, the library defines a UDT named `panelData`. This structure is central to the library's operation and is designed to hold all necessary values for populating the panel's data cells for each relevant FVG. Its fields include: Price levels for the nearest bullish and bearish FVGs for LTF, MTF, and HTF (e.g., `nearestBullMitLvl`, `nearestMtfBearMitLvl`). Boolean flags to indicate if these FVGs are classified as "Large Volume" (LV) (e.g., `isNearestBullLV`, `isNearestMtfBearLV`). Color information for the background and text of each data cell, allowing for conditional styling based on the FVG's status or proximity (e.g., `ltfBullBgColor`, `mtfBearTextColor`). The design of `panelData` allows the main script to prepare all display-related data and styling cues in one object, which is then passed to the `updatePanel` function for rendering. This separation of data preparation and display logic keeps the library focused on its presentation task. Visual Cues and Formatting Price Formatting: Price levels are formatted to match the instrument's minimum tick size using an internal `formatPrice` helper function, ensuring consistent and accurate display. Large FVG Icon: If an FVG is marked as a "Large Volume" FVG in the `panelData` object, a user-specified icon (e.g., an emoji) is prepended to its price level in the panel, providing an immediate visual distinction. Conditional Styling: The background and text colors for each FVG level displayed in the panel can be individually controlled via the `panelData` object, enabling the main script to implement custom styling rules (e.g., highlighting the overall nearest FVG across all timeframes). Handling Missing Data: If no FVG data is available for a particular cell (i.e., the corresponding level in `panelData` is `na`), the panel displays "---" and uses a specified background color for "Not Available" cells. █ CALCULATIONS AND USE Using the `FvgPanel` typically involves a two-stage process: initialization and dynamic updates. Step 1: Panel Creation First, an instance of the panel table is created once, usually during the script's initial setup. This is done using the `createPanel` function. Call `createPanel()` with parameters defining its position on the chart, border color, border width, header background color, header text color, and header text size. This function initializes the table with three columns ("TF", "Bull FVG", "Bear FVG") and three data rows labeled "Current", "MTF", and "HTF", plus a header row. Store the returned `table` object in a `var` variable to persist it across bars. // Example: var table infoPanel = na if barstate.isfirst infoPanel := panel.createPanel( position.top_right, color.gray, 1, color.new(color.gray, 50), color.white, size.small ) Step 2: Panel Updates On each bar, or whenever the FVG data changes (typically on `barstate.islast` or `barstate.isrealtime` for efficiency), the panel's content needs to be refreshed. This is done using the `updatePanel` function. Populate an instance of the `panelData` UDT with the latest FVG information. This includes setting the nearest bullish/bearish mitigation levels for LTF, MTF, and HTF, their LV status, and their desired background and text colors. Call `updatePanel()`, passing the persistent `table` object (from Step 1), the populated `panelData` object, the icon string for LV FVGs, the default text color for FVG levels, the background color for "N/A" cells, and the general text size for the data cells. The `updatePanel` function will then clear previous data and fill the table cells with the new values and styles provided in the `panelData` object. // Example (inside a conditional block like 'if barstate.islast'): var panelData fvgDisplayData = panelData.new() // ... (logic to populate fvgDisplayData fields) ... // fvgDisplayData.nearestBullMitLvl = ... // fvgDisplayData.ltfBullBgColor = ... // ... etc. if not na(infoPanel) panel.updatePanel( infoPanel, fvgDisplayData, "🔥", // LV FVG Icon color.white, color.new(color.gray, 70), // NA Cell Color size.small ) This workflow ensures that the panel is drawn only once and its cells are efficiently updated as new data becomes available. █ NOTES Data Source: This library is solely responsible for the visual presentation of FVG data in a table. It does not perform any FVG detection or calculation. The calling script must compute or retrieve the FVG levels, LV status, and desired styling to populate the `panelData` object. Styling Responsibility: While `updatePanel` applies colors passed via the `panelData` object, the logic for *determining* those colors (e.g., highlighting the closest FVG to the current price) resides in the calling script. Performance: The library uses `table.cell()` to update individual cells, which is generally more efficient than deleting and recreating the table on each update. However, the frequency of `updatePanel` calls should be managed by the main script (e.g., using `barstate.islast` or `barstate.isrealtime`) to avoid excessive processing on historical bars. `series float` Handling: The price level fields within the `panelData` UDT (e.g., `nearestBullMitLvl`) can accept `series float` values, as these are typically derived from price data. The internal `formatPrice` function correctly handles `series float` for display. Dependencies: The `FvgPanel` itself is self-contained and does not import other user libraries. It uses standard Pine Script™ table and string functionalities. █ EXPORTED TYPES panelData   Represents the data structure for populating the FVG information panel.   Fields:      nearestBullMitLvl (series float) : The price level of the nearest bullish FVG's mitigation point (bottom for bull) on the LTF.      isNearestBullLV (series bool) : True if the nearest bullish FVG on the LTF is a Large Volume FVG.      ltfBullBgColor (series color) : Background color for the LTF bullish FVG cell in the panel.      ltfBullTextColor (series color) : Text color for the LTF bullish FVG cell in the panel.      nearestBearMitLvl (series float) : The price level of the nearest bearish FVG's mitigation point (top for bear) on the LTF.      isNearestBearLV (series bool) : True if the nearest bearish FVG on the LTF is a Large Volume FVG.      ltfBearBgColor (series color) : Background color for the LTF bearish FVG cell in the panel.      ltfBearTextColor (series color) : Text color for the LTF bearish FVG cell in the panel.      nearestMtfBullMitLvl (series float) : The price level of the nearest bullish FVG's mitigation point on the MTF.      isNearestMtfBullLV (series bool) : True if the nearest bullish FVG on the MTF is a Large Volume FVG.      mtfBullBgColor (series color) : Background color for the MTF bullish FVG cell.      mtfBullTextColor (series color) : Text color for the MTF bullish FVG cell.      nearestMtfBearMitLvl (series float) : The price level of the nearest bearish FVG's mitigation point on the MTF.      isNearestMtfBearLV (series bool) : True if the nearest bearish FVG on the MTF is a Large Volume FVG.      mtfBearBgColor (series color) : Background color for the MTF bearish FVG cell.      mtfBearTextColor (series color) : Text color for the MTF bearish FVG cell.      nearestHtfBullMitLvl (series float) : The price level of the nearest bullish FVG's mitigation point on the HTF.      isNearestHtfBullLV (series bool) : True if the nearest bullish FVG on the HTF is a Large Volume FVG.      htfBullBgColor (series color) : Background color for the HTF bullish FVG cell.      htfBullTextColor (series color) : Text color for the HTF bullish FVG cell.      nearestHtfBearMitLvl (series float) : The price level of the nearest bearish FVG's mitigation point on the HTF.      isNearestHtfBearLV (series bool) : True if the nearest bearish FVG on the HTF is a Large Volume FVG.      htfBearBgColor (series color) : Background color for the HTF bearish FVG cell.      htfBearTextColor (series color) : Text color for the HTF bearish FVG cell. █ EXPORTED FUNCTIONS createPanel(position, borderColor, borderWidth, headerBgColor, headerTextColor, headerTextSize)   Creates and initializes the FVG information panel (table). Sets up the header rows and timeframe labels.   Parameters:      position (simple string) : The position of the panel on the chart (e.g., position.top_right). Uses position.* constants.      borderColor (simple color) : The color of the panel's border.      borderWidth (simple int) : The width of the panel's border.      headerBgColor (simple color) : The background color for the header cells.      headerTextColor (simple color) : The text color for the header cells.      headerTextSize (simple string) : The text size for the header cells (e.g., size.small). Uses size.* constants.   Returns: The newly created table object representing the panel. updatePanel(panelTable, data, lvIcon, defaultTextColor, naCellColor, textSize)   Updates the content of the FVG information panel with the latest FVG data.   Parameters:      panelTable (table) : The table object representing the panel to be updated.      data (panelData) : An object containing the FVG data to display.      lvIcon (simple string) : The icon (e.g., emoji) to display next to Large Volume FVGs.      defaultTextColor (simple color) : The default text color for FVG levels if not highlighted.      naCellColor (simple color) : The background color for cells where no FVG data is available ("---").      textSize (simple string) : The text size for the FVG level data (e.g., size.small).   Returns: _void
Biblioteca Pine Script®
por no1x
Adaptive Fibonacci Pullback System -FibonacciFluxAdaptive Fibonacci Pullback System (AFPS) - FibonacciFlux This work is licensed under a Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). Original concepts by FibonacciFlux. Abstract The Adaptive Fibonacci Pullback System (AFPS) presents a sophisticated, institutional-grade algorithmic strategy engineered for high-probability trend pullback entries. Developed by FibonacciFlux, AFPS uniquely integrates a proprietary Multi-Fibonacci Supertrend engine (0.618, 1.618, 2.618 ratios) for harmonic volatility assessment, an Adaptive Moving Average (AMA) Channel providing dynamic market context, and a synergistic Multi-Timeframe (MTF) filter suite (RSI, MACD, Volume). This strategy transcends simple indicator combinations through its strict, multi-stage confluence validation logic. Historical simulations suggest that specific MTF filter configurations can yield exceptional performance metrics, potentially achieving Profit Factors exceeding 2.6 , indicative of institutional-level potential, while maintaining controlled risk under realistic trading parameters (managed equity risk, commission, slippage). 4 hourly MTF filtering 1. Introduction: Elevating Pullback Trading with Adaptive Confluence Traditional pullback strategies often struggle with noise, false signals, and adapting to changing market dynamics. AFPS addresses these challenges by introducing a novel framework grounded in Fibonacci principles and adaptive logic. Instead of relying on static levels or single confirmations, AFPS seeks high-probability pullback entries within established trends by validating signals through a rigorous confluence of: Harmonic Volatility Context: Understanding the trend's stability and potential turning points using the unique Multi-Fibonacci Supertrend. Adaptive Market Structure: Assessing the prevailing trend regime via the AMA Channel. Multi-Dimensional Confirmation: Filtering signals with lower-timeframe Momentum (RSI), Trend Alignment (MACD), and Market Conviction (Volume) using the MTF suite. The objective is to achieve superior signal quality and adaptability, moving beyond conventional pullback methodologies. 2. Core Methodology: Synergistic Integration AFPS's effectiveness stems from the engineered synergy between its core components: 2.1. Multi-Fibonacci Supertrend Engine: Utilizes specific Fibonacci ratios (0.618, 1.618, 2.618) applied to ATR, creating a multi-layered volatility envelope potentially resonant with market harmonics. The averaged and EMA-smoothed result (`smoothed_supertrend`) provides a robust, dynamic trend baseline and context filter. // Key Components: Multi-Fibonacci Supertrend & Smoothing average_supertrend = (supertrend1 + supertrend2 + supertrend3) / 3 smoothed_supertrend = ta.ema(average_supertrend, st_smooth_length) 2.2. Adaptive Moving Average (AMA) Channel: Provides dynamic market context. The `ama_midline` serves as a key filter in the entry logic, confirming the broader trend bias relative to adaptive price action. Extended Fibonacci levels derived from the channel width offer potential dynamic S/R zones. // Key Component: AMA Midline ama_midline = (ama_high_band + ama_low_band) / 2 2.3. Multi-Timeframe (MTF) Filter Suite: An optional but powerful validation layer (RSI, MACD, Volume) assessed on a lower timeframe. Acts as a **validation cascade** – signals must pass all enabled filters simultaneously. 2.4. High-Confluence Entry Logic: The core innovation. A pullback entry requires a specific sequence and validation: Price interaction with `average_supertrend` and recovery above/below `smoothed_supertrend`. Price confirmation relative to the `ama_midline`. Simultaneous validation by all enabled MTF filters. // Simplified Long Entry Logic Example (incorporates key elements) long_entry_condition = enable_long_positions and (low < average_supertrend and close > smoothed_supertrend) and // Pullback & Recovery (close > ama_midline and close > ama_midline) and // AMA Confirmation (rsi_filter_long_ok and macd_filter_long_ok and volume_filter_ok) // MTF Validation This strict, multi-stage confluence significantly elevates signal quality compared to simpler pullback approaches. 1hourly filtering 3. Realistic Implementation and Performance Potential AFPS is designed for practical application, incorporating realistic defaults and highlighting performance potential with crucial context: 3.1. Realistic Default Strategy Settings: The script includes responsible default parameters: strategy('Adaptive Fibonacci Pullback System - FibonacciFlux', shorttitle = "AFPS", ..., initial_capital = 10000, // Accessible capital default_qty_type = strategy.percent_of_equity, // Equity-based risk default_qty_value = 4, // Default 4% equity risk per initial trade commission_type = strategy.commission.percent, commission_value = 0.03, // Realistic commission slippage = 2, // Realistic slippage pyramiding = 2 // Limited pyramiding allowed ) Note: The default 4% risk (`default_qty_value = 4`) requires careful user assessment and adjustment based on individual risk tolerance. 3.2. Historical Performance Insights & Institutional Potential: Backtesting provides insights into historical behavior under specific conditions (always specify Asset/Timeframe/Dates when sharing results): Default Performance Example: With defaults, historical tests might show characteristics like Overall PF ~1.38, Max DD ~1.16%, with potential Long/Short performance variance (e.g., Long PF 1.6+, Short PF < 1). Optimized MTF Filter Performance: Crucially, historical simulations demonstrate that meticulous configuration of the MTF filters (particularly RSI and potentially others depending on market) can significantly enhance performance. Under specific, optimized MTF filter settings combined with appropriate risk management (e.g., 7.5% risk), historical tests have indicated the potential to achieve **Profit Factors exceeding 2.6**, alongside controlled drawdowns (e.g., ~1.32%). This level of performance, if consistently achievable (which requires ongoing adaptation), aligns with metrics often sought in institutional trading environments. Disclaimer Reminder: These results are strictly historical simulations. Past performance does not guarantee future results. Achieving high performance requires careful parameter tuning, adaptation to changing markets, and robust risk management. 3.3. Emphasizing Risk Management: Effective use of AFPS mandates active risk management. Utilize the built-in Stop Loss, Take Profit, and Trailing Stop features. The `pyramiding = 2` setting requires particularly diligent oversight. Do not rely solely on default settings. 4. Conclusion: Advancing Trend Pullback Strategies The Adaptive Fibonacci Pullback System (AFPS) offers a sophisticated, theoretically grounded, and highly adaptable framework for identifying and executing high-probability trend pullback trades. Its unique blend of Fibonacci resonance, adaptive context, and multi-dimensional MTF filtering represents a significant advancement over conventional methods. While requiring thoughtful implementation and risk management, AFPS provides discerning traders with a powerful tool potentially capable of achieving institutional-level performance characteristics under optimized conditions. Acknowledgments Developed by FibonacciFlux. Inspired by principles of Fibonacci analysis, adaptive averaging, and multi-timeframe confirmation techniques explored within the trading community. Disclaimer Trading involves substantial risk. AFPS is an analytical tool, not a guarantee of profit. Past performance is not indicative of future results. Market conditions change. Users are solely responsible for their decisions and risk management. Thorough testing is essential. Deploy at your own considered risk.
Estratégia Pine Script®
por FibonacciFlux
Luxy Super-Duper SuperTrend Predictor Engine and Buy/Sell signalA professional trend-following grading system that analyzes historical trend patterns to provide statistical duration estimates using advanced similarity matching and k-nearest neighbors analysis. Combines adaptive Supertrend with intelligent duration statistics, multi-timeframe confluence, volume confirmation, and quality scoring to identify high-probability setups with data-driven target ranges across all timeframes. Note: All duration estimates are statistical calculations based on historical data, not guarantees of future performance. WHAT MAKES THIS DIFFERENT Unlike traditional SuperTrend indicators that only tell you trend direction, this system answers the critical question: "What is the typical duration for trends like this?" The Statistical Analysis Engine: • Analyzes your chart's last 15+ completed SuperTrend trends (bullish and bearish separately) • Uses k-nearest neighbors similarity matching to find historically similar setups • Calculates statistical duration estimates based on current market conditions • Learns from estimation errors and adapts over time (Advanced mode) • Displays visual duration analysis box showing median, average, and range estimates • Tracks Statistical accuracy with backtest statistics Complete Trading System: • Statistical trend duration analysis with three intelligence levels • Adaptive Supertrend with dynamic ATR-based bands • Multi-timeframe confluence analysis (6 timeframes: 5M to 1W) • Volume confirmation with spike detection and momentum tracking • Quality scoring system (0-70 points) rating each setup • One-click preset optimization for all trading styles • Anti-repaint guarantee on all signals and duration estimates METHODOLOGY CREDITS This indicator's approach is inspired by proven trading methodologies from respected market educators: • Mark Minervini - Volatility Contraction Pattern (VCP) and pullback entry techniques • William O'Neil - Volume confirmation principles and institutional buying patterns (CANSLIM methodology) • Dan Zanger - Volatility expansion entries and momentum breakout strategies Important: These are educational references only. This indicator does not guarantee any specific trading results. Always conduct your own analysis and risk management. KEY FEATURES 1. TREND DURATION ANALYSIS SYSTEM - The Core Innovation The statistical analysis engine is what sets this indicator apart from standard SuperTrend systems. It doesn't just identify trend changes - it provides statistical analysis of potential duration. How It Works: Step 1: Historical Tracking • Automatically records every completed SuperTrend trend (duration in bars) • Maintains separate databases for bullish trends and bearish trends • Stores up to 15 most recent trends of each type • Captures market conditions at each trend flip: volume ratio, ATR ratio, quality score, price distance from SuperTrend, proximity to support/resistance Step 2: Similarity Matching (k-Nearest Neighbors) • When new trend begins, system compares current conditions to ALL historical flips • Calculates similarity score based on: - Volume similarity (30% weight) - Is volume behaving similarly? - Volatility similarity (30% weight) - Is ATR/volatility similar? - Quality similarity (20% weight) - Is setup strength comparable? - Distance similarity (10% weight) - Is price distance from ST similar? - Support/Resistance proximity (10% weight) - Similar structural context? • Selects the 15 MOST SIMILAR historical trends (not just all trends) • This is like asking: "When conditions looked like this before, how long did trends last?" Step 3: Statistical Analysis • Calculates median duration (most common outcome) • Calculates average duration (mean of similar trends) • Determines realistic range (min to max of similar trends) • Applies exponential weighting (recent trends weighted more heavily) • Outputs confidence-weighted statistical estimate Step 4: Advanced Intelligence (Advanced Mode Only) The Advanced mode applies five sophisticated multipliers to refine estimates: A) Market Structure Multiplier (±30%): • Detects nearby support/resistance levels using pivot detection • If flip occurs NEAR a key level: Estimate adjusted -30% (expect bounce/rejection) • If flip occurs in open space: Estimate adjusted +30% (clear path for continuation) • Uses configurable lookback period and ATR-based proximity threshold B) Asset Type Multiplier (±40%): • Adjusts duration estimates based on asset volatility characteristics • Small Cap / Biotech: +40% (explosive, extended moves) • Tech Growth: +20% (momentum-driven, longer trends) • Blue Chip / Large Cap: 0% (baseline, steady trends) • Dividend / Value: -20% (slower, grinding trends) • Cyclical: Variable based on macro regime • Crypto / High Volatility: +30% (parabolic potential) C) Flip Strength Multiplier (±20%): • Analyzes the QUALITY of the trend flip itself • Strong flip (high volume + expanding ATR + quality score 60+): +20% • Weak flip (low volume + contracting ATR + quality score under 40): -20% • Logic: Historical data shows that powerful flips tend to be followed by longer trends D) Error Learning Multiplier (±15%): • Tracks Statistical accuracy over last 10 completed trends • Calculates error ratio: (estimated duration / Actual Duration) • If system consistently over-estimates: Apply -15% correction • If system consistently under-estimates: Apply +15% correction • Learns and adapts to current market regime E) Regime Detection Multiplier (±20%): • Analyzes last 3 trends of SAME TYPE (bull-to-bull or bear-to-bear) • Compares recent trend durations to historical average • If recent trends 20%+ longer than average: +20% adjustment (trending regime detected) • If recent trends 20%+ shorter than average: -20% adjustment (choppy regime detected) • Detects whether market is in trending or mean-reversion mode Three analysis modes: SIMPLE MODE - Basic Statistics • Uses raw median of similar trends only • No multipliers, no adjustments • Best for: Beginners, clean trending markets • Fastest calculations, minimal complexity STANDARD MODE - Full Statistical Analysis • Similarity matching with k-nearest neighbors • Exponential weighting of recent trends • Median, average, and range calculations • Best for: Most traders, general market conditions • Balance of accuracy and simplicity ADVANCED MODE - Statistics + Intelligence • Everything in Standard mode PLUS • All 5 advanced multipliers (structure, asset type, flip strength, learning, regime) • Highest Statistical accuracy in testing • Best for: Experienced traders, volatile/complex markets • Maximum intelligence, most adaptive Visual Duration Analysis Box: When a new trend begins (SuperTrend flip), a box appears on your chart showing: • Analysis Mode (Simple / Standard / Advanced) • Number of historical trends analyzed • Median expected duration (most likely outcome) • Average expected duration (mean of similar trends) • Range (minimum to maximum from similar trends) • Advanced multipliers breakdown (Advanced mode only) • Backtest accuracy statistics (if available) The box extends from the flip bar to the estimated endpoint based on historical data, giving you a visual target for trend duration. Box updates in real-time as trend progresses. Backtest & Accuracy Tracking: • System backtests its own duration estimates using historical data • Shows accuracy metrics: how well duration estimates matched actual durations • Tracks last 10 completed duration estimates separately • Displays statistics in dashboard and duration analysis boxes • Helps you understand statistical reliability on your specific symbol/timeframe Anti-Repaint Guarantee: • duration analysis boxes only appear AFTER bar close (barstate.isconfirmed) • Historical duration estimates never disappear or change • What you see in history is exactly what you would have seen real-time • No future data leakage, no lookahead bias 2. INTELLIGENT PRESET CONFIGURATIONS - One-Click Optimization Unlike indicators that require tedious parameter tweaking, this system includes professionally optimized presets for every trading style. Select your approach from the dropdown and ALL parameters auto-configure. "AUTO (DETECT FROM TF)" - RECOMMENDED The smartest option: automatically selects optimal settings based on your chart timeframe. • 1m-5m charts → Scalping preset (ATR: 7, Mult: 2.0) • 15m-1h charts → Day Trading preset (ATR: 10, Mult: 2.5) • 2h-4h-D charts → Swing Trading preset (ATR: 14, Mult: 3.0) • W-M charts → Position Trading preset (ATR: 21, Mult: 4.0) Benefits: • Zero configuration - works immediately • Always matched to your timeframe • Switch timeframe = automatic adjustment • Perfect for traders who use multiple timeframes "SCALPING (1-5M)" - Ultra-Fast Signals Optimized for: 1-5 minute charts, high-frequency trading, quick profits Target holding period: Minutes to 1-2 hours maximum Best markets: High-volume stocks, major crypto pairs, active futures Parameter Configuration: • Supertrend: ATR 7, Multiplier 2.0 (very sensitive) • Volume: MA 10, High 1.8x, Spike 3.0x (catches quick surges) • Volume Momentum: AUTO-DISABLED (too restrictive for fast scalping) • Quality minimum: 40 points (accepts more setups) • Duration Analysis: Uses last 15 trends with heavy recent weighting Trading Logic: Speed over precision. Short ATR period and low multiplier create highly responsive SuperTrend. Volume momentum filter disabled to avoid missing fast moves. Quality threshold relaxed to catch more opportunities in rapid market conditions. Signals per session: 5-15 typically Hold time: Minutes to couple hours Best for: Active traders with fast execution "DAY TRADING (15M-1H)" - Balanced Approach Optimized for: 15-minute to 1-hour charts, intraday moves, session-based trading Target holding period: 30 minutes to 8 hours (within trading day) Best markets: Large-cap stocks, major indices, established crypto Parameter Configuration: • Supertrend: ATR 10, Multiplier 2.5 (balanced) • Volume: MA 20, High 1.5x, Spike 2.5x (standard detection) • Volume Momentum: 5/20 periods (confirms intraday strength) • Quality minimum: 50 points (good setups preferred) • Duration Analysis: Balanced weighting of recent vs historical Trading Logic: The most balanced configuration. ATR 10 with multiplier 2.5 provides steady trend following that avoids noise while catching meaningful moves. Volume momentum confirms institutional participation without being overly restrictive. Signals per session: 2-5 typically Hold time: 30 minutes to full day Best for: Part-time and full-time active traders "SWING TRADING (4H-D)" - Trend Stability Optimized for: 4-hour to Daily charts, multi-day holds, trend continuation Target holding period: 2-15 days typically Best markets: Growth stocks, sector ETFs, trending crypto, commodity futures Parameter Configuration: • Supertrend: ATR 14, Multiplier 3.0 (stable) • Volume: MA 30, High 1.3x, Spike 2.2x (accumulation focus) • Volume Momentum: 10/30 periods (trend stability) • Quality minimum: 60 points (high-quality setups only) • Duration Analysis: Favors consistent historical patterns Trading Logic: Designed for substantial trend moves while filtering short-term noise. Higher ATR period and multiplier create stable SuperTrend that won't flip on minor corrections. Stricter quality requirements ensure only strongest setups generate signals. Signals per week: 2-5 typically Hold time: Days to couple weeks Best for: Part-time traders, swing style "POSITION TRADING (D-W)" - Long-Term Trends Optimized for: Daily to Weekly charts, major trend changes, portfolio allocation Target holding period: Weeks to months Best markets: Blue-chip stocks, major indices, established cryptocurrencies Parameter Configuration: • Supertrend: ATR 21, Multiplier 4.0 (very stable) • Volume: MA 50, High 1.2x, Spike 2.0x (long-term accumulation) • Volume Momentum: 20/50 periods (major trend confirmation) • Quality minimum: 70 points (excellent setups only) • Duration Analysis: Heavy emphasis on multi-year historical data Trading Logic: Conservative approach focusing on major trend changes. Extended ATR period and high multiplier create SuperTrend that only flips on significant reversals. Very strict quality filters ensure signals represent genuine long-term opportunities. Signals per month: 1-2 typically Hold time: Weeks to months Best for: Long-term investors, set-and-forget approach "CUSTOM" - Advanced Configuration Purpose: Complete manual control for experienced traders Use when: You understand the parameters and want specific optimization Best for: Testing new approaches, unusual market conditions, specific instruments Full control over: • All SuperTrend parameters • Volume thresholds and momentum periods • Quality scoring weights • analysis mode and multipliers • Advanced features tuning Preset Comparison Quick Reference: Chart Timeframe: Scalping (1M-5M) | Day Trading (15M-1H) | Swing (4H-D) | Position (D-W) Signals Frequency: Very High | High | Medium | Low Hold Duration: Minutes | Hours | Days | Weeks-Months Quality Threshold: 40 pts | 50 pts | 60 pts | 70 pts ATR Sensitivity: Highest | Medium | Lower | Lowest Time Investment: Highest | High | Medium | Lowest Experience Level: Expert | Advanced | Intermediate | Beginner+ 3. QUALITY SCORING SYSTEM (0-70 Points) Every signal is rated in real-time across three dimensions: Volume Confirmation (0-30 points): • Volume Spike (2.5x+ average): 30 points • High Volume (1.5x+ average): 20 points • Above Average (1.0x+ average): 10 points • Below Average: 0 points Volatility Assessment (0-30 points): • Expanding ATR (1.2x+ average): 30 points • Rising ATR (1.0-1.2x average): 15 points • Contracting/Stable ATR: 0 points Volume Momentum (0-10 points): • Strong Momentum (1.2x+ ratio): 10 points • Rising Momentum (1.0-1.2x ratio): 5 points • Weak/Neutral Momentum: 0 points Score Interpretation: 60-70 points - EXCELLENT: • All factors aligned • High conviction setup • Maximum position size (within risk limits) • Primary trading opportunities 45-59 points - STRONG: • Multiple confirmations present • Above-average setup quality • Standard position size • Good trading opportunities 30-44 points - GOOD: • Basic confirmations met • Acceptable setup quality • Reduced position size • Wait for additional confirmation or trade smaller Below 30 points - WEAK: • Minimal confirmations • Low probability setup • Consider passing • Only for aggressive traders in strong trends Only signals meeting your minimum quality threshold (configurable per preset) generate alerts and labels. 4. MULTI-TIMEFRAME CONFLUENCE ANALYSIS The system can simultaneously analyze trend alignment across 6 timeframes (optional feature): Timeframes analyzed: • 5-minute (scalping context) • 15-minute (intraday momentum) • 1-hour (day trading bias) • 4-hour (swing context) • Daily (primary trend) • Weekly (macro trend) Confluence Interpretation: • 5-6/6 aligned - Very strong multi-timeframe agreement (highest confidence) • 3-4/6 aligned - Moderate agreement (standard setup) • 1-2/6 aligned - Weak agreement (caution advised) Dashboard shows real-time alignment count with color-coding. Higher confluence typically correlates with longer, stronger trends. 5. VOLUME MOMENTUM FILTER - Institutional Money Flow Unlike traditional volume indicators that just measure size, Volume Momentum tracks the RATE OF CHANGE in volume: How it works: • Compares short-term volume average (fast period) to long-term average (slow period) • Ratio above 1.0 = Volume accelerating (money flowing IN) • Ratio above 1.2 = Strong acceleration (institutional participation likely) • Ratio below 0.8 = Volume decelerating (money flowing OUT) Why it matters: • Confirms trend with actual money flow, not just price • Leading indicator (volume often leads price) • Catches accumulation/distribution before breakouts • More intuitive than complex mathematical filters Integration with signals: • Optional filter - can be enabled/disabled per preset • When enabled: Only signals with rising volume momentum fire • AUTO-DISABLED in Scalping mode (too restrictive for fast trading) • Configurable fast/slow periods per trading style 6. ADAPTIVE SUPERTREND MULTIPLIER Traditional SuperTrend uses fixed ATR multiplier. This system dynamically adjusts the multiplier (0.8x to 1.2x base) based on: • Trend Strength: Price correlation over lookback period • Volume Weight: Current volume relative to average Benefits: • Tighter bands in calm markets (less premature exits) • Wider bands in volatile conditions (avoids whipsaws) • Better adaptation to biotech, small-cap, and crypto volatility • Optional - can be disabled for classic constant multiplier 7. VISUAL GRADIENT RIBBON 26-layer exponential gradient fill between price and SuperTrend line provides instant visual trend strength assessment: Color System: • Green shades - Bullish trend + volume confirmation (strongest) • Blue shades - Bullish trend, normal volume • Orange shades - Bearish trend + volume confirmation • Red shades - Bearish trend (weakest) Opacity varies based on: • Distance from SuperTrend (farther = more opaque) • Volume intensity (higher volume = stronger color) The ribbon provides at-a-glance trend strength without cluttering your chart. Can be toggled on/off. 8. INTELLIGENT ALERT SYSTEM Two-tier alert architecture for flexibility: Automatic Alerts: • Fire automatically on BUY and SELL signals • Include full context: quality score, volume state, volume momentum • One alert per bar close (alert.freq_once_per_bar_close) • Message format: "BUY: Supertrend bullish + Quality: 65/70 | Volume: HIGH | Vol Momentum: STRONG (1.35x)" Customizable Alert Conditions: • Appear in TradingView's "Create Alert" dialog • Three options: BUY Signal Only, SELL Signal Only, ANY Signal (BUY or SELL) • Use TradingView placeholders: {{ticker}}, {{interval}}, {{close}}, {{time}} • Fully customizable message templates All alerts use barstate.isconfirmed - Zero repaint guarantee. 9. ANTI-REPAINT ARCHITECTURE Every component guaranteed non-repainting: • Entry signals: Only appear after bar close • duration analysis boxes: Created only on confirmed SuperTrend flips • Informative labels: Wait for bar confirmation • Alerts: Fire once per closed bar • Multi-timeframe data: Uses lookahead=barmerge.lookahead_off What you see in history is exactly what you would have seen in real-time. No disappearing signals, no changed duration estimates. HOW TO USE THE INDICATOR QUICK START - 3 Steps to Trading: Step 1: Select Your Trading Style Open indicator settings → "Quick Setup" section → Trading Style Preset dropdown Options: • Auto (Detect from TF) - RECOMMENDED: Automatically configures based on your chart timeframe • Scalping (1-5m) - For 1-5 minute charts, ultra-fast signals • Day Trading (15m-1h) - For 15m-1h charts, balanced approach • Swing Trading (4h-D) - For 4h-Daily charts, trend stability • Position Trading (D-W) - For Daily-Weekly charts, long-term trends • Custom - Manual configuration (advanced users only) Choose "Auto" and you're done - all parameters optimize automatically. Step 2: Understand the Signals BUY Signal (Green Triangle Below Price): • SuperTrend flipped bullish • Quality score meets minimum threshold (varies by preset) • Volume confirmation present (if filter enabled) • Volume momentum rising (if filter enabled) • duration analysis box shows expected trend duration SELL Signal (Red Triangle Above Price): • SuperTrend flipped bearish • Quality score meets minimum threshold • Volume confirmation present (if filter enabled) • Volume momentum rising (if filter enabled) • duration analysis box shows expected trend duration Duration Analysis Box: • Appears at SuperTrend flip (start of new trend) • Shows median, average, and range duration estimates • Extends to estimated endpoint based on historical data visually • Updates mode-specific intelligence (Simple/Standard/Advanced) Step 3: Use the Dashboard for Context Dashboard (top-right corner) shows real-time metrics: • Row 1 - Quality Score: Current setup rating (0-70) • Row 2 - SuperTrend: Direction and current level • Row 3 - Volume: Status (Spike/High/Normal/Low) with color • Row 4 - Volatility: State (Expanding/Rising/Stable/Contracting) • Row 5 - Volume Momentum: Ratio and trend • Row 6 - Duration Statistics: Accuracy metrics and track record Every cell has detailed tooltip - hover for full explanations. SIGNAL INTERPRETATION BY QUALITY SCORE: Excellent Setup (60-70 points): • Quality Score: 60-70 • Volume: Spike or High • Volatility: Expanding • Volume Momentum: Strong (1.2x+) • MTF Confluence (if enabled): 5-6/6 • Action: Primary trade - maximum position size (within risk limits) • Statistical reliability: Highest - duration estimates most accurate Strong Setup (45-59 points): • Quality Score: 45-59 • Volume: High or Above Average • Volatility: Rising • Volume Momentum: Rising (1.0-1.2x) • MTF Confluence (if enabled): 3-4/6 • Action: Standard trade - normal position size • Statistical reliability: Good - duration estimates reliable Good Setup (30-44 points): • Quality Score: 30-44 • Volume: Above Average • Volatility: Stable or Rising • Volume Momentum: Neutral to Rising • MTF Confluence (if enabled): 3-4/6 • Action: Cautious trade - reduced position size, wait for additional confirmation • Statistical reliability: Moderate - duration estimates less certain Weak Setup (Below 30 points): • Quality Score: Below 30 • Volume: Low or Normal • Volatility: Contracting or Stable • Volume Momentum: Weak • MTF Confluence (if enabled): 1-2/6 • Action: Pass or wait for improvement • Statistical reliability: Low - duration estimates unreliable USING duration analysis boxES FOR TRADE MANAGEMENT: Entry Timing: • Enter on SuperTrend flip (signal bar close) • duration analysis box appears simultaneously • Note the median duration - this is your expected hold time Profit Targets: • Conservative: Use MEDIAN duration as profit target (50% probability) • Moderate: Use AVERAGE duration (mean of similar trends) • Aggressive: Aim for MAX duration from range (best historical outcome) Position Management: • Scale out at median duration (take partial profits) • Trail stop as trend extends beyond median • Full exit at average duration or SuperTrend flip (whichever comes first) • Re-evaluate if trend exceeds estimated range analysis mode Selection: • Simple: Clean trending markets, beginners, minimal complexity • Standard: Most markets, most traders (recommended default) • Advanced: Volatile markets, complex instruments, experienced traders seeking highest accuracy Asset Type Configuration (Advanced Mode): If using Advanced analysis mode, configure Asset Type for optimal accuracy: • Small Cap: Stocks under $2B market cap, low liquidity • Biotech / Speculative: Clinical-stage pharma, penny stocks, high-risk • Blue Chip / Large Cap: S&P 500, mega-cap tech, stable large companies • Tech Growth: High-growth tech (TSLA, NVDA, growth SaaS) • Dividend / Value: Dividend aristocrats, value stocks, utilities • Cyclical: Energy, materials, industrials (macro-driven) • Crypto / High Volatility: Bitcoin, altcoins, highly volatile assets Correct asset type selection improves Statistical accuracy by 15-20%. RISK MANAGEMENT GUIDELINES: 1. Stop Loss Placement: Long positions: • Place stop below recent swing low OR • Place stop below SuperTrend level (whichever is tighter) • Use 1-2 ATR distance as guideline • Recommended: SuperTrend level (built-in volatility adjustment) Short positions: • Place stop above recent swing high OR • Place stop above SuperTrend level (whichever is tighter) • Use 1-2 ATR distance as guideline • Recommended: SuperTrend level 2. Position Sizing by Quality Score: • Excellent (60-70): Maximum position size (2% risk per trade) • Strong (45-59): Standard position size (1.5% risk per trade) • Good (30-44): Reduced position size (1% risk per trade) • Weak (Below 30): Pass or micro position (0.5% risk - learning trades only) 3. Exit Strategy Options: Option A - Statistical Duration-Based Exit: • Exit at median estimated duration (conservative) • Exit at average estimated duration (moderate) • Trail stop beyond average duration (aggressive) Option B - Signal-Based Exit: • Exit on opposite signal (SELL after BUY, or vice versa) • Exit on SuperTrend flip (trend reversal) • Exit if quality score drops below 30 mid-trend Option C - Hybrid (Recommended): • Take 50% profit at median estimated duration • Trail stop on remaining 50% using SuperTrend as trailing level • Full exit on SuperTrend flip or quality collapse 4. Trade Filtering: For higher win-rate (fewer trades, better quality): • Increase minimum quality score (try 60 for swing, 50 for day trading) • Enable volume momentum filter (ensure institutional participation) • Require higher MTF confluence (5-6/6 alignment) • Use Advanced analysis mode with appropriate asset type For more opportunities (more trades, lower quality threshold): • Decrease minimum quality score (40 for day trading, 35 for scalping) • Disable volume momentum filter • Lower MTF confluence requirement • Use Simple or Standard analysis mode SETTINGS OVERVIEW Quick Setup Section: • Trading Style Preset: Auto / Scalping / Day Trading / Swing / Position / Custom Dashboard & Display: • Show Dashboard (ON/OFF) • Dashboard Position (9 options: Top/Middle/Bottom + Left/Center/Right) • Text Size (Auto/Tiny/Small/Normal/Large/Huge) • Show Ribbon Fill (ON/OFF) • Show SuperTrend Line (ON/OFF) • Bullish Color (default: Green) • Bearish Color (default: Red) • Show Entry Labels - BUY/SELL signals (ON/OFF) • Show Info Labels - Volume events (ON/OFF) • Label Size (Auto/Tiny/Small/Normal/Large/Huge) Supertrend Configuration: • ATR Length (default varies by preset: 7-21) • ATR Multiplier Base (default varies by preset: 2.0-4.0) • Use Adaptive Multiplier (ON/OFF) - Dynamic 0.8x-1.2x adjustment • Smoothing Factor (0.0-0.5) - EMA smoothing applied to bands • Neutral Bars After Flip (0-10) - Hide ST immediately after flip Volume Momentum: • Enable Volume Momentum Filter (ON/OFF) • Fast Period (default varies by preset: 3-20) • Slow Period (default varies by preset: 10-50) Volume Analysis: • Volume MA Length (default varies by preset: 10-50) • High Volume Threshold (default: 1.5x) • Spike Threshold (default: 2.5x) • Low Volume Threshold (default: 0.7x) Quality Filters: • Minimum Quality Score (0-70, varies by preset) • Require Volume Confirmation (ON/OFF) Trend Duration Analysis: • Show Duration Analysis (ON/OFF) - Display duration analysis boxes • analysis mode - Simple / Standard / Advanced • Asset Type - 7 options (Small Cap, Biotech, Blue Chip, Tech Growth, Dividend, Cyclical, Crypto) • Use Exponential Weighting (ON/OFF) - Recent trends weighted more • Decay Factor (0.5-0.99) - How much more recent trends matter • Structure Lookback (3-30) - Pivot detection period for support/resistance • Proximity Threshold (xATR) - How close to level qualifies as "near" • Enable Error Learning (ON/OFF) - System learns from estimation errors • Memory Depth (3-20) - How many past errors to remember Box Visual Settings: • duration analysis box Border Color • duration analysis box Background Color • duration analysis box Text Color • duration analysis box Border Width • duration analysis box Transparency Multi-Timeframe (Optional Feature): • Enable MTF Confluence (ON/OFF) • Minimum Alignment Required (0-6) • Individual timeframe enable/disable toggles • Custom timeframe selection options All preset configurations override manual inputs except when "Custom" is selected. ADVANCED FEATURES 1. Scalpel Mode (Optional) Advanced pullback entry system that waits for healthy retracements within established trends before signaling entry: • Monitors price distance from SuperTrend levels • Requires pullback to configurable range (default: 30-50%) • Ensures trend remains intact before entry signal • Reduces whipsaw and false breakouts • Inspired by Mark Minervini's VCP pullback entries Best for: Swing traders and day traders seeking precision entries Scalpers: Consider disabling for faster entries 2. Error Learning System (Advanced analysis mode Only) The system learns from its own estimation errors: • Tracks last 10-20 completed duration estimates (configurable memory depth) • Calculates error ratio for each: estimated duration / Actual Duration • If system consistently over-estimates: Applies negative correction (-15%) • If system consistently under-estimates: Applies positive correction (+15%) • Adapts to current market regime automatically This self-correction mechanism improves accuracy over time as the system gathers more data on your specific symbol and timeframe. 3. Regime Detection (Advanced analysis mode Only) Automatically detects whether market is in trending or choppy regime: • Compares last 3 trends to historical average • Recent trends 20%+ longer → Trending regime (+20% to estimates) • Recent trends 20%+ shorter → Choppy regime (-20% to estimates) • Applied separately to bullish and bearish trends Helps duration estimates adapt to changing market conditions without manual intervention. 4. Exponential Weighting Option to weight recent trends more heavily than distant history: • Default decay factor: 0.9 • Recent trends get higher weight in statistical calculations • Older trends gradually decay in importance • Rationale: Recent market behavior more relevant than old data • Can be disabled for equal weighting 5. Backtest Statistics System backtests its own duration estimates using historical data: • Walks through past trends chronologically • Calculates what duration estimate WOULD have been at each flip • Compares to actual duration that occurred • Displays accuracy metrics in duration analysis boxes and dashboard • Helps assess statistical reliability on your specific chart Note: Backtest uses only data available AT THE TIME of each historical flip (no lookahead bias). TECHNICAL SPECIFICATIONS • Pine Script Version: v6 • Indicator Type: Overlay (draws on price chart) • Max Boxes: 500 (for duration analysis box storage) • Max Bars Back: 5000 (for comprehensive historical analysis) • Security Calls: 1 (for MTF if enabled - optimized) • Repainting: NO - All signals and duration estimates confirmed on bar close • Lookahead Bias: NO - All HTF data properly offset, all duration estimates use only historical data • Real-time Updates: YES - Dashboard and quality scores update live • Alert Capable: YES - Both automatic alerts and customizable alert conditions • Multi-Symbol: Works on stocks, crypto, forex, futures, indices Performance Optimization: • Conditional calculations (duration analysis can be disabled to reduce load) • Efficient array management (circular buffers for trend storage) • Streamlined gradient rendering (26 layers, can be toggled off) • Smart label cooldown system (prevents label spam) • Optimized similarity matching (analyzes only relevant trends) Data Requirements: • Minimum 50-100 bars for initial duration analysis (builds historical database) • Optimal: 500+ bars for robust statistical analysis • Longer history = more accurate duration estimates • Works on any timeframe from 1 minute to monthly KNOWN LIMITATIONS • Trending Markets Only: Performs best in clear trends. May generate false signals in choppy/sideways markets (use quality score filtering and regime detection to mitigate) • Lagging Nature: Like all trend-following systems, signals occur AFTER trend establishment, not at exact tops/bottoms. Use duration analysis boxes to set realistic profit targets. • Initial Learning Period: Duration analysis system requires 10-15 completed trends to build reliable historical database. Early duration estimates less accurate (first few weeks on new symbol/timeframe). • Visual Load: 26-layer gradient ribbon may slow performance on older devices. Disable ribbon if experiencing lag. • Statistical accuracy Variables: Duration estimates are statistical estimates, not guarantees. Accuracy varies by: - Market regime (trending vs choppy) - Asset volatility characteristics - Quality of historical pattern matches - Timeframe traded (higher TF = more reliable) • Not Best Suitable For: - Ultra-short-term scalping (sub-1-minute charts) - Mean-reversion strategies (designed for trend-following) - Range-bound trading (requires trending conditions) - News-driven spikes (estimates based on technical patterns, not fundamentals) FREQUENTLY ASKED QUESTIONS Q: Does this indicator repaint? A: Absolutely not. All signals, duration analysis boxes, labels, and alerts use barstate.isconfirmed checks. They only appear after the bar closes. What you see in history is exactly what you would have seen in real-time. Zero repaint guarantee. Q: How accurate are the trend duration estimates? A: Accuracy varies by mode, market conditions, and historical data quality: • Simple mode: 60-70% accuracy (within ±20% of actual duration) • Standard mode: 70-80% accuracy (within ±20% of actual duration) • Advanced mode: 75-85% accuracy (within ±20% of actual duration) Best accuracy achieved on: • Higher timeframes (4H, Daily, Weekly) • Trending markets (not choppy/sideways) • Assets with consistent behavior (Blue Chip, Large Cap) • After 20+ historical trends analyzed (builds robust database) Remember: All duration estimates are statistical calculations based on historical patterns, not guarantees. Q: Which analysis mode should I use? A: • Simple: Beginners, clean trending markets, want minimal complexity • Standard: Most traders, general market conditions (RECOMMENDED DEFAULT) • Advanced: Experienced traders, volatile/complex markets (biotech, small-cap, crypto), seeking maximum accuracy Advanced mode requires correct Asset Type configuration for optimal results. Q: What's the difference between the trading style presets? A: Each preset optimizes ALL parameters for a specific trading approach: • Scalping: Ultra-sensitive (ATR 7, Mult 2.0), more signals, shorter holds • Day Trading: Balanced (ATR 10, Mult 2.5), moderate signals, intraday holds • Swing Trading: Stable (ATR 14, Mult 3.0), fewer signals, multi-day holds • Position Trading: Very stable (ATR 21, Mult 4.0), rare signals, week/month holds Auto mode automatically selects based on your chart timeframe. Q: Should I use Auto mode or manually select a preset? A: Auto mode is recommended for most traders. It automatically matches settings to your timeframe and re-optimizes if you switch charts. Only use manual preset selection if: • You want scalping settings on a 15m chart (overriding auto-detection) • You want swing settings on a 1h chart (more conservative than auto would give) • You're testing different approaches on same timeframe Q: Can I use this for scalping and day trading? A: Absolutely! The preset system is specifically designed for all trading styles: • Select "Scalping (1-5m)" for 1-5 minute charts • Select "Day Trading (15m-1h)" for 15m-1h charts • Or use "Auto" mode and it configures automatically Volume momentum filter is auto-disabled in Scalping mode for faster signals. Q: What is Volume Momentum and why does it matter? A: Volume Momentum compares short-term volume (fast MA) to long-term volume (slow MA). It answers: "Is money flowing into this asset faster now than historically?" Why it matters: • Volume often leads price (early warning system) • Confirms institutional participation (smart money) • No lag like price-based indicators • More intuitive than complex mathematical filters When the ratio is above 1.2, you have strong evidence that institutions are accumulating (bullish) or distributing (bearish). Q: How do I set up alerts? A: Two options: Option 1 - Automatic Alerts: 1. Right-click on chart → Add Alert 2. Condition: Select this indicator 3. Choose "Any alert() function call" 4. Configure notification method (app, email, webhook) 5. You'll receive detailed alerts on every BUY and SELL signal Option 2 - Customizable Alert Conditions: 1. Right-click on chart → Add Alert 2. Condition: Select this indicator 3. You'll see three options in dropdown: - "BUY Signal" (long signals only) - "SELL Signal" (short signals only) - "ANY Signal" (both BUY and SELL) 4. Choose desired option and customize message template 5. Uses TradingView placeholders: {{ticker}}, {{close}}, {{time}}, etc. All alerts fire only on confirmed bar close (no repaint). Q: What is Scalpel Mode and should I use it? A: Scalpel Mode waits for healthy pullbacks within established trends before signaling entry. It reduces whipsaws and improves entry timing. Recommended ON for: • Swing traders (want precision entries on pullbacks) • Day traders (willing to wait for better prices) • Risk-averse traders (prefer fewer but higher-quality entries) Recommended OFF for: • Scalpers (need immediate entries, can't wait for pullbacks) • Momentum traders (want to enter on breakout, not pullback) • Aggressive traders (prefer more opportunities over precision) Q: Why do some duration estimates show wider ranges than others? A: Range width reflects historical trend variability: • Narrow range: Similar historical trends had consistent durations (high confidence) • Wide range: Similar historical trends had varying durations (lower confidence) Wide ranges often occur: • Early in analysis (fewer historical trends to learn from) • In volatile/choppy markets (inconsistent trend behavior) • On lower timeframes (more noise, less consistency) The median and average still provide useful targets even when range is wide. Q: Can I customize the dashboard position and appearance? A: Yes! Dashboard settings include: • Position: 9 options (Top/Middle/Bottom + Left/Center/Right) • Text Size: Auto, Tiny, Small, Normal, Large, Huge • Show/Hide: Toggle entire dashboard on/off Choose position that doesn't overlap important price action on your specific chart. Q: Which timeframe should I trade on? A: Depends on your trading style and time availability: • 1-5 minute: Active scalping, requires constant monitoring • 15m-1h: Day trading, check few times per session • 4h-Daily: Swing trading, check once or twice daily • Daily-Weekly: Position trading, check weekly General principle: Higher timeframes produce: • Fewer signals (less frequent) • Higher quality setups (stronger confirmations) • More reliable duration estimates (better statistical data) • Less noise (clearer trends) Start with Daily chart if new to trading. Move to lower timeframes as you gain experience. Q: Does this work on all markets (stocks, crypto, forex)? A: Yes, it works on all markets with trending characteristics: Excellent for: • Stocks (especially growth and momentum names) • Crypto (BTC, ETH, major altcoins) • Futures (indices, commodities) • Forex majors (EUR/USD, GBP/USD, etc.) Best results on: • Trending markets (not range-bound) • Liquid instruments (tight spreads, good fills) • Volatile assets (clear trend development) Less effective on: • Range-bound/sideways markets • Ultra-low volatility instruments • Illiquid small-caps (use caution) Configure Asset Type (in Advanced analysis mode) to match your instrument for best accuracy. Q: How many signals should I expect per day/week? A: Highly variable based on: By Timeframe: • 1-5 minute: 5-15 signals per session • 15m-1h: 2-5 signals per day • 4h-Daily: 2-5 signals per week • Daily-Weekly: 1-2 signals per month By Market Volatility: • High volatility = more SuperTrend flips = more signals • Low volatility = fewer flips = fewer signals By Quality Filter: • Higher threshold (60-70) = fewer but better signals • Lower threshold (30-40) = more signals, lower quality By Volume Momentum Filter: • Enabled = Fewer signals (only volume-confirmed) • Disabled = More signals (all SuperTrend flips) Adjust quality threshold and filters to match your desired signal frequency. Q: What's the difference between entry labels and info labels? A: Entry Labels (BUY/SELL): • Your primary trading signals • Based on SuperTrend flip + all confirmations (quality, volume, momentum) • Include quality score and confirmation icons • These are actionable entry points Info Labels (Volume Spike): • Additional market context • Show volume events that may support or contradict trend • 8-bar cooldown to prevent spam • NOT necessarily entry points - contextual information only Control separately: Can show entry labels without info labels (recommended for clean charts). Q: Can I combine this with other indicators? A: Absolutely! This works well with: • RSI: For divergences and overbought/oversold conditions • Support/Resistance: Confluence with key levels • Fibonacci Retracements: Pullback targets in Scalpel Mode • Price Action Patterns: Flags, pennants, cup-and-handle • MACD: Additional momentum confirmation • Bollinger Bands: Volatility context This indicator provides trend direction and duration estimates - complement with other tools for entry refinement and additional confluence. Q: Why did I get a low-quality signal? Can I filter them out? A: Yes! Increase the Minimum Quality Score in settings. If you're seeing signals with quality below your preference: • Day Trading: Set minimum to 50 • Swing Trading: Set minimum to 60 • Position Trading: Set minimum to 70 Only signals meeting the threshold will appear. This reduces frequency but improves win-rate. Q: How do I interpret the MTF Confluence count? A: Shows how many of 6 timeframes agree with current trend: • 6/6 aligned: Perfect agreement (extremely rare, highest confidence) • 5/6 aligned: Very strong alignment (high confidence) • 4/6 aligned: Good alignment (standard quality setup) • 3/6 aligned: Moderate alignment (acceptable) • 2/6 aligned: Weak alignment (caution) • 1/6 aligned: Very weak (likely counter-trend) Higher confluence typically correlates with longer, stronger trends. However, MTF analysis is optional - you can disable it and rely solely on quality scoring. Q: Is this suitable for beginners? A: Yes, but requires foundational knowledge: You should understand: • Basic trend-following concepts (higher highs, higher lows) • Risk management principles (position sizing, stop losses) • How to read candlestick charts • What volume and volatility mean Beginner-friendly features: • Auto preset mode (zero configuration) • Quality scoring (tells you signal strength) • Dashboard tooltips (hover for explanations) • duration analysis boxes (visual profit targets) Recommended for beginners: 1. Start with "Auto" or "Swing Trading" preset on Daily chart 2. Use Standard Analysis Mode (not Advanced) 3. Set minimum quality to 60 (fewer but better signals) 4. Paper trade first for 2-4 weeks 5. Study methodology references (Minervini, O'Neil, Zanger) Q: What is the Asset Type setting and why does it matter? A: Asset Type (in Advanced analysis mode) adjusts duration estimates based on volatility characteristics: • Small Cap: Explosive moves, extended trends (+30-40%) • Biotech / Speculative: Parabolic potential, news-driven (+40%) • Blue Chip / Large Cap: Baseline, steady trends (0% adjustment) • Tech Growth: Momentum-driven, longer trends (+20%) • Dividend / Value: Slower, grinding trends (-20%) • Cyclical: Macro-driven, variable (±10%) • Crypto / High Volatility: Parabolic potential (+30%) Correct configuration improves Statistical accuracy by 15-20%. Using Blue Chip settings on a biotech stock may underestimate trend length (you'll exit too early). Q: Can I backtest this indicator? A: Yes! TradingView's Strategy Tester works with this indicator's signals. To backtest: 1. Note the entry conditions (SuperTrend flip + quality threshold + filters) 2. Create a strategy script using same logic 3. Run Strategy Tester on historical data Additionally, the indicator includes BUILT-IN duration estimate validation: • System backtests its own duration estimates • Shows accuracy metrics in dashboard and duration analysis boxes • Helps assess reliability on your specific symbol/timeframe Q: Why does Volume Momentum auto-disable in Scalping mode? A: Scalping requires ultra-fast entries to catch quick moves. Volume Momentum filter adds friction by requiring volume confirmation before signaling, which can cause missed opportunities in rapid scalping. Scalping preset is optimized for speed and frequency - the filter is counterproductive for that style. It remains enabled for Day Trading, Swing Trading, and Position Trading presets where patience improves results. You can manually enable it in Custom mode if desired. Q: How much historical data do I need for accurate duration estimates? A: Minimum: 50-100 bars (indicator will function but duration estimates less reliable) Recommended: 500+ bars (robust statistical database) Optimal: 1000+ bars (maximum Statistical accuracy) More history = more completed trends = better pattern matching = more accurate duration estimates. New symbols or newly-switched timeframes will have lower Statistical accuracy initially. Allow 2-4 weeks for the system to build historical database. IMPORTANT DISCLAIMERS No Guarantee of Profit: This indicator is an educational tool and does not guarantee any specific trading results. All trading involves substantial risk of loss. Duration estimates are statistical calculations based on historical patterns and are not guarantees of future performance. Past Performance: Historical backtest results and Statistical accuracy statistics do not guarantee future performance. Market conditions change constantly. What worked historically may not work in current or future markets. Not Financial Advice: This indicator provides technical analysis signals and statistical duration estimates only. It is not financial, investment, or trading advice. Always consult with a qualified financial advisor before making investment decisions. Risk Warning: Trading stocks, options, futures, forex, and cryptocurrencies involves significant risk. You can lose all of your invested capital. Never trade with money you cannot afford to lose. Only risk capital you can lose without affecting your lifestyle. Testing Required: Always test this indicator on a demo account or with paper trading before risking real capital. Understand how it works in different market conditions. Verify Statistical accuracy on your specific instruments and timeframes before trusting it with real money. User Responsibility: You are solely responsible for your trading decisions. The developer assumes no liability for trading losses, incorrect duration estimates, software errors, or any other damages incurred while using this indicator. Statistical Estimation Limitations: Trend Duration estimates are statistical estimates based on historical pattern matching. They are NOT guarantees. Actual trend durations may differ significantly from duration estimates due to unforeseen news events, market regime changes, or lack of historical precedent for current conditions. CREDITS & ACKNOWLEDGMENTS Methodology Inspiration: • Mark Minervini - Volatility Contraction Pattern (VCP) concepts and pullback entry techniques • William O'Neil - Volume analysis principles and CANSLIM institutional buying patterns • Dan Zanger - Momentum breakout strategies and volatility expansion entries Technical Components: • SuperTrend calculation - Classic ATR-based trend indicator (public domain) • Statistical analysis - Standard median, average, range calculations • k-Nearest Neighbors - Classic machine learning similarity matching concept • Multi-timeframe analysis - Standard request.security implementation in Pine Script For questions, feedback, or support, please comment below or send a private message. Happy Trading!
Indicador Pine Script®
por orenluxy
30
Opening Range Breakout with Multi-Timeframe Liquidity]═══════════════════════════════════════ OPENING RANGE BREAKOUT WITH MULTI-TIMEFRAME LIQUIDITY ═══════════════════════════════════════ A professional Opening Range Breakout (ORB) indicator enhanced with multi-timeframe liquidity detection, trading session visualization, volume analysis, and trend confirmation tools. Designed for intraday trading with comprehensive alert system. ─────────────────────────────────────── WHAT THIS INDICATOR DOES ─────────────────────────────────────── This indicator combines multiple trading concepts: - Opening Range Breakout (ORB) - Customizable time period detection with automatic high/low identification - Multi-Timeframe Liquidity - HTF (Higher Timeframe) and LTF (Lower Timeframe) key level detection - Trading Sessions - Tokyo, London, New York, and Sydney session visualization - Volume Analysis - Volume spike detection and strength measurement - Multi-Timeframe Confirmation - Trend bias from higher timeframes - EMA Integration - Trend filter and dynamic support/resistance - Smart Alerts - Quality-filtered breakout notifications ─────────────────────────────────────── HOW IT WORKS ─────────────────────────────────────── OPENING RANGE BREAKOUT (ORB): Concept: The Opening Range is a period at the start of a trading session where price establishes an initial high and low. Breakouts beyond this range often indicate the direction of the day's trend. Detection Method: - Default: 15-minute opening range (configurable) - Custom Range: Set specific session times with timezone support - Automatically identifies ORH (Opening Range High) and ORL (Opening Range Low) - Tracks ORB mid-point for reference Range Establishment: 1. Session starts (or custom time begins) 2. Tracks highest high and lowest low during the period 3. Range confirmed at end of opening period 4. Levels extend throughout the session Breakout Detection: - Bullish Breakout: Close above ORH - Bearish Breakout: Close below ORL - Mid-point acts as bias indicator Visual Display: - Shaded box during range formation - Horizontal lines for ORH, ORL, and mid-point - Labels showing level values - Color-coded fills based on selected method Fill Color Methods: 1. Session Comparison: - Green: Current OR mid > Previous OR mid - Red: Current OR mid < Previous OR mid - Gray: Equal or first session - Shows day-over-day momentum 2. Breakout Direction (Recommended): - Green: Price currently above ORH (bullish breakout) - Red: Price currently below ORL (bearish breakout) - Gray: Price inside range (no breakout) - Real-time breakout status MULTI-TIMEFRAME LIQUIDITY: Two-Tier System for comprehensive level identification: HTF (Higher Timeframe) Key Liquidity: - Default: 4H timeframe (configurable to Daily, Weekly) - Identifies major institutional levels - Uses pivot detection with adjustable parameters - Suitable for swing highs/lows where large orders rest LTF (Lower Timeframe) Key Liquidity: - Default: 1H timeframe (configurable) - Provides precision entry/exit levels - Finer granularity for intraday trading - Captures minor swing points Calculation Method: - Pivot high/low detection algorithm - Configurable left bars (lookback) and right bars (confirmation) - Timeframe multiplier for accurate multi-timeframe detection - Automatic level extension Mitigation System: - Tracks when levels are swept (broken) - Configurable mitigation type: Wick or Close-based - Option to remove or show mitigated levels - Display limit prevents chart clutter Asset-Specific Optimization: The indicator includes quick reference settings for different assets: - Major Forex (EUR/USD, GBP/USD): Default settings optimal - Crypto (BTC/ETH): Left=12, Right=4, Display=7 - Gold: HTF=1D, Left=20 TRADING SESSIONS: Four Major Sessions with Full Customization: Tokyo Session: - Default: 04:00-13:00 UTC+4 - Asian trading hours - Often sets daily range London Session: - Default: 11:00-20:00 UTC+4 - Highest liquidity period - Major institutional activity New York Session: - Default: 16:00-01:00 UTC+4 - US market hours - High-impact news events Sydney Session: - Default: 01:00-10:00 UTC+4 - Earliest Asian activity - Lower volatility Session Features: - Shaded background boxes - Session name labels - Optional open/close lines - Session high/low tracking with colored lines - Each session has independent color settings - Fully customizable times and timezones VOLUME ANALYSIS: Volume-Based Trade Confirmation: Volume MA: - Configurable period (default: 20) - Establishes average volume baseline - Used for spike detection Volume Spike Detection: - Identifies when volume exceeds MA * multiplier - Default: 1.5x average volume - Confirms breakout strength Volume Strength Measurement: - Calculates current volume as percentage of average - Shows relative volume intensity - Used in alert quality filtering High Volume Bars: - Identifies bars above 50th percentile - Additional confirmation layer - Indicates institutional participation MULTI-TIMEFRAME CONFIRMATION: Trend Bias from Higher Timeframes: HTF 1 (Trend): - Default: 1H timeframe - Uses EMA to determine intermediate trend - Compares current timeframe EMA to HTF EMA HTF 2 (Bias): - Default: 4H timeframe - Uses 50 EMA for longer-term bias - Confirms overall market direction Bias Classifications: - Bullish Bias: HTF close > HTF 50 EMA AND Current EMA > HTF1 EMA - Bearish Bias: HTF close < HTF 50 EMA AND Current EMA < HTF1 EMA - Neutral Bias: Mixed signals between timeframes EMA Stack Analysis: - Compares EMA alignment across timeframes - +1: Bullish stack (lower TF EMA > higher TF EMA) - -1: Bearish stack (lower TF EMA < higher TF EMA) - 0: Neutral/crossed Usage: - Filters false breakouts - Confirms trend direction - Improves trade quality EMA INTEGRATION: Dynamic EMA for Trend Reference: Features: - Configurable period (default: 20) - Customizable color and width - Acts as dynamic support/resistance - Trend filter for ORB trades Application: - Above EMA: Favor long breakouts - Below EMA: Favor short breakouts - EMA cross: Potential trend change - Distance from EMA: Momentum gauge SMART ALERT SYSTEM: Quality-Filtered Breakout Notifications: Alert Types: 1. Standard ORB Breakout 2. High Quality ORB Breakout Quality Criteria: - Volume Confirmation: Volume > 1.2x average - MTF Confirmation: Bias aligned with breakout direction Standard Alert: - Basic breakout detection - Price crosses ORH or ORL - Icon: 🚀 (bullish) or 🔻 (bearish) High Quality Alert: - Both volume AND MTF confirmed - Stronger probability setup - Icon: 🚀⭐ (bullish) or 🔻⭐ (bearish) Alert Information Includes: - Alert quality rating - Breakout level and current price - Volume strength percentage (if enabled) - MTF bias status (if enabled) - Recommended action One Alert Per Bar: - Prevents alert spam - Uses flag system to track sent alerts - Resets on new ORB session ─────────────────────────────────────── HOW TO USE ─────────────────────────────────────── OPENING RANGE SETUP: Basic Configuration: 1. Select time period for opening range (default: 15 minutes) 2. Choose fill color method (Breakout Direction recommended) 3. Enable historical data display if needed Custom Range (Advanced): 1. Enable Custom Range toggle 2. Set specific session time (e.g., 0930-0945) 3. Select appropriate timezone 4. Useful for specific market opens (NYSE, LSE, etc.) LIQUIDITY LEVELS SETUP: Quick Configuration by Asset: - Forex: Use default settings (Left=15, Right=5) - Crypto: Set Left=12, Right=4, Display=7 - Gold: Set HTF=1D, Left=20 HTF Liquidity: - Purpose: Major support/resistance levels - Recommended: 4H for day trading, 1D for swing trading - Use as profit targets or reversal zones LTF Liquidity: - Purpose: Entry/exit refinement - Recommended: 1H for day trading, 4H for swing trading - Use for position management Mitigation Settings: - Wick-based: More sensitive (default) - Close-based: More conservative - Remove or Show mitigated levels based on preference TRADING SESSIONS SETUP: Enable/Disable Sessions: - Master toggle for all sessions - Individual session controls - Show/hide session names Session High/Low Lines: - Enable to see session extremes - Each session has custom colors - Useful for range trading Customization: - Adjust session times for your broker - Set timezone to match your location - Customize colors for visibility VOLUME ANALYSIS SETUP: Enable Volume Analysis: 1. Toggle on Volume Analysis 2. Set MA length (20 recommended) 3. Adjust spike multiplier (1.5 typical) Usage: - Confirm breakouts with volume - Identify climactic moves - Filter false signals MULTI-TIMEFRAME SETUP: HTF Selection: - HTF 1 (Trend): 1H for day trading, 4H for swing - HTF 2 (Bias): 4H for day trading, 1D for swing Interpretation: - Trade only with bias alignment - Neutral bias: Be cautious - Bias changes: Potential reversals EMA SETUP: Configuration: - Period: 20 for responsive, 50 for smoother - Color: Choose contrasting color - Width: 1-2 for visibility Usage: - Filter trades: Long above, Short below - Dynamic support/resistance reference - Trend confirmation ALERT SETUP: TradingView Alert Creation: 1. Enable alerts in indicator settings 2. Enable ORB Breakout Alerts 3. Right-click chart → Add Alert 4. Select this indicator 5. Choose "Any alert() function call" 6. Configure delivery method (mobile, email, webhook) Alert Filtering: - All alerts include quality rating - High Quality alerts = Volume + MTF confirmed - Standard alerts = Basic breakout only ─────────────────────────────────────── TRADING STRATEGIES ─────────────────────────────────────── CLASSIC ORB STRATEGY: Setup: 1. Wait for opening range to complete 2. Price breaks and closes above ORH or below ORL 3. Volume > average (if enabled) 4. MTF bias aligned (if enabled) Entry: - Bullish: Buy on break above ORH - Bearish: Sell on break below ORL - Consider retest entries for better risk/reward Stop Loss: - Bullish: Below ORL or range mid-point - Bearish: Above ORH or range mid-point - Adjust based on volatility Targets: - Initial: Range width extension (ORH + range width) - Secondary: HTF liquidity levels - Final: Session high/low or major support/resistance ORB + LIQUIDITY CONFLUENCE: Enhanced Setup: 1. Opening range established 2. HTF liquidity level near or beyond ORH/ORL 3. Breakout occurs with volume 4. Price targets the liquidity level Entry: - Enter on ORB breakout - Target the HTF liquidity level - Use LTF liquidity for position management Management: - Partial profits at ORB + range width - Move stop to breakeven at LTF liquidity - Final exit at HTF liquidity sweep ORB REJECTION STRATEGY (Counter-Trend): Setup: 1. Price breaks above ORH or below ORL 2. Weak volume (below average) 3. MTF bias opposite to breakout 4. Price closes back inside range Entry: - Failed bullish break: Short below ORH - Failed bearish break: Long above ORL Stop Loss: - Beyond the failed breakout level - Or beyond session extreme Target: - Opposite end of opening range - Range mid-point for partial profit SESSION-BASED ORB TRADING: Tokyo Session: - Typically narrower ranges - Good for range trading - Wait for London open breakout London Session: - Highest volume and volatility - Strong ORB setups - Major liquidity sweeps common New York Session: - Strong trending moves - News-driven volatility - Good for momentum trades Sydney Session: - Quieter conditions - Suitable for range strategies - Sets up Tokyo session EMA-FILTERED ORB: Rules: - Only take bullish breaks if price > EMA - Only take bearish breaks if price < EMA - Ignore counter-trend breaks Benefits: - Reduces false signals - Aligns with larger trend - Improves win rate ─────────────────────────────────────── CONFIGURATION GUIDE ─────────────────────────────────────── OPENING RANGE SETTINGS: Time Period: - 15 min: Standard for most markets - 30 min: Wider range, fewer breakouts - 60 min: For slower markets or swing trades Custom Range: - Use for specific market opens - NYSE: 0930-1000 EST - LSE: 0800-0830 GMT - Set timezone to match exchange Historical Display: - Enable: See all previous session data - Disable: Cleaner chart, current session only LIQUIDITY SETTINGS: Left Bars (5-30): - Lower: More frequent, sensitive levels - Higher: Fewer, more significant levels - Recommended: 15 for most markets Right Bars (1-25): - Confirmation period - Higher: More reliable, less frequent - Recommended: 5 for balance Display Limit (1-20): - Number of active levels shown - Higher: More context, busier chart - Recommended: 7 for clarity Extension Options: - Short: Levels visible near formation - Current: Extended to current bar (recommended) - Max: Extended indefinitely VOLUME SETTINGS: MA Length (5-50): - Shorter: More responsive to spikes - Longer: Smoother baseline - Recommended: 20 for balance Spike Multiplier (1.0-3.0): - Lower: More sensitive spike detection - Higher: Only extreme spikes - Recommended: 1.5 for day trading MULTI-TIMEFRAME SETTINGS: HTF 1 (Trend): - 5m chart: Use 15m or 1H - 15m chart: Use 1H or 4H - 1H chart: Use 4H or 1D HTF 2 (Bias): - One level higher than HTF 1 - Provides longer-term context - Don't use same as HTF 1 EMA SETTINGS: Length: - 20: Responsive, more signals - 50: Smoother, stronger filter - 200: Long-term trend only Style: - Choose contrasting color - Width 1-2 for visibility - Match your trading style ─────────────────────────────────────── BEST PRACTICES ─────────────────────────────────────── Chart Timeframe Selection: - ORB Trading: Use 5m or 15m charts - Session Review: Use 1H or 4H charts - Swing Trading: Use 1H or 4H charts Quality Over Quantity: - Wait for high-quality alerts (volume + MTF) - Avoid trading every breakout - Focus on confluence setups Risk Management: - Position size based on range width - Wider ranges = smaller positions - Use stop losses always - Take partial profits at targets Market Conditions: - Best results in trending markets - Reduce position size in choppy conditions - Consider session overlaps for volatility - Avoid trading near major news if inexperienced Continuous Improvement: - Track win rate by session - Note which confluence factors work best - Adjust settings based on market volatility - Review performance weekly ─────────────────────────────────────── PERFORMANCE OPTIMIZATION ─────────────────────────────────────── This indicator is optimized with: - max_bars_back declarations for efficient processing - Conditional calculations based on enabled features - Proper memory management for drawing objects - Minimal recalculation on each bar Best Practices: - Disable unused features (sessions, MTF, volume) - Limit historical display to reduce rendering - Use appropriate timeframe for your strategy - Clear old drawing objects periodically ─────────────────────────────────────── EDUCATIONAL DISCLAIMER ─────────────────────────────────────── This indicator combines established trading concepts: - Opening Range Breakout theory (price action) - Liquidity level detection (pivot analysis) - Session-based trading (time-of-day patterns) - Volume analysis (confirmation technique) - Multi-timeframe analysis (trend alignment) All calculations use standard technical analysis methods: - Pivot high/low detection algorithms - Moving averages for trend and volume - Session time filtering - Timeframe security functions The indicator identifies potential trading setups but does not predict future price movements. Success requires proper application within a complete trading strategy including risk management, position sizing, and market context. ─────────────────────────────────────── USAGE DISCLAIMER ─────────────────────────────────────── This tool is for educational and analytical purposes. Opening Range Breakout trading involves substantial risk. The alert system and quality filters are designed to identify potential setups but do not guarantee profitability. Always conduct independent analysis, use proper risk management, and never risk capital you cannot afford to lose. Past performance does not indicate future results. Trading intraday breakouts requires experience and discipline. ─────────────────────────────────────── CREDITS & ATTRIBUTION ─────────────────────────────────────── ORIGINAL SOURCE: This indicator builds upon concepts from LuxAlgo's-ORB
Indicador Pine Script®
por Fx-Jithin
SMC Analysis - Fair Value Gaps (Enhanced)SMC Analysis - Fair Value Gaps (Enhanced) Script Summary Overview The "SMC Analysis - Fair Value Gaps (Enhanced)" script, written in Pine Script (version 6), is a technical analysis indicator designed for TradingView to identify and visualize Fair Value Gaps (FVGs) on a price chart. It supports both the main timeframe and multiple higher timeframes (MTF) for comprehensive market analysis. FVGs are price gaps formed by a three-candle pattern, indicating potential areas of market inefficiency where price may return to fill the gap. Key Features FVG Detection: Identifies bullish FVGs: Occur when the high of a candle two bars prior is lower than the low of the current candle, with the middle candle being bullish (close > open). Identifies bearish FVGs: Occur when the low of a candle two bars prior is higher than the high of the current candle, with the middle candle being bearish (close < open). Visualizes FVGs as colored boxes on the chart (green for bullish, red for bearish). Mitigation Tracking: Tracks when FVGs are touched (price overlaps the gap range) or mitigated (price fully closes the gap). Strict Mode: Marks an FVG as mitigated when price touches the gap range. Normal Mode: Requires a full breakthrough (price crossing the gap’s bottom for bullish FVGs or top for bearish FVGs) for mitigation. Optionally converts FVG box borders to dashed lines and increases transparency when partially touched. Multi-Timeframe (MTF) Support: Analyzes FVGs on three user-defined higher timeframes (default: 15m, 60m, 240m). Displays MTF FVGs with distinct labels and slightly more transparent colors. Ensures no duplicate processing of MTF bars to maintain performance. Customization Options: FVG Length: Adjustable duration for how long FVGs are displayed (default: 20 bars). Show/Hide FVGs: Toggle visibility for main timeframe and each MTF. Color Customization: User-defined colors for bullish and bearish FVGs (default: green and red). Display Options: Toggle for showing dashed lines after partial touches and strict mitigation mode. Performance Optimization: Limits the number of displayed boxes (50 for main timeframe, 20 per MTF) to prevent performance issues. Automatically removes older boxes to maintain a clean chart. Functionality Visualization: Draws boxes around detected FVGs, with customizable colors and text labels ("FVG" for main timeframe, "FVG " for MTF). Dynamic Updates: Extends or terminates FVG boxes based on mitigation status and user settings. Efficient Storage: Uses arrays to manage FVG data (boxes, tops, bottoms, indices, mitigation status, and touch status) separately for main and MTF analyses. Use Case This indicator is designed for traders using Smart Money Concepts (SMC) to identify areas of market inefficiency (FVGs) for potential price reversals or continuations. The MTF support allows analysis across different timeframes, aiding in confirming trends or spotting higher-timeframe support/resistance zones.
Indicador Pine Script®
por osterhansi_
SuperTrend Cyan — Split ST & Triple Bands (A/B/C)SuperTrend Cyan — Split ST & Triple Bands (A/B/C) ✨ Concept: The SuperTrend Cyan indicator expands the classical SuperTrend logic into a split-line + triple-band visualization for clearer structure and volatility mapping. Instead of a single ATR-based line, this tool separates SuperTrend direction from volatility envelopes (A/B/C), providing a layered view of both regime and range compression. ✨ The design goal: Preserve the simplicity of SuperTrend Add volatility context via multi-band envelopes Provide a compact MTF (Multi-Timeframe) summary for broader trend alignment ✨ How It Works 1. SuperTrend Core (Active & Opposite Lines) Uses ATR-based bands (Factor × ATR-Length). Active SuperTrend is plotted according to current regime. Opposite SuperTrend (optional) shows potential reversal threshold. 2. Triple Band System (A/B/C) Each band (A, B, C) scales from the median price (hl2) by different ATR multipliers. A: Outer band (wider, long-range context) B: Inner band (mid-range activity) C: Core band (closest to price, short-term compression) Smoothness can be controlled with EMA. Uptrend fills are lime-toned, downtrend fills are red-toned, with adjustable opacity (gap intensity). 3. Automatic Directional Switch When the regime flips from up → down (or vice versa), the overlay automatically switches between lower and upper bands for a clean transition. 4. Multi-Timeframe SuperTrend Table Displays SuperTrend direction across 5m, 15m, 1h, 4h, and 1D frames. Green ▲ = Uptrend, Red ▼ = Downtrend. Useful for checking cross-timeframe trend alignment. ✨ How to Read It Green SuperTrend + Lime Bands - Uptrend regime; volatility expanding upward Red SuperTrend + Red Bands - Downtrend regime; volatility expanding downward Narrow gaps (A–C) - Low volatility / compression (potential squeeze) Wide gaps - High volatility / active trend phase Opposite ST line close to price - Early warning for regime transition ✨ Practical Use Identify trend direction (SuperTrend color & line position). Assess volatility conditions (band width and gap transparency). Watch for MTF alignment: consistent up/down signals across 1h–4h–1D = strong structural trend. Combine with momentum indicators (e.g., RSI, DFI, PCI) for confirmation of trend maturity or exhaustion. ✨ Customization Tips ST Factor / ATR Length - Adjust sensitivity of SuperTrend direction changes Band ATR Length - Controls overall smoothness of volatility envelopes Band Multipliers (A/B/C) - Define how wide each volatility band extends Gap Opacity - Affects visual contrast between layers MTF Table - Enable/disable multi-timeframe display ✨ Educational Value This script visualizes the interaction between trend direction (SuperTrend) and volatility envelopes, helping traders understand how price reacts within layered ATR zones. It also introduces a clean MTF (multi-timeframe) perspective — ideal for discretionary and system traders alike. ✨ Disclaimer This indicator is provided for educational and research purposes only. It does not constitute financial advice or a trading signal. Use at your own discretion and always confirm with additional tools. ─────────────────────────────── 📘 한국어 설명 (Korean translation below) ─────────────────────────────── ✨개념 SuperTrend Cyan 지표는 기존의 SuperTrend를 확장하여, 추세선 분리(Split Line) + 3중 밴드 시스템(Triple Bands) 으로 시장의 구조적 흐름과 변동성 범위를 동시에 시각화합니다. 단순한 SuperTrend의 강점을 유지하면서도, ATR 기반의 A/B/C 밴드를 통해 변동성 압축·확장 구간을 직관적으로 파악할 수 있습니다. ✨ 작동 방식 1. SuperTrend 코어 (활성/반대 라인) ATR×Factor를 기반으로 추세선을 계산합니다. 현재 추세 방향에 따라 활성 라인이 표시되고, “Show Opposite” 옵션을 켜면 반대편 경계선도 함께 보입니다. 2. 트리플 밴드 시스템 (A/B/C) hl2(중간값)를 기준으로 ATR 배수에 따라 세 개의 밴드를 계산합니다. A: 외곽 밴드 (가장 넓고 장기 구조 반영) B: 중간 밴드 (중기적 움직임) C: 코어 밴드 (가격에 가장 근접, 단기 변동성 반영) EMA 스무딩으로 부드럽게 조정 가능. 업트렌드 구간은 라임색, 다운트렌드는 빨간색 음영으로 표시됩니다. 3. 자동 전환 시스템 추세가 전환될 때(Up ↔ Down), 밴드 오버레이도 자동으로 교체되어 깔끔한 시각적 구조를 유지합니다. 4. MTF SuperTrend 테이블 5m / 15m / 1h / 4h / 1D 프레임별 SuperTrend 방향을 표시합니다. 초록 ▲ = 상승, 빨강 ▼ = 하락. 복수 타임프레임 정렬 확인용으로 유용합니다. ✨ 해석 방법 초록 SuperTrend + 라임 밴드 - 상승 추세 및 확장 구간 빨강 SuperTrend + 레드 밴드 - 하락 추세 및 확장 구간 밴드 폭이 좁음 - 변동성 축소 (스퀴즈) 밴드 폭이 넓음 - 변동성 확장, 추세 강화 반대선이 근접 - 추세 전환 가능성 높음 ✨ 활용 방법 SuperTrend 색상으로 추세 방향을 확인 A/B/C 밴드 폭으로 변동성 수준을 판단 MTF 테이블을 통해 복수 타임프레임 정렬 여부 확인 RSI, DFI, PCI 등 다른 지표와 함께 활용 시, 추세 피로·모멘텀 변화를 조기에 파악 가능 ✨ 교육적 가치 이 스크립트는 추세 구조(SuperTrend) 와 변동성 레이어(ATR Bands) 의 상호작용을 시각적으로 학습하기 위한 교육용 지표입니다. 또한, MTF 구조를 통해 시장의 “위계적 정렬(hierarchical alignment)”을 쉽게 인식할 수 있습니다. ✨ 면책 이 지표는 교육 및 연구 목적으로만 제공됩니다. 투자 판단의 책임은 사용자 본인에게 있으며, 본 지표는 매매 신호를 보장하지 않습니다.
Indicador Pine Script®
por Cyan_TPM
1
Extreme Pressure Zones Indicator (EPZ) [BullByte]Extreme Pressure Zones Indicator(EPZ) The Extreme Pressure Zones (EPZ) Indicator is a proprietary market analysis tool designed to highlight potential overbought and oversold "pressure zones" in any financial chart. It does this by combining several unique measurements of price action and volume into a single, bounded oscillator (0–100). Unlike simple momentum or volatility indicators, EPZ captures multiple facets of market pressure: price rejection, trend momentum, supply/demand imbalance, and institutional (smart money) flow. This is not a random mashup of generic indicators; each component was chosen and weighted to reveal extreme market conditions that often precede reversals or strong continuations. What it is? EPZ estimates buying/selling pressure and highlights potential extreme zones with a single, bounded 0–100 oscillator built from four normalized components. Context-aware weighting adapts to volatility, trendiness, and relative volume. Visual tools include adaptive thresholds, confirmed-on-close extremes, divergence, an MTF dashboard, and optional gradient candles. Purpose and originality (not a mashup) Purpose: Identify when pressure is building or reaching potential extremes while filtering noise across regimes and symbols. Originality: EPZ integrates price rejection, momentum cascade, pressure distribution, and smart money flow into one bounded scale with context-aware weighting. It is not a cosmetic mashup of public indicators. Why a trader might use EPZ EPZ provides a multi-dimensional gauge of market extremes that standalone indicators may miss. Traders might use it to: Spot Reversals: When EPZ enters an "Extreme High" zone (high red), it implies selling pressure might soon dominate. This can hint at a topside reversal or at least a pause in rallies. Conversely, "Extreme Low" (green) can highlight bottom-fish opportunities. The indicator's divergence module (optional) also finds hidden bullish/bearish divergences between price and EPZ, a clue that price momentum is weakening. Measure Momentum Shifts: Because EPZ blends momentum and volume, it reacts faster than many single metrics. A rising MPO indicates building bullish pressure, while a falling MPO shows increasing bearish pressure. Traders can use this like a refined RSI: above 50 means bullish bias, below 50 means bearish bias, but with context provided by the thresholds. Filter Trades: In trend-following systems, one could require EPZ to be in the bullish (green) zone before taking longs, or avoid new trades when EPZ is extreme. In mean-reversion systems, one might specifically look to fade extremes flagged by EPZ. Multi-Timeframe Confirmation: The dashboard can fetch a higher timeframe EPZ value. For example, you might trade a 15-minute chart only when the 60-minute EPZ agrees on pressure direction. Components and how they're combined Rejection (PRV) – Captures price rejection based on candle wicks and volume (see Price Rejection Volume). Momentum Cascade (MCD) – Blends multiple momentum periods (3,5,8,13) into a normalized momentum score. Pressure Distribution (PDI) – Measures net buy/sell pressure by comparing volume on up vs down candles. Smart Money Flow (SMF) – An adaptation of money flow index that emphasizes unusual volume spikes. Each of these components produces a 0–100 value (higher means more bullish pressure). They are then weighted and averaged into the final Market Pressure Oscillator (MPO), which is smoothed and scaled. By combining these four views, EPZ stands out as a comprehensive pressure gauge – the whole is greater than the sum of parts Context-aware weighting: Higher volatility → more PRV weight Trendiness up (RSI of ATR > 25) → more MCD weight Relative volume > 1.2x → more PDI weight SMF holds a stable weight The weighted average is smoothed and scaled into MPO ∈ with 50 as the neutral midline. What makes EPZ stand out Four orthogonal inputs (price action, momentum, pressure, flow) unified in a single bounded oscillator with consistent thresholds. Adaptive thresholds (optional) plus robust extreme detection that also triggers on crossovers, so static thresholds work reliably too. Confirm Extremes on Bar Close (default ON): dots/arrows/labels/alerts print on closed bars to avoid repaint confusion. Clean dashboard, divergence tools, pre-alerts, and optional on-price gradients. Visual 3D layering uses offsets for depth only,no lookahead. Recommended markets and timeframes Best: liquid symbols (index futures, large-cap equities, major FX, BTC/ETH). Timeframes: 5–15m (more signals; consider higher thresholds), 1H–4H (balanced), 1D (clear regimes). Use caution on illiquid or very low TFs where wick/volume geometry is erratic. Logic and thresholds MPO ∈ ; 50 = neutral. Above 50 = bullish pressure; below 50 = bearish. Static thresholds (defaults): thrHigh = 70, thrLow = 30; warning bands 5 pts inside extremes (65/35). Adaptive thresholds (optional): thrHigh = min(BaseHigh + 5, mean(MPO,100) + stdev(MPO,100) × ExtremeSensitivity) thrLow = max(BaseLow − 5, mean(MPO,100) − stdev(MPO,100) × ExtremeSensitivity) Extreme detection High: MPO ≥ thrHigh with peak/slope or crossover filter. Low: MPO ≤ thrLow with trough/slope or crossover filter. Cooldown: 5 bars (default). A new extreme will not print until the cooldown elapses, even if MPO re-enters the zone. Confirmation "Confirm Extremes on Bar Close" (default ON) gates extreme markers, pre-alerts, and alerts to closed bars (non-repainting). Divergences Pivot-based bullish/bearish divergence; tags appear only after left/right bars elapse (lookbackPivot). MTF HTF MPO retrieved with lookahead_off; values can update intrabar and finalize at HTF close. This is disclosed and expected. Inputs and defaults (key ones) Core: Sensitivity=1.0; Analysis Period=14; Smoothing=3; Adaptive Thresholds=OFF. Extremes: Base High=70, Base Low=30; Extreme Sensitivity=1.5; Confirm Extremes on Bar Close=ON; Cooldown=5; Dot size Small/Tiny. Visuals: Heatmap ON; 3D depth optional; Strength bars ON; Pre-alerts OFF; Divergences ON with tags ON; Gradient candles OFF; Glow ON. Dashboard: ON; Position=Top Right; Size=Normal; MTF ON; HTF=60m; compact overlay table on price chart. Advanced caps: Max Oscillator Labels=80; Max Extreme Guide Lines=80; Divergence objects=60. Dashboard: what each element means Header: EPZ ANALYSIS. Large readout: Current MPO; color reflects state (extreme, approaching, or neutral). Status badge: "Extreme High/Low", "Approaching High/Low", "Bullish/Neutral/Bearish". HTF cell (when MTF ON): Higher-timeframe MPO, color-coded vs extremes; updates intrabar, settles at HTF close. Predicted (when MTF OFF): Simple MPO extrapolation using momentum/acceleration—illustrative only. Thresholds: Current thrHigh/thrLow (static or adaptive). Components: ASCII bars + values for PRV, MCD, PDI, SMF. Market metrics: Volume Ratio (x) and ATR% of price. Strength: Bar indicator of |MPO − 50| × 2. Confidence: Heuristic gauge (100 in extremes, 70 in warnings, 50 with divergence, else |MPO − 50|). Convenience only, not probability. How to read the oscillator MPO Value (0–100): A reading of 50 is neutral. Values above ~55 are increasingly bullish (green), while below ~45 are increasingly bearish (red). Think of these as "market pressure". Extreme Zones: When MPO climbs into the bright orange/red area (above the base-high line, default 70), the chart will display a dot and downward arrow marking that extreme. Traders often treat this as a sign to tighten stops or look for shorts. Similarly, a bright green dot/up-arrow appears when MPO falls below the base-low (30), hinting at a bullish setup. Heatmap/Candles: If "Pressure Heatmap" is enabled, the background of the oscillator pane will fade green or red depending on MPO. Users can optionally color the price candles by MPO value (gradient candles) to see these extremes on the main chart. Prediction Zone(optional): A dashed projection line extends the MPO forward by a small number of bars (prediction_bars) using current MPO momentum and acceleration. This is a heuristic extrapolation best used for short horizons (1–5 bars) to anticipate whether MPO may touch a warning or extreme zone. It is provisional and becomes less reliable with longer projection lengths — always confirm predicted moves with bar-close MPO and HTF context before acting. Divergences: When price makes a higher high but EPZ makes a lower high (bearish divergence), the indicator can draw dotted lines and a "Bear Div" tag. The opposite (lower low price, higher EPZ) gives "Bull Div". These signals confirm waning momentum at extremes. Zones: Warning bands near extremes; Extreme zones beyond thresholds. Crossovers: MPO rising through 35 suggests easing downside pressure; falling through 65 suggests waning upside pressure. Dots/arrows: Extreme markers appear on closed bars when confirmation is ON and respect the 5-bar cooldown. Pre-alert dots (optional): Proximity cues in warning zones; also gated to bar close when confirmation is ON. Histogram: Distance from neutral (50); highlights strengthening or weakening pressure. Divergence tags: "Bear Div" = higher price high with lower MPO high; "Bull Div" = lower price low with higher MPO low. Pressure Heatmap : Layered gradient background that visually highlights pressure strength across the MPO scale; adjustable intensity and optional zone overlays (warning / extreme) for quick visual scanning. A typical reading: If the oscillator is rising from neutral towards the high zone (green→orange→red), the chart may see strong buying culminating in a stall. If it then turns down from the extreme, that peak EPZ dot signals sell pressure. Alerts EPZ: Extreme Context — fires on confirmed extremes (respects cooldown). EPZ: Approaching Threshold — fires in warning zones if no extreme. EPZ: Divergence — fires on confirmed pivot divergences. Tip: Set alerts to "Once per bar close" to align with confirmation and avoid intrabar repaint. Practical usage ideas Trend continuation: In positive regimes (MPO > 50 and rising), pullbacks holding above 50 often precede continuation; mirror for bearish regimes. Exhaustion caution: E High/E Low can mark exhaustion risk; many wait for MPO rollover or divergence to time fades or partial exits. Adaptive thresholds: Useful on assets with shifting volatility regimes to maintain meaningful "extreme" levels. MTF alignment: Prefer setups that agree with the HTF MPO to reduce countertrend noise. Examples Screenshots captured in TradingView Replay to freeze the bar at close so values don't fluctuate intrabar. These examples use default settings and are reproducible on the same bars; they are for illustration, not cherry-picking or performance claims. Example 1 — BTCUSDT, 1h — E Low MPO closed at 26.6 (below the 30 extreme), printing a confirmed E Low. HTF MPO is 26.6, so higher-timeframe pressure remains bearish. Components are subdued (Momentum/Pressure/Smart$ ≈ 29–37), with Vol Ratio ≈ 1.19x and ATR% ≈ 0.37%. A prior Bear Div flagged weakening impulse into the drop. With cooldown set to 5 bars, new extremes are rate-limited. Many traders wait for MPO to curl up and reclaim 35 or for a fresh Bull Div before considering countertrend ideas; if MPO cannot reclaim 35 and HTF stays weak, treat bounces cautiously. Educational illustration only. Example 2 — ETHUSD, 30m — E High A strong impulse pushed MPO into the extreme zone (≥ 70), printing a confirmed E High on close. Shortly after, MPO cooled to ~61.5 while a Bear Div appeared, showing momentum lag as price pushed a higher high. Volume and volatility were elevated (≈ 1.79x / 1.25%). With a 5-bar cooldown, additional extremes won't print immediately. Some treat E High as exhaustion risk—either waiting for MPO rollover under 65/50 to fade, or for a pullback that holds above 50 to re-join the trend if higher-timeframe pressure remains constructive. Educational illustration only. Known limitations and caveats The MPO line itself can change intrabar; extreme markers/alerts do not repaint when "Confirm Extremes on Bar Close" is ON. HTF values settle at the close of the HTF bar. Illiquid symbols or very low TFs can be noisy; consider higher thresholds or longer smoothing. Prediction line (when enabled) is a visual extrapolation only. For coders Pine v6. MTF via request.security with lookahead_off. Extremes include crossover triggers so static thresholds also yield E High/E Low. Extreme markers and pre-alerts are gated by barstate.isconfirmed when confirmation is ON. Arrays prune oldest objects to respect resource limits; defaults (80/80/60) are conservative for low TFs. 3D layering uses negative offsets purely for drawing depth (no lookahead). Screenshot methodology: To make labels legible and to demonstrate non-repainting behavior, the examples were captured in TradingView Replay with "Confirm Extremes on Bar Close" enabled. Replay is used only to freeze the bar at close so plots don't change intrabar. The examples use default settings, include both Extreme Low and Extreme High cases, and can be reproduced by scrolling to the same bars outside Replay. This is an educational illustration, not a performance claim. Disclaimer This script is for educational purposes only and does not constitute financial advice. Markets involve risk; past behavior does not guarantee future results. You are responsible for your own testing, risk management, and decisions.
Indicador Pine Script®
por BullByte
18
DynamoSent DynamoSent Pro+ — Professional Listing (Preview) — Adaptive Macro Sentiment (v6) — Export, Adaptive Lookback, Confidence, Boxes, Heatmap + Dynamic OB/OS Preview / Experimental build. I’m actively refining this tool—your feedback is gold. If you spot edge cases, want new presets, or have market-specific ideas, please comment or DM me on TradingView. ⸻ What it is DynamoSent Pro+ is an adaptive, non-repainting macro sentiment engine that compresses VIX, DXY and a price-based activity proxy (e.g., SPX/sector ETF/your symbol) into a 0–100 sentiment line. It scales context by volatility (ATR%) and can self-calibrate with rolling quantile OB/OS. On top of that, it adds confidence scoring, a plain-English Context Coach, MTF agreement, exportable sentiment for other indicators, and a clean Light/Dark UI. Why it’s different • Adaptive lookback tracks regime changes: when volatility rises, we lengthen context; when it falls, we shorten—less whipsaw, more relevance. • Dynamic OB/OS (quantiles) self-calibrates to each instrument’s distribution—no arbitrary 30/70 lines. • MTF agreement + Confidence gate reduce false positives by highlighting alignment across timeframes. • Exportable output: hidden plot “DynamoSent Export” can be selected as input.source in your other Pine scripts. • Non-repainting rigor: all request.security() calls use lookahead_off + gaps_on; signals wait for bar close. Key visuals • Sentiment line (0–100), OB/OS zones (static or dynamic), optional TF1/TF2 overlays. • Regime boxes (Overbought / Oversold / Neutral) that update live without repaint. • Info Panel with confidence heat, regime, trend arrow, MTF readout, and Coach sentence. • Session heat (Asia/EU/US) to match intraday behavior. • Light/Dark theme switch in Inputs (auto-contrasted labels & headers). ⸻ How to use (examples & recipes) 1) EURUSD (swing / intraday blend) • Preset: EURUSD 1H Swing • Chart: 1H; TF1=1H, TF2=4H (default). • Proxies: Defaults work (VIX=D, DXY=60, Proxy=D). • Dynamic OB/OS: ON at 20/80; Confidence ≥ 55–60. • Playbook: • When sentiment crosses above 50 + margin with Δ ≥ signalK and MTF agreement ≥ 0.5, treat as trend breakout. • In Oversold with rising Coach & TF agreement, take fade longs back toward mid-range. • Alerts: Enable Breakout Long/Short and Fade; keep cooldown 8–12 bars. 2) SPY (daytrading) • Preset: SPY 15m Daytrade; Chart: 15m. • VIX (D) matters more; preset weights already favor it. • Start with static 30/70; later try dynamic 25/75 for adaptive thresholds. • Use Coach: in US session, when it says “Overbought + MTF agree → sell rallies / chase breakouts”, lean momentum-continuation after pullbacks. 3) BTCUSD (crypto, 24/7) • Preset: BTCUSD 1H; Chart: 1H. • DXY and BTC.D inform macro tone; keep Carry-forward ON to bridge sparse ticks. • Prefer Dynamic OB/OS (15/85) for wider swings. • Fade signals on weekend chop; Breakout when Confidence > 60 and MTF ≥ 1.0. 4) XAUUSD (gold, macro blend) • Preset: XAUUSD 4H; Chart: 4H. • Weights tilt to DXY and US10Y (handled by preset). • Coach + MTF helps separate trend legs from news pops. ⸻ Best practices • Theme: Switch Light/Dark in Inputs; the panel adapts contrast automatically. • Export: In another script → Source → DynamoSent Pro+ → DynamoSent Export. Build your own filters/strategies atop the same sentiment. • Dynamic vs Static OB/OS: • Static 30/70: fast, universal baseline. • Dynamic (quantiles): instrument-aware; use 20/80 (default) or 15/85 for choppy markets. • Confidence gate: Start at 50–60% to filter noise; raise when you want only A-grade setups. • Adaptive Lookback: Keep ON. For ultra-liquid indices, you can switch it OFF and set a fixed lookback. ⸻ Non-repainting & safety notes • All request.security() calls use lookahead=barmerge.lookahead_off and gaps=barmerge.gaps_on. • No forward references; signals & regime flips are confirmed on bar close. • History-dependent funcs (ta.change, ta.percentile_linear_interpolation, etc.) are computed each bar (not conditionally). • Adaptive lookback is clamped ≥ 1 to avoid lowest/highest errors. • Missing-data warning triggers only when all proxies are NA for a streak; carry-forward can bridge small gaps without repaint. ⸻ Known limits & tips • If a proxy symbol isn’t available on your plan/exchange, you’ll see the NA warning: choose a different symbol via Symbol Search, or keep Carry-forward ON (it defaults to neutral where needed). • Intraday VIX is sparse—using Daily is intentional. • Dynamic OB/OS needs enough history (see dynLenFloor). On short histories it gracefully falls back to static levels. Thanks for trying the preview. Your comments drive the roadmap—presets, new proxies, extra alerts, and integrations.
Indicador Pine Script®
por ACTradeFIN
CCI Stochastic - YOSI CCI Stochastic (Pro v6) – MTF, Adaptive Bands & Live Label What it does This indicator applies a Stochastic calculation on the CCI (K/D lines) to highlight momentum shifts, overbought/oversold zones, and adaptive market regimes. It comes with optional higher-timeframe confirmation, adaptive volatility bands, a live value label, and built-in alerts. Key Features Core Signal: Choose between D or K line of the Stoch-CCI. Extreme Zones: Customizable OB/OS thresholds (default 80/20) and a midline (50), with dynamic background shading. Adaptive Bands (optional): Mean ± k·standard deviation of the signal, to capture cyclic extremes. MTF Confirmation (optional): Fetches the same signal from a higher timeframe via request.security. Arrows/Signals: Enter – Cross above OS (Buy) / below OB (Sell). Center – Cross of the 50 midline (momentum shift). Exit – Exit from extreme zones. Alerts: All arrow signals + adaptive band crosses. Live Value Label: Shows the latest signal value near the last bar, customizable decimals/offset/background colors. Visuals: Red line above OB, green below OS, gray neutral; adaptive band fills. Use Cases Momentum / Reversals: Enter with OS/OB crosses confirmed by MTF. Trend validation: Combine with moving averages (e.g., EMA200) or support/resistance. Mean Reversion: Fade extreme zones, especially with adaptive band or OB/OS exit alerts. Inputs CCI Period, Stoch Period, Smooth K/D – core calculation. Overbought / Oversold – thresholds (default 80/20). Line to plot – K or D. Show Arrows (Enter, Center, Exit) – visual control. Adaptive Bands – length and k multiplier. Higher TF – optional confirmation timeframe. Live Label – decimals, offset, colors. Quick Tips For scalping/short-term setups: tighten OB/OS (e.g., 85/15) to filter noise. In high volatility: increase adaptLen or decrease k to smooth bands. Reduce false signals: require local + MTF alignment (e.g., only long if MTF > 50). Disclaimer This is a technical analysis tool – not a standalone buy/sell signal. Always use with proper risk management, key levels, and confluence from multiple factors. מה זה עושה? האינדיקטור מחשב Stochastic על CCI (קו K/D) ומציג אזורי קיצון, חציות ומשטרי שוק. הוא כולל אופציה לאישור מטיימפריים גבוה, בנדים אדפטיביים, תווית ערך חיה והתרעות מוכנות. יכולות עיקריות סיגנל מרכזי: בחירה בין קו D או K של Stoch-CCI. אזורי קיצון: קווים ניתנים להגדרה (ברירת מחדל 80/20) וקו אמצע 50, עם צביעת רקע דינמית כשנכנסים לקיצון. Adaptive Bands (אופציונלי): ממוצע ± ‎k·סטיית תקן של הסיגנל—מסייע לזהות overheat ומחזוריות. אישור MTF (אופציונלי): אותו סיגנל מטיימפריים גבוה באמצעות request.security. חיצים/סיגנלים: Enter – חציה מלמטה מעל OS (קנייה) / מלמעלה מתחת OB (מכירה). Center – חציה של 50 (שינוי מומנטום). Exit – יציאה מאזורים קיצוניים (OS/OB). Alerts: לכל הסיגנלים לעיל + כניסה/יציאה לבנדים האדפטיביים. תווית ערך חיה: מציגה את ערך הסיגנל האחרון ליד הנקודה (ספרות ו־offset ניתנים להגדרה). עיצוב קריא: צבע קו אדום מעל OB, ירוק מתחת OS, אפור ניטרלי; מילוי אזורים. שימוש מומלץ מומנטום/היפוכים: כניסה עם חציה מה-OS/OB ואישור מה-MTF. ממוצע נע/רמות מחיר: חברו לאימות מגמה (למשל EMA200 או תמיכה/התנגדות). Mean Reversion: חיפוש חזרה מאזורי קיצון, במיוחד כשיש התרעת יציאה מ-OB/OS או נגיעה בבנד אדפטיבי. קלטים מרכזיים CCI Period, Stoch Period, Smooth K/D – פרמטרי חישוב. Overbought / Oversold – ספי קיצון (ברירת מחדל 80/20). Line to plot – בחירה בין K או D. Show Arrows/Center/Exit/Enter – שליטה בתצוגת החיצים. Adaptive Bands (len, k) – חלון ורגישות לבנדים. Higher TF – טיימפריים לאישור (אופציונלי). Live Label – ספרות, היסט ברים, צבעי רקע. טיפים מהירים בסקלפים/טווחים קצרים: הקשיחו ספי קיצון (למשל 85/15) להפחתת רעש. בשוק תנודתי: העלו את adaptLen או הורידו את k כדי לקבל בנדים רגישים פחות. להקטנת אותות שווא: דרשו התאמה בין הסיגנל המקומי ל-MTF (לדוגמה, לונג רק כשה-MTF מעל 50). הערה חשובה זהו כלי ניתוח טכני—לא אות קנייה/מכירה בפני עצמו. שלבו אותו עם ניהול סיכונים (SL/TP), בדיקת רמות מפתח ואימות ממספר אינדיקטורים או טיימפריימים.
Indicador Pine Script®
por yosia900
Multi Timeframe Relative Strength Index {DCAquant}Overview The Multi Timeframe Relative Strength Index (MTF RSI) is a powerful technical analysis tool designed to provide insights into market momentum and potential trend reversals across multiple timeframes. Leveraging the Relative Strength Index (RSI) formula, this indicator offers traders a comprehensive view of market sentiment and identifies overbought and oversold conditions. Key Features RSI Calculation: Utilizes the standard RSI calculation formula to measure the magnitude of recent price changes and assess the strength of market trends. Employs a user-defined length parameter to customize the sensitivity of the RSI calculation based on trading preferences. Multiple Timeframe Analysis: Allows traders to analyze RSI values across up to six different timeframes, ranging from minutes to days, providing a holistic perspective on market dynamics. Calculates RSI values independently for each selected timeframe, enabling comparison and trend identification. Threshold Levels: Defines overbought and oversold levels to highlight potential reversal points in market trends. Offers flexibility in adjusting threshold levels based on individual risk tolerance and trading strategies. Neutral Zone: Establishes upper and lower neutral thresholds to identify periods of consolidation or sideways movement in price. Helps traders distinguish between trending and ranging market conditions for more accurate analysis. Moving Average Smoothing: Provides the option to apply moving average smoothing to aggregated RSI values for enhanced clarity and reduced noise. Enables smoother visualization of RSI trends, facilitating easier interpretation for traders. Visual Representation: Plots the aggregated MTF RSI values on the price chart, allowing traders to visually assess market momentum and potential reversal points. Utilizes color-coded backgrounds to indicate Long, Short, or Neutral conditions for quick identification. Dynamic Table Display: Displays trading signals alongside graphical indicators (rocket for Long, snowflake for Short, and star for Neutral) in a customizable table format. Offers flexibility in table placement and size to accommodate user preferences. How to Use: Parameter Configuration: Adjust the length parameter to fine-tune the sensitivity of the RSI calculation based on the desired timeframe and trading strategy. Define overbought and oversold levels to identify potential reversal points in market trends. Customize upper and lower neutral thresholds to differentiate between trending and ranging market conditions. Interpretation: Monitor the aggregated MTF RSI values plotted on the price chart for signals of overbought or oversold conditions. Pay attention to color-coded backgrounds and graphical indicators in the table for actionable trading insights. Trading Strategy: Consider entering Long positions when the aggregated MTF RSI is above the upper neutral threshold, indicating potential bullish momentum. Evaluate Short opportunities when the aggregated MTF RSI falls below the lower neutral threshold, signaling possible bearish momentum. Exercise caution during Neutral conditions, as there may be uncertainty in market direction. Risk Management: Combine MTF RSI analysis with robust risk management strategies, including stop-loss and take-profit levels, to manage trading risks effectively. Practice prudent risk management and trade within your risk tolerance to minimize potential losses. Disclaimer Trading in financial markets involves risk, and past performance is not indicative of future results. The use of the MTF RSI indicator does not guarantee profits or prevent losses. Traders should conduct their own analysis, exercise caution, and seek advice from qualified financial professionals before making trading decisions.
Indicador Pine Script®
por DCAquant
Fair Value Gap█ OVERVIEW This indicator displays the Fair Value Gap of the current timeframe and an additional higher timeframe. For each FVG the gaps act as targets creating bullish and bearish gaps that are often filled. █ FEATURES MTF Options MidPoint FIll Delete Old On Fill Label FVG Timeframe MTF Options Enabling the MTF Options will allow the user to use the "MTF Timeframe" setting to choose what HTF Fair Value Gap to display MidPoint FIll A line plot at the Half way point will be included in the Fair Value Gap, this will be used to delete the gap when reached instead of a full fill. Delete Old On Fill Deletes historical Fair Value Gaps when filled. Label FVG Timeframe Labels Every Fair Value gap with there relevant timeframe to make it easier to determine which gap is being filled. █ HOW TO USE IT The indicator is quite straight forward in its application, providing users with targets that are often filled as they are seen as market imbalance. Just applying it to your chart will provide the existing Fair Value Gaps. MTF Confluence is helpful in seeing what is happening on the macro perspective. █ SUGGESTION My suggestion for clarity is to use a different color to some degree between the MTF and Current TF as Opposed to text, keeps the chart clear. █ LIMITATIONS OF PINE (Please read) I see many users going on different indicators with MTF in mind and trying to use it for LTF data e.g. 1hour chart, and selecting 5min in chart settings. This is not recommended by the team themselves and should be noted for use always use HTF: www.tradingview.com To understand how to use fair value gaps I recommend learning about the subject some more, searching online will provide you resources. The internet is your friend when learning. All the best.
Indicador Pine Script®
por spacemanbtc
106
Multi SMA EMA WMA HMA BB (5+5 MAs + Bollinger Bands) by RRB Multi SMA EMA WMA HMA BB (5+5 Moving Averages of Any Type with Bollinger Bands) by RagingRocketBull 2018 Version 1.0 This indicator shows multiple MAs of any type (SMA EMA WMA HMA etc) with BB on a chart at the same time with/without MTF support depending on the version. There are several versions (published later): Simple, MTF, Pro MTF and Ultimate MTF. This is the Simple version. The Differences are listed below. All versions have BB - Simple: you have 2 groups of MAs that can be assigned any type (5+5) - MTF: +assign 1 custom Timeframe to any group combo (5+5 Custom TF) - Pro MTF: +multiple Timeframes for multiple MA groups (4*3 MTF), horizontal levels and show max bars back options - Ultimate MTF: +individual settings for each MA, multiple Timeframes You can use different types of MAs as dynamic S/R levels to trade of off and MA crosses as signals for possible trend change (golden/death bull/bear crosses). Most common MA types are: SMA, EMA, WMA, HMA. Most common MA lengths are: 12, 20, 26, 30, 50, 100, 200, 400 etc. Features: - 2 groups of custom 5+5 MAs of any type including Hull Moving Average (HMA) - BB 1. based on 3EmaBB, uses plot, fill, stdev and custom hma functions 2. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params Feel free to use. Good Luck!
Indicador Pine Script®
por RagingRocketBull
12
RCV Essentials════════════════════════════════════════════ RCV ESSENTIALS - MULTI-TIMEFRAME & SESSION ANALYSIS TOOL ════════════════════════════════════════════ 📊 WHAT THIS INDICATOR DOES This professional-grade indicator combines two powerful analysis modules: 1. TRADING SESSION TRACKER - Visualizes high/low ranges for major global market sessions (NY Open, London Open, Asian Session, etc.) 2. MULTI-TIMEFRAME CANDLE DISPLAY - Shows up to 8 higher timeframes simultaneously on your chart (15m, 30m, 1H, 4H, 1D, 1W, 1M, 3M) ════════════════════════════════════════════ 🎯 KEY FEATURES ════════════════════════════════════════════ TRADING SESSIONS MODULE: ✓ Track up to 6 custom trading sessions simultaneously ✓ Real-time high/low range detection during active sessions ✓ Pre-configured for NYO (7-9am), LNO (2-3am), Asian Session (4:30pm-12am) ✓ 60+ global timezone options ✓ Customizable colors, labels, and transparency ✓ Daily divider lines (optional Sunday skip for traditional markets) ✓ Only displays on ≤30m timeframes for optimal clarity MULTI-TIMEFRAME CANDLES MODULE: ✓ Display 1-8 higher timeframes with up to 10 candles each ✓ Real-time candle updates (non-repainting) ✓ Fully customizable colors (separate bullish/bearish for body/border/wick) ✓ Adjustable candle width, spacing, and positioning ✓ Smart label system (top/bottom/both, aligned or follow candles) ✓ Automatic timeframe validation (only shows TFs higher than chart) ✓ Memory-optimized with automatic cleanup ════════════════════════════════════════════ 🔧 HOW IT WORKS ════════════════════════════════════════════ TECHNICAL IMPLEMENTATION: Session Tracking Algorithm: • Detects session start/end using time() function with timezone support • Continuously monitors and updates high/low during active session • Finalizes range when session ends using var persistence • Draws boxes using real-time bar_index positioning • Maintains session ranges across multiple days for reference Multi-Timeframe System: • Uses ta.change(time()) detection to identify new MTF candle formation • Constructs candles using custom Type definitions (Candle, CandleSet, Config) • Stores OHLC data in arrays with automatic size management • Renders using box objects (bodies) and line objects (wicks) • Updates current candle every tick; historical candles remain static • Calculates dynamic positioning based on user settings (offset, spacing, width) Object-Oriented Architecture: • Custom Type "Candle" - Stores OHLC values, timestamps, visual elements • Custom Type "CandleSet" - Manages arrays of candles + settings per timeframe • Custom Type "Config" - Centralizes all display configuration • Efficient memory management via unshift() for new candles, pop() for old Performance Optimizations: • var declarations minimize recalculation overhead • Conditional execution (sessions only on short timeframes) • Maximum display limits prevent excessive object creation • Timeframe validation at barstate.isfirst reduces redundant checks ════════════════════════════════════════════ 📈 HOW TO USE ════════════════════════════════════════════ SETUP: 1. Add indicator to chart (works best on 1m-30m timeframes) 2. Open Settings → "Trading Sessions" group - Enable desired sessions (NYO, LNO, AS, or custom) - Select your timezone from 60+ options - Adjust colors and transparency 3. Open Settings → "Multi-TF Candles" group - Enable timeframes (TF1-TF8) - Configure each timeframe and display count - Customize colors and layout READING THE CHART: • Session boxes show high/low ranges during active sessions • MTF candles display to the right of current price • Labels identify each timeframe (15m, 1H, 4H, etc.) • Real-time updates on the most recent MTF candle TRADING APPLICATIONS: Session Breakout Strategy: → Identify session high/low (e.g., Asian session 16:30-00:00) → Wait for break above/below range → Confirm with higher timeframe candle close → Enter in breakout direction, stop at opposite side of range Multi-Timeframe Confirmation: → Spot setup on primary chart (e.g., 5m) → Verify 15m, 1H, 4H candles align with trade direction → Only take trades where higher TFs confirm → Exit when higher TF candles show reversal Combined Session + MTF: → Asian session establishes range overnight → London Open breaks Asian high → Confirm with bullish 15m + 1H candles → Enter long with stop below Asian high ════════════════════════════════════════════ 🎨 ORIGINALITY & INNOVATION ════════════════════════════════════════════ What makes this indicator original: 1. INTEGRATED DUAL-MODULE DESIGN Unlike separate session or MTF indicators, this combines both in a single performance-optimized script, enabling powerful correlation analysis between session behavior and timeframe structure. 2. ADVANCED RENDERING SYSTEM Uses custom Pine Script v5 Types with dynamic box/line object management instead of basic plot functions. This enables: • Precise visual control over positioning and spacing • Real-time updates without repainting • Efficient memory handling via automatic cleanup • Support for 8 simultaneous timeframes with independent settings 3. INTELLIGENT SESSION TRACKING The algorithm continuously recalculates ranges bar-by-bar during active sessions, then preserves the final range. This differs from static zone indicators that simply draw fixed boxes at predefined levels. 4. MODULAR ARCHITECTURE Custom Type definitions (Candle, CandleSet, Config) create extensible, maintainable code structure while supporting complex multi-timeframe operations with minimal performance impact. 5. PROFESSIONAL FLEXIBILITY Extensive customization: 6 configurable sessions, 8 timeframe slots, 60+ timezones, granular color/sizing/spacing controls, multiple label positioning modes—adaptable to any market or trading style. 6. SMART VISUAL DESIGN Automatic timeframe validation, dynamic label alignment options, and intelligent spacing calculations ensure clarity even with multiple timeframes displayed simultaneously. ════════════════════════════════════════════ ⚙️ CONFIGURATION OPTIONS ════════════════════════════════════════════ TRADING SESSIONS: • Session 1-6: On/Off toggles • Time Ranges: Custom start-end times • Labels: Custom text for each session • Colors: Individual color per session • Timezone: 60+ options (Americas, Europe, Asia, Pacific, Africa) • Range Transparency: 0-100% • Outline: Optional border • Label Display: Show/hide session names • Daily Divider: Dotted lines at day changes • Skip Sunday: For traditional markets vs 24/7 crypto MULTI-TF CANDLES: • Timeframes 1-8: Enable/disable individually • Timeframe Selection: Any TF (seconds to months) • Display Count: 1-10 candles per timeframe • Bullish Colors: Body/Border/Wick (independent) • Bearish Colors: Body/Border/Wick (independent) • Candle Width: 1-10+ bars • Right Margin: 0-200+ bars from edge • TF Spacing: Gap between timeframe groups • Label Color: Any color • Label Size: Tiny/Small/Normal/Large/Huge • Label Position: Top/Bottom/Both • Label Alignment: Follow Candles or Align ════════════════════════════════════════════ 📋 TECHNICAL SPECIFICATIONS ════════════════════════════════════════════ • Pine Script Version: v5 • Chart Overlay: True • Max Boxes: 500 • Max Lines: 500 • Max Labels: 500 • Max Bars Back: 5000 • Update Frequency: Real-time (every tick) • Timeframe Compatibility: Chart TF must be lower than selected MTFs • Session Display: Activates only on ≤30 minute timeframes • Memory Management: Automatic cleanup via array operations
Indicador Pine Script®
por RCVisionaries
Intrabar Volume Delta — RealTime + History (Stocks/Crypto/Forex)Intrabar Volume Delta Grid — RealTime + History (Stocks/Crypto/Forex) # Short Description Shows intrabar Up/Down volume, Delta (absolute/relative) and UpShare% in a compact grid for both real-time and historical bars. Includes an MTF (M1…D1) dashboard, contextual coloring, density controls, and alerts on Δ and UpShare%. Smart historical splitting (“History Mode”) for Crypto/Futures/FX. --- # What it does (Quick) * **UpVol / DownVol / Δ / UpShare%** — visualizes order-flow inside each candle. * **Real-time** — accumulates intrabar volume live by tick-direction. * **History Mode** — splits Up/Down on closed bars via simple or range-aware logic. * **MTF Dashboard** — one table view across M1, M5, M15, M30, H1, H4, D1 (Vol, Up/Down, Δ%, Share, Trend). * **Contextual opacity** — stronger signals appear bolder. * **Label density** — draw every N-th bar and limit to last X bars for performance. * **Alerts** — thresholds for |Δ|, Δ%, and UpShare%. --- # How it works (Real-Time vs History) * **Real-time (open bar):** volume increments into **UpVolRT** or **DownVolRT** depending on last price move (↑ goes to Up, ↓ to Down). This approximates live order-flow even when full tick history isn’t available. * **History (closed bars):** * **None** — no split (Up/Down = 0/0). Safest for equities/indices with unreliable tick history. * **Approx (Close vs Open)** — all volume goes to candle direction (green → Up 100%, red → Down 100%). Fast but yields many 0/100% bars. * **Price Action Based** — splits by Close position within High-Low range; strength = |Close−mid|/(High−Low). Above mid → more Up; below mid → more Down. Falls back to direction if High==Low. * **Auto** — **Stocks/Index → None**, **Crypto/Futures/FX → Approx**. If you see too many 0/100 bars, switch to **Price Action Based**. --- # Rows & Meaning * **Volume** — total bar volume (no split). * **UpVol / DownVol** — directional intrabar volume. * **Delta (Δ)** — UpVol − DownVol. * **Absolute**: raw units * **Relative (Δ%)**: Δ / (Up+Down) × 100 * **Both**: shows both formats * **UpShare%** — UpVol / (Up+Down) × 100. >50% bullish, <50% bearish. * Helpful icons: ▲ (>65%), ▼ (<35%). --- # MTF Dashboard (🔧 Enable Dashboard) A single table with **Vol, Up, Down, Δ%, Share, Trend (🔼/🔽/⏭️)** for selected timeframes (M1…D1). Great for a fast “panorama” read of flow alignment across horizons. --- # Inputs (Grouped) ## Display * Toggle rows: **Volume / Up / Down / Delta / UpShare** * **Delta Display**: Absolute / Relative / Both ## Realtime & History * **History Mode**: Auto / None / Approx / Price Action Based * **Compact Numbers**: 1.2k, 1.25M, 3.4B… ## Theme & UI * **Theme Mode**: Auto / Light / Dark * **Row Spacing**: vertical spacing between rows * **Top Row Y**: moves the whole grid vertically * **Draw Guide Lines**: faint dotted guides * **Text Size**: Tiny / Small / Normal / Large ## 🔧 Dashboard Settings * **Enable Dashboard** * **📏 Table Text Size**: Tiny…Huge * **🦓 Zebra Rows** * **🔲 Table Border** ## ⏰ Timeframes (for Dashboard) * **M1…D1** toggles ## Contextual Coloring * **Enable Contextual Coloring**: opacity by signal strength * **Δ% cap / Share offset cap**: saturation caps * **Min/Max transparency**: solid vs faint extremes ## Label Density & Size * **Show every N-th bar**: draw labels only every Nth bar * **Limit to last X bars**: keep labels only in the most recent X bars ## Colors * Up / Down / Text / Guide ## Alerts * **Delta Threshold (abs)** — |Δ| in volume units * **UpShare > / <** — bullish/bearish thresholds * **Enable Δ% Alert**, **Δ% > +**, **Δ% < −** — relative delta levels --- # How to use (Quick Start) 1. Add the indicator to your chart (overlay=false → separate pane). 2. **History Mode**: * Crypto/Futures/FX → keep **Auto** or switch to **Price Action Based** for richer history. * Stocks/Index → prefer **None** or **Price Action Based** for safer splits. 3. **Label Density**: start with **Limit to last X bars = 30–150** and **Show every N-th bar = 2–4**. 4. **Contextual Coloring**: keep on to emphasize strong Δ% / Share moves. 5. **Dashboard**: enable and pick only the TFs you actually use. 6. **Alerts**: set thresholds (ideas below). --- # Alerts (in TradingView) Add alert → pick this indicator → choose any of: * **Delta exceeds threshold** (|Δ| > X) * **UpShare above threshold** (UpShare% > X) * **UpShare below threshold** (UpShare% < X) * **Relative Delta above +X%** * **Relative Delta below −X%** **Starter thresholds (tune per symbol & TF):** * **Crypto M1/M5**: Δ% > +25…35 (bullish), Δ% < −25…−35 (bearish) * **FX (tick volume)**: UpShare > 60–65% or < 40–35% * **Stocks (liquid)**: set **Absolute Δ** by typical volume scale (e.g., 50k / 100k / 500k) --- # Notes by Market Type * **Crypto/Futures**: 24/7 and high liquidity — **Price Action Based** often gives nicer history splits than Approx. * **Forex (FX)**: TradingView volume is typically **tick volume** (not true exchange volume). Treat Δ/Share as tick-based flow, still very useful intraday. * **Stocks/Index**: historical tick detail can be limited. **None** or **Price Action Based** is a safer default. If you see too many 0/100% shares, switch away from Approx. --- # “All Timeframes” accuracy * Works on **any TF** (M1 → D1/W1). * **Real-time accuracy** is strong for the open bar (live accumulation). * **Historical accuracy** depends on your **History Mode** (None = safest, Approx = fastest/simplest, Price Action Based = more nuanced). * The MTF dashboard uses `request.security` and therefore follows the same logic per TF. --- # Trade Ideas (Use-Cases) * **Scalping (M1–M5)**: a spike in Δ% + UpShare>65% + rising total Vol → momentum entries. * **Intraday (M5–M30–H1)**: when multiple TFs show aligned Δ%/Share (e.g., M5 & M15 bullish), join the trend. * **Swing (H4–D1)**: persistent Δ% > 0 and UpShare > 55–60% → structural accumulation bias. --- # Advantages * **True-feeling live flow** on the open bar. * **Adaptable history** (three modes) to match data quality. * **Clean visual layout** with guides, compact numbers, contextual opacity. * **MTF snapshot** for quick bias read. * **Performance controls** (last X bars, every N-th bar). --- # Limitations & Care * **FX uses tick volume** — interpret Δ/Share accordingly. * **History Mode is an approximation** — confirm with trend/structure/liquidity context. * **Illiquid symbols** can produce noisy or contradictory signals. * **Too many labels** can slow charts → raise N, lower X, or disable guides. --- # Best Practices (Checklist) * Crypto/Futures: prefer **Price Action Based** for history. * Stocks: **None** or **Price Action Based**; be cautious with **Approx**. * FX: pair Δ% & UpShare% with session context (London/NY) and volatility. * If labels overlap: tweak **Row Spacing** and **Text Size**. * In the dashboard, keep only the TFs you actually act on. * Alerts: start around **Δ% 25–35** for “punchy” moves, then refine per asset. --- # FAQ **1) Why do some closed bars show 0%/100% UpShare?** You’re on **Approx** history mode. Switch to **Price Action Based** for smoother splits. **2) Δ% looks strong but price doesn’t move — why?** Δ% is an **order-flow** measure. Price also depends on liquidity pockets, sessions, news, higher-timeframe structure. Use confirmations. **3) Performance slowdown — what to do?** Lower **Limit to last X bars** (e.g., 30–100), increase **Show every N-th bar** (2–6), or disable **Draw Guide Lines**. **4) Dashboard values don’t “match” the grid exactly?** Dashboard is multi-TF via `request.security` and follows the history logic per TF. Differences are normal. --- # Short “Store” Marketing Blurb Intrabar Volume Delta Grid reveals the order-flow inside every candle (Up/Down, Δ, UpShare%) — live and on history. With smart history splitting, an MTF dashboard, contextual emphasis, and flexible alerts, it helps you spot momentum and bias across Crypto, Forex (tick volume), and Stocks. Tidy labels and compact numbers keep the panel readable and fast.
Indicador Pine Script®
por a_jabbaroff
QFisher-R™ [ParadoxAlgo]QFISHER-R™ (Regime-Aware Fisher Transform) A research/education tool that helps visualize potential momentum exhaustion and probable inflection zones using a quantitative, non-repainting Fisher framework with regime filters and multi-timeframe (MTF) confirmation. What it does Converts normalized price movement into a stabilized Fisher domain to highlight potential turning points. Uses adaptive smoothing, robust (MAD/quantile) thresholds, and optional MTF alignment to contextualize extremes. Provides a Reversal Probability Score (0–100) to summarize signal confluence (extreme, slope, cross, divergence, regime, and MTF checks). Key features Non-repainting logic (bar-close confirmation; security() with no lookahead). Dynamic exhaustion bands (data-driven thresholds vs fixed ±2). Adaptive smoothing (efficiency-ratio based). Optional divergence tags on structurally valid pivots. MTF confirmation (same logic computed on a higher timeframe). Compact visuals with subtle plotting to reduce chart clutter. Inputs (high level) Source (e.g., HLC3 / Close / HA). Core lookback, fast/slow range blend, and ER length. Band sensitivity (robust thresholding). MTF timeframe(s) and agreement requirement. Toggle divergence & intrabar previews (default off). Signals & Alerts Turn Candidate (Up/Down) when multiple conditions align. Trade-Grade Turn when score ≥ threshold and MTF agrees. Divergence Confirmed when structural criteria are met. Alerts are generated on confirmed bar close by default. Optional “preview” mode is available for experimentation. How to use Start on your preferred timeframe; optionally enable an HTF (e.g., 4×) for confirmation. Look for RPS clusters near the exhaustion bands, slope inflections, and (optionally) divergences. Combine with your own risk management, liquidity, and trend context. Paper test first and calibrate thresholds to your instrument and timeframe. Notes & limitations This is not a buy/sell signal generator and does not predict future returns. Readings can remain extreme during strong trends; use HTF context and your own filters. Parameters are intentionally conservative by default; adjust carefully. Compliance / Disclaimer Educational & research tool only. Not financial advice. No recommendation to buy/sell any security or derivative. Past performance, backtests, or examples (if any) are not indicative of future results. Trading involves risk; you are responsible for your own decisions and risk management. Built upon the Fisher Transform concept (Ehlers); all modifications, smoothing, regime logic, scoring, and visualization are original work by Paradox Algo.
Indicador Pine Script®
por paradoxalgo
2
[Mad]Triple Bollinger Bands ForecastTriple Bollinger Bands Forecast (BBx3+F) This open-source indicator is an advanced version of the classic Bollinger Bands, designed to provide a more comprehensive and forward-looking view of market volatility and potential price levels. It plots three distinct sets of Bollinger Bands and projects them into the future based on statistical calculations. How It Is Built and Key Features Triple Bollinger Bands: Instead of a single set of bands, this indicator plots three. All three share the same central basis line (a Simple Moving Average), but each has a different standard deviation multiplier. This creates three distinct volatility zones for analyzing price deviation from its mean. Multi-Timeframe (MTF) Capability: The indicator can calculate and display Bollinger Bands from a higher timeframe (e.g., showing daily bands on a 4-hour chart). This allows for contextualizing price action within the volatility structure of a more significant trend. (Lower HTF selection will result in script-crash!) Future Forecasting: This is the indicator's main feature. It projects the calculated Bollinger Bands up to 8 bars into the future. This forecast is a recalculation of the Simple Moving Average and Standard Deviation based on a projected future source price. Selectable Forecast Methods: The mathematical model for estimating the future source price can be selected: Flat: A model that uses the most recent closing price as the price for all future bars in the calculation window. Linreg (Linear Regression): A model that calculates a linear regression trend on the last few bars and projects it forward to estimate the future source price. Efficient Drawing with Polylines: The future projections are drawn on the chart using Pine Script's polyline object. This is an efficient method that draws the forecast data only on the last bar, which avoids repainting issues. Differences from a Classical Bollinger Bands Indicator Band Count: A classical indicator shows one set of bands. This indicator plots three sets for a multi-layered view of volatility. Perspective: Classical Bollinger Bands are purely historical. This indicator is both historical and forward-looking . Forecasting: The classic version has no forecasting capability. This indicator projects the bands into the future . Timeframe: The classic version works only on the current timeframe. This indicator has full Multi-Timeframe (MTF) support . The Mathematics Behind the Future Predictions The core challenge in forecasting Bollinger Bands is that a future band value depends on future prices, which are unknown. This indicator solves this by simulating a future price series. Here is the step-by-step logic: Forecast the Source Price for the Next Bar First, the indicator estimates what the price will be on the next bar. Flat Method: The forecasted price is the current bar's closing price. Price_forecast = close Linreg Method: A linear regression is calculated on the last few bars and extrapolated one step forward. Price_forecast = ta.linreg(close, linreglen, 1) Calculate the Future SMA (Basis) To calculate the Simple Moving Average for the next bar, a new data window is simulated. This window includes the new forecasted price and drops the oldest historical price. For a 1-bar forecast, the calculation is: SMA_future = (Price_forecast + close + close + ... + close ) / length Calculate the Future Standard Deviation Similarly, the standard deviation for the next bar is calculated over this same simulated window of prices, using the new SMA_future as its mean. // 1. Calculate the sum of squared differences from the new mean d_f = Price_forecast - SMA_future d_0 = close - SMA_future // ... and so on for the rest of the window's prices SumOfSquares = (d_f)^2 + (d_0)^2 + ... + (d_length-2)^2 // 2. Calculate future variance and then the standard deviation Var_future = SumOfSquares / length StDev_future = sqrt(Var_future) Extending the Forecast (2 to 8 Bars) For forecasts further into the future (e.g., 2 bars), the script uses the same single Price_forecast for all future steps in the calculation. For a 2-bar forecast, the simulated window effectively contains the forecasted price twice, while dropping the two oldest historical prices. This provides a statistically-grounded projection of where the Bollinger Bands are likely to form. Usage as a Forecast Extension This indicator's functionality is designed to be modular. It can be used in conjunction with as example Mad Triple Bollinger Bands MTF script to separate the rendering of historical data from the forward-looking forecast. Configuration for Combined Use: Add both the Mad Triple Bollinger Bands MTF and this Triple Bollinger Bands Forecast indicator to your chart. Open the Settings for this indicator (BBx3+F). In the 'General Settings' tab, disable the Activate Plotting option. To ensure data consistency, the Bollinger Length, Multipliers, and Higher Timeframe settings should be identical across both indicators. This configuration prevents the rendering of duplicate historical bands. The Mad Triple Bollinger Bands MTF script will be responsible for visualizing the historical and current bands, while this script will overlay only the forward-projected polyline data.
Indicador Pine Script®
por djmad
Probabilistic Panel - COMPLETE VERSION📘 Probabilistic Panel — User Manual ________________________________________ INTRODUCTION The Probabilistic Panel is an advanced TradingView indicator that merges multiple technical-analysis components to provide a probabilistic evaluation of market direction. It is composed of several sections that assess trend, volume, price zones, support and resistance, multiple timeframes, and candle distribution. ________________________________________ PANEL STRUCTURE 1. HEADER • PROBABILISTIC PANEL: Indicator name. • FULL VERSION: Indicates that all functionalities are enabled. ________________________________________ 2. GENERAL INFORMATION • ASSET: Displays the asset symbol being analyzed. • LIMITS: Shows score thresholds for classifying setups (A+, B, C). ________________________________________ 3. DIRECTION PROBABILITIES • PROB: Displays probability of upward movement (upPct) and downward movement (downPct) in percentage. o Importance: Indicates the direction with the highest probability based on weighted factors. ________________________________________ 4. CONTINUATION BIAS • BIAS: Shows the probability of continuation of the current trend (intrProbCont). o Importance: Evaluates whether the market is likely to continue in the same direction. ________________________________________ 5. MULTI-TIMEFRAME ANALYSIS (MTF) • MTF: Shows trend direction across multiple timeframes (1D, 1H, 15M, 5M, 1M) using arrows (↑ uptrend, ↓ downtrend, → sideways). o Importance: Helps identify convergence or divergence between timeframes. • ALIGNED MTF: Displays the percentage of alignment between timeframes. o Importance: Higher alignment indicates stronger trends. ________________________________________ 6. VOLUME • VOLUME: Indicates whether volume is “INCREASING”, “DECREASING”, or “STABLE.” o Importance: Increasing volume confirms trend strength. ________________________________________ 7. TECHNICAL INDICATORS • RSI/ROC: Displays RSI (Relative Strength Index) and ROC (Rate of Change). o Importance:  RSI > 65 → Overbought  RSI < 35 → Oversold  ROC → Momentum strength indicator ________________________________________ 8. PRICE ZONE • ZONE: Classifies current price as “PREMIUM” (above average), “DISCOUNT” (below average), or “EQUILIBRIUM.” o Importance: Helps identify buying/selling opportunities based on mean-reversion logic. ________________________________________ 9. CANDLE ANALYSIS • AMPLITUDE: Shows current candle size in percentage and ticks. o Importance: Candles above minimum amplitude threshold are considered trade-valid. • FORMATION: Classifies candle as: o HIGH INDECISION o TOP REJECTION o BOTTOM REJECTION o CONVICTION o MIXED o Importance: Reflects market sentiment and psychology. • WICKS: Displays upper and lower wick size in percentage. o Importance: Longer wicks suggest rejection or indecision. • RATIO: Ratio between total wick size and candle body. o Importance: High ratio = indecision; low ratio = conviction. ________________________________________ 10. TRENDS • AMPLITUDE TREND: Indicates if amplitude is “INCREASING,” “DECREASING,” or “STABLE.” o Importance: Increasing amplitude may signal rising volatility. • CONVICTION TREND: Indicates recent candle conviction: o STRONG UP o STRONG DOWN o INDECISIVE o MIXED o Importance: Measures the strength of recent candles. ________________________________________ 11. PROBABILITY DIFFERENCE (DIF PROB) • Shows the percentage difference between upward and downward probabilities, classified as: o EXCELLENT: Very favorable o GOOD: Significant o MEDIUM: Moderate (avoid entering) o MARKET LOSING STRENGTH: Small difference (avoid entering) o UNSTABLE MARKET: Very small difference (do not trade) o Importance: Higher difference = more directional clarity. ________________________________________ 12. CONFIRMATIONS • Shows how many consecutive confirmations of the current signal were achieved relative to the configured requirement. o Importance: More confirmations increase reliability. ________________________________________ 13. SCORE & CLASSIFICATION • SCORE: Final score from 0 to 100, calculated based on multiple factors. o Higher scores = better setups. • CLASSIFICATION: Setup categorized as: o A+ SETUP o B SETUP o C SETUP o DO NOT TRADE o Importance: Defines whether conditions are favorable. ________________________________________ 14. ACTION • ACTION: Suggests “BUY,” “SELL,” or “WAIT.” o Importance: Final actionable signal. ________________________________________ DECISION LOGIC The indicator uses a weighted combination of multiple factors: 1. Trend (wTrend): Based on the price relative to EMA50. 2. Volume (wVol): Based on recent volume vs. its average. 3. Zone (wZona): Based on price position within recent price range. 4. Support/Resistance (wSR): Based on strength of S/R levels. 5. MTF (wMTF): Timeframe alignment. 6. Distribution (wDist): Distribution of bullish, bearish, and neutral candles. The final score integrates: • Probability of upward movement • Continuation bias • MTF conflict • Moving-average alignment • Volume • Extreme RSI conditions ________________________________________ FALSE-SIGNAL FILTERS • Close-Only Mode: Updates calculations only on candle close. • Minimum Candle Size: Ignores very small candles. • Consecutive Confirmations: Requires repeated signal confirmation. • Minimum Probability Difference: Enforces a minimum separation between bullish and bearish probabilities. ________________________________________ CONCLUSION The Probabilistic Panel is a comprehensive tool that integrates multiple technical-analysis dimensions to deliver more reliable trading signals. Parameters must be adjusted according to the asset and timeframe. Remember: no indicator is infallible. Always combine it with risk management and additional confirmations.
Indicador Pine Script®
por pf0210