התחל

חפש סקריפטים עבור "4月10日A股市场分析"

Volume Profile with a few polylinesThe base of "Volume Profile with a few polylines" is another script of mine, Volume Profile (Maps) . The structure of maps is used to gather the data. However, the drawings is done with polylines. This enables coders to draw an entire volume profile with just a few polylines, while the range is broader. This results in the benefit to draw more "lines" than with line.new() / box.new() alone. 🔶 CONCEPTS 🔹 Polylines polyline.new creates a new polyline instance and displays it on the chart, sequentially connecting all of the points in the `points` array with line segments. The segments in the drawing can be straight or curved depending on the `curved` parameter. In this script, points are connected, starting from the bottom. The created line moves up until there is a price level where a volume value needs to be displayed, at which the line goes to the left to the concerning volume value, coming back at the same price level until the line returns to its initial x-axis, after which the line will continue to rise until all values are displayed. A polyline can contain maximum 10000 points (10K). Since the line has to go back and forth, each price/volume line takes 3 points. In the case that 20K bars all have a different price, we would need 60K points, or just 6 polylines. A maximum of 100 polylines can be displayed. The 3 highest volume values are displayed with line.new(), each with their own colour. 🔹 Maps A map object is a collection that consists of key - value pairs Each key is unique and can only appear once. When adding a new value with a key that the map already contains, that value replaces the old value associated with the key . You can change the value of a particular key though, for example adding volume (value) at the same price (key), the latter technique is used in this script. Volume is added to the map, associated with a particular price (default close, can be set at high, low, open,...) When the map already contains the same price (key), the value (volume) is added to the existing volume at the associated price. A map can contain maximum 50K values, which is more than enough to hold 20K bars (Basic 5K - Premium plan 20K), so the whole history can be put into a map. 🔹 Rounding function This publication contains 2 round functions, which can be used to widen the Volume Profile Round • "Round" set     at    zero -> nothing changes to the source number • "Round" set below zero -> x digit(s)   after the decimal point, starting from the right side, and rounded. • "Round" set above zero -> x digit(s) before the decimal point, starting from the right side, and rounded. Example: 123456.789   0->123456.789   1->123456.79   2->123456.8   3->123457 -1->123460 -2->123500 Step Another option is custom steps. After setting "Round" to "Step", choose the desired steps in price, Examples •     2  -> 1234.00, 1236.00, 1238.00, 1240.00 •     5  -> 1230.00, 1235.00, 1240.00, 1245.00 • 100  -> 1200.00, 1300.00, 1400.00, 1500.00 • 0.05 -> 1234.00, 1234.05, 1234.10, 1234.15 ••• 🔶 FEATURES 🔹 Volume * currency Let's take as example BTCUSD, relative to USD, 10 volume at a price of 100 BTCUSD will be very different than 10 volume at a price of 30000 (1K vs. 300K) If you want volume to be associated with USD, enable Volume * currency . Volume will then be multiplied by the price: • 10 volume, 1 BTC = 100 -> 1000 • 10 volume, 1 BTC = 30K -> 300K Polylines has the attributes curved & closed. When "curved" is enabled the drawing will connect all points from the `points` array using curved line segments. When "closed" is enabled the drawing will also connect the first point to the last point from the `points` array, resulting in a closed polyline. They are default disabled, but can be enabled: 🔶 DETAILS 🔹 Put When the map doesn't contain a price, it will be added, using map.put(id, key, value) In our code: map.put(originalMap, price, volume) or originalMap.put(price, volume) A key (price) is now associated with a value (volume) -> key : value Since all keys are unique, we don't have to know its position to extract the value, we just need to know the key -> map.get(id, key) We use map.get() when a certain key already exists in the map, and we want to add volume with that value. if originalMap.contains(price) originalMap.put(price, originalMap.get(price) + volume) -> At the last bar, all prices (source) are now associated with volume. 🔶 SETTINGS Source : Set source of choice; default close , can be set as high , low , open , ... Volume & currency : Enable to multiply volume with price (see Features ) Amount of bars : Set amount of bars which you want to include in the Volume Profile 🔹 Round -> ' Round/Step ' Round -> see Concepts Step    -> see Concepts 🔹 Display Volume Profile Offset: shifts the Volume Profile (max. 500 bars to the right of last bar, see Features ) Max width Volume Profile: largest volume will be x bars wide, the rest is displayed as a ratio against largest volume (see Features ) Colours Curved: make lines curved Closed: connect last with first point 🔶 LIMITATIONS • Lines won't go further than first bar (coded). • The Volume Profile can be placed maximum 500 bar to the right of last price.
אינדיקטור Pine Script®
מאת ‎fikira‎
18
Machine Learning: MFI Heat Map [YinYangAlgorithms]Overview: MFI Heat Maps are a visually appealing way to display the values of 29 different MFIs at the same time while being able to make sense of it. Each plot within the Indicator represents a different MFI value. The higher you get up, the longer the length that was used for this MFI. This Indicator also features the use of Machine Learning to help balance the MFI levels. It doesn’t solely rely upon Machine Learning but instead incorporates a growing length MFI averaged with the Machine Learning MFI at any given index. For instance, say we are calculating the 10th plot from the bottom, the MFI would be an average of: MFI(source, 11) Machine Learning MFI at Index of 10 We do it this way as they both help smooth each other out without relying solely on just one calculation method. Due to plot limitations, you are capped at 28 Plot Amounts within this indicator, but that is still quite a bit of information you can glean from a Heat Map. The Machine Learning used in this indicator is of the K-Nearest Neighbor (KNN). It uses a Fast and Slow MFI calculation then sorts through them over Machine Learning Length and calculates the differences between them. It then slices off KNN length to create our Max/Min Distances allotted. It adds the average between Fast and Slow MFIs to a Viable Distances array if their distances are within the KNN Min/Max distance. It then averages all distances in the Viable Distances array and returns the result. The result of the KNN Function is saved to another ML Data array whose length is that of Plot Amount (Heat Map Size). This way each Index of the ML Data array can be indexed according to the Heat Map Size. The Average of the ML Data array is the MFI line (white) that you’ll see plotted on the Indicator. There is also the SMA of the MFI Average (orange) which is likewise plotted. These plots allow you to visualize where the ML MFI is sitting and can potentially be useful for seeing when the MFI Average and SMA cross over and under each other. We’ve heard many people talk highly of RSI, but sadly not too many even refer to MFI. MFI oftentimes may be overlooked, especially with new traders who may not even know what it is. Essentially MFI is an RSI but it also incorporates Volume into its calculations, which in our opinion leads to a more accurate reading; afterall, what is price movement without Volume. Tutorial: You may be thinking, this Indicator looks appealing to the eye, but how do I benefit from it trading wise? Before we get into our visual examples, let's talk briefly about what makes Heat Maps in general a useful tool for trading. Heat Maps give us the ability to visualize and understand lots of data while removing the clutter. We can understand the data of 29 different MFIs without having to look at and decipher 29 different MFI plots. When you overlay too many MFI lines on top of each other, they can be very difficult to read and oftentimes end up actually hindering your Technical Analysis. For this reason, we have a simple solution to this problem; Heat Maps. This MFI Heat Map allows you to easily know (in a relative %) what the MFI level is for varying lengths. For Instance, the First (bottom) plot indexes an MFI of (K(0) (loop of Plot Amount) + Smoothing Length (default 1)) = 1. Since this is indexing (usually) a very low length, it will change much quicker. Whereas the Last (top) plot indexes an MFI of (K(27) (loop of Plot Amount) + Smoothing Length (default 1)) = 28. This is indexing a much higher length of MFI which results in the MFI the higher you go up in the Heat Map to move much slower. Heat Maps give us the ability to see changes happening over multiple MFIs at the same time, which can be very useful for seeing shifts in MFI / Momentum. Remember, MFI incorporates Volume, so even if the price goes up a lot, if there was low volume, the MFI won’t move as much as an RSI would. However, likewise, if there is high volume but low price movement, the MFI will move slightly more than the RSI. Heat Maps change color based on their MFI level. If the MFI is >= 90 it is HOT (red), if the MFI <= 9 it is COLD (teal, think of ICE). Green represents an MFI of 50-59 and Dark Blue represents an MFI of 40-49. Green and Dark blue are the most common colors as all the others are more ‘Extreme’ MFI levels. Okay, time to get to the Examples : Since there is so much going on in Heat Maps, we’ve decided to focus this tutorial to this specific area and talk about individual locations before talking about it as a whole. If you refer to the example above where there are 2 white circles; these white circles are highlighting a key location you’ll be wanting to identify within your Heat Maps, many things are happening here: The MFI crossed over the SMA (bullish). The Heat Map started changing from mid/dark Blue (30-50 MFI) to Green (50-59 MFI) around the midline (the 50% dashed like). The Lower levels of the Heat Map are turning Yellow/Orange/Red (60-100 MFI). The Upper Levels of the Heat Map are still Light Blue - Green (10-50 MFI). The 4 Key points above, all point towards potential Bullish Momentum changes. You’re likely wondering, but why? Let's discuss about each one in more specific detail: 1. The MFI crossed over the SMA (bullish): What this tells us is that the current MFI Average is now greater than its average over the last (default) 16 bars. This means there's been a large amount of Money Flow (Price and Volume) recently (subjectively based on the last (default) 16 average). This is one of the leading Bullish / Bearish signals you will see within this Indicator. You can enable Signals within the Settings and/or even add Alerts for when these crossings occur. 2. The Heat Map started changing from mid/dark Blue (30-50 MFI) to Green (50-59 MFI) around the midline (the 50% dashed like): This shows us that the index’s in the mid (if using all 28 heat map plots it would be at 14) has already received some of this momentum change. If you look at the second white circle (right), you’ll also notice the higher MFI plot indexes are also green. This is because since their length is long they still have some momentum and strength from the first white circle (left). Just because the first white circle failed in its bullish push, doesn’t mean it didn’t achieve momentum that would later on help to push the price up. 3. The Lower levels of the Heat Map are turning Yellow/Orange/Red (60-100 MFI): It occurred somewhat in the left white circle, but mainly in the right white circle. This shows us the MFI is very high on the lower lengths, this may lead to the current, middle and higher length MFIs following suit soon. Remember it has to work its way up, the higher levels can’t go red unless the lower levels go red first and the higher levels can also lag quite a bit behind and take awhile to catch up, this is normal, expected and meant to happen. Vice versa is also true with getting higher levels to go cold (light teal (think of ICE)). 4. The Upper Levels of the Heat Map are still Light Blue - Green (10-50 MFI): You might think at first that this is a bad thing, but it's not! Remember you want to be Fearful when others are Greedy and Greedy when others are Fearful! You don’t want to buy when the higher levels have a high MFI, you want to buy when you see the momentum pushing up in the lower MFI levels (getting yellow/orange/red in the low levels) while it is still Cold in the higher levels (BLUE OR GREEN, nothing higher than green as it is already slightly too high). There will be many times that it is Yellow or possibly Orange in the high levels and the bullish push still happens, but this is much more risky! The key to trading is to minimize risks while maximizing potential. Hopefully now you’re getting an idea of how to spot potential bullish momentum changes, but what about bearish momentum changes? Technically they are the exact opposite, so we don’t need to go into as much detail, but lets still take a look at a few examples: In the example above we marked the 3 times where it was displaying overly bullish characteristics. We marked the bullish momentum occurring with arrows. If you look closely at the start of the arrow to where it finishes, you’ll notice how the heat (HOT)(RED) works its way up from the lower levels to the higher levels. We then see the MFI to SMA cross under. In all 3 of these examples the heat made it all the way to the top of the chart. These are all very bearish signals that represent a bearish momentum movement that may occur soon. Also, please note, the level the MFI is at DOES matter! That line isn’t there simply for you to see when there are crosses over and under. The MFI is considered to be Overbought when it is greater than 70 (the upper white dashed line, it is just formatted to be on a different scale cause there are 28 plots, but it represents 70). The MFI is considered to be Oversold when it is less than 30 (the lower white dashed line). If we look to the left a little here where a big drop in price occurred shortly after our MFI and SMA crossed, would we have been able to identify it using the Heat Maps? Likely, No. There was some color change in the lower levels a few bars prior that went yellow/orange/red but before this cross happened they all went back to Dark Blue. In the middle section when the cross happened it was only Green and Yellow and in the upper section we are Blue. This would be a very risky trade to go on as the only real Bearish Indication was the MFI to SMA cross under. Remember, you want to reduce risk, you don’t want to simply trade on everytime the MFI and SMA cross each other or you’ll be getting yourself into many risky trades based on false signals. Based on what you’ve learned above, can you see the signs that are indicating where this white circle may have potential for a bullish momentum change? Now that we are more zoomed in, you may also be noticing there are colors to the price bars. This can be disabled in the settings, but just so you know what they mean, let’s zoom in a little more and talk about it. We’ve condensed the Indicator a bit so you can see the bars better here. The colors that are displayed on these bars are the Heat Map value for your MFI (the white line in the Indicator). This way you can better see when the Price is Hot and Cold. As you may see while looking, the colors generally go from cold to hot when bullish momentum is happening and hot to cold when bearish momentum is happening. We don’t recommend solely looking at the bars as indicators to MFI momentum change, as seeing the Heat Map will give you much more data; however it can be nice to see the Heat Map projected on the bars rather than trying to eyeball it yourself or hover over each bar specifically to see their levels. We will conclude our Tutorial here. Hopefully this has given you some insight to how useful Heat Maps can be and why it works well with a Machine Learning (KNN) Model applied to the MFI. PLEASE NOTE: You can adjust the line width for the Heat Map within the settings. If you condense the Indicator a lot or have a small screen, likely use a length of 1-2. If you have it stretched out or a large screen, a length of 2-3 will work nice. You just don’t want to have the lines overlapping or it defeats the purpose of a Heat Map. Also, the bigger the linewidth, generally you’ll want to increase the Transparency within the Settings also as it can get quite bright and hurt your eyes over time. Settings: MFI: Show MFI and SMA Crossing Signals: MFI and SMA Crossing is one of the leading Bullish and Bearish Signals in this Indicator. You can also add alerts for these signals. Plot Amount: How many plots are used in this Heat Map. (2 - 28). Source: The Source to use in all MFI calculations. Smooth Initial MFI Length: How much to smooth the Fast and Slow MFI calculation by. 1 = No smoothing. MFI SMA Length: What length we smooth the MFI Average over to get our MFI SMA. Machine Learning: Average MFI data by adding a lookback to the Source: While populating our Heat Map with the MFI's, should use use the Source each MFI Length increase or should we also lookback a Source each MFI Length Increase. KNN Distance Requirement: To be a valid KNN, it needs to abide by a Distance calculation. Generally only Max is used, but you can change it if it suits your trading style better. Machine Learning Length: How much ML data should we store? The longer the length generally the smoother the result; which may not be as accurate for something like a Heat Map, so keeping this relatively low may lead to more accurate results. KNN Length: How many KNN are used in the slice to calculate max/min distance allowed. Fast Length: Fast MFI length used in KNN to calculate distances by comparing its distance with the Slow MFI Length. Slow Length: Slow MFI length used in KNN to calculate distances by comparing its distance with the Fast MFI Length. Smoothing Length: When populating our Heat Map, at what length do we start our MFI calculations with (A Higher value with result in a slower and more smoothed MFI / Heat Map). Colors: Change Bar Color: Change bar colors to MFI Avg Color. Heat Map Transparency: If there isn't any transparency it can be a little hard on the eyes. The Greater the Line Width, generally the more transparency you'll want for your eyes. Line Width: Set how wide the Heat Map lines are MFI 90-100 Color: Color when the MFI is between these levels. MFI 80-89 Color: Color when the MFI is between these levels. MFI 70-79 Color: Color when the MFI is between these levels. MFI 60-69 Color: Color when the MFI is between these levels. MFI 50-59 Color: Color when the MFI is between these levels. MFI 40-49 Color: Color when the MFI is between these levels. MFI 30-39 Color: Color when the MFI is between these levels. MFI 20-29 Color: Color when the MFI is between these levels. MFI 10-19 Color: Color when the MFI is between these levels. MFI 0-100 Color: Color when the MFI is between these levels. If you have any questions, comments, ideas or concerns please don't hesitate to contact us. HAPPY TRADING!
אינדיקטור Pine Script®
מאת ‎YinYangAlgorithms‎
5
Machine Learning: Support and Resistance [YinYangAlgorithms]Overview: Support and Resistance is normally based upon Pivot Points and Highest Highs and Lowest Lows. Many times coders even incorporate Volume, RSI and other factors into the equation. However there may be a downside to doing a pure technical approach based on historical levels. We live in a time where Machine Learning is becoming more and more used; thus we have decided to create a Machine Learning Support and Resistance Projection based Indicator. Rather than using traditional Support and Resistance calculations using historical data, we have taken a rather different approach. This Indicator instead attempts to Predict and Project where Support and Resistance locations will be based on a Machine Learning Model using a form of KNN (k-Nearest Neighbors). Since this indicator creates a Projection of where it deems Support and Resistance will be, it has the ability to move its Support and Resistance before the price even gets to it if it believes it will surpass its projections. This may create a more accurate placement of Support and Resistance as they’re not based on historical levels. This Indicator does not Repaint. How it works: This Indicator makes its projections based on the source you provide (by default close) of the previous bar and submits the source, RSI and EMA to our Projection Function to get its projection of the current bar. The Projection function essentially calculates potential movement after finding the differences between the source the MA from the current bar, previous bar and average over the span of Machine Learning Length. Potential movement is defined as: Average Difference + Average(Machine Learning Average, Average Last Distance) Average Difference: (Absolute value of Current Source - Current MA) - (Absolute value of Machine Learning Average - Machine Learning MA) Average Last Distance: Average(Current Source - Current MA, Previous Source - Previous MA) It then predicts the next bars directional movement (bullish or bearish bar) using several factors: Previous Source > Previous MA Current Source - Current MA > Average Source - Average MA Current RSI > Previous RSI Current RSI > 30 and Previous RSI <= 30 Current RSI < 70 and Previous RSI >= 70 This helps us to predict the direction the next bar may move. We then calculate a multiplier that we apply to our Potential Movement value to get our final result which is our Current Bars Close Projection. Our multiplier is calculated using: (Current RSI > 30 and Previous RSI <= 30) OR (Current RSI < 70 and Previous RSI >= 70) Current Source - Current MA > Previous Source - Previous MA We then create an array and fill it with the previous X projections (Machine Learning Length) and send it to another function. This function, if told to, will sort the data accordingly and then output the KNN average of the length given. We calculate and plot various KNN lengths to create different Zones: Strong Support: Length of 2 but sort the data Ascending (low to high) Strong Resistance: Length of 2 but sort the data Descending (high to low) Support: Length of Machine Length Length / 10 or Min of 2 sorted by Ascending Resistance: Length of Machine Length Length / 10 or Min of 2 sorted by Descending There are also 4 other plots you may be wondering what they are, there is your AVG, VWMA, Long Term Memory and Current Projection. By default your Current Projection is disabled in settings but you can enable it if you are curious to see how the projections for each close are calculated. It is, however, not a crucial point of interest (white line). The average is simply the average value of the Machine Learning Data (purple line). The VWMA is a VWMA calculation applied to our Data over a length specified in settings (by default 1)(blue line). The VWMA is crucial when combined with the Avg as they can cross over and under each other. These crosses represent potential Bullish and Bearish zones. Lastly, but certainly not least, we have the Long Term Memory (maroon line). The Long Term Memory can be displayed either as an ‘Average’, ‘Hard Line’ or ‘None’. The Long Term Average is only updated every Machine Learning Length Bar Index’s and is populated with the average of the Machine Learning Data. For Instance, if Machine Learning Length is set to 100, the Long Term Memory is only updated every 100 bars, and since its length is the same as the Machine Learning Length, that means its data is composed of 10,000 bars worth of data. The Long Term Memory may be very beneficial for determining where Support and Resistance lie over the Long Term within a Machine Learning Algorithm. When set to ‘Average’ it plots the connection lines diagonally, and although they may be more visually appealing, they’re less useful when it comes to actually seeing support and resistance as generally speaking, support and resistance lie on the horizontal. When set to ‘Hard Line’ the Long Term Memory is connected with hard lines and holds the price value until the next time it is updated. This makes it much more useful for potentially identifying Support and Resistance. Tutorial: Here is an overview of what the Indicator looks like, now let's start to dissect it. In the example above we can see how all of the lines between the Major Support and Resistance zones may act as BOTH Support and Resistance depending on which side the price is currently on. In the circle on the left, we can see how it can fluctuate between the two. If you look at the circle on the right, we can see how the Average line acts as a strong support before it fails to maintain it. Generally speaking, most Support and Resistance locations may potentially fail to hold after 3 tests, as the Average did in this example. As you can see, the Support and Resistance doesn’t wait to be tested before adjusting, which is why there are 2 lines which create their zones. The inner line is the Support/Resistance and the outer line is the Strong Support/Resistance. The Yellow Circle shows the inner line was able to calculate the moving resistance correctly and then adjusted accordingly as it was projecting the price to keep increasing. However, if you look at the White Circle, you can see that since there was first a crash, and then parabolic movement, that the inner zone could not move and predict the resistance as well as the outer zone could. We consider the price to be ‘Overvalued’ when it is above the VWMA (blue line) and ‘Undervalued’ when it is below the VWMA. It is considered ‘fair’ price when it is within the VWMA to Average zone (between the blue and purple lines). If you look at the example above, you’ll notice where the two yellow circles are, it is not only considered ‘Overvalued’, but it then proceeds to ride the inner resistance line upwards. This is common when the market is overly bullish and vice versa when it is bearish. Please keep in mind, although it is common, it doesn’t mean a correction can’t happen. In this example above we look at the last bull run that may have started due to the halving. This bull run was very bullish as you can see in the example above. The price was constantly sitting within the Resistance Zone and the VWMA that was very close to it was constantly acting as a Support. Naturally, due to the Algorithm used in this Indicator, as the momentum starts to slow down, the VWMA (blue line) will start to space out more and more from the Resistance Zone. This doesn’t mean the momentum is gone, it just means it may be slowing down. Unfortunately we have to study the Bear Market with a different perspective than the Bull Market. However, there are still some similarities within the two. If you refer to the example above and the previous example, you can clearly see that the Bull Market loves to stay with the Resistance Zone and use the VWMA as a Support. However, the Bear Market does not. This is a normal occurrence, however we can see from the example above you may see a correction / horizontal movement when the Outer Support Line is touched. If you look at all 3 yellow circles, the Outer Support Line was touched, then either a small correction or horizontal consolidation occurred. We will conclude our Tutorial here, hopefully you’ll be able to benefit from a moving Support and Resistance calculated with Machine Learning that projects its locations, rather than using traditional calculations. Settings: Source: This source is the base for all our calculations Machine Learning Length: How much projection data are we storing and using to make calculations. Smoothing Length: We need to smooth calculations such as RSI, EMA and VWMA. What length are we smoothing it with? VWMA ML Projection Length: How far into our Machine Learning data should we average for our VWMA. Please note the 'Smoothing Length' is still applied here after getting the Projection Average. Long Term Memory: Long term memory has the same storage length but is only updated once per Machine Learning Length. For instance, if Machine Learning Length is 100, it will save the Average of our data once every 100 bars. This means its memory is an average of 10,000 bars of Machine Learning. 'Average' connects its values diagonally whereas 'Hard Line' holds its value until it changes. Use Average Last Distance In Potential Movement: This can help accuracy but generally also displaces the Support and Resistance by projecting it further. Show Current Projection: Projections occur for each bar, and our Machine Learning utilizes these projections by storing and evaluating them. This toggle will display the Current Projection Line which is used to create all our Projections. If you have any questions, comments, ideas or concerns please don't hesitate to contact us. HAPPY TRADING!
אינדיקטור Pine Script®
מאת ‎YinYangAlgorithms‎
8
MA Support & Resistance SignalThis indicator is to show MA Support/Resistance and trend of a stock. It contains three (3) Moving Averages that can be set to SMA or EMA: 1. Upper Line : SMA 5 (default) 2. Lower Line : SMA 20 (default) 3. Support/Resistance Line : SMA 10 (default) Other signals: 1. Bull and Blue Dotted Line signal: Upper Line (SMA 5) crossover with Lower Line (SMA 20). 2. Bear and Red Dotted Line signal: Lower Line (SMA 20) crossover with Upper Line (SMA 5). 3. Red Triangle signal: Price closes below Support/Resistance Line (SMA 10). 4. Green Bar signal: Price breaks Support/Resistance Line (SMA 10). The way how I use it: - Since I don't like my chart to be crowded with a lot of moving averages, I will disable SMA 5 and SMA 10 and will only leave SMA 20 as my final support line. - Entry when only: 1. Bull signal appeared. 2. Green bar appeared, or; 3. Price rebound on SMA 20. I let the script open so that you guys can custom it based on your own preferences. Hope you guys enjoy it.
אינדיקטור Pine Script®
מאת ‎taufan_ganas‎
Volume Profile (Maps) [LuxAlgo]The Pine Script® developers have unleashed "maps"! Volume Profile (Maps) displays volume, associated with price, above and below the latest price, by using maps The largest and second-largest volume is highlighted. 🔶 USAGE The proposed script can highlight more frequent closing prices/prices with the highest volume, potentially highlighting more liquid areas. The prices with the highest associated volume (in red and orange in the indicator) can eventually be used as support/resistance levels. Voids within the volume profile can highlight large price displacements (volatile variations). 🔶 CONCEPTS 🔹 Maps A map object is a collection that consists of key - value pairs Each key is unique and can only appear once. When adding a new value with a key that the map already contains, that value replaces the old value associated with the key . You can change the value of a particular key though, for example adding volume (value) at the same price (key), the latter technique is used in this script. Volume is added to the map, associated with a particular price (default close, can be set at high, low, open,...) When the map already contains the same price (key), the value (volume) is added to the existing volume at the associated price. A map can contain maximum 50K values, which is more than enough to hold 20K bars (Basic 5K - Premium plan 20K), so the whole history can be put into a map. 🔹 Visible line/box limit We can only display maximum 500 line.new() though. The code locates the current (last) close, and displays volume values around this price, using lines, for example 250 lines above and 250 lines below current price. If one side contains fewer values, the other side can show more lines, taking the maximum out of the 500 visible line limitation. Example (max. 500 lines visible) • 100 values below close • 2000 values above close -> 100 values will be displayed below close -> 400 remaining -> 400 values will be displayed above close Pushing the limits even further, when ' Amount of bars ' is set higher than 500, boxes - box.new() - will be used as well. These have a limit of 500 as well, bringing the total limit to 1000. Note that there are visual differences when boxes overlap against lines. If this is confusing, please keep ' Amount of bars ' at max. 500 (then only lines will be used). 🔹 Rounding function This publication contains 2 round functions, which can be used to widen the Volume Profile Round • "Round" set     at    zero -> nothing changes to the source number • "Round" set below zero -> x digit(s)   after the decimal point, starting from the right side, and rounded. • "Round" set above zero -> x digit(s) before the decimal point, starting from the right side, and rounded. Example: 123456.789   0->123456.789   1->123456.79   2->123456.8   3->123457 -1->123460 -2->123500 Step Another option is custom steps. After setting "Round" to "Step", choose the desired steps in price, Examples •     2  -> 1234.00, 1236.00, 1238.00, 1240.00 •     5  -> 1230.00, 1235.00, 1240.00, 1245.00 • 100  -> 1200.00, 1300.00, 1400.00, 1500.00 • 0.05 -> 1234.00, 1234.05, 1234.10, 1234.15 ••• 🔶 FEATURES 🔹 Adjust position & width 🔹 Table The table shows the details: • Size originalMap : amount of elements in original map • # higher: amount of elements, higher than last "close" (source) • index "close" : index of last "close" (source), or # element, lower than source • Size newMap : amount of elements in new map (used for display lines) • # higher : amount of elements in newMap, higher than last "close" (source) • # lower : amount of elements in newMap, lower than last "close" (source) 🔹 Volume * currency Let's take as example BTCUSD, relative to USD, 10 volume at a price of 100 BTCUSD will be very different than 10 volume at a price of 30000 (1K vs. 300K) If you want volume to be associated with USD, enable Volume * currency . Volume will then be multiplied by the price: • 10 volume, 1 BTC = 100 -> 1000 • 10 volume, 1 BTC = 30K -> 300K Disabled Enabled 🔶 DETAILS 🔹 Put When the map doesn't contain a price, it will be added, using map.put(id, key, value) In our code: map.put(originalMap, price, volume) or originalMap.put(price, volume) A key (price) is now associated with a value (volume) -> key : value Since all keys are unique, we don't have to know its position to extract the value, we just need to know the key -> map.get(id, key) We use map.get() when a certain key already exists in the map, and we want to add volume with that value. if originalMap.contains(price) originalMap.put(price, originalMap.get(price) + volume) -> At the last bar, all prices (source) are now associated with volume. 🔹 Copy & sort Next, every key of the map is copied and sorted (array of keys), after which the index (idx) is retrieved of last (current) price. copyK = originalMap.keys().copy() copyK.sort() idx = copyK.binary_search_leftmost(src) Then left and right side of idx is investigated to show a maximum amount of lines at both sides of last price. 🔹 New map & display The keys (from sorted array of copied keys) that will be displayed are put in a new map, with the associated volume values from the original map. newMap = map.new() 🔹 Re-cap • put in original amp (price key, volume value) • copy & sort • find index of last price • fetch relevant keys left/right from that index • put keys in new map and fetch volume associated with these keys (from original map) Simple example (only show 5 lines) bar 0, price = 2, volume = 23 bar 1, price = 4, volume = 3 bar 2, price = 8, volume = 21 bar 3, price = 6, volume = 7 bar 4, price = 9, volume = 13 bar 5, price = 5, volume = 85 bar 6, price = 3, volume = 13 bar 7, price = 1, volume = 4 bar 8, price = 7, volume = 9 Original map:           Copied keys array:     Sorted:                 -> 5 keys around last price (7) are fetched (5, 6, 7, 8, 9) -> keys are placed into new map + volume values from original map                         Lastly, these values are displayed. 🔶 SETTINGS Source : Set source of choice; default close , can be set as high , low , open , ... Volume & currency : Enable to multiply volume with price (see Features ) Amount of bars : Set amount of bars which you want to include in the Volume Profile Max lines : maximum 1000 (if you want to use only lines, and no boxes -> max. 500, see Concepts ) 🔹 Round -> ' Round/Step ' Round -> see Concepts Step    -> see Concepts 🔹 Display Volume Profile Offset: shifts the Volume Profile (max. 500 bars to the right of last bar, see Features ) Max width Volume Profile: largest volume will be x bars wide, the rest is displayed as a ratio against largest volume (see Features ) Show table : Show details (see Features ) 🔶 LIMITATIONS • Lines won't go further than first bar (coded). • The Volume Profile can be placed maximum 500 bar to the right of last price. • Maximum 500 lines/boxes can be displayed
אינדיקטור Pine Script®
מאת ‎LuxAlgo‎
8
Swing Action PriceEnglish: **Description of "Swing Action Price" TradingView Script** "Swing Action Price" is a custom technical indicator designed to identify swing highs and swing lows in a financial market. The script calculates and plots various lines on the chart to visualize these swing points. Swing highs are points where the price has made a local peak, while swing lows are points where the price has made a local trough. The indicator displays the following lines on the chart: 1. Dotted lines representing each individual swing high and swing low identified on different timeframes (10, 30, 60, 100, 150, 200, 700, and 1000 bars). 2. Dotted lines representing the most recent swing high and swing low for the current bar. How the indicator works: 1. The script uses historical price data to calculate swing highs and swing lows based on specific conditions. 2. For each of the mentioned timeframes, the indicator identifies the highest high and lowest low within a defined number of bars (10, 30, 60, etc.). 3. Once a new swing high or swing low is identified, the corresponding dotted lines are drawn on the chart, extending from the previous swing point to the current one. The "Swing Action Price" indicator can be used by traders to visually identify key support and resistance levels in the market. It helps them recognize potential trend reversals or continuation points, which may be valuable for making trading decisions. Please note that trading indicators should always be used in conjunction with other technical and fundamental analysis tools to make informed trading choices. The "Swing Action Price" indicator is offered under the Mozilla Public License 2.0, and the developer's username is "damianjorgeportillo." Remember that past performance is not indicative of future results, and it's essential to exercise caution and apply risk management strategies when trading financial markets. /******************************/ Spanish: **Descripción del Script "Swing Action Price" en TradingView** "Swing Action Price" es un indicador técnico personalizado diseñado para identificar máximos y mínimos en un mercado financiero. El script calcula y muestra diversas líneas en el gráfico para visualizar estos puntos de inflexión. Los máximos se producen cuando el precio alcanza un pico local, mientras que los mínimos ocurren cuando el precio alcanza un valle local. El indicador muestra las siguientes líneas en el gráfico: 1. Líneas punteadas que representan cada máximo y mínimo individual identificado en diferentes marcos de tiempo (10, 30, 60, 100, 150, 200, 700 y 1000 barras). 2. Líneas punteadas que representan el máximo y mínimo más reciente para la barra actual. Cómo funciona el indicador: 1. El script utiliza datos históricos de precios para calcular los máximos y mínimos en función de ciertas condiciones. 2. Para cada uno de los marcos de tiempo mencionados, el indicador identifica el máximo más alto y el mínimo más bajo dentro de un número específico de barras (10, 30, 60, etc.). 3. Una vez que se identifica un nuevo máximo o mínimo, se dibujan las líneas punteadas correspondientes en el gráfico, extendiéndose desde el punto de inflexión anterior hasta el actual. El indicador "Swing Action Price" puede ser utilizado por traders para identificar visualmente niveles clave de soporte y resistencia en el mercado. Ayuda a reconocer posibles puntos de inversión o continuación de tendencia, lo que puede ser valioso para tomar decisiones comerciales. Por favor, ten en cuenta que los indicadores de trading siempre deben utilizarse junto con otras herramientas de análisis técnico y fundamental para tomar decisiones comerciales informadas. El indicador "Swing Action Price" se ofrece bajo la Licencia Pública de Mozilla 2.0, y el nombre de usuario del desarrollador es "damianjorgeportillo". Recuerda que el rendimiento pasado no garantiza resultados futuros, y es esencial ser cauteloso y aplicar estrategias de gestión de riesgos al operar en los mercados financieros.
אינדיקטור Pine Script®
מאת ‎damianjorgeportillo‎
7
[FC] Multi EMA Cross Alerts Fltered with RSI and StochThis script prints Green Dots and Red Dots on candle close using Faster EMA ( 5 ) and Slower EMA (10 ) filtering with RSI (50)+ Stochastic %K ( 20 to 80 ) Smoothning(3). The idea behind is to you use dots for scalping on smaller timeframe(5) ,(10) etc but you can modify all values to better fit your needs. Explaination for Green Dots and Red Dots: ---> Green dot : 5 Ema crosses above 10 Ema ( i.e faster EMA crosses above slower EMA which signals price is trying to move up RSI value > 50 (filtering for quick move) stoch %k value between 20 and 80 ( filtering to know there is leg left in the move and all movement is already not done) ---> Red dot : 5 Ema crosses below 10 Ema ( i.e faster EMA crosses above slower EMA which signals price is trying to move down RSI value < 50 (filtering for quick move) stoch %k value between 20 and 80 ( filtering to know there is leg left in the move and all movement is already not done)
אינדיקטור Pine Script®
מאת ‎Gabru21‎
LYGLibraryLibrary "LYGLibrary" A collection of custom tools & utility functions commonly used with my scripts getDecimals()   Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price truncate(number, decimalPlaces)   Truncates (cuts) excess decimal places   Parameters:      number (float)      decimalPlaces (simple float)   Returns: The given number truncated to the given decimalPlaces toWhole(number)   Converts pips into whole numbers   Parameters:      number (float)   Returns: The converted number toPips(number)   Converts whole numbers back into pips   Parameters:      number (float)   Returns: The converted number getPctChange(value1, value2, lookback)   Gets the percentage change between 2 float values over a given lookback period   Parameters:      value1 (float)      value2 (float)      lookback (int) av_getPositionSize(balance, risk, stopPoints, conversionRate)   Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      balance (float)      risk (float)      stopPoints (float)      conversionRate (float)   Returns: The calculated position size (in units - only compatible with OANDA) bullFib(priceLow, priceHigh, fibRatio)   Calculates a bullish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio)   Calculates a bearish fibonacci value   Parameters:      priceLow (float) : The lowest price point      priceHigh (float) : The highest price point      fibRatio (float) : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(length, maType)   Gets a Moving Average based on type (MUST BE CALLED ON EVERY CALCULATION)   Parameters:      length (simple int)      maType (string)   Returns: A moving average with the given parameters getEAP(atr)   Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      atr (float)   Returns: The EAP SL converted ATR size getEAP2(atr)   Performs secondary EAP stop loss size calculation (eg. ATR < 40, add 5 pips, ATR between 40-50, add 10 pips etc)   Parameters:      atr (float)   Returns: The EAP SL converted ATR size barsAboveMA(lookback, ma)   Counts how many candles are above the MA   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are above the MA barsBelowMA(lookback, ma)   Counts how many candles are below the MA   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(lookback, ma)   Counts how many times the EMA was crossed recently   Parameters:      lookback (int)      ma (float)   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(lookback, direction)   Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      lookback (int)      direction (int)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize()   Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize()   Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize()   Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent()   Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(fib, colorMatch)   Checks if the current bar is a hammer candle based on the given parameters   Parameters:      fib (float)      colorMatch (bool)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(fib, colorMatch)   Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      fib (float)      colorMatch (bool)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(wickSize, bodySize)   Checks if the current bar is a doji candle based on the given parameters   Parameters:      wickSize (float)      bodySize (float)   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bullish engulfing candle   Parameters:      allowance (float)      rejectionWickSize (float)      engulfWick (bool)   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(allowance, rejectionWickSize, engulfWick)   Checks if the current bar is a bearish engulfing candle   Parameters:      allowance (float)      rejectionWickSize (float)      engulfWick (bool)   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar()   Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar()   Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(sess, useFilter)   Determines if the current price bar falls inside the specified session   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls within the given time session barOutSession(sess, useFilter)   Determines if the current price bar falls outside the specified session   Parameters:      sess (simple string)      useFilter (bool)   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(startTime, endTime)   Determines if this bar's time falls within date filter range   Parameters:      startTime (int)      endTime (int)   Returns: A boolean - true if the current bar falls within the given dates dayFilter(monday, tuesday, wednesday, thursday, friday, saturday, sunday)   Checks if the current bar's day is in the list of given days to analyze   Parameters:      monday (bool)      tuesday (bool)      wednesday (bool)      thursday (bool)      friday (bool)      saturday (bool)      sunday (bool)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter(atrValue, maxSize)   Parameters:      atrValue (float)      maxSize (float) fillCell(tableID, column, row, title, value, bgcolor, txtcolor)   This updates the given table's cell with the given values   Parameters:      tableID (table)      column (int)      row (int)      title (string)      value (string)      bgcolor (color)      txtcolor (color)   Returns: A boolean - true if the current bar falls within the given dates
ספריית Pine Script®
מאת ‎liyugen‎
Rainbow Drift BetaRainbow Drift Beta is an indicator that detects the triggers of long and short positions at any TF. It's based on two different type of approaches to the EMAs periods: - Classic EMAs periods: 10 and 50 - Cycle EMAs perdios: 16, 64 and 256 The 256 period EMA (Annual Cycle) detects the trend: if the EMA 64 (Three-Weekly Cycle) is above, it shows an uptrend; while the EMA 64 is below, it means that the price action is in downtrend. 10 and 16 periods EMAs are working together as well as the 50 and the 64. The first couple reacts faster than the second one and as soon as the 10 is above the 16, the band shows the first attempt of the price action to go in the uptrend direction. The same concept is applied to the second couple (50, 64): when EMA 50 > EMA 64 it's a confirmation of the faster EMAs long direction. Viceverca happens for the downtrend but with the same concept. As the EMA periods taken in consideration are quite often a sensitive level of reaction of the price, the indicator detects when there is trigger of a long or a short set up and plots a label on the chart. It's possibile to set up an alert as well. Quite important, the indicator is looking for sideways patterns as the breakout of them shows a clear direction of the price. Moreover, in order to privide the first and the best entry possibile, the indicator has a function that is triggering only one time as the trend reverted: for example, a long entry on the EMA 10-16 happens only one time since they crossover the EMA 64. As included in the name, this is a beta version and new improvements will be added in the near future like suggested price entry, SL and TP, and the focus of the development is to avoid as much as possibile the false triggers. Of course the best way to improve the code is to receive the users' feedbacks, so please feel free to post your comments and questions.
אינדיקטור Pine Script®
מאת ‎math_rave‎
8
Fan Projections [theEccentricTrader]█   OVERVIEW This indicator automatically projects trendlines in the shape of a fan, from a single point of origin. In the example above I have applied the indicator twice to the 1D SPXUSD. The seven upper lines (green) are projected at an angle of -5 from the 1-month swing high anchor point. And the five lower lines (blue) are projected at an angle of 10 from the 1-week swing low anchor point. █   CONCEPTS Green and Red Candles • A green candle is one that closes with a high price equal to or above the price it opened. • A red candle is one that closes with a low price that is lower than the price it opened. Swing Highs and Swing Lows • A swing high is a green candle or series of consecutive green candles followed by a single red candle to complete the swing and form the peak. • A swing low is a red candle or series of consecutive red candles followed by a single green candle to complete the swing and form the trough. Peak and Trough Prices (Basic) • The peak price of a complete swing high is the high price of either the red candle that completes the swing high or the high price of the preceding green candle, depending on which is higher. • The trough price of a complete swing low is the low price of either the green candle that completes the swing low or the low price of the preceding red candle, depending on which is lower. Historic Peaks and Troughs The current, or most recent, peak and trough occurrences are referred to as occurrence zero. Previous peak and trough occurrences are referred to as historic and ordered numerically from right to left, with the most recent historic peak and trough occurrences being occurrence one. Support and Resistance • Support refers to a price level where the demand for an asset is strong enough to prevent the price from falling further. • Resistance refers to a price level where the supply of an asset is strong enough to prevent the price from rising further. Support and resistance levels are important because they can help traders identify where the price of an asset might pause or reverse its direction, offering potential entry and exit points. For example, a trader might look to buy an asset when it approaches a support level , with the expectation that the price will bounce back up. Alternatively, a trader might look to sell an asset when it approaches a resistance level , with the expectation that the price will drop back down. It's important to note that support and resistance levels are not always relevant, and the price of an asset can also break through these levels and continue moving in the same direction. Trendlines Trendlines are straight lines that are drawn between two or more points on a price chart. These lines are used as dynamic support and resistance levels for making strategic decisions and predictions about future price movements. For example traders will look for price movements along, and reactions to, trendlines in the form of rejections or breakouts/downs. █   FEATURES Inputs • Anchor Point Type • Swing High/Low Occurrence • HTF Resolution • Highest High/Lowest Low Lookback • Angle Degree • Number Lines • Line Color Anchor Point Types • Swing High • Swing Low • Swing High (HTF) • Swing Low (HTF) • Highest High • Lowest Low • Intraday Highest High (intraday charts only) • Intraday Lowest Low (intraday charts only) Swing High/Swing Low Occurrence This input is used to determine which historic peak or trough to reference for swing high or swing low anchor point types. HTF Resolution This input is used to determine which higher timeframe to reference for swing high (HTF) or swing low (HTF) anchor point types. Highest High/Lowest Low Lookback This input is used to determine the lookback length for highest high or lowest low anchor point types. Intraday Highest High/Lowest Low Lookback When using intraday highest high or lowest low anchor point types, the lookback length is calculated automatically based on number of bars since the daily candle opened. Angle Degree This input is used to determine the angle of the trendlines. The output is expressed in terms of point or pips, depending on the symbol type, which is then passed through the built in math.todegrees() function. Positive numbers will project the lines upwards while negative numbers will project the lines downwards. Depending on the market and timeframe, the impact input values will have on the visible gaps between the lines will vary greatly. For example, an input of 10 will have a far greater impact on the gaps between the lines when viewed from the 1-minute timeframe than it would on the 1-day timeframe. The input is a float and as such the value passed through can go into as many decimal places as the user requires. It is also worth mentioning that as more lines are added the gaps between the lines, that are closest to the anchor point, will get tighter as they make their way up the y-axis. Although the gaps between the lines will stay constant at the x2 plot, i.e. a distance of 10 points between them, they will gradually get tighter and tighter at the point of origin as the slope of the lines get steeper. Number Lines This input is used to determine the number of lines to be drawn on the chart, maximum is 500. █   LIMITATIONS All green and red candle calculations are based on differences between open and close prices, as such I have made no attempt to account for green candles that gap lower and close below the close price of the preceding candle, or red candles that gap higher and close above the close price of the preceding candle. This may cause some unexpected behaviour on some markets and timeframes. I can only recommend using 24-hour markets, if and where possible, as there are far fewer gaps and, generally, more data to work with. If the lines do not draw or you see a study error saying that the script references too many candles in history, this is most likely because the higher timeframe anchor point is not present on the current timeframe. This problem usually occurs when referencing a higher timeframe, such as the 1-month, from a much lower timeframe, such as the 1-minute. How far you can lookback for higher timeframe anchor points on the current timeframe will also be limited by your Trading View subscription plan. Premium users get 20,000 candles worth of data, pro+ and pro users get 10,000, and basic users get 5,000. █   RAMBLINGS It is my current thesis that the indicator will work best when used in conjunction with my Wavemeter indicator, which can be used to set the angle. For example, the average wave height or amplitude could be used as the value for the angle input. Or some factor or multiple of such an average. I think this makes sense as it allows for objectivity when applying the indicator across different markets and timeframes with different energies and vibrations. “If you want to find the secrets of the universe, think in terms of energy, frequency and vibration.” ― Nikola Tesla
אינדיקטור Pine Script®
מאת ‎theEccentricTrader‎
Wavemeter [theEccentricTrader]█   OVERVIEW This indicator is a representation of my take on price action based wave cycle theory. The indicator counts the number of confirmed wave cycles, keeps a rolling tally of the average wave length, wave height and frequency, and displays the statistics in a table. The indicator also displays the current wave measurements as an optional feature. █   CONCEPTS Green and Red Candles • A green candle is one that closes with a high price equal to or above the price it opened. • A red candle is one that closes with a low price that is lower than the price it opened. Swing Highs and Swing Lows • A swing high is a green candle or series of consecutive green candles followed by a single red candle to complete the swing and form the peak. • A swing low is a red candle or series of consecutive red candles followed by a single green candle to complete the swing and form the trough. Peak and Trough Prices (Basic) • The peak price of a complete swing high is the high price of either the red candle that completes the swing high or the high price of the preceding green candle, depending on which is higher. • The trough price of a complete swing low is the low price of either the green candle that completes the swing low or the low price of the preceding red candle, depending on which is lower. Historic Peaks and Troughs The current, or most recent, peak and trough occurrences are referred to as occurrence zero. Previous peak and trough occurrences are referred to as historic and ordered numerically from right to left, with the most recent historic peak and trough occurrences being occurrence one. Wave Cycles A wave cycle is here defined as a complete two-part move between a swing high and a swing low, or a swing low and a swing high. As can be seen in the example above, the first swing high or swing low will set the course for the sequence of wave cycles that follow; a chart that begins with a swing low will form its first complete wave cycle upon the formation of the first complete swing high and vice versa. Wave Length Wave length is here measured in terms of bar distance between the start and end of a wave cycle. For example, if the current wave cycle ends on a swing low the wave length will be the difference in bars between the current swing low and current swing high. In such a case, if the current swing low completes on candle 100 and the current swing high completed on candle 95, we would simply subtract 95 from 100 to give us a wave length of 5 bars. Average wave length is here measured in terms of total bars as a proportion as total waves. The average wavelength is calculated by dividing the total candles by the total wave cycles. Wave Height Wave height is here measured in terms of current range. For example, if the current peak price is 100 and the current trough price is 80, the wave height will be 20. Amplitude Amplitude is here measured in terms of current range divided by two. For example if the current peak price is 100 and the current trough price is 80, the amplitude would be calculated by subtracting 80 from 100 and dividing the answer by 2 to give us an amplitude of 10. Frequency Frequency is here measured in terms of wave cycles per second (Hertz). For example, if the total wave cycle count is 10 and the amount of time it has taken to complete these 10 cycles is 1-year (31,536,000 seconds), the frequency would be calculated by dividing 10 by 31,536,000 to give us a frequency of 0.00000032 Hz. Range The range is simply the difference between the current peak and current trough prices, generally expressed in terms of points or pips. █   FEATURES Inputs Show Sample Period Start Date End Date Position Text Size Show Current Show Lines Table The table is colour coded, consists of two columns and, as many as, nine rows. Blue cells display the total wave cycle count and average wave measurements. Green cells display the current wave measurements. And the final row in column one, coloured black, displays the sample period. Both current wave measurements and sample period cells can be hidden at the user’s discretion. Lines For a visual aid to the wave cycles, I have added a blue line that traces out the waves on the chart. These lines can be hidden at the user’s discretion. █   HOW TO USE The indicator is intended for research purposes, strategy development and strategy optimisation. I hope it will be useful in helping to gain a better understanding of the underlying dynamics at play on any given market and timeframe. For example, the indicator can be used to compare the current range and frequency with the average range and frequency, which can be useful for gauging current market conditions versus historic and getting a feel for how different markets and timeframes behave. █   LIMITATIONS Some higher timeframe candles on tickers with larger lookbacks such as the DXY , do not actually contain all the open, high, low and close (OHLC) data at the beginning of the chart. Instead, they use the close price for open, high and low prices. So, while we can determine whether the close price is higher or lower than the preceding close price, there is no way of knowing what actually happened intra-bar for these candles. And by default candles that close at the same price as the open price, will be counted as green. You can avoid this problem by utilising the sample period filter. The green and red candle calculations are based solely on differences between open and close prices, as such I have made no attempt to account for green candles that gap lower and close below the close price of the preceding candle, or red candles that gap higher and close above the close price of the preceding candle. I can only recommend using 24-hour markets, if and where possible, as there are far fewer gaps and, generally, more data to work with. Alternatively, you can replace the scenarios with your own logic to account for the gap anomalies, if you are feeling up to the challenge. It is also worth noting that the sample size will be limited to your Trading View subscription plan. Premium users get 20,000 candles worth of data, pro+ and pro users get 10,000, and basic users get 5,000. If upgrading is currently not an option, you can always keep a rolling tally of the statistics in an excel spreadsheet or something of the like.
אינדיקטור Pine Script®
מאת ‎theEccentricTrader‎
Percent Change of Day [ilovealgotrading] OVERVIEW: This indicator aims to effectively show us the percentage change of the price within the time frame we have chosen. What is the purpose of this indicator? This indicator shows how the price changes for each bar at different time frames we have chosen. By examining the percentage change in different time periods, we can easily look at the change in the face of the market during the time interval. Also if the price is above or below the value of 0 during the specified time, the color of our percentage line changes. IMPLEMENTATION DETAILS: First of all, let's understand How to Calculate Percent Change? The difference between the old and new value of a quantity given in percentages is known as a percent change. It's rather simple to calculate the % difference between two given quantities. The formula is given by; Example The price of a kilo of rice went from 10$ to12.5$, what is the percentage change? Explanation • The old value of sugar = $ 10 • New value = $12.5 • Now apply the percent change formula; • Percentage change = ×100% = x 100% = (2.5/10) x 100% = 25% In this case, the percent change is positive and therefore, it is an increase. How Is Percentage Change Used in Finance? In the world of finance, percentage change is frequently used to analyze changes in the value of stocks or major market indexes over time. Percentage change is used for many purposes in finance, most notably to track the price change of stocks market and crypto market. What can we change from the settings panel ? We can set time frame setting of the percentage change from place number 1 We are able to adjust the changing color if the percentage change is above or below zero from place 2 and 3 ALSO: Please do not open trades without properly managing your risk and psychology!!! If you have any ideas what to add to my work to add more sources or make calculations cooler, suggest in DM .
אינדיקטור Pine Script®
מאת ‎projeadam‎
3
Failed Breakdown Detection'Failed Breakdowns' are a popular set up for long entries. In short, the set up requires: 1) A significant low is made ('initial low') 2) Initial low is undercut with a new low 3) Price action then 'reclaims' the initial low by moving +8-10 points from the initial low This script aims at detecting such set ups. It was coded with the ES Futures 15 minute chart in mind but may be useful on other instruments and time frames. Business Logic: 1) Uses pivot lows to detect 'significant' initial lows 2) Uses amplitude threshold to detect a new low beneath the initial low; used /u/ben_zen script for this 3) Looks for a valid reclaim - a green candle that occurs within 10 bars of the new low 4) Price must reclaim at least 8 points for the set up to be valid 5) If a signal is detected, the initial low value (pivot low) is stored in array that prevents duplicate signals from being generated. 6) FBD Signal is plotted on the chart with "X" 7) Pivot low detection is plotted on the chart with "P" and a label 8) New lows are plotted on the chart with a blue triangle Notes: User input - My preference is to use the defaults as is, but as always feel free to experiment - Can modify pivot length but in my experience 10/10 work best for pivot lows - New low detection - 55 bars and 0.05 amplitude work well based on visual checks of signals - Can modify the number of points needed to reclaim a low, and the # of bars limit under which this must occur. Alerts: - Alerts are available for detection of new lows and detection of failed breakdowns - Alerts are also available for these signals but only during 7:30PM-4PM EST - 'prime time' US trading hours Limitations: - Current version of the script only compares new lows to the most recent pivot low, does not look at anything prior to that - Best used as a discretionary signal Visit /u/ben_zen's Profile: www.tradingview.com Profile Link www.tradingview.com
אינדיקטור Pine Script®
מאת ‎xfuturesgod‎
21
RSI with Market FilterThis is a normal Relative Strength Index with default length set to 14 periods In addition, SET and MAI market Trend filter: When SET or MAI is above 10 and 35 EMA - consider as a strong uptrend. SET or MAI is below EMA 10 but still above EMA 35 - consider as a healthy Uptrend but resting with lower momentum. SET or MAI is below EMA 10 and 35 - consider as a Downtrend. It is recommended not to trade in this market. SET or MAI is above EMA 10 but below EMA 35 - consider as a starting point of the uptrend. It is recommended to start looking for a possible trade when the market flip into Uptrend.
אינדיקטור Pine Script®
מאת ‎vite111‎
DR/IDR Candles [LuxAlgo]This indicator displays defining ranges (DR) and implied defining ranges (IDR) constructed from two user set sessions (RDR/ODR) as graphical candles on the chart. The script introduces additional graphical elements to the original DR/IDR concept and as such can be thought as a graphical method in addition to a technical indicator. Additionally, this script can display various Fibonacci retracements from the constructed DR/IDR if enabled within the settings. Settings Regular Session: Enable/disable regular session's DR/IDR alongside setting the session time. By default, 09:30 - 10:30 am. Overnight Session: Enable/disable overnight session's DR/IDR alongside setting the session time. By default, 03:00 - 04:00 am. UTC Offset: UTC offset for the time zone, by default -5 (EST) Retracements Reverse: Inverts source range upper/lower value for constructing the retracements. From: Source range used to construct the retracements, by default DR is used. By default, the 0.5 retracement (average line) is displayed. Usage The used sessions are highlighted by a gray background. DRs are highlighted by dashed lines while IDRs are highlighted by solid ones. The maximum/minimum price between each user set session is highlighted by solid wicks. The color of the DRs/IDRs/wicks are determined by the price position relative to the DR; if price is above the DR maximum, then a blue color is used. If price is below, then an orange color is used, and if price is within the DR range, then a gray color is used. Additionally, the area of the DR range is used to highlight the number of time price is located within the DR, with a longer background highlighting a higher number of occurrences. This can help highlight if the DR levels were potentially useful as support/resistance. When price is outside the IDR range, the area between the price and IDR is highlighted, in blue if price is above the IDR, and orange if it is under. The original author of the DR/IDR concept describes 3 rules using the price position relative to the DR/IDR levels: 1.) If price on the 5-minute timeframe closes above the DR high after 10:30 AM or 04:00 AM then the DR low will likely be the low of the trading session. 2.) If price on the 5-minute timeframe closes below the DR low after 10:30 AM or 04:00 AM then the DR high will likely be the high of the trading session. 3.) If price closes above the IDR high after 10:30 AM or 04:00 AM it is an early indication that the low of the DR will be the low of the day and vice versa. We can see that the above rules are cases of conditional probabilities. There is no significant data supporting or regarding any statistical probability of the above rules to be true, which are more than uncertain given the stochastic nature of prices. The lack of precision of these rules is also a concern (time zone dependance, applicable markets, etc...). Credits Credits to trader TheMas7er who originally created the DR/IDR concept in November of 2022. This script was derived from his proposed session times & rules for trading.
אינדיקטור Pine Script®
מאת ‎LuxAlgo‎
34
Morning Scalp StrategyThe Morning Scalp Strategy combines the 50EMA with the Stochastic Momentum Index. The morning period is when penny stocks usually have the highest volatility, so the strategy works between 10:00 AM and 12:10 PM. ***It opens only long positions. The ideal timeframe for this scalping strategy is 5 minutes on low-price stocks. The stock should spike in the morning with momentum and Volume. ***Look for a daily or intraday support area, close to the open position, to increase the confidence in the play The components are: - EMA50: Exponential Moving Average (EMA50) - Stochastic Momentum Index (SMI) Rules: - Period: 10:00 AM and 12:10 PM - if SMI Crossover and SMI < 0, open a position - If close < EMA50, close the position - Profit target: To be decided by the user, default value = 10% above the entry price If you have any questions, let me know!
אסטרטגיית Pine Script®
מאת ‎Trading_Bites‎
6
TASC 2022.10 RS VA EMA█ OVERVIEW TASC's October 2022 edition Traders' Tips includes the second part of the "​Relative Strength Moving Averages" article series authored by Vitali Apirine. This is the code that implements the ​Relative Strength Volume-Adjusted ​Exponential Moving Average (​RS VA ​EMA) presented in this publication. █ CONCEPTS In his article series, the author argues that the relative strength of price, ​volume, and ​volatility can potentially be used to filter price movements and define turning points. In particular, the ​RS VA ​​EMA indicator is designed to account for the ​relative strength of ​volume. Like the traditional ​ exponential moving average (​EMA) , it is a lagging trend-following indicator. The difference is that it responds more quickly. In a trading strategy, ​​RS VA ​EMA is suggested to be used in combination with ​​EMA of the same length to determine the overall trend or in combination with ​RS VA ​EMA of a different length to identify turning points and filter price movements. █ CALCULATIONS The calculation of ​RS VA ​EMA is based on the concept of ​volume strength (VS). By definition, VS measures the difference between "positive" and "negative" ​volume flow. ​Volume is indicated as "positive" when the close is higher than the previous close and "negative" when the close is below the previous close. The following steps are used in the calculation process: • Calculate the ​volume strength (VS) of a given length. • Multiply VS by a predefined multiplier and calculate the ​EMA of the resulting time series. The values of 10,10,10 are the typical input settings for ​RS VA ​EMA, where the first parameter is the length of the moving average, the second is the length of VS, and the third is the ​volume strength multiplier.
אינדיקטור Pine Script®
מאת ‎PineCodersTASC‎
2
TriexDev - SuperBuySellTrend (PLUS+)Minimal but powerful. Have been using this for myself, so thought it would be nice to share publicly. Of course no script is correct 100% of the time, but this is one of if not the best in my basic tools. (This is the expanded/PLUS version) Github Link for latest/most detailed + tidier documentation Base Indicator - Script Link TriexDev - SuperBuySellTrend (SBST+) TradingView Trend Indicator --- SBST Plus+ Using the "plus" version is optional, if you only want the buy/sell signals - use the "base" version. ## What are vector candles? Vector Candles (inspired to add from TradersReality/MT4) are candles that are colour coded to indicate higher volumes, and likely flip points / direction changes, or confirmations. These are based off of PVSRA (Price, Volume, Support, Resistance Analysis). You can also override the currency that this runs off of, including multiple ones - however adding more may slow things down. PVSRA - From MT4 source: Situation "Climax" Bars with volume >= 200% of the average volume of the 10 previous chart TFs, and bars where the product of candle spread x candle volume is >= the highest for the 10 previous chart time TFs. Default Colours: Bull bars are green and bear bars are red. Situation "Volume Rising Above Average" Bars with volume >= 150% of the average volume of the 10 previous chart TFs. Default Colours: Bull bars are blue and bear are blue-violet. A blue or purple bar can mean the chart has reached a top or bottom. High volume bars during a movement can indicate a big movement is coming - or a top/bottom if bulls/bears are unable to break that point - or the volume direction has flipped. This can also just be a healthy short term movement in the opposite direction - but at times sets obvious trend shifts. ## Volume Tracking You can shift-click any candle to get the volume of that candle (in the pair token/stock), if you click and drag - you will see the volume for that range. ## Bollinger Bands Bollinger Bands can be enabled in the settings via the toggle. Bollinger Bands are designed to discover opportunities that give investors a higher probability of properly identifying when an asset is oversold (bottom lines) or overbought (top lines). >There are three lines that compose Bollinger Bands: A simple moving average (middle band) and an upper and lower band. >The upper and lower bands are typically 2 standard deviations +/- from a 20-day simple moving average, but they can be modified. --- Base Indicator ## What is ATR? The average true range (ATR) is a technical analysis indicator, which measures market volatility by decomposing the entire range of an asset price for that period. The true range indicator is taken as the greatest of the following: - current high - the current low; - the absolute value of the current high - the previous close; - and the absolute value of the current low - the previous close. The ATR is then a moving average, generally using 10/14 days, of the true ranges. ## What does this indicator do? Uses the ATR and multipliers to help you predict price volatility, ranges and trend direction. > The buy and sell signals are generated when the indicator starts plotting either on top of the closing price or below the closing price. A buy signal is generated when the ‘Supertrend’ closes above the price and a sell signal is generated when it closes below the closing price. > It also suggests that the trend is shifting from descending mode to ascending mode. Contrary to this, when a ‘Supertrend’ closes above the price, it generates a sell signal as the colour of the indicator changes into red. > A ‘Supertrend’ indicator can be used on equities, futures or forex, or even crypto markets and also on daily, weekly and hourly charts as well, but generally, it will be less effective in a sideways-moving market. Thanks to KivancOzbilgic who made the original SuperTrend Indicator this was based off --- ## Usage Notes Two indicators will appear, the default ATR multipliers are already set for what I believe to be perfect for this particular (double indicator) strategy. If you want to break it yourself (I couldn't find anything that tested more accurately myself), you can do so in the settings once you have added the indicator. Basic rundown: - A single Buy/Sell indicator in the dim colour; may be setting a direction change, or just healthy movement. - When the brighter Buy/Sell indicator appears; it often means that a change in direction (uptrend or downtrend) is confirmed. --- You can see here, there was a (brighter) green indicator which flipped down then up into a (brighter) red sell indicator which set the downtrend. At the end it looks like it may be starting to break the downtrend - as the price is hitting the trend line. (Would watch for whether it holds above or drops below at that point) Another example, showing how sometimes it can still be correct but take some time to play out - with some arrow indicators. Typically I would also look at oscillators, RSI and other things to confirm - but here it held above the trend lines nicely, so it appeared to be rather obvious. It's worth paying attention to the trend lines and where the candles are sitting. Once you understand/get a feel for the basics of how it works - it can become a very useful tool in your trading arsenal. Also works for traditional markets & commodities etc in the same way / using the same ATR multipliers, however of course crypto generally has bigger moves. --- You can use this and other indicators to confirm likeliness of a direction change prior to the brighter/confirmation one appearing - but just going by the 2nd(brighter) indicators, I have found it to be surprisingly accurate. Tends to work well on virtually all timeframes, but personally prefer to use it on 5min,15min,1hr, 4hr, daily, weekly. Will still work for shorter/other timeframes, but may be more accurate on mid ones. --- This will likely be updated as I go / find useful additions that don't convolute things. The base indicator may be updated with some limited / toggle-able features in future also.
אינדיקטור Pine Script®
מאת ‎Xeirt‎
4
SUPERTREND MIXED ICHI-DMI-DONCHIAN-VOL-GAP-HLBox@RLSUPERTREND MIXED ICHI-DMI-VOL-GAP-HLBox@RL by RegisL76 This script is based on several trend indicators. * ICHIMOKU (KINKO HYO) * DMI (Directional Movement Index) * SUPERTREND ICHIMOKU + SUPERTREND DMI * DONCHIAN CANAL Optimized with Colored Bars * HMA Hull * Fair Value GAP * VOLUME/ MA Volume * PRICE / MA Price * HHLL BOXES All these indications are visible simultaneously on a single graph. A data table summarizes all the important information to make a good trade decision. ICHIMOKU Indicator: The ICHIMOKU indicator is visualized in the traditional way. ICHIMOKU standard setting values are respected but modifiable. (Traditional defaults = . An oriented visual symbol, near the last value, indicates the progression (Ascending, Descending or neutral) of the TENKAN-SEN and the KIJUN-SEN as well as the period used. The CLOUD (KUMO) and the CHIKOU-SPAN are present and are essential for the complete analysis of the ICHIMOKU. At the top of the graph are visually represented the crossings of the TENKAN and the KIJUN. Vertical lines, accompanied by labels, make it possible to quickly visualize the particularities of the ICHIMOKU. A line displays the current bar. A line visualizes the end of the CLOUD (KUMO) which is shifted 25 bars into the future. A line visualizes the end of the chikou-span, which is shifted 25 bars in the past. DIRECTIONAL MOVEMENT INDEX (DMI) : Treated conventionally : DI+, DI-, ADX and associated with a SUPERTREND DMI. A visual symbol at the bottom of the graph indicates DI+ and DI- crossings A line of oriented and colored symbols (DMI Line) at the top of the chart indicates the direction and strength of the trend. SUPERTREND ICHIMOKU + SUPERTREND DMI : Trend following by SUPERTREND calculation. DONCHIAN CHANNEL: Treated conventionally. (And optimized by colored bars when overshooting either up or down. The lines, high and low of the last values of the channel are represented to quickly visualize the level of the RANGE. SUPERTREND HMA (HULL) Treated conventionally. The HMA line visually indicates, according to color and direction, the market trend. A visual symbol at the bottom of the chart indicates opportunities to sell and buy. VOLUME: Calculation of the MOBILE AVERAGE of the volume with comparison of the volume compared to the moving average of the volume. The indications are colored and commented according to the comparison. PRICE: Calculation of the MOBILE AVERAGE of the price with comparison of the price compared to the moving average of the price. The indications are colored and commented according to the comparison. HHLL BOXES: Visualizes in the form of a box, for a given period, the max high and min low values of the price. The configuration allows taking into account the high and low wicks of the price or the opening and closing values. FAIR VALUE GAP : This indicator displays 'GAP' levels over the current time period and an optional higher time period. The script takes into account the high/low values of the current bar and compares with the 2 previous bars. The "gap" is generated from the lack of overlap between these bars. Bearish or bullish gaps are determined by whether the gap is above or below HmaPrice, as they tend to fill, and can be used as targets. NOTE: FAIR VALUE GAP has no values displayed in the table and/or label. Important information (DATA) relating to each indicator is displayed in real time in a table and/or a label. Each information is commented and colored according to direction, value, comparison etc. Each piece of information indicates the values of the current bar and the previous value (in "FULL" mode). The other possible modes for viewing the table and/or the label allow a more synthetic view of the information ("CONDENSED" and "MINIMAL" modes). In order not to overload the vision of the chart too much, the visualization box of the RANGE DONCHIAN, the vertical lines of the shifted marks of the ICHIMOKU, as well as the boxes of the HHLL Boxes indicator are only visualized intermittently (managed by an adjustable time delay ). The "HISTORICAL INFO READING" configuration parameter set to zero (by default) makes it possible to read all the information of the current bar in progress (Bar #0). All other values allow to read the information of a historical bar. The value 1 reads the information of the bar preceding the current bar (-1). The value 10 makes it possible to read the information of the tenth bar behind (-10) compared to the current bar, etc. At the bottom of the DATAS table and label, lights, red, green or white indicate quickly summarize the trend from the various indicators. Each light represents the number of indicators with the same trend at a given time. Green for a bullish trend, red for a bearish trend and white for a neutral trend. The conditions for determining a trend are for each indicator: SUPERTREND ICHIMOHU + DMI: the 2 Super trends together are either bullish or bearish. Otherwise the signal is neutral. DMI: 2 main conditions: BULLISH if DI+ >= DI- and ADX >25. BEARISH if DI+ < DI- and ADX >25. NEUTRAL if the 2 conditions are not met. ICHIMOKU: 3 main conditions: BULLISH if PRICE above the cloud and TENKAN > KIJUN and GREEN CLOUD AHEAD. BEARISH if PRICE below the cloud and TENKAN < KIJUN and RED CLOUD AHEAD. The other additional conditions (Data) complete the analysis and are present for informational purposes of the trend and depend on the context. DONCHIAN CHANNEL: 1 main condition: BULLISH: the price has crossed above the HIGH DC line. BEARISH: the price has gone below the LOW DC line. NEUTRAL if the price is between the HIGH DC and LOW DC lines The 2 other complementary conditions (Datas) complete the analysis: HIGH DC and LOW DC are increasing, falling or stable. SUPERTREND HMA HULL: The script determines several trend levels: STRONG BUY, BUY, STRONG SELL, SELL AND NEUTRAL. VOLUME: 3 trend levels: VOLUME > MOVING AVERAGE, VOLUME < MOVING AVERAGE, VOLUME = MOVING AVERAGE. PRICE: 3 trend levels: PRICE > MOVING AVERAGE, PRICE < MOVING AVERAGE, PRICE = MOVING AVERAGE. If you are using this indicator/strategy and you are satisfied with the results, you can possibly make a donation (a coffee, a pizza or more...) via paypal to: lebourg.regis@free.fr. Thanks in advance !!! Have good winning Trades. ************************************************************************************************************************** SUPERTREND MIXED ICHI-DMI-VOL-GAP-HLBox@RL by RegisL76 Ce script est basé sur plusieurs indicateurs de tendance. * ICHIMOKU (KINKO HYO) * DMI (Directional Movement Index) * SUPERTREND ICHIMOKU + SUPERTREND DMI * DONCHIAN CANAL Optimized with Colored Bars * HMA Hull * Fair Value GAP * VOLUME/ MA Volume * PRIX / MA Prix * HHLL BOXES Toutes ces indications sont visibles simultanément sur un seul et même graphique. Un tableau de données récapitule toutes les informations importantes pour prendre une bonne décision de Trade. I- Indicateur ICHIMOKU : L’indicateur ICHIMOKU est visualisé de manière traditionnelle Les valeurs de réglage standard ICHIMOKU sont respectées mais modifiables. (Valeurs traditionnelles par défaut = Un symbole visuel orienté, à proximité de la dernière valeur, indique la progression (Montant, Descendant ou neutre) de la TENKAN-SEN et de la KIJUN-SEN ainsi que la période utilisée. Le NUAGE (KUMO) et la CHIKOU-SPAN sont bien présents et sont primordiaux pour l'analyse complète de l'ICHIMOKU. En haut du graphique sont représentés visuellement les croisements de la TENKAN et de la KIJUN. Des lignes verticales, accompagnées d'étiquettes, permettent de visualiser rapidement les particularités de l'ICHIMOKU. Une ligne visualise la barre en cours. Une ligne visualise l'extrémité du NUAGE (KUMO) qui est décalé de 25 barres dans le futur. Une ligne visualise l'extrémité de la chikou-span, qui est décalée de 25 barres dans le passé. II-DIRECTIONAL MOVEMENT INDEX (DMI) Traité de manière conventionnelle : DI+, DI-, ADX et associé à un SUPERTREND DMI Un symbole visuel en bas du graphique indique les croisements DI+ et DI- Une ligne de symboles orientés et colorés (DMI Line) en haut du graphique, indique la direction et la puissance de la tendance. III SUPERTREND ICHIMOKU + SUPERTREND DMI Suivi de tendance par calcul SUPERTREND IV- DONCHIAN CANAL : Traité de manière conventionnelle. (Et optimisé par des barres colorées en cas de dépassement soit vers le haut, soit vers le bas. Les lignes, haute et basse des dernières valeurs du canal sont représentées pour visualiser rapidement la fourchette du RANGE. V- SUPERTREND HMA (HULL) Traité de manière conventionnelle. La ligne HMA indique visuellement, selon la couleur et l'orientation, la tendance du marché. Un symbole visuel en bas du graphique indique les opportunités de vente et d'achat. *VI VOLUME : Calcul de la MOYENNE MOBILE du volume avec comparaison du volume par rapport à la moyenne mobile du volume. Les indications sont colorées et commentées en fonction de la comparaison. *VII PRIX : Calcul de la MOYENNE MOBILE du prix avec comparaison du prix par rapport à la moyenne mobile du prix. Les indications sont colorées et commentées en fonction de la comparaison. *VIII HHLL BOXES : Visualise sous forme de boite, pour une période donnée, les valeurs max hautes et min basses du prix. La configuration permet de prendre en compte les mèches hautes et basses du prix ou bien les valeurs d'ouverture et de fermeture. IX - FAIR VALUE GAP Cet indicateur affiche les niveaux de 'GAP' sur la période temporelle actuelle ET une période temporelle facultative supérieure. Le script prend en compte les valeurs haut/bas de la barre actuelle et compare avec les 2 barres précédentes. Le "gap" est généré à partir du manque de recouvrement entre ces barres. Les écarts baissiers ou haussiers sont déterminés selon que l'écart est supérieurs ou inférieur à HmaPrice, car ils ont tendance à être comblés, et peuvent être utilisés comme cibles. NOTA : FAIR VALUE GAP n'a pas de valeurs affichées dans la table et/ou l'étiquette. Les informations importantes (DATAS) relatives à chaque indicateur sont visualisées en temps réel dans une table et/ou une étiquette. Chaque information est commentée et colorée en fonction de la direction, de la valeur, de la comparaison etc. Chaque information indique la valeurs de la barre en cours et la valeur précédente ( en mode "COMPLET"). Les autres modes possibles pour visualiser la table et/ou l'étiquette, permettent une vue plus synthétique des informations (modes "CONDENSÉ" et "MINIMAL"). Afin de ne pas trop surcharger la vision du graphique, la boite de visualisation du RANGE DONCHIAN, les lignes verticales des marques décalées de l'ICHIMOKU, ainsi que les boites de l'indicateur HHLL Boxes ne sont visualisées que de manière intermittente (géré par une temporisation réglable ). Le paramètre de configuration "HISTORICAL INFO READING" réglé sur zéro (par défaut) permet de lire toutes les informations de la barre actuelle en cours (Barre #0). Toutes autres valeurs permet de lire les informations d'une barre historique. La valeur 1 permet de lire les informations de la barre précédant la barre en cours (-1). La valeur 10 permet de lire les information de la dixième barre en arrière (-10) par rapport à la barre en cours, etc. Dans le bas de la table et de l'étiquette de DATAS, des voyants, rouge, vert ou blanc indique de manière rapide la synthèse de la tendance issue des différents indicateurs. Chaque voyant représente le nombre d'indicateur ayant la même tendance à un instant donné. Vert pour une tendance Bullish, rouge pour une tendance Bearish et blanc pour une tendance neutre. Les conditions pour déterminer une tendance sont pour chaque indicateur : SUPERTREND ICHIMOHU + DMI : les 2 Super trends sont ensemble soit bullish soit Bearish. Sinon le signal est neutre. DMI : 2 conditions principales : BULLISH si DI+ >= DI- et ADX >25. BEARISH si DI+ < DI- et ADX >25. NEUTRE si les 2 conditions ne sont pas remplies. ICHIMOKU : 3 conditions principales : BULLISH si PRIX au dessus du nuage et TENKAN > KIJUN et NUAGE VERT DEVANT. BEARISH si PRIX en dessous du nuage et TENKAN < KIJUN et NUAGE ROUGE DEVANT. Les autres conditions complémentaires (Datas) complètent l'analyse et sont présents à titre informatif de la tendance et dépendent du contexte. CANAL DONCHIAN : 1 condition principale : BULLISH : le prix est passé au dessus de la ligne HIGH DC. BEARISH : le prix est passé au dessous de la ligne LOW DC. NEUTRE si le prix se situe entre les lignes HIGH DC et LOW DC Les 2 autres conditions complémentaires (Datas) complètent l'analyse : HIGH DC et LOW DC sont croissants, descendants ou stables. SUPERTREND HMA HULL : Le script détermine plusieurs niveaux de tendance : STRONG BUY, BUY, STRONG SELL, SELL ET NEUTRE. VOLUME : 3 niveaux de tendance : VOLUME > MOYENNE MOBILE, VOLUME < MOYENNE MOBILE, VOLUME = MOYENNE MOBILE. PRIX : 3 niveaux de tendance : PRIX > MOYENNE MOBILE, PRIX < MOYENNE MOBILE, PRIX = MOYENNE MOBILE. Si vous utilisez cet indicateur/ stratégie et que vous êtes satisfait des résultats, vous pouvez éventuellement me faire un don (un café, une pizza ou plus ...) via paypal à : lebourg.regis@free.fr. Merci d'avance !!! Ayez de bons Trades gagnants.
אינדיקטור Pine Script®
מאת ‎RegisL76‎
1
Options Volume Indicator Volume Indicator for Option Trading, it is a simple indicator based on Relative Strength Index. There are two horizontal lines are mention 10 and -10, if bar crossed above the (Line 10) then go for buy and when Bar cross under (Line -10) go for sell side. If Bar Color changed to Respective color of the previous bar i.e. color gets darker then you can exit/ trail SL there because it overbought / Oversold position and vice versa for Sell Side. this volume indicator works on any Script. The Black Floating Line indicates the Average volume
אינדיקטור Pine Script®
מאת ‎LossTronaut‎
10
Estrategia Larry Connors [JoseMetal]============ ENGLISH ============ - Description: This strategy is based on the original Larry Connors strategy, using 2 SMAs and RSI. The strategy has been optimized for better total profit and works better on 4H (tested on BTCUSDT). LONG: Price must be ABOVE the slow SMA. When a candle closes in RSI oversold area, the next candle closes out of the oversold area and the closing price is BELOW the fast SMA = open LONG. LONG is closed when a candle closes ABOVE the fast SMA. SHORT: Price must be BELOW the slow SMA. When a candle closes in RSI overbought area, the next candle closes out of the overbought area and the closing price is ABOVE the fast SMA = open SHORT. SHORT is closed when a candle closes BELOW the fast SMA. *Larry Connor's strategy does NOT use a fixed Stop Loss or Take Profit, as he said, that reduces performance significantly. - Visual: Both SMAs (fast and slow) are shown in the chart. By default, the fast SMA is aqua color, the slow changes between green and red depending on the "trend" (price over slow SMA = bullish, below = bearish). RSI can't be shown because TradingView doesn't allow to show both overlay and panel indicators, so candles get a RED color when RSI is in OVERBOUGHT area and GREEN when they're on OVERSOLD area to help with that. Background is colored when conditions are met and a position is going to be open, green for LONGs red for SHORTs. - Usage and recommendations: As this is a coded strategy, you don't even have to check for indicators, just open and close trades as the strategy shows. The original strategy uses a 5 period SMA instead of the 10, and 10/90 for oversold/overbought levels, this has been optimized after the testings and results but feel free to change settings and test by yourself. Also, the original strategy was developed for daily, but seems to work better en 4H. - Customization: As usual I like to make as many aspects of my indicators/strategies customizable, indicators, colors etc., feel free to ask if you feel that something that should be configurable is missing or if you have any ideas to optimize the strategy. ============ ESPAÑOL ============ - Descripción: Esta estrategia está basada en la estrategia original de Larry Connors, utilizando 2 SMAs y RSI. La estrategia ha sido optimizada para un mejor beneficio total y funciona mejor en 4H (probado en BTCUSDT). LONG: El precio debe estar por encima de la SMA lenta. Cuando una vela cierra en la zona de sobreventa del RSI, la siguiente vela cierra fuera de la zona de sobreventa y el precio de cierre está POR DEBAJO de la SMA rápida = abre LONG. Se cierra cuando una vela cierra POR ENCIMA de la SMA rápida. SHORT: El precio debe estar POR DEBAJO de la SMA lenta. Cuando una vela cierra en la zona de sobrecompra del RSI, la siguiente vela cierra fuera de la zona de sobrecompra y el precio de cierre está POR ENCIMA de la SMA rápida = abre SHORT. Se cierra cuando una vela cierra POR DEBAJO de la SMA rápida. *La estrategia de Larry Connor NO utiliza un Stop Loss o Take Profit fijo, como él dijo, eso reduce el rendimiento significativamente. - Visual: Ambas SMAs (rápida y lenta) se muestran en el gráfico. Por defecto, la SMA rápida es de color aqua, la lenta cambia entre verde y rojo dependiendo de la "tendencia" (precio por encima de la SMA lenta = alcista, por debajo = bajista). El RSI no puede mostrarse porque TradingView no permite mostrar tanto los indicadores superpuestos como los del panel, así que las velas obtienen un color ROJO cuando el RSI está en el área de SOBRECOMPRA y VERDE cuando están en el área de VENTA para ayudar a ello. El fondo se colorea cuando se cumplen las condiciones y se va a abrir una posición, verde para LONGs rojo para SHORTs. - Uso y recomendaciones: Como se trata de una estrategia ya programada, ni siquiera hay que comprobar los indicadores, sólo hay que abrir y cerrar las operaciones tal y como muestra la estrategia en el gráfico. La estrategia original utiliza una SMA de 5 periodos en lugar de 10, y 10/90 para los niveles de sobreventa/sobrecompra, esto ha sido optimizado después de las pruebas y los resultados, pero sé libre de cambiar la configuración y probarla por sí mismo. Además, la estrategia original fue desarrollada para diario, pero parece funcionar mejor en 4H. - Personalización: Como siempre me gusta hacer personalizables todos los aspectos de mis indicadores/estrategias, indicadores, colores, etc., preguntar si notas que falta algo que debería ser configurable o si tienes alguna idea para optimizar la estrategia.
אסטרטגיית Pine Script®
מאת ‎JoseMetal‎
14
Library CommonLibrary "LibraryCommon" A collection of custom tools & utility functions commonly used with my scripts @description TODO: add library description here getDecimals() Calculates how many decimals are on the quote price of the current market   Returns: The current decimal places on the market quote price truncate(float, float) Truncates (cuts) excess decimal places   Parameters:      float : number The number to truncate      float : decimalPlaces (default=2) The number of decimal places to truncate to   Returns: The given number truncated to the given decimalPlaces toWhole(float) Converts pips into whole numbers   Parameters:      float : number The pip number to convert into a whole number   Returns: The converted number toPips(float) Converts whole numbers back into pips   Parameters:      float : number The whole number to convert into pips   Returns: The converted number getPctChange(float, float, int) Gets the percentage change between 2 float values over a given lookback period   Parameters:      float : value1 The first value to reference      float : value2 The second value to reference      int : lookback The lookback period to analyze av_getPositionSize(float, float, float, float) Calculates OANDA forex position size for AutoView based on the given parameters   Parameters:      float : balance The account balance to use      float : risk The risk percentage amount (as a whole number - eg. 1 = 1% risk)      float : stopPoints The stop loss distance in POINTS (not pips)      float : conversionRate The conversion rate of our account balance currency   Returns: The calculated position size (in units - only compatible with OANDA) bullFib(priceLow, priceHigh, fibRatio) Calculates a bullish fibonacci value   Parameters:      priceLow : The lowest price point      priceHigh : The highest price point      fibRatio : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points bearFib(priceLow, priceHigh, fibRatio) Calculates a bearish fibonacci value   Parameters:      priceLow : The lowest price point      priceHigh : The highest price point      fibRatio : The fibonacci % ratio to calculate   Returns: The fibonacci value of the given ratio between the two price points getMA(int, string) Gets a Moving Average based on type (MUST BE CALLED ON EVERY CALCULATION)   Parameters:      int : length The MA period      string : maType The type of MA   Returns: A moving average with the given parameters getEAP(float) Performs EAP stop loss size calculation (eg. ATR >= 20.0 and ATR < 30, returns 20)   Parameters:      float : atr The given ATR to base the EAP SL calculation on   Returns: The EAP SL converted ATR size getEAP2(float) Performs secondary EAP stop loss size calculation (eg. ATR < 40, add 5 pips, ATR between 40-50, add 10 pips etc)   Parameters:      float : atr The given ATR to base the EAP SL calculation on   Returns: The EAP SL converted ATR size barsAboveMA(int, float) Counts how many candles are above the MA   Parameters:      int : lookback The lookback period to look back over      float : ma The moving average to check   Returns: The bar count of how many recent bars are above the MA barsBelowMA(int, float) Counts how many candles are below the MA   Parameters:      int : lookback The lookback period to look back over      float : ma The moving average to reference   Returns: The bar count of how many recent bars are below the EMA barsCrossedMA(int, float) Counts how many times the EMA was crossed recently   Parameters:      int : lookback The lookback period to look back over      float : ma The moving average to reference   Returns: The bar count of how many times price recently crossed the EMA getPullbackBarCount(int, int) Counts how many green & red bars have printed recently (ie. pullback count)   Parameters:      int : lookback The lookback period to look back over      int : direction The color of the bar to count (1 = Green, -1 = Red)   Returns: The bar count of how many candles have retraced over the given lookback & direction getBodySize() Gets the current candle's body size (in POINTS, divide by 10 to get pips)   Returns: The current candle's body size in POINTS getTopWickSize() Gets the current candle's top wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's top wick size in POINTS getBottomWickSize() Gets the current candle's bottom wick size (in POINTS, divide by 10 to get pips)   Returns: The current candle's bottom wick size in POINTS getBodyPercent() Gets the current candle's body size as a percentage of its entire size including its wicks   Returns: The current candle's body size percentage isHammer(float, bool) Checks if the current bar is a hammer candle based on the given parameters   Parameters:      float : fib (default=0.382) The fib to base candle body on      bool : colorMatch (default=false) Does the candle need to be green? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a hammer candle isStar(float, bool) Checks if the current bar is a shooting star candle based on the given parameters   Parameters:      float : fib (default=0.382) The fib to base candle body on      bool : colorMatch (default=false) Does the candle need to be red? (true/false)   Returns: A boolean - true if the current bar matches the requirements of a shooting star candle isDoji(float, bool) Checks if the current bar is a doji candle based on the given parameters   Parameters:      float : wickSize (default=2) The maximum top wick size compared to the bottom (and vice versa)      bool : bodySize (default=0.05) The maximum body size as a percentage compared to the entire candle size   Returns: A boolean - true if the current bar matches the requirements of a doji candle isBullishEC(float, float, bool) Checks if the current bar is a bullish engulfing candle   Parameters:      float : allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bullish engulfing candle isBearishEC(float, float, bool) Checks if the current bar is a bearish engulfing candle   Parameters:      float : allowance (default=0) How many POINTS to allow the open to be off by (useful for markets with micro gaps)      float : rejectionWickSize (default=disabled) The maximum rejection wick size compared to the body as a percentage      bool : engulfWick (default=false) Does the engulfing candle require the wick to be engulfed as well?   Returns: A boolean - true if the current bar matches the requirements of a bearish engulfing candle isInsideBar() Detects inside bars   Returns: Returns true if the current bar is an inside bar isOutsideBar() Detects outside bars   Returns: Returns true if the current bar is an outside bar barInSession(string, bool) Determines if the current price bar falls inside the specified session   Parameters:      string : sess The session to check      bool : useFilter (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls within the given time session barOutSession(string, bool) Determines if the current price bar falls outside the specified session   Parameters:      string : sess The session to check      bool : useFilter (default=true) Whether or not to actually use this filter   Returns: A boolean - true if the current bar falls outside the given time session dateFilter(int, int) Determines if this bar's time falls within date filter range   Parameters:      int : startTime The UNIX date timestamp to begin searching from      int : endTime the UNIX date timestamp to stop searching from   Returns: A boolean - true if the current bar falls within the given dates dayFilter(bool, bool, bool, bool, bool, bool, bool) Checks if the current bar's day is in the list of given days to analyze   Parameters:      bool : monday Should the script analyze this day? (true/false)      bool : tuesday Should the script analyze this day? (true/false)      bool : wednesday Should the script analyze this day? (true/false)      bool : thursday Should the script analyze this day? (true/false)      bool : friday Should the script analyze this day? (true/false)      bool : saturday Should the script analyze this day? (true/false)      bool : sunday Should the script analyze this day? (true/false)   Returns: A boolean - true if the current bar's day is one of the given days atrFilter() fillCell()
ספריית Pine Script®
מאת ‎Wheeelman‎
2