Inizia

Pinescript

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)
Indicatore Pine Script®
di 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!
Indicatore Pine Script®
di Dragon-Bot
1
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
Indicatore Pine Script®
di 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.
Indicatore Pine Script®
di MartinMystere
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
Indicatore Pine Script®
di Crinklebine
Heffae Resolution Commander (RAW)This is a script to call resolutions with some math on top of your base resolution. Using the modulo operator to quantize integer values, it works by converting the modified resolution integer to a 4 digit string value. Use the function within your own scripts to call funny resolutions otherwise difficult to calculate. You cannot add series expressions to the resolution value since pine does not allow "series" as a resolution for a security call However, you could easily stack a crapload of these together and use an expression to switch the referenced security function for your purposes. This is the raw timeframe output as integer, not string. To go back to string outputs (for use in security calls etc) unslash line 52 //resvalue For those interested in the verbose version of the timeframe mod function, showing all the steps, here is a pastebin: pastebin.com Cheers! Drop a line / comment if you enjoy or have any questions on how to integrate this into your script@! The Modulo operator is so much fun!
Indicatore Pine Script®
di SNOW_CITY
6
Heffae Resolution CommanderThis is a script to call resolutions with some math on top of your base resolution. THIS IS NOT AN INDICATOR TO USE ON A CHART!!! The resolution call function is really useful for your own scripting ideas! Using the modulo operator to quantize integer values, it works by converting the modified resolution integer to a 4 digit string value. The function within this script is what is valuable, use it within your own scripts to call funny resolutions otherwise difficult to calculate. You cannot add series expressions to the resolution value since pine does not allow "series " as a resolution for a security call However, you could easily stack a crapload of these together and use an expression to switch the referenced security function for your purposes. The SMA and plot overlay are just there to show a visual example of how the function works. You can view the raw timeframe output integer by getting rid of tostring(x) and // out the security calls, plotting the raw function outputs. For those interested in the verbose version of the timeframe mod function, showing all the steps, here is a pastebin: pastebin.com Cheers! Drop a line / comment if you enjoy or have any questions on how to integrate this into your script@! The Modulo operator is so much fun!
Indicatore Pine Script®
di SNOW_CITY
2
alert reloadedtype: alert creation required time: 5 minutes level: easy Getting alerts for indicators and strats is good to easy the eyes of the charts for a while :) After my first script itroducing how to do alerts here there is an easier, more clear way to create an alert. It's still good to do it the "old way" to understand/debug an alert, but after that you'll want this extra tool for sure. I assume you read my previous post, or understand how alerts are set up on a chart. So, there is this function called alercondition() that does (almost)the whole job for us :) The function does NOT create the alert automatically, what is does is introducing a new option in the alerts popup. While in the v1.0 of my script the alert was triggered checking for the plot value against 0.9 or -0.9, in this example the alertcondition() function just fires the alert by itself. Get the script for yourself, in favourites, copy/paste, whatever. Add it to any chart. Then, open the popup to create an alert(the little clock at the top). There will be a drop menu with the options and "Alert reloaded". This is the title provided in the study() parameter. Choose this one. Now, the second drop menu has the "going UP" and "going DOWN" options. These are the titles from the alertcondition() function. Select one. Make all the aditional choices for the alert you want. Save it. And that's it, the alert will fire when the conditions become true. You can still keep the plot() for graphical reference, but it's now an extra, removing it will not affect the alert, so more space in the chart. Yey!! :)
Indicatore Pine Script®
di deimosaffair
Back to zero: Understanding seriestype: pine series basic example time required: 10 minutes level: medium (need to know the "array" data variable as a generic programming concept, basic Pine syntax) tl;dr how variables and series work in Pine Pine is an array/vector language. That's something that twists how it behaves, and how we have to think about it. A lot of misunderstandings come from forgetting this fact. This example tries to clear that concept. First, you need to know what an array is, and how it works in a programmig language. Also, having javascript under your belt helps too. If you don't, google "javascript array basic tutorial" is your friend :) So, in pine arrays are called "series". Every variable is an array with values for each candle in the chart. if we do: myVar = true this is not a constant. It is a series of values for each candle, { true, true,....., true } In practice, the result is the same, but we can access each of the values in the series, like myVar{0}, myVar{7}, myVar{anyNumber}.... Again, it is not a constant, since you can access/modify the each value individually so, lets show it: plot (myVar, clolor = gray) this plots an horizontal line of value 1 ( 1 is equal to true ) so it's all good. On to a more usual series: tipicalSeries = close > open ? true : false plot(tipicalSeries, color= blue) This gives the expected result, a tipical up and down line with values at 1 or 0. Naturally, "tipicalSeries" is an array, the "ups" and "downs" are all stored under the same variable, indexed by the candles. In Pine, the ZERO position in the array is the last one, which corresponds to the last candle on the right. Say you have a chart with 12 candles. The close would be the closing value of what we intuitively think as first candle, the one on the left. then close ... and so on.... until close , the value of the "last" candle, the one on the right. It actually helps to start thinking of the positions backwards, counting down to zero, rocket launch style :) And back to our series. The myVar will also be the same size, from myVar to myVar . When we do some operation with them, something simple like if ( myVar == tipicalSeries) what is really happening is that internally, Pine is checking each of the indexes, as in myVar == tipicalSeries , myVar == tipicalSeries .... myVar == tipicalSeries And we can store that stuff to check it. simply: result = (myVar == tipicalSeries) ? true : false //yes, this is the same as tipicalSeries, but we're not in a boolean logic tut ;) plot (result) The reason we can plot the result is that it is an array, not a single value. The example indicator i provide shows a plot where the values are obtained from different places in the array, this line here: mySeries3 = mySeries2 and mySeries1 this creates a series that is the result of the PREVIOUS values stored (the zero index is the one most at the right, or the "current" one), which here just causes a shift in the plotted line by one candle. Go ahead, grab a copy of my code, try to change the indexes and see the results. Understanding this stuff is critical to go deeper into Pine :)
Indicatore Pine Script®
di deimosaffair
9
Code for Cup With Handle calculations (using Pine)Cup with Handle formation calculations using Pine. First of all, ignore all other lines in the example chart except the two FAT lines. The two fat lines are the ones that define the Cup With handle or in the example chart: a Reversed Cup With Handle. Note: Handle does not always develop and sometimes the final target price is reached without forming any handle. This script can calculate both Cup With Handle ( CH ) and Reversed Cup With Handle ( RCH ). Just order the input values accordingly. For more information about Cup With Handle, use google: www.google.se The script need two input parameters : The highest price in the Cup formation and the lowest price in the cup formation or vice versa for the Reversed Cup formation. Best regards, /Hull, 2015.05.20.16:31
Indicatore Pine Script®
di R2D2B2C2
CM_Donchian Channels Modified_V2 - Alert CapableCM_Donchian Channels Modified_V2 With Alert Capability ***This Indicator was created by user Request to Add Alerts Capabilities for Donchian Channels. New Features: ***Alerts Work - Ability To Create Alerts From Main Indicator. ***Can Also Be Used In Conjunction with Lower Indicator - CM_Donchian Channels Modified_V2_Lower_Alert ***Added Ability To Turn On/Off Highlight Bars. ***Added Ability to Turn On/Off Donch Channel Midline ***Added Ability to Turn On/Off Triangles That Plot At Top and Bottom Of Chart When Breakout Condition is TRUE. Special Indicator Features: ***Ability To Use Different LookBack Period on Upper and Lower Donch Channel Lines. How To Create Alerts: ***Create Alert by selecting Indicator - Either the name of the Upper Or Lower Indicator... ***Then select either Alert Breakout Upside or Downside(To The Right Of Indicator Name) ***Select Greater Than ***Select Value ***For Value put .99 Original Post Explaining Indicator is - ***If You Need Help Getting Custom Indicators to Trigger Alerts then View This Post.
Indicatore Pine Script®
di ChrisMoody
2
CM_Donchian Channels Modified_V2_Lower_Alert***This Indicator was created by user Request to Add Alerts Capabilities for Donchian Channels. New Features: ***Alerts Work - Ability To Create Alerts From Main Indicator. ***Can Also Be Used In Conjunction with Upper Indicator - CM_Donchian Channels Modified_V2 With Alert Capability ***Added Ability To Turn On/Off Highlight Bars. ***Added Ability to Turn On/Off Donch Channel Midline ***Added Ability to Turn On/Off Triangles That Plot At Top and Bottom Of Chart When Breakout Condition is TRUE. Special Indicator Features: ***Ability To Use Different LookBack Period on Upper and Lower Donch Channel Lines. How To Create Alerts: ***Create Alert by selecting Indicator - Either the name of the Upper Or Lower Indicator... ***Then select either Alert Breakout Upside or Downside(To The Right Of Indicator Name) ***Select Greater Than ***Select Value ***For Value put .99 Original Post Explaining Indicator is - ***If You Need Help Getting Custom Indicators to Trigger Alerts then View This Post.
Indicatore Pine Script®
di ChrisMoody
6
CM ATR Stops/Bands - Multi-TimeFrameCM_MTF ATR Bands/Stops Many Options Available Via Input Tab: -Chart Defaults to Upper and Lower ATR's Based on Current Chart TimeFrame -Ability to Plot either Upper and/or Lower ATR's -Ability to Change the Time Frame ATR's are Based On! -Ability to change Look Back Period and ATR Multiplier Individually for Both Time Frames -This Gives you the ability to plot same Time Frame with (for ex.) a 5 ATR with a 1.5 Mult and a 14 ATR with a 2.0 Mult etc. -Or you can plot Daily ATR's on a 60 minute Chart etc. -ATR Multipliers are Calculated with Code that allows "Non Whole Numbers" Allowing Ability to use 1.5 ATR's, 1.8 ATR's etc. ***Endless # of Combinations can be used!!!!
Indicatore Pine Script®
di ChrisMoody
12