Começar

Pesquisar nos scripts por "足球日本vs中国"

GBTC & BTCE Premium Indicator- This indicator illustrates the premium of GBTC and the European equivalent, BTCE. Relative to the spot price of Bitcoin - It represents the premium investors are willing to pay to be able to gain exposure to Bitcoin . Whilst holding them in an investment vehicle such as a 401k or an ISA. - The premiums can be plotted. GBTC vs BTCUSD and BTCE vs BTCEUR OR - The "real price" of BTCUSD , GBTC and BTCE (denominated in USD) can be plotted against each other
Indicador Pine Script®
por Pinnacle_Investor
2
Probability: Bull/Bear Dominance | Ratio | Bar CountIntro What's the probability of the next bar being red? How about green? Well, there are many ways to quantify the probability but I am presenting just one stupidly simple (but generally accurate) way to measure it. Strangely... no one has done this before that I can find. I try to check if someone else has done it first (Pro Tip: Plz do this. We honestly don't need the 5 trillionth "MTF MAs" script.) Indicator Its a basic counting script, but the nice thing about this script is you choose the time range. It starts counting from a specified point of your choosing. It counts up the bull bars and bear bars separately. Bull Bar = Close > Open Bear Bar = Open > Close You can look at them in sum or as a ratio of Green Bars : Red Bars I know, it's almost too simple. But, here's some interesting food for thought from a layman to fellow laymen. Analysis/Edge Between the time of candle open and candle close, the price can do one of three things, close higher, close lower, or close equal to. 'Equal to' is rare on higher timeframes in liquid markets and it provides no useful information. Thus, we'll nix it for purposes of this conversation. So boil it down. The next candle is going to be a red candle or a green candle. It is popular to refer to the general probability of most candles as 50/50, with trader's mission in life being to seek an edge that tilts the probabilities slightly in their favor. The truth is the odds are probably never actually 50/50, but knowing the precisely correct probability is unknowable, just like the accuracy of a weather forecast is inherently unknowable. What we're trying to do as traders is develop systems that give us predictive probabilistic outcomes that correspond with future realities based on various ways of measuring the market (most often heavily dependent on the past). The reality is that the market can be measured in many, many different ways. The important thing is that you measure it in a way that is accurate, relevant, and universally applicable. So look at this indicator here: You start from a point in time on a chosen timeframe and you put red bars in the red column, green in the green column, and count them all up. Then you make a ratio, in this case, Green : Red. What the ratio shows you is the percentage of green bars compared to red bars . At the time of this screenshot, the 4h on the SPX starting from the 2020 bottom is showing a ratio of 1.2. This means there have been 20% more green bars than there have been red bars. Now there are 1,000 directions you can take this discussion. What is the overall volatility picture, the size of the red bars vs the green bars, what happens if you miss out on the 5 biggest green bars... so many more variables that you would need to take into account to develop a true edge from this idea. But, the bottom line fact (which is what I like about this) is that we can take this data and say with a certain level of confidence that on the SPX you have a 20% better shot at making money (otherwise stated there's a 60/40 chance) if you open a LONG trade at the beginning of a 4h candle than if you open a short. That's useful information. One could argue that it's not a complete strategy in and of itself (although I bet it could be with a couple of additional parameters). But I can tell you, based on the 4h candles in the 2020 rally if you open a short, the deck is stacked against you from this perspective. And we can actually somewhat demonstrate this to be true for our dataset because we can look at the price history and see who likely made more money. The SPX is up 1000pts off the bottom. So, thus far, for this dataset, it rings true; Bulls have been doing way better in the latter part of 2020 than the bears. Conclusion Predictive systems with a small number of variables tend to be more robust than a system with many variables when applied to a complex system. I may keep updating this script if people like it and determine aspects like population vs sample size, confidence intervals, volatility, and exclusion of outliers. For now, this is just an opening foray into the basic idea of how we can establish an edge in the markets. It really can be this simple. Thanks for Reading.
Indicador Pine Script®
por kurtsmock
9
Bar Balance [LucF]Bar Balance extracts the number of up, down and neutral intrabars contained in each chart bar, revealing information on the strength of price movement. It can display stacked columns representing raw up/down/neutral intrabar counts, or an up/down balance line which can be calculated and visualized in many different ways. WARNING: This is an analysis tool that works on historical bars only. It does not show any realtime information, and thus cannot be used to issue alerts or for automated trading. When realtime bars elapse, the indicator will require a browser refresh, a change to its Inputs or to the chart's timeframe/symbol to recalculate and display information on those elapsed bars. Once a trader understands this, the indicator can be used advantageously to make discretionary trading decisions. Traders used to work with my  Delta Volume Columns Pro  will feel right at home in this indicator's Inputs . It has lots of options, allowing it to be used in many different ways. If you value the bar balance information this indicator mines, I hope you will find the time required to master the use of Bar Balance well worth the investment. █  OVERVIEW The indicator has two modes: Columns and Line . Columns • In Columns mode you can display stacked Up/Down/Neutral columns. • The "Up" section represents the count of intrabars where `close > open`, "Down" where `close < open` and "Neutral" where `close = open`. • The Up section always appears above the centerline, the Down section below. The Neutral section overlaps the centerline, split halfway above and below it.  The Up and Down sections start where the Neutral section ends, when there is one. • The Up and Down sections can be colored independently using 7 different methods. • The signal line plotted in Line mode can also be displayed in Columns mode. Line • Displays a single balance line using a zero centerline. • A variable number of independent methods can be used to calculate the line (6), determine its color (5), and color the fill (5).  You can thus evaluate the state of 3 different components with this single line. • A "Divergence Levels" feature will use the line to automatically draw expanding levels on divergence events. Features available in both modes • The color of all components can be selected from 15 base colors, with 16 gradient levels used for each base color in the indicator's gradients. • A zero line can show a 6-state aggregate value of the three main volume balance modes. • The background can be colored using any of 5 different methods. • Chart bars can be colored using 5 different methods. • Divergence and large neutral count ratio events can be shown in either Columns or Line mode, calculated in one of 4 different methods. • Markers on 6 different conditions can be displayed. █  CONCEPTS Intrabar inspection Intrabar inspection means the indicator looks at lower timeframe bars ( intrabars ) making up a given chart bar to gather its information. If your chart is on a 1-hour timeframe and the intrabar resolution determined by the indicator is 5 minutes, then 12 intrabars will be analyzed for each chart bar and the count of up/down/neutral intrabars among those will be tallied. Bar Balances and calculation methods The indicator uses a variety of methods to evaluate bar balance and to derive other calculations from them: 1. Balance on Bar : Uses the relative importance of instant Up and Down counts on the bar. 2. Balance Averages : Uses the difference between the EMAs of Up and Down counts. 3. Balance Momentum : Starts by calculating, separately for both Up and Down counts, the difference between the same EMAs used in Balance Averages and an SMA of double the period used for the EMAs. These differences are then aggregated and finally, a bounded momentum of that aggregate is calculated using RSI. 4. Markers Bias : It sums the bull/bear occurrences of the four previous markers over a user-defined period (the default is 14). 5. Combined Balances : This is the aggregate of the instant bull/bear bias of the three main bar balances. 6. Dual Up/Down Averages : This is a display mode showing the EMA calculated for each of the Up and Down counts. Interpretation of neutral intrabars What do neutral intrabars mean? When price does not change during a bar, it can be because there is simply no interest in the market, or because of a perfect balance between buyers and sellers. The latter being more improbable, Bar Balance assumes that neutral bars reveal a lack of interest, which entails uncertainty. That is the reason why the option is provided to interpret ratios of neutral intrabars greater than 50% as divergences. It is also the rationale behind the option to dampen signal lines on the inverse ratio of neutral intrabars, so that zero intrabars do not affect the signal, and progressively larger proportions of neutral intrabars will reduce the signal's amplitude, as the balance calcs using the up/down counts lose significance. The impact of the dampening will vary with markets. Weaker markets such as cryptos will often contain greater numbers of neutral intrabars, so dampening the Line in that sector will have a greater impact than in more liquid markets. █  FEATURES 1 — Columns • While the size of the Up/Down columns always represents their respective importance on the bar, their coloring mode is independent. The default setup uses a standard coloring mode where the Up/Down columns over/under the zero line are always in the bull/bear color with a higher intensity for the winning side. Six other coloring modes allow you to pack more information in the columns. When choosing to color the top columns using a bull/bear gradient on Balance Averages, for example, you will end up with bull/bear colored tops. In order for the color of the bottom columns to continue to show the instant bar balance, you can then choose the "Up/Down Ratio on Bar — Dual Solid Colors" coloring mode to make those bars the color of the winning side for that bar. • Line mode shows only the line, but Columns mode allows displaying the line along with it. If the scale of the line is different than that of the scale of the columns, the line will often appear flat. Traders may find even a flat line useful as its bull/bear colors will be easily distinguishable. 2 — Line • The default setup for Line mode uses a calculation on "Balance Momentum", with a fill on the longer-term "Balance Averages" and a line color based on the "Markers Bias". With the background set on "Line vs Divergence Levels" and the zero line on the hard-coded "Combined Bar Balances", you have access to five distinct sources of information at a glance, to which you can add divergences, divergences levels and chart bar coloring. This provides powerful potential in displaying bar balance information. • When no columns are displayed, Line mode can show the full scale of whichever line you choose to calculate because the columns' scale no longer interferes with the line's scale. • Note that when "Balance on Bar" is selected, the Neutral count is also displayed as a ratio of the balance line. This is the only instance where the Neutral count is displayed in Line mode. • The "Dual Up/Down Averages" is an exception as it displays two lines: one average for the Up counts and another for the Down counts. This mode will be most useful when Columns are also displayed, as it provides a reference for the top and bottom columns. 3 — Zero Line The zero line can be colored using two methods, both based on the Combined Balances, i.e., the aggregate of the instant bull/bear bias of the three main bar balances. • In "Six-state Dual Color Gradient" mode, a dot appears on every bar. Its color reflects the bull/bear state of the Combined Balances, and the dot's brightness reflects the tally of balance biases. • In "Dual Solid Colors (All Bull/All Bear Only)" a dot only appears when all three balances are either bullish or bearish. The resulting pattern is identical to that of Marker 1. 4 — Divergences • Divergences are displayed as a small circle at the top of the scale. Four different types of divergence events can be detected. Divergences occur whenever the bull/bear bias of the method used diverges with the bar's price direction. • An option allows you to include in divergence events instances where the count of neutral intrabars exceeds 50% of the total intrabar count. • The divergence levels are dynamic levels that automatically build from the line's values on divergence events. On consecutive divergences, the levels will expand, creating a channel. This implementation of the divergence levels corresponds to my view that divergences indicate anomalies, hesitations, points of uncertainty if you will. It excludes any association of a pre-determined bullish/bearish bias to divergences. Accordingly, the levels merely take note of divergence events and mark those points in time with levels. Traders then have a reference point from which they can evaluate further movement. The bull/bear/neutral colors used to plot the levels are also congruent with this view in that they are determined by price's position relative to the levels, which is how I think divergences can be put to the most effective use. 5 — Background • The background can show a bull/bear gradient on four different calculations. You can adjust its brightness to make its visual importance proportional to how you use it in your analysis. 6 — Chart bars • Chart bars can be colored using five different methods. • You have the option of emptying the body of bars where volume does not increase, as does my TLD indicator, the idea behind this being that movement on bars where volume does not increase is less relevant. 7 — Intrabar Resolution You can choose between three modes. Two of them are automatic and one is manual:   a) Fast, Longer history, Auto-Steps (~12 intrabars) : Optimized for speed and deeper history. Uses an average minimum of 12 intrabars.   b) More Precise, Shorter History Auto-Steps (~24 intrabars) : Uses finer intrabar resolution. It is slower and provides less history. Uses an average minimum of 24 intrabars.   c) Fixed : Uses the fixed resolution of your choice. Auto-Steps calculations vary for 24/7 and conventional markets in order to achieve the proper target of minimum intrabars. You can choose to view the intrabar resolution currently used to calculate delta volume. It is the default. The proper selection of the intrabar resolution is important. It must achieve maximal granularity to produce precise results while not unduly slowing down calculations, or worse, causing runtime errors. 8 — Markers Six markers are available: 1. Combined Balances Agreement : All three Bar Balances are either bullish or bearish. 2. Up or Down % Agrees With Bar : An up marker will appear when the percentage of up intrabars in an up chart bar is greater than the specified percentage. Conditions mirror to down bars. 3. Divergence confirmations By Price : One of the four types of balance calculations can be used to detect divergences with price. Confirmations occur when the bar following the divergence confirms the balance bias. Note that the divergence events used here do not include neutral intrabar events. 4. Balance Transitions : Bull/bear transitions of the selected balance. 5. Markers Bias Transitions : Bull/bear transitions of the Markers Bias. 6. Divergence Confirmations By Line : Marks points where the line first breaches a divergence level. Markers appear when the condition is detected, without delay. Since nothing is plotted in realtime, markers do not appear on the realtime bar. 9 — Settings • Two modes can be selected to dampen the line on the ratio of neutral intrabars. • A distinct weight can be attributed to the count of the latter half of intrabars, on the assumption that later intrabars may be more important in determining the outcome of chart bars. • Allows control over the periods of the different moving averages used in calculations. • The default periods used for the various calculations define the following hierarchy from slow to fast:   Balance Averages: 50,   Balance Momentum: 20,   Dual Up/Down Averages: 20,   Marker Bias: 10. █  LIMITATIONS • This script uses a special characteristic of the `security()` function allowing the inspection of intrabars—which is not officially supported by TradingView. • The method used does not work on the realtime bar—only on historical bars. • The indicator only works on some chart resolutions: 3, 5, 10, 15 and 30 minutes, 1, 2, 4, 6, and 12 hours, 1 day, 1 week and 1 month. The script’s code can be modified to run on other resolutions, but chart resolutions must be divisible by the lower resolution used for intrabars and the stepping mechanism could require adaptation. • When using the "Line vs Divergence Levels — Dual Color Gradient" color mode to fill the line, background or chart bars, keep in mind that a line calculation mode must be defined for it to work, as it determines gradients on the movement of the line relative to divergence levels. If the line is hidden, it will not work. • When the difference between the chart’s resolution and the intrabar resolution is too great, runtime errors will occur. The Auto-Steps selection mechanisms should avoid this. • Alerts do not work reliably when `security()` is used at intrabar resolutions. Accordingly, no alerts are configured in the indicator. • The color model used in the indicator provides for fancy visuals that come at a price; when you change values in Inputs , it can take 20 seconds for the changes to materialize. Luckily, once your color setup is complete, the color model does not have a large performance impact, as in normal operation the `security()` calls will become the most important factor in determining response time. Also, once in a while a runtime error will occur when you change inputs. Just making another change will usually bring the indicator back up. █  RAMBLINGS Is this thing useful? I'll let you decide. Bar Balance acts somewhat like an X-Ray on bars. The intrabars it analyzes are no secret; one can simply change the chart's resolution to see the same intrabars the indicator uses. What the indicator brings to traders is the precise count of up/down/neutral intrabars and, more importantly, the calculations it derives from them to present the information in a way that can make it easier to use in trading decisions. How reliable is Bar Balance information? By the same token that an up bar does not guarantee that more up bars will follow, future price movements cannot be inferred from the mere count of up/down/neutral intrabars. Price movement during any chart bar for which, let's say, 12 intrabars are analyzed, could be due to only one of those intrabars. One can thus easily see how only relying on bar balance information could be very misleading. The rationale behind Bar Balance is that when the information mined for multiple chart bars is aggregated, it can provide insight into the history behind chart bars, and thus some bias as to the strength of movements. An up chart bar where 11/12 intrabars are also up is assumed to be stronger than the same up bar where only 2/12 intrabars are up. This logic is not bulletproof, and sometimes Bar Balance will stray. Also, keep in mind that balance lines do not represent price momentum as RSI would. Bar Balance calculations have no idea where price is. Their perspective, like that of any historian, is very limited, constrained that it is to the narrow universe of up/down/neutral intrabar counts. You will thus see instances where price is moving up while Balance Momentum, for example, is moving down. When Bar Balance performs as intended, this indicates that the rally is weakening, which does necessarily imply that price will reverse. Occasionally, price will merrily continue to advance on weakening strength. Divergences Most of the divergence detection methods used here rely on a difference between the bias of a calculation involving a multi-bar average and a given bar's price direction. When using "Bar Balance on Bar" however, only the bar's balance and price movement are used. This is the default mode. As usual, divergences are points of interest because they reveal imbalances, which may or may not become turning points. I do not share the overwhelming enthusiasm traders have for the purported ability of bullish/bearish divergences to indicate imminent reversals. Superfluity In "The Bed of Procrustes", Nassim Nicholas Taleb writes: To bankrupt a fool, give him information . Bar Balance can display lots of information. While learning to use a new indicator inevitably requires an adaptation period where we put it through its paces and try out all its options, once you have become used to Bar Balance and decide to adopt it, rigorously eliminate the components you don't use and configure the remaining ones so their visual prominence reflects their relative importance in your analysis. I tried to provide flexible options for traders to control this indicator's visuals for that exact reason—not for window dressing. █  NOTES For traders • To avoid misleading traders who don't read script descriptions, the indicator shows nothing in the realtime bar. • The Data Window shows key values for the indicator. • All gradients used in this indicator determine their brightness intensities using advances/declines in the signal—not their relative position in a fixed scale. • Note that because of the way gradients are optimized internally, changing their brightness will sometimes require bringing down the value a few steps before you see an impact. • Because this indicator does not use volume, it will work on all markets. For coders • For those interested in gradients, this script uses an advanced version of the Advance/Decline gradient function from the PineCoders Color Gradient (16 colors) Framework . It allows more precise control over the range, steps and min/max values of the gradients. • I use the PineCoders Coding Conventions for Pine to write my scripts. • I used functions modified from the PineCoders MTF Selection Framework for the selection of timeframes. █  THANKS TO: — alexgrover who helped me think through the dampening method used to attenuate signal lines on high ratios of neutral intrabars. — A guy called Kuan who commented on a Backtest Rookies presentation of their Volume Profile indicator . The technique I use to inspect intrabars is derived from Kuan's code. — theheirophant , my partner in the exploration of the sometimes weird abysses of `security()`’s behavior at intrabar resolutions. — midtownsk8rguy , my brilliant companion in mining the depths of Pine graphics. He is also the co-author of the PineCoders Color Gradient Frameworks .
Indicador Pine Script®
por LucF
29
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!
Indicador Pine Script®
por 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
Estratégia Pine Script®
por 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.
Indicador Pine Script®
por 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...
Indicador Pine Script®
por 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
Indicador Pine Script®
por 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.
Indicador Pine Script®
por 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
Indicador Pine Script®
por 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.
Indicador Pine Script®
por 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.
Indicador Pine Script®
por 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.
Indicador Pine Script®
por 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.
Indicador Pine Script®
por 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))
Indicador Pine Script®
por 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.
Indicador Pine Script®
por 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.
Indicador Pine Script®
por dscottmuller