Get started

Indicators and strategies

Auto Fibonacci and Gann Fan/Retracements ComboIntroduction This is a combination of Fibonacci and Gann fan/retracements. The script can automatically draw as many: Fibonacci Retracements Fibonacci Fan Gann Retracements Gann Fan as the user requires on the chart. Each level set or fan consists of 7 lines based on the most important ratios of Fibonacci/Gann. Basics What are Fibonacci retracements? Fibonacci retracement levels are horizontal lines that indicate where support and resistance are likely to occur. They stem from Fibonacci’s sequence. Each level is associated with a percentage which is how much of a prior move the price has retraced. The Fibonacci retracement levels are 23.6%, 38.2%, 61.8%, and 78.6%. While not officially a Fibonacci ratio, 50% is also used. The indicator is useful because it can be drawn between any two significant price points, such as a high and a low. The indicator will then create the levels between those two points. What are Gann retracements? A developer of technical analysis and trading was W.D. Gann. Gann theory expects a normal retracement of 50 percent. This means that under normal selling pressure, the stock price will decline half the amount of its most recent rise, and vice versa. It also suggests that retracements occur at the halfway point of a move, such as 25 percent (half of 50 percent), 12.5 percent (half of 25 percent), and so on. What is Fibonacci fan? Fibonacci fan is a set of sequential trend lines drawn from a trough or peak through a set of points dictated by Fibonacci retracements. The first step to create it is to draw a trend line covering the local lowest and highest prices of a security. To reach retracement levels, the trader divides the difference in price at the low and high end by ratios determined by the Fibonacci series. The lines formed by connecting the starting point for the base trend line and each retracement level create the Fibonacci fan. What is Gann fan? A Gann fan consists of a series of lines called Gann angles. These angles are superimposed over a price chart to show potential support and resistance levels. The resulting image is supposed to help technical analysts predict price changes. Gann believed the 45-degree angle to be most important, but the Gann fan also draws angles at degrees like 75, 63.75, 26.25 and 15. The Gann fan originates at a low or high point. The resulting lines show areas of potential future support and resistance. The 45-degree line is known as the 1:1 line because the price will rise or fall at a 45-degree angle when the price moves up/down one unit for each unit of time. All other lines in the Gann fan are drawn above and below the 1:1 line. The other angles are associated with 2:1, 3:1, 4:1, 8:1 and 1:8, 1:4, 1:3, and 1:2 time-to-price moves. Challenges The most of the time I dedicated to writing this script has been spent on handling these problems: 1. Finding Local Highest/Lowest Prices In order to draw Fibonacci and Gann fan/retracements, it's necessary to find local highest and lowest price points (Extrema) on the chart. As this could be so challenging, most traders and coders draw the lines covering the low and high prices over a given period of time or a limited number of bars back instead. I already wrote an indicator using this approach ( Auto Fibonacci Combo ). In this new script I tried to find the exact highest and lowest prices based on this idea that: if a high point is formed lower than previous high which was after a lowest point, then that previous one was the local highest point, and vice versa if a low point is formed higher than previous low which was after a highest point, then that previous one was the local lowest point. So logically an extremum price on the chart won't be found until the next high/low point is formed. 2. Finding Proper Chart Scale for Gann Fan Based on the theory, Gann angles are sensitive to the chart price scale and in order to have the right angles, the chart must be made with the proper scale. J.A. Hyerczyk in his book "Pattern, Price & Time - Using Gann Theory in Technical Analysis" suggests that the easiest way to determine the scale of a market is by taking the difference between top-to-top and bottom-to-bottom and dividing it by the time it took the market to move from top to top and bottom to bottom. Thus on a properly constructed chart, the basic equation for calculating Gann angles is: Price * Time. 3. Drawing Fans and Relocating Fan Labels at Each New Bar in Pine (A Programming-Related Subject) To do this, I used linear equations and line slopes. Of course it was so complicated and exhausting, but finally I overcame that thanks to my genius cousin. Settings and Usage By default, the script shows detected extremum points plus 1 Fibonacci fan, 1 Gann fan, 1 set of Fibonacci retracements and no Gann retracements on the chart. All of these could be changed in the indicator settings beside the color and transparency of each line. Feel free to use this and send me your thoughts!
Pine Script™ indicator
by informanerd
81
Zigzag Trend/Divergence DetectorPullbacks are always hardest part of the trade and when it happen, we struggle to make decision on whether to continue the trade and wait for recovery or cut losses. Similarly, when an instrument is trending well, it is often difficult decision to make if we want to take some profit off the table. This indicator is aimed to make these decisions easier by providing a combined opinion of sentiment based on trend and possible divergence. ⬜ Process ▶ Use any indicator to find trend bias. Here we are using simple supertrend ▶ Use any oscillator. I have added few inbuilt oscillators as option. Default used is RSI. ▶ Find divergence by using zigzag to detect pivot high/low of price and observing indicator movement difference between subsequent pivots in the same direction. ▶ Combine divregence type, divergence bias and trend bias to derive overall sentiment. Complete details of all the possible combinations are present here along with table legend ⬜Chart Legend C - Continuation D - Divergence H - Hidden Divergence I - Indeterminate ⬜ Settings ▶ Zigzag parameters : These let you chose zigzag properties. If you check "Use confirmed pivots", then unconfirmed pivot will be ignored in the table and in the chart ▶ Oscillator parameters : Lets you select different oscillators and settings. Available oscillators involve CCI - Commodity Channel Index CMO - Chande Momentum Oscillator COG - Center Of Gravity DMI - Directional Movement Index (Only ADX is used here) MACD - Moving average convergence divergence (Can chose either histogram or MACD line) MFI - Money Flow Index MOM - Momentum oscillator ROC - Rate Of Change RSI - Relative Strength Index TSI - Total Strength Index WPR - William Percent R BB - Bollinger Percent B KC - Keltner Channel Percent K DC - Donchian Channel Percent D ADC - Adoptive Donchian Channel Percent D ( Adoptive-Donchian-Channel ) ▶ Trend bias : Supertrend is used for trend bias. Coloring option color candles in the direction of supertrend. More option for trend bias can be added in future. ▶ Stats : Enables you to display history in tabular format. Overview of settings present here: ⬜ Notes Trend detection is done only with respect to previous pivot in the same direction. Hence, if chart has too many zigzags in short period, try increasing the zigzag length or chart timeframe. Similarly, if there is a steep trend, use lower timeframe charts to dig further. Oscillators does not always make pivots at same bar as price. Due to this some the divergence calculation may not be correct. Hence visual inspection is always recommended. ⬜ Possible future enhancements More options for trend bias Enhance divergence calculation. Possible options include using oscillator based zigzag as primary or using close prices based zigzag instead of high/low. Multi level zigzag option - Can be messy to include more than one zigzag. Option can be added to chose either Level1 or Level2 zigzags. Alerts - Alerts can only be added for confirmed pivots - otherwise it will generate too many unwanted alerts. Will think about it :) If I get time, I will try to make a video.
Pine Script™ indicator
by Trendoscope
147
Momentum-based ZigZag (incl. QQE) NON-REPAINTINGI spent a lot of time searching for the best ZigZag indicator. Difficulty with all of them is that they are always betting on some pre-defined rules which identify or confirm pivot points. Usually it is time factor - pivot point gets confirmed after a particular number of candles. This methodology is probably the best when market is moving relatively slow, but when price starts chopping up and down, there is no way the ZigZag follows accurately. On the other hand if you set it too tight (for example pivot confirmation after only 2 or even 1 candle), you will get hundreds of zigzag lines and they will tell you nothing. My point of view is to follow the market. If it has reversed, then it has reversed, and there is no need to wait pre-defined number of candles for the confirmation. Such reversals will always be visible on momentum indicators, such as the most popular MACD. But a single-line moving average can be also good enough to notice reversals. Or my favourite one - QQE, which I borrowed (and improved) from JustUncleL, who borrowed it from Glaz, who borrowed it from... I don't even know where Quantitative Qualitative Estimation originates from. Thanks to all these guys for their input and code. So whichever momentum indicator you choose - yes, there is a pick-your-poison-type selector as in in-famous Moving Average indicators - once it reverses, a highest (or lowest) point from the impulse is caught and ZigZag gets printed. One thing I need to emphasize. This indicator DOES NOT REPAINT. It might look like the lines are a bit delayed, especially when compared to all the other ZigZag indicators on TradingView, but they are actually TRUE. There is a value in this - my indicator prints pivot points and Zigzag exactly on the moment they have been noticed, not earlier faking to be faster than they could be. As a bonus, the indicator marks which impulse had strength in it. It is very nice to see a progressing impulse, but without force - a very likely that reversal on a bigger move is happening. I'm about to publish some more scripts based on this ZigZag algo, so follow me on TradingView to get notified. Enjoy!
Pine Script™ indicator
by Peter_O
120
Trading ABCHello Traders, For a few months I have been getting requests from my followers about ABC pattern and finally I decided to make this indicator. How it works? - It creates Trend Cloud using Simple and Exponential moving averages with the lenghts 50, 100, 150, 200, 20, 40 by default and checks the trend. you can change the lengths as you wish - It also creates ZigZag using the ZigZag Period in the options. - Using last 2 zigzag waves it checks if there is suitable ABC pattern according the Trend, the Min/Max Fibonacci levels and Error Rate - Then it check if the price bounces after this ABC pattern - And if all these conditions met then it plot triangle - If there are multiple bouncing then you can see multiple triangles You can change/set; - Zigzag Period - Fibonacci Max level - Fibonacci Min Level - Error Rate - The Lengths that are used for Moving Averages - Keeping old ABC lines/labels - Show Zigzag and min/max Fibonacci levels - Show Trend Cloud - and colors if you don't want to see old ABC lines/labels you can disable it: if you don't want to see Trend Cloud you can disable it: Zigzag and Fibonacci levels: P.S. if you have new ideas to improve this indicator then let me know please. We together can do this life easier! Enjoy!
Pine Script™ indicator
by LonesomeTheBlue
108
[UTILS] Unit Testing FrameworkTL;DR This script doesn't provide any buy/sell signals. This script won't make you profitable implicitly. This script is intended for utility function testing, library testing, custom assertions. It is free and open-source. Introduction About the idea: is not exclusive, programmers tend to use this method a lot and for a long time. The point is to ensure that parts of a software, "units" (i.e modules, functions, procedures, class methods etc), work as they should, meet they design and behave as intended. That's why we use the term "Unit testing". In PineScript we don't have a lot of entities mentioned above yet. What we have are functions. For example, a function that sums numbers should return a number, a particular sum. Or a professor wrote a function that calculates something or whatever. He and you want to be sure that the function works as expected and further code changes (refactoring) won't break its behaviour. What the professor needs to do is to write unit tests for his function/library of functions. And what you need to do is to check if the professor wrote tests or not. No tests = No code - Total test-driven development Ok, it is not so serious, but very important in software development. And I created a tool for that. I tried to follow the APIs of testing tools/libs/frameworks I worked or work with: Jasmine (Javascript), Mocha/Chai (Javascript), Jest (Javascript), RSpec (Ruby), unittest (Python), pytest (Python) and others. Got something workable but it would be much easier to implement (and it would look much better) if PineScript had a higher-order functions feature. API _describe(suiteName: string) A function to declare a test suite. Each suite with tests may have 2 statuses: ✔️ Passed ❌ Failed A suite is considered to be failed if at least one of the specs in it has failed. _it(specName: string, actual: any, expected: any) A function to run a test. Each test may have 3 statuses: ✔️ Passed ❌ Failed ⛔ Skipped Some examples: _it("is a falsey value", 1 != 2, true) _it("is not a number", na(something), true) _it("should sum two integers", _sum(1, 2), 1) _it("arrays are equal", _isEqual(array.from(1, 2), array.from(1, 2)), true) Remember that both the 'actual' and 'expected' arguments must be of the same type. And a group of _it() functions must be preceded by a _describe() declaration (see in the code). _test(specName: string, actual: any, expected: any) An alias for _it . Does the same thing. _xit(specName: string, actual: any, expected: any) A function to skip a particular test for a while. Doesn't make any comparisons, but the test will appear in the results as skipped. This feature is unstable and may be removed in the future releases. _xtest(specName: string, actual: any, expected: any) An alias for _xit . Does the same thing. _isEqual(id_1: array, id_2: array) A function to compare two arrays for equality. Both arrays must be of the same type. This function doesn't take into account the order of elements in each array. So arrays like (1, 2, 3) and (3, 2, 1) will be equal. _isStrictEqual(id_1: array, id_2: array) A function to compare two arrays for equality. Both arrays must be of the same type. This function is a stricter version of _isEqual because it takes into account the order of elements in each array. So arrays like (1, 2, 3) and (3, 2, 1) won't be equal. Usage To use this script to test your library you need to do the following steps: 1) Copy all the code you see between line #5 and #282 (Unit Testing Framework Core) 2) Place the copied code at the very beginning of your script (but below study()) 3) Start to write suites and tests where your code ends. That's it. NOTE The current version is 0.0.1 which means that a lot of things may be changed on the way to 1.0.0 - the first stable version.
Pine Script™ indicator
by everget
8
Volume Profile Auto [line]This project is about: - VPSV - array.new_line() - array.new_box() VPSV (pine) is one of the rare features that draws lines/figures BETWEEN bars It doesn't run on Pine script, which makes it possible to do such things. I wanted to have something similar while a restriction of Pine script is the impossibility to draw between bars, the only way I could think of is by using line width In this script the higher timeframe is started with several lines (left) and a box, this box goes further until the higher timeframe ends. During the creation of the box, each candle (lower timeframe) in this box (higher timeframe - period) is checked for position and volume, the volume is added to the left line, so when you see a thicker line, this means at that level there is more volume traded. One of the big differences with other volume profiles is that many look back to a previous period, here when a period starts, the lines collect data - volume until the period ends, it is especially very visible in very low TF's (seconds) This is my first script with array.new_line() - array.new_box(), which is a very nice Pine feature! I hope this script can be helpful to see the possibilities Settings: 'Parts' -> amount of lines (left of box) 5 Parts: 15 Parts: 25 Parts: 50 Parts: 'Max Width' -> Sets the max width of the lines 'Automatic Settings' -> Sets the higher time frame automatically, see the tooltip ⓘ for more info The yellow line is the max volume line of that period, last period has a red line (POC), also referring the max. Cheers!
Pine Script™ indicator
by fikira
51
MY:Aggregated Volume BTC:SPOT█ MY Aggregated Volume BTC SPOT This indicator shows a panel to display the Bitcoin Trading Volume of different exchanges. A lot of traders follow the default volume indicator provided by tradingview. This default indicator shows the volume for the current ticker (example BTCUSD:BITSTAMP), but each exchange has its own volume. In a matter of visibility and accessibility, I've decided to aggregate the volume of almost all the Bitcoin exchanges (tickers) in tradingview. Some have been commented out (Kucoin, FTX) due to high volume data which was hiding the other ones. This indicator helps identifying decreasing volume, where the volume comes from (spot or derivatives). A decreasing SPOT volume isn't a good sign as it shows a decrease in the buying pressure. The panel has 1 main configuration : Display mode, showing Aggregated (all exchanges in one bar) or Difference (Stacked bar) The other configuration Legend Item Gap and Legend X Gap is for when the difference mode is selected. It affects the position of the legend. Some might have smaller screens, bigger screens, viewport zoomed in etc. Due to the number of exchanges, and pinescript limitations, I had to split the volume in 2 indicators, the SPOT volume, and the DERIVATIVES volume. The script in this page is specific to the SPOT volume. For the DERIVATIVES, please refer to my other available script. Exchange list : // BINANCE:BTCUSD // BINANCE:BTCUSDT // BINANCE:BTCEUR // COINBASE:BTCUSD // COINBASE:BTCUSDT // COINBASE:BTCEUR // KRAKEN:XBTUSD // KRAKEN:XBTUSDT // KRAKEN:XBTEUR // BITFINEX:BTCUSD // BITFINEX:BTCEUR // HUOBI:BTCUSDT // HUOBI:BTCUSDC // OKEX:BTCUSDT // FTX:BTCUSD DISABLED FOR NOW, TO MUCH VOLUME // FTX:BTCUSDT DISABLED FOR NOW, TO MUCH VOLUME // KUCOIN:BTCUSDT DISABLED FOR NOW, TO MUCH VOLUME // KUCOIN:BTCUSDC DISABLED FOR NOW, TO MUCH VOLUME // GEMINI:BTCUSD // GEMINI:BTCEUR // PHEMEX:BTCUSDT // BITTREX:BTCUSD // BITTREX:BTCUSDT // BITTREX:BTCEUR
Pine Script™ indicator
by Thlem
12
3Commas BotBjorgum 3Commas Bot A strategy in a box to get you started today With 3rd party API providers growing in popularity, many are turning to automating their strategies on their favorite assets. With so many options and layers of customization possible, TradingView offers a place no better for young or even experienced coders to build a platform from to meet these needs. 3Commas has offered easy access with straight forward TradingView compatibility. Before long many have their brokers hooked up and are ready to send their alerts (or perhaps they have been trying with mixed success for some time now) only they realize there might just be a little bit more to building a strategy that they are comfortable letting out of their sight to trade their money while they eat, sleep, etc. Many may have ideas for entry criteria they are excited to try, but further questions arise... "What about risk mitigation?" "How can I set stop or limit orders?" "Is there not some basic shell of a strategy that has laid some of this out for me to get me going?" Well now there is just that. This strategy is meant for those that have begun to delve into the world of algorithmic trading providing a template that offers risk defined positions complete with stops, limit orders, and even trailing stops should one so choose to employ any of these criteria. It provides a framework that is easily manipulated (with some basic working knowledge of pine coding) to encompass ones own ideas and entry criteria, while also providing an already functioning strategy. The default settings have a basic 1:1 risk to reward ratio, which sets a limit and a stop equal distance from the entry. The entry is a simple MA cross (up for long, down for short). There a variety of MA's to choose from and the user can define the lengths of the averages. The ratio can be adjusted from the menu along with a volatility based adder (ATR) that helps to distance a stop from support or resistance. These values are calculated off the swing low/high of the user defined lookback period. Risk is calculated from position entry to stop, and projected upwards to the limit as a function of the desired risk to reward ratio. Of note: the default settings include 0.05% commissions. Competitive commissions of the leading cryptocurrency exchanges are .1% round trip (one buy and one sell) for market orders. There is also some slippage to allow time for alerts to be sent and orders to fill giving the back test results a more accurate representation of real time conditions. Its recommended to research the going rates for your exchange and set them to default for the strategy you use or build. To get started a user would: 1) Make a copy of the code and paste in their bot keys in the area provided under the "3Comma Keys" section - eg. Long bot "start deal" copied from 3commas in to define "Long" etc. (code is commented) 2) Place alert on desired asset with desired settings ensuring to select "Order fills and alert() function calls" 3) Paste webhook into the webhook box and select webhook URL alerts (3rd party provided webhook) 3) Delete contents of alert message box and replace with {{strategy.order.alert_message}} and nothing else - the codes will be sent to the webhook appropriately as the strategy enters and exits positions. Only 1 alert is needed settings used for the display image: 1hr chart on BTCUSD -ATR stop -Risk adjustment 1.2 -ATR multiplier 1.3 -RnR 0.6 -MAs HEMA/SMA -MA Length 50/100 -Order size percent of equity -Trail trigger 60% of target Experiment with your own settings on your crypto of choice or implement your own code! Implementing your trailing stop (optional) Among the options for possible settings is a trailing stop. This stop will ratchet higher once triggered as a function of the Average True Range (ATR). There is a variable level to choose where the user would like to begin trailing the stop during the trade. The level can be assigned with a decimal between 0 and 1 (eg. 0.5 = 50% of the distance between entry and the target which must be exceeded before the trail triggers to begin). This can allow for some dips to occur during the trade possibly keeping you in the trade for longer, while potentially reducing risk of drawdown over time. The default for this setting is 0 meaning unless adjusted, the trail will trigger on entry if the trailing stop exit method is selected. An example can be seen below: Again, optional as well is the choice to implement a limit order. If one were to select a trailing stop they could choose not to set a limit, which could allow a trail to run further until hit. Drawdowns of this strategy would be foregoing locking gains at highs on target on other trades. This is a trade-off the user can decide on and test. An example of this working in favor can be observed below: Conclusion Although a simple strategy is implemented here, the benefits of this script allow a user a starting platform to build their strategies from with built in risk mitigation. This allows the user to sidestep some of the potential difficulties' that can arise while learning Pine and taking on the endeavor of automating their trading strategies. It is meant as an aid, a structure, and an educational piece that can be seen as a "pick-up-and-go" strategy with easy 3Commas compatibility. Additionally, this can help users become more comfortable with strategy alert messages and sending strings in the form of alerts from Pine. As well, FAQs are often littered with questions regarding "strategy.exit" calls, how to implement stops. how to properly set a trailing stop based on ATR, and more. The time this can save an individual to get started is likely of the best "take-aways" here. Happy trading
Pine Script™ strategy
by Bjorgum
185
Monthly Returns in PineScript StrategiesI'm not 100% satisfied with the strategy performance output I receive from TradingView. Quite often I want to see something that is not available by default. I usually export raw trades/metrics from TradingView and then do additional analysis manually. But with tables, you can build additional metrics and tools for your strategies quite easily. This script will just show a table with monthly/yearly performance of your script. Quite a lot of traders/investors used to look at returns like that. Also, it might help you to identify periods of time when your strategy performed good/bad than expected and try to analyze that better. The script is very simple and I believe you can easily apply it to your own strategies. Disclaimer Please remember that past performance may not be indicative of future results. Due to various factors, including changing market conditions, the strategy may no longer perform as well as in historical backtesting. This post and the script don’t provide any financial advice.
Pine Script™ strategy
by QuantNomad
78
Zigzag CloudThis is Bollinger Band built on top of Zigzags instead of regular price + something more. Indicator presents 7 lines and cloud around it. This can be used to visualize how low or high price is with respect to its past movement. Middle line is moving average of last N zigzag pivots Lines adjacent to moving average are also moving averages. But, they are made of only pivot highs and pivot lows. Means, line above moving average is pivot high moving average and line below moving average is pivot low moving average. Lines after pivot high/low moving averages are upper and lower bolllinger bands based on Moving Average Line with 2 standard deviation difference. Outermost lines are bollinger band top of Moving average pivot high and bollinger band bottom of moving average pivot low.
Pine Script™ indicator
by Trendoscope
27
MESA Stochastic Multi LengthJohn Ehler's MESA Stochastic uses super smoothing to give solid signals. This indicator uses the same rules as every other Stochastic indicator so it would be worth looking into if you are not already familiar with reading a Stochastic. There are 4 different lengths displayed to give traders an edge on reading the market. This is a great tool to analyze waves and find tops and bottoms. It gives great pump and dump signals and even helps filter out bad trades when used with other indicators such as Boom Hunter. Below are some examples of signals to look out for: oo
Pine Script™ indicator
by veryfid
42
Fast Fourier Transform (FFT) FilterDear friends! I'm happy to present an implementation of the Fast Fourier Transform (FFT) algorithm. The script uses the FFT procedure to decompose the input time series into its cyclical constituents, in other words, its frequency components , and convert it back to the time domain with modified frequency content, that is, to filter it. Input Description and Usage Source and Length : Indicates where the data comes from and the size of the lookback window used to build the dataset. Standardize Input Dataset : If enabled, the dataset is preprocessed by subtracting its mean and normalizing the result by the standard deviation, which is sometimes useful when analyzing seasonalities. This procedure is not recommended when using the FFT filter for smoothing (see below), as it will not preserve the average of the dataset. Show Frequency-Domain Power Spectrum : When enabled, the results of Fourier analysis (for the last price bar!) are plotted as a frequency-domain power spectrum , where “power” is a measure of the significance of the component in the dataset. In the spectrum, lower frequencies (longer cycles) are on the right, higher frequencies are on the left. The graph does not display the 0th component, which contains only information about the mean value. Frequency components that are allowed to pass through the filter (see below) are highlighted in magenta . Dominant Cycles, Rows : If this option is activated, the periods and relative powers of several dominant cyclical components that is, those that have a higher power, are listed in the table. The number of the component in the power spectrum (N) is shown in the first column. The number of rows in the table is defined by the user. Show Inverse Fourier Transform (Filtered) : When enabled, the reconstructed and filtered time-domain dataset (for the last price bar!) is displayed. Apply FFT Filter in a Moving Window : When enabled, the FFT filter with the same parameters is applied to each bar. The last data point of the reconstructed​ and filtered dataset is used to build a new time series. For example, by getting rid of high-frequency noise, the FFT filter can make the data smoother. By removing slowly evolving low-frequency components (including non-periodic constituents), one can reveal and analyze shorter cycles. Since filtering is done in real-time in a moving window (similar to the moving average), the modified data can potentially be used as part of a strategy and be subjected to other technical indicators. Lowest Allowed N : Indicates the number of the lowest frequency component used in the reconstructed time series. Highest Allowed N : Indicates the number of the highest frequency component used in the reconstructed time series. Filtering Time Range block: Specifies the time range over which real-time FFT filtering is applied. The reason for the presence of this block is that the FFT procedure is relatively computationally intensive. Therefore, the script execution may encounter the time limit imposed by TradingView when all historical bars are processed. As always, I look forward to your feedback! Also, leave a comment if you'd be interested in the tutorial on how to use this tool and/or in seeing the FFT filter in a strategy. ​​
Pine Script™ indicator
by tbiktag
71
Multi ZigZag Harmonic PatternsCombining Multizigzag with harmonic patterns - this script generates harmonic patterns based on multiple deapth zigzags. Input parameter allows to chose which Zigzag to be included in pattern identification and set different length, line color, width and style for each Zigzag combinations. Pattern rules are as below: Gartley xab = 0.618 0.382 <= abc <= 0.886 1.272 <= bcd <= 1.618 OR xad = 0.786 Crab 0.382 <= xab <= 0.618 0.382 <= abc <= 0.886 2.24 <= bcd <= 3.618 OR xad = 1.618 Deep Crab xab = 0.886 0.382 <= abc <= 0.886 2.0 <= bcd <= 3.618 OR xad = 1.618 Bat 0.382 <= xab <= 0.50 0.382 <= abc <= 0.886 1.618 <= bcd <= 2.618 OR xad = 0.886 Butterfly xab = 0.786 0.382 <= abc <= 0.886 1.618 <= bcd <= 2.618 OR 1.272 <= xad <= 2.618 Shark xab = 0.786 1.13 <= abc <= 1.618 1.618 <= bcd <= 2.24 OR 0.886 <= xad <= 1.13 Cypher 0.382 <= xab <= 0.618 1.13 <= abc <= 1.414 1.272 <= bcd <= 2.0 OR xad = 0.786 Three Drives oxa = 0.618 1.27 <= xab <= 1.618 abc = 0.618 1.27 <= bcd <= 1.618 5-0 1.13 <= xab <= 1.618 1.618 <= abc <= 2.24 bcd = 0.5 Related scripts are present here:
Pine Script™ indicator
by Trendoscope
111
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***
Pine Script™ indicator
by ChrisMoody
145
KINSKI Volume Regression TrendRegression trends are typically used to determine when a price is unusually far from its baseline. The script calculates the linear regression of volume and price to determine the trend direction and strength. This can be used to determine the volume support for upward/downward trends. As a special feature, this indicator allows you to choose from three (as of 07/20/2021) templates with special presets. The following templates are available: "Precise" (Period: 4, Smoothing Factor Type: "DISABLED", Smoothing Factor Length = 1). "Smooth" (Period: 4, Smoothing Factor Type: "RMA", Smoothing Factor Length = 2) "Long Term (Period: 20, Smoothing Factor Type: "DISABLED", Smoothing Factor Length = 1) In the selection for templates, the option "DISABLED" can also be selected. Then the user-defined settings selectable under it take effect. There are the following setting options. "Length": Adjustable period "Smoothing Factor: Type": Type of moving average "Smoothing Factor: Length": Adjustable period Other setting options are: Color codes: The color codes are explained in the settings Display types: "Columns", "Histogram", "Area", "Line", "Stepline"
Pine Script™ indicator
by KINSKI
15
Probability Distribution HistogramProbability Distribution Histogram During data exploration it is often useful to plot the distribution of the data one is exploring. This indicator plots the distribution of data between different bins. Essentially, what we do is we look at the min and max of the entire data set to determine its range. When we have the range of the data, we decide how many bins we want to divide this range into, so that the more bins we get, the smaller the range (a.k.a. width) for each bin becomes. We then place each data point in its corresponding bin, to see how many of the data points end up in each bin. For instance, if we have a data set where the smallest number is 5 and the biggest number is 105, we get a range of 100. If we then decide on 20 bins, each bin will have a width of 5. So the left-most bin would therefore correspond to values between 5 and 10, and the bin to the right would correspond to values between 10 and 15, and so on. Once we have distributed all the data points into their corresponding bins, we compare the count in each bin to the total number of data points, to get a percentage of the total for each bin. So if we have 100 data points, and the left-most bin has 2 data points in it, that would equal 2%. This is also known as probability mass (or well, an approximation of it at least, since we're dealing with a bin, and not an exact number). Usage This is not an indicator that will give you any trading signals. This indicator is made to help you examine data. It can take any input you give it and plot how that data is distributed. The indicator can transform the data in a few ways to help you get the most out of your data exploration. For instance, it is usually more accurate to use logarithmic data than raw data, so there is an option to transform the data using the natural logarithmic function. There is also an option to transform the data into %-Change form or by using data differencing. Another option that the indicator has is the ability to trim data from the data set before plotting the distribution. This can help if you know there are outliers that are made up of corrupted data or data that is not relevant to your research. I also included the option to plot the normal distribution as well, for comparison. This can be useful when the data is made up of residuals from a prediction model, to see if the residuals seem to be normally distributed or not.
Pine Script™ indicator
by lejmer
71
{Gunzo} Market Trading Sessions (Tokyo, London, New York)Market Trading Sessions is a tool designed to help traders to find the best times of the day for price action trading. It displays non-overlapping visuals for the major trading sessions : Oceania, Asia, Europe, and USA. OVERVIEW : This tool has been designed to match all the following requirements that I needed for optimal usage : Display opening and closing of main markets See clearly market sessions (non-overlapping colors) Display Sydney session if wanted Display GMT hours and days Visually pleasing design and colors Highly configurable As I had trouble finding a script matching all these criteria, I created this tool and I'm sharing it with the TradingView community, hoping you will find it useful too. SETTINGS : Display market sessions on weekends : Display theoretical market sessions times on the weekend which can be useful for non forex markets. Display session for Oceania\Sydney : Display "Oceania\Sydney" trading session Display session for Asia\Tokyo : Display "Asia\Tokyo" trading session Display session for Europe\London : Display "Europe\London" trading session Display session for USA\New York : Display "USA\New York" trading session Display session names : Display names of the session on the visual Oceania color : Configurable color for the "Oceania\Sydney" sessions Asia color : Configurable color for the "Asia\Tokyo" sessions Europe color : Configurable color for the "Europe\London" sessions USA color : Configurable color for the "USA\New York" sessions Background color : Configurable color for the table background Border color : Configurable color for the table borders Text color : Configurable color for the table text Header color : Configurable color for the table header (even days) Header color (alternate) : Configurable color for the table header (odd days)
Pine Script™ indicator
by Gunzo_TV
25
Volume Profile / Fixed RangeHello All, This script calculates and shows Volume Profile for the fixed range . Recently we have box.new() feature in Pine Language and it's used in this script as an example. Thanks to Pine Team and Tradingview!.. Sell/Buy volumes are calculated approximately!. Options: "Number of Bars" : Number of the bars that volume profile will be calculated/shown "Row Size" : Number of the Rows "Value Area Volume % " : the percent for Value Area and there are other options for coloring and POC line style Enjoy!
Pine Script™ indicator
by LonesomeTheBlue
168
Portfolio Backtester Engine█  OVERVIEW Portfolio Backtester Engine (PBTE). This tool will allow you to backtest strategies across multiple securities at once. Allowing you to easier understand if your strategy is robust. If you are familiar with the PineCoders backtesting engine , then you will find this indicator pleasant to work with as it is an adaptation based on that work. Much of the functionality has been kept the same, or enhanced, with some minor adjustments I made on the account of creating a more subjectively intuitive tool. █  HISTORY The original purpose of the backtesting engine (`BTE`) was to bridge the gap between strategies and studies . Previously, strategies did not contain the ability to send alerts, but were necessary for backtesting. Studies on the other hand were necessary for sending alerts, but could not provide backtesting results . Often, traders would have to manage two separate Pine scripts to take advantage of each feature, this was less than ideal. The `BTE` published by PineCoders offered a solution to this issue by generating backtesting results under the context of a study(). This allowed traders to backtest their strategy and simultaneously generate alerts for automated trading, thus eliminating the need for a separate strategy() script (though, even converting the engine to a strategy was made simple by the PineCoders!). Fast forward a couple years and PineScript evolved beyond these issues and alerts were introduced into strategies. The BTE was not quite as necessary anymore, but is still extremely useful as it contains extra features and data not found under the strategy() context. Below is an excerpt of features contained by the BTE: """ More than `40` built-in strategies, Customizable components, Coupling with your own external indicator, Simple conversion from Study to Strategy modes, Post-Exit analysis to search for alternate trade outcomes, Use of the Data Window to show detailed bar by bar trade information and global statistics, including some not provided by TV backtesting, Plotting of reminders and generation of alerts on in-trade events. """ Before I go any further, I want to be clear that the BTE is STILL a good tool and it is STILL very useful. The Portfolio Backtesting Engine I am introducing is only a tangental advancement and not to be confused as a replacement, this tool would not have been possible without the `BTE`. █  THE PROBLEM Most strategies built in Pine are limited by one thing. Data. Backtesting should be a rigorous process and researchers should examine the performance of their strategy across all market regimes; that includes, bullish and bearish markets, ranging markets, low volatility and high volatility. Depending on your TV subscription The Pine Engine is limited to 5k-20k historical bars available for backtesting, which can often leave the strategy results wanting. As a general rule of thumb, strategies should be tested across a quantity of historical bars which will allow for at least 100 trades. In many cases, the lack of historical bars available for backtesting and frequency of the strategy signals produces less than 100 trades, rendering your strategy results inconclusive. █  THE SOLUTION In order to be confident that we have a robust strategy we must test it across all market regimes and we must have over 100 trades. To do this effectively, researchers can use the Portfolio Backtesting Engine (PBTE). By testing a strategy across a carefully selected portfolio of securities, researchers can now gather 5k-20k historical bars per security! Currently, the PTBE allows up to 5 securities, which amounts to 25k-100k historical bars. █  HOW TO USE 1 — Add the indicator to your chart.  • Confirm inputs. These will be the most important initial values which you can change later by clicking the gear icon ⚙ and opening up the settings of the indicator. 2 — Select a portfolio.  • You will want to spend some time carefully selecting a portfolio of securities.    • Each security should be uncorrelated.    • The entire portfolio should contain a mix of different market regimes.     You should understand that strategies generally take advantage of one particular type of market regime. (trending, ranging, low/high volatility)    For example, the default RSI strategy is typically advantageous during ranging markets, whereas a typical moving average crossover strategy is advantageous in trending markets.    If you were to use the standard RSI strategy during a trending market, you might be selling when you should be buying.    Similarily, if you use an SMA crossover during a ranging market, you will find that the MA's may produce many false signals.    Even if you build a strategy that is designed to be used only in a trending market, it is still best to select a portfolio of all market regimes    as you will be able to test how your strategy will perform when the market does something unexpected. 3 — Test a built-in strategy or add your own.    • Navigate to gear icon ⚙ (settings) of strategy.    • Choose your options.       • Select a Main Entry Strat and Alternate Entry Strat .          • If you want to add your own strategy, you will need to modify the source code and follow the built-in example.          • You will only need to generate (buy 1 / sell -1/ neutral 0) signals.       • Select a Filter , by default these are all off.       • Select an Entry Stop - This will be your stop loss placed at the trade entry.       • Select Pyamiding - This will allow you to stack positions. By default this is off.       • Select Hard Exits - You can also think of these as Take Profits.    • Let the strategy run and take note of the display tables results.       • Portfolio - Shows each security.          • The strategy runs on each asset in your portfolio.          • The initial capital is equally distributed across each security.           So if you have 5 securities and a starting capital of 100,000$ then each security will run the strategy starting with 20,000$           The total row will aggregate the results on a bar by bar basis showing the total results of your initial capital.       • Net Profit (NP) - Shows profitability.       • Number of Trades (#T) - Shows # of trades taken during backtesting period.          • Typically will want to see this number greater than 100 on the "Total" row.       • Average Trade Length (ATL) - Shows average # of days in a trade.       • Maximum Drawdown (MD ) - Max peak-to-valley equity drawdown during backtesting period.          • This number defines the minimum amount of capital required to trade the system.          • Typically, this shouldn’t be lower than 34% and we will want to allow for at least 50% beyond this number.       • Maximum Loss (ML) - Shows largest loss experienced on a per-trade basis.          • Normally, don’t want to exceed more than 1-2 % of equity.       • Maximum Drawdown Duration (MDD) - The longest duration of a drawdown in equity prior to a new equity peak.          • This number is important to help us psychologically understand how long we can expect to wait for a new peak in account equity.       • Maximum Consecutive Losses (MCL) - The max consecutive losses endured throughout the backtesting period.          • Another important metric for trader psychology, this will help you understand how many losses you should be prepared to handle.       • Profit to Maximum Drawdown (P:MD) - A ratio for the average profit to the maximum drawdown.          • The higher the ratio is, the better. Large profits and small losses contribute to a good PMD.          • This metric allows us to examine the profit with respect to risk.       • Profit Loss Ratio (P:L) - Average profit over the average loss.          • Typically this number should be higher in trend following systems.          • Mean reversion systems show lower values, but compensate with a better win %.       • Percent Winners (% W) - The percentage of winning trades.          • Trend systems will usually have lower win percentages, since statistically the market is only trending roughly 30% of the time.          • Mean reversion systems typically should have a high % W.       • Time Percentage (Time %) - The amount of time that the system has an open position.          • The more time you are in the market, the more you are exposed to market risk, not to mention you could be using that money for something else right?       • Return on Investment (ROI) - Your Net Profit over your initial investment, represented as a percentage.          • You want this number to be positive and high.       • Open Profit (OP) - If the strategy has any open positions, the floating value will be represented here.       • Trading Days (TD) - An important metric showing how many days the strategy was active.          • This is good to know and will be valuable in understanding how long you will need to run this strategy in order to achieve results. █  FEATURES These are additional features that extend the original `BTE` features. - Portfolio backtesting. - Color coded performance results. - Circuit Breakers that will stop trading. - Position reversals on exit. (Simulating the function of always in the market. Similar to strategy.entry functionality) - Whipsaw Filter - Moving Average Filter - Minimum Change Filter - % Gain Equity Exit - Popular strategies, (MACD, MA cross, supertrend) Below are features that were excluded from the original `BTE` - 2 stage in-trade stops with kick-in rules (This was a subjective decision to remove. I found it to be complex and thwarted my use of the `BTE` for some time.) - Simple conversion from Study to Strategy modes. (Not possible with multiple securities) - Coupling with your own external indicator (Not really practical to use with multiple securities, but could be used if signals were generated based on some indicator which was not based on the current chart) - Use of the Data Window to show detailed bar by bar trade information and global statistics. - Post Exit Analysis. - Plotting of reminders and generation of alerts on in-trade events. - Alerts (These may be added in the future by request when I find the time.) █  THANKS The whole PineCoders team for all their shared knowledge and original publication of the BTE and Richard Weismann for his ideas on building robust strategies. ═════════════════════════════════════════════════════════════════════════
Pine Script™ indicator
by pAulseperformance
36