Auf geht's

Indikatoren und Strategien

EMA HH/LL Levels v6This indicator builds dynamic horizontal levels based on Higher Highs (HH) and Lower Lows (LL) of an Exponential Moving Average (EMA) rather than raw price. It is designed to highlight structural EMA-based resistance and support levels and automatically manage their lifecycle. 🔹 Core Logic The script calculates an EMA (default length: 26). Pivot Highs and Pivot Lows are detected directly on the EMA line, not on price. Each confirmed: EMA Higher High (HH) → creates a solid blue horizontal level EMA Lower Low (LL) → creates a solid red horizontal level Levels extend to the right and remain active until specific conditions are met. 🔹 Level State Management Each level can be in one of three states: Active (Solid line) The level has been created but not interacted with yet. Touched by Price (Dotted line) When a price bar touches the level (High ≥ level AND Low ≤ level), the level changes its style from solid to dotted, but remains on the chart. Broken by EMA (Removed) When the EMA itself crosses the level: HH level → removed when EMA crosses above it LL level → removed when EMA crosses below it The level is then deleted from the chart. ⚠️ Important: Levels are never removed by price action alone — only by an EMA break. 🔹 EMA Visualization The EMA line is color-coded by direction: Upward slope → user-defined “up” color Downward slope → user-defined “down” color EMA length, colors, and line width are fully configurable. 🔹 Customization Options EMA length EMA up/down colors and thickness Pivot sensitivity (left/right bars) HH / LL level colors and thickness Maximum number of stored levels (to control memory and chart clutter) 🔹 Use Cases Identifying EMA-based dynamic support and resistance Tracking trend structure via EMA swings Confluence with price action, pullbacks, and breakouts Trend-following and mean-reversion strategies 🔹 Notes This indicator works on all markets and timeframes. No repainting after pivot confirmation. No ta.crossover() / ta.crossunder() is used — all logic is calculated manually for maximum stability in Pine Script v6.
Pine Script® Indikator
von Benepamm
Auction Weighted Support and Resistance [Metrify]This script builds an “auction-weighted” S/R map that’s intentionally closer to a microstructure proxy than a classic “draw pivots → draw lines” approach. The core idea: treat repeated interactions around the same price as evidence of auction behavior (acceptance vs rejection), then compress that behavior into a small set of ranked horizontal zones per horizon. Instead of outputting dozens of levels, it runs a selection pass to keep only the strongest, spatially distinct levels. Candidate discovery is pivot-driven, but not used naively. The script collects pivot highs/lows into rolling buffers for three horizons (Micro/Short/Medium) with different pivot lengths and memory caps. Those candidates don’t become “levels” directly; they’re just seeds that get clustered and rescored. Clustering is ATR-normalized (distance measured in ATR multiples), so the same logic doesn’t fall apart when you change symbol volatility or timeframe. Each horizon has its own clustering radius (distATR_micro/short/medium), which makes Micro more granular and Medium more tolerant. The “weight” you see is not a single metric. It’s a composite score that tries to approximate how meaningful a price is in an auction sense: Touch count (distinct): interactions are counted only when the candle range gets within a near-band threshold (ATR-normalized), and then gated by minimum bar separation so you don’t get spam from chop printing 20 touches in a row. (this is done with a stride-based loop to avoid blowing runtime on deep lookbacks) Acceptance: a rolling overlap rate of candle ranges inside the box. It’s exponentially weighted (half-life decay), so recent acceptance matters more, but older acceptance still contributes. If price has been “living” around that level, acceptance rises. Rejection quality: wick-aware rejection, but range-gated (not close-gated). The scoring looks at whether the candle range overlaps/approaches the level, then measures wick dominance on the rejecting side plus where the close sits inside the bar range. Age decay: older levels aren’t thrown away automatically, but they get downweighted via an exponential decay term so stale structure doesn’t dominate forever. Those components get combined by f_weightCompose() into a bounded weight using saturating transforms (so touches don’t scale linearly forever) and a decay factor tied to age. When multiple candidates land in the same cluster, the merge is done with a saturating union on weights (1 - (1-oldW)*(1-wAdd)) rather than simple addition, so weights don’t explode and a level can converge toward 1.0 without becoming meaningless. The cluster center price is updated via a weight-based average to prevent random drift from weak additions. After clustering, we does an explicit selection pass instead of drawing everything. First it filters by minScore, then sorts by weight, then applies a spatial suppression step (basically NMS for horizontal levels). The minimum spacing is ATR-based and incorporates both a horizon spacing floor and the zone thickness, so you don’t end up with two bands that overlap visually or convey the same information. On top of that, there’s a global cross-horizon collision gate (f_canDraw) so Medium zones can coexist with Short/Micro without the chart turning into a layered fog of rectangles. Visualization is intentionally “zone-first.” Each selected level becomes a box band whose half-thickness is ATR-scaled per horizon (bandThicknessATR_*). Opacity isn’t linear: it normalizes weight above minScore, applies a power curve to compress mid-range values, and also scales relative to the strongest level in that horizon (so you still get contrast when everything is “kind of strong”). The pressure overlay is not volume-based and not orderflow (pine can’t read L2), but it tries to expose short-term imbalance while price is inside a band. When the last price is inside a zone, it computes a pressure score from two parts: proximity to the center (closer = higher) and a directional imbalance proxy from recent returns sampled only on bars that intersect the band. It then draws two thin lines at the band edges with alpha proportional to that pressure score. This is meant as a “are we being pushed out or absorbed here” hint (not a prediction engine). If you enable the audit panel, the script builds a table listing the levels that actually got drawn (post-selection + collision filtering). The columns map directly to the internal metrics (weight, touches, acceptance, rejection), so you can sanity-check why a level exists. Level IDs are horizon-prefixed (MC/ST/MD) and assigned based on ranking within each horizon. note: rebuild is throttled (rebuildEveryN) and only runs on the last bar. Loops that can go deep use a stride heuristic (1/2/4) to keep runtime predictable on large lookbacks. Arrays are used as bounded buffers for candidate storage, and drawing objects are aggressively deleted/rebuilt to avoid object leaks.
Pine Script® Indikator
von Metrify
Sakalau02 Weekly Daily SessionsSakalau02: Weekly Daily Sessions – The Architecture of the Trading Week The "Sakalau02 Weekly Daily Sessions" is a high-definition visual mapping tool designed to dissect the trading week into distinct daily blocks. More than just a period separator, this script defines the "field of play" for each day, allowing you to visualize where liquidity builds and how price interacts with temporal boundaries. Here is why this script is the cornerstone of a professional Top-Down analysis: 📅 High-Definition Daily Structure The indicator transforms your chart into a logical map of the week, providing visual support for all 7 days, with a focus on active trading from Monday to Friday. Visual Identity: Each day is assigned its own unique color, helping you instantly recognize repetitive market signatures (like the "Tuesday Reversal" or "Mid-week Expansion"). Timezone Precision: Featuring a dedicated Timezone Input, the script ensures that daily boxes open exactly at 00:00 according to your chosen financial hub (UTC, New York, London, etc.). 📐 Range and Liquidity Analysis Through its Dynamic Box System, the script monitors price evolution in real-time: High/Low Tracking: Automatically expands the box boundaries as price carves out new daily highs or lows. The 0.5 Level (Daily Equilibrium): Automatically calculates the midpoint of the entire day. This is the critical "Fair Value" zone where price decides whether to trend or mean-revert. Open/Close Trajectory: A discreet line tracks price relative to the daily open, providing an instant read on the intraday bias (Bullish/Bearish). ⚡ Precision Alert System Never miss a structural shift. The indicator comes equipped with built-in alerts for: Session Starts: Be notified the moment a new daily cycle begins. Liquidity Sweeps (New High/Low): Receive alerts the second price breaches the current day’s high or low—perfect for executing Judas Swings or Expansion setups. 💎 Versatile Display Modes Boxes Mode: Encapsulates price for a clear view of market structure. Zones Mode: Highlights the background for a cleaner integration with secondary indicators. Timeline Mode: Marks the base of the chart, keeping the price action area completely untouched. Piața nu este doar preț, este ritm. În timp ce alții se pierd în zgomotul fiecărei secunde, eu definesc limitele zilei. O structură creată pentru traderul care știe că volumul urmează timpul, iar profitul urmează disciplina — păstrați ochii pe echilibrul zilei!" — Semnat, Andrei (Sakalau02) ⏳
Pine Script® Indikator
von Aa002
ATR % V3Now I'll provide you with the fully translated script and comprehensive documentation: ATR % V3 Indicator - Introduction The ATR % V3 is a Pine Script indicator that displays the Average True Range (ATR) as a percentage of price, providing traders with a normalized view of market volatility. Unlike the standard ATR which shows absolute price values, this percentage-based approach allows for easier comparison across different securities and timeframes. The indicator includes advanced features such as multi-day extreme value detection, customizable horizontal reference lines, and optional coordinate inversion for specialized charting needs. Key Features Percentage-based ATR calculation relative to either current open or previous close Flexible smoothing methods (RMA, SMA, EMA, WMA) for different trading styles Multi-period extreme value markers for 3-day and 7-day highs/lows Dynamic horizontal reference line showing current ATR% value Optional coordinate flip for alternative visualization perspectives Bar confirmation control to prevent repainting on live bars Technical Explanation ATR Percentage Calculation The script calculates ATR% using the formula: ATR% = (ATR / Basis Price) × 100. The basis price can be either the current bar's open price or the previous bar's close price, allowing traders to choose the reference point that best suits their trading methodology. Smoothing Methods The indicator supports four moving average types for ATR smoothing: ​ RMA (Relative Moving Average): Default method, provides exponentially smoothed values similar to Wilder's original ATR implementation SMA (Simple Moving Average): Equal weighting of all periods EMA (Exponential Moving Average): Recent prices weighted more heavily WMA (Weighted Moving Average): Linear weighting scheme Extreme Value Detection The script identifies when the current ATR% value represents a local extreme over 3-day or 7-day lookback periods. These markers appear only on the most recent bar and help traders identify volatility compression or expansion zones that may precede significant price moves. ​ Anti-Repainting Feature The "Wait for Bar Close to Update" option prevents the indicator from recalculating on every tick within an unconfirmed bar. When enabled, the ATR% value updates only after each bar closes, ensuring consistent historical values that won't change retroactively. ​ Usage Recommendations For Volatility Analysis: Use the percentage-based approach to compare volatility across different assets or timeframes objectively. Higher ATR% values indicate increased volatility relative to price. ​ For Position Sizing: ATR% can inform position size adjustments—reduce exposure when volatility (ATR%) spikes, and potentially increase when volatility contracts. ​ For Stop Loss Placement: The horizontal reference line provides a quick visual reference for current volatility levels, useful for setting volatility-adjusted stop losses. ​ For Breakout Confirmation: Watch for 3-day or 7-day extreme markers—volatility extremes often precede or confirm trend reversals or breakouts.
Pine Script® Indikator
von Dooogiig
MovingAveragesLibrary "MovingAverages" A collection of O(1) numerically stable moving averages that support anchors and fractional lengths up to 100k bars. Pine Script has a robust set of moving averages suitable for a majority of cases, making these alternatives useful only if you need anchoring, fractional lengths, or more than 5k bars. Included are the classic SMA , EMA , RMA , WMA , VWMA , VWAP , HMA , SWMA , Linear Regression , and ATR . The common parameters are: source (float) : Series of values to process. length (simple float) : Number of bars. Optional. anchor (bool) : The condition that triggers a calculation reset. Optional. parity (simple bool) : Sets if built-in function should be used. Optional. Other DSP filter adaptations include One Euro , Laguerre , Super Smoother , and Holt , as well as rate limiting functions such as Smooth Damp and Slew Rate Limiter . ANCHORING This is the libraries first and primary benefit. Akin to the built-in VWAP, anchoring is managed by passing a series bool into the function. For sessional anchoring, the included new_session() returns true on the first bar of intraday sessions, and stabilize_anchor() helps reduce near-anchor volatility. When no length is provided, the series continues indefinitely until a new anchor is set. Values during the warmup period are returned. source = close length = 9.5 anchor = ma.new_session() // Assumes library is imported as "ma" swma = ma.swma(source, length, anchor).stabilize_anchor(source, length, anchor) STREAMING UPDATES Rather than naively using loops to recalculate the whole series on each bar, linear interpolation (aka. "lerping") is used to incrementally update and translate between values. The canonical formula being: a + (b - a) * t. This formula is effectively an EMA, but it's applicable to nearly all averaging equations. Coupling this technique with a circular buffer captures 3 of the 5 benefits this library offers: O(1) computation, fractional lengths, and 100k bars. NUMERIC STABILITY The last benefit is how the library minimizes floating point errors. When possible, Pine Script functions are used for mathematical parity. Otherwise Kahan summation error compensation is used when calculating an average. Not only does this keep custom implementations stable throughout the series, it also helps keep them within 1.0e-10 of the built-in functions. Automatically defaulting to the built-in functions can be disabled by setting parity to false .
Pine Script® Bibliothek
von liquid-trader
Manus Gold Daily Range Choppy Filter### Manus Gold Daily Range Choppy Filter This indicator is designed to answer one simple but critical question **before trading begins**: **Is today a day worth trading, or is the market too choppy?** Instead of generating entries or signals, this tool acts as a **daily market condition filter**. It helps traders avoid low-quality sessions where breakouts fail and price action is dominated by noise and mean-reversion. --- ### 🔍 What the indicator does The script evaluates **market tradability once per day**, based on **yesterday’s completed data**, and then locks that decision for the entire trading day. It combines two independent concepts: #### 1️⃣ Choppiness Analysis (core logic) * Calculates the **Choppiness Index** on **1H and 4H timeframes** * Detects whether the market is: * **Trending / expanding** (low & falling choppiness) * **Range-bound / noisy** (high choppiness) * Optional requirement that choppiness must be **falling** (early expansion phase) #### 2️⃣ Daily Range Contraction (optional filter) * Detects **NR days** (narrowest range in N days) * Detects **ADR contraction** (yesterday’s range significantly smaller than normal) * Used to identify potential **breakout-ready environments** Both components are combined into a single **daily tradability decision**. --- ### 🟢 / 🔴 Output logic * **Green bar** → Market is considered **tradable** * **Red bar** → Market is **not tradable** (choppy / low quality) Important characteristics: * **Exactly one bar per day** * No intraday repainting * Decision is locked using **yesterday’s final data** * Designed to be used on **any intraday chart** --- ### 📊 Visual elements * Histogram bar (green / red) indicating daily tradability * Optional background highlight on the first bar of each new day * Optional table showing: * Choppiness values (1H / 4H) * Choppy / not-choppy status * Falling expansion state * DRB / contraction filter status --- ### 🎯 How to use it This indicator is **not a trading strategy** and does **not provide entries**. It is best used as: * A **pre-market filter** * A **“trade / no-trade” switch** * A **risk and expectation management tool** Typical usage: * Trade breakout and trend strategies **only on green days** * Reduce size or avoid trading entirely on red days * Combine with your existing setups (London Breakout, NY session, trend continuation, etc.) --- ### ⚠️ Notes * Designed and optimized for **Gold (XAUUSD)** but works on other instruments * Uses higher-timeframe context to protect against intraday noise * Especially useful for traders who struggle with **overtrading in ranges** --- ### ✅ Summary This indicator helps you **stay out of bad days**, not chase more trades. Sometimes, **the best trade is not trading at all**.
Pine Script® Indikator
von feiler_manuel
Expectancy Reality Check Most trading discussions focus on entries. This tool focuses on math. Expectancy Reality Check is a symbol-agnostic calculator that shows whether your assumed edge is mathematically viable — before you trade it. It does not generate signals. It does not predict price. It exists to answer one question: “If my assumptions are correct, does this strategy deserve capital?” What this tool does Given your assumptions for: Win rate Reward-to-Risk (R) Costs per trade Risk per trade Trade frequency the indicator computes: Expected Value (R per trade) Expected Value per month Break-even win rate (cost-adjusted) Edge vs break-even (percentage points) Risk-of-ruin proxy (fixed-fractional approximation) Estimated sample size needed to validate your win rate at a chosen confidence level All values are expressed in R-units, not currency, to remain portfolio-independent. How to use it Enter honest assumptions — not best-case backtest results. Observe: Is EV meaningfully positive? How small is the margin above break-even? How many trades are required before results are statistically meaningful? Decide whether the strategy is worth: testing, refining, or discarding. If the math fails here, execution quality will not save it. What this tool is not ❌ Not a strategy ❌ Not a signal generator ❌ Not a performance backtest ❌ Not a guarantee of results It is a reality check, not a promise. Notes on methodology Expectancy is computed in standard R-unit form. Break-even win rate is adjusted for per-trade costs. Risk-of-ruin is a proxy, based on a Lundberg-type root for i.i.d. outcomes under fixed fractional risk. Sample size guidance uses a normal approximation for binomial confidence intervals. All calculations assume stationarity — real markets may violate this. Use judgment. Who this is for Traders designing rule-based systems Traders comparing multiple strategies Traders tired of “high win rate” marketing Anyone who wants math before emotion Final note A strategy with: high win rate but negative expectancy or positive expectancy but no statistical margin is not an edge — it’s noise. Systems over feelings.
Pine Script® Indikator
von SystemsOverFeelings
DSMS - DeltaSurge Matrix Station - 1M Scalping [SurgeGuru]DSMS - DeltaSurge Matrix Station HOW TO READ THE CHART ===================================== This guide explains every visual element you see on the chart. DSMS is a volume profile + order flow indicator built for 1-minute Bitcoin scalping. It shows WHERE institutional money is sitting and WHERE price is likely to react next. ===================================== 1. THE VOLUME PROFILE (left side of chart) ===================================== The colored horizontal bars extending left from the candles are the volume profile. Each bar represents a price level (called a "bin") and shows how much volume traded there. LONGER BAR = more volume at that price. BAR COLOR tells you who is in control: - Green/teal bar = buyers dominated that level (bullish delta) - Red/orange bar = sellers dominated that level (bearish delta) - The more intense the color, the stronger the imbalance SPLIT BARS (bull/bear breakdown): If enabled, each bar splits into two halves showing exact buy vs sell volume. Top half = sell volume, bottom half = buy volume. HEATMAP (wide faded bars behind the profile): The large transparent boxes behind the profile bars are the heatmap. They show the same delta information but stretched wider for quick visual scanning. Bright = high conviction. Faded = low conviction. ===================================== 2. KEY PRICE LEVELS ON THE PROFILE ===================================== POC (Point of Control): The bin outlined with a bright border is the POC -- the single price level with the MOST volume. Price tends to gravitate back to the POC. A small label shows the POC price and context like "EQUILIBRIUM" or "BULL ATK". POC FLASH LINE: A short dashed cyan line appears at the POC when a bounce is detected. Trigger conditions: price is at the POC, the current candle is bullish after a bearish candle, and volume is at least 1.2x average. This signals that the POC is acting as active support and price is reacting to it in real time. VA HIGH / VA LOW (Value Area lines): Two horizontal lines mark the top and bottom of the Value Area -- the price range where approximately 70% of volume traded. These act as support and resistance. - VA High = resistance when price is below, breakout level when price pushes above - VA Low = support when price is above, breakdown level when price drops below When a breakout happens, the line turns green (up) or red (down) and gets thicker. ===================================== 3. LABELS ON PROFILE BINS ===================================== Each profile bin can show a small text label. These describe what is happening at that specific price level. Here is what each label means: ABS (with up/down arrow): "ABS▼ 7b" = Absorption detected. Institutional players are absorbing selling pressure at this level (likely accumulating). The "7b" means it held for 7 bars. ABS▼ = absorbing sells (bullish). ABS▲ = absorbing buys (bearish). FLOW (with arrow): "FLOW↑" or "FLOW↓" = A flow shift happened here. The delta direction reversed, meaning buyers took over from sellers or vice versa. This is a momentum change signal. FAIL (with arrow): "FAIL↑" or "FAIL↓" = A flow shift was detected but FAILED to confirm. The reversal started but price did not follow through. Shown in orange. Often means the opposing side absorbed the move. INVAL / INVALID: "INVAL" or "INVALID" = A previously confirmed flow shift was invalidated. Price reversed back through the shift level, canceling the signal. Shown in orange. Treat the original shift direction as no longer valid. BULL EXH / BEAR EXH: "BULL EXH" or "BEAR EXH" = Exhaustion zone. Extreme delta (above 65%) combined with FADING volume. The dominant side pushed too hard and is running out of fuel. Shown in gold. Often precedes a reversal. Higher delta + lower volume = more exhausted. IMBALANCE RATIO (number:1): "4:1" = The ratio of buy volume to sell volume (or vice versa) at this bin. A 4:1 ratio means one side has 4x the volume of the other. Only shown when the imbalance exceeds the configured threshold. ICE: "ICE" = Iceberg order detected in this bin. High volume traded but price barely moved, suggesting a large hidden order was absorbing all the activity. CONFL / CONF+ / CONF-: Confluence detected. Multiple signals (structure + order flow) agree on direction. CONF+ = bullish confluence. CONF- = bearish confluence. CONFLICT: Structure says one thing, order flow says another. Be cautious. STK (with multiplier): "STK x3" = Imbalance stack. Three or more consecutive bins all lean the same direction. Shows institutional pressure building across multiple price levels. OB (with arrow): "OB↑" or "OB↓" = This bin overlaps with an active Order Block (see section 6). FVG (with arrow): "FVG↑" or "FVG↓" = This bin overlaps with an active Fair Value Gap (see section 7). "uFVG↑" or "uFVG↓" = Same but for a micro-level FVG (smaller gap detected within the profile structure rather than on-chart candle gaps). uSR: Micro structure level. A price level that has been tested multiple times with high volume -- acts as local support or resistance. EQUILIBRIUM / BULL ATK / BEAR DEF / etc: Context labels that describe the state of the bin: - EQUILIBRIUM = balanced buyers and sellers - BULL ATK = buyers attacking with increasing volume - BULL DEF = buyers holding but volume fading - BEAR ATK = sellers attacking with increasing volume - BEAR DEF = sellers holding but volume fading CONFIDENCE SCORE (number at end of label): Example: "ABS▼ CONFL " The number in brackets is a confidence score from 0-100. Higher = more signals agreeing. Above 70 is strong. DWELL TIME: "8d" at the end means price spent 8 bars dwelling at this level. More time at a level = stronger support/resistance. ===================================== 4. ARROWS ON PROFILE BINS ===================================== Small arrows may appear to the right of profile bars: DELTA ARROWS (^^): Show if buying/selling pressure is accelerating or decelerating. pointing up = bullish momentum gaining speed pointing down = bearish momentum gaining speed VOLUME ARROWS: Show if volume is increasing or decreasing at each level. Up arrow = volume building. Down arrow = volume fading. VELOCITY BANDS: Small colored boxes to the right of the profile. Green = volume accelerating. Red = volume decelerating. Only appears on high-volume bins. ===================================== 5. CVD LINE (curved line inside the profile) ===================================== The colored line running through the profile area is the CVD (Cumulative Volume Delta) line. It tracks the running total of buy volume minus sell volume across the session. - Line going UP = buyers accumulating over time - Line going DOWN = sellers accumulating over time HOW THE LINE COLOR WORKS: The line color is NOT random. It checks the CVD value against 5 moving averages (EMA 8, 13, 21, 34, and 55). Each EMA that CVD is ABOVE scores +1. Each EMA that CVD is BELOW scores -1. The total score (-5 to +5) sets the color: +5 (above ALL 5 EMAs) = deep forest green -- strong bullish momentum +3 to +4 = bright green -- solid bullish +1 to +2 = light green -- lean bullish 0 = gray -- neutral, no clear direction -1 to -2 = light red -- lean bearish -3 to -4 = bright red -- solid bearish -5 (below ALL 5 EMAs) = deep dark red -- strong bearish momentum In practice: when the line shifts from red to green, it means CVD has crossed above its moving averages -- buying pressure is accelerating. When green turns red, selling pressure is taking over. A gray section means CVD is choppy and sitting between its averages with no conviction. CVD LABEL (at the right end of the line): "CVD +1.2K +5" First number = raw CVD value (+1,200 net buy volume) Second number = confirmation count (+5 means 5 consecutive bars where the adaptive reset system confirmed the bullish direction) The label color uses a separate gradient based on the confirmation count: Deep green = many consecutive bullish confirmations Deep red = many consecutive bearish confirmations Yellow/gray = few or mixed confirmations ===================================== 6. ORDER BLOCKS (OBs) - colored boxes on candles ===================================== Order Blocks are zones where institutions placed large orders. They appear as colored boxes around groups of candles. ACTIVE OBs (not yet tested): - Green/teal box = bullish OB (expect support when price returns) - Red box = bearish OB (expect resistance when price returns) - Solid fill, extends rightward from the origin candles BROKEN OBs (breakers): - Same colors but with a transparent fill and border outline only - A bullish OB becomes a breaker when price closes below its bottom - A bearish OB becomes a breaker when price closes above its top - Once broken, the OB flips role: old support becomes resistance and vice versa - A dotted midline shows the 50% level of the broken OB - If price then closes through the breaker in the new direction, it is removed entirely Two detection methods run simultaneously: - Fast: simple 3-bar pivot swings for reactive OBs near current price - Deep: ICS-style fractal depth swings for structural OBs from further back The "Detection Depth" setting controls the fractal depth (Short/Intermediate/Long Term). ===================================== 7. FAIR VALUE GAPS (FVGs) - striped zones on candles ===================================== FVGs are gaps in the price action where one side (buyers or sellers) was so dominant that price skipped over a range. Price tends to come back and fill these gaps. They appear as small striped/hatched boxes at the gap location. - Purple-ish stripes = the gap zone - Each individual stripe is deleted when price crosses through its midpoint, so the gap visually erodes from the inside out as price fills it - After 21 bars, remaining unfilled stripes fade to show the gap is aging - Once every stripe is filled, the FVG is fully removed from the chart - Maximum 30 FVGs tracked at once (oldest removed first if exceeded) ===================================== 8. MULTI-TIMEFRAME BOXES (2m / 5m / 15m) ===================================== Colored boxes extending behind and slightly ahead of the current candles. These show FVGs and Order Blocks detected on HIGHER timeframes (2-minute, 5-minute, 15-minute charts) projected onto your 1-minute chart. HOW TO TELL THEM APART: Border style: - Dashed border = FVG (Fair Value Gap) - Solid border = OB (Order Block) Thickness and length: - Thin border, extends 20 bars back = 2-minute timeframe - Thin border, extends 30 bars back = 5-minute timeframe - Thick border, extends 50 bars back = 15-minute timeframe Color: - Cyan/teal = bullish (expect support) - Orange = bearish (expect resistance) When your 1-minute price touches a higher-timeframe structure, it carries more weight because institutions watch those levels. ===================================== 9. PREDICTIVE CONFLUENCE ZONES (projected boxes) ===================================== These are the "ZONE S x3" and "ZONE R x2" boxes that project AHEAD of current price (to the right of the last candle). They appear when multiple structures from different sources cluster at the same price area: - 1m Order Blocks + 1m FVGs + 2m structures + 5m structures + 15m structures The system scans all unmitigated levels, finds where they overlap, and projects a high-probability reaction zone. "ZONE S x3" = Support zone, 3 structures converge here (green box) "ZONE R x2" = Resistance zone, 2 structures converge here (red box) Higher count = stronger zone. These are the highest-conviction levels on the chart. ===================================== 10. SIGNAL LABELS ON CANDLES ===================================== These labels appear directly on or near candles when specific conditions are met: SWEEP LABELS (cyan/magenta bubbles): Example: "VA High 8" A liquidity sweep happened -- price wicked past a key level and reversed. The name shows which level was swept. The number is a quality score. Higher score = more reliable sweep. Cyan = bullish sweep. Magenta = bearish. ICE (cyan/red squares): Small squares below (bull) or above (bear) candles. "ICE 2.3x" = Iceberg order detected. Volume was 2.3x average but price barely moved. A hidden large order was absorbing all activity. COILED: "COILED " = Price has been compressing (low volatility) for 4 bars while sitting near a wall of support/resistance. Like a spring ready to release. Green = bullish coil (expect breakout up). Red = bearish coil (expect breakdown). !!SR (with arrow and count): "!!SR 5x" = A wall of 5 micro-structure levels stacked at this price. Strong support (arrow down, green) or resistance (arrow up, red). CVD DIV: "CVD DIV (up arrow)" = Bullish CVD divergence. Price is making lower lows but CVD is improving -- hidden buying. "CVD DIV (down arrow)" = Bearish CVD divergence. Price making higher highs but CVD declining -- hidden selling. VA BREAK: "VA BREAK (up arrow)" or "VA BREAK (down arrow)" = Price just broke out of the Value Area. A thick green or red line extends forward showing the breakout level. This is a high-momentum signal. VOLUME SPIKE: "x3.2" = Volume on this candle is 3.2x the average. Shows in magenta above the candle. REJECT: "REJECT (arrow)" = Price momentum is pushing into a wall of support or resistance. Warns of a potential rejection/reversal at that wall. ===================================== 11. SEQUENCE PATTERNS (triangles) ===================================== These track a full institutional flow sequence through 4 stages: 1. ABSORPTION = institution absorbs orders at a level 2. FLOW SHIFT = delta reverses confirming direction 3. SWEEP = liquidity grab confirms intent 4. BREAKOUT = Value Area breakout completes the pattern PROGRESS LABELS (small, during build-up): "SEQ:SHIFT" or "SEQ:SWEEP" = Sequence is building, currently at that stage. COMPLETED SEQUENCE (large triangle + label): Hot pink triangle (up or down) with "SEQ BULL " or "SEQ BEAR ". The number is the sequence score. This is the highest-confidence signal in DSMS. A full 4-stage institutional sequence just completed. ===================================== 12. CANDLE TECH (colored candle borders) ===================================== Certain candles get a colored border and a small label: - Green border = bullish pattern detected (hammer, bullish engulfing, etc.) - Red border = bearish pattern detected (shooting star, bearish engulfing, etc.) The label shows: "R 5" = Reversal pattern, score 5 "(up arrow) 3" = Continuation pattern, score 3 Higher score = more confirming factors (CVD alignment, volume surge, trend direction). Thicker border = stronger pattern. ===================================== 13. LIQUIDITY VOID LINES ===================================== Yellow dashed horizontal lines extending left from the profile. These mark price levels with very low volume -- gaps where price moved through quickly without much trading. When price returns to these levels, it tends to move through them fast again or react sharply. ===================================== 14. STATE OF THE ARENA TABLE (corner dashboard) ===================================== The table in the corner of the chart is the real-time scoring dashboard. It combines all signals into one weighted score from -100 (max bearish) to +100 (max bullish). HEADER ROW: Shows the overall market state and final score. States: BREAKOUT, TRENDING, COMPRESSED, CONTESTED, or NEUTRAL. COMPONENT ROWS (each scored -100 to +100, weighted into final score): Delta Flow (10%) -- raw buying vs selling pressure on current bar CVD Flow (10%) -- cumulative volume delta trend and EMA band position Flow Shift (9%) -- recent delta direction reversals Absorption (9%) -- institutional stop hunt detection Sequence (8%) -- institutional flow sequence progress Confluence (7%) -- structural + psychological signal agreement OB/FVG (7%) -- nearest order block or gap bias Sweep (7%) -- recent liquidity grab signals MTF (6%) -- multi-timeframe alignment (2m/5m/15m) Volume (6%) -- spike detection Walls (6%) -- support/resistance cluster strength Accel (5%) -- delta acceleration (2nd derivative of momentum) Iceberg (4%) -- hidden institutional order detection Candle (3%) -- pattern recognition score POC Shift (3%) -- value area migration direction The final score is the weighted sum, clamped to -100 to +100. 70+ or below -70 = STRONG conviction 40-69 = MEDIUM conviction 15-39 = WEAK conviction Below 15 = no clear direction Each row shows a text status, numeric score, and a visual bar made of blocks. Green blocks = bullish. Red blocks = bearish. More blocks = stronger signal. SIGNAL SECTION (bottom of table): Shows the single highest-priority actionable signal right now. "Key" = what the signal is based on "Action" = suggested stance (BUY / SELL / HOLD / CAUTION) "Watch" = what to watch for next ===================================== QUICK REFERENCE - COLOR GUIDE ===================================== Cyan/Teal ......... Bullish structures, support, buy signals Red/Orange ........ Bearish structures, resistance, sell signals Green ............. Bullish momentum, buyers winning Red ............... Bearish momentum, sellers winning Yellow ............ Liquidity voids, caution zones Purple ............ FVG gap zones Hot Pink .......... Completed sequence patterns Magenta ........... Volume spikes, sweep highlights Gold .............. Predictive zone projections White text ........ All on-chart signal labels ===================================== ALERTS ===================================== DSMS has 6 built-in alerts you can set from TradingView's alert menu: Flow Shift -- delta direction reversed at a price level Volume Spike -- volume exceeds threshold with bin concentration VA Breakout -- price broke out of the Value Area Strong Confluence -- multiple signals align above the confluence threshold Absorption -- institutional absorption pattern detected Sequence Complete -- full 4-stage institutional sequence finished To set an alert: click the alarm clock icon in TradingView, select DSMS as the condition source, pick the alert type, and choose your notification method. Each alert can be toggled on/off in the settings panel. ===================================== SETTINGS OVERVIEW ===================================== Everything is toggleable. The main groups in settings are: Core Settings -- lookback period, number of bins, profile width Display Options -- toggle heatmap, delta flow, volume breakdown, POC 1M Scalping -- CVD line, zoomed-out mode, volume trend arrows Signal Settings -- enable/disable each signal type Advanced Tuning -- compression bars, confidence thresholds OB/FVG Settings -- order block depth, FVG stripe count, max blocks Candle Tech -- pattern detection and scoring Liquidity Sweeps -- wick ratio, volume requirement, score display Tier 3: Flow Intel -- sequence patterns, multi-timeframe (2m/5m/15m), predictive zones Colors -- customize every major visual element State of the Arena -- table position, size, and which components to show
Pine Script® Indikator
von SurgeGuru
blueprint_ephemeris_lib🔭 Library blueprint_ephemeris_lib Consolidated planetary ephemeris library with improved accuracy. Supersedes previous individual planet libraries (lib_vsop_core, lib_vsop_mercury, lib_vsop_venus, etc.). One import gives you geocentric/heliocentric positions for all 10 solar system bodies. █ ACCURACY — VALIDATED AGAINST JPL DE440 Every planetary body was validated against NASA's DE440 ephemeris (via Skyfield). Using only 1.6% of the full VSOP87D theory (511 of 31,577 terms), this library achieves sub-arcminute accuracy for all planets: Sun 0.004° (14 arcseconds) Mercury 0.005° (18") Venus 0.006° (22") Mars 0.010° (36") Jupiter 0.007° (25") Saturn 0.009° (32") Uranus 0.013° (47") Neptune 0.017° (61") Moon 0.062° (3.7') Pluto 0.059° (3.5') All bodies under 0.1° RMS — more than sufficient for aspect calculations, ingress timing, and planetary line work. The Sun is accurate to 14 arcseconds using a truncated series that fits entirely inside Pine Script's token limits. █ WHAT'S NEW (V2) The original ephemeris required 11 chained library imports. A full validation audit uncovered critical coefficient errors and motivated this rewrite: • L1 Precession Fix — All 8 VSOP87 planets had incorrect longitude rate coefficients (VSOP87B values instead of VSOP87D). Each was missing +0.24382 rad/millennium of general precession. This single correction reduced error from ~0.75° to < 0.1° across the board. • 28% Smaller — 4,300 lines across 11 files → ~3,100 lines in 1 file. • Single Import — No dependency chain. Faster execution. • Moon Improvements — Functions accept raw `time` directly. Node functions renamed with explicit north/south designation. █ THEORIES VSOP87D (Bretagnon & Francou, 1988) — Mercury through Neptune 511 truncated terms out of 31,577 total (1.6%). Heliocentric spherical coordinates in the ecliptic of date. ELP2000-82 (Chapront-Touzé & Chapront, 1983) — Moon 91 terms (48 longitude + 43 latitude) from Meeus Chapter 47. Meeus Series (Meeus, 1998) — Pluto Analytical series from "Astronomical Algorithms" Ch. 37. Valid ±1 century from J2000. █ HOW TO USE Import the library: import BlueprintResearch/blueprint_ephemeris_lib/1 as eph Basic — plot a planet's geocentric longitude and declination: float jupiter_lon = eph.get_longitude(eph.Planet.Jupiter, time, true) float jupiter_decl = eph.get_declination(eph.Planet.Jupiter, time) plot(jupiter_lon, "Jupiter Geo Lon", color.yellow) plot(jupiter_decl, "Jupiter Decl", color.red) Retrograde detection: bool mercury_retro = eph.is_retrograde(eph.Planet.Mercury, time) bgcolor(mercury_retro ? color.new(color.red, 90) : na) Moon nodes and declination: float north_node = eph.get_mean_north_node_lon(time) float south_node = eph.get_mean_south_node_lon(time) float moon_decl = eph.get_declination(time) plot(north_node, "North Node", color.green) plot(south_node, "South Node", color.purple) plot(moon_decl, "Moon Declination", color.orange) Dynamic planet selection from input: string planet_str = input.string("Sun", "Planet", options= ) eph.Planet p = eph.string_to_planet(planet_str) float geo = eph.get_longitude(p, time, true) float helio = eph.get_longitude(p, time, false) float speed = eph.get_speed(p, time) plot(geo, "Geocentric", color.yellow) plot(helio, "Heliocentric", color.blue) plot(speed * 100, "Speed x100", color.white) All functions accept TradingView's `time` variable directly. █ FUNCTIONS Unified API (all planets): `get_longitude(Planet, time, preferGeo)` — geo or heliocentric longitude `get_declination(Planet, time)` — equatorial declination `get_speed(Planet, time)` — longitude speed (°/day) `is_retrograde(Planet, time)` — true when retrograde `string_to_planet(string)` — name to enum Averages : `get_avg6_geo_lon` / `get_avg6_helio_lon` — Mercury–Saturn `get_avg8_geo_lon` / `get_avg8_helio_lon` — Mercury–Neptune Moon (direct access): `get_geo_ecl_lon(time)` · `get_geo_ecl_lat(time)` · `get_declination(time)` `get_mean_north_node_lon(time)` · `get_mean_south_node_lon(time)` `get_true_north_node_lon(time)` · `get_true_south_node_lon(time)` `get_north_node_declination(time)` · `get_south_node_declination(time)` █ LIMITATIONS • Truncated series — sub-degree accuracy, not sub-arcsecond. More than sufficient for ingress timing and aspect work. • Validated against DE440 across 250 years (1850–2100). Over this full span, the worst-case VSOP87 planet (Uranus) is 0.017° RMS / 0.043° max error. Ingress dates manually verified back to the late 1800s with consistent accuracy. • Pluto uses Meeus series, limited to ±1 century from J2000. • Moon has no speed function. █ ACKNOWLEDGMENTS Coefficient validation was made possible by Greg Miller's VSOP87 multi-language project, which provides the complete VSOP87D coefficient tables in accessible formats. His work converting the original Fortran data files into CSV/JSON for multiple languages was essential for identifying the L1 precession errors in the original libraries. Miller released this work into the public domain. github.com/gmiller123456/vsop87-multilang References : • Meeus, Jean. Astronomical Algorithms (2nd Ed., 1998) • Bretagnon & Francou. VSOP87 Solutions (Astronomy & Astrophysics, 1988) • Chapront-Touzé & Chapront. ELP2000-82 (1983) █ OPEN SOURCE MIT License — part of the Blueprint Research open-source toolkit. Source code on GitHub get_geo_ecl_lon(time_)   Returns geocentric ecliptic longitude of the Moon.   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). get_geo_ecl_lat(time_)   Returns geocentric ecliptic latitude of the Moon.   Parameters:      time_ (float)   Returns: (float) Latitude in degrees. get_obliquity_j(time_)   Returns mean obliquity of the ecliptic.   Parameters:      time_ (float)   Returns: (float) Obliquity in degrees. get_declination(time_)   Returns geocentric equatorial declination of the Moon.   Parameters:      time_ (float)   Returns: (float) Declination in degrees, range where positive is north. get_declination(p, t)   Returns planetary geocentric equatorial declination.   Parameters:      p (series Planet) : (Planet) Planet to query.      t (float) : (float) Unix timestamp in milliseconds (use built-in 'time' variable).   Returns: (float) Geocentric declination in degrees, range where positive is north. @note Declination is always geocentric (no heliocentric equivalent in library). get_mean_north_node_lon(time_)   Returns mean longitude of the Moon's North Node (ascending node).   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). @note Mean node is a simple averaged calculation, reducing computational error. Used for declination calculations. get_mean_south_node_lon(time_)   Returns mean longitude of the Moon's South Node (descending node).   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). Equals North Node + 180°. get_true_north_node_lon(time_)   Returns true longitude of the Moon's North Node with perturbation corrections.   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). @note True node includes periodic perturbations but formula is low precision. Consider using mean node for consistency. get_true_south_node_lon(time_)   Returns true longitude of the Moon's South Node with perturbation corrections.   Parameters:      time_ (float)   Returns: (float) Longitude in degrees, range [0, 360). Equals True North Node + 180°. get_north_node_declination(time_)   Returns declination of the Moon's North Node.   Parameters:      time_ (float)   Returns: (float) Declination in degrees, range (bounded by obliquity). @note Uses mean node for calculation (more consistent than true node). get_south_node_declination(time_)   Returns declination of the Moon's South Node.   Parameters:      time_ (float)   Returns: (float) Declination in degrees. Inverse of North Node declination. normalizeLongitude(lon)   Normalizes any longitude value to the range [0, 360) degrees.   Parameters:      lon (float) : (float) Longitude in degrees (can be any value, including negative or >360).   Returns: (float) Normalized longitude in range [0, 360). string_to_planet(planetStr)   Converts a planet string identifier to Planet enum value.   Parameters:      planetStr (string) : (string) Planet name (case-insensitive). Supports formats: "Sun", "☉︎ Sun", "sun", "SUN"   Returns: (Planet) Corresponding Planet enum. Returns Planet.Sun if string not recognized. @note Supported planet strings: Sun, Moon, Mercury, Venus, Earth, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto get_longitude(p, t, preferGeo)   Returns planetary longitude with automatic coordinate system selection.   Parameters:      p (series Planet) : (Planet) Planet to query.      t (float) : (float) Unix timestamp in milliseconds (use built-in 'time' variable).      preferGeo (bool) : (bool) If true, return geocentric; if false, return heliocentric.   Returns: (float) Longitude in degrees, normalized to range [0, 360). @note Sun and Moon always return geocentric regardless of preference (heliocentric not applicable). get_speed(p, t)   Returns planetary geocentric longitude speed (rate of change).   Parameters:      p (series Planet) : (Planet) Planet to query.      t (float) : (float) Unix timestamp in milliseconds (use built-in 'time' variable).   Returns: (float) Geocentric longitude speed in degrees per day. Negative values indicate retrograde motion. Returns na for Moon. @note Speed is always geocentric (no heliocentric equivalent in library). Moon speed calculation not implemented. get_avg6_geo_lon(t)   get_avg6_geo_lon @description Returns the arithmetic average of the geocentric longitudes for the six outer planets: Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average geocentric longitude of the six outer planets in degrees, range [0, 360). get_avg6_helio_lon(t)   get_avg6_helio_lon @description Returns the arithmetic average of the heliocentric longitudes for the six outer planets: Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average heliocentric longitude of the six outer planets in degrees, range [0, 360). get_avg8_geo_lon(t)   get_avg8_geo_lon @description Returns the arithmetic average of the geocentric longitudes for all eight classical planets: Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average geocentric longitude of all eight classical planets in degrees, range [0, 360). get_avg8_helio_lon(t)   get_avg8_helio_lon @description Returns the arithmetic average of the heliocentric longitudes for all eight classical planets: Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, and Pluto.   Parameters:      t (float) : (float) Time in Unix timestamp (milliseconds).   Returns: (float) Average heliocentric longitude of all eight classical planets in degrees, range [0, 360). is_retrograde(p, t)   Returns true if the planet is currently in retrograde motion (geocentric speed < 0) == 0 = stationary.   Parameters:      p (series Planet) : The planet to check.      t (float) : Time in Unix timestamp (milliseconds).   Returns: true if the planet is in retrograde, false otherwise.
Pine Script® Bibliothek
von BlueprintResearch
2
MAX + OffsetThis indicator plots the highest value over a configurable lookback period, using a selectable price source (High, Low, Open, or Close). It is designed to provide a clear and stable reference for dynamic resistance levels, with the ability to apply a vertical price offset directly on the chart. The offset allows the line to be shifted upward or downward based on the user-defined value, making it useful for: Fine-tuning resistance zones Defining entry and exit margins Adapting levels to different trading styles The indicator uses a single buffer, is lightweight, non-repainting, and fully compatible with any market and timeframe. 🔧 Inputs Price: High / Low / Open / Close Period: number of bars used to calculate the high Offset: vertical price displacement Positive values move the line upward Negative values move the line downward ✅ Features Single buffer (single plotted line) Clean and thin line Stable period-high calculation Works on Forex, indices, stocks, and cryptocurrencies Ideal as a dynamic resistance or structural price reference
Pine Script® Indikator
von MarkiStrategy
Bullish Flag Breakout Alert//@version=5 indicator("Bullish Flag Breakout Alert", overlay=true) // Inputs flagLookback = input.int(15, "Flag High Lookback") volMultiplier = input.float(1.5, "Volume Multiplier") // Calculations flagHigh = ta.highest(high, flagLookback) avgVol = ta.sma(volume, 20) // Breakout condition breakout = close > flagHigh and volume > avgVol * volMultiplier // Plot plot(flagHigh, "Flag High", color=color.orange) plotshape(breakout, style=shape.triangleup, location=location.belowbar, color=color.green, size=size.small, text="BO") // Alert alertcondition(breakout, title="Bullish Flag Breakout")
Pine Script® Indikator
von nitinrise9
Normalized ROC - Two Security SpreadThis is my exploratory script for comparing the movement of two securities: the one that is studied is compared to some benchmark (like QQQ etc.). The movements of both are measured as ROC(t) normalized with each others own ATR. Normalized ROCs are then subtracted to create a "spread". The plot draws both securities' NormROC as lines and the spread as a histogram. So, histogram shows green, when the stock is stronger than the benchmark even in their normalized terms, indicating strong momentum, and vice versa as red. Furthermore, the indicator marks with triangles so called hidden strength and hidden weakness. Hidden strength occurs when Benchmark (e.g. QQQ) is weak, but the stock is not. The assumption is that when the benchmark turns positive the stock is ready to run faster. Respectively, hidden weakness is when Benchmark is strong, but the stock does not follow. Of course, there will be many false signals, these are just potential indications of strength and weakness. Parameters can be adjusted, length of ROC and the line smoothing EMA. Also alerts can be set for histogram level and the hidden strength/weakness levels. DISCLAIMER: Indicator has not been tested. Use with caution and own responsibility. As always, be aware of false signals. Never make decisions with one indicator only.
Pine Script® Indikator
von wizka
Multi-Strategy Filter: Pivot/Breakout/VWAP/RSI/MACDStrategy Overview: Multi-Confirmation Technical Scanner This filter is a high-probability trend-following system that combines three core trading methodologies: Pivot Points (for institutional levels), Breakout Trading (for price action momentum), and VWAP (for volume-weighted value tracking). To ensure accuracy and avoid false breakouts, a signal is only generated when at least three of these core strategies align, further validated by a "Sweet Spot" RSI (momentum confirmation without being overbought) and a bullish MACD crossover. This multi-layered approach identifies stocks with strong institutional support and significant upward momentum.
Pine Script® Indikator
von fimasan