Black FridayUp to 80% OFF

Search in scripts for "mtf"

MTF Trailing SL Strategy [QuantNomad]This is a Multi-Timeframe version of my Trailing SL Strategy. Few weeks ago I published Trailing SL Strategy. There I used only basic Trailing SL to enter positions. It worked pretty well so I tried to work on it a bit. I thought what if you can use the same ATR TSL on different timeframes and combine them into one signal. In this strategy you can use only ATR stops and choose 3 other higher timeframes in addition to your current timeframe. You'll see Trailing SL plotted on the chart form all these timeframes. Entry Long position if all 4 time-frames agree on long signal. Exit Long positions when at least 2 time-frames disagree on long signal. Entry to Short position if all 4 time-frames agree on Short signal. Exit from Short positions when at least 2 time-frames disagree on Short signal. Here is the link to my basic Trailing SL Strategy:
Pine Script® strategy
by QuantNomad
45
MTF Selection Framework - PineCoders FAQOur MTF Selection Framework allows Pine coders to add multi-timeframe capabilities to their script with the following features: ► Timeframe selection The higher timeframe can be selected using 3 different ways: • By steps (60 min., 1D, 3D, 1W, 1M, 1Y). • As a multiple of the current chart's resolution, which can be fractional, so 3.5 will work. • Fixed. ► Non-repainting or Repainting mode can be selected. ► Smoothing of the HTF line Can be turned on/off and a smoothing factor allows the user to select the degree of smoothing he requires. The framework is used here to create a higher timeframe version of a simple RSI line, but it can be used to access HTF information for almost any signal. Functions used f_resInMinutes() Converts the current timeframe.multiplier plus the TF into minutes of type float. • In Pine, the timeframe.multiplier is an integer representing the resolution, but a value of 1 can mean one day or one minute. This function converts that information in a standard fractional float minutes format that can then be used by the other functions in the framework. • If the chart's current resolution is 15 seconds, the function will return 0.25 . If the chart's resolution is one day, it will return 1440 . f_tfResInMinutes(_resolution) Returns resolution of _resolution period in minutes. • This function does the same as f_resInMinutes() , but on the target resolution supplied as a parameter in the timeframe.period string format. f_resNextStep(_res) Given a current resolution in fractional float minutes, returns its corresponding stepped HTF in the timeframe.period string format. • This allows the implementation of the step HTF selection mode. f_multipleOfRes(_res, _mult) Given a current resolution in fractional float minutes and a fractional multiplier, returns a multiple of the resolution as a string in "timeframe.period" format usable with "security()". • A multiple like 3.5 is allowed. • Note that with seconds resolutions, the result returned is constrained by the discrete seconds resolutions available on TV. f_htfLabel(_txt, _y, _color) Used to display a label showing either: • A warning when the chart's resolution is not lower than the HTF. • The HTF resolution currently used. The y position used to position the label will require adaptation to the signal you are using. For use in "overlay = true" mode, a technique that works well is commented out in the code. Look first. Then leap.
Pine Script® indicator
by PineCoders
24
[RichG] Easy MTF Strategy v1.1This is a second attempt at an easy to understand multiple time frame strategy. This one uses ATR for exits. If the position is long, and the price closes below the ATR multiplier, it triggers a close. If the position is short, and the price closes above the ATR/multiplier, it triggers a close. This generates a lot of little trades but is useful because it uses multiple time frames along with cutting losses when the ATR disagrees.
Pine Script® strategy
by RichGTastyTrader
7
MTF MACD 2 By YuthavithiIf you want a good strategy without repaint. This one might be for you. Excellent profitable for BTCUSD3M for OKCoin. It uses multiple time frame MACD for trading decision. To avoid repaint, set the delay period = 1 for both long term and midterm. The idea is that, if long term, mid term and current time frame all agree on traidng direction, the trade will take place. I also uses it in my automated trading bot with good result. www.tradingview.com
Pine Script® strategy
by yongyuth.rootwararit
8
Smart RSI MTF [DotGain]Summary Are you tired of constantly switching between timeframes to check the RSI, only to miss the bigger picture? The Smart RSI MTF (Multi-Timeframe) is designed to solve this exact problem. It is a streamlined chart overlay that monitors RSI conditions across up to 10 different timeframes simultaneously —from the 1-minute chart all the way up to the Monthly view. This indicator removes the need for multiple open tabs and declutters your analysis by plotting signals directly on your main chart using a smart "visual hierarchy" system based on transparency. ⚙️ Core Components and Logic The Smart RSI MTF relies on a sophisticated 3-layer logic to deliver clear, actionable context: Multi-Timeframe Engine: The script runs 10 independent RSI calculations in the background. It checks standard intervals (5m, 15m, 1h, 4h, Daily, Weekly, Monthly) to ensure you never miss a momentum extreme on any scale. Classic RSI Thresholds: Overbought (> 70): Indicates price may be extended to the upside. Oversold (< 30): Indicates price may be extended to the downside. Smart Visibility System (The "Secret Sauce"): Not all signals are equal. A 5-minute Overbought signal is "noise" compared to a Weekly Overbought signal. This indicator automatically applies Transparency to differentiate importance: Minutes = High Transparency (Faint). Hours = Medium Transparency. Days/Weeks/Months = No Transparency (Solid/Bold). 🚦 How to Read the Indicator The indicator plots shapes (Labels by default) directly above or below the candles. The appearance tells you the direction and the timeframe significance: 🟥 RED SIGNALS (Overbought Condition) Trigger: RSI is above 70 on a specific timeframe. Location: Placed above the candle bar. Meaning: Potential bearish reversal or pullback. 🟩 GREEN SIGNALS (Oversold Condition) Trigger: RSI is below 30 on a specific timeframe. Location: Placed below the candle bar. Meaning: Potential bullish reversal or bounce. 👻 TRANSPARENCY (Signal Strength) Faint/Ghostly: The signal comes from a lower timeframe (e.g., 5m, 15m). Use for scalping or entry timing. Solid/Bright: The signal comes from a major timeframe (e.g., Daily, Weekly). Use for swing trading and identifying major market turns. Visual Elements Symbol Shapes: Fully customizable (Label, Diamond, Circle, Triangle, etc.) via settings. Stacking: If multiple timeframes trigger at once, symbols will overlay, creating a visually denser and darker color, indicating Confluence . Key Benefit The goal of the Smart RSI MTF is to help traders instantly spot Confluence . When you see a faint short-term signal align with a solid long-term signal, you have identified a high-probability reversal zone without leaving your chart. Have fun :) Disclaimer This "Smart RSI MTF" indicator is provided for informational and educational purposes only. It does not, and should not be construed as, financial, investment, or trading advice. The signals generated by this tool (both "Buy" and "Sell" indications) are the result of a specific set of algorithmic conditions. They are not a direct recommendation to buy or sell any asset. All trading and investing in financial markets involves substantial risk of loss. You can lose all of your invested capital. Past performance is not indicative of future results. The signals generated may produce false or losing trades. The creator (© DotGain) assumes no liability for any financial losses or damages you may incur as a result of using this indicator. You are solely responsible for your own trading and investment decisions. Always conduct your own research (DYOR) and consider your personal risk tolerance before making any trades.
Pine Script® indicator
by DotGain
[CT] Kurutoga MTF HistogramWhat is Kurutoga MTF Histogram? The Kurutoga MTF Histogram is a multi-time-frame momentum and mean-deviation tool. It measures how far the current close is trading away from a rolling midpoint of price and then displays that deviation as a color-coded histogram. Instead of looking only at one lookback, this version plots three Kurutoga “leads” at the same time: Kurutoga Lead (x1) – base length Kurutoga Lead 2x – slower, 2 × base length Kurutoga Lead 4x – slowest, 4 × base length Each lead is calculated both on the chart’s timeframe (LTF) and on a Higher Time Frame (HTF) of your choice, so you can see short-term deviation inside a higher-time-frame structure. 4-color Kurutoga scheme Each Kurutoga lead uses a 4-color MACD-style scheme: For a given lead: Up Light – divergence ≥ 0 and rising compared to the previous bar Up Dark – divergence ≥ 0 and falling (positive but losing momentum) Down Light – divergence < 0 and falling (bearish momentum increasing) Down Dark – divergence < 0 and rising (negative but contracting) By default the same four teal / red hues are shared across x1, x2, and x4. The only difference between the leads is transparency: x1 = strongest (least transparent) x2 = medium opacity x4 = faintest This lets you see all three layers at once without the chart becoming a solid block of color. The HTF areas use the same palette but with an extra transparency offset applied, so they appear as soft background bands rather than competing with the histograms. Inputs and how to use them 1. Base Length Defines the lookback for the main Kurutoga Lead. The script automatically creates: len1 = baseLength len2 = baseLength × 2 len3 = baseLength × 4 Smaller base lengths → faster, more reactive histograms. Larger base lengths → smoother, trend-focused behavior. 2. Higher Time Frame This is the HTF used for the area plots and HTF midpoints. Examples: 5-minute chart with HTF = 30 or 60 minutes 15-minute chart with HTF = 4H or 1D The idea is to trade on the lower timeframe while seeing how far price is stretched relative to a higher-time-frame range midpoint. 3. Show / Hide toggles Under “Show / Hide” you can independently turn on/off: Kurutoga Lead (x1) Kurutoga Lead 2x Kurutoga Lead 4x HTF Lead, HTF Lead 2x, HTF Lead 4x This lets you: Run only a single Kurutoga if you want a clean panel, or Stack multiple leads for a “multi-speed” view of extension and mean reversion. 4. Color Scheme (4-color Kurutoga) Up Light / Up Dark / Down Light / Down Dark – base hues used for every lead. Lead opacity (x1, 2x, 4x) – sets how strong or faint each lead appears. x1 is usually your primary “trading speed.” x2 and x4 can be faded so they act as context. Extra transparency for HTF areas – additional opacity applied on top of each lead’s opacity when drawing HTF areas. This keeps the HTF layer subtle. You can fine-tune the exact teal/red values here to match your personal palette. Practical reading & trade ideas Trend alignment When all three Kurutoga leads (x1, 2x, 4x) are above zero, price is trading above its rolling mid-range on multiple speeds → bullish environment. When all three are below zero, you have a multi-speed bearish environment. Mixed readings (e.g., x1 above zero, x4 below zero) can signal transition or mean-reversion areas. Momentum vs exhaustion Up Light / Down Light (light colors) show momentum expanding in that direction. Up Dark / Down Dark (dark colors) show momentum contracting – price still on that side of zero, but the push is weakening. After a run of Up Light bars, a shift to Up Dark may hint at a stall or pullback. After a run of Down Light bars, a shift to Down Dark may hint at short covering / bounce potential. Multi-time-frame confluence Use the HTF areas as a backdrop: If LTF Kurutoga leads are above zero while the HTF area is also positive (and ideally expanding), that’s strong bullish alignment. If LTF leads are trying to flip up while HTF divergence is still deeply negative, you may be looking at a counter-trend bounce rather than a true trend change. Example setups Trend-following entries: Look for x2 & x4 leads on the same side of zero as the HTF area, then use x1 color shifts (from Down Dark → Up Light or vice versa) to fine-tune entries in the direction of that higher-time-frame bias. Mean-reversion fades: Watch for extreme Kurutoga values where x1/x2 are strongly extended beyond zero while color flips from Light to Dark (momentum stalling) against an opposing HTF backdrop . Notes The indicator is non-directional by itself – it measures distance from a rolling midpoint rather than trend structure or order flow. It works best when combined with your existing price action/trend tools (moving averages, HLBO, structure zones, etc.). Because HTF values are brought down via request.security, choose HTF settings that make sense for your product and session (for example, don’t use very high HTFs on thin intraday markets). Use the Kurutoga MTF Histogram as a visual scanner for extension, momentum regime, and multi-speed alignment, then layer your own entry/exit rules on top.
Pine Script® indicator
by ChaosTrader63
Multi SMA EMA WMA HMA BB (4x3 MAs Bollinger Bands) Pro MTF - RRBMulti SMA EMA WMA HMA 4x3 Moving Averages with Bollinger Bands Pro MTF by RagingRocketBull 2018 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. You can assign any type/timeframe combo to a group, for example: - EMAs 50,100,200 x H1, H4, D1, W1 (4 TFs x 3 MAs x 1 type) - EMAs 8,13,21,55,100,200 x M15, H1 (2 TFs x 6 MAs x 1 type) - D1 EMAs and SMAs 12,26,50,100,200,400 (1 TF x 6 MAs x 2 types) - H1 WMAs 7,77,231; H4 HMAs 50,100,200; D1 EMAs 144,169,233; W1 SMAs 50,100,200 (4 TFs x 3 MAs x 4 types) - +1 extra MA type/timeframe for BB compile time: 25-30 sec full redraw time after parameter change in UI: 3 sec There are several versions: Simple, MTF, Pro MTF, Advanced MTF and Ultimate MTF. This is the Pro 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) - Pro MTF: +4 custom Timeframes for each group (4x3 MTF), MA levels and show max bars back options - Advanced MTF: +2 extra MAs/group (4x5 MTF), custom Ticker/Symbol, backreferences for type, TF and MA lengths in UI - Ultimate MTF: +individual settings for each MA, custom Ticker/Symbols Features: - 4x3 = 12 MAs of any type including Hull Moving Average (HMA) - 4x MTF groups with step line smoothing - BB +1 extra TF/type for BB MAs - 12 MA levels with adjustable group offsets, indents and shift - show max bars back - you can show/hide both groups of MAs/levels and individual MAs Notes: 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. uses timeframe textbox instead of input resolution to allow for 120 240 and other custom TFs. Also supports TFs in hours: 2H or H2 6. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params 7. Smoothing is applied by default for visual aesthetics on MTF. To use exact ma mtf values (lines with stair stepping) - disable it MTF Notes: - uses simple timeframe textbox instead of input resolution dropdown to allow for 120, 240 and other custom TFs, also supports timeframes in H: 2H, H2 - Groups that are not assigned a Custom TF will use Current Timeframe (0). - MTF will work for any MA type assigned to the group - MTF works both ways: you can display a higher TF MA/BB on a lower TF or a lower TF MA/BB on a higher TF. - MTF MA values are normally aligned at the boundary of their native timeframe. This produces stair stepping when a higher TF MA is viewed on a lower TF. Therefore X Y Point Density/Smoothing is applied by default on MA MTF for visual aesthetics. Set both to 0 to disable and see exact ma mtf values (lines with stair stepping and original mtf alignment). - Smoothing is disabled for BB MTF bands because fill doesn't work with smoothed MAs after duplicate values are replaced with na. - MTF MA Value fluctuation is possible on the current bar due to default security lookahead Smoothing: - X,Y == 0 - X,Y smoothing disabled (stair stepping on high TFs) - X == 0, Y > 0 - X,Y smoothing applied to all TFs - Y == 0, X > 0 - X smoothing applied to all TFs < deltaX_max_tf, Y smoothing disabled - X > 0, Y > 0 - Y smoothing applied to all TFs, then X smoothing applied to all TFs < deltaX_max_tf X Smoothing with Y == 0 - shows only every deltaX-th point starting from the first bar. X Smoothing with Y > 0 - shows only every deltaX-th point starting from the last shown Y point, essentially filling huge gaps remaining after Y Smoothing with points and preserving the curve's general shape X Smoothing on high TFs with already scarce points produces weird curve shapes, it works best only on high density lower TFs Y Smoothing reduces points on all TFs, removes adjacent points with prices within deltaY, while preserving the smaller curve details. A combination of X,Y produces the most accurate smoothing. Higher delta value - larger range, more points removed. Show Max Bars Back: - can't set plot show_last from input -> implemented using a timenow based range check - you can't delete/modify history once plotted, so essentially it just sets a start point for plotting (from num_bars bars back) that works only in realtime mode (not in replay) Levels: You can plot current MA value using plot trackprice=true or by checking Show Price Line in Style. Problem is: - you can only change color (not the dashed line style, width), have both ma + price line (not just the line), and it's full screen wide - you can't set plot trackprice from input => implemented using plotshape/plotchar with fixed text labels serving as levels - there's no other way of creating a dynamic level: hline, plot, offset - nothing else works. - you can't plot a text var - all text strings must be constants, so you can't change the style, width and text labels without recompiling. - from input you can only adjust offset, indent and shift for each level group, and change color - the dot below each level line is the exact MA value. If you want just the line swap plotshape with plotchar, recompile and save as your private version, adjust Y shift. To speed up redraw times: reduce last_bars to ~2000, recompile and use as your own private version Pinescript is a rudimentary language (should be called Painscript instead) that can basically only plot data. You can't do much else. Please see the code for tips and hints. Certain things just can't be done or require shady workarounds and weeks of testing trying to resolve weird node.js compiler errors. Feel free to learn from/reuse/change the code as needed and use as your own private version. See comments in code. Good Luck!
Pine Script® indicator
by RagingRocketBull
7
FvgCalculations█ OVERVIEW This library provides the core calculation engine for identifying Fair Value Gaps (FVGs) across different timeframes and for processing their interaction with price. It includes functions to detect FVGs on both the current chart and higher timeframes, as well as to check for their full or partial mitigation. █ CONCEPTS The library's primary functions revolve around the concept of Fair Value Gaps and their lifecycle. Fair Value Gap (FVG) Identification An FVG, or imbalance, represents a price range where buying or selling pressure was significant enough to cause a rapid price movement, leaving an "inefficiency" in the market. This library identifies FVGs based on three-bar patterns: Bullish FVG: Forms when the low of the current bar (bar 3) is higher than the high of the bar two periods prior (bar 1). The FVG is the space between the high of bar 1 and the low of bar 3. Bearish FVG: Forms when the high of the current bar (bar 3) is lower than the low of the bar two periods prior (bar 1). The FVG is the space between the low of bar 1 and the high of bar 3. The library provides distinct functions for detecting FVGs on the current (Low Timeframe - LTF) and specified higher timeframes (Medium Timeframe - MTF / High Timeframe - HTF). FVG Mitigation Mitigation refers to price revisiting an FVG. Full Mitigation: An FVG is considered fully mitigated when price completely closes the gap. For a bullish FVG, this occurs if the current low price moves below or touches the FVG's bottom. For a bearish FVG, it occurs if the current high price moves above or touches the FVG's top. Partial Mitigation (Entry/Fill): An FVG is partially mitigated when price enters the FVG's range but does not fully close it. The library tracks the extent of this fill. For a bullish FVG, if the current low price enters the FVG from above, that low becomes the new effective top of the remaining FVG. For a bearish FVG, if the current high price enters the FVG from below, that high becomes the new effective bottom of the remaining FVG. FVG Interaction This refers to any instance where the current bar's price range (high to low) touches or crosses into the currently unfilled portion of an active (visible and not fully mitigated) FVG. Multi-Timeframe Data Acquisition To detect FVGs on higher timeframes, specific historical bar data (high, low, and time of bars at indices and relative to the higher timeframe's last completed bar) is required. The requestMultiTFBarData function is designed to fetch this data efficiently. █ CALCULATIONS AND USE The functions in this library are typically used in a sequence to manage FVGs: 1. Data Retrieval (for MTF/HTF FVGs): Call requestMultiTFBarData() with the desired higher timeframe string (e.g., "60", "D"). This returns a tuple of htfHigh1, htfLow1, htfTime1, htfHigh3, htfLow3, htfTime3. 2. FVG Detection: For LTF FVGs: Call detectFvg() on each confirmed bar. It uses high , low, low , and high along with barstate.isconfirmed. For MTF/HTF FVGs: Call detectMultiTFFvg() using the data obtained from requestMultiTFBarData(). Both detection functions return an fvgObject (defined in FvgTypes) if an FVG is found, otherwise na. They also can classify FVGs as "Large Volume" (LV) if classifyLV is true and the FVG size (top - bottom) relative to the tfAtr (Average True Range of the respective timeframe) meets the lvAtrMultiplier. 3. FVG State Updates (on each new bar for existing FVGs): First, check for overall price interaction using fvgInteractionCheck(). This function determines if the current bar's high/low has touched or entered the FVG's currentTop or currentBottom. If interaction occurs and the FVG is not already mitigated: Call checkMitigation() to determine if the FVG has been fully mitigated by the current bar's currentHigh and currentLow. If true, the FVG's isMitigated status is updated. If not fully mitigated, call checkPartialMitigation() to see if the price has further entered the FVG. This function returns the newLevel to which the FVG has been filled (e.g., currentLow for a bullish FVG, currentHigh for bearish). This newLevel is then used to update the FVG's currentTop or currentBottom. The calling script (e.g., fvgMain.c) is responsible for storing and managing the array of fvgObject instances and passing them to these update functions. █ NOTES Bar State for LTF Detection: The detectFvg() function relies on barstate.isconfirmed to ensure FVG detection is based on closed bars, preventing FVGs from being detected prematurely on the currently forming bar. Higher Timeframe Data (lookahead): The requestMultiTFBarData() function uses lookahead = barmerge.lookahead_on. This means it can access historical data from the higher timeframe that corresponds to the current bar on the chart, even if the higher timeframe bar has not officially closed. This is standard for multi-timeframe analysis aiming to plot historical HTF data accurately on a lower timeframe chart. Parameter Typing: Functions like detectMultiTFFvg and detectFvg infer the type for boolean (classifyLV) and numeric (lvAtrMultiplier) parameters passed from the main script, while explicitly typed series parameters (like htfHigh1, currentAtr) expect series data. fvgObject Dependency: The FVG detection functions return fvgObject instances, and fvgInteractionCheck takes an fvgObject as a parameter. This UDT is defined in the FvgTypes library, making it a dependency for using FvgCalculations. ATR for LV Classification: The tfAtr (for MTF/HTF) and currentAtr (for LTF) parameters are expected to be the Average True Range values for the respective timeframes. These are used, if classifyLV is enabled, to determine if an FVG's size qualifies it as a "Large Volume" FVG based on the lvAtrMultiplier. MTF/HTF FVG Appearance Timing: When displaying FVGs from a higher timeframe (MTF/HTF) on a lower timeframe (LTF) chart, users might observe that the most recent MTF/HTF FVG appears one LTF bar later compared to its appearance on a native MTF/HTF chart. This is an expected behavior due to the detection mechanism in `detectMultiTFFvg`. This function uses historical bar data from the MTF/HTF (specifically, data equivalent to `HTF_bar ` and `HTF_bar `) to identify an FVG. Therefore, all three bars forming the FVG on the MTF/HTF must be fully closed and have shifted into these historical index positions relative to the `request.security` call from the LTF chart before the FVG can be detected and displayed on the LTF. This ensures that the MTF/HTF FVG is identified based on confirmed, closed bars from the higher timeframe. █ EXPORTED FUNCTIONS requestMultiTFBarData(timeframe)   Requests historical bar data for specific previous bars from a specified higher timeframe.   It fetches H , L , T (for the bar before last) and H , L , T (for the bar three periods prior) from the requested timeframe.   This is typically used to identify FVG patterns on MTF/HTF.   Parameters:      timeframe (simple string) : The higher timeframe to request data from (e.g., "60" for 1-hour, "D" for Daily).   Returns: A tuple containing: .   - htfHigh1 (series float): High of the bar at index 1 (one bar before the last completed bar on timeframe).   - htfLow1 (series float): Low of the bar at index 1.   - htfTime1 (series int) : Time of the bar at index 1.   - htfHigh3 (series float): High of the bar at index 3 (three bars before the last completed bar on timeframe).   - htfLow3 (series float): Low of the bar at index 3.   - htfTime3 (series int) : Time of the bar at index 3. detectMultiTFFvg(htfHigh1, htfLow1, htfTime1, htfHigh3, htfLow3, htfTime3, tfAtr, classifyLV, lvAtrMultiplier, tfType)   Detects a Fair Value Gap (FVG) on a higher timeframe (MTF/HTF) using pre-fetched bar data.   Parameters:      htfHigh1 (float) : High of the first relevant bar (typically high ) from the higher timeframe.      htfLow1 (float) : Low of the first relevant bar (typically low ) from the higher timeframe.      htfTime1 (int) : Time of the first relevant bar (typically time ) from the higher timeframe.      htfHigh3 (float) : High of the third relevant bar (typically high ) from the higher timeframe.      htfLow3 (float) : Low of the third relevant bar (typically low ) from the higher timeframe.      htfTime3 (int) : Time of the third relevant bar (typically time ) from the higher timeframe.      tfAtr (float) : ATR value for the higher timeframe, used for Large Volume (LV) FVG classification.      classifyLV (bool) : If true, FVGs will be assessed to see if they qualify as Large Volume.      lvAtrMultiplier (float) : The ATR multiplier used to define if an FVG is Large Volume.      tfType (series tfType enum from no1x/FvgTypes/1) : The timeframe type (e.g., types.tfType.MTF, types.tfType.HTF) of the FVG being detected.   Returns: An fvgObject instance if an FVG is detected, otherwise na. detectFvg(classifyLV, lvAtrMultiplier, currentAtr)   Detects a Fair Value Gap (FVG) on the current (LTF - Low Timeframe) chart.   Parameters:      classifyLV (bool) : If true, FVGs will be assessed to see if they qualify as Large Volume.      lvAtrMultiplier (float) : The ATR multiplier used to define if an FVG is Large Volume.      currentAtr (float) : ATR value for the current timeframe, used for LV FVG classification.   Returns: An fvgObject instance if an FVG is detected, otherwise na. checkMitigation(isBullish, fvgTop, fvgBottom, currentHigh, currentLow)   Checks if an FVG has been fully mitigated by the current bar's price action.   Parameters:      isBullish (bool) : True if the FVG being checked is bullish, false if bearish.      fvgTop (float) : The top price level of the FVG.      fvgBottom (float) : The bottom price level of the FVG.      currentHigh (float) : The high price of the current bar.      currentLow (float) : The low price of the current bar.   Returns: True if the FVG is considered fully mitigated, false otherwise. checkPartialMitigation(isBullish, currentBoxTop, currentBoxBottom, currentHigh, currentLow)   Checks for partial mitigation of an FVG by the current bar's price action.   It determines if the price has entered the FVG and returns the new fill level.   Parameters:      isBullish (bool) : True if the FVG being checked is bullish, false if bearish.      currentBoxTop (float) : The current top of the FVG box (this might have been adjusted by previous partial fills).      currentBoxBottom (float) : The current bottom of the FVG box (similarly, might be adjusted).      currentHigh (float) : The high price of the current bar.      currentLow (float) : The low price of the current bar.   Returns: The new price level to which the FVG has been filled (e.g., currentLow for a bullish FVG).   Returns na if no new partial fill occurred on this bar. fvgInteractionCheck(fvg, highVal, lowVal)   Checks if the current bar's price interacts with the given FVG.   Interaction means the price touches or crosses into the FVG's current (possibly partially filled) range.   Parameters:      fvg (fvgObject type from no1x/FvgTypes/1) : The FVG object to check.     Its isMitigated, isVisible, isBullish, currentTop, and currentBottom fields are used.      highVal (float) : The high price of the current bar.      lowVal (float) : The low price of the current bar.   Returns: True if price interacts with the FVG, false otherwise.
Pine Script® library
by no1x