Get started

HMA

HMA-Kahlman Trend, DifferenceFilter & TrendlinesThis update to the previous HMA-Kahlman Trend, Clipping & Trendlines script features the same structure with the three modules: - Trendlines module, - NEW Winsorizing submodule using difference-based filtering. - HMA-Kahlman Trend module. The Winsorizing submodule filters signals by a volume level, eliminating the ones with the volume below a threshold. This module substitutes the previous 'low-level' filtering implementation. This time it filters out based on difference between scaled volume and its moving average. Tested with BTCUSD.
Pine Script™ indicator
by capissimo
15
HMA-Kahlman Trend, Clipping & TrendlinesThis script utilizes three modules: - Trendlines module (by Joris Duyck), - Winsorizing submodule and - HMA-Kahlman Trend module. The Trendlines module produces crossovers predictive of the next local trend. The Winsorizing (clipping) submodule filters signals by a volume level, eliminating the ones with the volume below a threshold. The last feature obviously does not work with the assets not supporing Volume, so set the Winsorizing submodule to false. The Winsorizing and Trendlines modules can be turned off.
Pine Script™ indicator
by capissimo
13
3HMAIntroduction The Hull smoothing method aim to reduce the lag of a moving average by using a simple calculation involving smoothing with a moving average of period √p the subtraction of a moving average of period p/2 multiplied by 2 with another moving average of period p , however it is possible to extend this calculation by introducing more terms thus reducing both the lag and overshoot of the classical HMA. Comparison The proposed filter add 1 more term to the classical hull moving average thus ending with : sma(sma(p/3) * 3 - sma(p/2) - sma(p),p) , this can be developed as long as every terms add to total unity, more terms will often require more smoothing, this is why i replace √p by p . In blue a HMA and in red the proposed filter of both period 50. The third term added allow for more reactivity which sometimes allow for overshoots with lower amplitudes. Conclusions Adding more terms to certain filtering methods can correct certain behaviours as well as reducing lag or increasing smoothing.
Pine Script™ indicator
by alexgrover
12
No Nonsense NNFX VP Strategy for Back Testing | jhMy first script, be kind :) Most of the rules are implemented: - Money management - ATR, Baseline, Confirmation, Volume, Exit More details below. ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// //Designed per No Nonsense Forex VP rules //Made to be as modular as possible, so we can swap the indicators in and out. //Originated from causecelebre //Tried to put in as much VP rules as possible /////////////////////////////////////////////////// //Rules Implemented: /////////////////////////////////////////////////// // - SL 1.5 x ATR // - TP 1 x ATR // // - Entry conditions //// - Entry within 1 candles of baseline + 1 x confirmation + volume //// - Entry only if baseline is < 1 x ATR // - Exit conditions //// - Exit on exit indicator or when baseline or confirmation flip /////////////////////////////////////////////////// //Trades entries /////////////////////////////////////////////////// // - First entry L1 or S1 with standard SL and TP // - Second entry L2 or S2 with standard SL and exit upon the exit conditions /////////////////////////////////////////////////// //Included Indicators and settings /////////////////////////////////////////////////// // - Baseline = HMA 20 // - Confirmtion = SSL 10 // - Volume = TDFI 4 // - Exit = RVI 4 /////////////////////////////////////////////////// //Credits // Strategy causecelebre // TDFI causecelebre // SSL Channel ErwinBeckers ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pine Script™ strategy
by jiehonglim
33
Hull MAThis Hull MA uses the default settings of the built-in MA. The basic idea is that we are in a buy setup when hull is below price, and a sell setup when hull is above price. The indicator is extended with slightly change in contrast when moving average is declining and it plot the ma/price crossovers: green dot when a buy setup is appearing, and red dot when a sell setup is forming. It is possible to hide crossovers in the option panel. Three alert conditions is added "Hull MA cross", "Hull MA sell" and "Hull MA buy". I use "Hull MA cross" on slow frames (2w, M) and "Hull MA buy/sell" on faster frames.
Pine Script™ indicator
by Skrymten
8
Multi SMA EMA WMA HMA BB (5x8 MAs Bollinger Bands) MAX MTF - RRBMulti SMA EMA WMA HMA 4x7 Moving Averages with Bollinger Bands MAX MTF by RagingRocketBull 2019 Version 1.0 All available MAX MTF versions are listed below (They are very similar and I don't want to publish them as separate indicators): ver 1.0: 4x7 = 28 MTF MAs + 28 Levels + 3 BB = 59 < 64 ver 2.0: 5x6 = 30 MTF MAs + 30 Levels + 3 BB = 63 < 64 ver 3.0: 3x10 = 30 MTF MAs + 30 Levels + 3 BB = 63 < 64 ver 4.0: 5(4+1)x8 = 8 CurTF MAs + 32 MTF MAs + 20 Levels + 3 BB = 63 < 64 ver 5.0: 6(5+1)x6 = 6 CurTF MAs + 30 MTF MAs + 24 Levels + 3 BB = 63 < 64 ver 6.0: 4(3+1)x10 = 10 CurTF MAs + 30 MTF MAs + 20 Levels + 3 BB = 63 < 64 Fib numbers: 8, 13, 21, 34, 55, 89, 144, 233, 377 This indicator shows multiple MAs of any type SMA EMA WMA HMA etc with BB and MTF support, can show MAs as dynamically moving levels. There are 4 MA groups + 1 BB group, a total of 4 TFs * 7 MAs = 28 MAs. You can assign any type/timeframe combo to a group, for example: - EMAs 9,12,26,50,100,200,400 x H1, H4, D1, W1 (4 TFs x 7 MAs x 1 type) - EMAs 8,13,21,30,34,50,55,89,100,144,200,233,377,400 x M15, H1 (2 TFs x 14 MAs x 1 type) - D1 EMAs and SMAs 8,13,21,30,34,50,55,89,100,144,200,233,377,400 (1 TF x 14 MAs x 2 types) - H1 WMAs 13,21,34,55,89,144,233; H4 HMAs 9,12,26,50,100,200,400; D1 EMAs 12,26,89,144,169,233,377; W1 SMAs 9,12,26,50,100,200,400 (4 TFs x 7 MAs x 4 types) - +1 extra MA type/timeframe for BB There are several versions: Simple, MTF, Pro MTF, Advanced MTF, MAX MTF and Ultimate MTF. This is the MAX MTF version. The Differences are listed below. All versions have BB - Simple: you have 2 groups of MAs that can be assigned any type (5+5) - MTF: +2 custom Timeframes for each group (2x5 MTF) +1 TF for BB, TF XY smoothing - Pro MTF: 4 custom Timeframes for each group (4x3 MTF), 1 TF for BB, MA levels and show max bars back options - Advanced MTF: +4 extra MAs/group (4x7 MTF), custom Ticker/Symbols, Timeframe <>= filter, Remove Duplicates Option - MAX MTF: +2 subtypes/group, packed to the limit with max possible MAs/TFs: 4x7, 5x6, 3x10, 4(3+1)x10, 5(4+1)x8, 6(5+1)x6 - Ultimate MTF: +individual settings for each MA, custom Ticker/Symbols MAX MTF version tests the limits of Pinescript trying to squeeze as many MAs/TFs as possible into a single indicator. It's basically a maxed out Advanced version with subtypes allowing for mixed types within a group (i.e. both emas and smas in a single group/TF) Pinescript has the following limits: - max 40 security calls (6 calls are reserved for dupe checks and smoothing, 2 are used for BB, so only 32 calls are available) - max 64 plot outputs (BB uses 3 outputs, so only 61 plot outputs are available) - max 50000 (50kb) size of the compiled code Based on those limits, you can only have the following MAs/TFs combos in a single script: 1. 4x7, 5x6, 3x10 - total number of MTF MAs must always be <= 32, and you can still have BB and Num Levels = total MAs, without any compromises 2. 5(4+1)x8, 6(5+1)x6, 4(3+1)x10 - you can use the Current Symbol/Timeframe as an extra (+1) fixed TF with the same number of MTF MAs - you don't need to call security to display MAs on the Current Symbol/Timeframe, so the total number of MTF MAs remains the same and is still <= 32 - to fit that many MAs into the max 64 plot outputs limit you need to reduce the number of levels (not every MA Group will have corresponding levels) Features: - 4x7 = 28 MAs of any type - 4x MTF groups with XY step line smoothing - +1 extra TF/type for BB MAs - 2 MA subtypes within each group/TF - 4x7 = 28 MA levels with adjustable group offsets, indents and shift - supports any existing type of MA: SMA, EMA, WMA, Hull Moving Average (HMA) - custom tickers/symbols for each group - show max bars back option - show/hide both groups of MAs/levels/BB and individual MAs - timeframe filter: show only MAs/Levels with TFs <>= Current TF - hide MAs/Levels with duplicate TFs - support for custom TFs that are not available in free accounts: 2D, 3D etc - support for timeframes in H: H, 2H, 4H etc Notes: - Uses timeframe textbox instead of input resolution dropdown to allow for 240 120 and other custom TFs - Uses symbol textbox instead of input symbol to avoid establishing multiple dummy security connections to the current ticker - otherwise empty symbols will prevent script from running - Possible reasons for missing MAs on a chart: - there may not be enough bars in history to start plotting it. For example, W1 EMA200 needs at least 200 bars on a weekly chart. - for charts with low/fractional prices i.e. 0.00002 << 0.001 (default Y smoothing step) decrease Y smoothing as needed (set Y = 0.0000001) or disable it completely (set X,Y to 0,0) - for charts with high price values i.e. 20000 >> 0.001 increase Y smoothing as needed (set Y = 10-20). Higher values exceeding MAs point density will cause it to disappear as there will be no points to plot. Different TFs may require diff adjustments - TradingView Replay Mode UI and Pinescript security calls are limited to TFs >= D (D,2D,W,MN...) for free accounts - attempting to plot any TF < D1 in Replay Mode will only result in straight lines, but all TFs will work properly in history and real-time modes. This is not a bug. - Max Bars Back (num_bars) is limited to 5000 for free accounts (10000 for paid), will show error when exceeded. To plot on all available history set to 0 (default) - Slow load/redraw times. This indicator becomes slower, its UI less responsive when: - Pinescript Node.js graphics library is too slow and inefficient at plotting bars/objects in a browser window. Code optimization doesn't help much - the graphics engine is the main reason for general slowness. - the chart has a long history (10000+ bars) in a browser's cache (you have scrolled back a couple of screens in a max zoom mode). - Reload the page/Load a fresh chart and then apply the indicator or - Switch to another Timeframe (old TF history will still remain in cache and that TF will be slow) - in max possible zoom mode around 4500 bars can fit on 1 screen - this also slows down responsiveness. Reset Zoom level - initial load and redraw times after a param change in UI also depend on TF. For example: D1/W1 - 2 sec, H1/H4 - 5-6 sec, M30 - 10 sec, M15/M5 - 4 sec, M1 - 5 sec. M30 usually has the longest history (up to 16000 bars) and W1 - the shortest (1000 bars). - when indicator uses more MAs (plots) and timeframes it will redraw slower. Seems that up to 5 Timeframes is acceptable, but 6+ Timeframes can become very slow. - show_last=last_bars plot limit doesn't affect load/redraw times, so it was removed from MA plot - Max Bars Back (num_bars) default/custom set UI value doesn't seem to affect load/redraw times - In max zoom mode all dynamic levels disappear (they behave like text) - Dupe check includes symbol: symbol, tf, both subtypes - all must match for a duplicate group - For the dupe check to work correctly a custom symbol must always include an exchange prefix. BB is not checked for dupes Good Luck! Feel free to learn from/reuse the code to build your own indicators.
Pine Script™ indicator
by RagingRocketBull
12
Multi SMA EMA WMA HMA BB (4x5 MAs Bollinger Bands) Adv MTF - RRBMulti SMA EMA WMA HMA 4x5 Moving Averages with Bollinger Bands Advanced MTF by RagingRocketBull 2019 Version 1.0 This indicator shows multiple MAs of any type SMA EMA WMA HMA etc with BB and MTF support, can show MAs as dynamically moving levels. There are 4 MA groups + 1 BB group, a total of 4 TFs * 5 MAs = 20 MAs. You can assign any type/timeframe combo to a group, for example: - EMAs 12,26,50,100,200 x H1, H4, D1, W1 (4 TFs x 5 MAs x 1 type) - EMAs 8,10,13,21,30,50,55,100,200,400 x M15, H1 (2 TFs x 10 MAs x 1 type) - D1 EMAs and SMAs 8,10,12,26,30,50,55,100,200,400 (1 TF x 10 MAs x 2 types) - H1 WMAs 7,77,89,167,231; H4 HMAs 12,26,50,100,200; D1 EMAs 89,144,169,233,377; W1 SMAs 12,26,50,100,200 (4 TFs x 5 MAs x 4 types) - +1 extra MA type/timeframe for BB There are several versions: Simple, MTF, Pro MTF, Advanced MTF and Ultimate MTF. This is the Advanced MTF version. The Differences are listed below. All versions have BB - Simple: you have 2 groups of MAs that can be assigned any type (5+5) - MTF: +2 custom Timeframes for each group (2x5 MTF) +1 TF for BB, TF XY smoothing - Pro MTF: 4 custom Timeframes for each group (4x3 MTF), 1 TF for BB, MA levels and show max bars back options - Advanced MTF: +2 extra MAs/group (4x5 MTF), custom Ticker/Symbols, Timeframe <>= filter, Remove Duplicates Option - Ultimate MTF: +individual settings for each MA, custom Ticker/Symbols Features: - 4x5 = 20 MAs of any type - 4x MTF groups with XY step line smoothing - +1 extra TF/type for BB MAs - 4x5 = 20 MA levels with adjustable group offsets, indents and shift - supports any existing type of MA: SMA, EMA, WMA, Hull Moving Average (HMA) - custom tickers/symbols for each group - you can compare MAs of the same symbol across exchanges - show max bars back option - show/hide both groups of MAs/levels/BB and individual MAs - timeframe filter: show only MAs/Levels with TFs <>= Current TF - hide MAs/Levels with duplicate TFs - support for custom TFs that are not available in free accounts: 2D, 3D etc - support for timeframes in H: H, 2H, 4H etc Notes: - Uses timeframe textbox instead of input resolution dropdown to allow for 240 120 and other custom TFs - Uses symbol textbox instead of input symbol to avoid establishing multiple dummy security connections to the current ticker - otherwise empty symbols will prevent script from running - Possible reasons for missing MAs on a chart: - there may not be enough bars in history to start plotting it. For example, W1 EMA200 needs at least 200 bars on a weekly chart. - price << default Y smoothing step 5. For charts with low/fractional prices (i.e. 0.00002 << 5) adjust X Y smoothing as needed (set Y = 0.0000001) or disable it completely (set X,Y to 0,0) - TradingView Replay Mode UI and Pinescript security calls are limited to TFs >= D (D,2D,W,MN...) for free accounts - attempting to plot any TF < D1 in Replay Mode will only result in straight lines, but all TFs will work properly in history and real-time modes. This is not a bug. - Max Bars Back (num_bars) is limited to 5000 for free accounts (10000 for paid), will show error when exceeded. To plot on all available history set to 0 (default) - Slow load/redraw times. This indicator becomes slower, its UI less responsive when: - Pinescript Node.js graphics library is too slow and inefficient at plotting bars/objects in a browser window. Code optimization doesn't help much - the graphics engine is the main reason for general slowness. - the chart has a long history (10000+ bars) in a browser's cache (you have scrolled back a couple of screens in a max zoom mode). - Reload the page/Load a fresh chart and then apply the indicator or - Switch to another Timeframe (old TF history will still remain in cache and that TF will be slow) - in max possible zoom mode around 4500 bars can fit on 1 screen - this also slows down responsiveness. Reset Zoom level - initial load and redraw times after a param change in UI also depend on TF. For example: D1/W1 - 2 sec, H1/H4 - 5-6 sec, M30 - 10 sec, M15/M5 - 4 sec, M1 - 5 sec. M30 usually has the longest history (up to 16000 bars) and W1 - the shortest (1000 bars). - when indicator uses more MAs (plots) and timeframes it will redraw slower. Seems that up to 5 Timeframes is acceptable, but 6+ Timeframes can become very slow. - show_last=last_bars plot limit doesn't affect load/redraw times, so it was removed from MA plot - Max Bars Back (num_bars) default/custom set UI value doesn't seem to affect load/redraw times - In max zoom mode all dynamic levels disappear (they behave like text) 1. based on 3EmaBB, uses plot*, barssince and security functions 2. you can't set certain constants from input due to Pinescript limitations - change the code as needed, recompile and use as a private version 3. Levels = trackprice implementation 4. Show Max Bars Back = show_last implementation 5. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params 6. Smoothing is applied by default for visual aesthetics on MTF. To use exact ma mtf values (lines with stair stepping) - disable it Good Luck! You can explore, modify/reuse the code to build your own indicators.
Pine Script™ indicator
by RagingRocketBull
3
4 Hull MAThe Hull Moving Average (HMA) was developed by Alan Hull in 2005 for the purpose of reducing lag, increasing responsiveness while at the same time eliminating noise. Its calculation is elaborate and makes use of the Weighted Moving Average (WMA). It emphasizes recent prices over older ones, resulting in a fast-acting yet smooth moving average that can be used to identify the prevailing market trend. It can also be used for entry and exit signals. I have integrated 4 HMA's into one which can be used for taking entry and exits similar to 4 EMA strategies. All credit goes to Alan Hull for developing this technique.
Pine Script™ indicator
by ghazni
HMA + HMA + Dispersion background fill (ver 2.0)fast HMA • slow HMA • Dispersion Zone| background color's --- Background colors: Red, Green and Yellow. Default transperent = 5% • Green background: fast HMA above the dispersion zone • Red background: fast HMA below the dispersion zone • Yellow background: fast HMA inside the Dispersion Zone --- # Alerts only for cross Yellow to Green and Yellow to Red zones. --- • The dispersion zone is calculated relative to the slow HMA.
Pine Script™ indicator
by Mr.Mozart
20
Hull Moving Average and Daily Candle CrossoverHull Moving Average. Alan Hull developed Hull Moving Average in 2005 in his quest to create a moving average that is "responsive to current price activity while maintaining curve smoothness". Hull claims that his moving average "almost eliminates lag altogether and manages to improve smoothing at the same time" This strategy has Lag built in, the signal will appear 1 or 2 candles lagged, but it wont repaint the signal.... in theory! Does this repaint? you tell me. thankyou Change the settings every time you change timeframe or pair
Pine Script™ strategy
by SeaSide420
7