Get started

Search in scripts for "西布罗姆vs伯恩利"

RedK_Directional Index / K xDMIHere's a modern take on the famous DMI/ADX. i first wrote this on another platform few years ago, so i'm happy to be able to share it on TradingView quick refresher: what does DMI/ADX tell us: ------------------------------------------------------ in simple terms, at the core of this indicator, there are 3 main calculations / lines: the Plus Directional Index ( +DI ) which represents how much the bulls are able to push the high of a bar compared to previous one, the Minus Directional Index ( -DI ), showing how much the bears are able to push the low of a bar from previous one, then the Average Directional index ( ADX ) line, which creates an oscillator of the +DI and -DI to represent the strength of a trend -- usually the lines will be colored accordingly (bulls = green, bears = red, and any different color for the ADX ) Similar to my version of the RSI , we take a classic concept, then use the computing and visualization "super powers" available to us today, to extend and improve on what those masters created in the past. I guess they sort of expected us to do exactly that :) this "extended" version of DMI/ADX provides couple of highly needed features (in my opinion) -- let's explore: trying as much as possible to avoid jargon - pls forgive me if i failed in some places. ------------------------------------------------------------------------------------------------- 1 - the big change: the ability to visualize the ADX in a way that makes some more sense. - the original calculation restricted the ADX to oscillate below zero - i'm sure they had a good reason to build it that way in the past - but to me, it becomes super hard to interpret what the ADX line means, especially when a negative trend (the bears) take over. by removing that restriction and allowing the ADX to oscillate up or down (and we're free to do that, so the indicator shows *us* what *we need* to see), we end up with an improved representation of the trend and the trend strength. - also the original calculation applies a moving average (default 14 bars) of a moving average (another 14 of the Directional Indexes, which represent the strength of bulls vs bears) to calculate the ADX - that makes the ADX very "removed" from the base price values - i change that, and just smooth the initial +Di / -Di then calculate the ADX from there. again, this shows me the outcome of the (relatively) immediate moves. 2 - i use weighted average WMA () in all my averaging calculations .. i believe this type of average is the best to express the importance of recent days / bars vs the ones further in the past, compared to other averaging techniques 3 - ability to make the DMI volume-weighted .. but contrary to my RSI , this is not set by default. 4 - couple of options to view the unrestricted ADX (as an area or as histogram/columns .. which i call Vertical Bars) for improved visualization other stuff: 5 - a "step" option for the ADX .. you can set the step option to an increment of, say 5 or 10. this is in case you prefer to see the trend more in "quality" terms - so the equivalent of weak, medium, strong, v. strong...etc -- since in reality, a number like 47.7683 doesn't really mean anything specific 6 - optional "strong trend" adjustable level Settings & usage suggestion: ----------------------------------- i prefer to use the defaults (length = 7, smoothing = 3, ..etc) -- i believe these are more suitable to the much faster trading that we have now. you can review the comparison chart and see if this works for you, and adjust as you need. from a "signal" standpoint, you can use the xDMI as you use the classic DMI/ADX, bulls (or bears) are in control when the corresponding DI line crosses the other going up, *AND* moving above the "strong trend" level that you can set as an extra filter (usually a value between 20 to 30), while ADX will show the quality/strength of the trend. i suggest you also utilize this indicator with other trend / momentum confirmation methods, and additional analysis and not in isolation - as well as inspecting the prevailing / longer time frame to ensure you're acting in the direction of the broader move / trend. the above chart includes a side-by-side comparison between our new xDMI with the classic DMI/ADX using the same settings - then we add at the bottom panel also the xDMI, but with my default (faster) settings and showing other visualization options that can be utilized - the Moving Averages on the top / price panel is just to help put the price movement into perspective in terms of trend and trend strength. The code is open and commented - please feel free to use, share, comment & provide feedback. if you're a DMI fan, and you find this useful in your trading, i would be more than happy to hear about it Good luck!
Pine Script® indicator
by RedKTrader
7
BEST Engulfing + Breakout StrategyHello traders This is a simple algorithm for a Tradingview strategy tracking a convergence of 2 unrelated indicators. Convergence is the solution to my trading problems. It's a puzzle with infinite possibilities and only a few working combinations. Here's one that I like - Engulfing pattern - Price vs Moving average for detecting a breakout Definition Take out the notebooks :) and some coffee (good for focus). I'm bullish in coffee The engulfing pattern is a two-candle reversal pattern. The second candle completely ‘engulfs’ the real body of the first one, without regard to the length of the tail shadows. The bullish Engulfing pattern appears in a downtrend and is a combination of one red candle followed by a larger green candle The bearish Engulfing pattern appears in a downtrend and is a combination of one green candle followed by a larger red candle Example: imgur.com We're bored sir... what's the point of all this? In summary, an engulfing is a pattern to track reversals. (the whole TradingView audience stands up now giving a standing ovation) Adding the Price vs Moving average filters allows to track reversals with momentums (half of the audience collapsed because this is too awesome) Ok sir... you picked up my interest I included some cool backtest filters: - date range filtering - flexible take profit in USD value (plotted in blue) - flexible stop loss in USD value (plotted in red) All the best Dave
Pine Script® strategy
by Daveatt
22
Premium/Discount (Input)Used to show Contango or Backwardation in futures contracts vs spot price. You can input your own tickers so can technically can be used to compare anything. * In this example I'm showing Okex Quarterly contract vs Okex spot index price because it showcases it better. * If you are using this after 2019 the default setting will not work because I set it to Bitmex which does not currently have a "current contract in front" ticker available. It should be fairly self explanatory, but just ask below if you have any questions.
Pine Script® indicator
by Plumptoiletduck
8
Volume Profile Free Ultra SLI (100 Levels Value Area VWAP) - RRBVolume Profile Free Ultra SLI by RagingRocketBull 2019 Version 1.0 This indicator calculates Volume Profile for a given range and shows it as a histogram consisting of 100 horizontal bars. This is basically the MAX SLI version with +50 more Pinescript v4 line objects added as levels. It can also show Point of Control (POC), Developing POC, Value Area/VWAP StdDev High/Low as dynamically moving levels. Free accounts can't access Standard TradingView Volume Profile, hence this indicator. There are several versions: Free Pro, Free MAX SLI, Free Ultra SLI, Free History. This is the Free Ultra SLI version. The Differences are listed below: - Free Pro: 25 levels, +Developing POC, Value Area/VWAP High/Low Levels, Above/Below Area Dimming - Free MAX SLI: 50 levels, 2x SLI modes for Buy/Sell or even higher res 150 levels - Free Ultra SLI: 100 levels, packed to the limit, 2x SLI modes for Buy/Sell or even higher res 300 levels - Free History: auto highest/lowest, historic poc/va levels for each session Features: - High-Res Volume Profile with up to 100 levels (line implementation) - 2x SLI modes for even higher res: 300 levels with 3x vertical SLI, 100 buy/sell levels with 2x horiz SLI - Calculate Volume Profile on full history - POC, Developing POC Levels - Buy/Sell/Total volume modes - Side Cover - Value Area, VAH/VAL dynamic levels - VWAP High/Low dynamic levels with Source, Length, StdDev as params - Show/Hide all levels - Dim Non Value Area Zones - Custom Range with Highlighting - 3 Anchor points for Volume Profile - Flip Levels Horizontally - Adjustable width, offset and spacing of levels - Custom Color for POC/VA/VWAP levels, Transparency for buy/sell levels WARNING: - Compilation Time: 1 min 20 sec Usage: - specify max_level/min_level/spacing (required) - select range (start_bar, range length), confirm with range highlighting - select volume type: Buy/Sell/Total - select mode Value Area/VWAP to show corresponding levels - flip/select anchor point to position the buy/sell levels - use Horiz Buy/Sell SLI mode with 100 or Vertical SLI with 300 levels if needed - use POC/Developing POC/VA/VWAP High/Low as S/R levels. Usually daily values from 1-3 days back are used as levels for the current day. SLI: use SLI modes to extend the functionality of the indicator: - Horiz Buy/Sell 2x SLI lets you view 100 Buy/Sell Levels at the same time - Vertical Max_Vol 3x SLI lets you increase the resolution to 300 levels - you need at least 2 instances of the indicator attached to the same chart for SLI to work 1) Enable Horiz SLI: - attach 2 indicator instances to the chart - make sure all instances have the same min_level/max_level/range/spacing settings - select volume type for each instance: you can have a buy/sell or buy/total or sell/total SLI. Make sure your buy volume instance is the last attached to be displayed on top of sell/total instances without overlapping. - set buy_sell_sli_mode to true for indicator instances with volume_type = buy/sell, for type total this is optional. - this basically tells the script to calculate % lengths based on total volume instead of individual buy/sell volumes and use ext offset for sell levels - Sell Offset is calculated relative to Buy Offset to stack/extend sell after buy. Buy Offset = Zero - Buy Length. Sell Offset = Buy Offset - Sell Length = Zero - Buy Length - Sell Length - there are no master/slave instances in this mode, all indicators are equal, poc/va levels are not affected and can work independently, i.e. one instance can show va levels, another - vwap. 2) Enable Vertical SLI: - attach the first instance and evaluate the full range to roughly determine where is the highest max_vol/poc level i.e. 0..20000, poc is in the bottom half (third, middle etc) or - add more instances and split the full vertical range between them, i.e. set min_level/max_level of each corresponding instance to 0..10000, 10000..20000 etc - make sure all instances have the same range/spacing settings - an instance with a subrange containing the poc level of the full range is now your master instance (bottom half). All other instances are slaves, their levels will be calculated based on the max_vol/poc of the master instance instead of local values - set show_max_vol_sli to true for the master instance. for slave instances this is optional and can be used to check if master/slave max_vol values match and slave can read the master's value. This simply plots the max_vol value - you can also attach all instances and set show_max_vol_sli to true in all of them - the instance with the largest max_vol should become the master Auto/Manual Ext Max_Vol Modes: - for auto vertical max_vol SLI mode set max_vol_sli_src in all slave instances to the max_vol of the master indicator: "VolumeProfileFree_MAX_RRB: Max Volume for Vertical SLI Mode". It can be tricky with 2+ instances - in case auto SLI mode doesn't work - assign max_vol_sli_ext in all slave instances the max_vol value of the master indicator manually and repeat on each change - manual override max_vol_sli_ext has higher priority than auto max_vol_sli_src when both values are assigned, when they are 0 and close respectively - SLI is disabled - master/slave max_vol values must match on each bar at all times to maintain proper level scale, otherwise slave's levels will look larger than they should relative to the master's levels. - Max_vol (red) is the last param in the long list of indicator outputs - the only true max_vol/poc in this SLI mode is the master's max_vol/poc. All poc/va levels in slaves will be irrelevant and are disabled automatically. Slaves can only show VWAP levels. - VA Levels of the master instance in this SLI mode are calculated based on the subrange, not the whole range and may be inaccurate. Cross check with the full range. WARNING! - auto mode max_vol_sli_src is experimental and may not work as expected - you can only assign auto mode max_vol_sli_src = max_vol once due to some bug with unhandled exception/buffer overflow in Tradingview. Seems that you can clear the value only by removing the indicator instance - sometimes you may see a "study in error state" error when attempting to set it back to close. Remove indicator/Reload chart and start from scratch - volume profile may not finish to redraw and freeze in an ugly shape after an UI parameter change when max_vol_sli_src is assigned a max_vol value. Assign it to close - VP should redraw properly, but it may not clear the assigned max_vol value - you can't seem to be able to assign a proper auto max_vol value to the 3rd slave instance - 2x Vertical SLI works and tested in both auto/manual, 3x SLI - only manual seems to work (you can have a mixed mode: 2nd instance - auto, 3rd - manual) Notes: - This code uses Pinescript v3 compatibility framework - This code is 20x-30x faster (main for cycle is removed) especially on lower tfs with long history - only 4-5 sec load/redraw time vs 30-60 sec of the old Pro versions - Instead of repeatedly calculating the total sum of volumes for the whole range on each bar, vol sums are now increased on each bar and passed to the next in the range making it a per range vs per bar calculation that reduces time dramatically - 100 levels consist of 50 main plot levels and 50 line objects used as alternate levels, differences are: - line objects are always shown on top of other objects, such as plot levels, zero line and side cover, it's not possible to cover/move them below. - all line objects have variable lengths, use actual x,y coords and don't need side cover, while all plot levels have a fixed length of 100 bars, use offset and require cover. - all key properties of line objects, such as x,y coords, color can be modified, objects can be moved/deleted, while this is not possible for static plot levels. - large width values cause line objects to expand only up/down from center while their length remains the same and stays within the level's start/end points similar to an area style. - large width values make plot levels expand in all directions (both h/v), beyond level start/end points, sometimes overlapping zero line, making them an inaccurate % length representation, as opposed to line objects/plot levels with area style. - large width values translate into different widths on screen for line objects and plot levels. - you can't compensate for this unwanted horiz width expansion of plot levels because width uses its own units, that don't translate into bars/pixels. - line objects are visible only when num_levels > 50, plot levels are used otherwise - Since line objects are lines, plot levels also use style line because other style implementations will break the symmetry/spacing between levels. - if you don't see a volume profile check range settings: min_level/max_level and spacing, set spacing to 0 (or adjust accordingly based on the symbol's precision, i.e. 0.00001) - you can view either of Buy/Sell/Total volumes, but you can't display Buy/Sell levels at the same time using a single instance (this would 2x reduce the number of levels). Use 2 indicator instances in horiz buy/sell sli mode for that. - Volume Profile/Value Area are calculated for a given range and updated on each bar. Each level has a fixed length. Offsets control visible level parts. Side Cover hides the invisible parts. - Custom Color for POC/VA/VWAP levels - UI Style color/transparency can only change shape's color and doesn't affect textcolor, hence this additional option - Custom Width - UI Style supports only width <= 4, hence this additional option - POC is visible in both modes. In VWAP mode Developing POC becomes VWAP, VA High and Low => VWAP High and Low correspondingly to minimize the number of plot outputs - You can't change buy/sell level colors from input (only transparency) - this requires 2x plot outputs => 2x reduces the number of levels to fit the max 64 limit. That's why 2 additional plots are used to dim the non Value Area zones - You can change level transparency of line objects. Due to Pinescript limitations, only discrete values are supported. - Inverse transp correlation creates the necessary illusion of "covered" line objects, although they are shown on top of the cover all the time - If custom lines_transp is set the illusion will break because transp range can't be skewed easily (i.e. transp 0..100 is always mapped to 100..0 and can't be mapped to 50..0) - transparency can applied to lines dynamically but nva top zone can't be completely removed because plot/mixed type of levels are still used when num_levels < 50 and require cover - transparency can't be applied to plot levels dynamically from script this can be done only once from UI, and you can't change plot color for the past length bars - All buy/sell volume lengths are calculated as % of a fixed base width = 100 bars (100%). You can't set show_last from input to change it - Range selection/Anchoring is not accurate on charts with time gaps since you can only anchor from a point in the future and measure distance in time periods, not actual bars, and there's no way of knowing the number of future gaps in advance. - Adjust Width for Log Scale mode now also works on high precision charts with small prices (i.e. 0.00001) - in Adjust Width for Log Scale mode Level1 width extremes can be capped using max deviation (when level1 = 0, shift = 0 width becomes infinite) - There's no such thing as buy/sell volume, there's just volume, but for the purposes of the Volume Profile method, assume: bull candle = buy volume, bear candle = sell volume P.S. I am your grandfather, Luke! Now, join the Dark Side in your father's steps or be destroyed! Once more the Sith will rule the Galaxy, and we shall have peace...
Pine Script® indicator
by RagingRocketBull
112
Volume Profile Free MAX SLI (50 Levels Value Area VWAP) by RRBVolume Profile Free MAX SLI by RagingRocketBull 2019 Version 1.0 All available Volume Profile Free MAX SLI versions are listed below (They are very similar and I don't want to publish them as separate indicators): ver 1.0: style columns implementation ver 2.0: style histogram implementation ver 3.0: style line implementation This indicator calculates Volume Profile for a given range and shows it as a histogram consisting of 50 horizontal bars. It can also show Point of Control (POC), Developing POC, Value Area/VWAP StdDev High/Low as dynamically moving levels. Free accounts can't access Standard TradingView Volume Profile, hence this indicator. There are several versions: Free Pro, Free MAX SLI, Free History. This is the Free MAX SLI version. The Differences are listed below: - Free Pro: 25 levels, +Developing POC, Value Area/VWAP High/Low Levels, Above/Below Area Dimming - Free MAX SLI: 50 levels, packed to the limit, 2x SLI modes for Buy/Sell or even higher res 150 levels - Free History: auto highest/lowest, historic poc/va levels for each session Features: - High-Res Volume Profile with up to 50 levels (3 implementations) - 20-30x faster than the old Pro versions especially on lower tfs with long history - 2x SLI modes for even higher res: 150 levels with 3x vertical SLI, 50 buy/sell levels with 2x horiz SLI - Calculate Volume Profile on full history - POC, Developing POC Levels - Buy/Sell/Total volume modes - Side Cover - Value Area, VAH/VAL dynamic levels - VWAP High/Low dynamic levels with Source, Length, StdDev as params - Show/Hide all levels - Dim Non Value Area Zones - Custom Range with Highlighting - 3 Anchor points for Volume Profile - Flip Levels Horizontally - Adjustable width, offset and spacing of levels - Custom Color for POC/VA/VWAP levels and Transparency for buy/sell levels Usage: - specify max_level/min_level/spacing (required) - select range (start_bar, range length), confirm with range highlighting - select volume type: Buy/Sell/Total - select mode Value Area/VWAP to show corresponding levels - flip/select anchor point to position the buy/sell levels - use Horiz SLI mode for 50 Buy/Sell or Vertical SLI for 150 levels if needed - use POC/Developing POC/VA/VWAP High/Low as S/R levels. Usually daily values from 1-3 days back are used as levels for the current day. SLI: - use SLI modes to extend the functionality of the indicator: - Horiz Buy/Sell 2x SLI lets you view 50 Buy/Sell Levels at the same time - Vertical Max_Vol 3x SLI lets you increase the resolution to 150 levels - you need at least 2 instances of the indicator attached to the same chart for SLI to work 1) Enable Horiz SLI: - attach 2 indicator instances to the chart - make sure all instances have the same min_level/max_level/range/spacing settings - select volume type for each instance: you can have a buy/sell or buy/total or sell/total SLI. Make sure your buy volume instance is the last attached to be displayed on top of sell/total instances without overlapping. - set buy_sell_sli_mode to true for indicator instances with volume_type = buy/sell, for type total this is optional. - this basically tells the script to calculate % lengths based on total volume instead of individual buy/sell volumes and use ext offset for sell levels - Sell Offset is calculated relative to Buy Offset to stack/extend sell after buy. Buy Offset = Zero - Buy Length. Sell Offset = Buy Offset - Sell Length = Zero - Buy Length - Sell Length - there are no master/slave instances in this mode, all indicators are equal, poc/va levels are not affected and can work independently, i.e. one instance can show va levels, another - vwap. 2) Enable Vertical SLI: - attach the first instance and evaluate the full range to roughly determine where is the highest max_vol/poc level i.e. 0..20000, poc is in the bottom half (third, middle etc) or - add more instances and split the full vertical range between them, i.e. set min_level/max_level of each corresponding instance to 0..10000, 10000..20000 etc - make sure all instances have the same range/spacing settings - an instance with a subrange containing the poc level of the full range is now your master instance (bottom half). All other instances are slaves, their levels will be calculated based on the max_vol/poc of the master instance instead of local values - set show_max_vol_sli to true for the master instance. for slave instances this is optional and can be used to check if master/slave max_vol values match and slave can read the master's value. This simply plots the max_vol value - you can also attach all instances and set show_max_vol_sli to true in all of them - the instance with the largest max_vol should become the master Auto/Manual Ext Max_Vol Modes: - for auto vertical max_vol SLI mode set max_vol_sli_src in all slave instances to the max_vol of the master indicator: "VolumeProfileFree_MAX_RRB: Max Volume for Vertical SLI Mode". It can be tricky with 2+ instances - in case auto SLI mode doesn't work - assign max_vol_sli_ext in all slave instances the max_vol value of the master indicator manually and repeat on each change - manual override max_vol_sli_ext has higher priority than auto max_vol_sli_src when both values are assigned, when they are 0 and close respectively - SLI is disabled - master/slave max_vol values must match on each bar at all times to maintain proper level scale, otherwise slave's levels will look larger than they should relative to the master's levels. - Max_vol (red) is the last param in the long list of indicator outputs - the only true max_vol/poc in this SLI mode is the master's max_vol/poc. All poc/va levels in slaves will be irrelevant and are disabled automatically. Slaves can only show VWAP levels. - VA Levels of the master instance in this SLI mode are calculated based on the subrange, not the whole range. Cross check with the full range. WARNING! - auto mode max_vol_sli_src is experimental and may not work as expected - you can only assign auto mode max_vol_sli_src = max_vol once due to some bug with unhandled exception/buffer overflow in Tradingview. Seems that you can clear the value only by removing the indicator instance - sometimes you may see a "study in error state" error when attempting to set it back to close. Remove indicator/Reload chart and start from scratch - volume profile may not finish to redraw and freeze in an ugly shape after an UI parameter change when max_vol_sli_src is assigned a max_vol value. Assign it to close - VP should redraw properly, but it may not clear the assigned max_vol value - you can't seem to be able to assign a proper auto max_vol value to the 3rd slave instance - 2x Vertical SLI works and tested in both auto/manual, 3x SLI - only manual seems to work Notes: - This code is 20x-30x faster (main for cycle is removed) especially on lower tfs with long history - only 2-3 sec load/redraw time vs 30-60 sec of the old Pro versions - Instead of repeatedly calculating the total sum of volumes for the whole range on each bar, vol sums are now increased on each bar and passed to the next in the range making it a per range vs per bar calculation that reduces time dramatically - hist_base for levels still results is ugly redraw - if you don't see a volume profile check range settings: min_level/max_level and spacing, set spacing to 0 (or adjust accordingly based on the symbol's precision, i.e. 0.00001) - you can view either of Buy/Sell/Total volumes, but you can't display Buy/Sell levels at the same time using a single instance (this would 2x reduce the number of levels). Use 2 indicator instances in horiz buy/sell sli mode for that. - Volume Profile/Value Area are calculated for a given range and updated on each bar. Each level has a fixed length. Offsets control visible level parts. Side Cover hides the invisible parts. - Custom Color for POC/VA/VWAP levels - UI Style color/transparency can only change shape's color and doesn't affect textcolor, hence this additional option - Custom Width - UI Style supports only width <= 4, hence this additional option - POC is visible in both modes. In VWAP mode Developing POC becomes VWAP, VA High and Low => VWAP High and Low correspondingly to minimize the number of plot outputs - You can't change buy/sell level colors from input (only plot transparency) - this requires 2x plot outputs => 2x reduces the number of levels to fit the max 64 limit. That's why 2 additional plots are used to dim the non Value Area zones - All buy/sell volume lengths are calculated as % of a fixed base width = 100 bars (100%). You can't set show_last from input to change it - There's no such thing as buy/sell volume, there's just volume, but for the purposes of the Volume Profile method, assume: bull candle = buy volume, bear candle = sell volume P.S. Gravitonium Levels Are Increasing. Unobtainium is nowhere to be found! Links on Volume Profile and Value Area calculation and usage: www.tradingview.com stockcharts.com onlinelibrary.wiley.com
Pine Script® indicator
by RagingRocketBull
25
ST_Trend_ReversalSTRONG TREND REVERSAL INDICATOR The code is the percentage difference between the spot price of a given financial asset and its 200-day MA of that period. My standard setup is Daily, and I think it's got very good predictive power at that timeframe. It can be read in two ways: 1. Values extremely above or below the 200-period MA present chances of buying/selling agains the prevailing trend. 2. Values closely above or below the 200-period MA are make-or-break market periods, where a medium-term trend becomes evident. Breaks above or below the MA are associated with strong chances of directional movements. But it's not fool-proof as false breaks have become commonplace nowadays. Other way to use it is as confirmation of breakdowns: For example, an asset that loses its 200-day MA and then can't rally above it becomes exposed to steep losses afterwards. It's also helpful to use in volatility trading: the closer the asset goes to its MA, the lower goes implied vol, and thus better opportiunities to be long volatility on those occasions where direction is hard to predict. STRI = close/(200dMA) Values over 100 indicate percentage premiums of spot vs its moving average. Values below indicate percentage discounts of spot vs its moving average.
Pine Script® indicator
by Daniel_Urdaneta
2
Ersoy-intersection(Kesisme)-Update-1website: www.ersoytoptas.com Newspaper : tr.investing.com hi , Friends i wanna be someone who wants to help everyone updated my script he published some time ago. What happened? * intersection When ever Bar Color Yellow Be * Alarms to be more comprehensible * Short and Long Days Choosing a Opportunities * Source Opportunities All Charts Usable( Example ;15,30,60 ... vs) and ALL MARKETS ( Stocks , forex , ... vs) i strive to improve further Easy to get
Pine Script® indicator
by Lemnos
8
Trend MACD [JopAlgo]Trend MACD — momentum made obvious (4-state histogram) What it does (one line): A clean MACD histogram using EMA(fast) − EMA(slow) with a signal line. The columns change color to show trend side and momentum change at a glance. Green = above 0 and rising → positive trend, momentum building White (upside) = above 0 but fading → still positive, momentum cooling White (downside) = below 0 but improving → still negative, momentum recovering Red = below 0 and falling → negative trend, momentum building down Zero line = the bull/bear divider. Distance from zero = thrust. Color change = momentum shift. What you’ll see Dashed zero line for the trend divider Column histogram with the 4-state color logic above No clutter—just momentum and regime, clean Read it in 3 seconds: Which side of 0? Are bars getting bigger or smaller? Did the color flip? How to use it (simple playbook) Direction filter Look for longs while histogram is ≥ 0. Look for shorts while histogram is ≤ 0. Timing Green sequence (above 0, growing): join pullbacks at real levels. White above 0: positive but cooling—buy pullbacks only at levels, don’t chase. White below 0: negative but improving—prepare for reclaim trades at levels. Red sequence: trend down—sell pops at levels. Location first (always) Use Volume Profile v3.2 (VAH/VAL/POC/LVNs) and Anchored VWAP (session/weekly/event). No level, no trade. Quality check (optional, strong) CVDv1 : execute when Alignment OK and no Absorption against your side. RVOL (if you track it): prefer breakouts with RVOL above cutoff. Entries, exits, risk (keep it tight) Continuation long: price retests VAL / AVWAP / MA cluster in an up regime (≥ 0). Histogram stays ≥ 0 and turns green again → enter. Stop: under structure. Targets: POC/HVNs or next swing. Break + retest: breakout through a level while histogram flips from white→green above 0 (or white→red below 0 for shorts). Enter on the retest that holds. Trim / avoid: when bars shrink toward 0 (white) into your target / HVN—momentum is cooling. Don’t chase fresh highs with white bars. Settings that matter (how to tune) Fast Length (default 25) Shorter = quicker turns (more noise). Longer = steadier, slower. Slow Length (default 200) Big backbone. For intraday you might use 21/55 or 12/26; for swing the default 25/200 or 20/100 is solid. Signal Smoothing (default 9) Higher = smoother, fewer flips. Lower = more reactive. Source close is fine; if you use hlc3, expect slightly smoother behavior. Suggested presets Scalp (1–5m): 12 / 26 / 9 Intraday (15m–1H): 21 / 55 / 9 Swing (2H–4H): 25 / 100 or 25 / 200 / 9 Daily backdrop: 20 / 100 or 50 / 200 / 9 (execute on lower TF) Pattern cheat sheet Green staircase above 0 → trend leg; buy pullbacks to VP/AVWAP. White above 0 → positive but tiring; avoid chasing; wait for retest. Flip through 0 with expansion → regime change; use the first retest at a level. Red staircase below 0 → trend down; sell pops at VP edges. Diverging price vs shrinking bars → momentum thinning; tighten risk. Best combos (kept simple) Volume Profile v3.2: entries at VAH/VAL/LVNs, targets at POC/HVNs. Anchored VWAP: reclaim/reject with matching histogram side is high-quality timing. CVDv1: take MACD-aligned setups with flow (ALIGN OK, no Absorption). RVOL: confirmation that the push has participation. Common mistakes this helps you avoid Longs with red momentum or shorts with green momentum. Chasing new highs on white (cooling) bars. Trading mid-range when histogram keeps whipsawing around 0 (do less; wait for level). Disclaimer: This indicator is an educational tool, not financial advice. Markets are risky; you can lose money. Always test your settings, trade at defined levels, and use risk management. Data/feeds vary across venues; outcomes may differ. No guarantees or warranties are provided.
Pine Script® indicator
by JopAlgo
Smart Choppy Index v1 [JopAlgo]Smart Choppy Index v1 — decide trend vs. chop in seconds What it does (one line): Measures the percent range of price over a lookback and tells you if the market is choppy (do less, fade edges) or trending (go with breaks/pullbacks). Range% = (Highest High − Lowest Low) / Close × 100 over length Below Choppy Threshold → likely range (red tint / X marker) Above Trending Threshold → likely trend (green tint / ● marker) Between them = mixed/transition (no background) Read the pane fast Orange line: the live Range%. Red dashed line: Choppy Threshold. Green dashed line: Trending Threshold. Background: soft red during chop, soft green during trend. Markers: X at the top when chop is detected, ● at the bottom when trend is detected. TL;DR: Red = play defense / mean-revert. Green = play offense / trend-follow. Simple playbook (copy this into your process) Identify regime Choppy (Range% < red line): prefer mean-reversion at VP edges / AVWAP; smaller targets, quicker exits. Trending (Range% > green line): prefer breakouts + pullbacks; hold to POC/HVNs or structure. Only execute at real locations Volume Profile v3.2 : VAH/VAL/POC/LVNs for entries/targets. Anchored VWAP : reclaims/rejections for timing. Quality check (optional, recommended) CVDv1 : execute with flow (Alignment OK, strong Imbalance, no Absorption against your side). Risk Stops go beyond structure/level, not on indicator flips. If regime flips right after entry (green → red or red → green), consider tightening or exiting early. Timeframe guidance 1–5m (scalps): length 14–20. You’ll see more flips—use thresholds a touch wider and execute only at edges. 15m–1H (intraday): length 14–34. Sweet spot for day trading bias. 2H–4H (swing): length 20–50. Fewer, cleaner signals; great for planning. 1D+ (position): length 50–100. Use as backdrop; trigger on lower TFs. Settings that actually matter (and how to tune) Lookback Period (length) Shorter = faster regime changes; longer = smoother, fewer flips. Choppy Threshold (%) / Trending Threshold (%) Calibrate by history: scroll back and mark typical Range% during range days vs trend days for your market/TF. If you get too many trend flags, raise the green threshold. If everything looks “choppy,” lower the red threshold slightly. Background color Turn off if your chart feels busy; markers remain. How to trade it with other tools In Chop (red): Fade VAH/VAL/AVWAP touches toward POC with tight stops. Confirm with CVDv1 (avoid longs if Absorption is red, etc.). In Trend (green): Break + retest at VP levels/AVWAP. Add on pullbacks that hold while Range% stays above the green line. Patterns to recognize Squeeze → Expansion: Range% ramps from below red toward/through green → expect a trend phase. Exhaustion → Balance: After a long green phase, Range% falls back toward the middle → take profits into HVNs, expect more two-way trade. False break tell: Level poke while Range% sits near red → low odds of follow-through; prefer reclaims. Practical defaults to start length = 14 Choppy Threshold = 1.5% Trending Threshold = 2.5% Process: Regime → Location → Flow → Execute with structure-based risk Serious Disclaimer & Licensing This script and description are provided for educational purposes only and do not constitute financial, investment, or trading advice. Markets are risky; you can lose some or all of your capital. Past performance does not guarantee future results. You are solely responsible for your trading decisions, including evaluating the suitability of this tool in your process, testing it on historical and simulated data, and managing risk. This indicator relies on exchange data that may vary across venues; differences in volume, liquidity, and price feeds can impact results. No warranty is made—express or implied—regarding accuracy, completeness, or fitness for a particular purpose. assumes no liability for any direct or consequential losses arising from the use of this script or description. License: This Pine Script® code is released under the Mozilla Public License 2.0 (MPL 2.0), © JopAlgo. You may use, modify, and distribute the code in accordance with MPL 2.0 terms.
Pine Script® indicator
by JopAlgo
Kairi Relative Index Upgrated v1Kairi Relative Index Upgraded v1 — how far from “fair” are we, right now? Most oscillators mash together price and momentum in ways that are hard to explain to a new trader. KRI is refreshingly simple: it measures how far price is from its moving average, as a percent of that average. KRI = 100 × (Price − SMA) / SMA Above 0 → price is above its average (stretched up). Below 0 → price is below its average (stretched down). The farther from 0, the more stretched we are from the mean. This upgraded version keeps the pane clean (zero line, colored KRI, optional guide rails at +Line Above / Line Below) so you can read extension, reversion pressure, and reclaims at a glance—on any timeframe. (If you add screenshots: image #1 should label the zero line and ± threshold lines; image #2 should show a textbook “overshoot at VAH/VAL + KRI extreme → rotate back to POC.”) What you’re seeing (and how to read it fast) KRI line Green when KRI ≥ 0 (price above SMA) Red when KRI < 0 (price below SMA) Zero line = the moving average itself (no stretch). Guide lines (default +10/−10) = “This is pretty far for this setting.” Treat these as review-and-decide zones, not auto-trade signals. Three quick reads: Magnitude: how far from the mean (size of KRI). Direction: above/below zero (which side of the mean). Turn: KRI curling back toward zero (reversion starting) or accelerating away (trend impulse continuing). What KRI really measures (plain-English) The SMA(length) is your “fair value” line for this indicator. KRI tells you the percentage deviation from that fair value—normalized, so you can compare across assets/timeframes with the same length. Because it’s a pure distance metric, KRI excels at: spotting over-extensions into VP edges (VAH/VAL) and AVWAP, timing mean-reversion back to POC/AVWAP in balance, confirming reclaims (KRI crossing back through zero at a level), framing pullbacks in trend (healthy dips usually avoid deep negative KRI in strong uptrends). Using KRI on any timeframe The workflow is always Location → Flow → KRI: Location: a real level (Volume Profile v3.2’s VAH/VAL/POC/LVNs or Anchored VWAP). Flow quality: check CVDv1 (Alignment OK? Absorption not red?). KRI: are we stretched into/away from the level, and is KRI turning? Scalping (1–5m) Fade the stretch (balance): At VAH/VAL or Session AVWAP, an extreme KRI that rolls back toward zero = quick rotation to the middle (POC/AVWAP). Don’t fade if bands are expanding and flow is strong (CVDv1 says go) — big KRI can stay big in expansion. Intraday (15m–1H) Continuation after pullback: In uptrends, look for shallow negative KRI at support (VAL/AVWAP) that turns up → join trend. Failed breakout tell: Price pokes above VAH but KRI barely increases or rolls over quickly → likely a reclaim back inside value. Swing (2H–4H) Edge-to-mean rotations: At composite VAH/VAL, KRI extremes are great context: fade back to POC/HVNs if flow doesn’t confirm a breakout. Reclaim confirmation: After a flush below Weekly AVWAP, KRI crossing back up through zero on the reclaim bar is a clean green light. Position (1D–1W) Regime posture: Multi-day runs with sustained positive KRI (and shallow dips) = constructive; mirror for downtrends. Use KRI pullbacks to ~0 at Weekly AVWAP for adds. Entries, exits, and risk (simple rules) Mean-reversion entry: At VAH/VAL or AVWAP, wait for KRI extreme at/through your guide line and a turn back toward zero. Stop: just beyond the level; Target: POC/HVN or the zero line on KRI. Trend-continuation entry: In a trend, take pullbacks where KRI stays modest (doesn’t blow through your lower/upper guide) and turns back with the trend at the level. Avoid: chasing breakouts where KRI is already extreme and still climbing unless CVDv1 says Alignment OK + no Absorption and you have a clean retest. Settings that matter (and how to tune them) Length (default 50): defines the moving average “fair value.” Shorter (20–34): faster, more signals, more noise—good for intraday. Longer (50–100): steadier, better for swings/position. Source (default close): keep it simple; hlc3 or close both work. Line Above / Below (defaults +10/−10): your review zones. Tune them to the asset/timeframe: Scroll back 6–12 months and eyeball typical |KRI| spikes. Set your lines around the 80th–90th percentile of |KRI| for that market and length. Majors often need smaller thresholds than thin alts on the same timeframe. Tip: If your KRI is always beyond the lines, increase length or widen the thresholds. If it never touches them, shorten length or tighten thresholds. What to look for (pattern cheat sheet) Stretch into level → curl: KRI tags an extreme right at VAH/VAL/AVWAP, then turns back → classic rotation. Shallow pullback in trend: KRI dips toward zero but doesn’t hit your lower guide, then turns up at support → continuation. No-juice break: New price high with weaker KRI (smaller positive % vs prior leg) → breakout lacks extension; plan for retest or reclaim. Zero-line reclaims: After a washout, KRI crosses zero as price reclaims AVWAP/VAL → clean confirmation. Combining KRI with other tools Cumulative Volume Delta v1 (CVDv1): Use KRI for stretch/turn, CVDv1 for quality. A KRI extreme at VAH with CVDv1 Absorption (red) is a do-not-chase; look for the fail/reclaim. A KRI pullback toward zero at VAL with Alignment OK + strong Imbalance + no Absorption = high-quality continuation. Volume Profile v3.2: KRI’s best signals happen at VAH/VAL/POC/LVNs. LVN traversals with rising KRI often run quickly to the next HVN—use VP for targets. Anchored VWAP : Treat AVWAP as fair-value rails. KRI zero cross on an AVWAP reclaim is your green flag; KRI extreme + failure to accept beyond AVWAP warns of a fake break. Common pitfalls KRI helps you avoid Buying high into a tired move: KRI already very positive at VAH and rolling over = likely rotation; wait. Fading true expansion: In strong trends with confirmed flow, KRI can remain extreme; don’t automatically fade just because it’s “far.” Wrong thresholds: Copy-pasting ±10 to every market/timeframe can mislead. Calibrate to the market you trade. Practical defaults to start with Length: 50 Lines: +10 / −10 as placeholders—calibrate later. Timeframes: great out of the box on 15m–4H; for 1–5m try Length 34 and tighter lines; for daily swings try Length 100 and broader lines. Process: Level → CVDv1 quality → KRI stretch/turn. If any of the three disagree, wait for the retest. Disclaimer & Licensing This indicator and its description are provided for educational purposes only and do not constitute financial or investment advice. Trading involves risk, including the possible loss of capital. makes no warranties and assumes no responsibility for any decisions or outcomes resulting from the use of this script. Past performance is not indicative of future results. Use at your own risk. Licensing & Attribution: Copyright (c) 2018–present, Alex Orekhov (everget). Modified and upgraded by . The original “Kairi Relative Index” is released under the MIT License, and this derivative is distributed under the MIT License as well. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files to deal in the Software without restriction, subject to the conditions of the MIT License, including the above copyright notice and this permission notice. The Software is provided “AS IS,” without warranty of any kind, express or implied.
Pine Script® indicator
by JopAlgo
Cycle Momentum Filter [JopAlgo]Cycle Momentum Filter (CMF) — spot “when” to engage the market, on any timeframe Markets breathe in cycles (expansion → contraction) while momentum and trend decide which moves actually travel. CMF is a compact filter that blends those ideas so you can answer two questions before you click: Is this a good moment to take a trade? (cycle position) If I take it, is there enough force behind the move to carry it? (momentum + trend) CMF does not replace your levels—use it with your location tools (e.g., Volume Profile v3.2 and Anchored VWAP). It simply keeps you out of entries taken at the wrong part of the swing or against weak momentum. (When you add screenshots: image #1 should label each sub-line and the green/yellow/red background; image #2 can show CMF turning green at VAL + AVWAP before a rotation back to POC.) What you’re seeing (and how to read it at a glance) CMF draws five sub-lines around a zero line, plus a background color: Cycle Oscillator (blue): where you are in the swing. Above zero ≈ cycle crest side; below zero ≈ trough side. ROC % (purple): short-term price acceleration. Above zero = positive momentum; below zero = negative. MACD Histogram (orange): classic impulse measure (fast–slow EMA gap). Above zero = bullish impulse. EWO (cyan): Elliott Wave Oscillator (EMA fast – EMA slow). Above zero = trend tilt up. RSI-MA (gray, plotted as RSI−50): smoothed RSI relative to 50. Above zero = buyers have the relative strength. Background color = the filter result: Green → bullish window: cycle favors longs and momentum/trend/RS confirm. Red → bearish window: mirror logic. Yellow → neutral: at least one piece disagrees—do less, or wait for alignment. For new traders: Every sub-line crossing above/below zero is a yes/no vote. Green happens only when all bullish checks are true; red when all bearish checks are true. How CMF is built (plain-English version) Cycle (DPO-style): CMF subtracts a displaced SMA from price to remove trend and expose the swing. Below 0 = you’re on the dip side of the cycle; above 0 = rally side. Momentum (ROC): percent change over roc_length bars; tells you if price is actually accelerating. Impulse (MACD hist): measures push from fast vs slow EMAs. Trend tilt (EWO): broader drift via two EMAs (fast/slow). Participation bias (RSI-MA): smoothed RSI relative to 50 (plotted as RSI−50 so its zero line matches the others). The signal rules are strict AND conditions: Bullish = cycle < 0 and ROC > 0 and MACD hist > 0 and EWO > 0 and RSI-MA > 0. Bearish = cycle > 0 and ROC < 0 and MACD hist < 0 and EWO < 0 and RSI-MA < 0. Otherwise Neutral. This strictness is deliberate: it cuts a lot of low-quality entries. Using CMF on any timeframe The framework is the same—only your anchors/targets change as you zoom. Scalping (1–5m) Where: VP v3.2 VAL/VAH/LVNs or Session AVWAP. When: take longs when CMF turns green on/after a dip to your level; shorts when it turns red on/after a pop into resistance. Skip: yellow reads in the middle of the range; that’s chop. Tip: on very fast pairs, require two consecutive green/red bars before entry. Intraday (15m–1H) Use CMF green to time pullbacks to AVWAP or VA edges in the trend direction. In balance days, wait for CMF color + level alignment to fade back to POC. If CMF flips yellow after entry, tighten risk; if it flips against you, consider exiting early. Swing (2H–4H) Treat first green after a higher-timeframe pullback to Weekly AVWAP or composite VAL as your A-setup. If CMF stays green through the first pullback, consider adding; the opposite for red in downtrends. Position (1D–1W) Fewer, bigger decisions: CMF green at Monthly/Quarterly AVWAP or at composite VAL suggests rotation toward POC/HVNs; CMF red at VAH suggests mean-reversion lower. If CMF can’t turn green/red at key retests, that’s valuable: the level likely won’t hold. Entries, exits, and risk (simple rules) Entry: trade at a level when CMF just flips to your side (green for longs / red for shorts). Invalidation: if CMF reverts to yellow immediately, it’s a warning; if it flips to the opposite color, that’s your soft stop condition—tighten or exit unless higher-timeframe context argues otherwise. Targets: use Volume Profile v3.2 (POC/HVNs) and AVWAP (mean) for logical destinations. Don’t use CMF alone for stops; place them beyond the level or structure. Settings that actually matter (and how to tune them) Cycle Length (default 20): swing detection. Shorter (10–14): quicker flips, better for scalps. Longer (30–40): steadier cycle for swings/position. ROC Length (default 10): momentum lookback. Shorter: earlier yes/no, more noise. Longer: slower, more selective. MACD Fast/Slow (5/13) & EWO Fast/Slow (5/35): impulse and drift. Increase slow values to calm false flips; decrease fast to react sooner. RSI Length (14) & Smoothing (5): participation tilt. Reduce smoothing for faster confirmation; increase to avoid whips. Background on/off: keep it on while learning; once you’re comfortable, you can hide the background and read the lines against zero. Tuning tip: If you trade only a few coins, optimize Cycle and ROC first; leave MACD/EWO defaults. Then decide how strict you want RSI (try RSI smoothing = 3 for faster reads). What to look for (pattern cheatsheet) Green at a dip-level (VAL/AVWAP) → rotate toward POC/HVN. Red at a pop-level (VAH/AVWAP) → rotate down toward POC/HVN. Color holds through the retest → continuation is more likely. Color flips against the breakout → watch for failed break and reclaim. Only one line disagrees (e.g., ROC < 0 while others > 0) → expect slower follow-through; consider waiting one bar. Combining CMF with other tools Volume Profile v3.2 : Use VAH/VAL/POC/LVNs for where. CMF answers when. Green at VAL → mean-reversion long to POC. Red at VAH → fade to POC. LVN breaks with green often travel quickly to the next HVN. Anchored VWAP : Reclaim of AVWAP + CMF turns green → higher-quality long; rejection + red → cleaner short. Weekly AVWAP + CMF color is a reliable swing compass. Cumulative Volume Delta v1 (CVDv1): CMF says “now”, CVDv1 says “how good”. Prefer CMF green when CVDv1 Alignment = OK, Imbalance strong, Absorption ≠ red. If CMF flips green but CVDv1 shows Absorption (red), do not chase; look for a reclaim instead. Common pitfalls CMF helps you avoid Buying high in the cycle: CMF keeps longs to when the cycle is on the dip side and momentum/trend agree. Forcing trades on yellow: yellow is your do-less mode—wait for alignment. Ignoring flow at levels: CMF gives the window, but quality still matters; confirm with CVDv1. Practical defaults to start with Cycle 20 | ROC 10 | MACD 5/13 | EWO 5/35 | RSI 14 (smooth 5) Works out of the box on 15m–4H. For scalps, try Cycle 14 / ROC 7–9 / RSI smooth 3. For daily swings, Cycle 30–34 / ROC 12–14. Alerts (what they tell you) Bullish Signal: CMF turned green (all bullish checks passed). Use it as a heads-up; still anchor the entry to VP/AVWAP. Bearish Signal: CMF turned red. Same rule: wait for the level. Open source & disclaimer This indicator is published open source so traders can learn, tweak, and build rules they trust. Tools guide decisions; risk management decides outcomes. Disclaimer — Not Financial Advice. The “Cycle Momentum Filter ” indicator and this description are provided for educational purposes only and do not constitute financial or investment advice. Trading involves risk, including possible loss of capital. makes no warranties and assumes no responsibility for any trading decisions or outcomes resulting from the use of this script. Past performance is not indicative of future results.
Pine Script® indicator
by JopAlgo
SM OTC style Supply/Demand Zones Lite+//@version=6 indicator("OTC SD MTF Lite+", "OTCSDmtf+", overlay=true, max_boxes_count=200, max_labels_count=200) // ================= Inputs ================= useH4 = input.bool(true, "Show 4H zones") useD1 = input.bool(true, "Show 1D zones") useW1 = input.bool(true, "Show 1W zones") useM1 = input.bool(false, "Show 1M zones") baseLen = input.int(2, "Base length (HTF bars)", 1, 5) wickPctMax = input.float(35.0, "Max wick % in base", 0, 100) impulseX = input.float(1.5, "Departure body vs ATR (x)", 0.5, 5.0) atrLen = input.int(14, "ATR length (HTF)") extendBars = input.int(2000, "Extend bars on chart", 200, 10000) maxPerTF = input.int(12, "Max zones per TF", 3, 30) showLegend = input.bool(true, "Show tiny legend (4H/1D/1W/1M)") onlyNearest = input.bool(false, "Show ONLY nearest zone above/below") hideOverlapTF = input.bool(true, "Hide overlapping zones within each TF (keep newest)") showNearestLabels = input.bool(false, "Show distance labels to nearest above/below") // --- Hard cap for future drawing with xloc.bar_index --- FUTURE_CAP = 500 // Colors (Demand hues per TF). Supply uses red for contrast. colH4 = color.new(color.teal, 78) colD1 = color.new(color.blue, 78) colW1 = color.new(color.orange, 78) colM1 = color.new(color.purple, 78) colSup= color.new(color.red, 78) // ================= Helpers ================= wickiness(h, l, o, c) => rng = math.max(h - l, syminfo.mintick) topW = h - math.max(o, c) botW = math.min(o, c) - l 100.0 * (topW + botW) / rng // Returns: (dTrig, dProx, dDist, sTrig, sProx, sDist) f_htfSignals(baseBars, wickMax, xImpulse, aLen) => float _o = open float _h = high float _l = low float _c = close float _atr = ta.atr(aLen) bool ok = true for i = 1 to baseBars ok := ok and (wickiness(_h , _l , _o , _c ) <= wickMax) bool bullDepart = _c > _o and (_c - _o) > xImpulse * _atr bool bearDepart = _c < _o and (_o - _c) > xImpulse * _atr float dTrig = 0.0 float dProx = na float dDist = na float sTrig = 0.0 float sProx = na float sDist = na if ok and bullDepart float hi = ta.highest(_h, baseBars) float lo = ta.lowest(_l, baseBars) dTrig := 1.0 dProx := lo dDist := hi if ok and bearDepart float hi2 = ta.highest(_h, baseBars) float lo2 = ta.lowest(_l, baseBars) sTrig := 1.0 sProx := hi2 sDist := lo2 // ================= Pull HTF signals ================= = request.security(syminfo.tickerid, "240", f_htfSignals(baseLen, wickPctMax, impulseX, atrLen)) = request.security(syminfo.tickerid, "D", f_htfSignals(baseLen, wickPctMax, impulseX, atrLen)) = request.security(syminfo.tickerid, "W", f_htfSignals(baseLen, wickPctMax, impulseX, atrLen)) = request.security(syminfo.tickerid, "M", f_htfSignals(baseLen, wickPctMax, impulseX, atrLen)) // ================= Storage per TF ================= var zH4 = array.new_box() var aH4 = array.new_bool() var lH4 = array.new_label() var sH4 = array.new_int() // 1 = Demand, -1 = Supply var zD1 = array.new_box() var aD1 = array.new_bool() var lD1 = array.new_label() var sD1 = array.new_int() var zW1 = array.new_box() var aW1 = array.new_bool() var lW1 = array.new_label() var sW1 = array.new_int() var zM1 = array.new_box() var aM1 = array.new_bool() var lM1 = array.new_label() var sM1 = array.new_int() // ================= Overlap utils ================= overlap(topA, botA, topB, botB) => not (topA < botB or botA > topB) purgeOverlaps(arrB, arrA, arrL, newTop, newBot) => if hideOverlapTF and array.size(arrB) > 0 for i = 0 to array.size(arrB) - 1 if array.get(arrA, i) box bOld = array.get(arrB, i) float t = box.get_top(bOld) float btm = box.get_bottom(bOld) if overlap(newTop, newBot, t, btm) box.delete(bOld) label.delete(array.get(arrL, i)) array.set(arrA, i, false) // ================= Add zone ================= addZone(arrB, arrA, arrL, arrS, topV, botV, baseColor, isDemand) => purgeOverlaps(arrB, arrA, arrL, topV, botV) int leftX = bar_index - 1 int rightX = bar_index + math.min(extendBars, FUTURE_CAP) // respect +500 cap box b = box.new(leftX, topV, rightX, botV, xloc=xloc.bar_index, bgcolor=baseColor, border_color=color.new(color.black, 0)) float ly = isDemand == 1 ? topV : botV st = isDemand == 1 ? label.style_label_down : label.style_label_up string tagTxt = isDemand == 1 ? "Demand" : "Supply" label l = label.new(leftX, ly, tagTxt, xloc=xloc.bar_index, style=st, textcolor=color.white, color=color.new(color.black, 0), size=size.tiny) array.push(arrB, b) array.push(arrA, true) array.push(arrL, l) array.push(arrS, isDemand) if array.size(arrB) > maxPerTF box.delete(array.shift(arrB)) array.shift(arrA) label.delete(array.shift(arrL)) array.shift(arrS) // ================= Maintain / Invalidate ================= extendAll(arrB, arrA) => if array.size(arrB) > 0 for i = 0 to array.size(arrB) - 1 if array.get(arrA, i) box.set_right(array.get(arrB, i), bar_index + math.min(extendBars, FUTURE_CAP)) // respect +500 cap invalidate(arrB, arrA, arrL) => if array.size(arrB) > 0 for i = 0 to array.size(arrB) - 1 if array.get(arrA, i) box b = array.get(arrB, i) float t = box.get_top(b) float btm = box.get_bottom(b) // Close outside band → remove if close > t or close < btm box.delete(b) label.delete(array.get(arrL, i)) array.set(arrA, i, false) // ================= New HTF bar flags (strict booleans) ================= int chH4 = ta.change(time("240")) int chD1 = ta.change(time("D")) int chW1 = ta.change(time("W")) int chM1 = ta.change(time("M")) bool newBarH4 = useH4 and (not na(chH4)) and (chH4 != 0) bool newBarD1 = useD1 and (not na(chD1)) and (chD1 != 0) bool newBarW1 = useW1 and (not na(chW1)) and (chW1 != 0) bool newBarM1 = useM1 and (not na(chM1)) and (chM1 != 0) // ================= Create zones on new HTF bar ================= if newBarH4 if d4t > 0 and not na(d4p) and not na(d4d) addZone(zH4, aH4, lH4, sH4, d4d, d4p, colH4, 1) if s4t > 0 and not na(s4p) and not na(s4d) addZone(zH4, aH4, lH4, sH4, s4p, s4d, colSup, -1) if newBarD1 if d1t > 0 and not na(d1p) and not na(d1d) addZone(zD1, aD1, lD1, sD1, d1d, d1p, colD1, 1) if s1t > 0 and not na(s1p) and not na(s1d) addZone(zD1, aD1, lD1, sD1, s1p, s1d, colSup, -1) if newBarW1 if w1t > 0 and not na(w1p) and not na(w1d) addZone(zW1, aW1, lW1, sW1, w1d, w1p, colW1, 1) if swt > 0 and not na(swp) and not na(swd) addZone(zW1, aW1, lW1, sW1, swp, swd, colSup, -1) if newBarM1 if m1t > 0 and not na(m1p) and not na(m1d) addZone(zM1, aM1, lM1, sM1, m1d, m1p, colM1, 1) if smt > 0 and not na(smp) and not na(smd) addZone(zM1, aM1, lM1, sM1, smp, smd, colSup, -1) // ================= Maintain & Invalidate (every bar) ================= extendAll(zH4, aH4) extendAll(zD1, aD1) extendAll(zW1, aW1) extendAll(zM1, aM1) invalidate(zH4, aH4, lH4) invalidate(zD1, aD1, lD1) invalidate(zW1, aW1, lW1) invalidate(zM1, aM1, lM1) // ================= Nearest across all TFs ================= tfNearest(arrB, arrA) => int upIdx = -1 int dnIdx = -1 float upDist = 1e10 float dnDist = 1e10 float upBtm = na float dnTop = na if array.size(arrB) > 0 for i = 0 to array.size(arrB) - 1 if array.get(arrA, i) box b = array.get(arrB, i) float t = box.get_top(b) float btm = box.get_bottom(b) if btm >= close float d = btm - close if d < upDist upDist := d upIdx := i upBtm := btm if t <= close float d2 = close - t if d2 < dnDist dnDist := d2 dnIdx := i dnTop := t = tfNearest(zH4, aH4) = tfNearest(zD1, aD1) = tfNearest(zW1, aW1) = tfNearest(zM1, aM1) float upBest = 1e10, dnBest = 1e10 int upArr = -1, upIdxSel = -1, dnArr = -1, dnIdxSel = -1 color upColor = color.new(color.white, 100), dnColor = color.new(color.white, 100) if (not na(uh4y)) and uh4d < upBest upBest := uh4d, upArr := 0, upIdxSel := uh4i, upColor := colH4 if (not na(ud1y)) and ud1d < upBest upBest := ud1d, upArr := 1, upIdxSel := ud1i, upColor := colD1 if (not na(uw1y)) and uw1d < upBest upBest := uw1d, upArr := 2, upIdxSel := uw1i, upColor := colW1 if (not na(um1y)) and um1d < upBest upBest := um1d, upArr := 3, upIdxSel := um1i, upColor := colM1 if (not na(dh4y)) and dh4d < dnBest dnBest := dh4d, dnArr := 0, dnIdxSel := dh4i, dnColor := colH4 if (not na(dd1y)) and dd1d < dnBest dnBest := dd1d, dnArr := 1, dnIdxSel := dd1i, dnColor := colD1 if (not na(dw1y)) and dw1d < dnBest dnBest := dw1d, dnArr := 2, dnIdxSel := dw1i, dnColor := colW1 if (not na(dm1y)) and dm1d < dnBest dnBest := dm1d, dnArr := 3, dnIdxSel := dm1i, dnColor := colM1 // ================= Nearest-only visibility (optional) ================= hideAll(arrB, arrA) => if array.size(arrB) > 0 for i = 0 to array.size(arrB) - 1 if array.get(arrA, i) box.set_bgcolor(array.get(arrB, i), color.new(color.white, 100)) box.set_border_color(array.get(arrB, i), color.new(color.white, 100)) showOne(arrB, arrA, arrS, idx, demColor) => if idx >= 0 and idx < array.size(arrB) if array.get(arrA, idx) bool isDemand = array.get(arrS, idx) == 1 color c = isDemand ? demColor : colSup box.set_bgcolor(array.get(arrB, idx), c) box.set_border_color(array.get(arrB, idx), color.new(color.black, 0)) if onlyNearest hideAll(zH4, aH4), hideAll(zD1, aD1), hideAll(zW1, aW1), hideAll(zM1, aM1) if upArr == 0 showOne(zH4, aH4, sH4, upIdxSel, upColor) if upArr == 1 showOne(zD1, aD1, sD1, upIdxSel, upColor) if upArr == 2 showOne(zW1, aW1, sW1, upIdxSel, upColor) if upArr == 3 showOne(zM1, aM1, sM1, upIdxSel, upColor) if dnArr == 0 showOne(zH4, aH4, sH4, dnIdxSel, dnColor) if dnArr == 1 showOne(zD1, aD1, sD1, dnIdxSel, dnColor) if dnArr == 2 showOne(zW1, aW1, sW1, dnIdxSel, dnColor) if dnArr == 3 showOne(zM1, aM1, sM1, dnIdxSel, dnColor) // ================= Nearest distance labels (optional) ================= var label nearUp = na var label nearDn = na makeNearLabel(y, txt) => label.new(bar_index, y, txt, xloc=xloc.bar_index, style=label.style_label_left, color=color.new(color.black, 0), textcolor=color.white, size=size.tiny) if showNearestLabels if not na(nearUp) label.delete(nearUp) if not na(nearDn) label.delete(nearDn) if upArr != -1 box bUp = upArr == 0 ? array.get(zH4, upIdxSel) : upArr == 1 ? array.get(zD1, upIdxSel) : upArr == 2 ? array.get(zW1, upIdxSel) : array.get(zM1, upIdxSel) float upBtm = box.get_bottom(bUp) float pctUp = math.round(10000.0 * (upBtm - close) / close) / 100.0 nearUp := makeNearLabel(upBtm, "Nearest Above ~ " + str.tostring(pctUp) + "%") if dnArr != -1 box bDn = dnArr == 0 ? array.get(zH4, dnIdxSel) : dnArr == 1 ? array.get(zD1, dnIdxSel) : dnArr == 2 ? array.get(zW1, dnIdxSel) : array.get(zM1, dnIdxSel) float dnTop = box.get_top(bDn) float pctDn = math.round(10000.0 * (close - dnTop) / close) / 100.0 nearDn := makeNearLabel(dnTop, "Nearest Below ~ " + str.tostring(pctDn) + "%") // ================= Tiny legend (dots) ================= var table legend = na if showLegend and na(legend) legend := table.new(position.top_left, 4, 1) if showLegend and not na(legend) table.cell(legend, 0, 0, "● 4H", text_color=color.white, bgcolor=color.new(color.black, 0)) table.cell(legend, 1, 0, "● 1D", text_color=color.white, bgcolor=color.new(color.black, 0)) table.cell(legend, 2, 0, "● 1W", text_color=color.white, bgcolor=color.new(color.black, 0)) table.cell(legend, 3, 0, "● 1M", text_color=color.white, bgcolor=color.new(color.black, 0)) table.cell_set_bgcolor(legend, 0, 0, color.new(color.teal, 70)) table.cell_set_bgcolor(legend, 1, 0, color.new(color.blue, 70)) table.cell_set_bgcolor(legend, 2, 0, color.new(color.orange, 70)) table.cell_set_bgcolor(legend, 3, 0, color.new(color.purple, 70))
Pine Script® indicator
by imsiddharthm
DTM 444 BANDS 🚀DTM 444 BANDS 🚀: The DTM 444 BANDS 🚀 is a powerful, multi-purpose trading indicator combining Supertrend, Dynamic Band Levels, Breakout Signals, and Volume Confirmation to help traders identify high-probability trade setups across different timeframes. 🔧 Key Features ✅ Multi-Timeframe Support Analyze price action across any timeframe using the Timeframe input. All band calculations (High, Low, Midline, and Supertrend) are pulled from a higher timeframe for clearer context. ✅ Dynamic Bands Based on Supertrend High Band: Rolling highest of Supertrend over hiLen period. Low Band: Rolling lowest of Supertrend over loLen period. Midline: Midpoint of the above. Acts like dynamic support/resistance, ideal for trend-following and breakout strategies. ✅ Dual Signal System Breakout Signals (Buy and Sell): Triggered when price breaks the bands with volume confirmation. Supertrend Crossover Signals (Buy1 and Sell1): Classic momentum entries with a confirmation twist. Exit Signals: Optional take-profit/neutral indicators when price reverses. ✅ Volume Confirmation Filter (Optional) Only triggers signals if the volume exceeds its 20-period SMA. Helps filter out false breakouts and weak trends in low-liquidity periods. ✅ Visual Enhancements Color-coded candles based on band positioning (e.g., red = weak, green = strong, etc.) On-chart labels for each signal for quick reference. Real-time Signal Dashboard using Pine Script tables showing: Current signal Volume filter status Live volume vs volume SMA 🧪 Practical Use Cases Trend Traders: Use the Supertrend cross and band breakouts to ride trends early. Breakout Traders: Catch high-probability moves outside established ranges. Swing Traders: Time entries and exits using color-coded bars and exit labels. Volume-Sensitive Traders: Focus on trades with strong volume backing. 📊 Backtest Snapshot Based on the example chart for Reliance Industries (RELIANCE.NS) on the weekly timeframe: Several profitable buy and breakout signals during uptrends. Timely exits and breakdown alerts before reversals. Volume filter keeps trades clean and avoids noise. ⚙️ Customizable Parameters High Length and Low Length (default: 19) Supertrend Multiplier and ATR Length Volume Filter: Toggle ON/OFF Volume SMA Length: Default 20 Custom Timeframe: Choose any higher timeframe for multi-timeframe analysis 📢 Alerts Ready Fully integrated with TradingView alerts: Breakout & Breakdown Supertrend crossovers All alerts respect the volume filter setting 🏁 Final Thoughts DTM 444 BANDS 🚀 is a versatile and adaptive trading system that blends trend analysis, volatility bands, and volume validation. Whether you're a trend trader, breakout hunter, or swing trader — this tool gives you a structured edge with clear visual cues and real-time alerts.
Pine Script® indicator
by KUMARSTOCKS
FEI: Futures Entry Identifier📘 FEI: Futures Entry Identifier FEI is a modular, futures-grade entry engine designed for precision trading across GC1!, MNQ1!, ES1!, and related contracts. It combines manual SVP structure, CHoCH detection, and Colby-style candle strength filters to identify high-probability long and short entries. 🔧 Features • Manual SVP inputs (VAH, VAL, POC) • Symbol-aware filters for micro vs standard contracts • Multi-timeframe signal logic (3m, 5m, 10m, 15m, 30m) • CHoCH detection with optional engulfing filter (default off) • FRVP entry zone plotting after CHoCH confirmation • Candle coloring on CHoCH trigger • Session-aware logic (ETH default, optional RTH-only) • Narratable visuals and audit-safe alerts 🧭 How to Use 1. Input VAH, VAL, and POC manually 2. Select signal timeframe (e.g. 3m or 5m) 3. Watch for CHoCH (white candle = structural shift) 4. Entry line plots at top/bottom of recent range 5. Long/short markers appear when SVP + candle strength align 6. Toggle RTH-only mode if needed 🌟 Why It’s Unique FEI is built for traders who demand clarity, structure, and precision. Every signal is narratable, audit-safe, and resolution-aware—ideal for futures overlays and sniper-grade entries.
Pine Script® indicator
by dscottmuller
KAPITAS CBDR# PO3 Mean Reversion Standard Deviation Bands - Pro Edition ## 📊 Professional-Grade Mean Reversion System for MES Futures Transform your futures trading with this institutional-quality mean reversion system based on standard deviation analysis and PO3 (Power of Three) methodology. Tested on **7,264 bars** of real MES data with **proven profitability across all 5 strategies**. --- ## 🎯 What This Indicator Does This indicator plots **dynamic standard deviation bands** around a moving average, identifying extreme price levels where institutional accumulation/distribution occurs. Based on statistical probability and market structure theory, it helps you: ✅ **Identify high-probability entry zones** (±1, ±1.5, ±2, ±2.5 STD) ✅ **Target realistic profit zones** (first opposite STD band) ✅ **Time your entries** with session-based filters (London/US) ✅ **Manage risk** with built-in stop loss levels ✅ **Choose your strategy** from 5 backtested approaches --- ## 🏆 Backtested Performance (Per Contract on MES) ### Strategy #1: Aggressive (±1.5 → ∓0.5) 🥇 - **Total Profit:** $95,287 over 1,452 trades - **Win Rate:** 75% - **Profit Factor:** 8.00 - **Target:** 80 ticks ($100) | **Stop:** 30 ticks ($37.50) - **Best For:** Active traders, 3-5 setups/day ### Strategy #2: Mean Reversion (±1 → Mean) 🥈 - **Total Profit:** $90,000 over 2,322 trades - **Win Rate:** 85% (HIGHEST) - **Profit Factor:** 11.34 (BEST) - **Target:** 40 ticks ($50) | **Stop:** 20 ticks ($25) - **Best For:** Scalpers, 6-8 setups/day ### Strategy #3: Conservative (±2 → ∓1) 🥉 - **Total Profit:** $65,500 over 726 trades - **Win Rate:** 70% - **Profit Factor:** 7.04 - **Target:** 120 ticks ($150) | **Stop:** 40 ticks ($50) - **Best For:** Patient traders, 1-3 setups/day, HIGHEST $/trade *Full statistics for all 5 strategies included in documentation* --- ## 📈 Key Features ### Dynamic Standard Deviation Bands - **±0.5 STD** - Intraday mean reversion zones - **±1.0 STD** - Primary reversion zones (68% of price action) - **±1.5 STD** - Extended zones (optimal balance) - **±2.0 STD** - Extreme zones (95% of price action) - **±2.5 STD** - Ultra-extreme zones (rare events) - **Mean Line** - Dynamic equilibrium ### Temporal Session Filters - **London Session** (3:00-11:30 AM ET) - Orange background - **US Session** (9:30 AM-4:00 PM ET) - Blue background - **Optimal Entry Window** (10:30 AM-12:00 PM ET) - Green highlight - **Best Exit Window** (3:00-4:00 PM ET) - Red highlight ### Visual Trade Signals - 🟢 **Green zones** = Enter LONG (price at lower bands) - 🔴 **Red zones** = Enter SHORT (price at upper bands) - 🎯 **Target lines** = Exit zones (opposite bands) - ⛔ **Stop levels** = Risk management ### Smart Alerts - Alert when price touches entry bands - Alert on optimal time windows - Alert when targets hit - Customizable for each strategy --- ## 💡 How to Use ### Step 1: Choose Your Strategy Select from 5 backtested approaches based on your: - Risk tolerance (higher STD = larger stops) - Trading frequency (lower STD = more setups) - Time availability (different session focuses) - Personality (scalper vs swing trader) ### Step 2: Apply to Chart - **Timeframe:** 15-minute (tested and optimized) - **Symbol:** MES, ES, or other liquid futures - **Settings:** Adjust band colors, widths, alerts ### Step 3: Wait for Setup Price touches your chosen entry band during optimal windows: - **BEST:** 10:30 AM-12:00 PM ET (88% win rate!) - **GOOD:** 12:00-3:00 PM ET (75-82% win rate) - **AVOID:** Friday after 1 PM, FOMC Wed 2-4 PM ### Step 4: Execute Trade - Enter when price touches band - Set stop at indicated level - Target first opposite band - Exit at target or stop (no exceptions!) ### Step 5: Manage Risk - **For $50K funded account ($250 limit): Use 2 MES contracts** - Stop after 3 consecutive losses - Reduce size in low-probability windows - Track cumulative daily P&L --- ## 📅 Optimal Trading Windows ### By Time of Day - **10:30 AM-12:00 PM ET:** 88% win rate (BEST) ⭐⭐⭐ - **12:00-1:30 PM ET:** 82% win rate (scalping) - **1:30-3:00 PM ET:** 76% win rate (afternoon) - **3:00-4:00 PM ET:** Best EXIT window ### By Day of Week - **Wednesday:** 82% win rate (BEST DAY) ⭐⭐⭐ - **Tuesday:** 78% win rate (highest volume) - **Thursday:**
Pine Script® indicator
by L1f3MA
Trend/Range Composite (Single-Line) v1.4🔹 Step 1: Add it to your chart Copy the whole script. In TradingView → Pine Editor → paste it. Click Add to chart. It will show a white line in a subwindow, plus thresholds at 40 and 60, and a colored background. Optional: You’ll see a status box (top-right of chart) with details like ADX, ATR, slope, etc. 🔹 Step 2: Understand the Score The indicator compresses all signals into a 0–100 “Trend Strength Score”: ≥ 60 = TREND (teal background) → Market is trending, consider trend strategies like vertical spreads, runners, breakouts. ≤ 40 = RANGE (orange background) → Market is choppy/sideways, consider range strategies like butterflies, condors, mean-reversion fades. 40–60 = MIXED (gray background) → Indecision / chop. Best to reduce size or wait for clarity. 🔹 Step 3: Use with Your Trading Plan Intraday (5m, 15m, 30m) Score < 40 → play support/resistance bounces, fade extremes. Score > 60 → play momentum breakouts or pullback continuations. Daily chart Good for swing context (is this month trending or just chopping?). 🔹 Step 4: Alerts You can set TradingView alerts: Cross above 60 → market entering trend mode. Cross below 40 → market entering range mode. Useful if you don’t want to watch constantly. 🔹 Step 5: Confirm with Price Levels The score tells you “trend vs range”, but you still need levels: If score < 40 → mark PDH / PDL (previous day high/low), VAH/VAL, VWAP. Expect rejections/fades. If score > 60 → watch for breakouts beyond PDH/PDL or supply/demand zones.
Pine Script® indicator
by somberTruffle15943
Long Elite Squeeze (LES 2.1) NV/CDV AI LindsayLES 2.1 — Long Elite Squeeze Creator: Hunter Hammond •: Elite × FineFir H.H (AI “Lindsay”) Discord: elitexfinefir LES (“Long Elite Squeeze”) is a momentum + flow-aware long strategy built for small-float, high-velocity stocks. It blends a classic squeeze engine (BB/KC), adaptive RVOL/RSI gating, VWAP slope, ADX trend filtering, WaveTrend timing, and new Net-Volume/CVD flow exits—all wrapped with on-chart HUDs, a trade tracker, trap detection, and a lightweight AI selector to adapt entries to live conditions. Who it’s for (and where it thrives) LES 2.1 is tuned for the morning session and stocks that can really move: Top Pre-Market and Day Gainers Highest or Top Volume on Day Float: ≤ 40M Price: ≤ $20 Volume: ≥ 5× the 30-day average (intraday RVOL pop) Catalyst: ideally a fresh news driver / “day gainer” Timeframe: 1-minute (designed & tuned for 1m). Works on 2m/3m/5m, but wasn’t specifically designed for them (see tuning tips below). Evolution at a glance LES 1.0 — The foundation Squeeze engine using Bollinger vs. Keltner to detect expansion (“squeeze OFF”). EMA – ATR offset line (dynamic risk anchor) with EMA as trend filter. RSI guard for overheated moves. RVOL confirmation using average volume lookback. WaveTrend (WT + Signal) to time entries/exits. Basic buy/sell logic + simple on-chart labels. LES 2.0 — Quality-of-life & timing upgrades AI Lindsay assistant v2 (periodic / contextual commentary). VWAP Slope Detector with sensitivity modes (Loose → Very Strict). Manual defaults pre-tuned for ease of use. Double-EMA trailing (visual take-profit helper). Improved on-chart commentary and Trade Summary (10:30am snapshot). AI Version Suggester (V1/V2/V3 modes) with stickiness/cooldown. Trap Detector Pro (sweep, VWAP reject, blow-off, etc.) with scored severity. Trade Tracker HUD + Entry Checklist HUD. Overall stability & UX polish. LES 2.1 — Flow-based exit superpowers New Flow Exit: integrates 1m Net Volume and 5m CVD-style pressure: 1m NetVol window (rolling sum of signed volume) 5m CVD window (downsampled, smoothed) Debounce (consecutive red bars to avoid one-tick fakes) Optional ATR Guard (only exit if the move is meaningful vs ATR) Cooldown after a flow exit to avoid re-chop Chart labels: “SELL (NV/CVD)” when flow triggers Keeps you in good trends, but kicks you out when aggressive sellers actually show up. How the engine works (plain English) Market prep: We confirm trend & energy using EMA/ATR, RSI, RVOL, Squeeze OFF, and Price > VWAP. Entry mode (V1/V2/V3): V1 — Balanced trades (default “safe” behavior) V2 — Fast trades (more aggressive when action heats up) V3 — Trending trades (stricter; waits for strong slope & trend) You can pick a version manually or let the AI Suggester switch modes based on slope/ADX/RVOL/acceleration (with a cooldown so it doesn’t flip-flop). Entry timing: WaveTrend and squeeze momentum improve timing while VWAP slope avoids buying flat tape. Risk anchor: The EMA – (ATR × Multiplier) “offset line” is your dynamic stop/line in the sand. Exits: Base exits (version-aware): WT crossback, momentum fade, price losing offsetLine or EMA. Flow Exit (2.1): If 1m NetVol and 5m CVD both turn decisively red (with debounce and optional ATR guard), close—no arguing. Entry rules (exactly what has to be true) Buy (Core) — fires when all are true: Not already in a trade Close > EMA and Close > OffsetLine (offsetLine = EMA − ATR × Mult) RVOL confirmed (meets dynamic RVOL multiplier) RSI below the overbought ceiling (version-aware slack in V3) Squeeze OFF (BBs expanded outside Keltner) Price > VWAP (toggleable) Extra for V3 (Trending trades): VWAP slope gate passes (and, if set, VWAP must be green) ADX strong (≥ 25 by design, ≥ 20 baseline) Minimum slopePctPerBar met (default V3 expects ≥ 0.05%/bar) AI Suggester (optional): Scores V1/V2/V3 from conditions like ADX, VWAP slope, RVOL, intrabar acceleration, then locks a pick for aiSwitchCoolBars bars. On-chart help: Checklist HUD lights up ✅/❌ for each gate (EMA, ATR, RVOL, RSI, VWAP, Slope, etc.). Trade Quality Rating (🌟x/10) appears on buy bars if enabled. Exit rules (every sell condition) Base sells (V1/V2): WaveTrend crossback (signal crosses over WT) OR Momentum fade (two darker squeeze momentum bars) OR Close < OffsetLine OR Close < EMA Base sells (V3): Close < OffsetLine OR Close < EMA (trend-respecting; ignores WT/momentum so you’re not shaken out early) Flow Exit (2.1, applies to all versions if enabled): In trade AND Flow Exit enabled 1m NetVol window is red (and ≥ Min |NetVol|) 5m CVD (smoothed) is red **Deb *** FYI: Play with settings until it fits your style, everything thats set default when script is loaded is what I run currently. I made LES 2.1 more customizable than ever to meet every trades style and execution. LES 2.1 with Lindsay upgrade new AI trade tracking feature (when enabled) and risk management LES 2.1 is something special to meet many challenges a trader faces everyday.
Pine Script® indicator
by ElitexFineFir