Şimdi başlat

Göstergeler ve stratejiler

Short Entry Setup - PL1!//@version=5 indicator("Short Signal - Platinum", overlay=true) // === User Inputs === entryTop = input.float(1182.0, "Resistance Zone Top") entryBottom = input.float(1178.0, "Resistance Zone Bottom") rsiLevel = input.float(75.0, "RSI Overbought Level") // === RSI Calculation === rsi = ta.rsi(close, 14) rsiOverbought = rsi > rsiLevel // === Price in Resistance Zone === priceInZone = close >= entryBottom and close <= entryTop // === Bearish Candle Condition === bearishCandle = close < open // === Final Short Signal Condition === shortSignal = priceInZone and bearishCandle and rsiOverbought // === Plot Short Signal on Chart === plotshape(shortSignal, location=location.abovebar, style=shape.labeldown, color=color.red, size=size.small, text="SHORT") // === Optional: Plot Background of Zone === bgcolor(priceInZone ? color.new(color.red, 90) : na, title="Resistance Zone") // === Alert Condition for Automation === alertcondition(shortSignal, title="Short Signal Alert", message="SHORT SIGNAL: Price in resistance zone, RSI overbought, bearish candle.")
Pine Script® göstergesi
suneetsaurabh_stock1M tarafından
Time//@version=5 indicator('Time', overlay=true, max_bars_back=1000, max_labels_count=500, max_lines_count=500, max_boxes_count=500) // Asia var GRP1 = "Asian Session" extendLines = true rangeTime = '1705-0101' boxLineColor = input(color.new(color.rgb(212, 129, 4), int(80)), 'Line color', group=GRP1) backgroundColor = input(color.new(color.rgb(221, 133, 0), int(90)), "Background color", group=GRP1) // A session inSession1 = not na(time(timeframe.period, rangeTime)) inExtend = not na(time(timeframe.period, "0100-0801")) startTime = 0 startTime := inSession1 and not inSession1 ? time : startTime var line lowHLine = na var line topHLine = na var line leftVLine = na var line rightVLine = na var line middleHLine = na var box bgBox = na var low_val = float(0.0) var high_val = 0.0 if inSession1 and not inSession1 low_val := low high_val := high high_val if inSession1 and timeframe.isintraday if inSession1 line.delete(lowHLine) line.delete(topHLine) line.delete(middleHLine) box.delete(bgBox) if low < low_val low_val := low low_val if high > high_val high_val := high high_val if true and timeframe.multiplier <= 60 bgBox := box.new(startTime, high_val, time, low_val, xloc=xloc.bar_time, bgcolor=backgroundColor, border_width=0) if true and timeframe.multiplier <= 60 lowHLine := line.new(startTime, low_val, time, low_val, xloc=xloc.bar_time, color=boxLineColor, style=line.style_solid, width=1) topHLine := line.new(startTime, high_val, time, high_val, xloc=xloc.bar_time, color=boxLineColor, style=line.style_solid, width=1) if true and timeframe.multiplier <= 60 middleHLine := line.new(startTime, (high_val + low_val) / 2, time, (high_val + low_val) / 2, xloc=xloc.bar_time, color=boxLineColor, style=line.style_solid, width=1) else if inExtend and extendLines and not inSession1 and timeframe.isintraday time1 = line.get_x1(lowHLine) time2 = line.get_x2(lowHLine) price = line.get_y1(lowHLine) line.delete(lowHLine) lowHLine := line.new(time1, price, time, price, xloc=xloc.bar_time, color=boxLineColor, style=line.style_solid, width=1) time1 := line.get_x1(topHLine) time2 := line.get_x2(topHLine) price := line.get_y1(topHLine) line.delete(topHLine) topHLine := line.new(time1, price, time, price, xloc=xloc.bar_time, color=boxLineColor, style=line.style_solid, width=1) time1 := line.get_x1(middleHLine) time2 := line.get_x2(middleHLine) price := line.get_y1(middleHLine) line.delete(middleHLine) middleHLine := line.new(time1, price, time, price, xloc=xloc.bar_time, color=boxLineColor, style=line.style_solid, width=1) middleHLine // LDN & NY remove(str, pos, length) => arr = str.split(str, "") len = array.size(arr) pos1 = pos >= 0 ? pos : len + pos length_ = length >= 0 ? length : len - pos1 pos2 = pos1 + length_ if len > 0 and length_ > 0 and pos1 >= 0 and pos2 <= len for i = 0 to length_ - 1 array.remove(arr, pos1) res = array.join(arr, "") CalcOffs(timeStr) => hourStartStr = remove(timeStr, 2, 7) hourStart = str.tonumber(hourStartStr) minStartTemp = remove(timeStr, 0, 2) minStartStr = remove(minStartTemp, 2, 5) minStart = str.tonumber(minStartStr) timeEndStr = remove(timeStr, 0, 5) hourEndStr = remove(timeEndStr, 2, 2) hourEnd = str.tonumber(hourEndStr) minEndStr = remove(timeEndStr, 0, 2) minEnd = str.tonumber(minEndStr) time_diff_minutes = str.tostring(math.abs((hourEnd * 60 + minEnd) - (hourStart * 60 + minStart))) // Settings isLondon = true loSessionTime = input.session("0300-0400", title="Session", group = "London Session") loBoxColor = input.color(color.new(#2962ff, 80), title="Background color", group = "London Session") isNewYorkTrap = true nytrapSessionTime = input.session("0900-1000", title="Session", group ="New York Trap Session") nytrapBoxColor = input.color(color.new(#2962ff, 80), title="Background color", group = "New York Trap Session") loOffs = math.round(str.tonumber(CalcOffs(loSessionTime))) nytrapOffs = math.round(str.tonumber(CalcOffs(nytrapSessionTime))) dayOffs = 1440 if timeframe.period == "S" loOffs := loOffs * 60 nytrapOffs := nytrapOffs * 60 dayOffs := dayOffs * 60 if timeframe.period == "5S" loOffs := loOffs * 60 / 5 nytrapOffs := nytrapOffs * 60/5 dayOffs := dayOffs * 60 / 5 if timeframe.period == "15S" loOffs := loOffs * 60 / 15 nytrapOffs := nytrapOffs *60 / 15 dayOffs := dayOffs * 60 / 15 if timeframe.period == "30S" loOffs := loOffs * 60 / 30 nytrapOffs := nytrapOffs *60 / 30 dayOffs := dayOffs * 60 / 30 if timeframe.period == "3" loOffs := loOffs / 3 nytrapOffs := nytrapOffs /3 dayOffs := dayOffs / 3 if timeframe.period == "5" loOffs := loOffs / 5 nytrapOffs := nytrapOffs / 5 dayOffs := dayOffs / 5 if timeframe.period == "15" loOffs := loOffs / 15 nytrapOffs := nytrapOffs / 15 dayOffs := dayOffs / 15 if timeframe.period == "30" loOffs := loOffs / 30 nytrapOffs := nytrapOffs / 30 dayOffs := dayOffs / 30 if timeframe.period == "45" loOffs := loOffs / 45 nytrapOffs := nytrapOffs / 45 dayOffs := dayOffs / 45 if timeframe.period == "60" loOffs := loOffs / 60 nytrapOffs := nytrapOffs / 60 dayOffs := dayOffs / 60 if timeframe.period == "120" loOffs := loOffs / 120 nytrapOffs := nytrapOffs / 120 dayOffs := dayOffs / 120 if timeframe.period == "180" loOffs := loOffs / 180 nytrapOffs := nytrapOffs / 180 dayOffs := dayOffs / 180 if timeframe.period == "240" loOffs := loOffs / 240 nytrapOffs := nytrapOffs / 240 dayOffs := dayOffs / 240 if true and timeframe.multiplier <= 60 if isLondon var sessionHighPrice = 0.0 var sessionLowPrice = 0.0 var sessionOpenPrice = 0.0 var box sessionBox = na var line sessionTopLine = na var line sessionLowLine = na inSession = not na(time(timeframe.period, loSessionTime)) and timeframe.isintraday sessionStart = inSession and not inSession if sessionStart sessionHighPrice := high sessionLowPrice := low sessionOpenPrice := open else if inSession sessionHighPrice := math.max(sessionHighPrice, high) sessionLowPrice := math.min(sessionLowPrice, low) if sessionStart sessionBox := box.new(left=bar_index, top=na, right=bar_index+loOffs, bottom=na, border_color = color.new(#ffffff, 100), bgcolor=loBoxColor) sessionTopLine := line.new(x1=bar_index, y1=na, x2=bar_index+loOffs, y2=na, style=line.style_solid, width=0) sessionLowLine := line.new(x1=bar_index, y1=na, x2=bar_index+loOffs, y2=na, style=line.style_solid, width=0) if inSession box.set_top(sessionBox, sessionHighPrice) box.set_bottom(sessionBox, sessionLowPrice) if isNewYorkTrap var sessionHighPrice = 0.0 var sessionLowPrice = 0.0 var sessionOpenPrice = 0.0 var box sessionBox = na var line sessionTopLine = na var line sessionLowLine = na inSession = not na(time(timeframe.period, nytrapSessionTime)) and timeframe.isintraday sessionStart = inSession and not inSession if sessionStart sessionHighPrice := high sessionLowPrice := low sessionOpenPrice := open else if inSession sessionHighPrice := math.max(sessionHighPrice, high) sessionLowPrice := math.min(sessionLowPrice, low) if sessionStart sessionBox := box.new(left=bar_index, top=na, right=bar_index+nytrapOffs, bottom=na, border_color = color.new(#ffffff, 100), bgcolor=nytrapBoxColor) sessionTopLine := line.new(x1= bar_index, y1=na, x2=bar_index+nytrapOffs, y2=na, style=line.style_solid, width=0) sessionLowLine := line.new(x1= bar_index, y1=na, x2=bar_index+nytrapOffs, y2=na, style=line.style_solid, width=0) if inSession box.set_top(sessionBox, sessionHighPrice) box.set_bottom(sessionBox, sessionLowPrice) box.set_top(sessionBox, sessionHighPrice) box.set_bottom(sessionBox, sessionLowPrice) var GRPFF = 'Frankfurt Session' ffsession = '0200-0201' ffcolor = input.color(color.new(#787b86, 70), title='Line color', group=GRPFF) var GRPMMM1 = 'Magic Manipulation Minute 1' mmm1time = '0430-0431' mmm1color = input.color(color.new(#787b86, 70), title="Line color",group=GRPMMM1) var GRPMMM2 = 'Magic Manipulation Minute 2' mmm2time = '0630-0631' mmm2color = input.color(color.new(#787b86, 70), title="Line color", group=GRPMMM2) var GRPNYO = 'New York Open' nyosession = '0800-0801' nyocolor = input.color(color.new(#787b86, 70),title="Line color", group=GRPNYO) var GRPLC = 'London Close' lcsession = '1100-1101' lccolor = input.color(color.new(#787b86, 0),title="Line color", group=GRPLC) asiansize = (high_val-low_val)/4 in_session_ff = time(timeframe.period, ffsession) sessionffActive = in_session_ff and timeframe.multiplier <= 15 var line ff = na if sessionffActive and sessionffActive == false ff := line.new(bar_index, high+asiansize, bar_index, low-asiansize, color=ffcolor, style=line.style_solid) in_session_mmm1 = time(timeframe.period, mmm1time) sessionmmm1Active = in_session_mmm1 and timeframe.multiplier <= 15 var line mmm1 = na if sessionmmm1Active and sessionmmm1Active == false mmm1 := line.new(bar_index, high+asiansize, bar_index, low-asiansize, color=mmm1color, style=line.style_solid) in_session_mmm2 = time(timeframe.period, mmm2time) sessionmmm2Active = in_session_mmm2 and timeframe.multiplier <= 15 var line mmm2 = na if sessionmmm2Active and sessionmmm2Active == false mmm2 := line.new(bar_index, high+asiansize, bar_index, low-asiansize, color=mmm2color, style=line.style_solid) in_session_nyo = time(timeframe.period, nyosession) sessionnyoActive = in_session_nyo and timeframe.multiplier <= 15 var line nyo = na if sessionnyoActive and sessionnyoActive == false nyo := line.new(bar_index, high+asiansize, bar_index, low-asiansize, color=nyocolor, style=line.style_solid) in_session_lc = time(timeframe.period, lcsession) sessionlcActive = in_session_lc and timeframe.multiplier <= 15 var line lc = na if sessionlcActive and sessionlcActive == false lc := line.new(bar_index, high+asiansize, bar_index, low-asiansize, color=lccolor, style=line.style_solid)
Pine Script® göstergesi
AttilaLukacs tarafından
1
10 EMA -3*ATRThis custom indicator plots the line calculated as 10-period Exponential Moving Average (EMA) minus 3 times the 14-period Average True Range (ATR). It helps traders identify dynamic support levels or pullback zones during strong trends by adjusting for market volatility. A falling line may signal increasing volatility or weakening momentum, while a rising line may indicate strengthening trend stability. Suitable for trend-following strategies and volatility-aware entries.
Pine Script® göstergesi
KPLTrader tarafından
OBV PanelOBV Panel – Volume-Based Price Prediction & Signal Dashboard Powered by Pine Script v6 🔍 Overview This multi-functional indicator is designed around the On-Balance Volume (OBV) concept, enhancing it with prediction models, trend tracking, and actionable buy/sell signals. It uses a combination of real-time OBV movement, smoothed OBV with EMA, and linear regression-based OBV forecasts to deliver both intraday and weekly insights — all neatly displayed in a table panel and directly plotted on your chart. ⚙️ Core Components 📌 1. OBV Core OBV is calculated based on volume flowing into or out of a stock as price moves up or down. Tracks raw OBV and its EMA (Exponential Moving Average) for smoother trend reading. Computes a Predicted OBV using Linear Regression (ta.linreg) over a user-defined number of bars. 🔮 2. Predicted Price Forecast Uses OBV percentage changes combined with a user-set sensitivity factor to project next day’s expected price. Offers an AI-style price forecast based on OBV strength, not just price action. 💹 3. Buy/Sell Signal Logic Daily Signals: Triggered when OBV, OBV EMA, and Predicted OBV all move upward or downward from the previous day. Weekly Signals: Based on EMA changes over a 5-bar period (approx. 1 week). Signal markers are drawn on the chart for visual reference. 📊 Table Panel (Top-Right Overlay) A detailed visual panel shows: Metric Description OBV, OBV EMA, Predicted OBV From previous close to current value OBV - Predicted OBV Difference In lakhs (scaled for readability) % Change Stats Daily percentage change in OBV, EMA, and Predicted OBV Weekly OBV EMA Change Actual & % change over 5 bars Signal Summary BUY/SELL or HOLD based on logic OBV Dominance Whether OBV > EMA and Predicted OBV Predicted Price (Next Day) Based on OBV dynamics and sensitivity
Pine Script® göstergesi
raghavprakash05 tarafından
CODEX#33CODEX#33 is a dynamic EMA-based system designed to visualize trend strength, volatility, and key market zones. It includes: 5 customizable EMAs (13, 21, 50, 200, 800) Optional labels with future offset to keep charts clean An EMA 50-based volatility cloud using standard deviation Full control over visibility, colors, and label display Built for clean execution and easy visual tracking of momentum shifts across all timeframes. Simplicity is key!
Pine Script® göstergesi
Phulays tarafından
Market Zone Analyzer[BullByte]Understanding the Market Zone Analyzer --- 1. Purpose of the Indicator The Market Zone Analyzer is a Pine Script™ (version 6) indicator designed to streamline market analysis on TradingView. Rather than scanning multiple separate tools, it unifies four core dimensions—trend strength, momentum, price action, and market activity—into a single, consolidated view. By doing so, it helps traders: • Save time by avoiding manual cross-referencing of disparate signals. • Reduce decision-making errors that can arise from juggling multiple indicators. • Gain a clear, reliable read on whether the market is in a bullish, bearish, or sideways phase, so they can more confidently decide to enter, exit, or hold a position. --- 2. Why a Trader Should Use It • Unified View: Combines all essential market dimensions into one easy-to-read score and dashboard, eliminating the need to piece together signals manually. • Adaptability: Automatically adjusts its internal weighting for trend, momentum, and price action based on current volatility. Whether markets are choppy or calm, the indicator remains relevant. • Ease of Interpretation: Outputs a simple “BULLISH,” “BEARISH,” or “SIDEWAYS” label, supplemented by an intuitive on-chart dashboard and an oscillator plot that visually highlights market direction. • Reliability Features: Built-in smoothing of the net score and hysteresis logic (requiring consecutive confirmations before flips) minimize false signals during noisy or range-bound phases. --- 3. Why These Specific Indicators? This script relies on a curated set of well-established technical tools, each chosen for its particular strength in measuring one of the four core dimensions: 1. Trend Strength: • ADX/DMI (Average Directional Index / Directional Movement Index): Measures how strong a trend is, and whether the +DI line is above the –DI line (bullish) or vice versa (bearish). • Moving Average Slope (Fast MA vs. Slow MA): Compares a shorter-period SMA to a longer-period SMA; if the fast MA sits above the slow MA, it confirms an uptrend, and vice versa for a downtrend. • Ichimoku Cloud Differential (Senkou A vs. Senkou B): Provides a forward-looking view of trend direction; Senkou A above Senkou B signals bullishness, and the opposite signals bearishness. 2. Momentum: • Relative Strength Index (RSI): Identifies overbought (above its dynamically calculated upper bound) or oversold (below its lower bound) conditions; changes in RSI often precede price reversals. • Stochastic %K: Highlights shifts in short-term momentum by comparing closing price to the recent high/low range; values above its upper band signal bullish momentum, below its lower band signal bearish momentum. • MACD Histogram: Measures the difference between the MACD line and its signal line; a positive histogram indicates upward momentum, a negative histogram indicates downward momentum. 3. Price Action: • Highest High / Lowest Low (HH/LL) Range: Over a defined lookback period, this captures breakout or breakdown levels. A closing price near the recent highs (with a positive MA slope) yields a bullish score, and near the lows (with a negative MA slope) yields a bearish score. • Heikin-Ashi Doji Detection: Uses Heikin-Ashi candles to identify indecision or continuation patterns. A small Heikin-Ashi body (doji) relative to recent volatility is scored as neutral; a larger body in the direction of the MA slope is scored bullish or bearish. • Candle Range Measurement: Compares each candle’s high-low range against its own dynamic band (average range ± standard deviation). Large candles aligning with the prevailing trend score bullish or bearish accordingly; unusually small candles can indicate exhaustion or consolidation. 4. Market Activity: • Bollinger Bands Width (BBW): Measures the distance between BB upper and lower bands; wide bands indicate high volatility, narrow bands indicate low volatility. • Average True Range (ATR): Quantifies average price movement (volatility). A sudden spike in ATR suggests a volatile environment, while a contraction suggests calm. • Keltner Channels Width (KCW): Similar to BBW but uses ATR around an EMA. Provides a second layer of volatility context, confirming or contrasting BBW readings. • Volume (with Moving Average): Compares current volume to its moving average ± standard deviation. High volume validates strong moves; low volume signals potential lack of conviction. By combining these tools, the indicator captures trend direction, momentum strength, price-action nuances, and overall market energy, yielding a more balanced and comprehensive assessment than any single tool alone. --- 4. What Makes This Indicator Stand Out • Multi-Dimensional Analysis: Rather than relying on a lone oscillator or moving average crossover, it simultaneously evaluates trend, momentum, price action, and activity. • Dynamic Weighting: The relative importance of trend, momentum, and price action adjusts automatically based on real-time volatility (Market Activity State). For example, in highly volatile conditions, trend and momentum signals carry more weight; in calm markets, price action signals are prioritized. • Stability Mechanisms: • Smoothing: The net score is passed through a short moving average, filtering out noise, especially on lower timeframes. • Hysteresis: Both Market Activity State and the final bullish/bearish/sideways zone require two consecutive confirmations before flipping, reducing whipsaw. • Visual Interpretation: A fully customizable on-chart dashboard displays each sub-indicator’s value, regime, score, and comment, all color-coded. The oscillator plot changes color to reflect the current market zone (green for bullish, red for bearish, gray for sideways) and shows horizontal threshold lines at +2, 0, and –2. --- 5. Recommended Timeframes • Short-Term (5 min, 15 min): Day traders and scalpers can benefit from rapid signals, but should enable smoothing (and possibly disable hysteresis) to reduce false whipsaws. • Medium-Term (1 h, 4 h): Swing traders find a balance between responsiveness and reliability. Less smoothing is required here, and the default parameters (e.g., ADX length = 14, RSI length = 14) perform well. • Long-Term (Daily, Weekly): Position traders tracking major trends can disable smoothing for immediate raw readings, since higher-timeframe noise is minimal. Adjust lookback lengths (e.g., increase adxLength, rsiLength) if desired for slower signals. Tip: If you keep smoothing off, stick to timeframes of 1 h or higher to avoid excessive signal “chatter.” --- 6. How Scoring Works A. Individual Indicator Scores Each sub-indicator is assigned one of three discrete scores: • +1 if it indicates a bullish condition (e.g., RSI above its dynamically calculated upper bound). • 0 if it is neutral (e.g., RSI between upper and lower bounds). • –1 if it indicates a bearish condition (e.g., RSI below its dynamically calculated lower bound). Examples of individual score assignments: • ADX/DMI: • +1 if ADX ≥ adxThreshold and +DI > –DI (strong bullish trend) • –1 if ADX ≥ adxThreshold and –DI > +DI (strong bearish trend) • 0 if ADX < adxThreshold (trend strength below threshold) • RSI: • +1 if RSI > RSI_upperBound • –1 if RSI < RSI_lowerBound • 0 otherwise • ATR (as part of Market Activity): • +1 if ATR > (ATR_MA + stdev(ATR)) • –1 if ATR < (ATR_MA – stdev(ATR)) • 0 otherwise Each of the four main categories shares this same +1/0/–1 logic across their sub-components. B. Category Scores Once each sub-indicator reports +1, 0, or –1, these are summed within their categories as follows: • Trend Score = (ADX score) + (MA slope score) + (Ichimoku differential score) • Momentum Score = (RSI score) + (Stochastic %K score) + (MACD histogram score) • Price Action Score = (Highest-High/Lowest-Low score) + (Heikin-Ashi doji score) + (Candle range score) • Market Activity Raw Score = (BBW score) + (ATR score) + (KC width score) + (Volume score) Each category’s summed value can range between –3 and +3 (for Trend, Momentum, and Price Action), and between –4 and +4 for Market Activity raw. C. Market Activity State and Dynamic Weight Adjustments Rather than contributing directly to the netScore like the other three categories, Market Activity determines how much weight to assign to Trend, Momentum, and Price Action: 1. Compute Market Activity Raw Score by summing BBW, ATR, KCW, and Volume individual scores (each +1/0/–1). 2. Bucket into High, Medium, or Low Activity: • High if raw Score ≥ 2 (volatile market). • Low if raw Score ≤ –2 (calm market). • Medium otherwise. 3. Apply Hysteresis (if enabled): The state only flips after two consecutive bars register the same high/low/medium label. 4. Set Category Weights: • High Activity: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Low Activity: Trend = 25 %, Momentum = 20 %, Price Action = 55 %. • Medium Activity: Use the trader’s base weight inputs (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 % by default). D. Calculating the Net Score 5. Normalize Base Weights (so that the sum of Trend + Momentum + Price Action always equals 100 %). 6. Determine Current Weights based on the Market Activity State (High/Medium/Low). 7. Compute Each Category’s Contribution: Multiply (categoryScore) × (currentWeight). 8. Sum Contributions to get the raw netScore (a floating-point value that can exceed ±3 when scores are strong). 9. Smooth the netScore over two bars (if smoothing is enabled) to reduce noise. 10. Apply Hysteresis to the Final Zone: • If the smoothed netScore ≥ +2, the bar is classified as “Bullish.” • If the smoothed netScore ≤ –2, the bar is classified as “Bearish.” • Otherwise, it is “Sideways.” • To prevent rapid flips, the script requires two consecutive bars in the new zone before officially changing the displayed zone (if hysteresis is on). E. Thresholds for Zone Classification • BULLISH: netScore ≥ +2 • BEARISH: netScore ≤ –2 • SIDEWAYS: –2 < netScore < +2 --- 7. Role of Volatility (Market Activity State) in Scoring Volatility acts as a dynamic switch that shifts which category carries the most influence: 1. High Activity (Volatile): • Detected when at least two sub-scores out of BBW, ATR, KCW, and Volume equal +1. • The script sets Trend weight = 50 % and Momentum weight = 35 %. Price Action weight is minimized at 15 %. • Rationale: In volatile markets, strong trending moves and momentum surges dominate, so those signals are more reliable than nuanced candle patterns. 2. Low Activity (Calm): • Detected when at least two sub-scores out of BBW, ATR, KCW, and Volume equal –1. • The script sets Price Action weight = 55 %, Trend = 25 %, and Momentum = 20 %. • Rationale: In quiet, sideways markets, subtle price-action signals (breakouts, doji patterns, small-range candles) are often the best early indicators of a new move. 3. Medium Activity (Balanced): • Raw Score between –1 and +1 from the four volatility metrics. • Uses whatever base weights the trader has specified (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 %). Because volatility can fluctuate rapidly, the script employs hysteresis on Market Activity State: a new High or Low state must occur on two consecutive bars before weights actually shift. This avoids constant back-and-forth weight changes and provides more stability. --- 8. Scoring Example (Hypothetical Scenario) • Symbol: Bitcoin on a 1-hour chart. • Market Activity: Raw volatility sub-scores show BBW (+1), ATR (+1), KCW (0), Volume (+1) → Total raw Score = +3 → High Activity. • Weights Selected: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Trend Signals: • ADX strong and +DI > –DI → +1 • Fast MA above Slow MA → +1 • Ichimoku Senkou A > Senkou B → +1 → Trend Score = +3 • Momentum Signals: • RSI above upper bound → +1 • MACD histogram positive → +1 • Stochastic %K within neutral zone → 0 → Momentum Score = +2 • Price Action Signals: • Highest High/Lowest Low check yields 0 (close not near extremes) • Heikin-Ashi doji reading is neutral → 0 • Candle range slightly above upper bound but trend is strong, so → +1 → Price Action Score = +1 • Compute Net Score (before smoothing): • Trend contribution = 3 × 0.50 = 1.50 • Momentum contribution = 2 × 0.35 = 0.70 • Price Action contribution = 1 × 0.15 = 0.15 • Raw netScore = 1.50 + 0.70 + 0.15 = 2.35 • Since 2.35 ≥ +2 and hysteresis is met, the final zone is “Bullish.” Although the netScore lands at 2.35 (Bullish), smoothing might bring it slightly below 2.00 on the first bar (e.g., 1.90), in which case the script would wait for a second consecutive reading above +2 before officially classifying the zone as Bullish (if hysteresis is enabled). --- 9. Correlation Between Categories The four categories—Trend Strength, Momentum, Price Action, and Market Activity—often reinforce or offset one another. The script takes advantage of these natural correlations: • Bullish Alignment: If ADX is strong and pointed upward, fast MA is above slow MA, and Ichimoku is positive, that usually coincides with RSI climbing above its upper bound and the MACD histogram turning positive. In such cases, both Trend and Momentum categories generate +1 or +2. Because the Market Activity State is likely High (given the accompanying volatility), Trend and Momentum weights are at their peak, so the netScore quickly crosses into Bullish territory. • Sideways/Consolidation: During a low-volatility, sideways phase, ADX may fall below its threshold, MAs may flatten, and RSI might hover in the neutral band. However, subtle price-action signals (like a small breakout candle or a Heikin-Ashi candle with a slight bias) can still produce a +1 in the Price Action category. If Market Activity is Low, Price Action’s weight (55 %) can carry enough influence—even if Trend and Momentum are neutral—to push the netScore out of “Sideways” into a mild bullish or bearish bias. • Opposing Signals: When Trend is bullish but Momentum turns negative (for example, price continues up but RSI rolls over), the two scores can partially cancel. Market Activity may remain Medium, in which case the netScore lingers near zero (Sideways). The trader can then wait for either a clearer momentum shift or a fresh price-action breakout before committing. By dynamically recognizing these correlations and adjusting weights, the indicator ensures that: • When Trend and Momentum align (and volatility supports it), the netScore leaps strongly into Bullish or Bearish. • When Trend is neutral but Price Action shows an early move in a low-volatility environment, Price Action’s extra weight in the Low Activity State can still produce actionable signals. --- 10. Market Activity State & Its Role (Detailed) The Market Activity State is not a direct category score—it is an overarching context setter for how heavily to trust Trend, Momentum, or Price Action. Here’s how it is derived and applied: 1. Calculate Four Volatility Sub-Scores: • BBW: Compare the current band width to its own moving average ± standard deviation. If BBW > (BBW_MA + stdev), assign +1 (high volatility); if BBW < (BBW_MA × 0.5), assign –1 (low volatility); else 0. • ATR: Compare ATR to its moving average ± standard deviation. A spike above the upper threshold is +1; a contraction below the lower threshold is –1; otherwise 0. • KCW: Same logic as ATR but around the KCW mean. • Volume: Compare current volume to its volume MA ± standard deviation. Above the upper threshold is +1; below the lower threshold is –1; else 0. 2. Sum Sub-Scores → Raw Market Activity Score: Range between –4 and +4. 3. Assign Market Activity State: • High Activity: Raw Score ≥ +2 (at least two volatility metrics are strongly spiking). • Low Activity: Raw Score ≤ –2 (at least two metrics signal unusually low volatility or thin volume). • Medium Activity: Raw Score is between –1 and +1 inclusive. 4. Hysteresis for Stability: • If hysteresis is enabled, a new state only takes hold after two consecutive bars confirm the same High, Medium, or Low label. • This prevents the Market Activity State from bouncing around when volatility is on the fence. 5. Set Category Weights Based on Activity State: • High Activity: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Low Activity: Trend = 25 %, Momentum = 20 %, Price Action = 55 %. • Medium Activity: Use trader’s base weights (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 %). 6. Impact on netScore: Because category scores (–3 to +3) multiply by these weights, High Activity amplifies the effect of strong Trend and Momentum scores; Low Activity amplifies the effect of Price Action. 7. Market Context Tooltip: The dashboard includes a tooltip summarizing the current state—e.g., “High activity, trend and momentum prioritized,” “Low activity, price action prioritized,” or “Balanced market, all categories considered.” --- 11. Category Weights: Base vs. Dynamic Traders begin by specifying base weights for Trend Strength, Momentum, and Price Action that sum to 100 %. These apply only when volatility is in the Medium band. Once volatility shifts: • High Volatility Overrides: • Trend jumps from its base (e.g., 40 %) to 50 %. • Momentum jumps from its base (e.g., 30 %) to 35 %. • Price Action is reduced to 15 %. Example: If base weights were Trend = 40 %, Momentum = 30 %, Price Action = 30 %, then in High Activity they become 50/35/15. A Trend score of +3 now contributes 3 × 0.50 = +1.50 to netScore; a Momentum +2 contributes 2 × 0.35 = +0.70. In total, Trend + Momentum can easily push netScore above the +2 threshold on its own. • Low Volatility Overrides: • Price Action leaps from its base (30 %) to 55 %. • Trend falls to 25 %, Momentum falls to 20 %. Why? When markets are quiet, subtle candle breakouts, doji patterns, and small-range expansions tend to foreshadow the next swing more effectively than raw trend readings. A Price Action score of +3 in this state contributes 3 × 0.55 = +1.65, which can carry the netScore toward +2—even if Trend and Momentum are neutral or only mildly positive. Because these weight shifts happen only after two consecutive bars confirm a High or Low state (if hysteresis is on), the indicator avoids constantly flipping its emphasis during borderline volatility phases. --- 12. Dominant Category Explained Within the dashboard, a label such as “Trend Dominant,” “Momentum Dominant,” or “Price Action Dominant” appears when one category’s absolute weighted contribution to netScore is the largest. Concretely: • Compute each category’s weighted contribution = (raw category score) × (current weight). • Compare the absolute values of those three contributions. • The category with the highest absolute value is flagged as Dominant for that bar. Why It Matters: • Momentum Dominant: Indicates that the combined force of RSI, Stochastic, and MACD (after weighting) is pushing netScore farther than either Trend or Price Action. In practice, it means that short-term sentiment and speed of change are the primary drivers right now, so traders should watch for continued momentum signals before committing to a trade. • Trend Dominant: Means ADX, MA slope, and Ichimoku (once weighted) outweigh the other categories. This suggests a strong directional move is in place; trend-following entries or confirming pullbacks are likely to succeed. • Price Action Dominant: Occurs when breakout/breakdown patterns, Heikin-Ashi candle readings, and range expansions (after weighting) are the most influential. This often happens in calmer markets, where subtle shifts in candle structure can foreshadow bigger moves. By explicitly calling out which category is carrying the most weight at any moment, the dashboard gives traders immediate insight into why the netScore is tilting toward bullish, bearish, or sideways. --- 13. Oscillator Plot: How to Read It The “Net Score” oscillator sits below the dashboard and visually displays the smoothed netScore as a line graph. Key features: 1. Value Range: In normal conditions it oscillates roughly between –3 and +3, but extreme confluences can push it outside that range. 2. Horizontal Threshold Lines: • +2 Line (Bullish threshold) • 0 Line (Neutral midline) • –2 Line (Bearish threshold) 3. Zone Coloring: • Green Background (Bullish Zone): When netScore ≥ +2. • Red Background (Bearish Zone): When netScore ≤ –2. • Gray Background (Sideways Zone): When –2 < netScore < +2. 4. Dynamic Line Color: • The plotted netScore line itself is colored green in a Bullish Zone, red in a Bearish Zone, or gray in a Sideways Zone, creating an immediate visual cue. Interpretation Tips: • Crossing Above +2: Signals a strong enough combined trend/momentum/price-action reading to classify as Bullish. Many traders wait for a clear crossing plus a confirmation candle before entering a long position. • Crossing Below –2: Indicates a strong Bearish signal. Traders may consider short or exit strategies. • Rising Slope, Even Below +2: If netScore climbs steadily from neutral toward +2, it demonstrates building bullish momentum. • Divergence: If price makes a higher high but the oscillator fails to reach a new high, it can warn of weakening momentum and a potential reversal. --- 14. Comments and Their Necessity Every sub-indicator (ADX, MA slope, Ichimoku, RSI, Stochastic, MACD, HH/LL, Heikin-Ashi, Candle Range, BBW, ATR, KCW, Volume) generates a short comment that appears in the detailed dashboard. Examples: • “Strong bullish trend” or “Strong bearish trend” for ADX/DMI • “Fast MA above slow MA” or “Fast MA below slow MA” for MA slope • “RSI above dynamic threshold” or “RSI below dynamic threshold” for RSI • “MACD histogram positive” or “MACD histogram negative” for MACD Hist • “Price near highs” or “Price near lows” for HH/LL checks • “Bullish Heikin Ashi” or “Bearish Heikin Ashi” for HA Doji scoring • “Large range, trend confirmed” or “Small range, trend contradicted” for Candle Range Additionally, the top-row comment for each category is: • Trend: “Highly Bullish,” “Highly Bearish,” or “Neutral Trend.” • Momentum: “Strong Momentum,” “Weak Momentum,” or “Neutral Momentum.” • Price Action: “Bullish Action,” “Bearish Action,” or “Neutral Action.” • Market Activity: “Volatile Market,” “Calm Market,” or “Stable Market.” Reasons for These Comments: • Transparency: Shows exactly how each sub-indicator contributed to its category score. • Education: Helps traders learn why a category is labeled bullish, bearish, or neutral, building intuition over time. • Customization: If, for example, the RSI comment says “RSI neutral” despite an impending trend shift, a trader might choose to adjust RSI length or thresholds. In the detailed dashboard, hovering over each comment cell also reveals a tooltip with additional context (e.g., “Fast MA above slow MA” or “Senkou A above Senkou B”), helping traders understand the precise rule behind that +1, 0, or –1 assignment. --- 15. Real-Life Example (Consolidated) • Instrument & Timeframe: Bitcoin (BTCUSD), 1-hour chart. • Current Market Activity: BBW and ATR both spike (+1 each), KCW is moderately high (+1), but volume is only neutral (0) → Raw Market Activity Score = +2 → State = High Activity (after two bars, if hysteresis is on). • Category Weights Applied: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Trend Sub-Scores: 1. ADX = 25 (above threshold 20) with +DI > –DI → +1. 2. Fast MA (20-period) sits above Slow MA (50-period) → +1. 3. Ichimoku: Senkou A > Senkou B → +1. → Trend Score = +3. • Momentum Sub-Scores: 4. RSI = 75 (above its moving average +1 stdev) → +1. 5. MACD histogram = +0.15 → +1. 6. Stochastic %K = 50 (mid-range) → 0. → Momentum Score = +2. • Price Action Sub-Scores: 7. Price is not within 1 % of the 20-period high/low and slope = positive → 0. 8. Heikin-Ashi body is slightly larger than stdev over last 5 bars with haClose > haOpen → +1. 9. Candle range is just above its dynamic upper bound but trend is already captured, so → +1. → Price Action Score = +2. • Calculate netScore (before smoothing): • Trend contribution = 3 × 0.50 = 1.50 • Momentum contribution = 2 × 0.35 = 0.70 • Price Action contribution = 2 × 0.15 = 0.30 • Raw netScore = 1.50 + 0.70 + 0.30 = 2.50 → Immediately classified as Bullish. • Oscillator & Dashboard Output: • The oscillator line crosses above +2 and turns green. • Dashboard displays: • Trend Regime “BULLISH,” Trend Score = 3, Comment = “Highly Bullish.” • Momentum Regime “BULLISH,” Momentum Score = 2, Comment = “Strong Momentum.” • Price Action Regime “BULLISH,” Price Action Score = 2, Comment = “Bullish Action.” • Market Activity State “High,” Comment = “Volatile Market.” • Weights: Trend 50 %, Momentum 35 %, Price Action 15 %. • Dominant Category: Trend (because 1.50 > 0.70 > 0.30). • Overall Score: 2.50, posCount = (three +1s in Trend) + (two +1s in Momentum) + (two +1s in Price Action) = 7 bullish signals, negCount = 0. • Final Zone = “BULLISH.” • The trader sees that both Trend and Momentum are reinforcing each other under high volatility. They might wait one more candle for confirmation but already have strong evidence to consider a long. --- • . --- Disclaimer This indicator is strictly a technical analysis tool and does not constitute financial advice. All trading involves risk, including potential loss of capital. Past performance is not indicative of future results. Traders should: • Always backtest the “Market Zone Analyzer ” on their chosen symbols and timeframes before committing real capital. • Combine this tool with sound risk management, position sizing, and, if possible, fundamental analysis. • Understand that no indicator is foolproof; always be prepared for unexpected market moves. Goodluck -BullByte! ---
Pine Script® göstergesi
BullByte tarafından
2
Golden Key: Opening Channel DashboardGolden Key: Opening Channel Dashboard Complementary to the original Golden Key – The Frequency Upgrade of 10 Monday's 1H Avg Range + 30-Day Daily Range This indicator provides a structured dashboard to monitor the opening channel range and related metrics on 15m and 5m charts. Built to work alongside the Golden Key methodology, it focuses on pip precision, average volatility, and SL sizing. What It Does Detects first 4 candles of the session: 15m chart → first 4 Monday candles (1 hour) 5m chart → first 4 candles of each day (20 minutes) Calculates pip range of the opening move Stores and averages the last 10 such ranges Calculates daily range average over 10 or 30 days Generates SL size based on your multiplier setting Auto-adjusts for FX, JPY, and XAUUSD pip sizes Displays all values in a clean table in the top-right How to Use It Add to a 15m or 5m chart Compare the current opening range to the average Use the daily average to assess broader volatility Define SL size using the opening range x multiplier Customize display colors per table row About This Script This is not a visual box-style indicator. It is designed to complement the original “Golden Key – The Frequency” by focusing on metric output. It is also an upgraded version of the earlier "10 Monday’s 1H Avg Range" script, now supporting multi-timeframe logic and additional customization. Disclaimer This is a technical analysis tool. It does not provide trading advice. Use it in combination with your own research and strategy.
Pine Script® göstergesi
bramirez37 tarafından
FX 2025 - Triple EMA Entrada y Cierre ÚnicaCruce de emas 9/21/50, se recomienda combinar con los indicadores de volumen y macd EMA 9: Represents very short-term price movement. EMA 21: Smoother and shows short-term trend. EMA 50: Reflects the medium-term trend. Common signals: Bullish crossover: When the EMA 9 crosses above the EMA 21 (and preferably also the EMA 50), it’s seen as a buy signal. Bearish crossover: When the EMA 9 crosses below the EMA 21 or 50, it may signal a sell or correction.
Pine Script® göstergesi
DOLLARDRUM tarafından
ML Super Divergence + ADX ConfirmationThe "ML Super Divergence + ADX Confirmation" indicator is a powerful tool designed for technical traders who want to combine machine learning-inspired divergence signals with the ADX (Average Directional Index) trend strength indicator for more reliable trade signals. This script is written in Pine Script v6 and is suitable for use on TradingView charts. It visually highlights potential buy and sell opportunities and also generates alerts when conditions are met. 📈 Core Components: 1. ADX System (Average Directional Index): Measures trend strength, not direction. Calculated using a 14-period (user-configurable) setting. DI+ (Positive Directional Index) and DI− (Negative Directional Index) are used to gauge bullish and bearish pressure. Signals are only valid when ADX > threshold (e.g., 20), ensuring that the trend is strong enough to act upon. 2. Simulated ML Super Divergence Signal: This is a placeholder for actual ML-based divergence detection. For demonstration, it simulates: Bullish divergence: when RSI crosses above 30 and OBV (On-Balance Volume) is rising. Bearish divergence: when RSI crosses below 70 and OBV is falling. This approximation helps visualize how real ML divergence signals could be integrated. ✅ Buy Signal Conditions: A buy signal is plotted when: A bullish divergence is detected. DI+ is greater than DI− (i.e., bullish directional strength). ADX is above the minimum threshold (confirming a strong trend). 📍 Visual cue: Green upward triangle below the price bar. 🔔 Alert Triggered: "Buy Signal: ML Super Divergence + DI+ + ADX Confirmation" ❌ Sell Signal Conditions: A sell signal is plotted when: A bearish divergence is detected. DI− is greater than DI+ (i.e., bearish directional strength). ADX is above the threshold. 📍 Visual cue: Red dot above the price bar. 🔔 Alert Triggered: "Sell Signal: ML Super Divergence + DI- + ADX Confirmation"
Pine Script® göstergesi
raghavprakash05 tarafından
_CM_MacD_Ult_MTF_V2.1//------New V2 Update 07-28-2021---------- //Thanks to @SKTennis for help in Updating code to V2 //Added Groups to Settings Pane. //Added Color Plots to Settings Pane //Switched MTF Logic to turn ON/OFF automatically w/ TradingView's Built in Feature //Updated Color Transparency plots to work in future update //Added Ability to Turn ON/OFF Show MacD & Signal Line //Added Ability to Turn ON/OFF Show Histogram //Added Ability to Change MACD Line Colors Based on Trend //Added Ability to Highlight Price Bars Based on Trend //Added Alerts to Settings Pane. //Customized how Alerts work. Must keep Checked in Settings Pane, and... //When you go to Alerts Panel, Change Symbol to Indicator (CM_Ult_MacD_MTF_V2) //Customized Alerts to Show Symbol, TimeFrame, Closing Price, MACD Crosses Up & MACD Crosses Down Signals in Alert //Alerts are Pre-Set to only Alert on Bar Close //------New V2.1 Update 08-03-2021---------- //Added back in ability to show Dots when MACD Crosses. //Added Ability to Change Plot Widths in Settings Pane //Added in Alert Feature where Cross Up if above 0 or cross down if below 0 (OFF By Default) user Request. @creid58 //FIXED - Plot Orders to Default what Plots are on top of each other //FIXED - Two of the histogrm colors were backwrds //------New V2.1 Update 12-07-2021---------- //Updated to PineScript V5 //------Minor Update 02-16-2022---------- //Per user request...Increased the Maxval for Signal Smoothing //Next Add in Plot Types to Settings Pane. //Next Add in more Moving Average types. //See Video for Detailed Overview //@version=5 indicator(title="_CM_MacD_Ult_MTF_V2.1", shorttitle="_CM_Ult_MacD_MTF_V2.1") //Plot Inputs res = input.timeframe("", "Indicator TimeFrame") fast_length = input.int(title="Fast Length", defval=12) slow_length = input.int(title="Slow Length", defval=26) src = input.source(title="Source", defval=close) signal_length = input.int(title="Signal Smoothing", minval = 1, maxval = 999, defval = 9) sma_source = input.string(title="Oscillator MA Type", defval="EMA", options= ) sma_signal = input.string(title="Signal Line MA Type", defval="EMA", options= ) // Show Plots T/F show_macd = input.bool(true, title="Show MACD Lines", group="Show Plots?", inline="SP10") show_macd_LW = input.int(3, minval=0, maxval=5, title = "MACD Width", group="Show Plots?", inline="SP11") show_signal_LW= input.int(2, minval=0, maxval=5, title = "Signal Width", group="Show Plots?", inline="SP11") show_Hist = input.bool(true, title="Show Histogram", group="Show Plots?", inline="SP20") show_hist_LW = input.int(5, minval=0, maxval=5, title = "-- Width", group="Show Plots?", inline="SP20") show_trend = input.bool(true, title = "Show MACD Lines w/ Trend Color", group="Show Plots?", inline="SP30") show_HB = input.bool(false, title="Show Highlight Price Bars", group="Show Plots?", inline="SP40") show_cross = input.bool(false, title = "Show BackGround on Cross", group="Show Plots?", inline="SP50") show_dots = input.bool(true, title = "Show Circle on Cross", group="Show Plots?", inline="SP60") show_dots_LW = input.int(5, minval=0, maxval=5, title = "-- Width", group="Show Plots?", inline="SP60") //show_trend = input(true, title = "Colors MACD Lines w/ Trend Color", group="Show Plots?", inline="SP5") // MACD Lines colors col_macd = input.color(#FF6D00, "MACD Line  ", group="Color Settings", inline="CS1") col_signal = input.color(#2962FF, "Signal Line  ", group="Color Settings", inline="CS1") col_trnd_Up = input.color(#4BAF4F, "Trend Up      ", group="Color Settings", inline="CS2") col_trnd_Dn = input.color(#B71D1C, "Trend Down    ", group="Color Settings", inline="CS2") // Histogram Colors col_grow_above = input.color(#26A69A, "Above   Grow", group="Histogram Colors", inline="Hist10") col_fall_above = input.color(#B2DFDB, "Fall", group="Histogram Colors", inline="Hist10") col_grow_below = input.color(#FF5252, "Below Grow", group="Histogram Colors", inline="Hist20") col_fall_below = input.color(#FFCDD2, "Fall", group="Histogram Colors", inline="Hist20") // Alerts T/F Inputs alert_Long = input.bool(true, title = "MACD Cross Up", group = "Alerts", inline="Alert10") alert_Short = input.bool(true, title = "MACD Cross Dn", group = "Alerts", inline="Alert10") alert_Long_A = input.bool(false, title = "MACD Cross Up & > 0", group = "Alerts", inline="Alert20") alert_Short_B = input.bool(false, title = "MACD Cross Dn & < 0", group = "Alerts", inline="Alert20") // Calculating fast_ma = request.security(syminfo.tickerid, res, sma_source == "SMA" ? ta.sma(src, fast_length) : ta.ema(src, fast_length)) slow_ma = request.security(syminfo.tickerid, res, sma_source == "SMA" ? ta.sma(src, slow_length) : ta.ema(src, slow_length)) macd = fast_ma - slow_ma signal = request.security(syminfo.tickerid, res, sma_signal == "SMA" ? ta.sma(macd, signal_length) : ta.ema(macd, signal_length)) hist = macd - signal // MACD Trend and Cross Up/Down conditions trend_up = macd > signal trend_dn = macd < signal cross_UP = signal >= macd and signal < macd cross_DN = signal <= macd and signal > macd cross_UP_A = (signal >= macd and signal < macd) and macd > 0 cross_DN_B = (signal <= macd and signal > macd) and macd < 0 // Condition that changes Color of MACD Line if Show Trend is turned on.. trend_col = show_trend and trend_up ? col_trnd_Up : trend_up ? col_macd : show_trend and trend_dn ? col_trnd_Dn: trend_dn ? col_macd : na //Var Statements for Histogram Color Change var bool histA_IsUp = false var bool histA_IsDown = false var bool histB_IsDown = false var bool histB_IsUp = false histA_IsUp := hist == hist ? histA_IsUp : hist > hist and hist > 0 histA_IsDown := hist == hist ? histA_IsDown : hist < hist and hist > 0 histB_IsDown := hist == hist ? histB_IsDown : hist < hist and hist <= 0 histB_IsUp := hist == hist ? histB_IsUp : hist > hist and hist <= 0 hist_col = histA_IsUp ? col_grow_above : histA_IsDown ? col_fall_above : histB_IsDown ? col_grow_below : histB_IsUp ? col_fall_below :color.silver // Plot Statements //Background Color bgcolor(show_cross and cross_UP ? col_trnd_Up : na, editable=false) bgcolor(show_cross and cross_DN ? col_trnd_Dn : na, editable=false) //Highlight Price Bars barcolor(show_HB and trend_up ? col_trnd_Up : na, title="Trend Up", offset = 0, editable=false) barcolor(show_HB and trend_dn ? col_trnd_Dn : na, title="Trend Dn", offset = 0, editable=false) //Regular Plots plot(show_Hist and hist ? hist : na, title="Histogram", style=plot.style_columns, color=color.new(hist_col ,0),linewidth=show_hist_LW) plot(show_macd and signal ? signal : na, title="Signal", color=color.new(col_signal, 0), style=plot.style_line ,linewidth=show_signal_LW) plot(show_macd and macd ? macd : na, title="MACD", color=color.new(trend_col, 0), style=plot.style_line ,linewidth=show_macd_LW) hline(0, title="0 Line", color=color.new(color.gray, 0), linestyle=hline.style_dashed, linewidth=1, editable=false) plot(show_dots and cross_UP ? macd : na, title="Dots", color=color.new(trend_col ,0), style=plot.style_circles, linewidth=show_dots_LW, editable=false) plot(show_dots and cross_DN ? macd : na, title="Dots", color=color.new(trend_col ,0), style=plot.style_circles, linewidth=show_dots_LW, editable=false) //Alerts if alert_Long and cross_UP alert("Symbol = (" + syminfo.tickerid + ") TimeFrame = (" + timeframe.period + ") Current Price (" + str.tostring(close) + ") MACD Crosses Up.", alert.freq_once_per_bar_close) if alert_Short and cross_DN alert("Symbol = (" + syminfo.tickerid + ") TimeFrame = (" + timeframe.period + ") Current Price (" + str.tostring(close) + ") MACD Crosses Down.", alert.freq_once_per_bar_close) //Alerts - Stricter Condition - Only Alerts When MACD Crosses UP & MACD > 0 -- Crosses Down & MACD < 0 if alert_Long_A and cross_UP_A alert("Symbol = (" + syminfo.tickerid + ") TimeFrame = (" + timeframe.period + ") Current Price (" + str.tostring(close) + ") MACD > 0 And Crosses Up.", alert.freq_once_per_bar_close) if alert_Short_B and cross_DN_B alert("Symbol = (" + syminfo.tickerid + ") TimeFrame = (" + timeframe.period + ") Current Price (" + str.tostring(close) + ") MACD < 0 And Crosses Down.", alert.freq_once_per_bar_close) //End Code
Pine Script® göstergesi
aaamaaaam255 tarafından