Get started

Pinescript

Rate Pine ScriptWhat do you think of Pine Script? Here's your chance to let off some steam if your frustrated with the limitations of Pine Script. This script stores a text string in a array. Unfortunately tradingview doesn't think anything useful can be done with strings. This is merely a demo of storing a string in an array. There currently seems to be no way to get an input.string and parse it. What do you think of Pine Script? Here's your chance to let off some steam if your frustrated with the limitations of Pine Script.
Pine Script™ indicator
by zeldromo
FundCandlesV1sloth288FundCandlesV1sloth288 is an indicator I decided to put together so I can track how funds are doing on $GVT Genesis Vision. Using a standard MACD or RSI indicator you can change source to use the FundsCandles values to determine if its a good time to enter or exit different funds on the platform. What you need to know... Currently all securities need to pair the same, (USD / BTC ). Security 01, 02, 03 etc etc to maximum of 10 need to be in "BINANCE:LINKUSD" format. Manually need to input circulating supply from CMC to get the proper ratios for index. Allocation is the % of the funds exposure to said security. Inputting the values does not track previous reallocation's, the whole chart will be if the history of the fund was using up to date settings. Values on the right is the Marketcap of the fund. Standard settings is of Oracle Basket on the platform made by Somnium Funds as of Aug 13 2020. Next update will be after GV includes traditional stocks onto the platform for managers to diversify their current allocations into them.
Pine Script™ indicator
by sloth288
1
Proper Round Functions [QuantNomad]Round function in PineScript is very simple and allows you to round numbers only to the closest integer number. This is a bit irritating because I very often have to round numbers to some decimal places and not integer. So I created 2 functions I use all the time and now sharing them with you. roundn - rounds the values in its first argument to the specified number of decimal places. roundtick - rounds the values to current symbol mintick I hope they will be useful for you.
Pine Script™ indicator
by QuantNomad
16
Barssince Context TestThis is just published for visibility as a public service until the Pine devs are able to fix or document this behavior. The barssince() function returns different values when inside a conditional context. As long as it can be documented (and relied upon), this could be a pretty cool feature, but right now this is now how I read the help documentation to describe the function's intended behavior. Anyway, in the script you'll see that test and test2 agree on red bars, but on green bars test gets a much lower value, which was pretty shocking to me until I traced down this particular cause within my larger script.
Pine Script™ indicator
by Lemrin
2
Multi-Timeframe Configuration DemoThis is a developer friendly solution to the current PineScript limitation of not being able to easily configure presets for multiple timeframes. If you're developing multi-timeframe strategies then you've no doubt done battle with built-in `input` function which only allows for a single default value. You've probably come up with all kinds of fancy workarounds, including messy hardcoding, and even gritting your teeth and patiently reentering all the necessary values each time you refresh the chart or change the timeframe. The last one is my personal favourite. As you can see in the code below we have defined a `usePresets` condition which tells the script to use our preset configuration, otherwise the default `input` values will be used. If `usePresets` is false then we use our presets which are defined in a (fairly) easy to read condition chain with the help of some basic timeframe utility functions. Obviously this is nothing groundbreaking, but its helped me clean up my scripts a bit, so hopefully it will help you too.
Pine Script™ indicator
by sourcey
1
Why is it ok to backtest on TradingView from now on!TradingView backtester has bad reputation. For a good reason - it was producing wrong results, and it was clear at first sight how bad they were. But this has changed. Along with many other improvements in its PineScript coding capabilities, TradingView fixed important bug, which was the main reason for miscalculations. TradingView didn't really speak out about this fix, so let me try :) Have a look at this short code of a swing trading strategy (PLEASE DON'T FOCUS ON BACKTEST RESULTS ATTACHED HERE - THEY DO NOT MATTER). Sometimes entry condition happens together with closing condition for the already ongoing trade. Example: the condition to close Long entry is the same as a condition to enter Short. And when these two aligned, not only a Long was closed and Short was entered (as intended), but also a second Short was entered, too!!! What's even worse, that second short was not controlled with closing conditions inside strategy.exit() function and it very often lead to losses exceeding whatever was declared in "loss=" parameter. This could not have worked well... But HOORAY!!! - it has been fixed and won't happen anymore. So together with other improvements - TradingView's backtester and PineScript is now ok to work with on standard candlesticks :) Yep, no need to code strategies and backtest them on other platforms anymore. ---------------- Having said the above, there are still some pitfalls remaining, which you need to be aware of and avoid: Don't backtest on HeikenAshi, Renko, Kagi candlesticks. They were not invented with backtesting in mind. There are still using wrong price levels for entries and therefore producing always too good backtesting results. Only standard candlesticks are reliable to backtest on. Don't use Trailing Stop in your code. TradingView operates only on closed candlesticks, not on tick data and because of that, backtester will always assume price has first reached its favourable extreme (so 'high' when you are in Long trade and 'low' when you are in Short trade) before it starts to pull back. Which is rarely the truth in reality. Therefore strategies using Trailing Stop are also producing too good backtesting results. It is especially well visible on higher timeframe strategies - for some reason your strategy manages to make gains on those huge, fat candlesticks :) But that's not reality. "when=" inside strategy.exit() does not work as you would intuitively expect. If you want to have logical condition to close your trade (for example - crossover(rsi(close,14),20)) you need to place it inside strategy.close() function. And leave StopLoss + TakeProfit conditions inside strategy.exit() function. Just as in attached code. If you're working with pyramiding, add "process_orders_on_close=ANY" to your strategy() script header. Default setting ("=FIFO") will first close the trade, which was opened first, not the one which was hit by Stop-Loss condidtion. ---------------- That's it, I guess :) If you are noticing other issues with backtester and would like to share, let everyone know in comments. If the issue is indeed a bug, there is a chance TradingView dev team will hear your voice and take it into account when working on other improvements. Just like they heard about the bug I described above. P.S. I know for a fact that more improvements in the backtesting area are coming. Some will change the game even for non-coding traders. If you want to be notified quickly and with my comment - gimme "follow".
Pine Script™ strategy
by Peter_O
27
Market EKGShort Summary This indicator takes the differences in the previous 4 period OHLC inputs, and compares them to the previously closed candle input. The difference is then placed into an oscillator that when all four inputs are scrolled back on, shows an EKG appearing oscillator / volatility measure for traders to use on indexes, tickers and markets that do not allow typical volume based indicators. Full Summary Named for its similar appearance to an EKG medical chart, this script takes the difference in relative averages of previous periods in a trend , and compares it to the most recent period input. This can be used as a price based volatility measure, useful in markets that may be limited by no valume measures or other indexes where volatility is useful to meeasure but will not allow volume initializations. Steps taken Taking Previous Period OHLC Taking Previous 3 Periods OHLC Avgs Difference Between #1 & #2 (Comparing most recent confirmation to relative trend Plot Results This RSI Script is intended for public use and can be shared / implemented as needed Questions? I do not monitor my TradingView inbox. See email address in signature at the bottom of this page for contact information. Use this script and its calculations as needed! No permission required. Cheers,
Editors' picks
Pine Script™ indicator
by kingthies
3
4K Notepad++ UDL Add-on for Pine Script v4.0FIRST OF ALL, THIS NOT AN INDICATOR! This is in XML format as a "utilitarian developer tool add-on" for Notepad++ editor for viewing Pine Script on 4K screens, but 4K isn't REQUIRED to use this. For all Notepad++ enthusiasts out there utilizing Pine Script, I present a UDL(User Defined Language)... for Notepad++... for Pine Script v4.0... on 4K LCDs. This is only for a dark background in Notepad++ editor, FYI. I would also like to mention, I used a 42" 4K LCD at this time of initial publication. NOTICE: Please be sure to strip the "//" from this code on every line where the XML is commented with Pine Script comment operators(//) before saving to drive as an XML(*.xml) file. This may be done easily within the Pine Editor using ' CTRL + / ' after a click/drag selection of the bulk XML code. Pine Script commenting will then be stripped out of the XML following after the beginning/closing tags and . The entire section below entitled "Notepad++ UDL INSTALLATION INSTRUCTIONS" is not required for importation into Notepad++. These are just HOW TOs concerning export/configuration in Notepad++ in the XML comments , and will be ignored if it's included during the import procedure, no worries. I will update this as PSv4.0 evolves and time provides itself to me. Any anomalies discovered, please respectfully contact me privately via TV chat to discuss any ideas/concerns. With all that aforementioned said, I believe this will be very useful to Pine Script developers who use Notepad++ editor in tandem with Pine Editor, further unleashing the "Power of Pine" on this planet. NOTICE: Copy pasting bandits who may be having nefarious thoughts, DO NOT attempt this, because this may violate Tradingview's terms, conditions and/or house rules. "WE" are always watching the TV community vigilantly for mischievous behaviors and actions that exploit well intended authors for the purpose of unscrupulously increasing brownie points in reputation scores. Hiding behind a "protected" wall may not protect you from investigation and account penalization by TV staff. Be respectful, and don't just throw a meaningless feature in there branding it as "your" gizmo. Fair enough? Alrighty then... I firmly believe in "innovating" future state-of-the-art indicators, and please contact me if you wish to do so. The comments section below is solely just for commenting and other remarks, ideas, compliments, etc... regarding only this indicator, not others. When available time provides itself, I will consider your inquiries, thoughts, and concepts presented below in the comments section if you do have any questions or comments regarding this indicator. When my indicators achieve more prevalent use by TV members, I may implement more ideas when they present themselves as worthy additions. As always, "Like" it if you simply just like it with a proper thumbs up, and also return to my scripts list occasionally for additional postings. Have a profitable future everyone!
Pine Script™ indicator
by ImmortalFreedom
29
PtahX 3 EMA IndicatorA Basic 3 EMA Study / Indicator built in version 4 of Pinescript. Individual color changing lines based on the position of the price (close) relative to each specific EMA Alerts can be set for either - All Signals Bullish - All Signals Bearish I try to keep my code clean and readable with comments and always enjoy seeing what others do with it. Please give me a thumbs up if you find it usefull & as always I hope you have very good luck with your trades!! :) Cheers PtahX
Pine Script™ indicator
by PtahX
2
QuantCat Intraday Strategy (15M)QuantCat Intraday Strategy This strategy is designed to be used on the 15 minute time frame, on liquid x/btc pairs and BTC/USD. It works by having 2 moving averages, automatic stop loss calculation, and taking positions on MA crosses and MA zone bounces for confirmation. Stoploss is so crucial to minimise any damage from huge unexpected candles, the strategies can just be used for entries as well, you don't have to stick to the exact formula- of the long and short system, but this by itself is profitable. The system nets positive results on -BTC/USD -ETH/BTC -LTC/BTC -XRP/BTC There is a small element of trend filtering also for the MA's, but I found adding it in actually hindered performance when testing and training the strategies unless it was using a loose value. You can get live alerts for this strategy and speak to our developers by joining our server on discord! (Link in signature)
Pine Script™ strategy
by QuantCat
Template For Custom FIR Filters - Make Your Moving AverageIntroduction FIR filters (finite impulse response) are widely used in technical analysis, there is the simple or arithmetic moving average, the triangular, the weighted, the least squares...etc. A FIR filter is characterized by the fact that its impulse response (the output of a filter using an impulse as input) is finite, this mean that the impulse response won't have infinite outputs unlike IIR filters. They are extremely simple to design to, even without the Fourier transform, this is why i post this template that will let you create custom filters from step responses. Don't hesitate to post your results. How It Works Originally you create your filters from the frequency response you want your filter to have, this is because the inverse Fourier transform of the frequency response is the filter impulse response. After that step you use convolution (convolution is the sum of the product between the signal and the impulse response) and you will have your filter. But we don't have Fourier transforms in pine so how can we possibly make FIR filters from convolution ? Well here the thing, the impulse response is the derivative of the step response and the step response is the sum of the impulse response, this mean we can create filters from step responses. Step response of a moving average. Step responses are easy to design, you just need a function that start at 0 and end up at 1. How To Use The Template All the work is done for you, the only thing you need to do is to enter your function at line 5 : f(x)=> your function For example if you want your filter to have a step response equal to sqrt(x) just enter : f(x)=> sqrt(x) This will give the following filter output : You can create custom step responses from online graphing tools like fooplot or wolfram alpha, i recommend fooplot. You can also design your filter step response from the line 14/15/16, b will be your filter step response, just use a , for example b = pow(a,2) , then replace output in plot by b and use overlay false, you can also plot step , if you like your step response copy the content of b and paste after f(x) => . Filter Characteristics The impulse response determine how many of a certain signal you want in your filter, this is also called weighting, you can think of filter design as cooking where your ingredients are the the signal at different periods and the impulse response determine how many of an ingredient you must include in the recipe. The step response can also tell you about your filter characteristics, for example : This one converge faster to the step function, this mean that the filter will have less lag. However this one converge slower to the step function, this mean the filter might have more lag but could be smoother. Be aware that you must find a good weighting balance, else you can have output equals to the signal or just a delayed version of the signal without smoothing. Real Case Lets design a sine weighted moving average (swma), this FIR filter use the first 180 degrees of a sine wave function as impulse response. Impulse response of the swma. We can design it from the step response without much problems, remember that the impulse response is the derivative of the step response, therefore the derivative of the step response is equal to the first 180 degrees of a sine wave, the derivative of the cosine function is a sine function, therefore : f(x)=> .5*(1 - cos(x*pi)) And voila. Designing A BandPass Filter The bandpass filter like a low-pass and high pass filter, you can think of it as a smooth oscillator. To design a bandpass filter your step response must be bell shaped, or starting at 0 and ending at 0, for example : f(x)=>sin(x*pi) give : Conclusion Just use fooplot and experiment, you could get nice filters, i will try to post some using this template but it would be really nice to have other people use it. If you need further help pm me. Thanks for reading !
Pine Script™ indicator
by alexgrover
19
Pinescript v3 Compatibility Framework (v4 Migration Tool)Pinescript v3 Compatibility Framework (v4 Migration Tool) This code makes most v3 scripts work in v4 with only a few minor changes below. Place the framework code before the first input statement. You can totally delete all comments. Pros: - to port to v4 you only need to make a few simple changes, not affecting the core v3 code functionality Cons: - without #include - large redundant code block, but can be reduced as needed - no proper syntax highlighting, intellisence for substitute constant names Make the following changes in v3 script: 1. standard types can't be var names, color_transp can't be in a function, rename in v3 script: color() => color.new() bool => bool_ integer => integer_ float => float_ string => string_ 2. init na requires explicit type declaration float a = na color col = na 3. persistent var init (optional): s = na s := nz(s , s) // or s := na(s ) ? 0 : s // can be replaced with var s var s = 0 s := s + 1 ___________________________________________________________ Key features of Pinescript v4 (FYI): 1. optional explicit type declaration/conversion (you still can't cast series to int) float s 2. persistent var modifier var s var float s 3. string series - persistent strings now can be used in cond and output to screen dynamically 4. label and line objects - can be dynamically created, deleted, modified using get/set functions, moved before/after the current bar - can be in if or a function unlike plot - max limit: 50-55 label, and 50-55 line drawing objects in addition to already existing plots - both not affected by max plot outputs 64 - can only be used in the main chart - can serve as the only output function - at least one is required: plot, barcolor, line, label etc. - dynamic var values (including strings) can be output to screen as text using label.new and to_string str = close >= open ? "up" : "down" label.new(bar_index, high, text=str) col = close >= open ? color.green : color.red label.new(bar_index, na, "close = " + tostring(close), color=col, textcolor=color.white, style=label.style_labeldown, yloc=yloc.abovebar) // create new objects, delete old ones l = line.new(bar_index, high, bar_index , low , width=4) line.delete(l ) // free object buffer by deleting old objects first, then create new ones var l = na line.delete(l) l = line.new(bar_index, high, bar_index , low , width=4)
Pine Script™ indicator
by RagingRocketBull
8
Dragon-Bot - Default ScriptDragon-Script is a framework to make it as easy as possible to test your own strategies and set alerts for external execution bots. This is the alerts version of the script. The script has many features build in, like: 1) A ping/pong mechanism between longs and shorts 2) A stop-loss 3) Trailing Stops with several ways to calculate them. 4) 2 different ways to flip from long to short. The script is divided into several parts. The first part of the script is used to set all the variables. You should normally never change the first part except for the comments at the top. The second part of the script is the part where you initialise all your indicators. Several indicators can be found on Tradingview and on other sites. Please keep in mind that all the variable names used in the indicator should be unique. (all the … = … parts) The third part of the script, is the most important part of the script. Here you can create the entry and exit points. Let’s look at the OPENLONG function to explain this part: The first variables are all the possible entries; These are longentry1 till longentry5. You can add many more if you like. The variables are all initialised as being false. This way the script can set a value to true if an entry happens. The if function is the actual logic: You could say “if this is true” then (the line below the if function) longentry1 := (becomes) true. In this case we have said: “if this is true” then (the line below the if function) longentry1 := (becomes) true when the current close is larger than the close that is 1 back. The last part is the makelong_funct. This part says that if any of the entries are true, the whole function is true. The last part of the script is the actual execution. Here the alerts are plotted and the back test strategies are opened and closed. We hope you guys like it and all feedback is welcome!
Pine Script™ indicator
by Dragon-Bot
1
Dragon Bot - Default ScriptDragon Script is a framework to make it as easy as possible to test your own strategies and set alerts for external execution bots. The script has many features build in, like: 1) A ping/pong mechanism between longs and shorts 2) A stop-loss 3) Trailing Stops with several ways to calculate them. 4) 2 different ways to flip from long to short. The script is divided into several parts. The first part of the script is used to set all the variables. You should normally never change the first part except for the comments at the top. The second part of the script is the part where you initialise all your indicators. Several indicators can be found on Tradingview and on other sites. Please keep in mind that all the variable names used in the indicator should be unique. (all the … = … parts) The third part of the script, is the most important part of the script. Here you can create the entry and exit points. Let’s look at the OPENLONG function to explain this part: The first variables are all the possible entries; These are longentry1 till longentry5. You can add many more if you like. The variables are all initialised as being false. This way the script can set a value to true if an entry happens. The if function is the actual logic: You could say “if this is true” then (the line below the if function) longentry1 := (becomes) true. In this case we have said: “if this is true” then (the line below the if function) longentry1 := (becomes) true when the current close is larger than the close that is 1 back. The last part is the makelong_funct. This part says that if any of the entries are true, the whole function is true. The last part of the script is the actual execution. Here the alerts are plotted and the back test strategies are opened and closed. We hope you guys like it and all feedback is welcome!
Pine Script™ strategy
by Dragon-Bot
4
50/100/200 Moving Averages (Pine Script For Copy)by fresca SCRIPT LANGUAGE Copy script below and adjust based on your preferences. -function (change function from "sma" to "ema", "wma" and more) -length (25 Day, 150 Day or add more averages to the three in this script.) -color, (red, yellow, etc. or use color hex codes i.e. #FEDA15, #FFAD8F, etc.) -transparency (set to desired level 1-100) Or add more options. RESOURCES Color hex codes site: www.canva.com Trading View Pine Script Editor Reference Guide: www.tradingview.com
Pine Script™ indicator
by manifresca
9
TRADING VIEW INDICATOR - PINE TUTORIAL 5After a long gap, I have written the 5th tutorial for the pine script. You can find the others below, if you read through all of these you should be good to do your own writing. This script mimics the Trading View Indicator . For example this one below. www.tradingview.com It shows the net result of the 28 indicator, either as buy or sell. I have worked hard to make sure it matches the trading view results but I am not in hundred percent agreement with tradingView on SMA, EMA and Ichimoku indicator. There are many commented plots because I needed to check separately if each indicator is working correctly. Someone else wrote this code but they did not make it public. It took me about 3 weeks to write this and to be honest it could be cleaner and better commented. If you find any mistake please let me know. I hope it will be useful in your learning.
Pine Script™ indicator
by MartinMystere
3
Help Requested - "Time-Slot" Delay for Crossover StrategyHello Tradingview Community, I've been playing around with some various volume-based indicators, and recently have been experiencing a delay in the entries for my strategy for 2 minutes in this scenario. If the time is adjusted, it also is delayed 2 bars. In this example, the "Short" position should enter when the blue line Crosses under the upper green line, and visa vera for the "Long" position. A simplified Pine Script is available below as well. I have Googled this issue and attempted to modify the code with => criteria instead, but too no avail. Would appreciate any help or anyone who could point me in the right direction on this Time Delay Issue. Thanks!
Pine Script™ strategy
by Kowasaki
3
BarstateThe TradingView system has two types of bars. Bars that are historical and bars that are real-time. When programming complex scripts and strategies that use higher timeframe data there can be difficult programming conditions due to these two bar states. Especially in the case of after-hours, end of day, low volume trading and thinly traded stocks the bar state status can sometimes be historical and sometimes be real-time in different timeframes or even the same timeframe. This script displays what state a bar is in by shading the background of the chart. The script is being made publicly available to help my script users know about and understand 'barstate'. The script allows users to see the 'barstate' in order to help report bugs and conduct their own workarounds. My testing has indicated that the 'barstate' status is sometimes spurious especially on thinly traded symbols. Additionally, the Tradingview back-end calls the script only after price changes to reduce system load. As a result, these two characteristics can cause unexpected Pine Script results. Crinkebine November 2018
Pine Script™ indicator
by Crinklebine