Mulakan

Cari dalam skrip untuk "mtf"

MTF Previous Open/Close/RangeThis indicator will simply plot on your chart the Daily/Weekly/Monthly previous candle levels. The "Auto" mode will allow automatic adjustment of timeframe displayed according to your chart. Otherwise you can select manually. Indicator plots the open/close and colors the high-low range area in the background. Hope this simple indicator will help you ! You can check my indicators via my TradingView's Profile : @PRO_Indicators
Penunjuk Pine Script®
oleh PRO_Indicators
6
Multi-Fibonacci Trend Average[FibonacciFlux]Multi-Fibonacci Trend Average (MFTA): An Institutional-Grade Trend Confluence Indicator for Discerning Market Participants My original indicator/Strategy: Engineered for the sophisticated demands of institutional and advanced traders, the Multi-Fibonacci Trend Average (MFTA) indicator represents a paradigm shift in technical analysis. This meticulously crafted tool is designed to furnish high-definition trend signals within the complexities of modern financial markets. Anchored in the rigorous principles of Fibonacci ratios and augmented by advanced averaging methodologies, MFTA delivers a granular perspective on trend dynamics. Its integration of Multi-Timeframe (MTF) filters provides unparalleled signal robustness, empowering strategic decision-making with a heightened degree of confidence. MFTA indicator on BTCUSDT 15min chart with 1min RSI and MACD filters enabled. Note the refined signal generation with reduced noise. MFTA indicator on BTCUSDT 15min chart without MTF filters. While capturing more potential trading opportunities, it also generates a higher frequency of signals, including potential false positives. Core Innovation: Proprietary Fibonacci-Enhanced Supertrend Averaging Engine The MFTA indicator’s core innovation lies in its proprietary implementation of Supertrend analysis, strategically fortified by Fibonacci ratios to construct a truly dynamic volatility envelope. Departing from conventional Supertrend methodologies, MFTA autonomously computes not one, but three distinct Supertrend lines. Each of these lines is uniquely parameterized by a specific Fibonacci factor: 0.618 (Weak), 1.618 (Medium/Golden Ratio), and 2.618 (Strong/Extended Fibonacci). // Fibonacci-based factors for multiple Supertrend calculations factor1 = input.float(0.618, 'Factor 1 (Weak/Fibonacci)', minval=0.01, step=0.01, tooltip='Factor 1 (Weak/Fibonacci)', group="Fibonacci Supertrend") factor2 = input.float(1.618, 'Factor 2 (Medium/Golden Ratio)', minval=0.01, step=0.01, tooltip='Factor 2 (Medium/Golden Ratio)', group="Fibonacci Supertrend") factor3 = input.float(2.618, 'Factor 3 (Strong/Extended Fib)', minval=0.01, step=0.01, tooltip='Factor 3 (Strong/Extended Fib)', group="Fibonacci Supertrend") This multi-faceted architecture adeptly captures a spectrum of market volatility sensitivities, ensuring a comprehensive assessment of prevailing conditions. Subsequently, the indicator algorithmically synthesizes these disparate Supertrend lines through arithmetic averaging. To achieve optimal signal fidelity and mitigate inherent market noise, this composite average is further refined utilizing an Exponential Moving Average (EMA). // Calculate average of the three supertends and a smoothed version superlength = input.int(21, 'Smoothing Length', tooltip='Smoothing Length for Average Supertrend', group="Fibonacci Supertrend") average_trend = (supertrend1 + supertrend2 + supertrend3) / 3 smoothed_trend = ta.ema(average_trend, superlength) The resultant ‘Smoothed Trend’ line emerges as a remarkably responsive yet stable trend demarcation, offering demonstrably superior clarity and precision compared to singular Supertrend implementations, particularly within the turbulent dynamics of high-volatility markets. Elevated Signal Confluence: Integrated Multi-Timeframe (MTF) Validation Suite MFTA transcends the limitations of conventional trend indicators by incorporating an advanced suite of three independent MTF filters: RSI, MACD, and Volume. These filters function as sophisticated validation protocols, rigorously ensuring that only signals exhibiting a confluence of high-probability factors are brought to the forefront. 1. Granular Lower Timeframe RSI Momentum Filter The Relative Strength Index (RSI) filter, computed from a user-defined lower timeframe, furnishes critical momentum-based signal validation. By meticulously monitoring RSI dynamics on an accelerated timeframe, traders gain the capacity to evaluate underlying momentum strength with precision, prior to committing to signal execution on the primary chart timeframe. // --- Lower Timeframe RSI Filter --- ltf_rsi_filter_enable = input.bool(false, title="Enable RSI Filter", group="MTF Filters", tooltip="Use RSI from lower timeframe as a filter") ltf_rsi_timeframe = input.timeframe("1", title="RSI Timeframe", group="MTF Filters", tooltip="Timeframe for RSI calculation") ltf_rsi_length = input.int(14, title="RSI Length", minval=1, group="MTF Filters", tooltip="Length for RSI calculation") ltf_rsi_threshold = input.int(30, title="RSI Threshold", minval=0, maxval=100, group="MTF Filters", tooltip="RSI value threshold for filtering signals") 2. Convergent Lower Timeframe MACD Trend-Momentum Filter The Moving Average Convergence Divergence (MACD) filter, also calculated on a lower timeframe basis, introduces a critical layer of trend-momentum convergence confirmation. The bullish signal configuration rigorously mandates that the MACD line be definitively positioned above the Signal line on the designated lower timeframe. This stringent condition ensures a robust indication of converging momentum that aligns synergistically with the prevailing trend identified on the primary timeframe. // --- Lower Timeframe MACD Filter --- ltf_macd_filter_enable = input.bool(false, title="Enable MACD Filter", group="MTF Filters", tooltip="Use MACD from lower timeframe as a filter") ltf_macd_timeframe = input.timeframe("1", title="MACD Timeframe", group="MTF Filters", tooltip="Timeframe for MACD calculation") ltf_macd_fast_length = input.int(12, title="MACD Fast Length", minval=1, group="MTF Filters", tooltip="Fast EMA length for MACD") ltf_macd_slow_length = input.int(26, title="MACD Slow Length", minval=1, group="MTF Filters", tooltip="Slow EMA length for MACD") ltf_macd_signal_length = input.int(9, title="MACD Signal Length", minval=1, group="MTF Filters", tooltip="Signal SMA length for MACD") 3. Definitive Volume Confirmation Filter The Volume Filter functions as an indispensable arbiter of trade conviction. By establishing a dynamic volume threshold, defined as a percentage relative to the average volume over a user-specified lookback period, traders can effectively ensure that all generated signals are rigorously validated by demonstrably increased trading activity. This pivotal validation step signifies robust market participation, substantially diminishing the potential for spurious or false breakout signals. // --- Volume Filter --- volume_filter_enable = input.bool(false, title="Enable Volume Filter", group="MTF Filters", tooltip="Use volume level as a filter") volume_threshold_percent = input.int(title="Volume Threshold (%)", defval=150, minval=100, group="MTF Filters", tooltip="Minimum volume percentage compared to average volume to allow signal (100% = average)") These meticulously engineered filters operate in synergistic confluence, requiring all enabled filters to definitively satisfy their pre-defined conditions before a Buy or Sell signal is generated. This stringent multi-layered validation process drastically minimizes the incidence of false positive signals, thereby significantly enhancing entry precision and overall signal reliability. Intuitive Visual Architecture & Actionable Intelligence MFTA provides a demonstrably intuitive and visually rich charting environment, meticulously delineating trend direction and momentum through precisely color-coded plots: Average Supertrend: Thin line, green/red for uptrend/downtrend, immediate directional bias. Smoothed Supertrend: Bold line, teal/purple for uptrend/downtrend, cleaner, institutionally robust trend. Dynamic Trend Fill: Green/red fill between Supertrends quantifies trend strength and momentum. Adaptive Background Coloring: Light green/red background mirrors Smoothed Supertrend direction, holistic trend perspective. Precision Buy/Sell Signals: ‘BUY’/‘SELL’ labels appear on chart when trend touch and MTF filter confluence are satisfied, facilitating high-conviction trade action. MFTA indicator applied to BTCUSDT 4-hour chart, showcasing its effectiveness on higher timeframes. The Smoothed Length parameter is increased to 200 for enhanced smoothness on this timeframe, coupled with 1min RSI and Volume filters for signal refinement. This illustrates the indicator's adaptability across different timeframes and market conditions. Strategic Applications for Institutional Mandates MFTA’s sophisticated design provides distinct advantages for advanced trading operations and institutional investment mandates. Key strategic applications include: High-Probability Trend Identification: Fibonacci-averaged Supertrend with MTF filters robustly identifies high-probability trend continuations and reversals, enhancing alpha generation. Precision Entry/Exit Signals: Volume and momentum-filtered signals enable institutional-grade precision for optimized risk-adjusted returns. Algorithmic Trading Integration: Clear signal logic facilitates seamless integration into automated trading systems for scalable strategy deployment. Multi-Asset/Timeframe Versatility: Adaptable parameters ensure applicability across diverse asset classes and timeframes, catering to varied trading mandates. Enhanced Risk Management: Superior signal fidelity from MTF filters inherently reduces false signals, supporting robust risk management protocols. Granular Customization and Parameterized Control MFTA offers unparalleled customization, empowering users to fine-tune parameters for precise alignment with specific trading styles and market conditions. Key adjustable parameters include: Fibonacci Factors: Adjust Supertrend sensitivity to volatility regimes. ATR Length: Control volatility responsiveness in Supertrend calculations. Smoothing Length: Refine Smoothed Trend line responsiveness and noise reduction. MTF Filter Parameters: Independently configure timeframes, lookback periods, and thresholds for RSI, MACD, and Volume filters for optimal signal filtering. Disclaimer MFTA is meticulously engineered for high-quality trend signals; however, no indicator guarantees profit. Market conditions are unpredictable, and trading involves substantial risk. Rigorous backtesting and forward testing across diverse datasets, alongside a comprehensive understanding of the indicator's logic, are essential before live deployment. Past performance is not indicative of future results. MFTA is for informational and analytical purposes only and is not financial or investment advice.
Penunjuk Pine Script®
oleh FibonacciFlux
4
LONG SAZB $This strategy combines the use of: -The MTF EMA to detect trends. -The MACD to create Long and Short Buy signals. -The ATR for setting Stop Losses and Take Profits. This works well with many different crypto and fiat pairs, but it must be optimized for the certain behavior of the currency pair. Its optimal use is strong trends, not so profitable when sideways. This strategy was developed with the 5-minute Bitcoin / TetherUS Perpetual futures for Binance (Crypto trading platform). This is the first version, updates will come. MTF EMA The MTF EMA (Multi-TimeFrame Exponential Moving Average ) is a great indicator to see the overall trend of an asset, you can see the status of a moving average for all timeframes on one chart. Normally when you check a moving average of the price it's on some specific timeframe. The MTF EMA allows you to see moving average status for all timeframes in a single place. You can simplify your visual representation and know if an asset or a pair is overall bullish or bearish , with this improving your entry and exit signal decisions. This strategy uses the 1 hour and 15 min EMA with different values. Experimenting with these is important to understand the currency pairs. Up trend: Price (source) > 1h MTF and 1h MTF < 15m MTF Down trend: Price (source) < 1h MTF and 1h MTF > 15m MTF MACD Using MACD (Moving Average Convergence Divergence) as a reference, the strategy identifies when the MACD line crosses over (a factor in a buy signal) and under (a factor in a Sell signal) the Signal line. This shows a shift in positive (cross over) and negative (cross under) of a security. This strategy uses values of 12 on the Fast MA, 26 on the Slow MA, and 9 in the Signal Line MA. The optional ribbon is for a more visual representation of the MACD . The MACD and Signal line have the option to have a crossover limit to cancel buy signals depending on the value they crossed at according to the 0 line of the MACD . This is to avoid fake signals. ATR TP/SL Using ATR to define the stop loss and take profit is that it should allow you to set them at a realistic distance from price. Simply put, a pair experiencing a high level of volatility has a higher ATR, and a low volatility stock has a lower ATR. The indicator does not indicate the price direction; rather it is used primarily to measure volatility caused by gaps and limit up or down moves. All this is used to allow the Stop Loss “breathing space” so trades don't get unnecessarily stopped, and allow the Take Profit to be at a more realistic, flexible, and profitable price. This strategy uses different values for Longs and Shorts depending on the market behavior, optionally analyzes swing lows and highs according to the value of the candle lookback and sets the ATR depending on them, they must be tested to optimum. Also the ATR has a multiplicator to find the most efficient price levels. Trade Setup Shorts and Longs can be turned OFF and ON. There is an optional maximum % loss for trades, the trade is closed when the high-low average of a candle is over this %. Longs This strategy indicates a Long Buy signal when these conditions are met: - Uptrend signal from MTF EMA . - MACD Crossover of Signal ( MACD > Signal) while being under the MACD crossover limit. A Long exit signal is indicated when: - Price crosses over the ATR Take Profit limit. - Price crosses under the ATR Stop Loss limit. - Price crosses under optional max % long loss. Shorts This strategy indicates a Long Buy signal when these conditions are met: - Downtrend signal from MTF EMA . - Signal Crossover of MACD ( MACD < Signal) while being over the MACD crossover limit. A Short exit signal is indicated when: - Price crosses under the ATR Take Profit limit. - Price crosses over the ATR Stop Loss limit. - Price crosses over optional max % short loss. Disclaimer 1. I am not a licensed financial advisor or broker dealer. I do not tell you when or what to buy or sell. I developed this software which enables you to execute manual or automated trades multiple trades using TradingView. The software allows you to set the criteria you want for entering and exiting trades. 2. Do not trade with money you cannot afford to lose. 3. I do not guarantee consistent profits or that anyone can make money with no effort. I am not selling the holy grail. 4. Every system can have winning and losing streaks. 5. Money management plays a large role in the results of your trading. For example: lot size, account size, broker leverage, and broker margin call rules all have an effect on results. Also, your Take Profit and Stop Loss settings for individual pair trades and for overall account equity have a major impact on results. If you are new to trading and do not understand these items, then I recommend you seek education materials to further your knowledge. **YOU NEED TO FIND AND USE THE TRADING SYSTEM THAT WORKS BEST FOR YOU AND YOUR TRADING TOLERANCE.** **I HAVE PROVIDED NOTHING MORE THAN A TOOL WITH OPTIONS FOR YOU TO TRADE WITH THIS PROGRAM ON TRADINGVIEW.** I am 100 % open to suggestions to improve the script. If you encounter any problems or would like to see the script, share them with me at "steven17zmuda@gmail.com". Items in this description text may not be written directly by me, but may be taken from education sites.
Strategi Pine Script®
oleh stevenz17
`security()` revisited [PineCoders]NOTE The non-repainting technique in this publication that relies on bar states is now deprecated, as we have identified inconsistencies that undermine its credibility as a universal solution. The outputs that use the technique are still available for reference in this publication. However, we do not endorse its usage. See this publication for more information about the current best practices for requesting HTF data and why they work. █  OVERVIEW This script presents a new function to help coders use security() in both repainting and non-repainting modes. We revisit this often misunderstood and misused function, and explain its behavior in different contexts, in the hope of dispelling some of the coder lure surrounding it. The function is incredibly powerful, yet misused, it can become a dangerous WMD and an instrument of deception, for both coders and traders. We will discuss:  • How to use our new `f_security()` function.  • The behavior of Pine code and security() on the three very different types of bars that make up any chart.  • Why what you see on a chart is a simulation, and should be taken with a grain of salt.  • Why we are presenting a new version of a function handling security() calls.  • Other topics of interest to coders using higher timeframe (HTF) data. █  WARNING We have tried to deliver a function that is simple to use and will, in non-repainting mode, produce reliable results for both experienced and novice coders. If you are a novice coder, stick to our recommendations to avoid getting into trouble, and DO NOT change our `f_security()` function when using it. Use `false` as the function's last argument and refrain from using your script at smaller timeframes than the chart's. To call our function to fetch a non-repainting value of close from the 1D timeframe, use: f_security(_sym, _res, _src, _rep) => security(_sym, _res, _src ) previousDayClose = f_security(syminfo.tickerid, "D", close, false) If that's all you're interested in, you are done. If you choose to ignore our recommendation and use the function in repainting mode by changing the `false` in there for `true`, we sincerely hope you read the rest of our ramblings before you do so, to understand the consequences of your choice. Let's now have a look at what security() is showing you. There is a lot to cover, so buckle up! But before we dig in, one last thing. What is a chart? A chart is a graphic representation of events that occur in markets. As any representation, it is not reality, but rather a model of reality. As Scott Page eloquently states in The Model Thinker : "All models are wrong; many are useful". Having in mind that both chart bars and plots on our charts are imperfect and incomplete renderings of what actually occurred in realtime markets puts us coders in a place from where we can better understand the nature of, and the causes underlying the inevitable compromises necessary to build the data series our code uses, and print chart bars. Traders or coders complaining that charts do not reflect reality act like someone who would complain that the word "dog" is not a real dog. Let's recognize that we are dealing with models here, and try to understand them the best we can. Sure, models can be improved; TradingView is constantly improving the quality of the information displayed on charts, but charts nevertheless remain mere translations. Plots of data fetched through security() being modelized renderings of what occurs at higher timeframes, coders will build more useful and reliable tools for both themselves and traders if they endeavor to perfect their understanding of the abstractions they are working with. We hope this publication helps you in this pursuit. █  FEATURES This script's "Inputs" tab has four settings:  • Repaint : Determines whether the functions will use their repainting or non-repainting mode.   Note that the setting will not affect the behavior of the yellow plot, as it always repaints.  • Source : The source fetched by the security() calls.  • Timeframe : The timeframe used for the security() calls. If it is lower than the chart's timeframe, a warning appears.  • Show timeframe reminder : Displays a reminder of the timeframe after the last bar. █  THE CHART The chart shows two different pieces of information and we want to discuss other topics in this section, so we will be covering:  A — The type of chart bars we are looking at, indicated by the colored band at the top.  B — The plots resulting of calling security() with the close price in different ways.  C — Points of interest on the chart. A — Chart bars The colored band at the top shows the three types of bars that any chart on a live market will print. It is critical for coders to understand the important distinctions between each type of bar:  1 — Gray : Historical bars, which are bars that were already closed when the script was run on them.  2 — Red : Elapsed realtime bars, i.e., realtime bars that have run their course and closed.    The state of script calculations showing on those bars is that of the last time they were made, when the realtime bar closed.  3 — Green : The realtime bar. Only the rightmost bar on the chart can be the realtime bar at any given time, and only when the chart's market is active. Refer to the Pine User Manual's Execution model page for a more detailed explanation of these types of bars. B — Plots The chart shows the result of letting our 5sec chart run for a few minutes with the following settings: "Repaint" = "On" (the default is "Off"), "Source" = `close` and "Timeframe" = 1min. The five lines plotted are the following. They have progressively thinner widths:  1 — Yellow : A normal, repainting security() call.  2 — Silver : Our recommended security() function.  3 — Fuchsia : Our recommended way of achieving the same result as our security() function, for cases when the source used is a function returning a tuple.  4 — White : The method we previously recommended in our MTF Selection Framework , which uses two distinct security() calls.  5 — Black : A lame attempt at fooling traders that MUST be avoided. All lines except the first one in yellow will vary depending on the "Repaint" setting in the script's inputs. The first plot does not change because, contrary to all other plots, it contains no conditional code to adapt to repainting/no-repainting modes; it is a simple security() call showing its default behavior. C — Points of interest on the chart Historical bars do not show actual repainting behavior To appreciate what a repainting security()  call will plot in realtime, one must look at the realtime bar and at elapsed realtime bars, the bars where the top line is green or red on the chart at the top of this page. There you can see how the plots go up and down, following the close value of each successive chart bar making up a single bar of the higher timeframe. You would see the same behavior in "Replay" mode. In the realtime bar, the movement of repainting plots will vary with the source you are fetching: open will not move after a new timeframe opens, low and high will change when a new low or high are found, close will follow the last feed update. If you are fetching a value calculated by a function, it may also change on each update. Now notice how different the plots are on historical bars. There, the plot shows the close of the previously completed timeframe for the whole duration of the current timeframe, until on its last bar the price updates to the current timeframe's close when it is confirmed (if the timeframe's last bar is missing, the plot will only update on the next timeframe's first bar). That last bar is the only one showing where the plot would end if that timeframe's bars had elapsed in realtime. If one doesn't understand this, one cannot properly visualize how his script will calculate in realtime when using repainting. Additionally, as published scripts typically show charts where the script has only run on historical bars, they are, in fact, misleading traders who will naturally assume the script will behave the same way on realtime bars. Non-repainting plots are more accurate on historical bars Now consider this chart, where we are using the same settings as on the chart used to publish this script, except that we have turned "Repainting" off this time: The yellow line here is our reference, repainting line, so although repainting is turned off, it is still repainting, as expected. Because repainting is now off, however, plots on historical bars show the previous timeframe's close until the first bar of a new timeframe, at which point the plot updates. This correctly reflects the behavior of the script in the realtime bar, where because we are offsetting the series by one, we are always showing the previously calculated—and thus confirmed—higher timeframe value. This means that in realtime, we will only get the previous timeframe's values one bar after the timeframe's last bar has elapsed, at the open of the first bar of a new timeframe. Historical and elapsed realtime bars will not actually show this nuance because they reflect the state of calculations made on their close , but we can see the plot update on that bar nonetheless. ► This more accurate representation on historical bars of what will happen in the realtime bar is one of the two key reasons why using non-repainting data is preferable.    The other is that in realtime, your script will be using more reliable data and behave more consistently. Misleading plots Valiant attempts by coders to show non-repainting, higher timeframe data updating earlier than on our chart are futile. If updates occur one bar earlier because coders use the repainting version of the function, then so be it, but they must then also accept that their historical bars are not displaying information that is as accurate. Not informing script users of this is to mislead them. Coders should also be aware that if they choose to use repainting data in realtime, they are sacrificing reliability to speed and may be running a strategy that behaves very differently from the one they backtested, thus invalidating their tests. When, however, coders make what are supposed to be non-repainting plots plot artificially early on historical bars, as in examples "c4" and "c5" of our script, they would want us to believe they have achieved the miracle of time travel. Our understanding of the current state of science dictates that for now, this is impossible. Using such techniques in scripts is plainly misleading, and public scripts using them will be moderated. We are coding trading tools here—not video games. Elementary ethics prescribe that we should not mislead traders, even if it means not being able to show sexy plots. As the great Feynman said: You should not fool the layman when you're talking as a scientist. You can readily appreciate the fantasy plot of "c4", the thinnest line in black, by comparing its supposedly non-repainting behavior between historical bars and realtime bars. After updating—by miracle—as early as the wide yellow line that is repainting, it suddenly moves in a more realistic place when the script is running in realtime, in synch with our non-repainting lines. The "c5" version does not plot on the chart, but it displays in the Data Window. It is even worse than "c4" in that it also updates magically early on historical bars, but goes on to evaluate like the repainting yellow line in realtime, except one bar late. Data Window The Data Window shows the values of the chart's plots, then the values of both the inside and outside offsets used in our calculations, so you can see them change bar by bar. Notice their differences between historical and elapsed realtime bars, and the realtime bar itself. If you do not know about the Data Window, have a look at this essential tool for Pine coders in the Pine User Manual's page on Debugging . The conditional expressions used to calculate the offsets may seem tortuous but their objective is quite simple. When repainting is on, we use this form, so with no offset on all bars: security(ticker, i_timeframe, i_source ) // which is equivalent to: security(ticker, i_timeframe, i_source) When repainting is off, we use two different and inverted offsets on historical bars and the realtime bar: // Historical bars: security(ticker, i_timeframe, i_source ) // Realtime bar (and thus, elapsed realtime bars): security(ticker, i_timeframe, i_source ) The offsets in the first line show how we prevent repainting on historical bars without the need for the `lookahead` parameter. We use the value of the function call on the chart's previous bar. Since values between the repainting and non-repainting versions only differ on the timeframe's last bar, we can use the previous value so that the update only occurs on the timeframe's first bar, as it will in realtime when not repainting. In the realtime bar, we use the second call, where the offsets are inverted. This is because if we used the first call in realtime, we would be fetching the value of the repainting function on the previous bar, so the close of the last bar. What we want, instead, is the data from the previous, higher timeframe bar , which has elapsed and is confirmed, and thus will not change throughout realtime bars, except on the first constituent chart bar belonging to a new higher timeframe. After the offsets, the Data Window shows values for the `barstate.*` variables we use in our calculations. █  NOTES Why are we revisiting security()  ? For four reasons:  1 — We were seeing coders misuse our `f_secureSecurity()` function presented in How to avoid repainting when using security() .    Some novice coders were modifying the offset used with the history-referencing operator in the function, making it zero instead of one,    which to our horror, caused look-ahead bias when used with `lookahead = barmerge.lookahead_on`.    We wanted to present a safer function which avoids introducing the dreaded "lookahead" in the scripts of unsuspecting coders.  2 — The popularity of security() in screener-type scripts where coders need to use the full 40 calls allowed per script made us want to propose    a solid method of allowing coders to offer a repainting/no-repainting choice to their script users with only one security() call.  3 — We wanted to explain why some alternatives we see circulating are inadequate and produce misleading behavior.  4 — Our previous publication on security() focused on how to avoid repainting, yet many other considerations worthy of attention are not related to repainting. Handling tuples When sending function calls that return tuples with security() , our `f_security()` function will not work because Pine does not allow us to use the history-referencing operator with tuple return values. The solution is to integrate the inside offset to your function's arguments, use it to offset the results the function is returning, and then add the outside offset in a reassignment of the tuple variables, after security() returns its values to the script, as we do in our "c2" example. Does it repaint? We're pretty sure Wilder was not asked very often if RSI repainted. Why? Because it wasn't in fashion—and largely unnecessary—to ask that sort of question in the 80's. Many traders back then used daily charts only, and indicator values were calculated at the day's close, so everybody knew what they were getting. Additionally, indicator values were calculated by generally reputable outfits or traders themselves, so data was pretty reliable. Today, almost anybody can write a simple indicator, and the programming languages used to write them are complex enough for some coders lacking the caution, know-how or ethics of the best professional coders, to get in over their heads and produce code that does not work the way they think it does. As we hope to have clearly demonstrated, traders do have legitimate cause to ask if MTF scripts repaint or not when authors do not specify it in their script's description. ► We recommend that authors always use our `f_security()` with `false` as the last argument to avoid repainting when fetching data dependent on OHLCV information. This is the only way to obtain reliable HTF data. If you want to offer users a choice, make non-repainting mode the default, so that if users choose repainting, it will be their responsibility. Non-repainting security() calls are also the only way for scripts to show historical behavior that matches the script's realtime behavior, so you are not misleading traders. Additionally, non-repainting HTF data is the only way that non-repainting alerts can be configured on MTF scripts, as users of MTF scripts cannot prevent their alerts from repainting by simply configuring them to trigger on the bar's close. Data feeds A chart at one timeframe is made up of multiple feeds that mesh seamlessly to form one chart. Historical bars can use one feed, and the realtime bar another, which brokers/exchanges can sometimes update retroactively so that elapsed realtime bars will reappear with very slight modifications when the browser's tab is refreshed. Intraday and daily chart prices also very often originate from different feeds supplied by brokers/exchanges. That is why security() calls at higher timeframes may be using a completely different feed than the chart, and explains why the daily high value, for example, can vary between timeframes. Volume information can also vary considerably between intraday and daily feeds in markets like stocks, because more volume information becomes available at the end of day. It is thus expected behavior—and not a bug—to see data variations between timeframes. Another point to keep in mind concerning feeds it that when you are using a repainting security() plot in realtime, you will sometimes see discrepancies between its plot and the realtime bars. An artefact revealing these inconsistencies can be seen when security() plots sometimes skip a realtime chart bar during periods of high market activity. This occurs because of races between the chart and the security() feeds, which are being monitored by independent, concurrent processes. A blue arrow on the chart indicates such an occurrence. This is another cause of repainting, where realtime bar-building logic can produce different outcomes on one closing price. It is also another argument supporting our recommendation to use non-repainting data. Alternatives There is an alternative to using security() in some conditions. If all you need are OHLC prices of a higher timeframe, you can use a technique like the one Duyck demonstrates in his security free MTF example - JD script. It has the great advantage of displaying actual repainting values on historical bars, which mimic the code's behavior in the realtime bar—or at least on elapsed realtime bars, contrary to a repainting security() plot. It has the disadvantage of using the current chart's TF data feed prices, whereas higher timeframe data feeds may contain different and more reliable prices when they are compiled at the end of the day. In its current state, it also does not allow for a repainting/no-repainting choice. When `lookahead` is useful When retrieving non-price data, or in special cases, for experiments, it can be useful to use `lookahead`. One example is our Backtesting on Non-Standard Charts: Caution! script where we are fetching prices of standard chart bars from non-standard charts. Warning users Normal use of security() dictates that it only be used at timeframes equal to or higher than the chart's. To prevent users from inadvertently using your script in contexts where it will not produce expected behavior, it is good practice to warn them when their chart is on a higher timeframe than the one in the script's "Timeframe" field. Our `f_tfReminderAndErrorCheck()` function in this script does that. It can also print a reminder of the higher timeframe. It uses one security() call. Intrabar timeframes security() is not supported by TradingView when used with timeframes lower than the chart's. While it is still possible to use security() at intrabar timeframes, it then behaves differently. If no care is taken to send a function specifically written to handle the successive intrabars, security() will return the value of the last intrabar in the chart's timeframe, so the last 1H bar in the current 1D bar, if called at "60" from a "D" chart timeframe. If you are an advanced coder, see our FAQ entry on the techniques involved in processing intrabar timeframes. Using intrabar timeframes comes with important limitations, which you must understand and explain to traders if you choose to make scripts using the technique available to others. Special care should also be taken to thoroughly test this type of script. Novice coders should refrain from getting involved in this. █  TERMINOLOGY Timeframe Timeframe , interval and resolution are all being used to name the concept of timeframe. We have, in the past, used "timeframe" and "resolution" more or less interchangeably. Recently, members from the Pine and PineCoders team have decided to settle on "timeframe", so from hereon we will be sticking to that term. Multi-timeframe (MTF) Some coders use "multi-timeframe" or "MTF" to name what are in fact "multi-period" calculations, as when they use MAs of progressively longer periods. We consider that a misleading use of "multi-timeframe", which should be reserved for code using calculations actually made from another timeframe's context and using security() , safe for scripts like Duyck's one mentioned earlier, or TradingView's Relative  Volume  at  Time , which use a user-selected timeframe as an anchor to reset calculations. Calculations made at the chart's timeframe by varying the period of MAs or other rolling window calculations should be called "multi-period", and "MTF-anchored" could be used for scripts that reset calculations on timeframe boundaries. Colophon Our script was written using the PineCoders Coding Conventions for Pine . The description was formatted using the techniques explained in the How We Write and Format Script Descriptions PineCoders publication. Snippets were lifted from our MTF Selection Framework , then massaged to create the `f_tfReminderAndErrorCheck()` function. █  THANKS Thanks to apozdnyakov for his help with the innards of security() . Thanks to bmistiaen for proofreading our description. Look first. Then leap.
Penunjuk Pine Script®
oleh PineCoders
60
Adaptive Fibonacci Pullback System -FibonacciFluxAdaptive Fibonacci Pullback System (AFPS) - FibonacciFlux This work is licensed under a Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). Original concepts by FibonacciFlux. Abstract The Adaptive Fibonacci Pullback System (AFPS) presents a sophisticated, institutional-grade algorithmic strategy engineered for high-probability trend pullback entries. Developed by FibonacciFlux, AFPS uniquely integrates a proprietary Multi-Fibonacci Supertrend engine (0.618, 1.618, 2.618 ratios) for harmonic volatility assessment, an Adaptive Moving Average (AMA) Channel providing dynamic market context, and a synergistic Multi-Timeframe (MTF) filter suite (RSI, MACD, Volume). This strategy transcends simple indicator combinations through its strict, multi-stage confluence validation logic. Historical simulations suggest that specific MTF filter configurations can yield exceptional performance metrics, potentially achieving Profit Factors exceeding 2.6 , indicative of institutional-level potential, while maintaining controlled risk under realistic trading parameters (managed equity risk, commission, slippage). 4 hourly MTF filtering 1. Introduction: Elevating Pullback Trading with Adaptive Confluence Traditional pullback strategies often struggle with noise, false signals, and adapting to changing market dynamics. AFPS addresses these challenges by introducing a novel framework grounded in Fibonacci principles and adaptive logic. Instead of relying on static levels or single confirmations, AFPS seeks high-probability pullback entries within established trends by validating signals through a rigorous confluence of: Harmonic Volatility Context: Understanding the trend's stability and potential turning points using the unique Multi-Fibonacci Supertrend. Adaptive Market Structure: Assessing the prevailing trend regime via the AMA Channel. Multi-Dimensional Confirmation: Filtering signals with lower-timeframe Momentum (RSI), Trend Alignment (MACD), and Market Conviction (Volume) using the MTF suite. The objective is to achieve superior signal quality and adaptability, moving beyond conventional pullback methodologies. 2. Core Methodology: Synergistic Integration AFPS's effectiveness stems from the engineered synergy between its core components: 2.1. Multi-Fibonacci Supertrend Engine: Utilizes specific Fibonacci ratios (0.618, 1.618, 2.618) applied to ATR, creating a multi-layered volatility envelope potentially resonant with market harmonics. The averaged and EMA-smoothed result (`smoothed_supertrend`) provides a robust, dynamic trend baseline and context filter. // Key Components: Multi-Fibonacci Supertrend & Smoothing average_supertrend = (supertrend1 + supertrend2 + supertrend3) / 3 smoothed_supertrend = ta.ema(average_supertrend, st_smooth_length) 2.2. Adaptive Moving Average (AMA) Channel: Provides dynamic market context. The `ama_midline` serves as a key filter in the entry logic, confirming the broader trend bias relative to adaptive price action. Extended Fibonacci levels derived from the channel width offer potential dynamic S/R zones. // Key Component: AMA Midline ama_midline = (ama_high_band + ama_low_band) / 2 2.3. Multi-Timeframe (MTF) Filter Suite: An optional but powerful validation layer (RSI, MACD, Volume) assessed on a lower timeframe. Acts as a **validation cascade** – signals must pass all enabled filters simultaneously. 2.4. High-Confluence Entry Logic: The core innovation. A pullback entry requires a specific sequence and validation: Price interaction with `average_supertrend` and recovery above/below `smoothed_supertrend`. Price confirmation relative to the `ama_midline`. Simultaneous validation by all enabled MTF filters. // Simplified Long Entry Logic Example (incorporates key elements) long_entry_condition = enable_long_positions and (low < average_supertrend and close > smoothed_supertrend) and // Pullback & Recovery (close > ama_midline and close > ama_midline) and // AMA Confirmation (rsi_filter_long_ok and macd_filter_long_ok and volume_filter_ok) // MTF Validation This strict, multi-stage confluence significantly elevates signal quality compared to simpler pullback approaches. 1hourly filtering 3. Realistic Implementation and Performance Potential AFPS is designed for practical application, incorporating realistic defaults and highlighting performance potential with crucial context: 3.1. Realistic Default Strategy Settings: The script includes responsible default parameters: strategy('Adaptive Fibonacci Pullback System - FibonacciFlux', shorttitle = "AFPS", ..., initial_capital = 10000, // Accessible capital default_qty_type = strategy.percent_of_equity, // Equity-based risk default_qty_value = 4, // Default 4% equity risk per initial trade commission_type = strategy.commission.percent, commission_value = 0.03, // Realistic commission slippage = 2, // Realistic slippage pyramiding = 2 // Limited pyramiding allowed ) Note: The default 4% risk (`default_qty_value = 4`) requires careful user assessment and adjustment based on individual risk tolerance. 3.2. Historical Performance Insights & Institutional Potential: Backtesting provides insights into historical behavior under specific conditions (always specify Asset/Timeframe/Dates when sharing results): Default Performance Example: With defaults, historical tests might show characteristics like Overall PF ~1.38, Max DD ~1.16%, with potential Long/Short performance variance (e.g., Long PF 1.6+, Short PF < 1). Optimized MTF Filter Performance: Crucially, historical simulations demonstrate that meticulous configuration of the MTF filters (particularly RSI and potentially others depending on market) can significantly enhance performance. Under specific, optimized MTF filter settings combined with appropriate risk management (e.g., 7.5% risk), historical tests have indicated the potential to achieve **Profit Factors exceeding 2.6**, alongside controlled drawdowns (e.g., ~1.32%). This level of performance, if consistently achievable (which requires ongoing adaptation), aligns with metrics often sought in institutional trading environments. Disclaimer Reminder: These results are strictly historical simulations. Past performance does not guarantee future results. Achieving high performance requires careful parameter tuning, adaptation to changing markets, and robust risk management. 3.3. Emphasizing Risk Management: Effective use of AFPS mandates active risk management. Utilize the built-in Stop Loss, Take Profit, and Trailing Stop features. The `pyramiding = 2` setting requires particularly diligent oversight. Do not rely solely on default settings. 4. Conclusion: Advancing Trend Pullback Strategies The Adaptive Fibonacci Pullback System (AFPS) offers a sophisticated, theoretically grounded, and highly adaptable framework for identifying and executing high-probability trend pullback trades. Its unique blend of Fibonacci resonance, adaptive context, and multi-dimensional MTF filtering represents a significant advancement over conventional methods. While requiring thoughtful implementation and risk management, AFPS provides discerning traders with a powerful tool potentially capable of achieving institutional-level performance characteristics under optimized conditions. Acknowledgments Developed by FibonacciFlux. Inspired by principles of Fibonacci analysis, adaptive averaging, and multi-timeframe confirmation techniques explored within the trading community. Disclaimer Trading involves substantial risk. AFPS is an analytical tool, not a guarantee of profit. Past performance is not indicative of future results. Market conditions change. Users are solely responsible for their decisions and risk management. Thorough testing is essential. Deploy at your own considered risk.
Strategi Pine Script®
oleh FibonacciFlux
Multi Timeframe Relative Strength Index {DCAquant}Overview The Multi Timeframe Relative Strength Index (MTF RSI) is a powerful technical analysis tool designed to provide insights into market momentum and potential trend reversals across multiple timeframes. Leveraging the Relative Strength Index (RSI) formula, this indicator offers traders a comprehensive view of market sentiment and identifies overbought and oversold conditions. Key Features RSI Calculation: Utilizes the standard RSI calculation formula to measure the magnitude of recent price changes and assess the strength of market trends. Employs a user-defined length parameter to customize the sensitivity of the RSI calculation based on trading preferences. Multiple Timeframe Analysis: Allows traders to analyze RSI values across up to six different timeframes, ranging from minutes to days, providing a holistic perspective on market dynamics. Calculates RSI values independently for each selected timeframe, enabling comparison and trend identification. Threshold Levels: Defines overbought and oversold levels to highlight potential reversal points in market trends. Offers flexibility in adjusting threshold levels based on individual risk tolerance and trading strategies. Neutral Zone: Establishes upper and lower neutral thresholds to identify periods of consolidation or sideways movement in price. Helps traders distinguish between trending and ranging market conditions for more accurate analysis. Moving Average Smoothing: Provides the option to apply moving average smoothing to aggregated RSI values for enhanced clarity and reduced noise. Enables smoother visualization of RSI trends, facilitating easier interpretation for traders. Visual Representation: Plots the aggregated MTF RSI values on the price chart, allowing traders to visually assess market momentum and potential reversal points. Utilizes color-coded backgrounds to indicate Long, Short, or Neutral conditions for quick identification. Dynamic Table Display: Displays trading signals alongside graphical indicators (rocket for Long, snowflake for Short, and star for Neutral) in a customizable table format. Offers flexibility in table placement and size to accommodate user preferences. How to Use: Parameter Configuration: Adjust the length parameter to fine-tune the sensitivity of the RSI calculation based on the desired timeframe and trading strategy. Define overbought and oversold levels to identify potential reversal points in market trends. Customize upper and lower neutral thresholds to differentiate between trending and ranging market conditions. Interpretation: Monitor the aggregated MTF RSI values plotted on the price chart for signals of overbought or oversold conditions. Pay attention to color-coded backgrounds and graphical indicators in the table for actionable trading insights. Trading Strategy: Consider entering Long positions when the aggregated MTF RSI is above the upper neutral threshold, indicating potential bullish momentum. Evaluate Short opportunities when the aggregated MTF RSI falls below the lower neutral threshold, signaling possible bearish momentum. Exercise caution during Neutral conditions, as there may be uncertainty in market direction. Risk Management: Combine MTF RSI analysis with robust risk management strategies, including stop-loss and take-profit levels, to manage trading risks effectively. Practice prudent risk management and trade within your risk tolerance to minimize potential losses. Disclaimer Trading in financial markets involves risk, and past performance is not indicative of future results. The use of the MTF RSI indicator does not guarantee profits or prevent losses. Traders should conduct their own analysis, exercise caution, and seek advice from qualified financial professionals before making trading decisions.
Penunjuk Pine Script®
oleh DCAquant
Fair Value Gap█ OVERVIEW This indicator displays the Fair Value Gap of the current timeframe and an additional higher timeframe. For each FVG the gaps act as targets creating bullish and bearish gaps that are often filled. █ FEATURES MTF Options MidPoint FIll Delete Old On Fill Label FVG Timeframe MTF Options Enabling the MTF Options will allow the user to use the "MTF Timeframe" setting to choose what HTF Fair Value Gap to display MidPoint FIll A line plot at the Half way point will be included in the Fair Value Gap, this will be used to delete the gap when reached instead of a full fill. Delete Old On Fill Deletes historical Fair Value Gaps when filled. Label FVG Timeframe Labels Every Fair Value gap with there relevant timeframe to make it easier to determine which gap is being filled. █ HOW TO USE IT The indicator is quite straight forward in its application, providing users with targets that are often filled as they are seen as market imbalance. Just applying it to your chart will provide the existing Fair Value Gaps. MTF Confluence is helpful in seeing what is happening on the macro perspective. █ SUGGESTION My suggestion for clarity is to use a different color to some degree between the MTF and Current TF as Opposed to text, keeps the chart clear. █ LIMITATIONS OF PINE (Please read) I see many users going on different indicators with MTF in mind and trying to use it for LTF data e.g. 1hour chart, and selecting 5min in chart settings. This is not recommended by the team themselves and should be noted for use always use HTF: www.tradingview.com To understand how to use fair value gaps I recommend learning about the subject some more, searching online will provide you resources. The internet is your friend when learning. All the best.
Penunjuk Pine Script®
oleh spacemanbtc
101
Multi SMA EMA WMA HMA BB (5+5 MAs + Bollinger Bands) by RRB Multi SMA EMA WMA HMA BB (5+5 Moving Averages of Any Type with Bollinger Bands) by RagingRocketBull 2018 Version 1.0 This indicator shows multiple MAs of any type (SMA EMA WMA HMA etc) with BB on a chart at the same time with/without MTF support depending on the version. There are several versions (published later): Simple, MTF, Pro MTF and Ultimate MTF. This is the Simple 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: +assign 1 custom Timeframe to any group combo (5+5 Custom TF) - Pro MTF: +multiple Timeframes for multiple MA groups (4*3 MTF), horizontal levels and show max bars back options - Ultimate MTF: +individual settings for each MA, multiple Timeframes You can use different types of MAs as dynamic S/R levels to trade of off and MA crosses as signals for possible trend change (golden/death bull/bear crosses). Most common MA types are: SMA, EMA, WMA, HMA. Most common MA lengths are: 12, 20, 26, 30, 50, 100, 200, 400 etc. Features: - 2 groups of custom 5+5 MAs of any type including Hull Moving Average (HMA) - BB 1. based on 3EmaBB, uses plot, fill, stdev and custom hma functions 2. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params Feel free to use. Good Luck!
Penunjuk Pine Script®
oleh RagingRocketBull
12
Multi Timeframe Moving Average Convergence Divergence {DCAquant}Overview The MTF MACD indicator provides a unique view of MACD (Moving Average Convergence Divergence) and Signal Line dynamics across various timeframes. It calculates the MACD and Signal Line for each selected timeframe and aggregates them for analysis. Key Features MACD Calculation Utilizes standard MACD calculations based on user-defined parameters like fast length, slow length, and signal smoothing. Determines the difference between the MACD and Signal Line to identify convergence or divergence. Multiple Timeframe Analysis Allows users to select up to six different timeframes for analysis, ranging from minutes to days, providing a holistic view of market trends. Calculates MACD and Signal Line for each timeframe independently. Aggregated Analysis Combines MACD and Signal Line values from multiple timeframes to derive a consolidated view. Optionally applies moving average smoothing to aggregated MACD and Signal Line values for better clarity. Position Identification Determines the trading position (Long, Short, or Neutral) based on the relationship between MACD and Signal Line. Considers the proximity of MACD and Signal Line to identify potential trading opportunities. Visual Representation Plots MACD and Signal Line on the price chart for visual analysis. Utilizes color-coded backgrounds to indicate trading conditions (Long, Short, or Neutral) for quick interpretation. Dynamic Table Display Displays trading position alongside graphical indicators (rocket for Long, snowflake for Short, and star for Neutral) in a customizable table. Offers flexibility in table placement and size for user preference. How to Use Parameter Configuration Adjust parameters like fast length, slow length, and signal smoothing to fine-tune MACD calculations. Select desired timeframes for analysis based on trading preferences and market conditions. Interpretation Monitor the relationship between MACD and Signal Line on the price chart. Pay attention to color-coded backgrounds and graphical indicators in the table for actionable insights. Decision Making Consider entering Long positions when MACD is above the Signal Line and vice versa for Short positions. Exercise caution during Neutral conditions, as there may be uncertainty in market direction. Risk Management Combine MTF MACD analysis with risk management strategies to optimize trade entries and exits. Set stop-loss and take-profit levels based on individual risk tolerance and market conditions. Conclusion The Multi Timeframe Moving Average Convergence Divergence (MTF MACD) indicator offers a robust framework for traders to analyze market trends across multiple timeframes efficiently. By combining MACD insights from various time horizons and presenting them in a clear and actionable format, it empowers traders to make informed decisions and enhance their trading strategies. Disclaimer The Multi Timeframe Moving Average Convergence Divergence (MTF MACD) indicator provided here is intended for educational and informational purposes only. Trading in financial markets involves risk, and past performance is not indicative of future results. The use of this indicator does not guarantee profits or prevent losses. Please be aware that trading decisions should be made based on your own analysis, risk tolerance, and financial situation. It is essential to conduct thorough research and seek advice from qualified financial professionals before engaging in any trading activity. The MTF MACD indicator is a tool designed to assist traders in analyzing market trends and identifying potential trading opportunities. However, it is not a substitute for sound judgment and prudent risk management. By using this indicator, you acknowledge that you are solely responsible for your trading decisions, and you agree to indemnify and hold harmless the developer and distributor of this indicator from any losses, damages, or liabilities arising from its use. Trading in financial markets carries inherent risks, and you should only trade with capital that you can afford to lose. Exercise caution and discretion when implementing trading strategies, and consider seeking independent financial advice if necessary.
Penunjuk Pine Script®
oleh DCAquant
1
CM MACD Custom Indicator - Multiple Time Frame - V2***For a Detailed Video Overview Showing all of the Settings... Click HERE to View Video New _CM_MacD_Ult_MTF _V2 Update 07-28-2021 Thanks to @SKTennis for help in Updating code to V2 Added Groups to Settings Pane. Added Color Plots to Settings Pane Switched MTF Logic to turn ON/OFF automatically w/ TradingView's Built in Feature Updated Color Transparency plots to work in future update Added Ability to Turn ON/OFF Show MacD & Signal Line Added Ability to Turn ON/OFF Show Histogram Added Ability to Change MACD Line Colors Based on Trend Added Ability to Highlight Price Bars Based on Trend Added Alerts to Settings Pane. Customized how Alerts work. Must keep Checked in Settings Pane, and When you go to Alerts Panel, Change Symbol to Indicator (CM_Ult_MacD_MTF_V2) Customized Alerts to Show Symbol, TimeFrame, Closing Price, MACD Crosses Up & MACD Crosses Down Signals in Alert Alerts are Pre-Set to only Alert on Bar Close See Video for Detailed Overview New Updates Coming Soon!!! ***Please Post Feedback and Any Feature Requests in the Comments Section Below***
Penunjuk Pine Script®
oleh ChrisMoody
145
Supertrend + MACD with Advanced FiltersDetailed Guide 1. Indicator Overview Purpose: This enhanced indicator combines Supertrend and MACD to signal potential trend changes. In addition, it now includes several extra filters for more reliable signals: Multi-Timeframe (MTF) Confirmation: Checks a higher timeframe’s trend. ADX (Momentum) Filter: Ensures the market is trending strongly. Dynamic Factor Adjustment: Adapts the Supertrend sensitivity to current volatility. Volume Filter: Verifies that current volume is above average. Each filter can be enabled or disabled according to your preference. How It Works: The Supertrend calculates dynamic support/resistance levels based on ATR and an adjustable factor, while MACD identifies momentum shifts via its crossovers. The additional filters then confirm whether the conditions meet your criteria for a trend change. If all enabled filters align, the indicator plots a shape and triggers an alert. 2. Supertrend Component with Dynamic Factor Base Factor & ATR Period: The Supertrend uses these inputs to compute its dynamic bands. Dynamic Factor Toggle: When enabled, the factor is adjusted by comparing the current ATR to its simple moving average. This makes the indicator adapt to higher or lower volatility conditions, helping to reduce false signals. 3. MACD Component Parameters: Standard MACD settings (Fast MA, Slow MA, Signal Smoothing) determine the responsiveness of the MACD line. Crossovers between the MACD line and its signal line indicate potential trend reversals. 4. Multi-Timeframe (MTF) Filter Function: If enabled, the indicator uses a higher timeframe’s simple moving average (SMA) to confirm the prevailing trend. Bullish Confirmation: The current close is above the higher timeframe SMA. Bearish Confirmation: The current close is below the higher timeframe SMA. 5. ADX Filter (Momentum) Custom Calculation: Since the built-in ta.adx function may not be available, a custom ADX is calculated. This involves: Determining positive and negative directional movements (DMs). Smoothing these values to obtain +DI and -DI. Calculating the DX and then smoothing it to yield the ADX. Threshold: Only signals where the ADX exceeds the set threshold (default 20) are considered valid, ensuring that the market is trending strongly enough. 6. Volume Filter Function: Checks if the current volume exceeds the average volume (SMA) multiplied by a specified factor. This helps confirm that a price move is supported by sufficient trading activity. 7. Combined Signal Logic & Alerts Final Signal: A bullish signal is generated when: MACD shows a bullish crossover, Supertrend indicates an uptrend, And all enabled filters (MTF, ADX, volume) confirm the signal. The bearish signal is generated similarly in the opposite direction. Alerts: Alert conditions are set so that TradingView can notify you via pop-up, email, or SMS when these combined conditions are met. 8. User Adjustments Toggle Filters: Use the on/off switches for MTF, ADX, and Volume filters as needed. Parameter Tuning: Adjust the ATR period, base factor, higher timeframe settings, ADX period/threshold, and volume multiplier to match your trading style and market conditions. Backtesting: Always backtest your settings to ensure that they perform well with your strategy.
Penunjuk Pine Script®
oleh kiemonline2016