Auf geht's

Indikatoren und Strategien

security free MTF example - JDThis script is not intended for trading purposes but gives some examples how you can get values from previous candles in other timeframes, without using security calls. NOTE: the "open", "high" and "low" values are calculated "on the fly", as the bar progresses, the "close" is determined at the end of the timeframe, so it's only know at the first bar of the next time period JD. #NotTradingAdvice #DYOR Disclaimer. I AM NOT A FINANCIAL ADVISOR. THESE IDEAS ARE NOT ADVICE AND ARE FOR EDUCATION PURPOSES ONLY. ALWAYS DO YOUR OWN RESEARCH!
Pine Script® Indikator
von Duyck
25
Reverse Stochastic Momentum Index On ChartIntroducing the Reverse Stochastic Momentum Index "On Chart" version According to Investopedia : “The Stochastic Momentum Index (SMI) is a more refined version of the stochastic oscillator, employing a wider range of values and having a higher sensitivity to closing prices.” The SMI is considered a refinement of the stochastic oscillator developed by William Blau and introduced in 1993 in an attempt to provide a more reliable indicator, less subject to false swings. It calculates the distance of the current closing price as it relates to the median of the high/low range of price. The SMI has a normal range of values between +100 and -100. When the present closing price is higher than the median, or midpoint value of the high/low range, the resulting value is positive. When the current closing price is lower than that of the midpoint of the high/low range, the SMI has a negative value. Here I have reverse engineered the SMI formula to derive 2 functions. One function calculates the chart price at which the SMI will reach a particular SMI scale value. The second function calculates the chart price at which the SMI will crossover its signal line. I have employed those functions here to give the "crossover" price levels for : Upper alert level ( default 40, color : aqua blue ) Mid-Line ( default value 0, color : white ) Lower alert level ( default -40, color : purple ) Signal line ( default 13, colors : bright red & lime green ) And also to give the SMI eq price ( colors : red & green ) The midline, upper and lower alert levels return the closing price which would make SMI equal to their respective values The user can infer from this that..... Closing above these prices will cause the Stochastic Momentum Index to cross above the associated levels Closing below these prices will cause the Stochastic Momentum Index to cross below the associated levels Signal line returns the closing price where Stochastic Momentum Index is equal to its signal line The user can infer from this that..... Closing above this price will cause the Stochastic Momentum Index to cross above the signal line Closing below this price will cause the Stochastic Momentum Index to cross below the signal line SMI eq price returns the closing price which would make the SMI equal to its previous value The user can infer from this that..... Closing above this price will cause the Stochastic Momentum Index to increase Closing below this price will cause the Stochastic Momentum Index to decrease Note : all returned prices have a returned value filter to replace any values below zero with zero to help prevent auto focus issues. These levels are displayed as plotted lines on the chart and also as an optional infobox with choice of displayed info. This allows the user to see directly on the chart the interplay between the various crossover levels and price action and to precisely plan entries, exits and stops for their SMI based trades. Traditionally traders and analysts will consider: Positives values above 40 indicate a bullish trend Negative values below -40 indicate a bearish trend . Common traditional ways to derive signals from the SMI : When the SMI crosses below -40 and then moves back above it, a buy signal is generated. When the SMI crosses above +40 and then moves back below it, a sell signal is generated. When the SMI line crosses above the signal line. A signal to buy is generated When the SMI line crosses below the signal line signal to sell is generated. When the SMI crosses above the zeroline, signal line and the SMI eq level many interpret that as a full bullish bias signal and take trades only in that direction, vice versa for bearish bias. Traders also look for divergences between the SMI and price action. The SMI is often used in conjunction with the Chande Momentum Oscillator or R squared indicator to determine overall market trendiness where the SMI is used to determine the direction of the trend, and also with volume indicators to show if the momentum carries significant selling or buying pressure.
Pine Script® Indikator
von The_Caretaker
27
Tick Data DetailedHello All, After Tick Chart and Tick Chart RSI scripts, this is Tick Data Detailed script. Like other tick scrips this one only works on real-time bars too. it creates two tables: the table at the right shows the detailed data for Current Bar and the table at the left shows the detailed data for all calculated bars (cumulative). the script checks the volume on each tick and add the tick and volume to the specified level (you can set/change levels) The volume is multiplied by close price to calculate real volume .There are 7 levels/zones and the default levels are: 0 - 10.000 10.000 - 20.000 20.000 - 50.000 50.000 - 100.000 100.000 - 200.000 200.000 - 400.000 > 400.000 With this info, you will get number of ticks and total volumes on each levels. The idea to separate this levels is in order to know which type of traders trade at that moment. for example volume of whale moves are probably greater than 400.000 or at least 100.000. Or volume of small traders is less than 10.000 or between 20.000-50.000. You will get info if there is anomaly on each candle as well. what is anomaly definition? Current candle is green but Sell volume is greater than Buy volume or current candle is red but Buy volume is greater than Sell volume . it is shown as (!). you should think/search why/how this anomaly occurs. You can see screenshot about it below. also "TOTAL" text color changes automatically. if Buy volume is greater than Sell volume then its color becomes Green, if Sell volume is greater than Buy volume then its color becomes Red (or any color you set) Optionally you can change background and text colors as shown in the example below. Explanation: How anomaly is shown: You can enable coloring background and set the colors as you wish: And Thanks to @Duyck for letting me use the special characters from his great script. Enjoy!
Pine Script® Indikator
von LonesomeTheBlue
93
Monte Carlo Simulation - Random WalkHello All, Monte Carlo Simulation is a model used to predict the probability of different outcomes when the intervention of random variables is present. it is used by professionals in such widely disparate fields as finance, project management etc. You can find many articles about Monte Carlo Simulation on the net. In this script I tried to make Monte Carlo Simulation and "Random Walk". it calculates results over and over, each time using a different set of random values that is created using historical data (500 times by default) and show min-max and some random paths. number of "random walks" is calculated by using number of bars to predict, so if you change "Number of Bars to Predict" then number of random walks may change. Total number of the lines must be less than 500. "Number of Simulations " is 500 by default, more simulation better results. but if you increase it a lot then you may get "loop takes too long error" "Number of Bars to Predict" can be between 10-100 "Number of Bars to use as Data Source" is the number of historical bars to use in simulations Thanks to Ricardo Santos (@RicardoSantos) for letting me use his Random Number Generator Function. P.S. I am not mathematician and I tried to make it as far as I understood the method. so if you see any issue let me know please. Some examples: Number of Bars to Predict = 100: Number of Bars to Predict = 10: if you enable "Keep Past Min-Max Levels" option then min-max levels will stay on the chart Enjoy!
Pine Script® Indikator
von LonesomeTheBlue
49
Exploring UnicodeThis script demonstrates how to display Unicode characters and symbols, including emoji, in Pine:  • Part 1 displays multi-line labels on hi/lo pivots.  • Part 2 displays price/volume bumps using small up/down arrows plotted with plotchar() .  • Part 3 detects bounces and uses plotshape() to mark them.   You can use our `f_bounceFrom()` function from this part as confirmation for signals in your strategies. Note that the labels displayed on pivots with the code in Part 1 are plotted in the past. In realtime, they would only appear where they are after 50 bars have elapsed from that point. The other plots are plotted on the bar where their conditions are detected. You can display thousands of Unicode characters and symbols using Pine. As you can see with our script, it is very easy to do so. The challenge will often be to find the exact symbols you are looking for. Many websites exist to help you explore Unicode characters or symbols. The PineCoders Resources page contains a section presenting a few of them. Duyck has a Unicode font function script containing functions to convert strings to monospaced Unicode representations. TradingView uses the Trebuchet font for most of its text, including text displayed with Pine scripts. While its numerals are monospace and will align vertically in labels text, Duyck's functions will be handy when you need to convert characters to a monospaced form, so they also align vertically in multi-line labels. What is Unicode? Unicode is to character encoding what Wikipedia is to knowledge; it holds codes to a good proportion of the characters or symbols used by humans, past or present. In the early days of computing, environments from different manufacturers often used different character encoding schemes, making transport between them difficult. Unicode solves that challenge. It is a comprehensive encoding scheme that visionaries from Xerox and Apple came up with in the late 80's. The addition of members from the Research Libraries Group, Sun Microsystems, Microsoft, Next and Metaphor created the "Unicode working group" and later, the Unicode Consortium , which continues to improve and manage the Unicode standard. Theoretically, Unicode encodes values representing characters or glyphs —not their pictorial representations. The letters "A" or "a", or the blue heart emoji "💙" are each represented by a Unicode value. In practice, however, there are many different versions of the Latin alphabet in Unicode. That is how our low pivot label can display different representations of the letters "ITV". The exact rendition of Unicode symbols on a specific device is left to equipment manufacturers and typeface designers. The current Unicode space is comprised of 17 planes of 65,536 characters each, which allows for more than one million code points . Planes are further divided into character blocks , which typically hold a character set corresponding to one script—or language. Emoticons are in the character block starting at U+1F600. Look first. Then leap.
Pine Script® Indikator
von TradingView
13
Unicode font function - JDPinescript only allows the use of one type of font in texts and label, which causes some inconveniences: - It's hard to make a label or text "look nice" and clear because it's not possible to use a different font for titles, etc. - Because the default Pinescript font is not a monospaced font, (in Pinescript different characters have different widths) this makes it really difficult to align things in a label on different rows and causes everything to be "all over the place" and look messy With the workaround in this script, you can "translate" the text string that you want to put in a label into a text with either upper case, bold and/or italic characters, allowing for more control over the layout of the label text, by adding differently styled titles, control over spacing for columns, etc... The characters provided in this script are an example of a monospaced font, but can easily be replaced by copy-pasting in other characters in the appropriate section and the script will then use the new characters as replacements. This script is to show the possibilities and principles of the functions. The principles of this framework can be used to build your own go-to "text style conversion" functions, for styles that you use a lot, for example for titles. A big shoutout to @DonovanWall, for the awesome character replacement idea that I built upon!!! A shoutout also to the PineCoders community, who provide an infinite source of knowlegde and inspiration!! Enjoy! Gr, JD.
Pine Script® Indikator
von Duyck
18
Grid Bot SimulatorThis script is a grid bot simulator for ranging/choppy markets. Prices are divided into grids, or trade zones, that will trigger signals each time a new zone is entered. During ranging markets, each transaction is followed by a “take profit.” As the market starts to trend, transactions are stacked (compare to DCA), until the market consolidates. No signals are triggered above the Upper Limit or Below the Lower Limit. Settings overview: Upper Limit/Lower Limit : Highest and Lowest values for entire grid. Number of Grids : Number of trade zones. Show Grids : Show or hide all gridlines. Show Only Current Grids : Only display the grids just above and just below the current trade zone. High/Low for signals : If enabled, signals are triggered as soon as the price touches the next zone. If disabled, signals are triggered after bar closes. Enable this for “Once Per Bar alerts. Disable for “Once Per Bar Close” alerts. Highlight Trade Zones The grid bot should work well during ranging/choppy markets. Each zone will have only one trade, and then will immediately take profit in the next zone. Ranging/Choppy Market However, trending markets can produce multiple signals in rapid succession: Trending Market If the gridlines are compressing the chart space, enable the “Show Only Current Grids” in settings. Show Only Current Grids disabled Show Only Current Grids enabled When changing symbols, adjust the Upper and Lower Limits to accommodate the new symbol. Otherwise, the chart will look compressed. XBTUSD chart with ETHUSDT settings The bot is a proof-of-concept and is considered experimental . Possible future updates will include Fibonacci grids and “smart entry/exits,” depending on the current trend. Comments and suggestions are encouraged.
Pine Script® Indikator
von xxattaxx
87
Auto Fib Speed Resistance Fans by DGTFibonacci Speed and Resistance Fan is an analytical drawing tool used to indicate the support and resistance levels of an existing trend and the price level at which possible changes in the trend may occur. A Fibonacci Speed Resistance Fan consists of a trend line drawn between two extreme points - a trough and opposing peak or a peak and opposing trough - on which a set of sequential speed resistance lines are drawn above (which represents time) and below (which represents price). These lines are drawn based on time/price percentages of the distance between the beginning and the end of the trend line. Speed resistance lines not only help to measure trend corrections but also measure the speed of a trend (the rate at which a trendline ascends or descends) Traders can use the lines of the Fibonacci Speed and Resistance Fan to predict key points of resistance or support, at which they might expect price trends to reverse. Once a trader identifies patterns within a chart, they can use those patterns to predict future price movements and future levels of support and resistance. Traders use the predictions to time their trades. Key support and resistance levels tend to occur frequently at the 61.8-percent level on both uptrends and downtrends. Please check for further details in the education post that I will share shortly after this publication : Nobody appears to know whether Fibonacci tools work because markets exhibit some form of natural pattern or because many investors use Fibonacci ratios to predict price movements, making them a self-fulfilling prophecy. █ Study OPTIONS   Auto Fibonacci Speed and Resistance Fan , the main aim of the study     - Pivot threshold can be adjusted via “Deviation” and “Depth” input options ‏    - Historical Fans option will allow plotting of Speed and Resistance Fans on previous pivot high/lows     - Ability to set ALERTs for the Speed and Resistance Levels     - Price Grid Lines if extended it will result with Fib Retracement levels     - All lines, line levels are customizable, default values are set exactly to the same with the available Fib Speed and Resistance Fan drawing tool   Zig Zag – Derived from build-in Auto Fib Retracement with some customization options. Example Usages : Disclaimer : Trading success is all about following your trading strategy and the indicators should fit within your trading strategy, and not to be traded upon solely The script is for informational and educational purposes only. Use of the script does not constitute professional and/or financial advice. You alone have the sole responsibility of evaluating the script output and risks associated with the use of the script. In exchange for using the script, you agree not to hold dgtrd TradingView user liable for any possible claim for damages arising from any decision you make based on use of the script
Pine Script® Indikator
von dgtrd
131
Correlation [array's]This script isn't about creating a correlation script with labels, there is a perfect working example of @Mango2Juice (Correlation Matrix, which was inspired by @Daveatt's Correlation Matrix) The intention was making it with the use of as less code as possible, looping through array's The Pine correlation function doesn't work consistently in a local scope (loop), so I had to work around it Inspired by @ZenAndTheArtOfTrading's Correlation Meter (using array.covariance and array.stdev) and especially with the help of @RicardoSantos and @LonesomeTheBlue I've managed to do this Symbols, timeframe, look-back period, colors and limits can be changed There is always room for improvement, but I think it shows what is possible. Many thanks to the people who I've mentioned, and of course to Tradingview! (Without the Earth nothing can grow) Cheers!
Pine Script® Indikator
von fikira
19
RedK_Portfolio Tracker v2: few enhancements and display optionsThis is an update for the PTracker v1 that I published couple of days ago. wanted to publish this as a separate script to get a chance to show how the new Portfolio Summary Infobox can be displayed on the price chart as an option. In my opinion, that info box is the most important element in this tool and that's the piece i was most looking for. quick note here: you can track your portfolio (if not so many positions) by entering something like (without the brackets) in TradingView's chart symbol area - TradingView will resolve these symbols and chart the total -- there's a nice post by our friend @boji1 about this in a lot more details - however, that wouldn't show the stats that i need to look at to track my portfolio on daily basis. i also made couple of other enhancements, like adding the ability to include "free cash" in the portfolio - While this free cash value will impact the Total P/L and P/L %, as part of the overall portfolio (and the denominator), it will not impact the "cost of positions" or the (current) "value of positions" -- also "Cash" will not count towards the total 10 positions that we can track with this tool. Using Portfolio Tracker as a floating panel on the price chart ==================================================== By default, when the Portfolio Tracker is added to the chart, it will occupy its own lower panel like the picture above. if your charts are already busy (like mine :)) - you most probably already have a couple of lower studies and it's crowded there. in this case, you can use the Object Tree tool after adding the PTracker, to drag it onto the price panel, or you can also do that by right-clicking on the infobox and choose to move up to the price panel. when you do that, remember to also use the Style settings of PTracker to hide both Portfolio and PnL plots, and choose Scale = no scale - this way you get the infobox to work like a floating panel on the price chart here's a screenshot that shows this scenario - also shows how the infobox color can be easily changed from the PTracker settings to suit your chart background and for best visibility i hope this is useful in your trading - i look forward to @TradingView team surprising us with a real portfolio tracking capability soon :) good luck.
Pine Script® Indikator
von RedKTrader
18
Higher Order PivotsFirst order pivot points are defined as 3 or 5 bar "V" shaped patterns. For example a high with a lower high either side of the peak and in the case of the 5 bar variant with lower highs adjacent to a high below the peak. Second order pivot points are defined by three first order pivots in the same manner. For example a peak pivot high with a lower pivot high to either side. Third order pivots follow the same pattern, a peak second order pivot high with two adjacent second order pivot highs. As it can take a significant and variable amount of time before higher order pivots are confirmed, it is generally inadvisable to use higher order pivots for live trading! However they can be used for historical analysis. For example to delineate market structure of major market inflections. For example : Delineating market structure using 2nd order pivots derived from 3 bar, 1st order pivots Major market inflections from 3rd order pivots derived from 5 bar, 1st order pivots
Pine Script® Indikator
von rumpypumpydumpy
24
RSI Bar ChartA different way to plot several RSI at once, 5 RSI with different options: - source, length, timeframe - size of indicator (width) - color change - limit change (30, 70), labels will be changed accordingly - type of RSI line (line, arrow), linewidth - offset label (at the right) There are 4 colors (RSI line) - when RSI > sell limit - when RSI > 50 but below sell limit - when RSI < 50 but above buy limit - when RSI < buy limit Arrows: Different size: Cheers!
Pine Script® Indikator
von fikira
34
[SK] Fibonacci Auto Trend ScouterThe FATS - Fibonacci Auto Trend Scouter automatically draws active trends from 2 different timeframes along with Fibonacci Support and Resistance levels. It also has a Sights feature for each timeframe which points from it's middle towards the current price. The tool is also highly customizable for you to take this indicator over 9000. If you like the tool and it adds value to you - share the love on the like button and visit my profile to check out my other indicators and subscribe, so you're notified of my next scripts and ideas! Automatic Trend Lines The indicator takes in 2 timeframes to detect High and Low values from which to draw the trend lines of each timeframe. As the values change with price movement, the lines are updated. They are color coded for uptrend and downtrend based on the direction of each individual line. Trend lines can be set up to color with only the default value on the configurations panel. - Toggle on/off Color Coded - Change Default, Uptrend, Downtrend color - Change Line Width - Change Line Style - Toggle on/off Line Extensions - Change Extended Line Width - Change Extended Line Style - Toggle On/Off labels for 7 data points of each timeframe Automatic Trend Sights This is a neat feature that may help you get a better feel for the direction the current movement is heading towards in correlation with the short or medium length timeframe trends. The sight draws a line from the middle vertical point of the trend coordinates towards the current price. They are toggled off by default but can be enabled in the configurations panel. - Toggle on/off sight on each timeframe - Change Width - Change Line Style Automatic Fibonacci Levels The tool has a very useful feature to automatically detect the highest and lowest value from the short timeframe to calculate Fibonacci support and resistant levels. To keep the chart area clean, the lines are drawn short by default towards the right side of the price but provide inputs to increase the size of the level lines towards the left and right direction. A triangle label appears to the side of each line which holds the Fibonacci level and price data inside the tooltip, hover over them to activate. - Toggle on/off color coded - Change Default, Resistance, Support colors - Change line size towards the left and right side - Change line width - Change Resistance line style - Change Support line style - Toggle on/off High and Low source line - Toggle on/off High and Low source labels
Pine Script® Indikator
von sirkriz
153
Faith IndicatorThis indicator compares buyers demand with sellers supply volumes and calculates which prevails. Therefore it only works if volume is published. Buyers demand is assumed for a period in which a higher high is reached with more volume. Sellers supply is recognized by a lower low combined with more volume. The average of sellers supplies is subtracted from buyers demand, the result is graded because a statement like “The faith in this period was ## percent” has no meaning. We can conclude to more faith and less faith but not represent it in some exact number. This indicator assigns the following grades: Very high faith graduated as 8 High faith as 6 Good faith as 4 Some Faith as 2 Little Faith as 1 Neither Faith nor Distrust as zero Self Protection Distrust graduated as -8 Fear Distrust as -6 Anxiety Distrust as -4 Suspicion Distrust as -2 Doubt Distrust as -1 It is presented as a histogram with blue staves pointing up (meaning faith) and red staves pointing down (meaning distrust) The background is colored using the Hull Agreement Indicator (Hullag), which I published before. Hullag graduates price movements in five grades to which it assigns a background color. These are as follows: grade 2: blue, clear upward movement grade 1: green, some upward movement grade 0: silver, neither upward nor downward movement grade -1: maroon, some downward movement grad -2: red, clear downward movement. Use of the Faith Indicator: The indicator shows price action/momentum as a background color and volume action analyzed as a grade of faith in the form of a histogram. Usually faith comes together with rising prices (blue/green background) and distrust with lowering prices (red/maroon background), however contrarian situations occur, e.g. lowering prices while the market has good faith. These can be explained by minority sellers who act contrary to the feelings in the market. You can then decide that this might be an unsustainable move of the quotes. If the faith indicator confirms the price movement, you might assume that the move is meaningful and will go further. Also if you see faith diminishing you might assume that the move is coming to an end and the tide is going to turn.
Pine Script® Indikator
von eykpunter
46
Hurst ExponentMy first try to implement Full Hurst Exponent. The Hurst exponent is used as a measure of long-term memory of time series. It relates to the autocorrelations of the time series and the rate at which these decrease as the lag between pairs of values increases The Hurst exponent is referred to as the "index of dependence" or "index of long-range dependence". It quantifies the relative tendency of a time series either to regress strongly to the mean or to cluster in a direction. In short, depending on the value you can spot the trending / reversing market. Values 0.5 to 1 - market trending Values 0 to 0.5 - market tend to mean revert Hurst Exponent is computed using Rescaled range (R/S) analysis. I split the lookback period (N) in the number of shorter samples (for ex. N/2, N/4, N/8, etc.). Then I calculate rescaled range for each sample size. The Hurst exponent is estimated by fitting the power law. Basically finding the slope of log(samples_size) to log(RS). You can choose lookback and sample sizes yourself. Max 8 possible at the moment, if you want to use less use 0 in inputs. It's pretty computational intensive, so I added an input so you can limit from what date you want it to be calculated. If you hit the time limit in PineScript - limit the history you're using for calculations. #################### 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 good as in historical backtesting. This post and the script don’t provide any financial advice.
Pine Script® Indikator
von QuantNomad
10
P-Square - Estimation of the Nth percentile of a seriesEstimation of the Nth percentile of a series When working with built-in functions in TradingView we have to limit our length parameters to max 4999. In case we want to use a function on the whole available series (bar 0 all the way to the current bar), we can usually not do this without manually creating these calculations in our code. For things like mean or standard deviation, this is quite trivial, but for things like percentiles, this is usually very costly. In more complex scripts, this becomes impossible because of resource restrictions from the Pine Script execution servers. One solution to this is to use an estimation algorithm to get close to the true percentile value. Therefore, I have ported this implementation of the P-Square algorithm to Pine Script. P-Square is a fast algorithm that does a good job at estimating percentiles in data streams. Here's the algorithms original paper . The chart On the chart we see: The returns of the series (blue scatter plot) The mean of the returns of the series (orange line) The standard deviation of the returns of the series (yellow line) The actual 84.1th percentile of the returns (white line) The estimatedl 84.1th percentile of the returns using the P-Square algorithm (green line) Note: We can see that the returns are not normally distributed as we can see that one standard deviation is higher than the 84.1th percentile. One standard deviation should equal the 84.1th percentile if the data is normally distributed.
Pine Script® Indikator
von lejmer
10
Auto Pitchfork, Fib Retracement and Zig Zag by DGTPitchfork is a technical indicator for a quick and easy way for traders to identify possible levels of support and resistance of an asset's price. It is presents and based on the idea that the market is geometric and cyclical in nature   Developed by Alan Andrews, so sometimes called Andrews’ Pitchfork   It is created by placing three points at the end of previous trends   Schiff and Modified Pitchfork is a technical analysis tool derived from Andrews' Pitchfork In general, traders will purchase the asset when the price falls near the support of either the center trendline or the lowest trendline. Conversely, they'll sell the asset when it approaches the resistance of either the center line or the highest trendline. █  Study OPTIONS   Auto Pitchfork , the main aim of the study ‏ ‏    Pivots threshold can be customized by “Deviation” and “Depth” input options ‏ ‏    Pitchfork Type selection, available options Andrews' Pitchfork (Original), Schiff and Modified Pitchfork ‏     Ability to set ALERTs for the Pitchfork Levels ‏     Ability to add customized levels (all level lines customizable)   Auto Fib Retracement – This is the build-in study of TradingView, slight changes applied to fit with Auto Pitchfork   Zig Zag – Derived from build-in Auto Fib Retracement with some customization options. █  Usage Tips :   Andrews' Pitchfork (Original) best fit in a Strong Trending Market   Schiff and Modified Pitchfork better with Correcting or Sideways Market. Modified Pitchfork is almost identical to a Parallel Chanel Disclaimer : Trading success is all about following your trading strategy and the indicators should fit within your trading strategy, and not to be traded upon solely The script is for informational and educational purposes only. Use of the script does not constitute professional and/or financial advice. You alone have the sole responsibility of evaluating the script output and risks associated with the use of the script. In exchange for using the script, you agree not to hold dgtrd TradingView user liable for any possible claim for damages arising from any decision you make based on use of the script
Pine Script® Indikator
von dgtrd
149
RedK Trader Pressure Index (TPX v1.0) Quick Summary --------------------- The RedK Trader Pressure Index (REDK_TPX) analyzes the changes in price bars to give the trader a clear visual insight that represents the ongoing fight between the bulls (buyers) and bears (sellers) in the market - to determine who is in control of the price action, which in turn can be helpful in a trader’s decision about how the price action may be unfolding, what type of trade and positions to take (or to close) and when is the ideal time to action. How the TPX calculation works --------------------------------------- The TPX uses a simple logic and that’s one of the things I like about it – there is no complex calculation or magic stuff - and the core idea makes sense to me, as well as being one of the ways I needed to analyze my price charts. The underlying assumption is that the buyers and sellers are competing for control of the market at all time. - if there’s more buyers than sellers in the market, and if the buyers’ (or bull) pressure is stronger (than the sellers’), they will be able pull the “price range” up – and that means that on the price chart we can expect to see an increase in value in both the “high” and the “low” of the next price bar. - Similarly, if there’s more sellers than buyers in the market, and if the sellers’ (or bear) pressure is stronger (than the buyers’), they will be able push the “price range” down – on the price chart we can expect to see a decrease in value in both the “high” and the “low” of the next price bar. So, we will use the change in high and low price, between 2 consecutive price bars, as a proxy for the bull and bear “pressures” – a (weighted) moving average of these “pressure” values are then calculated along with the “Net Pressure” – the final results are plotted. The importance of the "Control Level" ----------------------------------------------- As in similar price-action based indicators, there’s a certain threshold or “control level”, above which, the pressure becomes “dominant” when the bull or bear pressure is above that threshold, they will dominate and control the price move – this level can be found around the 25 or 30. I have included the ability to plot and adjust that control level in the TPX’s settings – and I also show some examples in the chart above (weekly chart for MSFT) The code is commented and the chart is annotated to explain how to “read” the TPX – and how to interpret the values on the price chart Using the Trader Pressure Index (TPX) in trading ------------------------------------------------------------ TPX can be valuable in showing well-supported (up or down) price moves that may lead to a strong trend that we can ride (when the pressure value is above the control level) - see exampled above TPX is also valuable in showing when there’s “lack of interest” from the buyers or the sellers (or both) – which is great in exploring chub or no-trade zones - so basically when to avoid trading. As usual, it's always recommended to use these types of "price action insight" indicators in conjunction with other trend and momentum indicators (moving averages, MACD..etc), so the insight we gain from them can be properly placed within the broader "context" - and to receive additional confimtion signals to support the trading decision. I will come back later to post something about how the TPX differs from my recently-posted Strength of Movement (SoM) because they wok completely differently but can be used together with great synergy – and also how the TPX compares to the classic DMI/ADX which uses a similar concept. Please feel free to integrate in your trading – hope you find this useful - comments and feedback are always welcome
Pine Script® Indikator
von RedKTrader
117
Tick ChartHello All, Tick Chart is created using ticks and each candlestick in Tick Chart shows the price variation of X consecutive ticks ( X : Number of Ticks Per Candle ). for example if you set Number of Ticks Per Candle = 100 then each candlestick is created using 100 ticks. so, Tick Charts are NOT time-based charts (like Renko or Point & Figure Charts). Tick is the price change in minimum time interval defined in the platform. There are several advantages of Tick Charts. You can find many articles about Tick Charts on the net. Tick Chart only works on realtime bars. You can set " Number of Ticks Per Candle " and " Number of Candles" using options. You can change color of body, wicks abd volume bars as well. The script shows current, minimum, maximum and average volumes. it also shows OHLC values on the last candle. Tick Chart using different number of ticks Volume info: Enjoy!
Pine Script® Indikator
von LonesomeTheBlue
105
Matrix Library (Linear Algebra, incl Multiple Linear Regression)What's this all about? Ever since 1D arrays were added to Pine Script, many wonderful new opportunities have opened up. There has been a few implementations of matrices and matrix math (most notably by TradingView-user tbiktag in his recent Moving Regression script: ). However, so far, no comprehensive libraries for matrix math and linear algebra has been developed. This script aims to change that. I'm not math expert, but I like learning new things, so I took it upon myself to relearn linear algebra these past few months, and create a matrix math library for Pine Script. The goal with the library was to make a comprehensive collection of functions that can be used to perform as many of the standard operations on matrices as possible, and to implement functions to solve systems of linear equations. The library implements matrices using arrays, and many standard functions to manipulate these matrices have been added as well. The main purpose of the library is to give users the ability to solve systems of linear equations (useful for Multiple Linear Regression with K number of independent variables for example), but it can also be used to simulate 2D arrays for any purpose. So how do I use this thing? Personally, what I do with my private Pine Script libraries is I keep them stored as text-files in a Libraries folder, and I copy and paste them into my code when I need them. This library is quite large, so I have made sure to use brackets in comments to easily hide any part of the code. This helps with big libraries like this one. The parts of this script that you need to copy are labeled "MathLib", "ArrayLib", and "MatrixLib". The matrix library is dependent on the functions from these other two libraries, but they are stripped down to only include the functions used by the MatrixLib library. When you have the code in your script (pasted somewhere below the "study()" call), you can create a matrix by calling one of the constructor functions. All functions in this library start with "matrix_", and all constructors start with either "create" or "copy". I suggest you read through the code though. The functions have very descriptive names, and a short description of what each function does is included in a header comment directly above it. The functions generally come in the following order: Constructors: These are used to create matrices (empy with no rows or columns, set shape filled with 0s, from a time series or an array, and so on). Getters and setters: These are used to get data from a matrix (like the value of an element or a full row or column). Matrix manipulations: These functions manipulate the matrix in some way (for example, functions to append columns or rows to a matrix). Matrix operations: These are the matrix operations. They include things like basic math operations for two indices, to transposing a matrix. Decompositions and solvers: Next up are functions to solve systems of linear equations. These include LU and QR decomposition and solvers, and functions for calculating the pseudo-inverse or inverse of a matrix. Multiple Linear Regression: Lastly, we find an implementation of a multiple linear regression, including all the standard statistics one can expect to find in most statistical software packages. Are there any working examples of how to use the library? Yes, at the very end of the script, there is an example that plots the predictions from a multiple linear regression with two independent (explanatory) X variables, regressing the chart data (the Y variable) on these X variables. You can look at this code to see a real-world example of how to use the code in this library. Are there any limitations? There are no hard limiations, but the matrices uses arrays, so the number of elements can never exceed the number of elements supported by Pine Script (minus 2, since two elements are used internally by the library to store row and column count). Some of the operations do use a lot of resources though, and as a result, some things can not be done without timing out. This can vary from time to time as well, as this is primarily dependent on the available resources from the Pine Script servers. For instance, the multiple linear regression cannot be used with a lookback window above 10 or 12 most of the time, if the statistics are reported. If no statistics are reported (and therefore not calculated), the lookback window can usually be extended to around 60-80 bars before the servers time out the execution. Hopefully the dev-team at TradingView sees this script and find ways to implement this functionality diretly into Pine Script, as that would speed up many of the operations and make things like MLR (multiple linear regression) possible on a bigger lookback window. Some parting words This library has taken a few months to write, and I have taken all the steps I can think of to test it for bugs. Some may have slipped through anyway, so please let me know if you find any, and I'll try my best to fix them when I have time to do so. This library is intended to help the community. Therefore, I am releasing the library as open source, in the hopes that people may improving on it, or using it in their own work. If you do make something cool with this, or if you find ways to improve the code, please let me know in the comments.
Pine Script® Indikator
von lejmer
21
Monte Carlo Range Forecast [DW]This is an experimental study designed to forecast the range of price movement from a specified starting point using a Monte Carlo simulation. Monte Carlo experiments are a broad class of computational algorithms that utilize random sampling to derive real world numerical results. These types of algorithms have a number of applications in numerous fields of study including physics, engineering, behavioral sciences, climate forecasting, computer graphics, gaming AI, mathematics, and finance. Although the applications vary, there is a typical process behind the majority of Monte Carlo methods: -> First, a distribution of possible inputs is defined. -> Next, values are generated randomly from the distribution. -> The values are then fed through some form of deterministic algorithm. -> And lastly, the results are aggregated over some number of iterations. In this study, the Monte Carlo process used generates a distribution of aggregate pseudorandom linear price returns summed over a user defined period, then plots standard deviations of the outcomes from the mean outcome generate forecast regions. The pseudorandom process used in this script relies on a modified Wichmann-Hill pseudorandom number generator (PRNG) algorithm. Wichmann-Hill is a hybrid generator that uses three linear congruential generators (LCGs) with different prime moduli. Each LCG within the generator produces an independent, uniformly distributed number between 0 and 1. The three generated values are then summed and modulo 1 is taken to deliver the final uniformly distributed output. Because of its long cycle length, Wichmann-Hill is a fantastic generator to use on TV since it's extremely unlikely that you'll ever see a cycle repeat. The resulting pseudorandom output from this generator has a minimum repetition cycle length of 6,953,607,871,644. Fun fact: Wichmann-Hill is a widely used PRNG in various software applications. For example, Excel 2003 and later uses this algorithm in its RAND function, and it was the default generator in Python up to v2.2. The generation algorithm in this script takes the Wichmann-Hill algorithm, and uses a multi-stage transformation process to generate the results. First, a parent seed is selected. This can either be a fixed value, or a dynamic value. The dynamic parent value is produced by taking advantage of Pine's timenow variable behavior. It produces a variable parent seed by using a frozen ratio of timenow/time. Because timenow always reflects the current real time when frozen and the time variable reflects the chart's beginning time when frozen, the ratio of these values produces a new number every time the cache updates. After a parent seed is selected, its value is then fed through a uniformly distributed seed array generator, which generates multiple arrays of pseudorandom "children" seeds. The seeds produced in this step are then fed through the main generators to produce arrays of pseudorandom simulated outcomes, and a pseudorandom series to compare with the real series. The main generators within this script are designed to (at least somewhat) model the stochastic nature of financial time series data. The first step in this process is to transform the uniform outputs of the Wichmann-Hill into outputs that are normally distributed. In this script, the transformation is done using an estimate of the normal distribution quantile function. Quantile functions, otherwise known as percent-point or inverse cumulative distribution functions, specify the value of a random variable such that the probability of the variable being within the value's boundary equals the input probability. The quantile equation for a normal probability distribution is μ + σ(√2)erf^-1(2(p - 0.5)) where μ is the mean of the distribution, σ is the standard deviation, erf^-1 is the inverse Gauss error function, and p is the probability. Because erf^-1() does not have a simple, closed form interpretation, it must be approximated. To keep things lightweight in this approximation, I used a truncated Maclaurin Series expansion for this function with precomputed coefficients and rolled out operations to avoid nested looping. This method provides a decent approximation of the error function without completely breaking floating point limits or sucking up runtime memory. Note that there are plenty of more robust techniques to approximate this function, but their memory needs very. I chose this method specifically because of runtime favorability. To generate a pseudorandom approximately normally distributed variable, the uniformly distributed variable from the Wichmann-Hill algorithm is used as the input probability for the quantile estimator. Now from here, we get a pretty decent output that could be used itself in the simulation process. Many Monte Carlo simulations and random price generators utilize a normal variable. However, if you compare the outputs of this normal variable with the actual returns of the real time series, you'll find that the variability in shocks (random changes) doesn't quite behave like it does in real data. This is because most real financial time series data is more complex. Its distribution may be approximately normal at times, but the variability of its distribution changes over time due to various underlying factors. In light of this, I believe that returns behave more like a convoluted product distribution rather than just a raw normal. So the next step to get our procedurally generated returns to more closely emulate the behavior of real returns is to introduce more complexity into our model. Through experimentation, I've found that a return series more closely emulating real returns can be generated in a three step process: -> First, generate multiple independent, normally distributed variables simultaneously. -> Next, apply pseudorandom weighting to each variable ranging from -1 to 1, or some limits within those bounds. This modulates each series to provide more variability in the shocks by producing product distributions. -> Lastly, add the results together to generate the final pseudorandom output with a convoluted distribution. This adds variable amounts of constructive and destructive interference to produce a more "natural" looking output. In this script, I use three independent normally distributed variables multiplied by uniform product distributed variables. The first variable is generated by multiplying a normal variable by one uniformly distributed variable. This produces a bit more tailedness (kurtosis) than a normal distribution, but nothing too extreme. The second variable is generated by multiplying a normal variable by two uniformly distributed variables. This produces moderately greater tails in the distribution. The third variable is generated by multiplying a normal variable by three uniformly distributed variables. This produces a distribution with heavier tails. For additional control of the output distributions, the uniform product distributions are given optional limits. These limits control the boundaries for the absolute value of the uniform product variables, which affects the tails. In other words, they limit the weighting applied to the normally distributed variables in this transformation. All three sets are then multiplied by user defined amplitude factors to adjust presence, then added together to produce our final pseudorandom return series with a convoluted product distribution. Once we have the final, more "natural" looking pseudorandom series, the values are recursively summed over the forecast period to generate a simulated result. This process of generation, weighting, addition, and summation is repeated over the user defined number of simulations with different seeds generated from the parent to produce our array of initial simulated outcomes. After the initial simulation array is generated, the max, min, mean and standard deviation of this array are calculated, and the values are stored in holding arrays on each iteration to be called upon later. Reference difference series and price values are also stored in holding arrays to be used in our comparison plots. In this script, I use a linear model with simple returns rather than compounding log returns to generate the output. The reason for this is that in generating outputs this way, we're able to run our simulations recursively from the beginning of the chart, then apply scaling and anchoring post-process. This allows a greater conservation of runtime memory than the alternative, making it more suitable for doing longer forecasts with heavier amounts of simulations in TV's runtime environment. From our starting time, the previous bar's price, volatility, and optional drift (expected return) are factored into our holding arrays to generate the final forecast parameters. After these parameters are computed, the range forecast is produced. The basis value for the ranges is the mean outcome of the simulations that were run. Then, quarter standard deviations of the simulated outcomes are added to and subtracted from the basis up to 3σ to generate the forecast ranges. All of these values are plotted and colorized based on their theoretical probability density. The most likely areas are the warmest colors, and least likely areas are the coolest colors. An information panel is also displayed at the starting time which shows the starting time and price, forecast type, parent seed value, simulations run, forecast bars, total drift, mean, standard deviation, max outcome, min outcome, and bars remaining. The interesting thing about simulated outcomes is that although the probability distribution of each simulation is not normal, the distribution of different outcomes converges to a normal one with enough steps. In light of this, the probability density of outcomes is highest near the initial value + total drift, and decreases the further away from this point you go. This makes logical sense since the central path is the easiest one to travel. Given the ever changing state of markets, I find this tool to be best suited for shorter term forecasts. However, if the movements of price are expected to remain relatively stable, longer term forecasts may be equally as valid. There are many possible ways for users to apply this tool to their analysis setups. For example, the forecast ranges may be used as a guide to help users set risk targets. Or, the generated levels could be used in conjunction with other indicators for meaningful confluence signals. More advanced users could even extrapolate the functions used within this script for various purposes, such as generating pseudorandom data to test systems on, perform integration and approximations, etc. These are just a few examples of potential uses of this script. How you choose to use it to benefit your trading, analysis, and coding is entirely up to you. If nothing else, I think this is a pretty neat script simply for the novelty of it. ---------- How To Use: When you first add the script to your chart, you will be prompted to confirm the starting date and time, number of bars to forecast, number of simulations to run, and whether to include drift assumption. You will also be prompted to confirm the forecast type. There are two types to choose from: -> End Result - This uses the values from the end of the simulation throughout the forecast interval. -> Developing - This uses the values that develop from bar to bar, providing a real-time outlook. You can always update these settings after confirmation as well. Once these inputs are confirmed, the script will boot up and automatically generate the forecast in a separate pane. Note that if there is no bar of data at the time you wish to start the forecast, the script will automatically detect use the next available bar after the specified start time. From here, you can now control the rest of the settings. The "Seeding Settings" section controls the initial seed value used to generate the children that produce the simulations. In this section, you can control whether the seed is a fixed value, or a dynamic one. Since selecting the dynamic parent option will change the seed value every time you change the settings or refresh your chart, there is a "Regenerate" input built into the script. This input is a dummy input that isn't connected to any of the calculations. The purpose of this input is to force an update of the dynamic parent without affecting the generator or forecast settings. Note that because we're running a limited number of simulations, different parent seeds will typically yield slightly different forecast ranges. When using a small number of simulations, you will likely see a higher amount of variance between differently seeded results because smaller numbers of sampled simulations yield a heavier bias. The more simulations you run, the smaller this variance will become since the outcomes become more convergent toward the same distribution, so the differences between differently seeded forecasts will become more marginal. When using a dynamic parent, pay attention to the dispersion of ranges. When you find a set of ranges that is dispersed how you like with your configuration, set your fixed parent value to the parent seed that shows in the info panel. This will allow you to replicate that dispersion behavior again in the future. An important thing to note when settings alerts on the plotted levels, or using them as components for signals in other scripts, is to decide on a fixed value for your parent seed to avoid minor repainting due to seed changes. When the parent seed is fixed, no repainting occurs. The "Amplitude Settings" section controls the amplitude coefficients for the three differently tailed generators. These amplitude factors will change the difference series output for each simulation by controlling how aggressively each series moves. When "Adjust Amplitude Coefficients" is disabled, all three coefficients are set to 1. Note that if you expect volatility to significantly diverge from its historical values over the forecast interval, try experimenting with these factors to match your anticipation. The "Weighting Settings" section controls the weighting boundaries for the three generators. These weighting limits affect how tailed the distributions in each generator are, which in turn affects the final series outputs. The maximum absolute value range for the weights is . When "Limit Generator Weights" is disabled, this is the range that is automatically used. The last set of inputs is the "Display Settings", where you can control the visual outputs. From here, you can select to display either "Forecast" or "Difference Comparison" via the "Output Display Type" dropdown tab. "Forecast" is the type displayed by default. This plots the end result or developing forecast ranges. There is an option with this display type to show the developing extremes of the simulations. This option is enabled by default. There's also an option with this display type to show one of the simulated price series from the set alongside actual prices. This allows you to visually compare simulated prices alongside the real prices. "Difference Comparison" allows you to visually compare a synthetic difference series from the set alongside the actual difference series. This display method is primarily useful for visually tuning the amplitude and weighting settings of the generators. There are also info panel settings on the bottom, which allow you to control size, colors, and date format for the panel. It's all pretty simple to use once you get the hang of it. So play around with the settings and see what kinds of forecasts you can generate! ---------- ADDITIONAL NOTES & DISCLAIMERS Although I've done a number of things within this script to keep runtime demands as low as possible, the fact remains that this script is fairly computationally heavy. Because of this, you may get random timeouts when using this script. This could be due to either random drops in available runtime on the server, using too many simulations, or running the simulations over too many bars. If it's just a random drop in runtime on the server, hide and unhide the script, re-add it to the chart, or simply refresh the page. If the timeout persists after trying this, then you'll need to adjust your settings to a less demanding configuration. Please note that no specific claims are being made in regards to this script's predictive accuracy. It must be understood that this model is based on randomized price generation with assumed constant drift and dispersion from historical data before the starting point. Models like these not consider the real world factors that may influence price movement (economic changes, seasonality, macro-trends, instrument hype, etc.), nor the changes in sample distribution that may occur. In light of this, it's perfectly possible for price data to exceed even the most extreme simulated outcomes. The future is uncertain, and becomes increasingly uncertain with each passing point in time. Predictive models of any type can vary significantly in performance at any point in time, and nobody can guarantee any specific type of future performance. When using forecasts in making decisions, DO NOT treat them as any form of guarantee that values will fall within the predicted range. When basing your trading decisions on any trading methodology or utility, predictive or not, you do so at your own risk. No guarantee is being issued regarding the accuracy of this forecast model. Forecasting is very far from an exact science, and the results from any forecast are designed to be interpreted as potential outcomes rather than anything concrete. With that being said, when applied prudently and treated as "general case scenarios", forecast models like these may very well be potentially beneficial tools to have in the arsenal.
Pine Script® Indikator
von DonovanWall
74