Rozpocznij

Wyszukaj w skryptach "mtf"

B3 Fibonacci Pivot S/RFor my second share, I give you some levels I look at everyday for the ES minis. HLC/3 of the MTF (multi-time-frame) inputs = mean and Fib-levels formed as support and resistance zones. There are some websites that will show you 20 ways to figure out a pivot for the day's intraday workings, and this one always rang true for me. I keep it set at Res=D and Len=3or5 and use on hourly charts. This indicator is capable of doing like a Res=60m Len=8 for a 5m chart or something of that nature if you wish to test it out. I haven't tested it out for tick charts and I have noticed that this is good on index and commodity futures, and not so much other things. Uncanny to me how well this works as reversal awareness for ES. Doesn't mean that one will happen, or if it does that it will have trade-able juice, though it is very important awareness never-the-less. screencast.com
Wskaźnik Pine Script®
od HammondB3
7
Percent Difference Between VWAP and Price MTFShows the difference between vwap and price in percent. You can can choose between multiple timeframe vwap. Default is normal daily. The levels on the indicator can be changed to whatever you want to. In the chart above we can see eurusd reverting up at 3% below monthly vwap, after the brexit dip, It then turns down again at 1% from monthly and lastly it turns up again at 2% from monthly. Script is a small modification of this:
Wskaźnik Pine Script®
od TheYangGuizi
2
EMA bullish/bearish dashboard - MTFThis is a good reminder for which way you should be placing orders. It's best to not ignore these signals!!! lime = full bull - 100ema above 200ema and price is above 200ema green = hallf bull - price now below 200ema but 100ema is still above the 200 maroon = full bear - opposite of full bull red = half bear - opposite of half bull Also with multi timeframe option - so I guess you could stack several of these on a single framed chart if you wanted.
Wskaźnik Pine Script®
od squattter
1
Multi-Functional Fisher Transform MTF with MACDL TRIGGERWhat this indicator gives you is a true signal when price is exhausted and ready for a fast turnaround. Fisher Transform is set for multi-time frame and also allows the user to change the length. This way a user can compare two or more time spans and lengths to look for these MACDL divergent triggers after a Fisher exhaustion. With so many indicators, it's probably best to merge these indicators and change the Fisher and Trigger colors so you can still have a look at price action (remember to scale right after merger). I've noticed from time to time when you have Fisher 34 100 and 300 up and running on two different time frames such as 5 and 15 min charts, with MACDL triggers on the 100/300 or 34/100 you get a high probability trade trigger. However, there are rare exceptions such as when price moves in a parabolic state up or down for a long period where this indication does not work. Ideally this indicator works best in a sideways market or slow rising/descending moving market. This indicator was worked on by Glaz, nmike and myself LazyBear also introduced the MACDL indicator
Wskaźnik Pine Script®
od QuantitativeExhaustion
18
TrendDetectorLibLibrary "TrendDetector_Lib" method formatTF(timeframe)   Namespace types: series string, simple string, input string, const string   Parameters:      timeframe (string) : (string) The timeframe to convert (e.g., "15", "60", "240").   Returns: (string) The formatted timeframe (e.g., "15M", "1H", "4H"). f_ma(type, src, len)   Computes a Moving Average value based on type and length.   Parameters:      type (simple string) : (string) One of: "SMA", "EMA", "RMA", "WMA", "VWMA".      src (float) : (series float) Source series for MA (e.g., close).      len (simple int) : (simple int) Length of the MA.   Returns: (float) The computed MA series. render(tbl, trendDetectorSwitch, frameColor, frameWidth, borderColor, borderWidth, textColor, ma1ShowTrendData, ma1Timeframe, ma1Value, ma2ShowTrendData, ma2Timeframe, ma2Value, ma3ShowTrendData, ma3Timeframe, ma3Value)   Fills the provided table with Trend Detector contents. @desc This renderer does NOT plot and does NOT create tables; call from indicator after your table exists.   Parameters:      tbl (table) : (table) Existing table to render into.      trendDetectorSwitch (bool) : (bool) Master toggle to draw the table content.      frameColor (color) : (color) Table frame color.      frameWidth (int) : (int) Table frame width (0–5).      borderColor (color) : (color) Table border color.      borderWidth (int) : (int) Table border width (0–5).      textColor (color) : (color) Table text color.      ma1ShowTrendData (bool) : (bool) Show MA #1 in table.      ma1Timeframe (simple string) : (string) MA #1 timeframe.      ma1Value (float)      ma2ShowTrendData (bool) : (bool) Show MA #2 in table.      ma2Timeframe (simple string) : (string) MA #2 timeframe.      ma2Value (float)      ma3ShowTrendData (bool) : (bool) Show MA #3 in table.      ma3Timeframe (simple string) : (string) MA #3 timeframe.      ma3Value (float)
Biblioteka Pine Script®
od rithsila
MTFDataLibrary "MTFData" Functions to store multi timeframe candle data and swing points. getCandleData(timeframe, openArray, highArray, lowArray, closeArray, timeArray, olcLookback, alltfs_olcLookback, tfIndex)   Stores current or higher timeframe candle data in arrays.   Parameters:      timeframe (string) : The timeframe, for example "240" for 4h      openArray (array) : An array to store the candle open price      highArray (array) : An array to store the candle high price      lowArray (array) : An array to store the candle low price      closeArray (array) : An array to store the candle close price      timeArray (array) : An array to store the candle time      olcLookback (int) : The history reference of the lookback limiting candle      alltfs_olcLookback (array) : An array holding the candle time of olcLookback candles ago, which can be used for limiting lookbacks      tfIndex (int) : The timeframe's index in the alltfs_olcLookback array   Returns: true if the timeframe changed trackHiLo(tfchange, timeframe, openArray, highArray, lowArray, closeArray, timeArray, highWickArray, highBodyArray, highTimeArray, lowWickArray, lowBodyArray, lowTimeArray, alltfs_olcLookback, tfIndex)   Stores current or higher timeframe swingpoint data into arrays.   Parameters:      tfchange (bool) : Must be true when the timeframe has changed (a new candle has opened)      timeframe (string) : The timeframe, for example "240" for 4h      openArray (array) : An array that stores the timeframe's candle open price      highArray (array) : An array that stores the timeframe's candle high price      lowArray (array) : An array that stores the timeframe's candle low price      closeArray (array) : An array that stores the timeframe's candle close price      timeArray (array) : An array that stores the timeframe's candle time      highWickArray (array) : An array to store the swing high price      highBodyArray (array) : An array to store the swing high's highest body price      highTimeArray (array) : An array to store the swing high candle's time      lowWickArray (array) : An array to store the swing low price      lowBodyArray (array) : An array to store the swing low's lowest body price      lowTimeArray (array) : An array to store the swing high candle's time      alltfs_olcLookback (array) : An array holding the time of the max allowed swing point age      tfIndex (int) : The timeframe's index in the alltfs_olcLookback array   Returns: Nothing. The array handling happens inside the function. tfReadable(tfInSec)   Converts a timeframe string ("240") into a more readable string ("4h").   Parameters:      tfInSec (int) : The timeframe that should be converted, as timeframe.in_seconds()   Returns: A more readable timeframe string
Biblioteka Pine Script®
od nilstrades_
MTF Dynamic MA TrackerThis indicator allows you to track the behavior of price relative to a key Moving Average across up to 9 different timeframes simultaneously. The idea behind this tool is to see what your favourite MA is doing at various TFs while solving the problem of "chart clutter." Plotting 9 different Moving Averages on a single chart usually results in a messy interface that is hard to read. This script solves that using Dynamic Dimming. Default Settings: By default, the script is configured to track the EMA 200 (Exponential Moving Average). However, this is for illustration purposes only. You can fully customize the indicator to track your preferred Moving Average Type (EMA, SMA, HMA, WMA, or RMA) and your preferred Length (e.g., 50, 100, 200) in the settings menu. Key Features: Multi-Timeframe Tracking: Monitor your chosen Moving Average across 9 user-defined timeframes (e.g., 1m, 5m, 15m, 1H, 4H, Daily, etc.) directly on your current chart. Dynamic Visibility (Dimming): By default, the MA lines remain transparent (dimmed) to keep your chart clean. The lines automatically brighten (light up) only when the price comes within a specific proximity of the MA. This highlights immediate Support or Resistance levels without visual noise. You can customize the "Proximity Method" using either a Percentage of price or an ATR multiplier. Tag Detection & Alerts: The script detects "Tags"—moments where price interacts with a Moving Average (e.g., wicks into it and closes back above/below). Bull Tag (Support): Price dips into the MA but closes above it. Bear Tag (Resistance): Price spikes into the MA but closes below it. You can set alerts to trigger whenever these interactions occur on any monitored timeframe. Dashboard (Nexus): A status table displays "Clusters" (when price is near multiple MAs simultaneously) and lists any active Bull/Bear tags occurring on the current bar. Customization: MA Type: Choose between EMA, SMA, HMA, WMA, or RMA. MA Length: Input any length (Default: 200). Timeframes: Individually enable/disable and select up to 9 specific timeframes. Dimming: Adjust the transparency for "dimmed" vs "bright" states.
Wskaźnik Pine Script®
od ChiragPatnaik
libSchedulerTLDR: This is a lightweight, easy-to-use way to throttle sections of Pinescript v6 scripts, the same as you'd use barstate.isconfirmed or barstate.islast. You can use this for enormous efficiency gains, provided you design your script to handle updates on differing intervals rather than computing everything on each cycle. Usage is easy: ``` import showmethegrail/libScheduler/1 as libScheduler i_tf_fetch = input.enum(libScheduler.Timeframes.C, "Fetch Interval", tooltip="Do things just once every interval, default=once per chart timeframe.") var scheduler = libScheduler.Scheduler.new().init() if scheduler.every(i_tf_fetch) // Do stuff ``` That's it. If you need to know more, the code is well-commented. Combine this with sensible caching, and you can right-size the compute-heavy sections of your script, for better stability and managed use of Pinescript compute quotas. You'll need to know the proper use of var and varip to make the most of this, but I found this effectively replaced a lot of boilerplate in throttling my own scripts. Sound software engineering, made Pinescript-level easy. That's all.
Biblioteka Pine Script®
od showmethegrail
1
MTF EMA50/200 // ADX (Auto TF Pairing) with SL/TP // v6Strategy overview (EMA50/EMA200 + ADX, multi-timeframe): This system trades only in the direction of the higher-timeframe trend and uses the current chart timeframe for precise entries. Trend filter (Higher TF): Bull trend: EMA50 > EMA200 and ADX ≥ threshold → only LONGs allowed Bear trend: EMA50 < EMA200 and ADX ≥ threshold → only SHORTs allowed If ADX is below the “no-trend” threshold, the market is considered choppy and trades are avoided. Entry (Lower TF / chart TF): Enter only when the chart timeframe confirms momentum in the HTF direction using one of: Touch: price pulls back to EMA50 and closes back on the trend side Rejection: stricter “touch + reject” near EMA50 Cross: close crosses EMA50 in the trend direction Stop Loss (structure + volatility): LONG: below the safer of last swing low or EMA50, minus an ATR buffer SHORT: above the safer of last swing high or EMA50, plus an ATR buffer Take Profit (risk-based): Targets are set as multiples of risk (R) from entry: TP1 = 2R (default) TP2 = 3R (optional) The indicator plots only the latest trade’s Entry (black line), Stop (red dashed), and TP (green dashed), and it auto-pairs the chart timeframe with a “next level up” higher timeframe for the trend filter.
Wskaźnik Pine Script®
od Corbu33