Mulai

Indikator dan strategi

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")
Indikator Pine Script®
oleh tommywija88
NQ Implied Range GovernorThis Pine Script v6 indicator, “NQ Implied Range (VIX ÷ √N) Governor”, builds a real-time implied range framework for Nasdaq futures by importing a volatility index (default CBOE:VXN) on a user-selected timeframe and smoothing it with an EMA. It converts the annualized vol reading into a daily 1σ percentage move via oneSigmaPct = (VIX ÷ √252)/100, then maps that into a point-based implied move from a session “anchor” price. The anchor is locked at RTH session start (0930–1600 ET by default) based on your chosen mode (RTH Open, prior bar close, or daily open). A band mode selector controls how sigma is interpreted: an “Intraday Range” mode uses √(2/π) (~0.798) as a proxy for expected max excursion, while close-to-close modes use ±1σ or ±2σ envelopes; a separate calibration multiplier lets you widen/tighten the bands beyond theory. Once the implied move is computed, the script plots the upper/lower 1.0 bands, the anchor midline, and optional fills above/below the anchor. It then derives symmetric Fibonacci retracement levels between the anchor and each band (.236, .382, .500, .618, .786) and optional extensions (1.272, 1.618), with right-edge price labels for quick reading. In parallel, it tracks realized RTH range (session high–low) and compares it to the implied total range to produce a “range spent” ratio, dynamically color-coded from green → yellow → orange → red as the session consumes volatility budget. That ratio drives a session-end summary label (realized vs implied, bands, % spent), a configurable dashboard table showing model inputs/outputs (smoothed vol, raw σ%, anchor, ± bands, total range, realized, remaining, distance to bands), and a set of alert conditions for key events: crossing spent thresholds (70/100/120%), touching outer bands, touching key fib levels, extension hits, and session start/end.
Indikator Pine Script®
oleh gggoaaat
1
Ict + Alert (Realtime) - Optimized v2📊 Description This indicator implements the ICT (Inner Circle Trader) strategy using Fair Order Blocks (FOB) to identify demand and supply zones in the market. Optimized for XAUUSD (Gold) trading with real-time alerts. 🎯 How It Works The indicator analyzes price movements to identify: Bullish Fair Order Blocks: Zones where price left uncovered liquidity (gap) during an upward movement Bearish Fair Order Blocks: Zones where price left uncovered liquidity during a downward movement When price returns to these zones, the indicator generates: 📦 Colored boxes on the chart (green for long, red for short) 🔔 Real-time alerts with automatically calculated Entry, Stop Loss, and Take Profit 📍 Visual signals (triangles) to easily spot trading opportunities ⚙️ Key Features Smart Alerts Realtime: receive instant notifications when a setup forms Configurable Risk/Reward: set your preferred risk/reward ratio (default 1:3) Session filter: focus signals during London (08:00-10:00) and New York (14:30-16:30) sessions Stop Loss with buffer: configurable additional protection Operating Modes Realtime Mode: immediate alerts as soon as condition triggers (faster) Confirmation Mode: alerts only on bar close (more reliable) Visualization FOB boxes with adjustable transparency Optional midline to identify precise entry Visual indicators (triangles) for long/short signals
Indikator Pine Script®
oleh Mallak
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.
Strategi Pine Script®
oleh crxxx
Occurrence Scanner | MA Resilience & Breakout LogicThis indicator is designed to quantify the reliability of a Moving Average (MA) as a dynamic Support or Resistance level. Unlike standard crossover indicators that generate signals on every touch, this script employs a rigorous "Zone Tolerance" and "Temporal Confirmation" logic to filter out noise and classify price action into three distinct behaviors: Valid Bounce, Confirmed Breakout, or False Breakout (Trap). It also integrates an optional Volatility Filter (based on TTM Squeeze mechanics) to prevent false signals during low-volatility "chop" regimes. HOW IT WORKS: 1. The "Safe Zone" (Buffer Logic): Standard MAs are thin lines. This script creates a programmable "Road" around the MA (defined by the Zone Tolerance % input). A touch is only considered a potential breakout if the price closes outside this zone. Wicks that pierce the MA but close inside the zone are treated as Bounces (respecting the level). 2. Event Classification (The Decision Engine): Once the price interacts with the MA Zone, a "Sovereignty Window" (Lookahead Timer) is activated to monitor the subsequent candles: ✅ Bounce: Price tests the MA but never closes outside the Safe Zone during the window. The MA held as support/resistance. ❌ Breakout (Breakdown/Breakup): Price closes outside the Safe Zone. A strict "2-Consecutive Close" logic is applied to confirm the trend change immediately, avoiding premature signals. ⚠️ False Break: Price momentarily closes outside the zone but aggressively reverses to the opposite side within the time window. This identifies "Bull/Bear Traps". 3. The Volatility Filter (Anti-Chop): Market consolidation often leads to MA whipsaws. The script calculates Bollinger Bands (2.0 std) vs. Keltner Channels (1.5 ATR). If the Squeeze Filter is enabled in settings, the script forces the scanner to IGNORE any MA touches while volatility is compressed (Squeeze ON). This ensures signals are only generated during active trends. SETTINGS: MA Type & Length: Choose between SMA or EMA and the period (e.g., 20, 50, 200). Zone Tolerance (+/- %): The buffer width. Default is 0.2%. Higher values filter more noise. Lookahead Candles: The confirmation window size. Squeeze Filter: Toggle On/Off to ignore signals during low volatility regimes. INTENDED USE: This tool is intended for Swing Traders and Scalpers looking to statistically validate which Moving Average is being respected by a specific asset. It automates the "visual backtest" process, providing a Dashboard with success rates for Bounces vs. Breaks.
Indikator Pine Script®
oleh impressive_Storkj9gr3
SMART TRADERSMART TRADER is a hybrid trend-structure indicator designed to identify high-probability market regimes and precision entry zones by combining Donchian breakout logic with Smart Money Concepts (SMC). The indicator uses a 200-candle Donchian channel to detect major regime shifts, filtering the market into bullish or bearish environments. After a confirmed shift, SMART TRADER automatically identifies order blocks and marks Change of Character (CHOCH) events to highlight potential continuation entries with structural confirmation. This approach helps traders avoid consolidation noise and focus only on expansion phases where trends are statistically stronger. Key features: • 200-candle Donchian regime detection • Automatic order block marking after regime shifts • CHOCH structure labeling for entry timing • Visual trend bias overlay • Built-in alert conditions • Optimized for the 45-minute timeframe SMART TRADER is built for swing and intraday traders who want a structured framework that blends trend following with price action execution. Created by Jonathan Mwendwa Ndunge.
Indikator Pine Script®
oleh jonathanmwendwa2021
WMA MAD Trend | RakoQuantWMA MAD Trend | RakoQuant is a robust volatility-regime trend system built on Weighted Moving Average structure and Median Absolute Deviation dispersion, engineered to produce clean directional states while suppressing wick-driven noise and unstable ATR distortions. This tool belongs to the RakoQuant protected research line, combining a smooth WMA baseline, statistically robust volatility envelopes (MAD bands), SuperTrend-style regime logic, and a strength-aware visualization layer designed for consistent performance across trending, mean-reverting, and mixed market environments. Core Concept This indicator answers one fundamental question: Is price holding a statistically meaningful deviation from its WMA baseline, or reverting back into range? Unlike classic SuperTrend variants that rely on ATR (highly sensitive to spikes and wicks), WMA MAD Trend uses Median Absolute Deviation as its volatility engine — a robust dispersion measure that remains stable in the presence of outliers. How It Works 1) WMA Baseline (Directional Structure) At its core, the indicator defines the market’s structural center using a Weighted Moving Average: * WMA Baseline tracks directional bias with smoother, trend-weighted responsiveness * The baseline can optionally be smoothed further in intraday mode to reduce micro-chop This provides a stable anchor for dispersion-based regime classification. 2) MAD Volatility Engine (Robust Dispersion Core) Instead of ATR, volatility is measured via Median Absolute Deviation (MAD) around the baseline: * Compute absolute deviation:
|Close − Baseline| * Take rolling median of deviation over madLen * Optional normalization scales MAD toward a stdev-like measure (via constant factor) This makes volatility estimation: * Outlier-resistant * Wick-resistant * Regime-stable during abnormal price spikes 3) MAD Bands + SuperTrend Trailing Logic (Regime State Model) Bands are built as: * Upper Band = Baseline + Factor × MAD * Lower Band = Baseline − Factor × MAD Then classic SuperTrend-style trailing constraints are applied so the active band persists until a true regime break occurs. That produces a state engine: * Bull regime when price breaks above the trailing upper logic (transition into trend-up state) * Bear regime when price breaks below the trailing lower logic (transition into trend-down state) This behaves like a structural market regime model, not a reactive oscillator. 4) Strength Engine (Deviation-Based Intensity) A defining layer of this tool is the MAD Z-score intensity system: * Compute Z-score:
z = |Close − Baseline| / MAD * Map into a 0 → 1 strength scale Interpretation: * Low deviation = weak regime confidence (likely chop / mean reversion) * High deviation = strong regime confidence (trend expansion) 5) Intensity Visual Engine (Signal Clarity Layer) WMA MAD Trend includes a protected visual engine that scales opacity with strength: * Strong expansion = solid trend band * Weak deviation = faded band This gives immediate clarity:
Not all flips are equal — strength is displayed structurally. 6) Optional Institutional Filters Two optional confirmation modules allow institutional-grade filtering: Baseline Confirmation * Bull flips only accepted if price is above baseline * Bear flips only accepted if price is below baseline EMA Stack Filter * Bull only when Fast EMA > Slow EMA * Bear only when Fast EMA < Slow EMA These modules make the tool suitable for: * Directional portfolio bias frameworks (RSPS) * Regime classification overlays * Trend confirmation filters for execution systems 7) Strong Flip Tier Alerts Signal quality is tiered: * Standard flip alerts * Strong flip alerts only when deviation strength exceeds a threshold This produces a higher-confidence regime transition model for swing positioning and exposure scaling. How To Use ✅ Trend regime overlay
✅ Wick-resistant volatility trend filter
✅ MAD-based deviation strength engine
✅ Directional bias tool for portfolio systems Best use cases: * 1H–1D trend frameworks * Regime filters for signal stacking * Chop suppression in volatile markets Suggested workflow: * Bull bias when the regime is bullish and strength is rising * Reduce risk / defensive when strength fades or a bearish flip occurs * Pair with execution tools (breakout/mean-reversion entries) for timing Screenshot Placement 📸 Example chart / screenshot: snapshot
Indikator Pine Script®
oleh RakoQuant
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
Indikator Pine Script®
oleh Eyemaginative
Arpoom//@version=5 indicator("Volume & Body Spike Multiplier", overlay=true) // 1. คำนวณค่าเฉลี่ย 20 แท่ง avgVol = ta.sma(volume, 20) currentBody = math.abs(close - open) // ใช้ math.abs เพื่อให้ค่าเป็นบวกเสมอ avgBody = ta.sma(currentBody, 20) // 2. คำนวณ Multipliers volMultiplier = volume / avgVol bodyMultiplier = currentBody / avgBody // 3. กำหนดเงื่อนไข // วอลุ่มมากกว่า 2 เท่า และ เนื้อเทียนยาวกว่าค่าเฉลี่ยเนื้อเทียน 20 แท่ง volCondition = volume > (avgVol * 2) bodyCondition = currentBody > avgBody longCondition = volCondition and bodyCondition and close > open shortCondition = volCondition and bodyCondition and close <= open // 4. วาดลูกศร plotshape(longCondition, style=shape.triangleup, location=location.belowbar, color=color.green, size=size.small, title="Long Body Spike") plotshape(shortCondition, style=shape.triangledown, location=location.abovebar, color=color.red, size=size.small, title="Short Body Spike") // 5. แสดงตัวเลขบน Label (V = Volume x, B = Body x) if longCondition label.new(bar_index, low, str.format("V: {0,number,#.#}x B: {1,number,#.#}x", volMultiplier, bodyMultiplier), yloc=yloc.belowbar, color=color.new(color.green, 20), textcolor=color.white, style=label.style_label_up, size=size.small) if shortCondition label.new(bar_index, high, str.format("V: {0,number,#.#}x B: {1,number,#.#}x", volMultiplier, bodyMultiplier), yloc=yloc.abovebar, color=color.new(color.red, 20), textcolor=color.white, style=label.style_label_down, size=size.small) // 6. ระบบแจ้งเตือน (Alerts) alertcondition(longCondition, title="Buy Spike (Vol & Body)", message="Body Spike Up! Vol: {{plot_0}}x, Body: {{plot_1}}x") alertcondition(shortCondition, title="Sell Spike (Vol & Body)", message="Body Spike Down! Vol: {{plot_0}}x, Body: {{plot_1}}x") // ส่งค่าออกเพื่อให้ Alert ดึงไปใช้ plot(volMultiplier, "Vol Mult", display=display.none) plot(bodyMultiplier, "Body Mult", display=display.none)
Indikator Pine Script®
oleh B-TSP-2nd
Accumulation FTD Bullsish SwingTradingThis script detects an “ACCVOL 1‑day” price/volume setup using two variants based on two different Simple Moving Averages (SMA), and then prints only two labels on the chart: “AD” and “B” (no visual distinction between the SMA variants). How it works: On each new bar, the script searches for a “key day” located 3 to 13 bars back. A setup is validated when multiple conditions align, including: a minimum current-day percentage gain (default 1.24%), volume strength (volume rising vs. prior day and above a volume SMA, default 50), and a structural price pattern around the key day (bullish key day, specific “higher lows” sequence between the key day and today, and the day after the key day being bearish). The SMA filter differs by case: for each tested key day, the close must be below the selected SMA (Case 1 uses SMA #1 length, default 5; Case 2 uses SMA #2 length, default 10). Each case can be enabled/disabled and its SMA length can be adjusted independently in the settings. When a setup triggers, the script places: - “AD” on the key day (n bars ago), and - “B” on the current bar. Priority is kept “as-is”: the script checks n = 3, then 4, then 5… up to 13, and it will plot only one AD/B pair per current bar (the first match in that 3→13 order), even if multiple matches occur. Important note (signal selection): This indicator can produce many signals, and you should not take them all. In practice, signals tend to be more meaningful when they occur after a drawdown of at least 10%, rather than during extended strength. Risk management (example): As a general risk framework (not financial advice), a common approach is to place a stop loss roughly 6% to 8% below the most recent meaningful swing low. Adjust this to the instrument’s volatility and your position sizing rules. Recommended confirmations (mix with 2 indicators): To improve signal quality, consider combining this script with two confirmation tools: 1. Chaikin Money Flow (CMF) set to CMF Length = 50 and a 50‑period SMA on the CMF. 2. The Volume Pressure Indicator. Signals are often more reliable when: CMF is above its moving average, and The Volume Pressure oscillator is also above its moving average. Market regime warning: There can be many false signals during bear markets, so applying stricter filters and confirmations is strongly recommended. Best use case: This indicator is designed to be particularly effective for swing trading on stocks and various ETFs, where you look for a post-drawdown rebound supported by improving volume/flow conditions.
Indikator Pine Script®
oleh DanyBedard2309
1
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.
Indikator Pine Script®
oleh nguyenvietnamkhanh
Bob's Whale Hunter - V7 (Jorge's Algo)Trade like a whale, not the bait. The Whale Hunter V7 is a high-performance toolkit specifically engineered for traders following Smart Money Concepts (SMC) and Institutional Price Action. This indicator automates the identification of high-probability zones based on the AMD (Accumulation, Manipulation, Distribution) cycle. 🚀 Key Features: Institutional Liquidity Sweeps: Automatically detects liquidity grabs at key highs and lows. These are the exact spots where institutional "whales" enter the market by triggering retail stop losses. Dynamic Fair Value Gaps (FVG): Highlights market imbalances that act as price magnets. This allows you to time your entries during the "rebalance" with surgical precision. Multi-Timeframe Dashboard (HTF Matrix): A real-time panel showing the Macro bias (4H) versus the Entry trend (15m). Stay aligned with the higher-timeframe order flow at all times. Elite Market Structure: An institutional-grade trend filter that shifts color based on market dominance, helping you distinguish between a deep retracement and a true trend reversal. 🛠 How to Trade it (The Institutional Checklist): Macro Alignment: Check the Dashboard. If 4H is green, look for buy setups only. Never trade against the "Big Money" flow. Identify the Sweep: Wait for the triangle signal (Sweep). This confirms that liquidity has been cleared and the "Manipulation Phase" is likely complete. The Trigger (FVG): Once a Break of Structure (ChoCH) occurs after the sweep, look for entries within the highlighted FVG boxes that align with your OTE (Optimal Trade Entry) Fibonacci levels. Targeting: Aim for the opposing liquidity pools or the next institutional level identified by the script. "Trading is a game of probabilities. Follow the footprints left by the giants."
Indikator Pine Script®
oleh JorgeG255
HVN Boundary Assist FRVP + ATR Tempo Auto TF Defaults (LOCKED)This indicator is a structure-assist tool, not a signal generator. It is designed to standardize High-Volume Node (HVN) boundary placement and evaluation when using TradingView’s Fixed Range Volume Profile (FRVP) on weekly and monthly timeframes. The script does not attempt to discover HVNs automatically. The trader selects the HVN visually using FRVP and inputs the HVN center (effective VPOC). From there, the script applies consistent, rules-based logic to define boundaries, track interaction, and prevent lower-timeframe levels from conflicting with higher-timeframe structure. What the indicator does 1. Standardizes HVN boundary placement Using the active timeframe’s ATR, the indicator identifies the first candle that regains tempo on each side of the HVN center. A valid boundary requires: A bar range ≥ a fixed fraction of ATR A close that breaks prior rotational overlap The close of that candle becomes the candidate HVN high or low. Wicks are ignored for structure. 2. Automatically adapts to timeframe The indicator enforces locked system defaults: Weekly: 0.33 ATR expansion, 10-bar overlap lookback Monthly: 0.25 ATR expansion, 8-bar overlap lookback These values adjust automatically based on chart timeframe, eliminating discretionary tuning. 3. Tracks retests without redefining structure HVN interaction is tracked via wick touches within a tight ATR-based tolerance. Retests are informational only and never move boundaries. This captures recognition and rejection behavior without violating close-based structure rules. 4. Ranks HVN strength (0–3) Each HVN is scored using: Tightness relative to ATR Relative volume confirmation Presence of at least one retest This produces a simple, comparable strength ranking without overfitting. 5. Enforces clean monthly → weekly nesting An optional monthly gate restricts weekly logic to operate only inside a defined monthly HVN. If conflicts arise, monthly structure always overrides weekly, preventing level overlap and structural ambiguity. What the indicator does NOT do It does not read FRVP data (TradingView limitation) It does not auto-detect HVNs It does not generate trade signals It exists to remove subjectivity and inconsistency from HVN boundary placement and evaluation. Intended use Apply FRVP and visually identify the HVN Enter the HVN center price into the indicator Let the script define precise boundaries and interaction metrics Use monthly HVNs as structural rails and weekly HVNs for execution Design philosophy Structure is defined by closes and volatility, not wicks Retests measure recognition, not acceptance Higher timeframe structure always dominates This tool enforces those rules mechanically so the trader doesn’t have to.
Indikator Pine Script®
oleh jackes87