Inizia

Cerca negli script per "bar"

Machine Learning: Lorentzian Classification█ OVERVIEW A Lorentzian Distance Classifier (LDC) is a Machine Learning classification algorithm capable of categorizing historical data from a multi-dimensional feature space. This indicator demonstrates how Lorentzian Classification can also be used to predict the direction of future price movements when used as the distance metric for a novel implementation of an Approximate Nearest Neighbors (ANN) algorithm. █ BACKGROUND In physics, Lorentzian space is perhaps best known for its role in describing the curvature of space-time in Einstein's theory of General Relativity (2). Interestingly, however, this abstract concept from theoretical physics also has tangible real-world applications in trading. Recently, it was hypothesized that Lorentzian space was also well-suited for analyzing time-series data (4), (5). This hypothesis has been supported by several empirical studies that demonstrate that Lorentzian distance is more robust to outliers and noise than the more commonly used Euclidean distance (1), (3), (6). Furthermore, Lorentzian distance was also shown to outperform dozens of other highly regarded distance metrics, including Manhattan distance, Bhattacharyya similarity, and Cosine similarity (1), (3). Outside of Dynamic Time Warping based approaches, which are unfortunately too computationally intensive for PineScript at this time, the Lorentzian Distance metric consistently scores the highest mean accuracy over a wide variety of time series data sets (1). Euclidean distance is commonly used as the default distance metric for NN-based search algorithms, but it may not always be the best choice when dealing with financial market data. This is because financial market data can be significantly impacted by proximity to major world events such as FOMC Meetings and Black Swan events. This event-based distortion of market data can be framed as similar to the gravitational warping caused by a massive object on the space-time continuum. For financial markets, the analogous continuum that experiences warping can be referred to as "price-time". Below is a side-by-side comparison of how neighborhoods of similar historical points appear in three-dimensional Euclidean Space and Lorentzian Space: This figure demonstrates how Lorentzian space can better accommodate the warping of price-time since the Lorentzian distance function compresses the Euclidean neighborhood in such a way that the new neighborhood distribution in Lorentzian space tends to cluster around each of the major feature axes in addition to the origin itself. This means that, even though some nearest neighbors will be the same regardless of the distance metric used, Lorentzian space will also allow for the consideration of historical points that would otherwise never be considered with a Euclidean distance metric. Intuitively, the advantage inherent in the Lorentzian distance metric makes sense. For example, it is logical that the price action that occurs in the hours after Chairman Powell finishes delivering a speech would resemble at least some of the previous times when he finished delivering a speech. This may be true regardless of other factors, such as whether or not the market was overbought or oversold at the time or if the macro conditions were more bullish or bearish overall. These historical reference points are extremely valuable for predictive models, yet the Euclidean distance metric would miss these neighbors entirely, often in favor of irrelevant data points from the day before the event. By using Lorentzian distance as a metric, the ML model is instead able to consider the warping of price-time caused by the event and, ultimately, transcend the temporal bias imposed on it by the time series. For more information on the implementation details of the Approximate Nearest Neighbors (ANN) algorithm used in this indicator, please refer to the detailed comments in the source code. █ HOW TO USE Below is an explanatory breakdown of the different parts of this indicator as it appears in the interface: Below is an explanation of the different settings for this indicator: General Settings: Source - This has a default value of "hlc3" and is used to control the input data source. Neighbors Count - This has a default value of 8, a minimum value of 1, a maximum value of 100, and a step of 1. It is used to control the number of neighbors to consider. Max Bars Back - This has a default value of 2000. Feature Count - This has a default value of 5, a minimum value of 2, and a maximum value of 5. It controls the number of features to use for ML predictions. Color Compression - This has a default value of 1, a minimum value of 1, and a maximum value of 10. It is used to control the compression factor for adjusting the intensity of the color scale. Show Exits - This has a default value of false. It controls whether to show the exit threshold on the chart. Use Dynamic Exits - This has a default value of false. It is used to control whether to attempt to let profits ride by dynamically adjusting the exit threshold based on kernel regression. Feature Engineering Settings: Note: The Feature Engineering section is for fine-tuning the features used for ML predictions. The default values are optimized for the 4H to 12H timeframes for most charts, but they should also work reasonably well for other timeframes. By default, the model can support features that accept two parameters (Parameter A and Parameter B, respectively). Even though there are only 4 features provided by default, the same feature with different settings counts as two separate features. If the feature only accepts one parameter, then the second parameter will default to EMA-based smoothing with a default value of 1. These features represent the most effective combination I have encountered in my testing, but additional features may be added as additional options in the future. Feature 1 - This has a default value of "RSI" and options are: "RSI", "WT", "CCI", "ADX". Feature 2 - This has a default value of "WT" and options are: "RSI", "WT", "CCI", "ADX". Feature 3 - This has a default value of "CCI" and options are: "RSI", "WT", "CCI", "ADX". Feature 4 - This has a default value of "ADX" and options are: "RSI", "WT", "CCI", "ADX". Feature 5 - This has a default value of "RSI" and options are: "RSI", "WT", "CCI", "ADX". Filters Settings: Use Volatility Filter - This has a default value of true. It is used to control whether to use the volatility filter. Use Regime Filter - This has a default value of true. It is used to control whether to use the trend detection filter. Use ADX Filter - This has a default value of false. It is used to control whether to use the ADX filter. Regime Threshold - This has a default value of -0.1, a minimum value of -10, a maximum value of 10, and a step of 0.1. It is used to control the Regime Detection filter for detecting Trending/Ranging markets. ADX Threshold - This has a default value of 20, a minimum value of 0, a maximum value of 100, and a step of 1. It is used to control the threshold for detecting Trending/Ranging markets. Kernel Regression Settings: Trade with Kernel - This has a default value of true. It is used to control whether to trade with the kernel. Show Kernel Estimate - This has a default value of true. It is used to control whether to show the kernel estimate. Lookback Window - This has a default value of 8 and a minimum value of 3. It is used to control the number of bars used for the estimation. Recommended range: 3-50 Relative Weighting - This has a default value of 8 and a step size of 0.25. It is used to control the relative weighting of time frames. Recommended range: 0.25-25 Start Regression at Bar - This has a default value of 25. It is used to control the bar index on which to start regression. Recommended range: 0-25 Display Settings: Show Bar Colors - This has a default value of true. It is used to control whether to show the bar colors. Show Bar Prediction Values - This has a default value of true. It controls whether to show the ML model's evaluation of each bar as an integer. Use ATR Offset - This has a default value of false. It controls whether to use the ATR offset instead of the bar prediction offset. Bar Prediction Offset - This has a default value of 0 and a minimum value of 0. It is used to control the offset of the bar predictions as a percentage from the bar high or close. Backtesting Settings: Show Backtest Results - This has a default value of true. It is used to control whether to display the win rate of the given configuration. █ WORKS CITED (1) R. Giusti and G. E. A. P. A. Batista, "An Empirical Comparison of Dissimilarity Measures for Time Series Classification," 2013 Brazilian Conference on Intelligent Systems, Oct. 2013, DOI: 10.1109/bracis.2013.22. (2) Y. Kerimbekov, H. Ş. Bilge, and H. H. Uğurlu, "The use of Lorentzian distance metric in classification problems," Pattern Recognition Letters, vol. 84, 170–176, Dec. 2016, DOI: 10.1016/j.patrec.2016.09.006. (3) A. Bagnall, A. Bostrom, J. Large, and J. Lines, "The Great Time Series Classification Bake Off: An Experimental Evaluation of Recently Proposed Algorithms." ResearchGate, Feb. 04, 2016. (4) H. Ş. Bilge, Yerzhan Kerimbekov, and Hasan Hüseyin Uğurlu, "A new classification method by using Lorentzian distance metric," ResearchGate, Sep. 02, 2015. (5) Y. Kerimbekov and H. Şakir Bilge, "Lorentzian Distance Classifier for Multiple Features," Proceedings of the 6th International Conference on Pattern Recognition Applications and Methods, 2017, DOI: 10.5220/0006197004930501. (6) V. Surya Prasath et al., "Effects of Distance Measure Choice on KNN Classifier Performance - A Review." . █ ACKNOWLEDGEMENTS @veryfid - For many invaluable insights, discussions, and advice that helped to shape this project. @capissimo - For open sourcing his interesting ideas regarding various KNN implementations in PineScript, several of which helped inspire my original undertaking of this project. @RikkiTavi - For many invaluable physics-related conversations and for his helping me develop a mechanism for visualizing various distance algorithms in 3D using JavaScript @jlaurel - For invaluable literature recommendations that helped me to understand the underlying subject matter of this project. @annutara - For help in beta-testing this indicator and for sharing many helpful ideas and insights early on in its development. @jasontaylor7 - For helping to beta-test this indicator and for many helpful conversations that helped to shape my backtesting workflow @meddymarkusvanhala - For helping to beta-test this indicator @dlbnext - For incredibly detailed backtesting testing of this indicator and for sharing numerous ideas on how the user experience could be improved.
Indicatore Pine Script®
di jdehorty
785
Electrocardiogram ChartThis is an attempt to develop alternative visualisation of financial charts. This script also makes use of new pine feature types which represents User Defined Object Types. You can refer to below documentation to understand more about this feature: www.tradingview.com www.tradingview.com 🎲 Structure of new chart components 🎯Instead of candles/bars, this type of chart contains Electrocardiogram blocks which resembles the heartbeat signals on electrocardiogram. Body color of the block is defined by the open and close prices of the bar. If close is greater than open, body is green. Otherwise, the body is painted red. Border color of the block is defined by the close prices of current and previous bar. If the close of current bar is greater than that of last bar, then the border color is green. Otherwise, border color is painted red. 🎯Inside each blocks there will be 5 connecting lines called the signal lines. open-open open-firstPeak(high or low of the bar whichever comes first) firstPeak-secondPeak(high or low of the bar whichever comes last) secondPeak-close close-close 🎯 Color of the signal lines are determined by which among the high/low of the bar comes last. If highest part of the bar reached after reaching the lowest part of the bar, then signal lines are coloured green signifying bullish sentiment towards the end of bar. If lowest part of the bar reached after reaching the highest part of the bar, then signal lines are coloured red signifying bearish sentiment towards the end of bar. Pictorial examples here: 🎲 Limitations with pinescript implementation Since, pinescript can only use maximum 500 lines and each block will take 1 box and 5 lines, it is not possible to display more than 100 bars. Each block of new Electrocardiogram chart will take the space of 7 bars of candlestick chart. Due to this, the alignment of regular OHLC candles is not inline with the new chart type. Background highlighting is done for the part of the OHLC candles where Electrocardiogram blocks are plotted so that it helps users to map the bars manually Thanks to @theheirophant for suggestion of name :)
Indicatore Pine Script®
di Trendoscope
48
PowerX by jwitt98This strategy attempts to replicate the PowerX strategy as described in the book by by Markus Heitkoetter Three indicators are used: RSI (7) - An RSI above 50 indicates and uptrend. An RSI below 50 indicates a downtrend. Slow Stochastics (14, 3, 3) - A %K above 50 indicates an uptrend. A %K below 50 indicates a downtrend. MACD (12, 26, 9) - A MACD above the signal line indicates an uptrend. A MACD below the signal line indicates a downtrend In addition, multiples of ADR (7) is used for setting the stops and profit targets Setup: When all 3 indicators are indicating an uptrend, the OHLC bar is green. When all 3 indicators are indicating a downtrend, the OHLC bar is red. When one or more indicators are conflicting, the OHLC bar is black The basic rules are: When the OHLC bar is green and the preceding bar is black or Red, enter a long stop-limit order .01 above the high of the first green bar When the OHLC bar is red and the preceding bar is black or green, enter a short stop-limit order .01 below the low of the first red bar If a red or black bar is encountered while in a long trade, or a green or black bar for a short trade, exit the trade at the close of that bar with a market order. Stop losses are set by default at a multiple of 1.5 times the ADR. Profit targets are set by default at a multiple of 3 times the ADR. Options: You can adjust the start and end dates for the trading range You can configure this strategy for long only, short only, or both long and short. You can adjust the multiples used to set the stop losses and profit targets. There is an option to use a money management system very similar to the one described in the PowerX book. Some assumptions had to be made for cases where the equity is underwater as those cases are not clearly defined in the book. There is an option to override this behavior and keep the risk at or above the set point (2% by default), rather than further reduce the risk when equity is underwater. Position sizing is limited when using money management so as not to exceed the current strategy equity. The starting risk can be adjusted from the default of 2%. Final notes: If you find any errors, have any questions, or have suggestions for improvements, please leave your message in the comments. Happy trading!
Strategia Pine Script®
di jwitt98
4
Rollover LTEThis indicator shows where price needs to be and when in order to cause the 20-sma and 50-sma moving averages to change directions. A change in direction requires the slope of a moving average to change from negative to positive or from positive to negative. When a moving average changes direction, it can be said that it has “rolled over” or “rolled up,” with the latter only applying if slope went from negative to positive. Theory: In order to solve for the price of the current bar that will cause the moving average to roll up, the slope from the previous bar’s average to the current bar’s average must be set equal to zero which is to say that the averages must be the same. For the 20-sma, the equation simply stated in words is as follows: Current MA as a function of current price and previous 19 values = previous MA which is fixed based on previous 20 values The denominators which are both 20 cancel and the previous 19 values cancel. What’s left is current price on the left side and the value from 20 bars ago on the right. Current price = value from 20 bars ago and since the equation was set up for solving for the price of the current bar that will cause the MA to roll over Rollover price = value from 20 bars ago This makes plotting rollover price, both current and forecasted, fairly simple, as it’s merely the closing price plotted with an offset to the right the same distance as the moving average length. Application: The 20-sma and 50-sma rollover prices are plotted because they are considered to be the two most important moving averages for rollover analysis. Moving average lengths can be modified in the indicator settings. The 20-sma and 20-sma rollover price are both plotted in white and the 50-sma and 50-sma rollover price are both plotted in blue. There are two rollover prices because the 20-sma rollover price is the price that will cause the 20-sma to roll over and the 50-sma rollover price is the price that will cause the 50-sma to roll over. The one that's vertically furthest away from the current price is the one that will cause both to rollover, as should become clearer upon reading the explanation below. The distance between the current price and the 20-sma rollover price is referred to as the “rollover strength” of the price relative to the 20-sma. A large disparity between the current price and the rollover price suggests bearishness (negative rollover strength) if the rollover price is overhead because price would need to travel all that distance in order to cause the moving average to roll up. If the rollover price and price are converging, as is often the case, a change in moving average and price direction becomes more plausible. The rollover strengths of the 20-sma and 50-sma are added together to calculate the Rollover Strength and if a negative number is the result then the background color of the plot cloud turns red. If the result is positive, it turns green. Rollover Strength is plotted below price as a separate indicator in this publication for reference only and it's not part of this indicator. It does not look much different from momentum indicators. The code is below if anybody wants to try to use it. The important thing is that the distances between the rollover prices and the price action are kept in mind as having shrinking, growing, or neutral bearish and bullish effects on current and forecasted price direction. Trades should not be entered based on cloud colorization changes alone. If you are about to crash into a wall of the 20-sma rollover price, as is indicated on the chart by the green arrow, you might consider going long so long as the rollover strength, both current and forecasted, of the 50-sma isn’t questionably bearish. This is subject to analysis and interpretation. There was a 20-sma rollover wall as indicated with yellow arrow, but the bearish rollover strength of the 50-sma was growing and forecasted to remain strong for a while at that time so a long entry would have not been suggested by both rollover prices. If you are about to crash into both the 20-sma and 50-sma rollover prices at the same time (not shown on this chart), that’s a good time to place a trade in anticipation of both slopes changing direction. You may, in the case of this chart, see that a 20-sma rollover wall precedes a 50-sma rollover convergence with price and anticipate a cascade which turned out to be the case with this recent NQ rally. Price exiting the cloud entirely to either the upside or downside has strong implications. When exiting to the downside, the 20-sma and 50-sma have both rolled over and price is below both of them. The same is true for upside exits. Re-entering the cloud after a rally may indicate a reversal is near, especially if the forecasted rollover prices, particularly the 50-sma, agree. This indicator should be used in conjunction with other technical analysis tools. Additional Notes: The original version of this script which will not be published was much heavier, cluttered, and is not as useful. This is the light version, hence the “LTE” suffix. LTE stands for “long-term evolution” in telecommunications, not “light.” Bar colorization (red, yellow, and green bars) was added using the MACD Hybrid BSH script which is another script I’ve published. If you’re not sure what a bar is, it’s the same thing as a candle or a data point on a line chart. Every vertical line showing price action on the chart above is a bar and it is a bar chart. sma = simple moving average Rollover Strength Script: // This source code is subject to the terms of the Mozilla Public License 2.0 at mozilla.org // © Skipper86 //@version=5 indicator(title="Rollover Strength", shorttitle="Rollover Strength", overlay=false) source = input.source(close) length1 = input.int(20, "Length 1", minval=1) length2 = input.int(50, "Length 2", minval=1) RolloverPrice1 = source RolloverPrice2 = source RolloverStrength1 = source-RolloverPrice1 RolloverStrength2 = source-RolloverPrice2 RolloverStrength = RolloverStrength1 + RolloverStrength2 Color1 = color.rgb(155, 155, 155, 0) Color2 = color.rgb(0, 0, 200, 0) Color3 = color.rgb(0, 200, 0, 0) plot(RolloverStrength, title="Rollover Strength", color=Color3) hline(0, "Middle Band", color=Color1) //End of Rollover Strength Script
Indicatore Pine Script®
di Skipper86
EMA bands + leledc + bollinger bands trend following strategy v2The basics: In its simplest form, this strategy is a positional trend following strategy which enters long when price breaks out above "middle" EMA bands and closes or flips short when price breaks down below "middle" EMA bands. The top and bottom of the middle EMA bands are calculated from the EMA of candle highs and lows, respectively. The idea is that entering trades on breakouts of the high EMAs and low EMAs rather than the typical EMA based on candle closes gives a bit more confirmation of trend strength and minimizes getting chopped up. To further reduce getting chopped up, the strategy defaults to close on crossing the opposite EMA band (ie. long on break above high EMA middle band and close below low EMA middle band). This strategy works on all markets on all timeframes, but as a trend following strategy it works best on markets prone to trending such as crypto and tech stocks. On lower timeframes, longer EMAs tend to work best (I've found good results on EMA lengths even has high up to 1000), while 4H charts and above tend to work better with EMA lengths 21 and below. As an added filter to confirm the trend, a second EMA can be used. Inputting a slower EMA filter can ensure trades are entered in accordance with longer term trends, inputting a faster EMA filter can act as confirmation of breakout strength. Bar coloring can be enabled to quickly visually identify a trend's direction for confluence with other indicators or strategies. The goods: Waiting for the trend to flip before closing a trade (especially when a longer base EMA is used) often leaves money on the table. This script combines a number of ways to identify when a trend is exhausted for backtesting the best early exits. "Delayed bars inside middle bands" - When a number of candle's in a row open and close between the middle EMA bands, it could be a sign the trend is weak, or that the breakout was not the start of a new trend. Selecting this will close out positions after a number of bars has passed "Leledc bars" - Originally introduced by glaz, this is a price action indicator that highlights a candle after a number of bars in a row close the same direction and result in greatest high/low over a period. It often triggers when a strong trend has paused before further continuation, or it marks the end of a trend. To mitigate closing on false Leledc signals, this strategy has two options: 1. Introducing requirement for increased volume on the Leledc bars can help filter out Leledc signals that happen mid trend. 2. Closing after a number of Leledc bars appear after position opens. These two options work great in isolation but don't perform well together in my testing. "Bollinger Bands exhaustion bars" - These bars are highlighted when price closes back inside the Bollinger Bands and RSI is within specified overbought/sold zones. The idea is that a trend is overextended when price trades beyond the Bollinger Bands. When price closes back inside the bands it's likely due for mean reversion back to the base EMA in which this strategy will ideally re-enter a position. Since the added RSI requirements often make this indicator too strict to trigger a large enough sample size to backtest, I've found it best to use "non-standard" settings for both the bands and the RSI as seen in the default settings. "Buy/Sell zones" - Similar to the idea behind using Bollinger Bands exhaustion bars as a closing signal. Instead of calculating off of standard deviations, the Buy/Sell zones are calculated off multiples of the middle EMA bands. When trading beyond these zones and subsequently failing back inside, price may be due for mean reversion back to the base EMA. No RSI filter is used for Buy/Sell zones. If any early close conditions are selected, it's often worth enabling trade re-entry on "middle EMA band bounce". Instead of waiting for a candle to close back inside the middle EMA bands, this feature will re-enter position on only a wick back into the middle bands as will sometimes happen when the trend is strong. Any and all of the early close conditions can be combined. Experimenting with these, I've found can result in less net profit but higher win-rates and sharpe ratios as less time is spent in trades. The deadly: The trend is your friend. But wouldn't it be nice to catch the trends early? In ranging markets (or when using slower base EMAs in this strategy), waiting for confirmation of a breakout of the EMA bands at best will cause you to miss half the move, at worst will result in getting consistently chopped up. Enabling "counter-trend" trades on this strategy will allow the strategy to enter positions on the opposite side of the EMA bands on either a Leledc bar or Bollinger Bands exhaustion bar. There is a filter requiring either a high/low (for Leledc) or open (for BB bars) outside the selected inner or outer Buy/Sell zone. There are also a number of different close conditions for the counter-trend trades to experiment with and backtest. There are two ways I've found best to use counter-trend trades 1. Mean reverting scalp trades when a trend is clearly overextended. Selecting from the first 5 counter-trend closing conditions on the dropdown list will usually close the trades out quickly, with less profit but less risk. 2. Trying to catch trends early. Selecting any of the close conditions below the first 5 can cause the strategy to behave as if it's entering into a new trend (from the wrong side). This feature can be deadly effective in profiting from every move price makes, or deadly to the strategy's PnL if not set correctly. Since counter-trend trades open opposite the middle bands, a stop-loss is recommended to reduce risk. If stop-losses for counter-trend trades are disabled, the strategy will hold a position open often until liquidation in a trending market if th trade is offsides. Note that using a slower base EMA makes counter-trend stop-losses even more necessary as it can reduce the effectiveness of the Buy/Sell zone filter for opening the trades as price can spend a long time trending outside the zones. If faster EMAs (34 and below) are used with "Inner" Buy/Zone filter selected, the first few closing conditions will often trigger almost immediately closing the trade at a loss. The niche: I've added a feature to default into longs or shorts. Enabling these with other features (aside from the basic long/short on EMA middle band breakout) tends to break the strategy one way or another. Enabling default long works to simulate trying to acquire more of the asset rather than the base currency. Enabling default short can have positive results for those high FDV, high inflation coins that go down-only for months at a time. Otherwise, I use default short as a hedge for coins that I hold and stake spot. I gain the utility and APR of staking while reducing the risk of holding the underlying asset by maintaining a net neutral position *most* of the time. Disclaimer: This script is intended for experimenting and backtesting different strategies around EMA bands. Use this script for your live trading at your own risk. I am a rookie coder, as such there may be errors in the code that cause the strategy to behave not as intended. As far as I can tell it doesn't repaint, but I cannot guarantee that it does not. That being said if there's any question, improvements, or errors you've found, drop a comment below!
Strategia Pine Script®
di readysetliqd
5
Relative Strength Index (OSC)Hello everyone, I'm sorry that the previous open-source version was hidden due to the house rules, I've re-edited the description and re-posted it (1) Indicator introduction This is RSI indicator with original divergence algorithm This indicator is plotted on the RSI and can display the divergence locations and corresponding divergence intensity The tolerance of N Klines at the top or bottom positions for price and indicator is supported, which is set by the "Tolerant Kline Number" Support the display of divergence intensity, that is, the REG/HID value displayed on the label, which is less than 0. The smaller the intensity value, the more obvious divergence Support the filtering of divergence intensity, which is set by "Cov Threshold". The divergence that REG/HID divergence intensity greater than this value will be ignored In the label, REG indicates regular top/bottom divergence while HID indicates hidden top/bottom divergence In the label, SRC(x-y) indicates a divergence occurred from the x-th kline to the y-th kline In the label, OSC(x-y) indicates a divergence occurred from the indicator corresponding to the x-th kline to the y-th kline (2) Parameter introduction - RSI Settings Source: The source to calculate RSI, close by default RSI Length: The length of RSI, 14 by default - RSI Divergence Pivot Lookback Right: Number of K-line bars recalling the pivot top/bottom point to the right Pivot Lookback Left: Number of K-line bars recalling the pivot top/bottom point to the left Max of Lookback Range: Maximum number of retracing K-line bars to find the pivot top/bottom point Min of Lookback Range: Minimum number of retracing K-line bars to find the pivot top/bottom point Tolerant Kline Number: Maximum tolerance in indexing top/bottom points of Klines and indicators Cov Threshold: Divergence intensity, which is less than 0. The smaller the intensity value, the more obvious divergence Plot Bullish: Whether to draw regular bullish divergence label Plot Hidden Bullish: Whether to draw hidden bullish divergence label Plot Bearish: Whether to draw regular bearish divergence label Plot Hidden Bearish: Whether to draw hidden bearish divergence label Happy trading and enjoy your life! ———————————————————————————————————————— 各位朋友大家好，很抱歉之前的开源版本因为规则原因被隐藏，我已经重新编辑了说明并重新发布 (1) 指标说明 该指标绘制于 RSI 上，并在对应位置显示背离点以及背离程度 支持顶底位置 N 根K线的容差，由 Tolerant Kline Number 参数设置 支持背离强度的显示，即标签上显示的 REG/HID 值，该值小于 0，且越小说明背离程度越大 支持背离强度的过滤，由 Cov Threshold 参数设置， REG/HID 值大于这个值的背离会被忽略 标签中，REG 表示常规顶/低背离，而 HID 表示隐藏顶/底背离 标签中，SRC(x-y) 表示从当前第 x 根 bar 开始到第 y 跟 bar 出现背离 标签中，OSC(x-y) 表示从当前第 x 根 bar 所对应的指标开始到第 y 跟 bar 所对应的指标出现背离 (2) 参数说明 - RSI Settings Source: 计算 RSI 指标的 source，默认为 close RSI Length: 计算 RSI 指标的长度，默认为 14 - RSI Divergence Pivot Lookback Right: 枢纽顶/底点往右回顾的 K线 bar 数量 Pivot Lookback Left: 枢纽顶/底点往左回顾的 K线 bar 数量 Max of Lookback Range: 回寻找枢纽顶/底点的最大回溯 K线 bar 数量 Min of Lookback Range: 回寻找枢纽顶/底点的最小回溯 K线 bar 数量 Tolerant Kline Number: K线和指标的顶/底点索引的最大误差 Cov Threshold: 背离程度，该值小于 0，且越小说明背离程度越大 Plot Bullish: 是否绘制常规底背离提示 Plot Hidden Bullish: 是否绘制隐藏底背离提示 Plot Bearish: 是否绘制常规顶背离提示 Plot Hidden Bearish: 是否绘制隐藏顶背离提示 祝大家交易愉快
Indicatore Pine Script®
di dandrideng
1
Relative Strength Index (SRC)Hello everyone, I'm sorry that the previous open-source version was hidden due to the house rules, I've re-edited the description and re-posted it (1) Indicator introduction This is RSI indicator with original divergence algorithm This indicator is plotted on the klines and can display the divergence locations and corresponding divergence intensity The tolerance of N Klines at the top or bottom positions for price and indicator is supported, which is set by the "Tolerant Kline Number" Support the display of divergence intensity, that is, the REG/HID value displayed on the label, which is less than 0. The smaller the intensity value, the more obvious divergence Support the filtering of divergence intensity, which is set by "Cov Threshold". The divergence that REG/HID divergence intensity greater than this value will be ignored In the label, REG indicates regular top/bottom divergence while HID indicates hidden top/bottom divergence In the label, SRC(x-y) indicates a divergence occurred from the x-th kline to the y-th kline In the label, OSC(x-y) indicates a divergence occurred from the indicator corresponding to the x-th kline to the y-th kline (2) Parameter introduction - RSI Settings Source: The source to calculate RSI, close by default RSI Length: The length of RSI, 14 by default - RSI Divergence Pivot Lookback Right: Number of K-line bars recalling the pivot top/bottom point to the right Pivot Lookback Left: Number of K-line bars recalling the pivot top/bottom point to the left Max of Lookback Range: Maximum number of retracing K-line bars to find the pivot top/bottom point Min of Lookback Range: Minimum number of retracing K-line bars to find the pivot top/bottom point Tolerant Kline Number: Maximum tolerance in indexing top/bottom points of Klines and indicators Cov Threshold: Divergence intensity, which is less than 0. The smaller the intensity value, the more obvious divergence Plot Bullish: Whether to draw regular bullish divergence label Plot Hidden Bullish: Whether to draw hidden bullish divergence label Plot Bearish: Whether to draw regular bearish divergence label Plot Hidden Bearish: Whether to draw hidden bearish divergence label Happy trading and enjoy your life! ———————————————————————————————————————— 各位朋友大家好，很抱歉之前的开源版本因为规则原因被隐藏，我已经重新编辑了说明并重新发布 (1) 指标说明 该指标绘制于 K线 上，并在对应位置显示背离点以及背离程度 支持顶底位置 N 根K线的容差，由 Tolerant Kline Number 参数设置 支持背离强度的显示，即标签上显示的 REG/HID 值，该值小于 0，且越小说明背离程度越大 支持背离强度的过滤，由 Cov Threshold 参数设置， REG/HID 值大于这个值的背离会被忽略 标签中，REG 表示常规顶/低背离，而 HID 表示隐藏顶/底背离 标签中，SRC(x-y) 表示从当前第 x 根 bar 开始到第 y 跟 bar 出现背离 标签中，OSC(x-y) 表示从当前第 x 根 bar 所对应的指标开始到第 y 跟 bar 所对应的指标出现背离 (2) 参数说明 - RSI Settings Source: 计算 RSI 指标的 source，默认为 close RSI Length: 计算 RSI 指标的长度，默认为 14 - RSI Divergence Pivot Lookback Right: 枢纽顶/底点往右回顾的 K线 bar 数量 Pivot Lookback Left: 枢纽顶/底点往左回顾的 K线 bar 数量 Max of Lookback Range: 回寻找枢纽顶/底点的最大回溯 K线 bar 数量 Min of Lookback Range: 回寻找枢纽顶/底点的最小回溯 K线 bar 数量 Tolerant Kline Number: K线和指标的顶/底点索引的最大误差 Cov Threshold: 背离程度，该值小于 0，且越小说明背离程度越大 Plot Bullish: 是否绘制常规底背离提示 Plot Hidden Bullish: 是否绘制隐藏底背离提示 Plot Bearish: 是否绘制常规顶背离提示 Plot Hidden Bearish: 是否绘制隐藏顶背离提示 祝大家交易愉快
Indicatore Pine Script®
di dandrideng
3
On Balance Volume wi Normalization (OSC)Hello everyone, I'm sorry that the previous open-source version was hidden due to the house rules, I've re-edited the description and re-posted it (1) Indicator introduction This indicator is a normalized OBV that never dulls and has a better divergence accuracy than RSI This indicator is plotted on the Normalized OBV and can display the divergence locations and corresponding divergence intensity The tolerance of N Klines at the top or bottom positions for price and indicator is supported, which is set by the "Tolerant Kline Number" Support the display of divergence intensity, that is, the REG/HID value displayed on the label, which is less than 0. The smaller the intensity value, the more obvious divergence Support the filtering of divergence intensity, which is set by "Cov Threshold". The divergence that REG/HID divergence intensity greater than this value will be ignored In the label, REG indicates regular top/bottom divergence while HID indicates hidden top/bottom divergence In the label, SRC(x-y) indicates a divergence occurred from the x-th kline to the y-th kline In the label, OSC(x-y) indicates a divergence occurred from the indicator corresponding to the x-th kline to the y-th kline (2) Parameter introduction - Normalized On Balance Volume MA Type: Type of moving average for calculating the normalized OBV, default is SMA MA Period: Period of moving average of normalized OBV, which is SMA14 by default NOBV Sigma: Upper and lower range of normalized OBV - Normalized On Balance Volume Divergence Pivot Lookback Right: Number of K-line bars recalling the pivot top/bottom point to the right Pivot Lookback Left: Number of K-line bars recalling the pivot top/bottom point to the left Max of Lookback Range: Maximum number of retracing K-line bars to find the pivot top/bottom point Min of Lookback Range: Minimum number of retracing K-line bars to find the pivot top/bottom point Tolerant Kline Number: Maximum tolerance in indexing top/bottom points of Klines and indicators Cov Threshold: Divergence intensity, which is less than 0. The smaller the intensity value, the more obvious divergence Plot Bullish: Whether to draw regular bullish divergence label Plot Hidden Bullish: Whether to draw hidden bullish divergence label Plot Bearish: Whether to draw regular bearish divergence label Plot Hidden Bearish: Whether to draw hidden bearish divergence label Happy trading and enjoy your life! ———————————————————————————————————————— 各位朋友大家好，很抱歉之前的开源版本因为规则原因被隐藏，我已经重新编辑了说明并重新发布 (1) 指标说明 该指标是 OBV 的归一化版本，永不钝化，背离准确率高于 RSI 该指标绘制于 归一化OBV 上，并在对应位置显示背离点以及背离程度 支持顶底位置 N 根K线的容差，由 Tolerant Kline Number 参数设置 支持背离强度的显示，即标签上显示的 REG/HID 值，该值小于 0，且越小说明背离程度越大 支持背离强度的过滤，由 Cov Threshold 参数设置， REG/HID 值大于这个值的背离会被忽略 标签中，REG 表示常规顶/低背离，而 HID 表示隐藏顶/底背离 标签中，SRC(x-y) 表示从当前第 x 根 bar 开始到第 y 跟 bar 出现背离 标签中，OSC(x-y) 表示从当前第 x 根 bar 所对应的指标开始到第 y 跟 bar 所对应的指标出现背离 (2) 参数说明 - Normalized On Balance Volume MA Type: 计算归一化 OBV 的移动平均的类型，默认为 SMA MA Period: 计算归一化 OBV 的移动平均的周期，默认为 SMA14 NOBV Sigma: 归一化 OBV 的过滤区间 - Normalized On Balance Volume Divergence Pivot Lookback Right: 枢纽顶/底点往右回顾的 K线 bar 数量 Pivot Lookback Left: 枢纽顶/底点往左回顾的 K线 bar 数量 Max of Lookback Range: 回寻找枢纽顶/底点的最大回溯 K线 bar 数量 Min of Lookback Range: 回寻找枢纽顶/底点的最小回溯 K线 bar 数量 Tolerant Kline Number: K线和指标的顶/底点索引的最大误差 Cov Threshold: 背离程度，该值小于 0，且越小说明背离程度越大 Plot Bullish: 是否绘制常规底背离提示 Plot Hidden Bullish: 是否绘制隐藏底背离提示 Plot Bearish: 是否绘制常规顶背离提示 Plot Hidden Bearish: 是否绘制隐藏顶背离提示 祝大家交易愉快
Indicatore Pine Script®
di dandrideng
2
On Balance Volume wi Normalization (SRC)Hello everyone, I'm sorry that the previous open-source version was hidden due to the house rules, I've re-edited the description and re-posted it (1) Indicator introduction This indicator is a normalized OBV that never dulls and has a better divergence accuracy than RSI This indicator is plotted on the klines and can display the divergence locations and corresponding divergence intensity The tolerance of N Klines at the top or bottom positions for price and indicator is supported, which is set by the "Tolerant Kline Number" Support the display of divergence intensity, that is, the REG/HID value displayed on the label, which is less than 0. The smaller the intensity value, the more obvious divergence Support the filtering of divergence intensity, which is set by "Cov Threshold". The divergence that REG/HID divergence intensity greater than this value will be ignored In the label, REG indicates regular top/bottom divergence while HID indicates hidden top/bottom divergence In the label, SRC(x-y) indicates a divergence occurred from the x-th kline to the y-th kline In the label, OSC(x-y) indicates a divergence occurred from the indicator corresponding to the x-th kline to the y-th kline (2) Parameter introduction - Normalized On Balance Volume MA Type: Type of moving average for calculating the normalized OBV, default is SMA MA Period: Period of moving average of normalized OBV, which is SMA14 by default NOBV Sigma: Upper and lower range of normalized OBV, but the function is reserved - Normalized On Balance Volume Divergence Pivot Lookback Right: Number of K-line bars recalling the pivot top/bottom point to the right Pivot Lookback Left: Number of K-line bars recalling the pivot top/bottom point to the left Max of Lookback Range: Maximum number of retracing K-line bars to find the pivot top/bottom point Min of Lookback Range: Minimum number of retracing K-line bars to find the pivot top/bottom point Tolerant Kline Number: Maximum tolerance in indexing top/bottom points of Klines and indicators Cov Threshold: Divergence intensity, which is less than 0. The smaller the intensity value, the more obvious divergence Plot Bullish: Whether to draw regular bullish divergence label Plot Hidden Bullish: Whether to draw hidden bullish divergence label Plot Bearish: Whether to draw regular bearish divergence label Plot Hidden Bearish: Whether to draw hidden bearish divergence label Happy trading and enjoy your life! ———————————————————————————————————————— 各位朋友大家好，很抱歉之前的开源版本因为规则原因被隐藏，我已经重新编辑了说明并重新发布 (1) 指标说明 该指标是 OBV 的归一化版本，永不钝化，背离准确率高于 RSI 该指标绘制于 K线 上，并在对应位置显示背离点以及背离程度 支持顶底位置 N 根K线的容差，由 Tolerant Kline Number 参数设置 支持背离强度的显示，即标签上显示的 REG/HID 值，该值小于 0，且越小说明背离程度越大 支持背离强度的过滤，由 Cov Threshold 参数设置， REG/HID 值大于这个值的背离会被忽略 标签中，REG 表示常规顶/低背离，而 HID 表示隐藏顶/底背离 标签中，SRC(x-y) 表示从当前第 x 根 bar 开始到第 y 跟 bar 出现背离 标签中，OSC(x-y) 表示从当前第 x 根 bar 所对应的指标开始到第 y 跟 bar 所对应的指标出现背离 (2) 参数说明 - Normalized On Balance Volume MA Type: 计算归一化 OBV 的移动平均的类型，默认为 SMA MA Period: 计算归一化 OBV 的移动平均的周期，默认为 SMA14 NOBV Sigma: 归一化 OBV 的过滤区间，其功能暂时保留 - Normalized On Balance Volume Divergence Pivot Lookback Right: 枢纽顶/底点往右回顾的 K线 bar 数量 Pivot Lookback Left: 枢纽顶/底点往左回顾的 K线 bar 数量 Max of Lookback Range: 回寻找枢纽顶/底点的最大回溯 K线 bar 数量 Min of Lookback Range: 回寻找枢纽顶/底点的最小回溯 K线 bar 数量 Tolerant Kline Number: K线和指标的顶/底点索引的最大误差 Cov Threshold: 背离程度，该值小于 0，且越小说明背离程度越大 Plot Bullish: 是否绘制常规底背离提示 Plot Hidden Bullish: 是否绘制隐藏底背离提示 Plot Bearish: 是否绘制常规顶背离提示 Plot Hidden Bearish: 是否绘制隐藏顶背离提示 祝大家交易愉快
Indicatore Pine Script®
di dandrideng
3
show bottomscript name: show bottom For left traders, how to accurately find the bottom is very important, and there are various methods, among which the bottom type is a common and convenient method. This script shows where the bottom is formed and when the bottom is broken. Although the definition of the bottom type is very simple: after processing the inclusion relationship, in three consecutive bars, the low point of the middle bar is the lowest point of the three bar low points, and the high point of the middle bar is the highest point of the three bar high points. However, because the containment relationship can be complex, so this script enumerates the common containment relationships, so it is more verbose. Also, in order to rule out a false break, the script thinks that the alarm will only be issued when the close price falls below the bottom. Finally, this script supports webhook, that is, when the bottom is broken, the alert content conforms to json format. At the same time, this script also supports sending the opening price, closing price, high point and low point of each bar in the form of json, which is a method of subscribing to real-time stock prices. Introduction in Chinese: 脚本名称：显示底分型 对于左侧交易者来说，如何准确地找到底部是非常重要的，方法也是多样的，其中底分型是一种常用的简便方法。 这个脚本可以显示底分型的位置，以及底部什么时候被跌破。 虽然底分型的定义很简单：处理包含关系后，连续三个bar中，中间bar的低点是三个bar低点中的最低点，且中间bar的高点是三个bar高点中的最高点，但是，因为包含关系可能比较复杂，所以这个脚本列举了常见的各种包含关系，也因此显得比较冗长。 另外，为排除假跌破，这个脚本认为只有当收盘价跌破底部时，才会报警。 最后，这个脚本支持webhook，也就是说，底部被跌破时，警报内容符合json格式。同时，这个脚本还支持将每个bar的开盘价、收盘价、高点和低点以json形式发送出来，这算是一种订阅实时股价的方法。
Indicatore Pine Script®
di slmgtv1
5
LineGetPriceOnLogScaleLibrary "LineGetPriceOnLogScale" This library provides a way to calculate the y-coordinate of a line on a specified bar when the chart scale is Log. The built-in `line.get_price()` function only works with linear scale and gives incorrect results when the chart is in Log scale. The library only works with `bar_index` values and `xloc.bar_index`-based lines, `time`-based lines will cause errors to appear. coordGetPriceLog(x1, y1, x2, y2, xi) Calculates the y-coordinate on the specified bar on the logarithmic scale. Only coordinates based on bar index are applicable, bar time will throw an error. Parameters: x1 : First X coordinate of a line, index of the bar where the line starts. y1 : First Y coordinate of a line, price on the price scale. x2 : Second X coordinate of a line, index of the bar where the line ends. y2 : Second Y coordinate of a line, price on the price scale. xi : Index of the bar for which the price should be calculated. Returns: Price of the line on the bar specified in `xi`, on the logarithmic scale. lineGetPriceLog(_line, xi) Calculates the y-coordinate on the specified bar for the logarithmic scale. Takes a line. Only lines drawn based on `xloc.bar_index` are applicable, `xloc.bar_time` will throw and error. Parameters: _line : The line for which the price is calculated. xi : Index of the bar for which the bar should calculate the price. Returns: Price of the line on the bar specified in `xi`, on the logarithmic scale.
Libreria Pine Script®
di BeeHolder
2
[CP]Pivot Boss Candlestick Scanner - No Repainting This indicator is based on the high probability candlestick patterns described in the ’Secrets of a Pivot Boss’ book. The indicator does not suffer from repainting. I have kept this indicator open source, so that you can take this indicator and design a complete trading system around it. Although the patterns have some statistical edge in the markets, blindly using them as Buy/Sell Indicators will certainly result in a heavy loss. I like some of these setups more than others, and I have listed them in the order of my likeness. The first one I like the most, the last one, I like the least. The patterns are universal and work well in both intraday, daily and even larger timeframes. Signals in the example charts are manually marked by, Hammer - profitable short signal Rocket - profitable long signal X - unprofitable long or short signal GENERAL USER INPUTS: These settings exist as the indicator uses ‘Labels’ to mark the patterns and Pine Script limits a maximum of 500 labels on a chart. If you want to go back in the past and check how the indicator was doing, set the Start and End dates both and check the ’Use the date range above to mark the Candlestick Setups?’ option. EXTREME REVERSAL SETUP: This is by far my favorite setup in the lot. Classic Mean Reversion setup. The logic, as explained in the book, goes like this, 1. The first bar of the pattern is about two times larger than the average size of the candles in the lookback period. 2. The body of the first bar of the pattern should encompass more than 50 percent of the bar’s total range, but usually not more than 85 percent. 3. The second bar of the pattern opposes the first. The setup works extremely well in high beta stocks like Vedanta VEDL. Feel free to play with the settings in order to better align this pattern with your favorite stock. Check out the examples below, No indicator is perfect, failed patterns are marked with an X. OUTSIDE REVERSAL SETUP: My second favorite setup, it is quite good at catching intraday trends. Here’s the logic, 1. The engulfing bar of a bullish outside reversal setup has a low that is below the prior bar’s low and a close that is above the prior bar’s high. Reverse the conditions for bearish outside reversal. 2. The engulfing bar is usually 5 to 25 percent larger than the size of the average bar in the lookback period. Settings for this pattern simply reflect these conditions. Feel free to modify them as you wish. The pattern is pretty powerful and will sometimes help you catch literally all the highs and lows of the market, as shown in the examples of Vedanta VEDL and RELIANCE stocks below. As usual, this pattern is not PERFECT either. DOJI REVERSAL SETUP: Doji candles signify market indecision and this pattern tries to profit off these market conditions. Logic: 1. The open and close price of the doji should fall within 10 percent of each other, as measured by the total range of the candlestick. 2. For a bullish doji, the high of the doji candlestick should be below the ten-period simple moving average. Vice-versa for bearish. 3. For a bullish doji setup, one of the two bars following the doji must close above the high of the doji. Vice-versa for bearish. Feel free to modify the settings and optimize according to the stock you are trading. Don't optimize too much :) This pattern works brilliantly well on larger intraday timeframes, like 15m/30m/60m. This pattern also has a higher propensity to give false indications than the two described above. Doji reversal typically helps to catch larger trend reversals. Check out the examples below from RELIANCE and NIFTY charts, Note that the RELIANCE chart below is the same as shown for the Outside Reversal Setup above, notice the confluence of Outside Reversal and Doji Reversal on the 31st August. Confluence of patterns usually increases the probability of success. RELIANCE 15m Chart - Pattern can catch nice trends on higher timeframes NIFTY 15m Chart WICK REVERSAL SETUP: This pattern tries to capture candlesticks with large wick sizes, as they often indicate trend reversal when coupled with significant support and resistance levels. Logic: 1. The body is used to determine the size of the reversal wick. A wick that is between 2.5 to 3.5 times larger than the size of the body is ideal. 2. For a bullish reversal wick to exist, the close of the bar should fall within the top 35 percent of the overall range of the candle. 3. For a bearish reversal wick to exist, the close of the bar should fall within the bottom 35 percent of the overall range of the candle. This pattern must always be coupled with important support resistance levels, else there will be a lot of false signals. The chart below is the same NIFTY chart as above with the Wick Reversal candles marked as well. You can see that there are a lot of false signals, but the price also indicates ’pausing’ at important levels by printing a wick reversal setup. You can use this information to your advantage when riding a trend. FINAL WORDS: Settings for various patterns simply reflect the logic described. You will probably need to tweak and optimize the pattern settings for the stock that you are trading. Higher Beta/Higher Volatility stocks are a great choice for these patterns. Using these patterns at critical support and resistance levels will result in dramatically high accuracy. Be creative and try to develop a proper system around this indicator, with rules for position sizing, stop loss etc. You do not have to trade all the patterns. Even trading just one pattern with a proper system is good enough. DO NOT USE THIS INDICATOR AS A BUY/SELL SYSTEM, YOU WILL LOSE MONEY. Feel free to drop any feedback in the comments section below, or if you have any unique candlestick patterns that you would like me to code.
Indicatore Pine Script®
di pranjalchaubey
28
Cyclic Smoothed RSI with Motive-Corrective Wave Indicator This indicator uses the cyclic smoothed Relative Strength Index (cRSI) instead of the traditional Relative Strength Index (RSI). See below for more info on the benefits to the cRSI. My key contributions 1) A Weighted Moving Average (WMA) to track the general trend of the cRSI signal. This is very helpful in determining when the equity switches from bullish to bearish, which can be used to determine buy/sell points. This is then is used to color the region between the upper and lower cRSI bands (green above, red below). 2) An attempt to detect the motive (impulse) and corrective and waves. Corrective waves are indicated A, B, C, D, E, F, G. F and G waves are not technically Elliot Waves, but the way I detect waves it is really hard to always get it right. Once and a while you could actually see G and F a second time. Motive waves are identified as s (strong) and w (weak). Strong waves have a peak above the cRSI upper band and weak waves have a peak below the upper band. 3) My own divergence indicator for bull, hidden bull, bear, and hidden bear. I was not able to replicate the TradingView style of drawing a line from peak to peak, but for this indicator I think in the end it makes the chart cleaner. There is a latency issue with an indicator that is based on moving averages. That means they tend to trigger right after key events. Perfect timing is not possible strictly with these indicators, but they do work very well "on average." However, my implementation has minimal latency as peaks (tops/bottoms) only require one bar to detect. As a bit of an Easter Egg, this code can be tweaked and run as a strategy to get buy/sell signals. I use this code for both my indicator and for trading strategy. Just copy and past it into a new strategy script and just change it from study to a strategy, something like this: strategy("cRSI + Waves Strategy with VWMA overlay", overlay=overlay) The buy/sell code is at the end and just needs to be uncommented. I make no promises or guarantees about how good it is as a strategy, but it gives you some code and ideas to work with. Tuning 1) Volume Weighted Moving Average (VWMA): This is a “hidden strategy” feature implemented that will display the high-low bands of the VWMA on the price chart if run the code using “overlay = true”. - If the equity does not have volume, then the VWMA will not show up. Uncheck this box and it will use the regular WMA (no volume). - defines how far back the WMA averages price. 2) cRSI (Black line in the indicator) - Increase to length that amount of time a band (upper/lower) stays high/low after a peak. Reduce the value to shorten the time. Just increment it up/down to see the effect. - defines how far back the SMA averages the cRSI. This affects the purple line in the indicator. - defines how many bars back the peak detector looks to determine if a peak has occurred. For example, a top is detected like this: current-bar down relative to the 1-bar-back, 1-bar-back up relative to 2-bars-back (look back = 1), c) 2-bars-back up relative to 3-bars-back (lookback = 2), and d) 3-bars-back up relative to 4-bars-back (lookback = 3). I hope that makes sense. There are only 2 options for this setting: 2 or 3 bars. 2 bars will be able to detect small peaks but create more “false” peaks that may not be meaningful. 3 bars will be more robust but can miss short duration peaks. 3) Waves - The check boxes are self explanatory for which labels they turn on and off on the plot. 4) Divergence Indicators - The check boxes are self explanatory for which labels they turn on and off on the plot. Hints - The most common parameter to change is the . Different stocks will have different levels of strength in their peaks. A setting of 2 may generate too many corrective waves. - Different times scales will give you different wave counts. This is to be expected. A counter impulse wave inside a corrective wave may actually go above the cRSI WMA on a smaller time frame. You may need to increase it one or two levels to see large waves. - Just because you see divergence (bear or hidden bear) does not mean a price is going to go down. Often price continues to rise through bears, so take note and that is normal. Bulls are usually pretty good indicators especially if you see them on C,E,G waves. ---------------------------------------------------------------------------------------------------------------------------- cyclic smoothed RSI (cRSI) indicator ---------------------------------------------------------------------------------------------------------------------------- The “core” code for the cyclic smoothed RSI (cRSI) indicator was written by Lars von Theinen and is subject to the terms of the Mozilla Public License 2.0 at mozilla.org Copyright (C) 2017 CC BY, whentotrade / Lars von Thienen. For more details on the cRSI Indicator: The cyclic smoothed RSI indicator is an enhancement of the classic RSI, adding 1) additional smoothing according to the market vibration, 2) adaptive upper and lower bands according to the cyclic memory and 3) using the current dominant cycle length as input for the indicator. It is much more responsive to market moves than the basic RSI. The indicator uses the dominant cycle as input to optimize signal, smoothing, and cyclic memory. To get more in-depth information on the cyclic-smoothed RSI indicator, please read Decoding The Hidden Market Rhythm - Part 1: Dynamic Cycles (2017), Chapter 4: "Fine-tuning technical indicators." You need to derive the dominant cycle as input parameter for the cycle length as described in chapter 4. Hope this helps and good luck.
Indicatore Pine Script®
di Dr_Roboto
25
Time Range StatisticsA good amount of users requested a text box showing various price statistics, the following script returns various of these stats in a user-selected range, and include classical ones such as a central tendency measurement (mean), dispersion (normalized range) and percent change, but also include less common statistics such as average traded volume and number of gaps. The script also calculates the correlation between the closing price and another user-selected instrument. The script is currently the longest one I ever made and took some efforts, as I wasn't satisfied with the statistics to be originally included. Big thx to Gael for the enormous feedback and the idea of the normalized range, to user @Cookiecrush for the feedback ( without ya I would have posted something bad you know umu ? ), and Lulidolce for the support, friendship is magic! Selected Range The setting Start determine the bar at which the range starts, while End determine at which bar the range end. To help you select these values, the current bar number (bar index) is displayed at the right of the indicator title in blue. The setting evaluate to last bar will use a range starting at Start and ending at the last bar, as such you can use a full range by using Start = 0 and select evaluate to last bar The range is highlighted by an area on the chart. By default Start = 9000 and End = 10000, you might not have this amount of data in your chart, as such use the displayed bar index to select Start and End, then set the settings as default. Displayed Statistics The statistics panel is displayed on the right side of the last bar, the panel has 3 sections, a title section who shows the symbol ticker, timeframe, and overall trends represented by a chart emoji, the overall trends are determined by comparing the number of higher highs with the number of lower low. Below are displayed the date ranges with time format: year/month/day/hour:minute. The second section shows the general statistics. The first one is the mean, also represented by the orange line in the chart, the blue line displayed represent the highest price value in the range, while the red one represents the lowest price value. The second stat is the normalized range, and determine how spread is the price in the user-selected range, why not the standard deviation? Because the standard deviation might return results varying widely depending on the scale of the closing price, you could get measures such as 0.0156 or 16 or even 56 depending on the instrument, as such using a normalized range can be more appropriate as it lays in a range of (0,1). Lower values indicate a low degree of price variation. Note that I still want to find another measure in the future. The percentage change (or relative change) indicates at which percentage the price has increased or decreased, and is calculated by subtracting the closing at bar Start with the price at bar End , divided by the price at bar End , the result is then multiplied by 100. The average traded volume calculate the mean of the volume in the selected range, I used the same format used by the original volume indicator for clarity. Finally, the last stats of the section is the number of gaps, this stat is by default hidden. An up gap is detected when the open price is superior to the previous high, while a down gap is detected when the open price is inferior to the previous low, this allow to only retain significant gaps. The last section of the indicator panel shows the correlation between the closing price and another instrument, by default GOOG, this correlation is also calculated within the user-selected range. Positive values indicate a positive relationship, that is the two instruments tend to move in the same direction. Negative values indicate a negative relationship, both instruments tend to move in a direction opposite to each other. Values closer to 1 or -1 indicate a stronger relationship, while values closer to 0 indicate no relationship. In Summary The script shows various stats, each calculated within a user-selected range, in general one would be more interested in how these stats might evolve with time, but checking them in a custom range can be quite interesting. Thx for reading. umu
Indicatore Pine Script®
di alexgrover
16
Multi SMA EMA WMA HMA BB (4x5 MAs Bollinger Bands) Adv MTF - RRBMulti SMA EMA WMA HMA 4x5 Moving Averages with Bollinger Bands Advanced MTF by RagingRocketBull 2019 Version 1.0 This indicator shows multiple MAs of any type SMA EMA WMA HMA etc with BB and MTF support, can show MAs as dynamically moving levels. There are 4 MA groups + 1 BB group, a total of 4 TFs * 5 MAs = 20 MAs. You can assign any type/timeframe combo to a group, for example: - EMAs 12,26,50,100,200 x H1, H4, D1, W1 (4 TFs x 5 MAs x 1 type) - EMAs 8,10,13,21,30,50,55,100,200,400 x M15, H1 (2 TFs x 10 MAs x 1 type) - D1 EMAs and SMAs 8,10,12,26,30,50,55,100,200,400 (1 TF x 10 MAs x 2 types) - H1 WMAs 7,77,89,167,231; H4 HMAs 12,26,50,100,200; D1 EMAs 89,144,169,233,377; W1 SMAs 12,26,50,100,200 (4 TFs x 5 MAs x 4 types) - +1 extra MA type/timeframe for BB There are several versions: Simple, MTF, Pro MTF, Advanced MTF and Ultimate MTF. This is the Advanced MTF version. The Differences are listed below. All versions have BB - Simple: you have 2 groups of MAs that can be assigned any type (5+5) - MTF: +2 custom Timeframes for each group (2x5 MTF) +1 TF for BB, TF XY smoothing - Pro MTF: 4 custom Timeframes for each group (4x3 MTF), 1 TF for BB, MA levels and show max bars back options - Advanced MTF: +2 extra MAs/group (4x5 MTF), custom Ticker/Symbols, Timeframe <>= filter, Remove Duplicates Option - Ultimate MTF: +individual settings for each MA, custom Ticker/Symbols Features: - 4x5 = 20 MAs of any type - 4x MTF groups with XY step line smoothing - +1 extra TF/type for BB MAs - 4x5 = 20 MA levels with adjustable group offsets, indents and shift - supports any existing type of MA: SMA, EMA, WMA, Hull Moving Average (HMA) - custom tickers/symbols for each group - you can compare MAs of the same symbol across exchanges - show max bars back option - show/hide both groups of MAs/levels/BB and individual MAs - timeframe filter: show only MAs/Levels with TFs <>= Current TF - hide MAs/Levels with duplicate TFs - support for custom TFs that are not available in free accounts: 2D, 3D etc - support for timeframes in H: H, 2H, 4H etc Notes: - Uses timeframe textbox instead of input resolution dropdown to allow for 240 120 and other custom TFs - Uses symbol textbox instead of input symbol to avoid establishing multiple dummy security connections to the current ticker - otherwise empty symbols will prevent script from running - Possible reasons for missing MAs on a chart: - there may not be enough bars in history to start plotting it. For example, W1 EMA200 needs at least 200 bars on a weekly chart. - price << default Y smoothing step 5. For charts with low/fractional prices (i.e. 0.00002 << 5) adjust X Y smoothing as needed (set Y = 0.0000001) or disable it completely (set X,Y to 0,0) - TradingView Replay Mode UI and Pinescript security calls are limited to TFs >= D (D,2D,W,MN...) for free accounts - attempting to plot any TF < D1 in Replay Mode will only result in straight lines, but all TFs will work properly in history and real-time modes. This is not a bug. - Max Bars Back (num_bars) is limited to 5000 for free accounts (10000 for paid), will show error when exceeded. To plot on all available history set to 0 (default) - Slow load/redraw times. This indicator becomes slower, its UI less responsive when: - Pinescript Node.js graphics library is too slow and inefficient at plotting bars/objects in a browser window. Code optimization doesn't help much - the graphics engine is the main reason for general slowness. - the chart has a long history (10000+ bars) in a browser's cache (you have scrolled back a couple of screens in a max zoom mode). - Reload the page/Load a fresh chart and then apply the indicator or - Switch to another Timeframe (old TF history will still remain in cache and that TF will be slow) - in max possible zoom mode around 4500 bars can fit on 1 screen - this also slows down responsiveness. Reset Zoom level - initial load and redraw times after a param change in UI also depend on TF. For example: D1/W1 - 2 sec, H1/H4 - 5-6 sec, M30 - 10 sec, M15/M5 - 4 sec, M1 - 5 sec. M30 usually has the longest history (up to 16000 bars) and W1 - the shortest (1000 bars). - when indicator uses more MAs (plots) and timeframes it will redraw slower. Seems that up to 5 Timeframes is acceptable, but 6+ Timeframes can become very slow. - show_last=last_bars plot limit doesn't affect load/redraw times, so it was removed from MA plot - Max Bars Back (num_bars) default/custom set UI value doesn't seem to affect load/redraw times - In max zoom mode all dynamic levels disappear (they behave like text) 1. based on 3EmaBB, uses plot*, barssince and security functions 2. you can't set certain constants from input due to Pinescript limitations - change the code as needed, recompile and use as a private version 3. Levels = trackprice implementation 4. Show Max Bars Back = show_last implementation 5. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params 6. Smoothing is applied by default for visual aesthetics on MTF. To use exact ma mtf values (lines with stair stepping) - disable it Good Luck! You can explore, modify/reuse the code to build your own indicators.
Indicatore Pine Script®
di RagingRocketBull
3
The Zone Trades v1.0The Zone is mention in New Trading Dimensions by Bill Williams,PhD. The Zone is used for Entry Signal Green Zone are painting Green Bars when Awesome Oscillator (AO) and Accelerater/Decelerator (AC) are both increasing. Red Zone are painting Red Bars when Awesome Oscillator (AO) and Accelerater/Decelerator (AC) are both decreasing. Gray Zone are painting Gray Bars AO and AC in difference changing Gray Zone are indicate the indecision between bulls and bears. Bill Williams, PhD. mention that Green Zone or Red Zone usually happen 6-8 bars Continuously. The First Bar that change to be Green or Red color is the Signal Bar. Entry Signal is the second bar in the same color as the Signal bar happen with Volume Price go higher the high of previous Green Bar is Buy Signal. Entry Buy (Long) and place Stop at 1 tick lower the Low of previous bar. Price go ;ower the Low of previous Red Bars is Sell Signal. Entry Sell (Short) and place Stop at 1 tick higher the High of previous bar. Do not Entry if Green Bars or Red Bars completed 5 bars continuously.
Indicatore Pine Script®
di WaveRiders
The Zone Trades v1.0The Zone v.1.0 The Zone is mention in New Trading Dimensions by Bill Williams,PhD. The Zone is used for Entry Signal of Both Long and Short side. Green Zone are painting Green Bars when Awesome Oscillator (AO) and Accelerater/Decelerator (AC) are both increasing. Red Zone are painting Red Bars when Awesome Oscillator (AO) and Accelerater/Decelerator (AC) are both decreasing. Gray Zone are painting Gray Bars AO and AC in difference changing. Gray Zone are indicate the indecision between bulls and bears. Bill Williams, PhD. mention that Green Zone or Red Zone usually happen 6-8 bars Continuously. The First Bar that change to be Green or Red color is the Signal Bar. Entry Signal is the second bar in the same color as the Signal bar happen with Volume Price go higher the high of previous Green Bar is Buy Signal. Entry Buy (Long) and place Stop at 1 tick lower the Low of previous bar. Price go ;ower the Low of previous Red Bars is Sell Signal. Entry Sell (Short) and place Stop at 1 tick higher the High of previous bar. Do not Entry if Green Bars or Red Bars completed 5 bars continuously.
Indicatore Pine Script®
di WaveRiders
Indicator: Relative Volume Indicator & Freedom Of MovementRelative Volume Indicator ------------------------------ RVI is a support-resistance technical indicator developed by Melvin E. Dickover. Unlike many conventional support and resistance indicators, the Relative Volume Indicator takes into account price-volume behavior in order to detect the supply and demand pools. These pools are marked by "Defended Price Lines" (DPLs), also introduced by the author. RVI is usually plotted as a histogram; its bars are highlighted (black, by default) when the volume is unusually large. According to the author, this happens if the indicator value exceeds 2.0, thus signifying that a possible DPL is present. DPLs are horizontal lines that run across the chart at levels defined by following conditions: * Overlapping bars: If the indicator spike (i.e., indicator is above 2.0 or a custom value) corresponds to a price bar overlapping the previous one, the previous close can be used as the DPL value. * Very large bars: If the indicator spike corresponds to a price bar of a large size, use its close price as the DPL value. * Gapping bars: If the indicator spike corresponds to a price bar gapping from the previous bar, the DPL value will depend on the gap size. Small gaps can be ignored: the author suggests using the previous close as the DPL value. When the gap is big, the close of the latter bar is used instead. * Clustering spikes: If the indicator spikes come in clusters, use the extreme close or open price of the bar corresponding to the last or next to last spike in cluster. DPLs can be used as support and resistance levels. In order confirm and refine them, RVI is used along with the FreedomOfMovement indicator discussed next. Freedom of Movement Indicator ------------------------------ FOM is a support-resistance technical indicator, also by Melvin E. Dickover. FOM is the ratio of relative effect (relative price change) to the relative effort (normalized volume), expressed in standard deviations. This value is plotted as a histogram; its bars are highlighted (black, by default( when this ratio is unusually high. These highlighted bars, or "spikes", define the positioning of the DPLs. Suggestions for placing DPLs are the same as for the Relative Volume Indicator discussed above. Note that clustering spikes provide the strongest DPLs while isolated spikes can be used to confirm and refine those provided by the Relative Volume Indicator. Coincidence of spikes of the two indicator can be considered a sign of greater strength of the DPL. More info: S&C magazine, April 2014. I am still trying these on various instruments to understand the workings more. Don't forget to share what you learn -- any use cases / ideal scenarios / gotchas, would love to hear them all.
Indicatore Pine Script®
di LazyBear
25
Perfect MA Touch – Full Setup 1,3,5,7,8,9 v2This indicator helps you track a precise candle countdown from a moving average touch, labeling key bars (1, 3, 5, 7, 8, 9) for timing entries and momentum setups — with optional coloring, alerts, and full customization. What It Detects 1. MA Touch Trigger The sequence starts when any selected moving average (up to 6 MAs, customizable) is touched by the candle's high/low range. This "perfect touch" initiates the count and labels that candle as "1". 2. Candle Number Labels After a perfect MA touch: Candle 1 = the bar that touches the MA Candle 3 = two bars after Candle 1 Candle 5 = the fifth bar after the touch Candle 7 = third bar after Candle 5 Candle 8 = fourth bar after Candle 5 Candle 9 = fifth bar after Candle 5 It creates a time-based sequence you can use to anticipate reactions or momentum shifts. 3. Customization You can: Choose between EMA or SMA for each MA (6 total) Set custom lengths for each MA (9, 20, 50, 100, 150, 200) Choose which candle numbers (1, 3, 5, 7, 8, 9) to highlight Pick font size and label color 4. Highlighting and Alerts Highlight candles (with color) when certain bars (like 3, 5, 7) print Alerts are available for all tracked bars (1, 3, 5, 7, 8, 9) Use Case Example Let’s say you want to enter trades on the 3rd candle after a perfect MA touch: You set the script to highlight candle 3. When a candle hits your chosen MA (say EMA 9), it’s labeled “1”. Two bars later, bar 3 appears — giving you a timed signal to enter if price behavior aligns. This method is especially useful when paired with: Volume confirmation Breakout or reversal patterns Support/resistance or order block zones
Indicatore Pine Script®
di TheTradingGoddess
Perfect MA Touch – Full Setup 1,3,5,7,8,9This indicator helps you track a precise candle countdown from a moving average touch, labeling key bars (1, 3, 5, 7, 8, 9) for timing entries and momentum setups — with optional coloring, alerts, and full customization. What It Detects 1. MA Touch Trigger The sequence starts when any selected moving average (up to 6 MAs, customizable) is touched by the candle's high/low range. This "perfect touch" initiates the count and labels that candle as "1". 2. Candle Number Labels After a perfect MA touch: Candle 1 = the bar that touches the MA Candle 3 = two bars after Candle 1 Candle 5 = the fifth bar after the touch Candle 7 = third bar after Candle 5 Candle 8 = fourth bar after Candle 5 Candle 9 = fifth bar after Candle 5 It creates a time-based sequence you can use to anticipate reactions or momentum shifts. 3. Customization You can: Choose between EMA or SMA for each MA (6 total) Set custom lengths for each MA (9, 20, 50, 100, 150, 200) Choose which candle numbers (1, 3, 5, 7, 8, 9) to highlight Pick font size and label color 4. Highlighting and Alerts Highlight candles (with color) when certain bars (like 3, 5, 7) print Alerts are available for all tracked bars (1, 3, 5, 7, 8, 9) Use Case Example Let’s say you want to enter trades on the 3rd candle after a perfect MA touch: You set the script to highlight candle 3. When a candle hits your chosen MA (say EMA 9), it’s labeled “1”. Two bars later, bar 3 appears — giving you a timed signal to enter if price behavior aligns. This method is especially useful when paired with: Volume confirmation Breakout or reversal patterns Support/resistance or order block zones
Indicatore Pine Script®
di TheTradingGoddess
Market Zone Analyzer[BullByte]Understanding the Market Zone Analyzer --- 1. Purpose of the Indicator The Market Zone Analyzer is a Pine Script™ (version 6) indicator designed to streamline market analysis on TradingView. Rather than scanning multiple separate tools, it unifies four core dimensions—trend strength, momentum, price action, and market activity—into a single, consolidated view. By doing so, it helps traders: • Save time by avoiding manual cross-referencing of disparate signals. • Reduce decision-making errors that can arise from juggling multiple indicators. • Gain a clear, reliable read on whether the market is in a bullish, bearish, or sideways phase, so they can more confidently decide to enter, exit, or hold a position. --- 2. Why a Trader Should Use It • Unified View: Combines all essential market dimensions into one easy-to-read score and dashboard, eliminating the need to piece together signals manually. • Adaptability: Automatically adjusts its internal weighting for trend, momentum, and price action based on current volatility. Whether markets are choppy or calm, the indicator remains relevant. • Ease of Interpretation: Outputs a simple “BULLISH,” “BEARISH,” or “SIDEWAYS” label, supplemented by an intuitive on-chart dashboard and an oscillator plot that visually highlights market direction. • Reliability Features: Built-in smoothing of the net score and hysteresis logic (requiring consecutive confirmations before flips) minimize false signals during noisy or range-bound phases. --- 3. Why These Specific Indicators? This script relies on a curated set of well-established technical tools, each chosen for its particular strength in measuring one of the four core dimensions: 1. Trend Strength: • ADX/DMI (Average Directional Index / Directional Movement Index): Measures how strong a trend is, and whether the +DI line is above the –DI line (bullish) or vice versa (bearish). • Moving Average Slope (Fast MA vs. Slow MA): Compares a shorter-period SMA to a longer-period SMA; if the fast MA sits above the slow MA, it confirms an uptrend, and vice versa for a downtrend. • Ichimoku Cloud Differential (Senkou A vs. Senkou B): Provides a forward-looking view of trend direction; Senkou A above Senkou B signals bullishness, and the opposite signals bearishness. 2. Momentum: • Relative Strength Index (RSI): Identifies overbought (above its dynamically calculated upper bound) or oversold (below its lower bound) conditions; changes in RSI often precede price reversals. • Stochastic %K: Highlights shifts in short-term momentum by comparing closing price to the recent high/low range; values above its upper band signal bullish momentum, below its lower band signal bearish momentum. • MACD Histogram: Measures the difference between the MACD line and its signal line; a positive histogram indicates upward momentum, a negative histogram indicates downward momentum. 3. Price Action: • Highest High / Lowest Low (HH/LL) Range: Over a defined lookback period, this captures breakout or breakdown levels. A closing price near the recent highs (with a positive MA slope) yields a bullish score, and near the lows (with a negative MA slope) yields a bearish score. • Heikin-Ashi Doji Detection: Uses Heikin-Ashi candles to identify indecision or continuation patterns. A small Heikin-Ashi body (doji) relative to recent volatility is scored as neutral; a larger body in the direction of the MA slope is scored bullish or bearish. • Candle Range Measurement: Compares each candle’s high-low range against its own dynamic band (average range ± standard deviation). Large candles aligning with the prevailing trend score bullish or bearish accordingly; unusually small candles can indicate exhaustion or consolidation. 4. Market Activity: • Bollinger Bands Width (BBW): Measures the distance between BB upper and lower bands; wide bands indicate high volatility, narrow bands indicate low volatility. • Average True Range (ATR): Quantifies average price movement (volatility). A sudden spike in ATR suggests a volatile environment, while a contraction suggests calm. • Keltner Channels Width (KCW): Similar to BBW but uses ATR around an EMA. Provides a second layer of volatility context, confirming or contrasting BBW readings. • Volume (with Moving Average): Compares current volume to its moving average ± standard deviation. High volume validates strong moves; low volume signals potential lack of conviction. By combining these tools, the indicator captures trend direction, momentum strength, price-action nuances, and overall market energy, yielding a more balanced and comprehensive assessment than any single tool alone. --- 4. What Makes This Indicator Stand Out • Multi-Dimensional Analysis: Rather than relying on a lone oscillator or moving average crossover, it simultaneously evaluates trend, momentum, price action, and activity. • Dynamic Weighting: The relative importance of trend, momentum, and price action adjusts automatically based on real-time volatility (Market Activity State). For example, in highly volatile conditions, trend and momentum signals carry more weight; in calm markets, price action signals are prioritized. • Stability Mechanisms: • Smoothing: The net score is passed through a short moving average, filtering out noise, especially on lower timeframes. • Hysteresis: Both Market Activity State and the final bullish/bearish/sideways zone require two consecutive confirmations before flipping, reducing whipsaw. • Visual Interpretation: A fully customizable on-chart dashboard displays each sub-indicator’s value, regime, score, and comment, all color-coded. The oscillator plot changes color to reflect the current market zone (green for bullish, red for bearish, gray for sideways) and shows horizontal threshold lines at +2, 0, and –2. --- 5. Recommended Timeframes • Short-Term (5 min, 15 min): Day traders and scalpers can benefit from rapid signals, but should enable smoothing (and possibly disable hysteresis) to reduce false whipsaws. • Medium-Term (1 h, 4 h): Swing traders find a balance between responsiveness and reliability. Less smoothing is required here, and the default parameters (e.g., ADX length = 14, RSI length = 14) perform well. • Long-Term (Daily, Weekly): Position traders tracking major trends can disable smoothing for immediate raw readings, since higher-timeframe noise is minimal. Adjust lookback lengths (e.g., increase adxLength, rsiLength) if desired for slower signals. Tip: If you keep smoothing off, stick to timeframes of 1 h or higher to avoid excessive signal “chatter.” --- 6. How Scoring Works A. Individual Indicator Scores Each sub-indicator is assigned one of three discrete scores: • +1 if it indicates a bullish condition (e.g., RSI above its dynamically calculated upper bound). • 0 if it is neutral (e.g., RSI between upper and lower bounds). • –1 if it indicates a bearish condition (e.g., RSI below its dynamically calculated lower bound). Examples of individual score assignments: • ADX/DMI: • +1 if ADX ≥ adxThreshold and +DI > –DI (strong bullish trend) • –1 if ADX ≥ adxThreshold and –DI > +DI (strong bearish trend) • 0 if ADX < adxThreshold (trend strength below threshold) • RSI: • +1 if RSI > RSI_upperBound • –1 if RSI < RSI_lowerBound • 0 otherwise • ATR (as part of Market Activity): • +1 if ATR > (ATR_MA + stdev(ATR)) • –1 if ATR < (ATR_MA – stdev(ATR)) • 0 otherwise Each of the four main categories shares this same +1/0/–1 logic across their sub-components. B. Category Scores Once each sub-indicator reports +1, 0, or –1, these are summed within their categories as follows: • Trend Score = (ADX score) + (MA slope score) + (Ichimoku differential score) • Momentum Score = (RSI score) + (Stochastic %K score) + (MACD histogram score) • Price Action Score = (Highest-High/Lowest-Low score) + (Heikin-Ashi doji score) + (Candle range score) • Market Activity Raw Score = (BBW score) + (ATR score) + (KC width score) + (Volume score) Each category’s summed value can range between –3 and +3 (for Trend, Momentum, and Price Action), and between –4 and +4 for Market Activity raw. C. Market Activity State and Dynamic Weight Adjustments Rather than contributing directly to the netScore like the other three categories, Market Activity determines how much weight to assign to Trend, Momentum, and Price Action: 1. Compute Market Activity Raw Score by summing BBW, ATR, KCW, and Volume individual scores (each +1/0/–1). 2. Bucket into High, Medium, or Low Activity: • High if raw Score ≥ 2 (volatile market). • Low if raw Score ≤ –2 (calm market). • Medium otherwise. 3. Apply Hysteresis (if enabled): The state only flips after two consecutive bars register the same high/low/medium label. 4. Set Category Weights: • High Activity: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Low Activity: Trend = 25 %, Momentum = 20 %, Price Action = 55 %. • Medium Activity: Use the trader’s base weight inputs (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 % by default). D. Calculating the Net Score 5. Normalize Base Weights (so that the sum of Trend + Momentum + Price Action always equals 100 %). 6. Determine Current Weights based on the Market Activity State (High/Medium/Low). 7. Compute Each Category’s Contribution: Multiply (categoryScore) × (currentWeight). 8. Sum Contributions to get the raw netScore (a floating-point value that can exceed ±3 when scores are strong). 9. Smooth the netScore over two bars (if smoothing is enabled) to reduce noise. 10. Apply Hysteresis to the Final Zone: • If the smoothed netScore ≥ +2, the bar is classified as “Bullish.” • If the smoothed netScore ≤ –2, the bar is classified as “Bearish.” • Otherwise, it is “Sideways.” • To prevent rapid flips, the script requires two consecutive bars in the new zone before officially changing the displayed zone (if hysteresis is on). E. Thresholds for Zone Classification • BULLISH: netScore ≥ +2 • BEARISH: netScore ≤ –2 • SIDEWAYS: –2 < netScore < +2 --- 7. Role of Volatility (Market Activity State) in Scoring Volatility acts as a dynamic switch that shifts which category carries the most influence: 1. High Activity (Volatile): • Detected when at least two sub-scores out of BBW, ATR, KCW, and Volume equal +1. • The script sets Trend weight = 50 % and Momentum weight = 35 %. Price Action weight is minimized at 15 %. • Rationale: In volatile markets, strong trending moves and momentum surges dominate, so those signals are more reliable than nuanced candle patterns. 2. Low Activity (Calm): • Detected when at least two sub-scores out of BBW, ATR, KCW, and Volume equal –1. • The script sets Price Action weight = 55 %, Trend = 25 %, and Momentum = 20 %. • Rationale: In quiet, sideways markets, subtle price-action signals (breakouts, doji patterns, small-range candles) are often the best early indicators of a new move. 3. Medium Activity (Balanced): • Raw Score between –1 and +1 from the four volatility metrics. • Uses whatever base weights the trader has specified (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 %). Because volatility can fluctuate rapidly, the script employs hysteresis on Market Activity State: a new High or Low state must occur on two consecutive bars before weights actually shift. This avoids constant back-and-forth weight changes and provides more stability. --- 8. Scoring Example (Hypothetical Scenario) • Symbol: Bitcoin on a 1-hour chart. • Market Activity: Raw volatility sub-scores show BBW (+1), ATR (+1), KCW (0), Volume (+1) → Total raw Score = +3 → High Activity. • Weights Selected: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Trend Signals: • ADX strong and +DI > –DI → +1 • Fast MA above Slow MA → +1 • Ichimoku Senkou A > Senkou B → +1 → Trend Score = +3 • Momentum Signals: • RSI above upper bound → +1 • MACD histogram positive → +1 • Stochastic %K within neutral zone → 0 → Momentum Score = +2 • Price Action Signals: • Highest High/Lowest Low check yields 0 (close not near extremes) • Heikin-Ashi doji reading is neutral → 0 • Candle range slightly above upper bound but trend is strong, so → +1 → Price Action Score = +1 • Compute Net Score (before smoothing): • Trend contribution = 3 × 0.50 = 1.50 • Momentum contribution = 2 × 0.35 = 0.70 • Price Action contribution = 1 × 0.15 = 0.15 • Raw netScore = 1.50 + 0.70 + 0.15 = 2.35 • Since 2.35 ≥ +2 and hysteresis is met, the final zone is “Bullish.” Although the netScore lands at 2.35 (Bullish), smoothing might bring it slightly below 2.00 on the first bar (e.g., 1.90), in which case the script would wait for a second consecutive reading above +2 before officially classifying the zone as Bullish (if hysteresis is enabled). --- 9. Correlation Between Categories The four categories—Trend Strength, Momentum, Price Action, and Market Activity—often reinforce or offset one another. The script takes advantage of these natural correlations: • Bullish Alignment: If ADX is strong and pointed upward, fast MA is above slow MA, and Ichimoku is positive, that usually coincides with RSI climbing above its upper bound and the MACD histogram turning positive. In such cases, both Trend and Momentum categories generate +1 or +2. Because the Market Activity State is likely High (given the accompanying volatility), Trend and Momentum weights are at their peak, so the netScore quickly crosses into Bullish territory. • Sideways/Consolidation: During a low-volatility, sideways phase, ADX may fall below its threshold, MAs may flatten, and RSI might hover in the neutral band. However, subtle price-action signals (like a small breakout candle or a Heikin-Ashi candle with a slight bias) can still produce a +1 in the Price Action category. If Market Activity is Low, Price Action’s weight (55 %) can carry enough influence—even if Trend and Momentum are neutral—to push the netScore out of “Sideways” into a mild bullish or bearish bias. • Opposing Signals: When Trend is bullish but Momentum turns negative (for example, price continues up but RSI rolls over), the two scores can partially cancel. Market Activity may remain Medium, in which case the netScore lingers near zero (Sideways). The trader can then wait for either a clearer momentum shift or a fresh price-action breakout before committing. By dynamically recognizing these correlations and adjusting weights, the indicator ensures that: • When Trend and Momentum align (and volatility supports it), the netScore leaps strongly into Bullish or Bearish. • When Trend is neutral but Price Action shows an early move in a low-volatility environment, Price Action’s extra weight in the Low Activity State can still produce actionable signals. --- 10. Market Activity State & Its Role (Detailed) The Market Activity State is not a direct category score—it is an overarching context setter for how heavily to trust Trend, Momentum, or Price Action. Here’s how it is derived and applied: 1. Calculate Four Volatility Sub-Scores: • BBW: Compare the current band width to its own moving average ± standard deviation. If BBW > (BBW_MA + stdev), assign +1 (high volatility); if BBW < (BBW_MA × 0.5), assign –1 (low volatility); else 0. • ATR: Compare ATR to its moving average ± standard deviation. A spike above the upper threshold is +1; a contraction below the lower threshold is –1; otherwise 0. • KCW: Same logic as ATR but around the KCW mean. • Volume: Compare current volume to its volume MA ± standard deviation. Above the upper threshold is +1; below the lower threshold is –1; else 0. 2. Sum Sub-Scores → Raw Market Activity Score: Range between –4 and +4. 3. Assign Market Activity State: • High Activity: Raw Score ≥ +2 (at least two volatility metrics are strongly spiking). • Low Activity: Raw Score ≤ –2 (at least two metrics signal unusually low volatility or thin volume). • Medium Activity: Raw Score is between –1 and +1 inclusive. 4. Hysteresis for Stability: • If hysteresis is enabled, a new state only takes hold after two consecutive bars confirm the same High, Medium, or Low label. • This prevents the Market Activity State from bouncing around when volatility is on the fence. 5. Set Category Weights Based on Activity State: • High Activity: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Low Activity: Trend = 25 %, Momentum = 20 %, Price Action = 55 %. • Medium Activity: Use trader’s base weights (e.g., Trend = 40 %, Momentum = 30 %, Price Action = 30 %). 6. Impact on netScore: Because category scores (–3 to +3) multiply by these weights, High Activity amplifies the effect of strong Trend and Momentum scores; Low Activity amplifies the effect of Price Action. 7. Market Context Tooltip: The dashboard includes a tooltip summarizing the current state—e.g., “High activity, trend and momentum prioritized,” “Low activity, price action prioritized,” or “Balanced market, all categories considered.” --- 11. Category Weights: Base vs. Dynamic Traders begin by specifying base weights for Trend Strength, Momentum, and Price Action that sum to 100 %. These apply only when volatility is in the Medium band. Once volatility shifts: • High Volatility Overrides: • Trend jumps from its base (e.g., 40 %) to 50 %. • Momentum jumps from its base (e.g., 30 %) to 35 %. • Price Action is reduced to 15 %. Example: If base weights were Trend = 40 %, Momentum = 30 %, Price Action = 30 %, then in High Activity they become 50/35/15. A Trend score of +3 now contributes 3 × 0.50 = +1.50 to netScore; a Momentum +2 contributes 2 × 0.35 = +0.70. In total, Trend + Momentum can easily push netScore above the +2 threshold on its own. • Low Volatility Overrides: • Price Action leaps from its base (30 %) to 55 %. • Trend falls to 25 %, Momentum falls to 20 %. Why? When markets are quiet, subtle candle breakouts, doji patterns, and small-range expansions tend to foreshadow the next swing more effectively than raw trend readings. A Price Action score of +3 in this state contributes 3 × 0.55 = +1.65, which can carry the netScore toward +2—even if Trend and Momentum are neutral or only mildly positive. Because these weight shifts happen only after two consecutive bars confirm a High or Low state (if hysteresis is on), the indicator avoids constantly flipping its emphasis during borderline volatility phases. --- 12. Dominant Category Explained Within the dashboard, a label such as “Trend Dominant,” “Momentum Dominant,” or “Price Action Dominant” appears when one category’s absolute weighted contribution to netScore is the largest. Concretely: • Compute each category’s weighted contribution = (raw category score) × (current weight). • Compare the absolute values of those three contributions. • The category with the highest absolute value is flagged as Dominant for that bar. Why It Matters: • Momentum Dominant: Indicates that the combined force of RSI, Stochastic, and MACD (after weighting) is pushing netScore farther than either Trend or Price Action. In practice, it means that short-term sentiment and speed of change are the primary drivers right now, so traders should watch for continued momentum signals before committing to a trade. • Trend Dominant: Means ADX, MA slope, and Ichimoku (once weighted) outweigh the other categories. This suggests a strong directional move is in place; trend-following entries or confirming pullbacks are likely to succeed. • Price Action Dominant: Occurs when breakout/breakdown patterns, Heikin-Ashi candle readings, and range expansions (after weighting) are the most influential. This often happens in calmer markets, where subtle shifts in candle structure can foreshadow bigger moves. By explicitly calling out which category is carrying the most weight at any moment, the dashboard gives traders immediate insight into why the netScore is tilting toward bullish, bearish, or sideways. --- 13. Oscillator Plot: How to Read It The “Net Score” oscillator sits below the dashboard and visually displays the smoothed netScore as a line graph. Key features: 1. Value Range: In normal conditions it oscillates roughly between –3 and +3, but extreme confluences can push it outside that range. 2. Horizontal Threshold Lines: • +2 Line (Bullish threshold) • 0 Line (Neutral midline) • –2 Line (Bearish threshold) 3. Zone Coloring: • Green Background (Bullish Zone): When netScore ≥ +2. • Red Background (Bearish Zone): When netScore ≤ –2. • Gray Background (Sideways Zone): When –2 < netScore < +2. 4. Dynamic Line Color: • The plotted netScore line itself is colored green in a Bullish Zone, red in a Bearish Zone, or gray in a Sideways Zone, creating an immediate visual cue. Interpretation Tips: • Crossing Above +2: Signals a strong enough combined trend/momentum/price-action reading to classify as Bullish. Many traders wait for a clear crossing plus a confirmation candle before entering a long position. • Crossing Below –2: Indicates a strong Bearish signal. Traders may consider short or exit strategies. • Rising Slope, Even Below +2: If netScore climbs steadily from neutral toward +2, it demonstrates building bullish momentum. • Divergence: If price makes a higher high but the oscillator fails to reach a new high, it can warn of weakening momentum and a potential reversal. --- 14. Comments and Their Necessity Every sub-indicator (ADX, MA slope, Ichimoku, RSI, Stochastic, MACD, HH/LL, Heikin-Ashi, Candle Range, BBW, ATR, KCW, Volume) generates a short comment that appears in the detailed dashboard. Examples: • “Strong bullish trend” or “Strong bearish trend” for ADX/DMI • “Fast MA above slow MA” or “Fast MA below slow MA” for MA slope • “RSI above dynamic threshold” or “RSI below dynamic threshold” for RSI • “MACD histogram positive” or “MACD histogram negative” for MACD Hist • “Price near highs” or “Price near lows” for HH/LL checks • “Bullish Heikin Ashi” or “Bearish Heikin Ashi” for HA Doji scoring • “Large range, trend confirmed” or “Small range, trend contradicted” for Candle Range Additionally, the top-row comment for each category is: • Trend: “Highly Bullish,” “Highly Bearish,” or “Neutral Trend.” • Momentum: “Strong Momentum,” “Weak Momentum,” or “Neutral Momentum.” • Price Action: “Bullish Action,” “Bearish Action,” or “Neutral Action.” • Market Activity: “Volatile Market,” “Calm Market,” or “Stable Market.” Reasons for These Comments: • Transparency: Shows exactly how each sub-indicator contributed to its category score. • Education: Helps traders learn why a category is labeled bullish, bearish, or neutral, building intuition over time. • Customization: If, for example, the RSI comment says “RSI neutral” despite an impending trend shift, a trader might choose to adjust RSI length or thresholds. In the detailed dashboard, hovering over each comment cell also reveals a tooltip with additional context (e.g., “Fast MA above slow MA” or “Senkou A above Senkou B”), helping traders understand the precise rule behind that +1, 0, or –1 assignment. --- 15. Real-Life Example (Consolidated) • Instrument & Timeframe: Bitcoin (BTCUSD), 1-hour chart. • Current Market Activity: BBW and ATR both spike (+1 each), KCW is moderately high (+1), but volume is only neutral (0) → Raw Market Activity Score = +2 → State = High Activity (after two bars, if hysteresis is on). • Category Weights Applied: Trend = 50 %, Momentum = 35 %, Price Action = 15 %. • Trend Sub-Scores: 1. ADX = 25 (above threshold 20) with +DI > –DI → +1. 2. Fast MA (20-period) sits above Slow MA (50-period) → +1. 3. Ichimoku: Senkou A > Senkou B → +1. → Trend Score = +3. • Momentum Sub-Scores: 4. RSI = 75 (above its moving average +1 stdev) → +1. 5. MACD histogram = +0.15 → +1. 6. Stochastic %K = 50 (mid-range) → 0. → Momentum Score = +2. • Price Action Sub-Scores: 7. Price is not within 1 % of the 20-period high/low and slope = positive → 0. 8. Heikin-Ashi body is slightly larger than stdev over last 5 bars with haClose > haOpen → +1. 9. Candle range is just above its dynamic upper bound but trend is already captured, so → +1. → Price Action Score = +2. • Calculate netScore (before smoothing): • Trend contribution = 3 × 0.50 = 1.50 • Momentum contribution = 2 × 0.35 = 0.70 • Price Action contribution = 2 × 0.15 = 0.30 • Raw netScore = 1.50 + 0.70 + 0.30 = 2.50 → Immediately classified as Bullish. • Oscillator & Dashboard Output: • The oscillator line crosses above +2 and turns green. • Dashboard displays: • Trend Regime “BULLISH,” Trend Score = 3, Comment = “Highly Bullish.” • Momentum Regime “BULLISH,” Momentum Score = 2, Comment = “Strong Momentum.” • Price Action Regime “BULLISH,” Price Action Score = 2, Comment = “Bullish Action.” • Market Activity State “High,” Comment = “Volatile Market.” • Weights: Trend 50 %, Momentum 35 %, Price Action 15 %. • Dominant Category: Trend (because 1.50 > 0.70 > 0.30). • Overall Score: 2.50, posCount = (three +1s in Trend) + (two +1s in Momentum) + (two +1s in Price Action) = 7 bullish signals, negCount = 0. • Final Zone = “BULLISH.” • The trader sees that both Trend and Momentum are reinforcing each other under high volatility. They might wait one more candle for confirmation but already have strong evidence to consider a long. --- • . --- Disclaimer This indicator is strictly a technical analysis tool and does not constitute financial advice. All trading involves risk, including potential loss of capital. Past performance is not indicative of future results. Traders should: • Always backtest the “Market Zone Analyzer ” on their chosen symbols and timeframes before committing real capital. • Combine this tool with sound risk management, position sizing, and, if possible, fundamental analysis. • Understand that no indicator is foolproof; always be prepared for unexpected market moves. Goodluck -BullByte! ---
Indicatore Pine Script®
di BullByte
2
Canuck Trading Projection IndicatorCanuck Trading Projection Indicator Overview The Canuck Trading Projection Indicator is a powerful PineScript v6 tool designed for TradingView to project potential bullish and bearish price trajectories based on historical price and volume movements. It provides traders with actionable insights by estimating future price targets and assigning confidence levels to each outlook, helping to identify probable market directions across any timeframe. Ideal for both short-term and long-term traders, this indicator combines momentum analysis, RSI filtering, support/resistance detection, and time-weighted trend analysis to deliver robust projections. Features Bullish and Bearish Projections: Forecasts price targets for upward (bullish) and downward (bearish) movements over a user-defined projection period (default 20 bars). Confidence Levels: Assigns percentage confidence scores to each outlook, reflecting the likelihood of the projected price based on historical trends, volatility, and volume. RSI Filter: Incorporates a 14-period Relative Strength Index (RSI) to validate trends, requiring RSI > 50 for bullish and RSI < 50 for bearish signals. Support/Resistance Detection: Adjusts confidence levels when projections are near key swing highs/lows (within 2% of average price), boosting confidence by 5% for alignments. Time-Based Weighting: Prioritizes recent price movements in trend analysis, giving more weight to newer bars for improved relevance. Customizable Inputs: Allows users to tailor lookback period, projection bars, RSI period, confidence threshold, colors, and label positioning. Forced Label Spacing: Prevents overlap of bullish and bearish text labels, even for tight projections, using fixed vertical slots when price differences are small (<2% of average price). Timeframe Flexibility: Works seamlessly across all TradingView timeframes (e.g., 30-minute, hourly, daily, weekly, monthly), adapting projections to the chart’s resolution. Clean Visualization: Displays projections as green (bullish) and red (bearish) dashed lines, with non-overlapping text labels at the projection endpoints showing price targets and confidence levels. How It Works The indicator analyzes historical price and volume data over a user-defined lookback period (default 50 bars) to calculate: Momentum: Combines price changes and volume to assess trend strength, using a weighted moving average (WMA) for directional bias. Trend Analysis: Counts bullish (price up, volume above average, RSI > 50) and bearish (price down, volume above average, RSI < 50) trends, weighting recent bars more heavily. Projections: Bullish Slope: Positive or flat when momentum is upward, scaled by price change and momentum intensity. Bearish Slope: Negative or flat when momentum is downward, amplified by bearish confidence for stronger projections. Projects prices forward by 20 bars (default) using current close plus slope times projection bars. Confidence Levels: Base confidence derived from the proportion of bullish/bearish trends, with a 5% minimum to avoid zero confidence. Adjusted by volatility (lower volatility increases confidence), volume trends, and proximity to support/resistance levels. Visualization: Draws projection lines from the current close to the 20-bar future target. Places text labels at line endpoints, showing price targets and confidence percentages, with forced spacing for readability. Input Parameters Lookback Period (default: 50): Number of bars for historical analysis (minimum 10). Projection Bars (default: 20): Number of bars to project forward (minimum 5). Confidence Threshold (default: 0.6): Minimum confidence for strong trend indication (0.1 to 1.0). Bullish Projection Line Color (default: Green): Color for bullish projection line and label. Bearish Projection Line Color (default: Red): Color for bearish projection line and label. RSI Period (default: 14): Period for RSI momentum filter (minimum 5). Label Vertical Offset (%) (default: 1.0): Base offset for labels as a percentage of price range (0.1% to 5.0%). Minimum Label Spacing (%) (default: 2.0): Minimum vertical spacing between labels for tight projections (0.5% to 10.0%). Usage Instructions Add to Chart: Copy the script into TradingView’s Pine Editor, save, and add the indicator to your chart. Select Timeframe: Apply to any timeframe (e.g., 30-minute, hourly, daily, weekly, monthly) to match your trading strategy. Interpret Outputs: Green Line/Label: Bullish price target and confidence (e.g., "Bullish: 414.37, Confidence: 35%"). Red Line/Label: Bearish price target and confidence (e.g., "Bearish: 279.08, Confidence: 41.3%"). Higher confidence indicates a stronger likelihood of the projected outcome. Adjust Inputs: Modify Lookback Period to focus on shorter/longer historical trends (e.g., 20 for short-term, 100 for long-term). Change Projection Bars to adjust forecast horizon (e.g., 10 for shorter, 50 for longer). Tweak RSI Period or Confidence Threshold for sensitivity to momentum or trend strength. Customize Colors for visual preference. Increase Minimum Label Spacing if labels overlap in volatile markets. Combine with Analysis: Use alongside other indicators (e.g., moving averages, Bollinger Bands) or fundamental analysis to confirm signals, as projections are probabilistic. Example: TSLA Across Timeframes Using live TSLA data (close ~346.46 USD, May 31, 2025), the indicator produces: 30-Minute: Bullish 341.93 (13.3%), Bearish 327.96 (86.7%) – Strong bearish sentiment due to intraday volatility. 1-Hour: Bullish 342.00 (33.9%), Bearish 327.50 (62.3%) – Bearish but less intense, reflecting hourly swings. 4-Hour: Bullish 345.52 (73.4%), Bearish 344.44 (19.0%) – Flat outlook, indicating consolidation. Daily: Bullish 391.26 (68.8%), Bearish 302.22 (31.2%) – Bullish bias from recent uptrend, bearish tempered by longer lookback. Weekly: Bullish 414.37 (35.0%), Bearish 279.08 (41.3%) – Wide range, reflecting annual volatility. Monthly: Bullish 396.70 (54.9%), Bearish 296.93 (10.2%) – Long-term bullish optimism. These results align with market dynamics: short-term intervals capture volatility, while longer intervals smooth trends, providing balanced outlooks. Notes Accuracy: Projections are estimates based on historical data and should be used with other analysis tools. Confidence levels indicate likelihood, not certainty. Timeframe Sensitivity: Short-term intervals (e.g., 30-minute) show larger price swings and higher confidence due to volatility, while longer intervals (e.g., monthly) are more stable. Customization: Adjust inputs to match your trading style (e.g., shorter lookback for day trading, longer for swing trading). Performance: Tested on volatile stocks like TSLA, NVIDIA, and others, ensuring robust performance across markets. Limitations: May produce conservative bearish projections in strong uptrends due to momentum weighting. Adjust lookback or projection_bars for sensitivity. Feedback If you encounter issues (e.g., label overlap, projection mismatches), please share your timeframe, settings, or a screenshot. Suggestions for enhancements (e.g., additional filters, visual tweaks) are welcome! Disclaimer The Canuck Trading Projection Indicator is provided for educational and informational purposes only. It is not financial advice. Trading involves significant risks, and past performance is not indicative of future results. Always perform your own due diligence and consult a qualified financial advisor before making trading decisions.
Indicatore Pine Script®
di ctoincanada
FvgObject█ OVERVIEW This library provides a suite of methods designed to manage the visual representation and lifecycle of Fair Value Gap (FVG) objects on a Pine Script™ chart. It extends the `fvgObject` User-Defined Type (UDT) by attaching object-oriented functionalities for drawing, updating, and deleting FVG-related graphical elements. The primary goal is to encapsulate complex drawing logic, making the main indicator script cleaner and more focused on FVG detection and state management. █ CONCEPTS This library is built around the idea of treating each Fair Value Gap as an "object" with its own visual lifecycle on the chart. This is achieved by defining methods that operate directly on instances of the `fvgObject` UDT. Object-Oriented Approach for FVGs Pine Script™ v6 introduced the ability to define methods for User-Defined Types (UDTs). This library leverages this feature by attaching specific drawing and state management functions (methods) directly to the `fvgObject` type. This means that instead of calling global functions with an FVG object as a parameter, you call methods *on* the FVG object itself (e.g., `myFvg.updateDrawings(...)`). This approach promotes better code organization and a more intuitive way to interact with FVG data. FVG Visual Lifecycle Management The core purpose of this library is to manage the complete visual journey of an FVG on the chart. This lifecycle includes: Initial Drawing: Creating the first visual representation of a newly detected FVG, including its main box and optionally its midline and labels. State Updates & Partial Fills: Modifying the FVG's appearance as it gets partially filled by price. This involves drawing a "mitigated" portion of the box and adjusting the `currentTop` or `currentBottom` of the remaining FVG. Full Mitigation & Tested State: Handling how an FVG is displayed once fully mitigated. Depending on user settings, it might be hidden, or its box might change color/style to indicate it has been "tested." Mitigation lines can also be managed (kept or deleted). Midline Interaction: Visually tracking if the price has touched the FVG's 50% equilibrium level (midline). Visibility Control: Dynamically showing or hiding FVG drawings based on various criteria, such as user settings (e.g., hide mitigated FVGs, timeframe-specific visibility) or external filters (e.g., proximity to current price). Deletion: Cleaning up all drawing objects associated with an FVG when it's no longer needed or when settings dictate its removal. Centralized Drawing Logic By encapsulating all drawing-related operations within the methods of this library, the main indicator script is significantly simplified. The main script can focus on detecting FVGs and managing their state (e.g., in arrays), while delegating the complex task of rendering and updating them on the chart to the methods herein. Interaction with `fvgObject` and `drawSettings` UDTs All methods within this library operate on an instance of the `fvgObject` UDT. This `fvgObject` holds not only the FVG's price/time data and state (like `isMitigated`, `currentTop`) but also the IDs of its associated drawing elements (e.g., `boxId`, `midLineId`). The appearance of these drawings (colors, styles, visibility, etc.) is dictated by a `drawSettings` UDT instance, which is passed as a parameter to most drawing-related methods. This `drawSettings` object is typically populated from user inputs in the main script, allowing for extensive customization. Stateful Drawing Object Management The library's methods manage Pine Script™ drawing objects (boxes, lines, labels) by storing their IDs within the `fvgObject` itself (e.g., `fvgObject.boxId`, `fvgObject.mitigatedBoxId`, etc.). Methods like `draw()` create these objects and store their IDs, while methods like `updateDrawings()` modify them, and `deleteDrawings()` removes them using these stored IDs. Drawing Optimization The `updateDrawings()` method, which is the most comprehensive drawing management function, incorporates optimization logic. It uses `prev_*` fields within the `fvgObject` (e.g., `prevIsMitigated`, `prevCurrentTop`) to store the FVG's state from the previous bar. By comparing the current state with the previous state, and also considering changes in visibility or relevant drawing settings, it can avoid redundant and performance-intensive drawing operations if nothing visually significant has changed for that FVG. █ METHOD USAGE AND WORKFLOW The methods in this library are designed to be called in a logical sequence as an FVG progresses through its lifecycle. A crucial prerequisite for all visual methods in this library is a properly populated `drawSettings` UDT instance, which dictates every aspect of an FVG's appearance, from colors and styles to visibility and labels. This `settings` object must be carefully prepared in the main indicator script, typically based on user inputs, before being passed to these methods. Here’s a typical workflow within a main indicator script: 1. FVG Instance Creation (External to this library) An `fvgObject` instance is typically created by functions in another library (e.g., `FvgCalculations`) when a new FVG pattern is identified. This object will have its core properties (top, bottom, startTime, isBullish, tfType) initialized. 2. Initial Drawing (`draw` method) Once a new `fvgObject` is created and its initial visibility is determined: Call the `myFvg.draw(settings)` method on the new FVG object. `settings` is an instance of the `drawSettings` UDT, containing all relevant visual configurations. This method draws the primary FVG box, its midline (if enabled in `settings`), and any initial labels. It also initializes the `currentTop` and `currentBottom` fields of the `fvgObject` if they are `na`, and stores the IDs of the created drawing objects within the `fvgObject`. 3. Per-Bar State Updates & Interaction Checks On each subsequent bar, for every active `fvgObject`: Interaction Check (External Logic): It's common to first use logic (e.g., from `FvgCalculations`' `fvgInteractionCheck` function) to determine if the current bar's price interacts with the FVG. State Field Updates (External Logic): Before calling the `FvgObjectLib` methods below, ensure that your `fvgObject`'s state fields (such as `isMitigated`, `currentTop`, `currentBottom`, `isMidlineTouched`) are updated using the current bar's price data and relevant functions from other libraries (e.g., `FvgCalculations`' `checkMitigation`, `checkPartialMitigation`, etc.). This library's methods render the FVG based on these pre-updated state fields. If interaction occurs and the FVG is not yet fully mitigated: Full Mitigation Update (`updateMitigation` method): Call `myFvg.updateMitigation(high, low)`. This method updates `myFvg.isMitigated` and `myFvg.mitigationTime` if full mitigation occurs, based on the interaction determined by external logic. Partial Fill Update (`updatePartialFill` method): If not fully mitigated, call `myFvg.updatePartialFill(high, low, settings)`. This method updates `myFvg.currentTop` or `myFvg.currentBottom` and adjusts drawings to show the filled portion, again based on prior interaction checks and fill level calculations. Midline Touch Check (`checkMidlineTouch` method): Call `myFvg.checkMidlineTouch(high, low)`. This method updates `myFvg.isMidlineTouched` if the price touches the FVG's 50% level. 4. Comprehensive Visual Update (`updateDrawings` method) After the FVG's state fields have been potentially updated by external logic and the methods in step 3: Call `myFvg.updateDrawings(isVisibleNow, settings)` on each FVG object. `isVisibleNow` is a boolean indicating if the FVG should currently be visible. `settings` is the `drawSettings` UDT instance. This method synchronizes the FVG's visual appearance with its current state and settings, managing all drawing elements (boxes, lines, labels), their styles, and visibility. It efficiently skips redundant drawing operations if the FVG's state or visibility has not changed, thanks to its internal optimization using `prev_*` fields, which are also updated by this method. 5. Deleting Drawings (`deleteDrawings` method) When an FVG object is no longer tracked: Call `myFvg.deleteDrawings(deleteTestedToo)`. This method removes all drawing objects associated with that `fvgObject`. This workflow ensures that FVG visuals are accurately maintained throughout their existence on the chart. █ NOTES Dependencies: This library relies on `FvgTypes` for `fvgObject` and `drawSettings` definitions, and its methods (`updateMitigation`, `updatePartialFill`) internally call functions from `FvgCalculations`. Drawing Object Management: Be mindful of TradingView's limits on drawing objects per script. The main script should manage the number of active FVG objects. Performance and `updateDrawings()`: The `updateDrawings()` method is comprehensive. Its internal optimization (checking `hasStateChanged` based on `prev_*` fields) is crucial for performance. Call it judiciously. Role of `settings.currentTime`: The `currentTime` field in `drawSettings` is key for positioning time-dependent elements like labels and the right edge of non-extended drawings. Mutability of `fvgObject` Instances: Methods in this library directly modify the `fvgObject` instance they are called upon (e.g., its state fields and drawing IDs). Drawing ID Checks: Methods generally check if drawing IDs are `na` before acting on them, preventing runtime errors. █ EXPORTED FUNCTIONS method draw(this, settings)   Draws the initial visual representation of the FVG object on the chart. This includes the main FVG box, its midline (if enabled), and a label (if enabled for the specific timeframe). This method is typically invoked immediately after an FVG is first detected and its initial properties are set. It uses drawing settings to customize the appearance based on the FVG's timeframe type.   Namespace types: types.fvgObject   Parameters:      this (fvgObject type from no1x/FvgTypes/1) : The FVG object instance to be drawn. Core properties (top, bottom, startTime, isBullish, tfType) should be pre-initialized. This method will initialize boxId, midLineId, boxLabelId (if applicable), and currentTop/currentBottom (if currently na) on this object.      settings (drawSettings type from no1x/FvgTypes/1) : A drawSettings object providing all visual parameters. Reads display settings (colors, styles, visibility for boxes, midlines, labels, box extension) relevant to this.tfType. settings.currentTime is used for positioning labels and the right boundary of non-extended boxes. method updateMitigation(this, highVal, lowVal)   Checks if the FVG has been fully mitigated by the current bar's price action.   Namespace types: types.fvgObject   Parameters:      this (fvgObject type from no1x/FvgTypes/1) : The FVG object instance. Reads this.isMitigated, this.isVisible, this.isBullish, this.top, this.bottom. Updates this.isMitigated and this.mitigationTime if full mitigation occurs.      highVal (float) : The high price of the current bar, used for mitigation check.      lowVal (float) : The low price of the current bar, used for mitigation check. method updatePartialFill(this, highVal, lowVal, settings)   Checks for and processes partial fills of the FVG.   Namespace types: types.fvgObject   Parameters:      this (fvgObject type from no1x/FvgTypes/1) : The FVG object instance. Reads this.isMitigated, this.isVisible, this.isBullish, this.currentTop, this.currentBottom, original this.top/this.bottom, this.startTime, this.tfType, this.isLV. Updates this.currentTop or this.currentBottom, creates/updates this.mitigatedBoxId, and may update this.boxId's top/bottom to reflect the filled portion.      highVal (float) : The high price of the current bar, used for partial fill check.      lowVal (float) : The low price of the current bar, used for partial fill check.      settings (drawSettings type from no1x/FvgTypes/1) : The drawing settings. Reads timeframe-specific colors for mitigated boxes (e.g., settings.mitigatedBullBoxColor, settings.mitigatedLvBullColor), box extension settings (settings.shouldExtendBoxes, settings.shouldExtendMtfBoxes, etc.), and settings.currentTime to style and position the mitigatedBoxId and potentially adjust the main boxId. method checkMidlineTouch(this, highVal, lowVal)   Checks if the FVG's midline (50% level or Equilibrium) has been touched.   Namespace types: types.fvgObject   Parameters:      this (fvgObject type from no1x/FvgTypes/1) : The FVG object instance. Reads this.midLineId, this.isMidlineTouched, this.top, this.bottom. Updates this.isMidlineTouched if a touch occurs.      highVal (float) : The high price of the current bar, used for midline touch check.      lowVal (float) : The low price of the current bar, used for midline touch check. method deleteDrawings(this, deleteTestedToo)   Deletes all visual drawing objects associated with this FVG object.   Namespace types: types.fvgObject   Parameters:      this (fvgObject type from no1x/FvgTypes/1) : The FVG object instance. Deletes drawings referenced by boxId, mitigatedBoxId, midLineId, mitLineId, boxLabelId, mitLineLabelId, and potentially testedBoxId, keptMitLineId. Sets these ID fields to na.      deleteTestedToo (simple bool) : If true, also deletes drawings for "tested" FVGs (i.e., testedBoxId and keptMitLineId). method updateDrawings(this, isVisibleNow, settings)   Manages the comprehensive update of all visual elements of an FVG object based on its current state (e.g., active, mitigated, partially filled) and visibility. It handles the drawing, updating, or deletion of FVG boxes (main and mitigated part), midlines, mitigation lines, and their associated labels. Visibility is determined by the isVisibleNow parameter and relevant settings (like settings.shouldHideMitigated or timeframe-specific show flags). This method is central to the FVG's visual lifecycle and includes optimization to avoid redundant drawing operations if the FVG's relevant state or appearance settings have not changed since the last bar. It also updates the FVG object's internal prev_* state fields for future optimization checks.   Namespace types: types.fvgObject   Parameters:      this (fvgObject type from no1x/FvgTypes/1) : The FVG object instance to update. Reads most state fields (e.g., isMitigated, currentTop, tfType, etc.) and updates all drawing ID fields (boxId, midLineId, etc.), this.isVisible, and all this.prev_* state fields.      isVisibleNow (bool) : A flag indicating whether the FVG should be currently visible. Typically determined by external logic (e.g., visual range filter). Affects whether active FVG drawings are created/updated or deleted by this method.      settings (drawSettings type from no1x/FvgTypes/1) : A fully populated drawSettings object. This method extensively reads its fields (colors, styles, visibility toggles, timeframe strings, etc.) to render FVG components according to this.tfType and current state. settings.currentTime is critical for positioning elements like labels and extending drawings.
Libreria Pine Script®
di no1x