Get started

Indicators and strategies

HSV and HSL gradient Tools ( Built-in Drop-in replacement )Library "hsvColor" HSV and HSL Gradient Tool Alternatives and helpers. Demo'd is built-in in the middle with HSL/HSV gradients on top/bottom TODO: Solve for #000000 issue rgbhsv(_col)   RGB Color to HSV Values   Parameters:      _col : Color input (#abc012 or color.name or color.rgb(0,0,0,0))   Returns: values rgbhsv(_r, _g, _b, _t)   RGB Color to HSV Values   Parameters:      _r : Red 0 - 255      _g : Green 0 - 255      _b : Blue 0 - 255      _t : Transp 0 - 100   Returns: values hsv(_h, _s, _v, _a)   HSV colors, Auto fix if past boundaries   Parameters:      _h : Hue Input (-360 - 360) or further      _s : Saturation 0.- 1.      _v : Value 0.- 1.      _a : Alpha 0.- 1.   Returns: Color output hue(_col)   returns 0-359 hue on color wheel   Parameters:      _col :   Returns: 360 degree hue value hsv_gradient(signal, _startVal, _endVal, _startCol, _endCol)   Color Gradient Replacement Function for HSV calculated Gradents   Parameters:      signal : Control signal      _startVal : start color limit      _endVal : end color limit      _startCol : start color      _endCol : end color   Returns: HSV calculated gradient hsl_gradient(signal, _startVal, _endVal, _startCol, _endCol)   Color Gradient Replacement Function for HSV calculated Gradents   Parameters:      signal : Control signal      _startVal : start color limit      _endVal : end color limit      _startCol : start color      _endCol : end color   Returns: HSV calculated gradient
Pine Script® library
by kaigouthro
31
STD-Filtered, N-Pole Gaussian Filter [Loxx]This is a Gaussian Filter with Standard Deviation Filtering that works for orders (poles) higher than the usual 4 poles that was originally available in Ehlers Gaussian Filter formulas. Because of that, it is a sort of generalized Gaussian filter that can calculate arbitrary (order) pole Gaussian Filter and which makes it a sort of a unique indicator. For this implementation, the practical mathematical maximum is 15 poles after which the precision of calculation is useless--the coefficients for levels above 15 poles are so high that the precision loss actually means very little. Despite this maximal precision utility, I've left the upper bound of poles open-ended so you can try poles of order 15 and above yourself. The default is set to 5 poles which is 1 pole greater than the normal maximum of 4 poles. The purpose of the standard deviation filter is to filter out noise by and by default it will filter 1 standard deviation. Adjust this number and the filter selections (price, both, GMA, none) to reduce the signal noise. What is Ehlers Gaussian filter? This filter can be used for smoothing. It rejects high frequencies (fast movements) better than an EMA and has lower lag. published by John F. Ehlers in "Rocket Science For Traders". A Gaussian filter is one whose transfer response is described by the familiar Gaussian bell-shaped curve. In the case of low-pass filters, only the upper half of the curve describes the filter. The use of gaussian filters is a move toward achieving the dual goal of reducing lag and reducing the lag of high-frequency components relative to the lag of lower-frequency components. A gaussian filter with... One Pole: f = alpha*g + (1-alpha)f Two Poles: f = alpha*2g + 2(1-alpha)f - (1-alpha)2f Three Poles: f = alpha*3g + 3(1-alpha)f - 3(1-alpha)2f + (1-alpha)3f Four Poles: f = alpha*4g + 4(1-alpha)f - 6(1-alpha)2f + 4(1-alpha)3f - (1-alpha)4f and so on... For an equivalent number of poles the lag of a Gaussian is about half the lag of a Butterworth filters: Lag = N*P / pi^2, where, N is the number of poles, and P is the critical period Special initialization of filter stages ensures proper working in scans with as few bars as possible. From Ehlers Book: "The first objective of using smoothers is to eliminate or reduce the undesired high-frequency components in the eprice data. Therefore these smoothers are called low-pass filters, and they all work by some form of averaging. Butterworth low-pass filters can do this job, but nothing comes for free. A higher degree of filtering is necessarily accompanied by a larger amount of lag. We have come to see that is a fact of life." References John F. Ehlers: "Rocket Science For Traders, Digital Signal Processing Applications", Chapter 15: "Infinite Impulse Response Filters" Included Loxx's Expanded Source Types Signals Alerts Bar coloring Related indicators STD-Filtered, Gaussian Moving Average (GMA) STD-Filtered, Gaussian-Kernel-Weighted Moving Average One-Sided Gaussian Filter w/ Channels Fisher Transform w/ Dynamic Zones R-sqrd Adapt. Fisher Transform w/ D. Zones & Divs .
Pine Script® indicator
by loxx
50
Portfolio PerformanceThis indicators will help you to compute portfolio performance and display results with a stats table and a nice monthly chart. In this script you can do following: Compose portfolio with up to 15 instruments Change Initial capital / date range / rebalancing period Compare portfolio performance with a benchmark Compute basic stats Compute instruments contribution Display monthly performance of portfolio and benchmark Change style for almost everything you see on your chart Hope it will be useful for you! Thanks to @MUQWISHI for helping me coding it. 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® indicator
by QuantNomad
13
Weighted percentile nearest rankYo, posting it for the whole internet, took the whole day to find / to design the actual working solution for weighted percentile 'nearest rank' algorithm, almost no reliable info online and a lot of library-style/textbook-style solutions that don't provide on real world production level. The principle: 0) initial data data = 22, 33, 11, 44, 55 weights = 5 , 3 , 2 , 1 , 4 array(s) size = 5 1) sort data array, apply the sorting pattern to the weights array, resulting: data = 11, 22, 33, 44, 55 weights = 2 , 5 , 3 , 1 , 4 2) get weights cumsum and sum: weights = 2, 5, 3 , 1 , 4 weights_cum = 2, 7, 10, 11, 15 weights_sum = 15 3) say we wanna find 50th percentile, get a threshold value: n = 50 thres = weights_sum / 100 * n 7.5 = 15 / 100 * 50 4) iterate through weights_cum until you find a value that >= the threshold: for i = 0 to size - 1 2 >= 7.5 ? nah 7 >= 7.5 ? nah 10 >= 7.5 ? aye 5) take the iteration index that resulted "aye", and find the data value with the same index, that's gonna be the resulting percentile. i = 2 data = 33 This one is not an approximation, not an estimator, it's the actual weighted percentile nearest rank as it is. I tested the thing extensively and it works perfectly. For the skeptics, check lines 40, 41, 69 in the code, you can comment/uncomment dem to switch for unit (1) weights, resulting in the usual non-weighted percentile nearest rank that ideally matches the TV's built-in function. Shoutout for @wallneradam for the sorting function mane ... Live Long and Prosper
Pine Script® indicator
by gorx1
54
(Quartile Vol.; Vol. Aggregation; Range US Bars; Gaps) [Kioseff]Hello! This indicator is a multifaceted tool that's, hopefully, useful for price action and volume analysis. (This script makes use of the newly introduced "text_font" parameter) With this script you'll have access to: Range US Chart Volume Aggregation Chart Gaps Chart Volume by Quartile Consequently, you'll have access to: First Quartile Volume Threshold Second Quartile Volume Threshold Third Quartile Volume Threshold 90th Percentile Volume Threshold Fourth Quartile Volume Threshold Q2 - Q1 Dispersion Q3 - Q2 Dispersion Q4 - Q3 Dispersion Quartile Deviation Interquartile Range Avg. "n" bar return following "high" volume Avg. "n" bar positive return following "high" volume Avg. "n" bar negative following "high" volume # of Positive Returns Following a Gap # of Negative Returns Following a Gap # of Gaps # of Up Gaps # of Down Gaps Average # of bars to fill Up Gaps Average # of bars to dill Down Gaps Average Gap Up % increase Average Gap Down % decrease Cumulative % increase of all Up Gaps Cumulative % decrease of all Down Gaps Sort gaps by distance from price Hide gaps that price substantially deviates from (gaps will reappear when price trades near the gap) Segment Range US bars by date Manually configure Range US price thresholds Identify "congestion" areas with Range US bars Range US Levels that must be exceeded for a new Range US bar to produce Manually configure cumulative volume threshold for Volume Aggregation bars Segment Volume Aggregation bars by date Largest Volume Aggregation bar increases Largest Volume Aggregation bar decreases Calculate log returns after "high" volume sessions Quartile Volume The Quartile Volume portion of the script segments price/volume intervals by quartile. The image above shows features of the indicator. For statistics, the following metrics are recorded: First Quartile Second Quartile Third Quartile 90th Percentile Fourth Quartile Q2 - Q1 Dispersion Q3 - Q2 Dispersion Q4 - Q3 Dispersion Quartile Deviation Interquartile Range Color-coordinated price bars (by volume quartiles) The percent rank for the volume of the current bar Avg. "n" bar return following "high" volume Avg. "n" bar positive return following "high" volume Avg. "n" bar negative following "high" volume The script colors bars via gradient. By default, bars are colored lime when volume for the interval is "high" (exceeds upper quartile thresholds). The greener the bar, the higher the volume for the interval. Bars are colored red when volume for the interval is "low" (fails to exceed lower quartile thresholds). The redder the bar, the lower the volume for the interval. Naturally, brownish-colored bars reflect a volume interval that concluded near the median. The image above exemplifies the process. This feature might be useful to categorize / objectively define high-volume clusters, low-volume clusters, high-volume price moves, low-volume price moves, etc. For greater precision, you can select to color bars by volume quartile they belong to. The image above shows color-coordinated price bars. More details shown in the image. Additionally, you can select to plot the quartile/percentile that a price bar belongs to on the chart. The image above shows price bars numbered by the volume quartile they belong to. The script will distinguish successive 90th percentile violations, superimpose a linear regression channel atop the data sequence, and record pertinent statistics. The image above shows the process. Lastly, the user can plot an anchored VWAP using a built-in time function. The image above shows the anchored VWAP. Range US Chart A Range US chart operates irrespective of time and volume - simply - bars produce after a user-defined price move is achieved/exceeded in either direction. A range us chart produces “trend candles” and “reversal candles”. A reversal candle always moves against the most immediate bar; a trend candle always moves in favor of the most immediate bar. The user defines the dollar amount price must travel up/down for a trend candle to fulfill, and for a reversal candle to fulfill. Note: if a “down reversal” candle (red) Is produced, it’s impossible for the next candle to also be a down reversal candle - for the downside move to continue the criteria for a down trend candle must be fulfilled. Similarly, if an “up reversal” candle (green) Is produced, it’s impossible for the next candle to also be an up reversal candle - for the upside move to continue, the criteria for an uptrend trend candle must be fulfilled. Consequently, Range US bars frequently trade at the same level for extended periods. This is intentional, as this chart type is theorized to “filter noise” (whether Range US charts fulfill this theory is to your discretion). Lastly, if an up trend candle (green) is produced, the next candle cannot be up a reversal up candle - only a trend up candle or reversal down candle can produce - vice versa for a trend down candle (the subsequent candle cannot be a reversal down candle). In this sense, an uptrend continues on successive trend up candles; a down trend continues on successive trend down candles. The image above exemplifies Range US chart functionality. The lower-right stats table shows the requisite price move for a "Trend" candle to produce and for a "Reversal" candle to produce. The default settings for this chart time automatically calculate the required "Trend" candle price move and the required "Reversal" candle price move. However, both settings are configurable. The image above shows manually configured parameters for a trend bar and reversal bar to produce. This feature allows the user to replicate the Range US chart hosted on extrinsic charting platforms. However, please consider that this script does not use tick data; 1-minute OHLC data is used for calculations. Consequently, configuring the trend bar and reversal bar requirement too low may return inaccurate data. For instance, if you set trend candles to form after a $1 price move then trend candles will form if price moves up $1 from a green Range US bar or down $1 from a red Range US bar. This is sufficient for lower priced assets; however, if you were trading, for instance, Bitcoin - a $1 price move can happen numerous times in one minute. This script can’t plot bars and record data until a 1-minute bar closes and a new 1-minute bar opens. Further, if Bitcoin moves up $1 twenty times and down $1 twenty times in a 1-minute bar - your Range US chart will record such variations as one price move. This data is inaccurate and likely useless. To counter this quandary, a warning message will appear if you configure trend bar price moves or reversal bar price moves too low. The image above shows the concealable warning message. The image above is a flow diagram (made with shaky hands) illustrating the Range US bar formation process. A google search will return additional information on the Range US chart type. Volume Aggregation Bars TradingView user and member of the TradingView Discord server @ferreirajames informed me of the Volume Aggregation chart type. The user commented in the "Suggestions" channel for the TradingView Discord server asking for the Volume Aggregation chart type. As an interim fix, I tried my hand at recreating the process, which is available in this script. Similar to the Range US chart type, Volume Aggregation bars aren’t bound to a time-axis; the bars form after a user-defined, cumulative amount of volume is achieved or exceeded. Consequently, once the cumulative amount of volume is achieved or exceeded - a bar is produced at the corresponding price level. Underlying theory: The chat type is conducive to identifying price levels where traders are “trapped”. Whether the process adequately distinguishes this circumstance is to your discretion. The image above exemplifies the Volume Aggregation chart type. Regardless of the current price, Volume Aggregation bars for after a requisite amount of volume is achieved/exceeded. Tick data isn't used; therefore, remainder values are carry over. By default, the script automatically calculates a proportional cumulative volume total to dictate the formation of Volume Aggregation bars. However, the cumulative threshold is configurable. The image above shows Volume Aggregation bars forming subsequent a user-defined cumulative volume total being exceeded. Note: This chart type uses OHLC data from the timeframe of your chart. Therefore, for instance, setting the volume threshold too low will produce inaccurate, useless data. A warning message will appear for such occurrence. Gaps The indicator incorporates a "Gaps" chart type. The image above shows accompanying features. A list of all unfilled gaps is accessible - gaps for this list are sorted by distance from current price. Partially filled gaps are displayed in the corresponding gap box - the percentage amount the gap was filled is also displayed. Gap statistics show: # of Gaps # of Up Gaps # of Down Gaps Average # of bars to fill Up Gaps Average # of bars to dill Down Gaps Average Gap Up % increase Average Gap Down % decrease Cumulative % increase of all Up Gaps Cumulative % decrease of all Down Gaps Naturally, there may be gaps formed thousands of bars ago that aren't close to price. Showing these gaps on the chart will "scrunch" the y-axis and make prices indistinguishable. I've added a setting that allows the user to hide gaps that are "n" % away from the current price. The gap, if unfilled, will reappear when price trades within the user-defined percentage. The image above shows an example. There's an unfilled down gap that's "hidden" because the current price is a further % away from price than what I've specified in the settings (1%). When prices trade back within 1% of the gap - it will reappear. The image above shows the process in action. Prices moved back within 1% (can be any %) of the gap; therefore, it reappeared on the chart. You can also set the % distance a gap must achieve for it to be considered a gap, recorded and plotted. Additionally, you can select to "visualize" gaps. Similar to the Range US chart and the Volume Aggregation chart, this setting will bars reflecting the most recent sequence of gaps - date and percentage distance of the gap are superimposed atop the bar. Let me know if there's anything else you'd like included! Note: The initial compilation time for this script is.... high. However, once the script's compiled, calculation load times are quick and you can sift through assets and timeframes relatively quick. There's also a setting to "Improve Load Times" in the user-inputs table. This setting only improves the load times for post-compilation calculations and plots. The initial compilation load time is unchanged. Simply, once the indicator has "first loaded", all subsequent loads are quick. Thank you! (:
Pine Script® indicator
by KioseffTrading
27
Cup & HandleHi, here is my take on 'Cup & Handle' Pivot Points - ph  (highest points in a certain period) are stored in an array When there is a new ph , previous ph's are compared to the latest one. A temporary test line is drawn between these 2 points. The script checks if a close (between these 2 points) doesn't break above this test line. (test line is deleted afterwards) If it doesn't, and the '% max breaks' are not breached, 2 circle shaped lines are drawn (Top & Bottom line of the cup) which forms the Cup, together with the Handle. The red box (Handle) is the maximum 33-50% retracement (% of cup height) -> Only the latest pattern is shown, enabling 'Show Cup labels' shows the position of cup patterns in history. They can be visualised by using 'Bar Replay' '% max breaks' -> 'maximum highs/lows breaking through the Top/Bottom line (% of bars between left & right extreme points of the Cup) Settings: - 'Left', 'Right' -> regulates Pivot Point values - 'PP back' -> max lookback for Pivot High More explanation can be found in following print screens, or by checking the tooltips in the settings Cheers!
Pine Script® indicator
by fikira
62
Blockchain Fundamentals - Active Address Sentiment Osc. [CR]Blockchain Fundamentals: Active Address Sentiment Oscillator AASO Back with another script today, this one is a useful tool in helping to determine bitcoins value. We are looking at 2 data sources: the daily active addresses on the BTC blockchain, and the daily returns of BTC. THIS INDICATOR WILL ONLY GIVE YOU THE CORRECT RESULTS ON THE DAILY TIMEFRAME There is an interesting relationship that you can see by comparing the two timeseries. But for us to create a good indicator we first need to normalize the data. So we look at the percent change over the past 28 days for each metric (DAA and price). THIS INDICATOR WILL ONLY GIVE YOU THE CORRECT RESULTS ON THE DAILY TIMEFRAME We then calculate standard deviation bands around the DAA metric. We finalize them by averaging the bands over a 28 day period. When the Price series (yellow line) is higher than the SD bands BTC is considered overvalued or price is overheated. A pullback could be expected soon. When the Price series is below the SD bands BTC is considered undervalued or price is oversold. THIS INDICATOR WILL ONLY GIVE YOU THE CORRECT RESULTS ON THE DAILY TIMEFRAME This tool doesnt give signals on the one minute chart or tell you exactly when to buy or sell. BUT what it does do is act as a convenient macro sentiment indicator that is not based completely upon price. In an attempt to narrow down the really juicy areas, if you seen the background color highlights with white, that means its likely a top or bottom. At the very least on a local sense and many times in a cyclical macro sense as well. It also narrows down the signal to a generally more profitable area. This indicator is not meant to be used on timeframes other than daily (did I mention that already?). I am lazy and did not code the calculations to be MTF (which is why you have to use on the daily chart). If you want to code this, please forward it on to me and I will post an update with a heartfelt credit to you.
Pine Script® indicator
by theheirophant
13
Gann Square of 144This indicator will create lines on the chart based on W.D. Gann's Square of 144. All the inputs will be detailed below Why create this indicator? I didn't find it on Tradingview (at least with open source). But the main reason is to study the strategy and be able to draw it fast. Manually drawing the square is not hard, but moving all together to the right spots and scale was time-consuming. It has a lot of inputs... Yes, each square point divisible by 6 has information with some options, so the user can create any configuration he wants. Also, it has the advantage of having the square built in seconds and adjusting itself on each new calculation. About the inputs Starting Date This input will be used when the "Set Upper/Lower Prices and Start Bar Automatically" checkbox is not selected. The indicator will calculate all the line locations on the chart using the selected start date. When selecting this input, change the Manual Max and Min Prices to the better calculation Manual Max/Min Price This input will be used when the "Set Upper/Lower Prices and Start Bar Automatically" checkbox is not selected. The indicator will calculate all the line's locations on the chart using these prices Set Upper/Lower Prices and Start Bar Automatically Selects if the starting date will be automatically selected by the system or based on the input data. When it's set, the indicator will use the most recent bar as the middle point of the square, using the higher price as the Upper Price and the lowest price as the Lower Price in the latest 72 bars (or more based on the Candles Per Division parameter) Update at a new bar When this option is market, the indicator will update all created lines to match the new bar position, together with all the possible new Upper/Lower prices. Let it unchecked to watch the progression of the price while the square remains fixed in the chart. Top X-Axis When checked, it will display the labels on the Top of the square Bottom X-Axis When checked, it will display the labels on the Bottom of the square Left X-Axis When checked, it will display the labels on the left of the square Right X-Axis When checked, it will display the labels on the right of the square Show Prices on the Right Y-Axis When checked, it will display the prices together with the labels on the right of the square Show Vertical Divisions Show the lines that will divide the square into 9 equal parts Show Extra Lines Show unique lines that will come from the Top and bottom middle of the square, connecting the center to the 36 and 108 levels Show Grid When selected, it will display a grid in the square Line Patterns A selector with some options of built-in lines configuration. When any option besides None is selected, it will override the lines inputs below Numbers Color Select the color of each number on the Axis Vertical Lines Color Select the color of the vertical lines Grid Color Select the grid line color Connections from corners to N Each corner is represented by 2 characters, so they all fit in a single line It will indicate where the line starts and where it ends ┏ ↓ = Top Left to Bottom ┏ → = Top Left to Right ┗ ↑ = Bottom Left to Top ┗ → = Bottom Left to Right ┓ ← = Top Right to Left ┓ ↓ = Top Right to Bottom ┛ ← = Bottom Right to Left ┛ ↑ = Bottom Right to Top Besides selecting what line will be created, it's possible to select the color, the style, and the extension How to use this indicator When you dig into Gann's books for more information about the square of 144, you find that it was part of his setup with multiple indicators (technical and fundamental, and astrological). It is not a "one indicator" setup, so it's hard to say that you will find entries, exits, stop loss, and take profit in this. Still, it will help see trendiness, support, and resistance levels. Mixing this with other indicators is probably a good idea, but some may find this indicator the only one needed. Some aspects of the square The end of the square is important, so where it starts is crucial. The end is important because it is where the price and time expire. The other parts of the square are defined based on their start and end, so placing them right is essential. So, where to set the start of the square? The last major low is the most indicated. The minimum price will be the lowest, and the max price will be the last major Top. Note that the indicator uses 1 candle on each point. After finding the start, the minimum, and the maximum prices for the square, it will draw all lines. Another essential part of the square is The Midpoint. The midpoint is the most crucial part of the square and is the best way to see if you positioned the square correctly. When the price is inside the square, using the starting candle as the start, a second higher low or a lower high occurs in that spot. When using the Vertical lines in the indicator, it's the middle square inside Gann's square. The other divisions will be opposing each other most of the time. So if the price is rising in the 1/3 of the square, it's common to see the price fall in the 3/3 of the square. More information about these aspects here Considerations This indicator was meant for price targets and a time calculator for possible support/resistances in the chart. It was created by William Delbert Gann and was part of his setup for trading almost a century ago. The lines will form geometric figures, which Gann used with high accuracy to predict tops/bottoms and when they would occur.
Pine Script® indicator
by ThiagoSchmitz
53
Annual Returns % Comparison [By MUQWISHI]Overview The Annual Returns % Comparison indicator aimed to compare the historical annual percentage change of any two symbols. The indicator output shows a column-plot that was developed by two using a pine script table, so each period has pair columns showing the yearly percentage change for entered symbols. Features - Enter date range. - Fill up with any two symbols. - Choose the output data whether adjusted or not. - Change the location of the table plot - Color columns by a symbol. - Size the height and width of columns. - Color background, border, and text. - The tooltip of the column value appears once the cursor sets above the specific column. As it seen below. Let me know if you have any questions. Thanks.
Pine Script® indicator
by MUQWISHI
13
R:R Trading System FrameworkFirst off, huge thanks to @fikira! He was able to adapt what I built to work much more efficiently, allowing for more strategies to be used simultaneously. Simply put, I could not have gotten to this point without you. Thanks for what you do for the TV community. Second, I am fairly new to pinescript writing, so I welcome criticism, thoughtful input and improvement suggestions. I would love to grow this concept into something even better, if possible. So please let me know if you have any ideas for improvement. However I do juggle a lot of different things outside of TV, so implementations may be delayed. I have decided, at this time, not to add alerts. First, because I feel most people looking to adapt this framework can add their own pretty easily. Also, given how customized the framework is currently, while also attempting to account for all the possible ways in which people may want alerts to function after they customize it, it seems best to leave them out as it doesn't exactly fit the idea of a framework. For best viewing, I recommend hovering over the script's name > ... > Visual order > Bring to front. Also I found hollow candles with mono-toned colors (like pictured) are more visually appealing for me personally. I HIGHLY RECOMMEND USING WITH BAR REPLAY TO BETTER UNDERSTAND THE FRAMEWORK'S FUNCTIONALITY. ▶️ WHAT THIS FRAMEWORK IS - A huge collection of concepts and capabilities for those trying to better understand, learn, or teach pinescript. - A system designed to showcase Risk:Reward concepts more holistically by providing all of the most popular components of retail trading to include backtesting, trade visual plotting, position tracking, market condition shifts, and useful info while positioned to help highlight changes in your risk:reward based decision-making processes. - A system that can showcase individual strategies regardless of trade direction, allowing you to develop hedging strategies without having multiple indicators that do not correlate with each other. - Designed around the idea that you trade less numbers of assets but manage your positions and risk based on multiple concurrently running strategies to manage your risk exposure and reward potential. - An attempt to combine all the things you need to execute with an active trading management style. - A framework that uses backtested results (in this case the number of averaged bars it takes to hit key levels) in real-time to inform your risk:reward decision-making while in-trade (in this case in your Trade Tracking Table using dynamic color to show how you might be early, on-time, or late compared to the average amount of backtested time it normally takes to hit that specific key level). ▶️ WHAT THIS FRAMEWORK IS NOT - A complete trading product. DO NOT USE as-is. It is a FRAMEWORK for you to generate ideas of your own and fairly easily implement your own triggering conditions in the appropriate sections of the script. ▶️ USE CASES - If you decide you like the Stop, Target, Trailing Stop, and Risk:Reward components as-is, then just understanding how to plug in your Entry and Bullish / Bearish conditions (Triangles) and adjust the input texts to match your custom naming will be all you need to make it your own! - If you want to adapt certain components, then this system gives you a great starting point to adapt your different concepts and ideas from. ▶️ SYSTEM COMPONENTS - Each of the system's components are described via tooltips both in the input menu and in the tables' cells. - Each label on the chart displays the corresponding price at those triggered conditions on hover with tooltips. - The Trailing Stop only becomes active once it is above the Entry Price for that trade, and brightens to show it is active. The STOP line (right of price) moves once it takes over for the Entry Stop representing the level of the Trailing Stop at that time for that trade. - The Lines / Labels to the right of price will brighten once price is above for Longs or below for Shorts. The Trade Tracking Table cells will add ☑️ once price is above for Longs or below for Shorts. - The brighter boxes on the chart show the trades that occurred based on your criteria and are color coded for all components of each trade type to ensure your references are consistent. (Defaults are TV built-in strategies) - The lighter boxes on the chart show the highest and lowest price levels reached during those trades, to highlight areas where improvements can be made or additional considerations can be accounted for by either adjusting Entry triggers or Bullish / Bearish triggers. - Default Green and Red Triangles (Bullish / Bearish) default to having the same triggering condition as the Entry it corresponds to. This is to highlight either a pyramiding concept, early exit, or you can change to account for other things occurring during your trades which could help you with Stop and Target management/considerations. TradingView and many of its community members have done a lot for me, so this is my attempt to give back.
Pine Script® indicator
by carnagecain
128
Bjorgum Double Tap█   OVERVIEW Double Tap is a pattern recognition script aimed at detecting Double Tops and Double Bottoms. Double Tap can be applied to the broker emulator to observe historical results, run as a trading bot for live trade alerts in real time with entry signals, take profit, and stop orders, or to simply detect patterns. █   CONCEPTS How Is A Pattern Defined? Doubles are technical formations that are both reversal patterns and breakout patterns. These formations typically have a distinctive “M” or a “W” shape with price action breaking beyond the neckline formed by the center of the pattern. They can be recognized when a ​pivot fails to break when tested for a second time and the retracement that follows breaks beyond the key level opposite. This can trap entrants that were playing in the direction of the prior trend. Entries are made on the breakout with a target projected beyond the neckline equal to the height of the pattern. Pattern Recognition Patterns are recognized through the use of ​zig-zag; a method of filtering price action by connecting swing highs and lows in an alternating fashion to establish trend, ​support and resistance, or derive shapes from price action. The script looks for the highest or lowest point in a given number of bars and updates a list with the values as they form. If the levels are exceeded, the values are updated. If the direction changes and a new significant point is made, a new point is added to the list and the process starts again. Meanwhile, we scan the list of values looking for the distinctive shape to form as previously described. █   STRATEGY RESULTS Back Testing Historical back testing is the most common method to test a strategy due in part to the general ease of gathering quick results. The underlying theory is that any strategy that worked well in the past is likely to work well in the future, and conversely, any strategy that performed poorly in the past is likely to perform poorly in the future. It is easy to poke holes in this theory, however, as for one to accept it as gospel, one would have to assume that future results will match what has come to pass. The randomness of markets may see to it otherwise, so it is important to scrutinize results. Some commonly used methods are to compare to other markets or benchmarks, perform statistical analysis on the results over many iterations and on differing datasets, walk-forward testing, out-of-sample analysis, or a variety of other techniques. There are many ways to interpret the results, so it is important to do research and gain knowledge in the field prior to taking meaningful conclusions from them. 👉  In short, it would be naive to place trust in one good backtest and expect positive results to continue. For this reason, results have been omitted from this publication. Repainting Repainting is simply the difference in behaviour of a strategy in real time vs the results calculated on the historical dataset. The strategy, by default, will wait for confirmed signals and is thus designed to not repaint. Waiting for bar close for entires aligns results in the real time data feed to those calculated on historical bars, which contain far less data. By doing this we align the behaviour of the strategy on the 2 data types, which brings significance to the calculated results. To override this behaviour and introduce repainting one can select "Recalculate on every tick" from the properties tab. It is important to note that by doing this alerts may not align with results seen in the strategy tester when the chart is reloaded, and thus to do so is to forgo backtesting and restricts a strategy to forward testing only. 👉  It is possible to use this script as an indicator as opposed to a full strategy by disabling "Use Strategy" in the "Inputs" tab. Basic alerts for detection will be sent when patterns are detected as opposed to complex order syntax. For alerts mid-bar enable "Recalculate on every tick" , and for confirmed signals ensure it is disabled. █   EXIT ORDERS Limit and Stop Orders By default, the strategy will place a stop loss at the invalidation point of the pattern. This point is beyond the pattern high in the case of Double Tops, or beneath the pattern low in the case of Double Bottoms. The target or take profit point is an equal-legs measurement, or 100% of the pattern height in the direction of the pattern bias. Both the stop and the limit level can be adjusted from the user menu as a percentage of the pattern height. Trailing Stops Optional from the menu is the implementation of an ATR based trailing stop. The trailing stop is designed to begin when the target projection is reached. From there, the script looks back a user-defined number of bars for the highest or lowest point +/- the ATR value. For tighter stops the user can look back a lesser number of bars, or decrease the ATR multiple. When using either Alertatron or Trading Connector, each change in the trail value will trigger an alert to update the stop order on the exchange to reflect the new trail price. This reduces latency and slippage that can occur when relying on alerts only as real exchange orders fill faster and remain in place in the event of a disruption in communication between your strategy and the exchange, which ensures a higher level of safety. 👉  It is important to note that in the case the trailing stop is enabled, limit orders are excluded from the exit criteria. Rather, the point in time that the limit value is exceeded is the point that the trail begins. As such, this method will exit by stop loss only. █   ALERTS Five Built-in 3rd Party Destinations The following are five options for delivering alerts from Double Tap to live trade execution via third party ​API solutions or chat bots to share your trades on social media. These destinations can be selected from the input menu and alert syntax will automatically configure in alerts appropriately to manage trades. Custom JSON JSON, or JavaScript Object Notation, is a readable format for structuring data. It is used primarily to transmit data between a server and a web application. In regards to this script, this may be a custom intermediary web application designed to catch alerts and interface with an exchange ​API. The JSON message is a trade map for an application to read equipped with where its been, where its going, targets, stops, quantity; a full diagnostic of the current state and its previous state. A web application could be configured to follow the messages sent in this format and conduct trades in sync with alerts running on the TV server. Below is an example of a rendered JSON alert: { "passphrase": "1234", "time": "2022-05-01T17:50:05Z", "ticker": "ETHUSDTPERP", "plot": { "stop_price": 2600.15, "limit_price": 3100.45 }, "strategy": { "position_size": 0.1, "order_action": "buy", "market_position": "long", "market_position_size": 0, "prev_market_position": "flat", "prev_market_position_size": 0 } } Trading Connector Trading Connector is a third party fully autonomous Chrome extension designed to catch alert webhooks from TradingView and interface with MT4/MT5 to execute live trades from your machine. Alerts to Trading Connector are simple; just select the destination from the input drop down menu, set your ticker in the "TC Ticker" box in the "Alert Strings" section and enter your URL in the alert window when configuring your alert. Alertatron Alertatron is an automated algo platform for cryptocurrency trading that is designed to automate your trading strategies. Although the platform is currently restricted to crypto, it offers a versatile interface with high flexibility syntax for complex market orders and conditions. To direct alerts to Alertatron, select the platform from the 3rd party drop down, configure your ​API key in the ”Alertatron Key” box and add your URL in the alert message box when making alerts. 3 Commas 3 Commas is an easy and quick to use click-and-go third party crypto ​API solution. Alerts are simple without overly complex syntax. Messages are simply pasted into alerts and executed as alerts are triggered. There are 4 boxes at the bottom of the "Inputs" tab where the appropriate messages to be placed. These messages can be copied from 3 Commas after the bots are set up and pasted directly into the settings menu. Remember to select 3 Commas as a destination from the third party drop down and place the appropriate URL in the alert message window. Discord Some may wish to share their trades with their friends in a Discord chat via webhook chat bot. Messages are configured to notify of the pattern type with targets and stop values. A bot can be configured through the integration menu in a Discord chat to which you have appropriate access. Select Discord from the 3rd party drop down menu and place your chat bot URL in the alert message window when configuring alerts. 👉  For further information regarding alert setup, refer to the platform specific instructions given by the chosen third party provider. █   IMPORTANT NOTES Setting Alerts For alert messages to be properly delivered on order fills it is necessary to place the following placeholder in the alert message box when creating an alert. {{strategy.order.alert_message}} This placeholder will auto-populate the alert message with the appropriate syntax that is designated for the 3rd party selected in the user menu. Order Sizing and Commissions The values that are sent in alert messages are populated from live metrics calculated by the strategy. This means that the actual values in the "Properties" tab are used and must be set by the user. The initial capital, order size, commission, etc. are all used in the calculations, so it is important to set these prior to executing live trades. Be sure to set the commission to the values used by the exchange as well. 👉  It is important to understand that the calculations on the account size take place from the beginning of the price history of the strategy. This means that if historical results have inflated or depleted the account size from the beginning of trade history until now, the values sent in alerts will reflect the calculated size based on the inputs in the "Properties" tab. To start fresh, the user must set the date in the "Inputs" tab to the current date as to remove trades from the trade history. Failure to follow this instruction can result in an unexpected order size being sent in the alert. █   FOR PINECODERS  • With the recent introduction of matrices in Pine, the script utilizes a matrix to track ​pivot points with the bars they occurred on, while tracking if that ​pivot has been traded against to prevent duplicate detections after a trade is exited.  • Alert messages are populated with placeholders ; capability that previously was only possible in alertcondition() , but has recently been extended to `strategy.*()` functions for use in the `alert_message` argument. This allows delivery of live trade values to populate in strategy alert messages.  • New arguments have been added to strategy.exit() , which allow differentiated messages to be sent based on whether the exit occurred at the stop or the limit. The new arguments used in this script are `alert_profit` and `alert_loss` to send messages to Discord
Pine Script® strategy
by Bjorgum
73
Fourier Extrapolator of Price w/ Projection Forecast [Loxx]Due to popular demand, I'm pusblishing Fourier Extrapolator of Price w/ Projection Forecast.. As stated in it's twin indicator, this one is also multi-harmonic (or multi-tone) trigonometric model of a price series xi, i=1..n, is given by: xi = m + Sum( a*Cos(w*i) + b*Sin(w*i), h=1..H ) Where: xi - past price at i-th bar, total n past prices; m - bias; a and b - scaling coefficients of harmonics; w - frequency of a harmonic ; h - harmonic number; H - total number of fitted harmonics. Fitting this model means finding m, a, b, and w that make the modeled values to be close to real values. Finding the harmonic frequencies w is the most difficult part of fitting a trigonometric model. In the case of a Fourier series, these frequencies are set at 2*pi*h/n. But, the Fourier series extrapolation means simply repeating the n past prices into the future. This indicator uses the Quinn-Fernandes algorithm to find the harmonic frequencies. It fits harmonics of the trigonometric series one by one until the specified total number of harmonics H is reached. After fitting a new harmonic , the coded algorithm computes the residue between the updated model and the real values and fits a new harmonic to the residue. see here: A Fast Efficient Technique for the Estimation of Frequency , B. G. Quinn and J. M. Fernandes, Biometrika, Vol. 78, No. 3 (Sep., 1991), pp . 489-497 (9 pages) Published By: Oxford University Press The indicator has the following input parameters: src - input source npast - number of past bars, to which trigonometric series is fitted; Nfut - number of predicted future bars; nharm - total number of harmonics in model; frqtol - tolerance of frequency calculations. The indicator plots two curves: the green/red curve indicates modeled past values and the yellow/fuchsia curve indicates the modeled future values. The purpose of this indicator is to showcase the Fourier Extrapolator method to be used in future indicators.
Pine Script® indicator
by loxx
55
VisibleChart█   OVERVIEW This library is a Pine programmer’s tool containing functions that return values calculated from the range of visible bars on the chart. This is now possible in Pine Script™ thanks to the recently-released chart.left_visible_bar_time and chart.right_visible_bar_time built-ins, which return the opening time of the leftmost and rightmost bars on the chart. These values update as traders scroll or zoom their charts, which gives way to a class of indicators that can dynamically recalculate and draw visuals on visible bars only, as users scroll or zoom their charts. We hope this library's functions help you make the most of the world of possibilities these new built-ins provide for Pine scripts. For an example of a script using this library, have a look at the Chart ​VWAP indicator. █   CONCEPTS Chart properties The new chart.left_visible_bar_time and chart.right_visible_bar_time variables return the opening time of the leftmost and rightmost bars on the chart. They are only two of many new built-ins in the `chart.*` namespace. See this blog post for more information, or look them up by typing "chart." in the Pine Script™ Reference Manual . Dynamic recalculation of scripts on visible bars Any script using chart.left_visible_bar_time or chart.right_visible_bar_time acquires a unique property, which triggers its recalculation when traders scroll or zoom their charts in such a way that the range of visible bars on the chart changes. This library's functions use the two recent built-ins to derive various values from the range of visible bars. Designing your scripts for dynamic recalculation For the library's functions to work correctly, they must be called on every bar. For reliable results, assign their results to global variables and then use the variables locally where needed — not the raw function calls. Some functions like `barIsVisible()` or `open()` will return a value starting on the leftmost visible bar. Others such as `high()` or `low()` will also return a value starting on the leftmost visible bar, but their correct value can only be known on the rightmost visible bar, after all visible bars have been analyzed by the script. You can plot values as the script executes on visible bars, but efficient code will, when possible, create resource-intensive labels, lines or tables only once in the global ​scope using var , and then use the setter functions to modify their properties on the last bar only. The example code included in this library uses this method. Keep in mind that when your script uses chart.left_visible_bar_time or chart.right_visible_bar_time , your script will recalculate on all bars each time the user scrolls or zooms their chart. To provide script users with the best experience you should strive to keep calculations to a minimum and use efficient code so that traders are not always waiting for your script to recalculate every time they scroll or zoom their chart. Another aspect to consider is the fact that the rightmost visible bar will not always be the last bar in the dataset. When script users scroll back in time, a large portion of the time series the script calculates on may be situated after the rightmost visible bar. We can never assume the rightmost visible bar is also the last bar of the time series. Use `barIsVisible()` to restrict calculations to visible bars, but also consider that your script can continue to execute past them. Look first. Then leap. █   FUNCTIONS The library contains the following functions: barIsVisible()   Condition to determine if a given bar is within the users visible time range.   Returns: (bool) True if the the calling bar is between the `chart.left_visible_bar_time` and the `chart.right_visible_bar_time`. high()   Determines the value of the highest `high` in visible bars.   Returns: (float) The maximum high value of visible chart bars. highBarIndex()   Determines the `bar_index` of the highest `high` in visible bars.   Returns: (int) The `bar_index` of the `high()`. highBarTime()   Determines the bar time of the highest `high` in visible bars.   Returns: (int) The `time` of the `high()`. low()   Determines the value of the lowest `low` in visible bars.   Returns: (float) The minimum low value of visible chart bars. lowBarIndex()   Determines the `bar_index` of the lowest `low` in visible bars.   Returns: (int) The `bar_index` of the `low()`. lowBarTime()   Determines the bar time of the lowest `low` in visible bars.   Returns: (int) The `time` of the `low()`. open()   Determines the value of the opening price in the visible chart time range.   Returns: (float) The `open` of the leftmost visible chart bar. close()   Determines the value of the closing price in the visible chart time range.   Returns: (float) The `close` of the rightmost visible chart bar. leftBarIndex()   Determines the `bar_index` of the leftmost visible chart bar.   Returns: (int) A `bar_index`. rightBarIndex()   Determines the `bar_index` of the rightmost visible chart bar.   Returns: (int) A `bar_index` bars()   Determines the number of visible chart bars.   Returns: (int) The number of bars. volume()   Determines the sum of volume of all visible chart bars.   Returns: (float) The cumulative sum of volume. ohlcv()   Determines the open, high, low, close, and volume sum of the visible bar time range.   Returns: ( ) A tuple of the OHLCV values for the visible chart bars. Example: open is chart left, high is the highest visible high, etc. chartYPct(​pct)   Determines a price level as a percentage of the visible bar price range, which depends on the chart's top/bottom margins in "Settings/Appearance".   Parameters:      pct : (series float) Percentage of the visible price range (50 is 50%). Negative values are allowed.   Returns: (float) A price level equal to the `pct` of the price range between the high and low of visible chart bars. Example: 50 is halfway between the visible high and low. chartXTimePct(​pct)   Determines a time as a percentage of the visible bar time range.   Parameters:      pct : (series float) Percentage of the visible time range (50 is 50%). Negative values are allowed.   Returns: (float) A time in UNIX format equal to the `pct` of the time range from the `chart.left_visible_bar_time` to the `chart.right_visible_bar_time`. Example: 50 is halfway from the leftmost visible bar to the rightmost. chartXIndexPct(​pct)   Determines a `bar_index` as a percentage of the visible bar time range.   Parameters:      pct : (series float) Percentage of the visible time range (50 is 50%). Negative values are allowed.   Returns: (float) A time in UNIX format equal to the `pct` of the time range from the `chart.left_visible_bar_time` to the `chart.right_visible_bar_time`. Example: 50 is halfway from the leftmost visible bar to the rightmost. whenVisible(​src, whenCond, length)   Creates an array containing the `length` last `src` values where `whenCond` is true for visible chart bars.   Parameters:      src : (series int/float) The source of the values to be included.      whenCond : (series bool) The condition determining which values are included. Optional. The default is `true`.      length : (simple int) The number of last values to return. Optional. The default is all values.   Returns: (float ) The array ID of the accumulated `src` values. avg(​src)   Gathers values of the source over visible chart bars and averages them.   Parameters:      src : (series int/float) The source of the values to be averaged. Optional. Default is `close`.   Returns: (float) A cumulative average of values for the visible time range. median(​src)   Calculates the median of a source over visible chart bars.   Parameters:      src : (series int/float) The source of the values. Optional. Default is `close`.   Returns: (float) The median of the `src` for the visible time range. vVwap(​src)   Calculates a volume-weighted average for visible chart bars.   Parameters:      src : (series int/float) Source used for the ​VWAP calculation. Optional. Default is `hlc3`.   Returns: (float) The ​VWAP for the visible time range.
Pine Script® library
by PineCoders
63
Time█   OVERVIEW This library is a Pine Script™ programmer’s tool containing a variety of time related functions to calculate or measure time, or format time into string variables. █   CONCEPTS `formattedTime()`, `formattedDate()` and `formattedDay()` Pine Script™, like many other programming languages, uses timestamps in UNIX format, expressed as the number of milliseconds elapsed since 00:00:00 UTC, 1 January 1970. These three functions convert a UNIX timestamp to a formatted string for human consumption. These are examples of ways you can call the functions, and the ensuing results: CODE RESULT formattedTime(timenow) >>> "00:40:35" formattedTime(timenow, "short") >>> "12:40 AM" formattedTime(timenow, "full") >>> "12:40:35 AM ​UTC​" formattedTime(1000 * 60 * 60 * 3.5, "HH:mm") >>> "03:30" formattedDate(timenow, "short") >>> "4/30/22" formattedDate(timenow, "medium") >>> ​"Apr​ 30, 2022" formattedDate(timenow, "full") >>> "Saturday, April 30, 2022" formattedDay(timenow, "E") >>> "Sat" formattedDay(timenow, "dd.MM.yy") >>> "30.04.22" formattedDay(timenow, "yyyy.MM.dd G 'at' hh:mm:ss z") >>> "2022.04.30 AD at 12:40:35 UTC" These functions use str.format() and some of the special formatting codes it allows for. Pine Script™ documentation does not yet contain complete specifications on these codes, but in the meantime you can find some information in the The Java™ Tutorials and in Java documentation of its MessageFormat class . Note that str.format() implements only a subset of the MessageFormat features in Java. `secondsSince()` The introduction of varip variables in Pine Script™ has made it possible to track the time for which a condition is true when a script is executing on a realtime bar. One obvious use case that comes to mind is to enable trades to exit only when the exit condition has been true for a period of time, whether that period is shorter that the chart's timeframe, or spans across multiple realtime bars. For more information on this function and varip please see our Using `varip` variables publication. `timeFrom( )` When plotting lines , boxes , and labels one often needs to calculate an offset for past or future end points relative to the time a condition or point occurs in history. Using xloc.bar_index is often the easiest solution, but some situations require the use of xloc.bar_time . We introduce `timeFrom()` to assist in calculating time-based offsets. The function calculates a timestamp using a negative (into the past) or positive (into the future) offset from the current bar's starting or closing time, or from the current time of day. The offset can be expressed in units of chart timeframe, or in seconds, minutes, hours, days, months or years. This function was ported from our Time Offset Calculation Framework . `formattedNoOfPeriods()` and `secondsToTfString()` Our final two offerings aim to confront two remaining issues: How much time is represented in a given timestamp? How can I produce a "simple string" timeframe usable with request.security() from a timeframe expressed in seconds? `formattedNoOfPeriods()` converts a time value in ​ms to a quantity of time units. This is useful for calculating a difference in time between 2 points and converting to a desired number of units of time. If no unit is supplied, the function automatically chooses a unit based on a predetermined time step. `secondsToTfString()` converts an input time in seconds to a target timeframe string in timeframe.period string format. This is useful for implementing stepped timeframes relative to the chart time, or calculating multiples of a given chart timeframe. Results from this function are in simple form, which means they are useable as `timeframe` arguments in functions like request.security() . █   NOTES Although the example code is commented in detail, the size of the library justifies some further explanation as many concepts are demonstrated. Key points are as follows:  • ​Pivot points are used to draw lines from. `timeFrom( )` calculates the length of the lines in the specified unit of time.   By default the script uses 20 units of the charts timeframe. Example: a 1hr chart has arrows 20 hours in length.  • At the point of the arrows `formattedNoOfPeriods()` calculates the line length in the specified unit of time from the input menu.   If “Use Input Time” is disabled, a unit of time is automatically assigned.  • At each ​pivot point a label with a formatted date or time is placed with one of the three formatting helper functions to display the time or date the ​pivot occurred.  • A label on the last bar showcases `secondsSince()` . The label goes through three stages of detection for a timed alert.   If the difference between the high and the open in ticks exceeds the input value, a timer starts and will turn the label red once the input time is exceeded to simulate a time-delayed alert.  • In the bottom right of the screen `secondsToTfString()` posts the chart timeframe in a table. This can be multiplied from the input menu. Look first. Then leap. █   FUNCTIONS formattedTime(timeInMs, format)   Converts a UNIX timestamp (in milliseconds) to a formatted time string.   Parameters:      timeInMs : (series float) Timestamp to be formatted.      format : (series string) Format for the time. Optional. The default value is "HH:mm:ss".   Returns: (string) A string containing the formatted time. formattedDate(timeInMs, format)   Converts a UNIX timestamp (in milliseconds) to a formatted date string.   Parameters:      timeInMs : (series float) Timestamp to be formatted.      format : (series string) Format for the date. Optional. The default value is "yyyy-MM-dd".   Returns: (string) A string containing the formatted date. formattedDay(timeInMs, format)   Converts a UNIX timestamp (in milliseconds) to the name of the day of the week.   Parameters:      timeInMs : (series float) Timestamp to be formatted.      format : (series string) Format for the day of the week. Optional. The default value is "EEEE" (complete day name).   Returns: (string) A string containing the day of the week. secondsSince(cond, resetCond)   The duration in milliseconds that a condition has been true.   Parameters:      cond : (series bool) Condition to time.      resetCond : (series bool) When `true`, the duration resets.   Returns: The duration in seconds for which `cond` is continuously true. timeFrom(from, qty, units)   Calculates a +/- time offset in variable units from the current bar's time or from the current time.   Parameters:      from : (series string) Starting time from where the offset is calculated: "bar" to start from the bar's starting time, "close" to start from the bar's closing time, "now" to start from the current time.      qty : (series int) The +/- qty of units of offset required. A "series float" can be used but it will be cast to a "series int".      units : (series string) String containing one of the seven allowed time units: "chart" (chart's timeframe), "seconds", "minutes", "hours", "days", "months", "years".   Returns: (int) The resultant time offset `from` the `qty` of time in the specified `units`. formattedNoOfPeriods(​ms, unit)   Converts a time value in ​ms to a quantity of time units.   Parameters:      ms : (series int) Value of time to be formatted.      unit : (series string) The target unit of time measurement. Options are "seconds", "minutes", "hours", "days", "weeks", "months". If not used one will be automatically assigned.   Returns: (string) A formatted string from the number of `ms` in the specified `unit` of time measurement secondsToTfString(tfInSeconds, mult)   Convert an input time in seconds to target string TF in `timeframe.period` string format.   Parameters:      tfInSeconds : (simple int) a timeframe in seconds to convert to a string.      mult : (simple float) Multiple of `tfInSeconds` to be calculated. Optional. 1 (no multiplier) is default.   Returns: (string) The `tfInSeconds` in `timeframe.period` format usable with `request.security()`.
Pine Script® library
by PineCoders
35
Relative Bandwidth FilterThis is a very simple script which can be used as measure to define your trading zones based on volatility. Concept This script tries to identify the area of low and high volatility based on comparison between Bandwidth of higher length and ATR of lower length. Relative Bandwidth = Bandwidth / ATR Bandwidth can be based on either Bollinger Band, Keltner Channel or Donchian Channel. Length of the bandwidth need to be ideally higher. ATR is calculated using built in ATR method and ATR length need to be ideally lower than that used for calculating Bandwidth. Once we got Relative Bandwidth, the next step is to apply Bollinger Band on this to measure how relatively high/low this value is. Overall - If relative bandwidth is higher, then volatility is comparatively low. If relative bandwidth is lower, then volatility is comparatively high. Usage This can be used with your own strategy to filter out your non-trading zones based on volatility. Script plots a variable called "Signal" - which is not shown on chart pane. But, it is available in the data window. This can be used in another script as external input and apply logic. Signal values can be 1 : Allow only Long -1 : Allow only short 0 : Do not allow any trades 2 : Allow both Long and Short
Pine Script® indicator
by Trendoscope
19
Breakout Probability (Expo)█ Overview Breakout Probability is a valuable indicator that calculates the probability of a new high or low and displays it as a level with its percentage. The probability of a new high and low is backtested, and the results are shown in a table— a simple way to understand the next candle's likelihood of a new high or low. In addition, the indicator displays an additional four levels above and under the candle with the probability of hitting these levels. The indicator helps traders to understand the likelihood of the next candle's direction, which can be used to set your trading bias. █ Calculations The algorithm calculates all the green and red candles separately depending on whether the previous candle was red or green and assigns scores if one or more lines were reached. The algorithm then calculates how many candles reached those levels in history and displays it as a percentage value on each line. █ Example In this example, the previous candlestick was green; we can see that a new high has been hit 72.82% of the time and the low only 28.29%. In this case, a new high was made. █ Settings Percentage Step The space between the levels can be adjusted with a percentage step. 1% means that each level is located 1% above/under the previous one. Disable 0.00% values If a level got a 0% likelihood of being hit, the level is not displayed as default. Enable the option if you want to see all levels regardless of their values. Number of Lines Set the number of levels you want to display. Show Statistic Panel Enable this option if you want to display the backtest statistics for that a new high or low is made. (Only if the first levels have been reached or not) █ Any Alert function call An alert is sent on candle open, and you can select what should be included in the alert. You can enable the following options: Ticker ID Bias Probability percentage The first level high and low price █ How to use This indicator is a perfect tool for anyone that wants to understand the probability of a breakout and the likelihood that set levels are hit. The indicator can be used for setting a stop loss based on where the price is most likely not to reach. The indicator can help traders to set their bias based on probability. For example, look at the daily or a higher timeframe to get your trading bias, then go to a lower timeframe and look for setups in that direction. ----------------- Disclaimer The information contained in my Scripts/Indicators/Ideas/Algos/Systems does not constitute financial advice or a solicitation to buy or sell any securities of any type. I will not accept liability for any loss or damage, including without limitation any loss of profit, which may arise directly or indirectly from the use of or reliance on such information. All investments involve risk, and the past performance of a security, industry, sector, market, financial product, trading strategy, backtest, or individual's trading does not guarantee future results or returns. Investors are fully responsible for any investment decisions they make. Such decisions should be based solely on an evaluation of their financial circumstances, investment objectives, risk tolerance, and liquidity needs. My Scripts/Indicators/Ideas/Algos/Systems are only for educational purposes!
Pine Script® indicator
by Zeiierman
286
Point of Control V2 The genesis of this project was to create a POC library that would be available to deliver volume profile information via pine to other scripts of indicators and strategies. This is a republish of an invite only script to open access This is the indicator version of the library function. A few points of significance: - Allows the choice of reset of the study period, day/week or bars. This is simple enough to expand to other conditions - Bar count resets starting from the beginning of the data set (bar index =0) vs bars back from the end of the data set - A 'period' in this context is the time between resets - the start of the POC (eg. start of Day or Week) until it resets (for example at the beginning of a next day or week) - Automates the determination of the increment level rather than the user specifying ticks or price brackets - Does not allow for setting the # of rows and then calculating the implied price increment levels - When a period is complete it is often useful to look back at the POCs of historical periods, or extend them forward. - This script will find the historical POCs around the current price and display them rather than extend all the historical POC lines to the right - This script also looks across all the period POCs and identifies the master POC or what I call the Grand POC, and also the next 3 runner up POCs This indicator is also available as a library. BINANCE:BTCUSDT NSE:NIFTY OANDA:XAUUSD NASDAQ:AAPL TVC:USOIL
Pine Script® indicator
by JohnBaron
28
Andean OscillatorThe following script is an original creation originally posted on the blog section of the broker Alpaca. The proposed indicator aims to measure the degree of variations of individual up-trends and down-trends in the price, thus allowing to highlight the direction and amplitude of a current trend. Settings Length : Determines the significance of the trends degree of variations measured by the indicator. Signal Length : Moving average period of the signal line. Usage The Andean Oscillator can return multiple information to the user, with its core interpretation revolving around the bull and bear components. A rising bull component (in green) indicates the presence of bullish price variations while a rising bear component (in red) indicates the presence of bearish price variations. When the bull component is over the bear component market is up-trending, and the user can expect new higher highs. When the bear component is over the bull component market is down-trending, and the user can expect new lower lows. The signal line (in orange) allows a more developed interpretation of the indicator and can be used in several ways. It is possible to use it to filter out potential false signals given by the crosses between the bullish and bearish components. As such the user might want to enter a position once the bullish or bearish component crosses over the signal line instead. Details Measuring the degree of variations of trends in the price by their direction (up-trend/down-trend) can be done in several way. The approach taken by the proposed indicator makes use of exponential envelopes and the naive computation of standard deviation. First, exponential envelopes are obtained from both the regular prices and squared prices, thus giving two upper extremities, and two lower extremities. The bullish component is obtained by first subtracting the upper extremity of the squared prices with the squared upper extremity of regular prices, the square root is then applied to this result. The bearish component is obtained in the same way, but makes use of the lower extremities of the exponential envelopes.
Pine Script® indicator
by alexgrover
84
Auto Trendline Indicator (based on fractals)A tool that automatically draws out trend lines by connecting the most recent fractals. Description: The process of manual drawing out trend lines is highly subjective. Many times, we don’t trade what we see, but what we “want to see”. As a result, we draw lines pointing to the direction that we wishfully want price to move towards. While there are no right/wrong ways to draw trend lines, there are, however, systematic/unsystematic ways to draw trend lines. This tool will systematically draw out trend lines based on fractals. Additional feature: This tool will also plot out symbols (default symbol “X”) to signify points of crossings. This can be useful for traders considering to use trend lines as part of their trading strategies. Here is an interesting observation on the price actions of NASDAQ futures on a 5 second chart during regular trading hours on July 14, 2022. It’s a phenomenon. People like to see straight lines connecting HL/LH, etc., so it's possible for the market as a whole to psychologically react to these lines. However, it is important to note that is is impossible to predict the direction of price. In the case above, price could have tanked below auto-drawn trend line. Fractal based trend lines should only be taken as references and regarded as price levels. No studies have ever proven that the slope of trend lines can indicate price's future direction. More about fractals: To understand more about fractals: www.investopedia.com www.tradingview.com Contrary to what it sounds like, fractal in "technical analysis" does not refer to the recursive self-repeating patterns that appear in nature, such as the mesmerizing patterns found in snowflakes. The Fractal Markets Hypothesis claims that market prices exhibit fractal properties over time. Assuming this assertion to be true, then fractals can be used a tool to represent the chaotic movements of price is a simplified manner. The purpose of this exercise is to take a tool that is readily available (ie. in this case, TradingView’s built-in fractals tool), and to create a newer tool based on it. Parameters: Fractal period (denoted as ‘n’ in code): It is the number of bars bounding a high/low point that must be lower/higher than it, respectively, in order for fractal to be considered valid. Period ‘n’ can be adjusted in this tool. Traditionally, chartists pick the value of 5. The longer it is, the less noise seen on the chart, and the pivot point may also be exhibited in higher timeframes. The drawback is that it will increase the period of lag, and it will take more bars to confirm the printed fractal. Others: Intuitive parameters such as whether to draw historical trend lines, what color to use, which way to extend the lines, and whether or not to show points of crossings.
Pine Script® indicator
by DojiEmoji
64
Chart VWAP█   OVERVIEW This indicator displays a ​Volume-Weighted Average Price anchored to the leftmost visible bar of the chart. It dynamically recalculates when the chart's visible bars change because you scroll or zoom your chart. If you are not already familiar with ​VWAP, our Help Center will get you started. The typical ​VWAP is designed to be used on intraday charts, as it resets at the beginning of the day. Our Rolling ​VWAP , instead, resets on a rolling time window. You may also find the VWAP Auto Anchored built-in indicator worth a try. █   HOW TO USE IT Load the indicator on an active chart (see the Help Center if you don't know how). By default, it displays the chart's ​VWAP in orange and a simple average of the chart's visible close values in gray. This average can be used as a companion to the ​VWAP, since both are calculated from the same set of bars. The script's settings allow you to hide it. You may also use the script's settings to enable the display of the chart's OHLC (open, high, low, close) levels and the values of the high and low. These are also calculated from the range of visible bars. You can complement the high and low lines with their price and their distance in percent from the chart's latest visible close . You can use the levels to quickly identify the distances from extreme points in the visible price range, as well as observe the visible chart's beginning and end prices. █   NOTES FOR Pine Script™ CODERS This script showcases three novelties:  • Dynamic recalculation on visible bars  • The VisibleChart library by PineCoders  • The new `anchor` parameter of ta.vwap() Dynamic recalculation on visible bars This script behaves in a novel way made possible by the recent introduction of two new built-in variables: chart.left_visible_bar_time and chart.right_visible_bar_time , which return the opening time of the leftmost and rightmost visible bars on the chart. These are only two of many new built-ins in the `chart.*` namespace. See this blog post for more information, or look up them up by typing "chart." in the Pine Script™ Reference Manual . Any script using chart.left_visible_bar_time or chart.right_visible_bar_time acquires a unique property, which triggers its recalculation when traders scroll or zoom their chart, causing the range of visible bars to change. This new capability is what makes it possible for this script to calculate its ​VWAP on the chart's visible bars only, and dynamically recalculate if the user scrolls or zooms their chart. This script is just a start to the party; endless uses for indicators that redraw on changes to the chart will no doubt emerge through the hands of our community's Pine Script™ programmers. The VisibleChart library by PineCoders The newly published VisibleChart library is designed to help programmers benefit from the new capabilities made possible by the fact that Pine Script™ code can now tell when it is executing on visible bars. The library's description, functions and example code will help programmers make the most of the new feature. This script uses three of the library's functions:  • `PCvc.vVwap()` calculates a ​VWAP for visible bars. ​​​​ • `PCvc.​avg()` calculates the average of a source value for visible bars only. We use it to calculate the average close (the default source).  • `PCvc.chartXTimePct(25)` calculates a time value corresponding to 25% of the horizontal distance between visible bars, starting from the left. The new `anchor` parameter of ta.vwap() Our script also uses this new `anchor` parameter to reset the ​VWAP at the leftmost visible bar. See how simple the code is for the VisibleChart library's `vVwap()` function. Look first. Then leap.
Pine Script® indicator
by TradingView
17
Ichimoku Kinkō hyō 目均衡表█ OVERVIEW Ichimoku is known to be an Indicator that completes itself, for its power but also for its complexity. This is why I decided to improve the work of Goichi Hosoda in order to offer the maximum number of options for the most seasoned users but also beginners with options to simplify the reading of Ichimoku (such as a panel directly giving you the status of each Ichimoku options or Supports/Resistances drawn automatically according to the conditions chosen in the settings. █ OPTIONS Here is the complete list of options to implement : - "Source" and "Alternative Source" (with lots of choices) - Heikin Ashi volume. - Weighted Moving Average Smoothing - Minimum, Maximum and Adaptive Percentage Length adjustable for Tenkan-Sen, Kijun-Sen, Chikou Span and Senkou-Span) - The Chikou has a Filter with modifiable Length (in Lookback Percentage) - Advanced Filter Settings: Volume, Tenkan-Sen/Kijun-Sen Cross, Volatility, Tenkan-Sen Equal Kijun-Sen, Chikou Greater Than Price, Chikou Momentum, Price Greater Than Kumo, Price Greater Than Tenkan-Sen, Chikou Trend Filter . - Oscillator volume adjustable via drop-down menu with 5 types of oscillators available: "TFS Volume", "On Balance Volume", "Klinger Volume", "Cumulative Volume", "Volume Zone". - Relative Volume Strength Index with Length, Peak and EMA's adjustable. 3 Oscillators available: “On Balance Volume”, “Cumulative Volume”, “Price Volume Trend”. - Volatility adjustable with Fast and Slow Length. - Totally customizable Support and Resistance. - Bar Trend Color based on chosen settings. - Fully customizable help panel. - Alerts available for: Labels Detection, Support/Resistance Line Cross, Panel Trend Status Direction. █ NOTES Remember to only make a decision once you are sure of your analysis. Good trading sessions to everyone and don't forget, risk management remains the most important!
Pine Script® indicator
by RickSimpson
124