지금 시작

밴드 및 채널

Volatility Expansion Indicator - D_QuantVolatility Expansion Indicator - D_Quant |V|C|E| 1. Concept & Overview The Volatility Expansion Indicator (VCE) is a composite quantitative tool designed to identify robust trend states by aggregating signals from three distinct market dimensions: Relative Position (Volatility), Cyclical Momentum, and Price Velocity. Unlike single-source indicators which often generate false positives during choppy markets, the VCE utilizes a "Consensus Engine." It normalizes signals from Bollinger %B, CCI, and ROC into a unified trend score (-1 to +1). This score drives the visual coloring of the price action and background, allowing traders to instantly gauge whether the market is in a state of volatility expansion (trending) or contraction (ranging). 2. Methodology & Calculation The core logic relies on a weighted aggregation of three technical components. Users can toggle these components on or off in the settings to isolate specific market mechanics. A. Component 1: Bollinger %B (Relative Positioning) Logic: Measures where the price is located relative to the Bollinger Bands. Bullish Condition: If %B > 0.5 (Price is operating in the upper hemisphere of the bands). Bearish Condition: If %B < 0.0 (Price has broken below the lower band). Purpose: Filters out weak trends by ensuring price is statistically significant relative to its recent volatility. B. Component 2: CCI (Commodity Channel Index) Logic: Measures current price levels relative to an average price level over a specific period. Thresholds: A standard +100 / -100 threshold is used. Values above 100 add to the bullish score; values below -100 add to the bearish score. Purpose: Identifies cyclical momentum extremes. f_cci(_len) => cci_val = ta.cci(close, _len) val = 0 if cci_val > 100 val := 1 if cci_val < -100 val := -1 val C. Component 3: ROC (Rate of Change) Logic: Calculates the percentage change between the current price and the price n periods ago. Thresholds: Simple zero-line crossover. Positive ROC implies bullish velocity; negative implies bearish. Purpose: Provides a raw directional bias based on pure price speed. D. The Aggregation Engine: The script sums the active signals and divides by the number of active components. Bullish Trend: Composite Score > 0 (Visualized as Deep Navy). Bearish/Neutral: Composite Score ≤ 0 (Visualized as White). E. Multi-Timeframe (MTF) Capability: The indicator includes a request.security module. This allows you to calculate the consensus trend on a higher timeframe (e.g., Daily) while viewing price action on a lower timeframe (e.g., 15-minute), ensuring you are trading in alignment with the macro trend. // NEW: Timeframe Selection tf_input = input.timeframe("", "VCE Timeframe", group=grp_sets, tooltip="Empty = Current Chart. Set to 'D' for fixed Daily trend.") = request.security(syminfo.tickerid, tf_input, , lookahead=barmerge.lookahead_on) 3. Visualizations The indicator overlays the following elements on the chart: Trend SMMA: A central Smoothed Moving Average (SMMA 20) representing the mean. Volatility Bands: Upper and Lower bands calculated at 2 Standard Deviations from the SMMA. Bar Coloring: Navy Blue: Indicates a confirmed Volatility Expansion (Bullish Confluence). White: Indicates Neutrality, Retracement, or Bearish conditions. Dynamic Fills: The space between the bands fills with color to highlight the strength of the current regime. 4. How to Use Trend Following: Look for the bar color to switch to Navy. This indicates that momentum, volatility, and velocity have aligned bullishly. This is often an entry trigger for long positions. Exits: When the bars switch from Navy back to White/Gray, the volatility expansion has ceased or momentum is diverging. This serves as a warning to tighten stops or take profits. MTF Filter: Set the "VCE Timeframe" input to "D" (Daily). Trade on the H1 chart. Only take long positions when the Daily VCE paints the background/bands in the Bullish color. 5. Settings Bollinger %B: Adjust Length and Multiplier (Default: 20, 2.0). CCI: Adjust Length (Default: 23). ROC: Adjust Length (Default: 50). Signal Components: Toggle specific logic blocks on/off to customize the sensitivity of the composite score. VCE Timeframe: Select the resolution for the calculation (Leave empty for current chart). Disclaimer: This tool is for informational purposes only. Past performance of volatility expansion does not guarantee future results. Always manage risk appropriately.
Pine Script® 인디케이터
D_QUANT의
SMA 20 & 5 MagicMoving Average based envelops and bands are quite popular tools in the equity trading universe. One such popular band is 20 SMA High-Low band. In 20 SMA High-Low band generally a BUY is signaled when price breaks above the High of the band, and a SELL when price falls below the Low of the band. However, at times the time-price points to look for trading/ investing opportunities and taking position are not very clear in this generic mode. This script combines the 20 SMA High-Low band and a 5 SMA line plotted over it, to tackle this limitation. It helps to find more precise trading/ investing opportunities, Entry and Exit time-price points above & below the band, traversing along the 5 SMA line. The price within the band is usually considered as 'no trades' zone. This set up can be applied on any TF, but generally holds good for swings on daily/ hourly TFs. By tweaking SMA 20 and 5 to SMA 200 and 50 respectively in the settings, it may also help in identifying medium/Long term trends and investment opportunities using daily/ weekly TFs . Take it as a tool for learning and analysis. Happy trading/ investing.
Pine Script® 인디케이터
akphuf의
3
Sessions [LuxAlgo & TrendRiderIO]Visualize and track trading sessions with customizable ranges, VWAP bands, and high/low levels. Enhanced version of LuxAlgo's Sessions indicator. Track up to 3 customizable trading sessions (NY, London, Tokyo) with session range boxes, session-specific anchored VWAP with standard deviation bands, and high/low extension lines for the last 3 completed sessions. Includes peak hours visualization, session overlap highlighting, and breach alerts with direction indication. Perfect for identifying key support/resistance levels, analyzing session strength, finding entry/exit points, and breakout trading. License: CC BY-NC-SA 4.0 | Based on work by @LuxAlgo, enhanced by TrendRiderIO.
Pine Script® 인디케이터
TrendRiderIO의
1
ddddddrrrrrr//@version=5 indicator("🚀 EventSniper HF v3.0 - 高频方向信号", overlay=true) // 参数 emaFast = input.int(5, "快速EMA") emaSlow = input.int(20, "慢速EMA") rsiLen = input.int(7, "RSI周期") volRatio = input.float(1.8, "量能放大倍数") // 指标计算 ema1 = ta.ema(close, emaFast) ema2 = ta.ema(close, emaSlow) rsi = ta.rsi(close, rsiLen) volAvg = ta.sma(volume, 20) volSpike = volume > volAvg * volRatio // 高频方向信号（核心逻辑） longCond = ema1 > ema2 and rsi > 50 and volSpike shortCond = ema1 < ema2 and rsi < 50 and volSpike // 信号绘图 plotshape(longCond, title="建议做多", location=location.belowbar, color=color.lime, style=shape.labelup, text="多") plotshape(shortCond, title="建议做空", location=location.abovebar, color=color.red, style=shape.labeldown, text="空") // 文本提示 label.new(longCond ? bar_index : na, low, "📈 建议多头方向", style=label.style_label_up, color=color.green, textcolor=color.white) label.new(shortCond ? bar_index : na, high, "📉 建议空头方向", style=label.style_label_down, color=color.red, textcolor=color.white) // 报警条件（用于接入Telegram） alertcondition(longCond, title="📈 多方向警报", message="🚀 多方向信号触发：{{ticker}}") alertcondition(shortCond, title="📉 空方向警报", message="🚨 空方向信号触发：{{ticker}}")
Pine Script® 인디케이터
zhaohongsen85의
Master ORB (Custom TZ, TF 5m/15m/30m/60m)Master ORB (Custom TZ, TF 5m / 15m / 30m / 60m) is a precision Opening Range Breakout indicator built for traders who want clean, rule-based structure across global market sessions. The indicator automatically defines the Opening Range based on your selected timeframe (5, 15, 30, or 60 minutes) and session, with full custom time zone support. Once the opening range is formed, the high and low are clearly plotted on the chart, creating objective breakout levels for the rest of the session. Master ORB is designed to remove discretion and noise by: Locking in the opening range once it completes Maintaining fixed, non-repainting levels Visually separating range formation from breakout phase This allows traders to focus on execution, confirmation, and risk management, rather than constantly adjusting levels. The indicator works across major sessions including London, New York, Frankfurt, and NY PM, making it suitable for index futures, forex, and liquid equities. It integrates seamlessly with momentum tools, trend filters, and higher-timeframe bias. Best used for: Opening range breakout and breakdown trades Session-based trading plans Bias confirmation and invalidation levels Structured entries with defined risk Key features: Selectable ORB length: 5m, 15m, 30m, or 60m Custom time zone alignment Fixed, non-repainting range levels Multi-session support Clean visual structure with minimal chart clutter Master ORB is a framework indicator, not a signal generator. It provides the structure needed to trade with discipline, consistency, and clarity across sessions and markets.
Pine Script™ 전략
crxxx의
LCCM & C7Lục Chỉ Cầm Ma (LCCM) This indicator replicates the Lục Chỉ Cầm Ma (LCCM) trading method developed by Khac Quy . Lục Chỉ Cầm Ma (LCCM) is a rule-based breakout and trend-following trading method, originally designed for Gold (XAUUSD) and optimized for M15 and M30 timeframes. The method focuses on key support and resistance levels (barriers), candle strength analysis, and MA20 for trade management. 🔹 Core Trading Logic Buy Signal: A buy setup is considered when a candle closes above a resistance barrier, indicating a valid breakout. Sell Signal: A sell setup is considered when a candle closes below a support barrier, indicating a downside breakout. 🔹 C7 Candle Pattern 🔸 C7CB (Basic 3-Candle Pattern) C7CB consists of three consecutive candles with decreasing body size. The body of candle 1 is larger than candle 2, and candle 2 is larger than candle 3. This pattern indicates that trend momentum is weakening and buyers/sellers are losing control. Usage: Exit or partially close positions. Alternatively, move stop loss to breakeven to protect profits. 🔸 C7CC (Extended 5-Candle Pattern) C7CC is a five-candle consolidation pattern, consisting of: One mother candle (largest range), Followed by four inside candles with smaller ranges. The final candle that breaks out of this structure is used to confirm trend continuation or reversal, depending on direction. Usage: If a strong reversal candle appears after C7CC, close existing positions. If breakout aligns with the trend, traders may continue holding or add positions cautiously. You can refer to other C7 patterns in the LCCM documentation by the author Khac Quy.
Pine Script® 인디케이터
nguyenvietnamkhanh의
Andra Algo//@version=5 indicator(title="Andra Algo V 1.2", shorttitle="Andra Algo V1.2", overlay=true) // ===================== // INPUT // ===================== src = input(defval=close, title="Source") per = input.int(defval=100, minval=1, title="Sampling Period") mult = input.float(defval=3.0, minval=0.1, title="Range Multiplier") // ===================== // COLOR SET // ===================== buyLineColor = color.white sellLineColor = color.blue midColor = #90bff9 buyBgColor = color.new(color.gray, 20) sellBgColor = color.new(color.blue, 20) // ===================== // SMOOTH RANGE // ===================== smoothrng(x, t, m) => wper = t * 2 - 1 avrng = ta.ema(math.abs(x - x ), t) ta.ema(avrng, wper) * m smrng = smoothrng(src, per, mult) // ===================== // RANGE FILTER // ===================== rngfilt(x, r) => rf = x rf := x > nz(rf ) ? (x - r < nz(rf ) ? nz(rf ) : x - r) : (x + r > nz(rf ) ? nz(rf ) : x + r) rf filt = rngfilt(src, smrng) // ===================== // TREND DIRECTION // ===================== upward = 0.0 upward := filt > filt ? nz(upward ) + 1 : filt < filt ? 0 : nz(upward ) downward = 0.0 downward := filt < filt ? nz(downward ) + 1 : filt > filt ? 0 : nz(downward ) // ===================== // MID LINE COLOR // ===================== filtColor = upward > 0 ? buyLineColor : downward > 0 ? sellLineColor : midColor plot(filt, title="Mid Line", color=filtColor, linewidth=2) // ===================== // BUY & SELL CONDITIONS // ===================== longCond = src > filt and upward > 0 shortCond = src < filt and downward > 0 CondIni = 0 CondIni := longCond ? 1 : shortCond ? -1 : CondIni longCondition = longCond and CondIni == -1 shortCondition = shortCond and CondIni == 1 // ===================== // SIGNALS (FIXED BG COLOR) // ===================== plotshape(longCondition, title="Buy Signal", text="BUY", style=shape.labelup, location=location.belowbar, size=size.small, textcolor=color.white, color=buyBgColor) plotshape(shortCondition, title="Sell Signal", text="SELL", style=shape.labeldown, location=location.abovebar, size=size.small, textcolor=color.white, color=sellBgColor) // ===================== // ALERTS // ===================== alertcondition(longCondition, title="Buy Alert", message="Andra Algo V1.2 BUY") alertcondition(shortCondition, title="Sell Alert", message="Andra Algo V1.2 SELL")
Pine Script® 인디케이터
tommywija88의
Mine Shaft + Drift + Ore Pocket Detector (Gap+Touch)Mine Shaft + Drift + Ore Pocket Detector (Gap+Touch) — Full Description (v1.6.1, Pine v6) *Experimental - *Test Phase* 1) What this indicator is intended to do This indicator attempts to algorithmically discover “mine shaft” price structure on a chart by: Collecting structural anchor points (gaps and optionally pivots), Generating candidate trend “rails” (centerline + parallel upper/lower borders) from pairs of anchors, Fitting an optimal channel width around each candidate centerline, Scoring candidates based on how well price action conforms to the channel (touches + containment), Selecting and rendering: the main shaft channel (primary), additional drifts (secondary shafts per direction), And then detecting Ore Pockets: time locations where multiple selected lines intersect (time confluence / intersection clustering). The conceptual model is: A shaft = a best-fit channel that price respects over time (the “main tunnel”). Drifts = alternate channels close in quality to the main shaft (secondary tunnels). Ore pockets = future/past time coordinates where multiple channels’ centerlines intersect densely (confluence in time, not necessarily in price). 2) What it is doing right now (current behavior) In its current form, the script does a bounded, performance-limited scan: It stores a limited number of anchor points in arrays. It only considers a bounded number of recent anchors per direction. It constructs candidate lines from anchor pairs and evaluates channel fitness using sampled bars. On the last bar, it selects top candidates per direction and draws: a “main” channel per mode (single best overall, or separate up/down), plus optional drift channels, plus ore pocket markers. It is producing meaningful channels and drifts, but it is currently more likely to lock onto a strong “local” shaft than the one macro shaft spanning the entire market structure. 3) Core mechanics (how the script finds shafts) 3.1 Anchor generation (what points it uses) Anchors are the “support points” used to build candidate shaft centerlines. Two anchor families are supported: A) Gap anchors (from your selected gap mode) These attempt to capture “displacement events” and their boundaries/mids. B) Pivot anchors (optional structural anchors) These use pivots to inject macro structure points that are not strictly gap-based. All anchors are stored as: anchorX: bar_index of anchor anchorY: price of anchor anchorD: direction flag (+1 for up, -1 for down) Anchors are capped by maxAnchors with FIFO trimming. 3.2 Candidate generation (how it produces centerlines) For each direction (+1 and -1): Collect “recent” anchors of that direction within lookbackBars (bounded to maxDirAnchors). For each pair of anchors (x1,y1) and (x2,y2) that satisfy: spacing within , slope sign consistent with direction, Construct the line equation: slope m and intercept b Fit a channel width w around that line (via width mode). Score it (touches + inside count minus width penalty). Keep the top K rails (K = driftCount+1 typically). 3.3 Scoring model (what “best” means right now) For a candidate centerline: At sampled bars (stride sampling), compute: channel top = y(x) + w channel bot = y(x) - w Evaluate: Inside: candle range fits within the channel ± tolerance Touches: high near top border, low near bottom border (within tolerance) Score formula: score = insideCount * insideWeight + touchCount * touchWeight - (w / ATR) * widthPenalty So: Higher inside and touch counts increase score Wider channels are penalized (in ATR units) to avoid “cheating” via enormous width 3.4 Width fitting (how the channel thickness is chosen) Width is either: Fit (scan widths): scans widths between a min width and a max deviation cap and selects the best scoring width. Fixed ATR Envelope: uses a fixed width derived from ATR (currently hard-coded to a 2.0 ATR envelope in your present draft). Fixed Max Deviation: width is max observed deviation from line in sampled window. This matters because “macro shaft” detection is strongly influenced by whether the width-fitting is allowed to expand enough to contain large historical moves, without being penalized into losing to a smaller local shaft. 3.5 Rendering (what gets drawn) For any selected rail, it draws: Upper border line (top rail) Lower border line (bottom rail) Optional centerline (main only) Optional fill between borders (main only) Label at current bar with touches and inside count Drifts render similarly but without main-only features (depending on flags). 3.6 Ore Pocket detection (time confluence) Ore pockets are not “price zones” directly. They are computed as follows: Collect selected centerlines (m,b) for: the main selected shaft(s), and all drift centerlines (both directions if present) For each pair of selected lines, compute intersection x-coordinate: x* = (b2 - b1) / (m1 - m2) Only keep intersections within: Cluster intersections by time proximity (clusterBars) Mark the strongest clusters (highest counts) as “Ore Pocket” vertical dotted lines with labels. Interpretation: A dense cluster indicates many selected rails converge around a similar time coordinate. It is a “time confluence” hypothesis point. 4) Full settings reference (what each setting is for) 01) Gap Anchors Gap Mode FVG (3-candle) Uses a classic 3-candle fair value gap pattern: Up gap if low > high Down gap if high < low Anchors are derived from the gap boundaries. Candle Gap (open-close) Gap based on open vs close of the same bar with a tick threshold. Candle Gap (open-prev close) Gap based on open vs close with a tick threshold. Gap Threshold (ticks) Only used for the candle gap modes. Controls the minimum gap size required to register an anchor. Anchor Price Boundary: anchors at one gap boundary (more “structural edge”) Mid: anchors at midpoint of the gap (more “center of displacement”) Include Pivot Anchors (structure) When enabled, adds pivots as additional anchors to stabilize macro detection. Pivot Length Pivot sensitivity (how many bars left/right define a pivot). Larger values = fewer, more structural pivots. 02) Channel Fit + Touch Scoring Lookback Bars The historical window used to: filter which anchors are considered “recent enough” evaluate channel fitness (sampled evaluation) Larger lookback tends to favor macro shafts, but also increases computational risk (mitigated by evalBars and stride). ATR Length ATR period used for tolerance and width penalty scaling. Tolerance (ATR mult) Defines how close price must be to a rail to count as “touch” and how strict the “inside channel” containment is. Higher tolerance = easier to score high on touch/inside. Min Border Touches (keep rail) Minimum number of border touches required before a candidate is even eligible. Score: Inside Weight Weight of inside count in score. Score: Border Touch Weight Weight of border touches in score. This is a strong driver of “shaft-like” behavior. Score: Width Penalty (in ATRs) Penalizes wide channels relative to ATR. Higher penalty biases toward narrow/local shafts. 03) Performance Controls Max Stored Anchors (global) Maximum anchor points kept in memory arrays. Too low can cause loss of macro structure; too high increases candidate noise. Max Anchors / Direction (scan) Hard cap on how many anchors are used in candidate generation per direction. Critical: this strongly influences whether macro shaft can be found, because if you only keep the most recent anchors, you lose the early-structure anchor points. Eval Bars (max) Maximum historical bars actually evaluated for scoring. Even if lookbackBars is large, evaluation is capped here. Eval Stride (sample every N bars) Sampling step for evaluation. Larger stride = faster but less accurate scoring. 04) Candidate Generation Min Anchor Spacing (bars) Minimum distance between the two anchors used to define a candidate line. Prevents micro-noise lines from being evaluated. Max Anchor Spacing (bars) Maximum distance between the two anchors used to define a candidate line. If this is too low, you cannot generate truly macro candidate lines. 05) Shaft + Drift Display Main Shaft Mode Best Overall (Single Shaft): chooses one best rail among Up/Down and draws it as main. Up Only: show only the best upward rail. Down Only: show only the best downward rail. Up + Down: show both main up rail and main down rail simultaneously. Show Ascending Shaft Toggles rendering for the “up” main shaft (when mode allows it). Show Descending Shaft Toggles rendering for the “down” main shaft (when mode allows it). Drifts per Direction Number of additional top-ranked rails to draw per direction (after the best one). Extend Lines Right: extend lines to the right only. Both: extend both left and right. Fill Main Shaft Channel Fill between upper and lower borders for main shaft. Main Shaft Fill Transparency Transparency level for main fill. Show Main Shaft Centerline Draw the dashed centerline for the main shaft. 06) Ore Pocket (Intersection-Time Confluence) Show Ore Pockets (Time Confluence) Enables ore pocket discovery and rendering. Intersection Window Forward (bars) How far into the future intersections are considered. Intersection Window Backward (bars) How far into the past intersections are considered. Cluster Radius (bars) How close in time intersections must be to merge into a cluster. Min Intersections per Cluster Minimum cluster count required before a pocket is shown. Max Pocket Markers Limit how many pocket clusters are drawn. 07) Visual Controls Show Gap Anchors Displays the gap anchor dots for debugging. Show Pivot Anchors Displays pivot anchor dots for debugging. 5) How to use it (practical workflow) Step A — Confirm anchor behavior Turn on Show Gap Anchors. Choose your Gap Mode. Verify you are seeing anchors where you expect (displacement boundaries). If anchors are sparse: Reduce gap threshold (ticks) for candle-gap modes Enable pivots to inject structure Increase lookbackBars and maxAnchors so early anchors are not dropped Step B — Get stable main shaft candidate discovery Enable Include Pivot Anchors with a medium pivotLen. Use Fit (scan widths) initially. Increase Max Anchors / Direction (scan) so you’re not only using recent anchors. Increase Max Anchor Spacing so macro pairs are eligible. If you keep getting only local shafts: That is usually because the candidate pool does not include enough old anchors, or the maxSpacing prevents long-span lines. Step C — Tune scoring so the “whole-structure” shaft wins If the script picks a small local channel instead of the macro channel: Increase insideWeight relative to touchWeight (macro channels tend to contain longer structure even with fewer perfect “touches”) Reduce widthPenalty, because macro channels may need to be wider to accommodate historical volatility Increase lookbackBars and evalBars to make “whole-structure fit” matter Step D — Drifts as secondary shafts Once main shaft is good: Increase Drifts per Direction Validate that drifts represent meaningful alternate sub-shafts rather than noisy duplicates. If drifts look too similar: This is expected if many candidates differ only slightly; future refinements should diversify drift selection (see “what still needs done”). Step E — Ore pockets interpretation Ore pockets indicate time confluence of multiple rails. Use them as: “Time windows to watch” Not as deterministic price levels Tune: clusterBars (cluster tightness) minClusterSize (signal strength) 6) What still needs done (explicit backlog) The macro “main mining shaft channel” spanning the entire market structure, and Smaller shafts/drifts nested inside the macro structure. To accomplish that, the current algorithm needs additional architecture. Concretely: A) True multi-scale / hierarchical discovery (primary missing feature) Right now: one pass, one lookback, one score objective. Still Needed: Macro pass: discover a primary shaft using a very long evaluation window and anchor set. Micro pass(es): discover drifts/secondary shafts using: residuals (distance from macro centerline), or segmented time windows (regime partitions), or anchor subsets constrained to local regions. This is the single biggest reason we are not consistently getting the full-structure shaft. B) Anchor retention strategy for macro detection Right now: anchors are FIFO capped and direction scanning uses “recent anchors only.” To reliably find 10-year shafts we need: an option to store/retain representative anchors across the entire history, not only the most recent ones. Examples of necessary improvements: “Stratified anchor sampling” across time (keep some old anchors even when maxAnchors is hit) “Macro anchor bank” (separate storage for pivots or major gaps) C) Candidate generation constraints must support macro lines If we want a shaft spanning the whole structure: maxSpacing must allow it the candidate pool must contain anchors far apart in time So the algorithm needs: better selection of anchor pairs for long-span candidates (e.g., include earliest/oldest anchors + newest anchors deliberately, not accidentally) D) Drift diversification Right now drifts are “next best by score,” which often yields near-duplicates. We want: “diverse” secondary shafts: enforce minimum angular difference, enforce minimum offset difference, or penalize candidates too similar to the already-selected shaft. E) Width fitting logic for macro channels Macro channels often require: either a higher width cap, or a different penalty profile. Current width penalty is simple and can bias against macro channels. Needed: width penalty that scales by timescale or by total evaluated bars, or separate macro/micro scoring. F) Ore pocket semantics enhancement (optional but aligned) Currently pockets are time intersections only. If you want “pocket zones,” improvements could include: projecting intersection price and drawing a zone box, clustering in (time, price) space instead of only time, adding “importance” weighting based on which lines intersect (macro line intersections weighted higher). 7) Known limitations (current version) Heavy compute only runs on last bar (good for performance), but means: changes in anchors/parameters can reselect rails abruptly Candidate set is bounded; macro shaft can be missed if not in pool Drift selection can be redundant Ore pockets are time clusters, not price clusters
Pine Script® 인디케이터
Eyemaginative의
1
INVESTIFY Free Intraday Indicator📌 INVESTIFY Free Intraday Indicator – Description INVESTIFY Free Intraday Indicator is designed to help traders identify clear market direction and avoid overtrading. This indicator focuses on trend-based confirmation, not random signals. It provides limited and high-quality BUY / SELL signals — only when the market shows a clear directional move. 🔍 What this indicator does: Identifies Bullish & Bearish market bias Gives only one BUY or SELL per trend Avoids signal spamming in sideways markets Helps traders stay disciplined and patient 🎯 Best use case: Intraday trading Directional confirmation Trend-following traders Beginners who want clean structure Works on all markets (Forex, Indices, Crypto, Commodities) ⚠️ Important Notes: This is a FREE version for learning and confirmation No targets or stop-loss are shown Best used along with price action & discipline Avoid overtrading — quality over quantity Trade the direction, not the noise. 🔐 Want more precision? The paid INVESTIFY Pro version includes: Advanced entries SL & risk structure Session filtering Re-entry logic Smart money confirmations 📩 DM to get access
Pine Script® 인디케이터
Investify-ChiragBhandari의
US Open Vertical LineUS Open Vertical Line This indicator automatically plots a vertical dashed line at the US market open (09:30 New York time) on your chart. It is designed for traders who focus on session-based price action, including: New York open volatility Opening drive and reversals Intraday rotations and liquidity events The indicator is minimal by design — it does not calculate ranges, highs/lows, or signals. It simply marks the exact moment the US session opens, allowing you to combine it with your own strategy, levels, and risk management. Key features: Accurate US open detection using New York time (handles DST automatically) Works on all timeframes Clean, non-intrusive vertical dashed line Ideal for futures, stocks, and index traders Use it as a visual anchor for planning and executing trades around the most liquid part of the trading day.
Pine Script® 인디케이터
HriMarko의
Impulse OTE Fibonacci & Trend Catcher V2------------IMPORTANT------------ Look at the first 3 options in the input settings. You can change these based on what your trading - crypto, NQ, Forex etc. There are tool tips with the recommended settings there as well. ------------What the trader is supposed to do------------ Wait for an UP or DOWN arrow (trend shift). Let the indicator lock an impulse and draw the fibs. When price pulls into OTE, it prints READY. When confirmation happens, it prints ENTRY. ------------Why it’s useful------------ It’s meant to stop you from: taking random fibs from random swings, trading weak/noisy moves, or entering too early without confirmation. Instead it forces a simple flow: Trend → Impulse → Pullback to OTE → Confirmed entry
Pine Script® 인디케이터
Reanu_Keeves의
1
Time SessionTime Session is a lightweight indicator to visually highlight up to 3 trading time windows on any chart. It’s built to help you verify sessions precisely (especially when TradingView timezones/session handling can be confusing). Key Features 3 independent session slots (enable/disable each slot) Global timezone mode: EXCHANGE : uses the symbol’s exchange timezone (recommended in most cases) CUSTOM : use your own timezone string, copy the timezone label shown on your chart (bottom-right corner) and paste it into the CUSTOM field. Example: `UTC+1`, `UTC+2`, `UTC-5`, etc. Background highlighting for each slot (custom color + transparency) Start/End markers at the bottom of the chart: S1 = Slot 1 Start , E1 = Slot 1 End S2 = Slot 2 Start , E2 = Slot 2 End S3 = Slot 3 Start , E3 = Slot 3 End Data Window debug : `inSlot1`, `inSlot2`, `inSlot3`, `inAny` How to Use 1. Add the indicator to your chart. 2. Set Timezone Mode to EXCHANGE or CUSTOM . 3. If CUSTOM , paste the chart timezone label (e.g., `UTC+1`) 4. Configure Session Slot 1/2/3 using `HHMM-HHMM` (example: `07:00-18:00`). 5. Use the highlighted background and **S/E markers** to confirm the exact hours. Good Trading
Pine Script® 인디케이터
paolo.peisino의
Adaptive Nadaraya-Watson (Non Repainting) [Metrify]To understand this implementation of the Nadaraya-Watson estimator, we have to look at the core equation governing non-parametric regression. This script aren't trying to average prices; we are trying to find the probability density of where price should be relative to its recent history. 1. The Kernel Physics (Bandwidth Modulation) In standard kernel regression, you have a bandwidth parameter (h). This controls the "smoothness" of the curve. If h is too low, the curve jitters with every tick of noise. If h is too high, it acts like a sluggish SMA. A static h fails because market volatility is dynamic. When the market explodes (high volatility), a tight bandwidth generates false signals. When the market sleeps, a wide bandwidth misses the micro-trends. It try solving this by making h a function of the Asset's volatility ratio: heff​=h×max(0.5,min(SMA(ATR20​,100)ATR20​​,2.0)) If the current ATR(20) is double the long-term average (100), the bandwidth doubles. This forces the estimator to "zoom out" during chaos, effectively ignoring noise that would otherwise look like a reversal. vol_ratio = use_vol ? vol_raw / (vol_base == 0 ? 1 : vol_base) : 1.0 vol_mod = math.max(0.5, math.min(vol_ratio, 2.0)) h_eff = h_val * vol_mod 2. The Gaussian Loop (Endpoint Estimation) Standard Nadaraya-Watson scripts repaint because they calculate the regression over a full window centered on the bar. To make this usable for live trading, we must calculate the Endpoint Estimate. We iterate backward from the current bar (i=0) to the lookback limit. For every historical price Xi​, we calculate a weight wi​ based on how far away it is in time (distance). The weight is derived from the Gaussian Kernel function: wi​=exp(−2heff2​i2​) Price data closer to the current bar (i=0) gets a weight near 1.0. Data further away (i=50) decays exponentially toward 0. for i = 0 to lookback by 1 float dist = float(i) float w = math.exp(-math.pow(dist, 2) / (2 * math.pow(h_eff, 2))) num := num + w * src den := den + w 3. Statistical Deviation (MAE vs. StDev) Most Bollinger Band-style indicators use Standard Deviation (Root Mean Square). The problem with StDev is that it squares the errors, which heavily penalizes large outliers. In crypto or volatile forex pairs, one wick can blow out the bands for 20 bars. This one use Mean Absolute Error (MAE) instead. MAE=N1​∑∣Price−y^​∣ MAE is linear. It measures the average distance price strays from the kernel estimate without squaring the penalty. This creates "tighter" bands that adhere closer to price action during normal trend behavior but don't expand ridiculously during a flash crash. Pine Script float error = math.abs(src - y_hat) float mae = ta.sma(error, lookback) We project two sets of bands: Inner Band (Balanced): The "Noise Zone". Price inside here is considered random walk. Outer Band (Precision): The "Exhaustion Zone". Price reaching here is statistically unlikely (2.8x MAE). Input & Visual Summary Kernel Physics: h_val: The base smoothness. Lower (e.g., 6) = faster, noisier. Higher (e.g., 10) = slower, smoother. use_vol: Keep this TRUE. It prevents the bands from being too tight during news events. Envelope Statistics: mult_in / mult_out: These are your risk settings. 1.5/2.8 is a standard deviation-like setting suited for MAE.
Pine Script® 인디케이터
Metrify의
SFP Trend & VWAP Liquidity Pro [Zofesu]🎯 SFP Trend & VWAP Liquidity Pro Master the Flow with Institutional Precision. It was primarily built on Nasdaq, sometimes works on Crypto and Commodities, mostly on Indices. Suitable for periods when the market is going sideways. Requires longer setup. This indicator is a high-performance trading tool designed to identify Swing Failure Patterns (SFP) while maintaining strict alignment with market momentum. By combining Dynamic Liquidity Zones with a Dual-Filter Trend Engine , it ensures you only trade the most high-probability sweeps in the direction of institutional money. 🧠 The Philosophy Trading liquidity sweeps (SFP) without a trend filter is like catching falling knives. This tool solves that by requiring Confluence . It identifies where retail stop-losses are being hunted and confirms if the major trend (VWAP/MA) is ready to defend that level. 🛠️ Key Features & Functionality ⚡ Smart SFP Detection: Automatically tracks historical Swing Highs and Lows to detect "fakeouts" where price sweeps liquidity and closes back within the range. 🛡️ Dual-Filter Trend Engine: Two fully customizable filters (EMA, SMA, HMA, or VWAP). You can use them to define a "Golden Zone" for entries. ⚓ Professional VWAP Anchoring: Choose how your volume-weighted price resets—Session, Week, Month, or Year. This allows you to track institutional value from intraday to long-term swing perspectives. 📊 Dynamic Liquidity Lines: Real-time visual tracking of the most recent "Upper" and "Lower" liquidity levels. ⚙️ Customizable Modes The Institutional Fort: Use two slow MAs (e.g., 2000 & 5000) for maximum safety. Only take SFPs that align with the long-term macro trend. The Volume Specialist: Combine one MA with a Weekly/Monthly VWAP. This aligns price action with pure volume-weighted value. The Pure Aggressor: Turn off MA filters and use only Session VWAP for high-frequency scalping and rapid liquidity plays. 🚀 How to Trade with STVL Pro Long Signal (BULL SFP): Price sweeps below a Swing Low but closes above it + Price is trending above your active Filters (A & B). Short Signal (BEAR SFP): Price sweeps above a Swing High but closes below it + Price is trending below your active Filters (A & B). You can preset filter A to EMA 2000 You can preset filter B to HMA 5000. If the price is approaching the green lookback, just switch filter B to VWAP, you don't have to change the numbers. VWAP automatically uses the "Session" setting. So you will have EMA as support on the chart and VWAP will search for SFP. If HMA is closer to the red lookback zone, switch filter A to VWAP, it will search for SFP for short. SFP label may not always appear, it is very strict. ⚠️ Disclaimer Past performance does not guarantee future results. Always use proper risk management. Designed for disciplined traders who value quality over quantity.
Pine Script® 인디케이터
Zofesu의