Mulakan

Cari dalam skrip untuk "摩根标普500指数基金的收益如何"

Realtime 5D Profile [LucF]█  OVERVIEW This indicator displays a realtime profile that can be configured to visualize five dimensions: ​volume, price, time, activity and age. For each price level in a bar or timeframe, you can display total or delta ​volume or ticks. The tick count measures activity on a level. The thickness of each level's line indicates its age, which helps you identify the most recent levels. █  WARNING The indicator only works in real time. Contrary to TradingView's line of volume profile indicators , it does not show anything on historical bars or closed markets, and it cannot display ​volume information if none exists for the data feed the chart is using. A realtime indicator such as this one only displays information accumulated while it is running on a chart. The information it calculates cannot be saved on charts, nor can it be recalculated from historical bars. If you refresh the chart, or the script must re-execute for some reason, as when you change inputs, the accumulated information will be lost. Because "Realtime 5D Profile" requires time to accumulate information on the chart, it will be most useful to traders working on small timeframes who trade only one instrument and do not frequently change their chart's symbol or timeframe. Traders working on higher timeframes or constantly changing charts will be better served by TradingView's ​volume profiles. Before using this indicator, please see the "Limitations" section further down for other important information. █  HOW TO USE IT Load the indicator on an active chart (see here if you don't know how). The default configuration displays:  • A double-sided ​volume profile showing at what price levels activity has occurred.  • The left side shows "down" ​​volume, the right side shows "up" ​volume.  • The value corresponding to each level is displayed.  • The width of lines reflects their relative value.  • The thickness of lines reflects their age. Four thicknesses are used, with the thicker lines being the most recent.  • The total value of down/up values for the profile appears at the top. To understand how to use profiles in your trading, please research the subject. Searches on "volume profile" or "market profile" will yield many useful results. I provide you with tools — I do not teach trading. To understand more about this indicator, read on. If you choose not to do so, please don't ask me to answer questions that are already answered here, nor to make videos; I don't. █  CONCEPTS Delta calculations ​Volume is slotted in up or down slots depending on whether the price of each new chart update is higher or lower than the previous update's price. When price does not move between chart updates, the last known direction is used. In a perfect world, Pine scripts would have access to bid and ask levels, as this would allow us to know for sure if market orders are being filled on upticks (at the ask) or downticks (at the bid). Comparing the price of successive chart updates provides the most precise way to calculate ​volume delta on TradingView, but it is still a compromise. Order books are in constant movement; in some cases, order cancellations can cause sudden movements of both the bid and ask levels such that the next chart update can occur on an uptick at a lower price than the previous one (or vice versa). While this update's ​volume should be slotted in the up slot because a buy market order was filled, it will erroneously be slotted in the down slot because the price of the chart's update is lower than that of the previous one. Luckily, these conditions are relatively rare, so they should not adversely affect calculations. Levels A profile is a tool that displays information organized by price levels. You can select the maximum quantity of levels this indicator displays by using the script's "Levels" input. If the profile's height is small enough for level increments to be less than the symbol's tick size, a smaller quantity of levels is used until the profile's height grows sufficiently to allow your specified quantity of levels to be displayed. The exact position of levels is not tethered to the symbol's tick increments. Activity for one level is that which happens on either side of the level, halfway between its higher or lower levels. The lowest/highest levels in the profile thus appear higher/lower than the profile's low/high limits, which are determined by the lowest/highest points reached by price during the profile's life. Level Values and Length The profile's vertical structure is dynamic. As the profile's height changes with the price range, it is rebalanced and the price points of its levels may be recalculated. When this happens, past updates will be redistributed among the new profile's levels, and the level values may thus change. The new levels where updates are slotted will of course always be near past ones, but keep this fluidity in mind when watching level values evolve. The profile's horizontal structure is also dynamic. The maximum length of level lines is controlled by the "Maximum line length" input value. This maximum length is always used for the largest level value in the profile, and the length of other levels is determined by their value relative to that maximum. Updates vs Ticks Strictly speaking, a tick is the record of a transaction between two parties. On TradingView, these are detected on seconds charts. On other charts, ticks are aggregated to form a chart update . I use the broader "update" term when it names both events. Note that, confusingly, tick is also used to name an instrument's minimal price increment. Volume Quality If you use ​volume, it's important to understand its nature and quality, as it varies with sectors and instruments. My Volume X-ray indicator is one way you can appraise the quality of an instrument's intraday ​volume. █  FEATURES Double-Sided Profiles When you choose one of the first two configuration selections in the "Configuration" field's dropdown menu, you are asking the indicator to display a double-sided profile, i.e., where the down values appear on the left and the up ones on the right. In this mode, the formatting options in the top section of inputs apply to both sides of the profile. Single-Sided Profiles The six other selections down the "Configuration" field's dropdown menu select single-sided profiles, where one side aggregates the up/down values for either ​volume or ticks. In this mode, the formatting options in the top section of inputs apply to the left profile. The ones in the following "Right format" section apply to the right profile. Calculation Mode The "Calculation" input field allows the selection of one of two modes which applies to single-sided profiles only. Values can represent the simple total of ​volume or ticks at each level, or their delta. The mode has no effect when a double-sided profile is used because then, the total is represented by the sum of the left and right sides. Note that when totals are selected, all levels appear in the up color. Age The age of each level is always displayed as one of four line thicknesses. Thicker lines are used for the youngest levels. The age of levels is determined by averaging the times of the updates composing that level. When viewing double-sided profiles, the age of each side is calculated independently, which entails you can have a down level on the left side of the profile appear thinner than its corresponding up side level line on the right side because the updates composing the up side are more recent. When calculating the age of single-sided profiles, the age of the up/down values aggregated to calculate the side are averaged. Since they may be different, the averaged level ages will not be as responsive as when using a double-sided profile configuration, where the age of levels on each side is calculated independently and follows price action more closely. Moreover, when displaying two single-sided profiles (​volume on one side and ticks on the other), the age of both sides will match because they are calculated from the same realtime updates. Profile Resets The profile can reset on timeframes or trend changes. The usual timeframe selections are available, including the chart's, in which case the profile will reset on each new chart bar. One of two trend detection logics can be used: Supertrend or the one used by LazyBear in his Weis Wave indicator . Settings for the trend logics are in the bottommost section of the inputs, where you can also control the display of trend changes and states. Note that the "Timeframe" field's setting also applies to the trend detection mechanism. Whatever the timeframe used for trend detection, its logic will not repaint. Format Formatting a profile for charts is often a challenge for traders, and this one is no exception. Varying zoom factors on your chart and the frequency of profile resets will require different profile formats. You can achieve a reasonable variety of effects by playing with the following input fields:  • "Resets on" controls how frequently new profiles are drawn. Spacing out profiles between bars can help make them more usable.  • "Levels" determines the maximum quantity of levels displayed.  • "Offset" allows you to shift the profile horizontally.  • "Profile size" affects the global size of the profile.  • Another "Size" field provides control over the size of the totals displayed above the profile.  • "Maximum line length" controls how far away from the center of the bar the lines will stretch left and right. Colors The color and brightness of levels and totals always allows you to determine the winning side between up and down values. On double-sided profiles, each side is always of one color, since the left side is down values and the right side, up values. However, the losing side is colored with half its brightness, so the emphasis is put on the winning side. When there is no winner, the toned-down version of each color is used for both sides. Single-sided profiles use the up and down colors in full brightness on the same side. Which one is used reflects the winning side. Candles The indicator can color candle bodies and borders independently. If you choose to do so, you may want to disable the chart's bars by using the eye icon near the symbol's name. Tooltips A tooltip showing the value of each level is available. If they do not appear when hovering over levels, select the indicator by clicking on its chart name. This should get the tooltips working. Data Window As usual, I provide key values in the Data Window, so you can track them. If you compare total realtime volumes for the profile and the built-in "Volume" indicator, you may see variations at some points. They are due to the different mechanisms running each program. In my experience, the values from the built-in don't always update as often as those of the profile, but they eventually catch up. █  LIMITATIONS  • The levels do not appear exactly at the position they are calculated. They are positioned slightly lower than their actual price levels.  • Drawing a 20-level double-sided profile with totals requires 42 labels. The script will only display the last 500 labels,   so the number of levels you choose affects how many past profiles will remain visible.  • The script is quite taxing, which will sometimes make the chart's tab less responsive.  • When you first load the indicator on a chart, it will begin calculating from that moment; it will not take into account prior chart activity.  • If you let the script run long enough when using profile reset criteria that make profiles last for a long time, the script will eventually run out of memory,   as it will be tracking unmanageable amounts of chart updates. I don't know the exact quantity of updates that will cause this,   but the script can handle upwards of 60K updates per profile, which should last 1D except on the most active markets. You can follow the number of updates in the Data Window.  • The indicator's nature makes it more useful at very small timeframes, typically in the sub 15min realm.  • The Weis Wave trend detection used here has nothing to do with how David Weis detects trend changes.   LazyBear's version was a port of a port, so we are a few generations removed from the Weis technique, which uses reversals by a price unit.   I believe the version used here is useful nonetheless because it complements Supertrend rather well. █  NOTES The aggregated view that ​volume and tick profiles calculate for traders is a good example of one of the most useful things software can do for traders: look at things from a methodical, mathematical perspective, and present results in a meaningful way. Profiles are powerful because, if the ​volume data they use is of good enough quality, they tell us what levels are important for traders, regardless of the nature or rationality of the methods traders have used to determine those levels. Profiles don't care whether traders use the news, fundamentals, Fib numbers, ​pivots, or the phases of the moon to find "their" levels. They don't attempt to forecast or explain markets. They show us real stuff containing zero uncertainty, i.e., what HAS happened. I like this. The indicator's "VPAA" chart name represents four of the five dimensions the indicator displays: ​volume, price, activity and age. The time dimension is implied by the fact it's a profile — and I couldn't find a proper place for a "T" in there ) I have not included alerts in the script. I may do so in the future. For the moment, I have no plans to write a profile indicator that works on historical bars. TradingView's ​volume profiles already do that, and they run much faster than Pine versions could, so I don't see the point in spending efforts on a poor ersatz. For Pine Coders  • The script uses labels that draw varying quantities of characters to break the limitation constraining other Pine plots/lines to bar boundaries.  • The code's structure was optimized for performance. When it was feasible, global arrays, "input" and other variables were used from functions,   sacrificing function readability and portability for speed. Code was also repeated in some places, to avoid the overhead of frequent function calls in high-traffic areas.  • I wrote my script using the revised recommendations in the Style Guide from the Pine v5 User Manual. █  THANKS  • To Duyck for his function that sorts an array while keeping it in synch with another array.   The `sortTwoArrays()` function in my script is derived from the Pine Wizard 's code.  • To the one and only Maestro, RicardoSantos , the creative ​volcano who worked hard to write a function to produce fixed-width, figure space-padded numeric values.   A change in design made the function unnecessary in this script, but I am grateful to you nonetheless.  • To midtownskr8guy , another Pine Wizard who is also a wizard with colors. I use the colors from his Pine Color Magic and Chart Theme Simulator constantly.  • Finally, thanks to users of my earlier "Delta Volume" scripts. Comments and discussions with them encouraged me to persist in figuring out how to achieve what this indicator does.
Penunjuk Pine Script®
oleh LucF
105
[AB] Support/Resistance Drawing ToolThis script is designed to help you identify viable support and resistance levels by automatically creating lines that become less transparent when said levels hold. It is based on Donchian Channels created by rounded closes, not by highs and lows. You can use it as an aid to draw your levels manually, or stick exclusively to automatic charting. Available settings are as follows: Source - highly recommended to use Close, but other options are available if you'd like to do some experimentation. Source Rounding - the accuracy of price sampling; higher rounding will make your lines more visible at the expense of precision. It is highly recommended to use decimals. Length (Array) - the overall lookback of the script (length of the array). This value shouldn't be higher than 500 if skip = 2, or 250 if skip = 1. If you'd like to reach further back into the past, I'd recommend switching timeframes instead of increasing this beyond 500. Sampling Skip - how frequently the data is sampled. I wouldn't recommend going beyond 2, especially with the default settings. Transparency Skip - you can think of it as "pencil hardness". The higher the skip, the bigger the imprint of a single level detection will be. Wouldn't recommend going beyond 10. Color R, G, and B - you can use these settings to adjust the color of the lines.
Penunjuk Pine Script®
oleh akalibot1987
5
Baekdoo multi OverSold OverBuy colored CandleHi forks, I'm trader Baekdoosan who trading Equity from South Korea. This Baekdoo multi OverSold OverBuy colored candle will give you the idea of multiple indicators in one shot with colored candle. Those indicators tell us that oversold or overbuy statistically. For the color, you can freely change based on your comfort. For me, in Korea white candle has red color and black candle has blue color. So somewhat confusing for you. Anyway you can easily modify color in the script. Please refer this line. barcolor(open<close and result_pos == 4 ? color.new(color.red, 0) : open<close and result_pos == 3 ? color.new(color.red, 25) : open<close and result_pos == 2 ? color.new(color.red, 50) : open<close and result_pos == 1? color.new(color.red, 75) : na) you can see I put different transparency at color.new() function with color code. Let me divide and conquer to explain for up candle white candle and black candle. 1. White candle with 4 oversold signal case with white candle tells us it is almost reached real bottom and try to rebound. In this case, I put vivid color (no transparency) on the candle. And all 4 signal case, I put text on "OverSold". It will not happen frequently. Then 2 approaches can be made. (a) short term approach You can buy on this time. and you set stop loss with open price. This is mainly aimed for technical rebound. (b) long term approach You can accumulate based on your budget with 5 times dividing. At that day might not be the very bottom but those period will most probably real bottom. You can put more weight on latter buy. Let say, 1 : 1.25 : 1.5 : 1.75 : 2.5. So for example, if you have $8,000 to investigate then, buy $1,000 and then $1,250, $1,500, accordingly. If price rebound then don't adding weight on accumulation but with the first amount that you buy(i.e., $1,000 with above example). With this approach, you will not have much stress and you will get profit well. If this is grand bottom case, then you can HODL this long term. What you needs is stick to the plan. :) with 3 signals the color is less vivid, 2 signals is much less vivid, accordingly. 2. Black candle The approaches are opposite to above. The signal will tells us for 4 overBuy signals, then vivid blue candle will be shown. Our strategy is distribute to sell. Please do not sell in one shot. As Newton said, "I can calculate the motions of the heavenly bodies, but not the madness of the people". Strong buy phase, we don't know how far will it go. But indicators will tell us it is quite overSold situation. So what I can suggest you is sell it 10% to 20% on resistance price, and put 50% of lower than certain support price. Remember, accumulation and distribution will always better than one shot trading if you want to survive long time on this war field. Hope this will help your trading on equity as well as crypto. I didn't try it on futures. Best of luck all of you. Gazua~!
Penunjuk Pine Script®
oleh traderbaekdoosan
[CP]Pivot Boss Candlestick Scanner - No Repainting This indicator is based on the high probability candlestick patterns described in the ’Secrets of a Pivot Boss’ book. The indicator does not suffer from repainting. I have kept this indicator open source, so that you can take this indicator and design a complete trading system around it. Although the patterns have some statistical edge in the markets, blindly using them as Buy/Sell Indicators will certainly result in a heavy loss. I like some of these setups more than others, and I have listed them in the order of my likeness. The first one I like the most, the last one, I like the least. The patterns are universal and work well in both intraday, daily and even larger timeframes. Signals in the example charts are manually marked by, Hammer - profitable short signal Rocket - profitable long signal X - unprofitable long or short signal GENERAL USER INPUTS: These settings exist as the indicator uses ‘Labels’ to mark the patterns and Pine Script limits a maximum of 500 labels on a chart. If you want to go back in the past and check how the indicator was doing, set the Start and End dates both and check the ’Use the date range above to mark the Candlestick Setups?’ option. EXTREME REVERSAL SETUP: This is by far my favorite setup in the lot. Classic Mean Reversion setup. The logic, as explained in the book, goes like this, 1. The first bar of the pattern is about two times larger than the average size of the candles in the lookback period. 2. The body of the first bar of the pattern should encompass more than 50 percent of the bar’s total range, but usually not more than 85 percent. 3. The second bar of the pattern opposes the first. The setup works extremely well in high beta stocks like Vedanta VEDL. Feel free to play with the settings in order to better align this pattern with your favorite stock. Check out the examples below, No indicator is perfect, failed patterns are marked with an X. OUTSIDE REVERSAL SETUP: My second favorite setup, it is quite good at catching intraday trends. Here’s the logic, 1. The engulfing bar of a bullish outside reversal setup has a low that is below the prior bar’s low and a close that is above the prior bar’s high. Reverse the conditions for bearish outside reversal. 2. The engulfing bar is usually 5 to 25 percent larger than the size of the average bar in the lookback period. Settings for this pattern simply reflect these conditions. Feel free to modify them as you wish. The pattern is pretty powerful and will sometimes help you catch literally all the highs and lows of the market, as shown in the examples of Vedanta VEDL and RELIANCE stocks below. As usual, this pattern is not PERFECT either. DOJI REVERSAL SETUP: Doji candles signify market indecision and this pattern tries to profit off these market conditions. Logic: 1. The open and close price of the doji should fall within 10 percent of each other, as measured by the total range of the candlestick. 2. For a bullish doji, the high of the doji candlestick should be below the ten-period simple moving average. Vice-versa for bearish. 3. For a bullish doji setup, one of the two bars following the doji must close above the high of the doji. Vice-versa for bearish. Feel free to modify the settings and optimize according to the stock you are trading. Don't optimize too much :) This pattern works brilliantly well on larger intraday timeframes, like 15m/30m/60m. This pattern also has a higher propensity to give false indications than the two described above. Doji reversal typically helps to catch larger trend reversals. Check out the examples below from RELIANCE and NIFTY charts, Note that the RELIANCE chart below is the same as shown for the Outside Reversal Setup above, notice the confluence of Outside Reversal and Doji Reversal on the 31st August. Confluence of patterns usually increases the probability of success. RELIANCE 15m Chart - Pattern can catch nice trends on higher timeframes NIFTY 15m Chart WICK REVERSAL SETUP: This pattern tries to capture candlesticks with large wick sizes, as they often indicate trend reversal when coupled with significant support and resistance levels. Logic: 1. The body is used to determine the size of the reversal wick. A wick that is between 2.5 to 3.5 times larger than the size of the body is ideal. 2. For a bullish reversal wick to exist, the close of the bar should fall within the top 35 percent of the overall range of the candle. 3. For a bearish reversal wick to exist, the close of the bar should fall within the bottom 35 percent of the overall range of the candle. This pattern must always be coupled with important support resistance levels, else there will be a lot of false signals. The chart below is the same NIFTY chart as above with the Wick Reversal candles marked as well. You can see that there are a lot of false signals, but the price also indicates ’pausing’ at important levels by printing a wick reversal setup. You can use this information to your advantage when riding a trend. FINAL WORDS: Settings for various patterns simply reflect the logic described. You will probably need to tweak and optimize the pattern settings for the stock that you are trading. Higher Beta/Higher Volatility stocks are a great choice for these patterns. Using these patterns at critical support and resistance levels will result in dramatically high accuracy. Be creative and try to develop a proper system around this indicator, with rules for position sizing, stop loss etc. You do not have to trade all the patterns. Even trading just one pattern with a proper system is good enough. DO NOT USE THIS INDICATOR AS A BUY/SELL SYSTEM, YOU WILL LOSE MONEY. Feel free to drop any feedback in the comments section below, or if you have any unique candlestick patterns that you would like me to code.
Penunjuk Pine Script®
oleh pranjalchaubey
28
Relative Strength 3D Indicator [CC]This is a custom indicator of mine loosely based on the work by James Garofallou (Stocks and Commodities Sep 2020 pg 14) and this is meant for medium to long term trend confirmations. The idea behind this indicator is to capture 3 different dimensions of trend strength. The first dimension captures the overall strength of the underlying stock vs the market (in this case the S&P 500). The second dimension captures the overall trend strength by assigning a scoring system so when all faster moving averages are stronger than slower moving averages then it gets the max points. The final dimension is the strength of the overall strength of everything so far. Buy when the indicator line turns green and sell when it turns red. Let me know if there are any other indicators or scripts you would like to see me publish!
Penunjuk Pine Script®
oleh cheatcountry
2
[BCT] Can BTC be predicted or is it purely random?Variance Ratio**This indicator can be applied to the ticker of your choice (not just BTC)** Markets are said to be "efficient". An efficient market is by definition unpredictable - no matter the amount of ML, computation, or indicators thrown at it. In particular, in an efficient market, TA will not be of help. An illustration of efficient markets is the WSJ's longstanding monkey vs. human contest:Blindfolded Monkey Beats Humans With Stock Picks, granted there are several flaws to it. BTC is a relatively new market. New markets are typically highly inefficient (easier to make money) and become more and more efficient over time (harder to make money). How much more efficient is BTC becoming? We apply the Variance Ratio method and apply it to BTC. BACKGROUND ON THE VARIANCE RATIO METHOD Based on 1988 MacKinlay's seminal paper "Stock Market Prices do not Follow a Random Walk", the idea is to exploit a phenomenon called "variance scaling". For those keen on looking into the math, the short version of it is under the assumption of iid (random walk) we have the following: H0: Var(Sum(returns over K bars))=Sum(Var(returns over 1 bar))=k*Var(return over 1 bar) We look to reject or not H0 depending on the observations. In this script, we compare the variance of the (log) returns for the chart selected between: (1) The (average) variance over k bars (call this Vk) (2) The (average) variance over 1 bar (call this V1) H0 simply says that Vk=k*V1 if the stock follows a random walk. We compute the Variance Ratio VR(k)=Variance(returns over k bar)/(Sum(Var(returns over 1 bar)))-1 We then compute the associated Z-score which we chart out for a configurable k number of bars. HOW TO INTERPRET THE CHART The line drawn is the Z-Score for VR(k). It represents the number of standard deviations of VR(k) from 0 - the further out, the less random. - If the line is close / hovers around 0, the ticker appears to follow a random walk (i.e. may not be predictable) - If the line is consistently > 2 or <-2, the ticker likely does not follow a random walk (i.e. may have predictable features) - If the line is positive, it means that the Variance on the k bars is larger than the variance on 1 bar (more variance on longer timeframes) - If the line is negative, it means that the Variance on the k bars is smaller than the variance on 1 bar (more variance on smaller timeframes) USE CASES - Identify timeframes where you won't be able to make money - Identify whether a stock cannot be predicted (forget about TA, indicators etc. -- a random walk is not predictable) - Identify whether a stock is becoming less and less predictable (Z-score amplitude will decrease over time) FEATURES - select the number of K bar to compare vs. 1 bar (default = 16) - ideally a power of 2 but any other number will work. The chart is based off this selection - select the lookback period for the analysis (500 bars by default) - select the source to analyze (default = close, but you may select other inputs to calculate the returns from) - results form the statistical tests on different K's in the table on the right/bottom side of the chart (H0 rejected = not random walk; H0 not rejected = it essentially looks rather random and we can't conclude that it's not a random walk) COMMENTARY ON BTC - It appears BTC's absolute value of the ZScore on the Variance Ratio is declining year after year - corroborating an increasingly efficient market as new participants join. - However, we can still detect a fair amount of potential inefficiency using this simple test. As usual, this is not investment advice. DYOR. With love, 🐵BCT🐵
Penunjuk Pine Script®
oleh THE_REAL_BCT
2
Combo Backtest 123 Reversal & Smart Money Index (SMI) This is combo strategies for get a cumulative signal. First strategy This System was created from the Book "How I Tripled My Money In The Futures Market" by Ulf Jensen, Page 183. This is reverse type of strategies. The strategy buys at market, if close price is higher than the previous close during 2 days and the meaning of 9-days Stochastic Slow Oscillator is lower than 50. The strategy sells at market, if close price is lower than the previous close price during 2 days and the meaning of 9-days Stochastic Fast Oscillator is higher than 50. Second strategy Smart money index (SMI) or smart money flow index is a technical analysis indicator demonstrating investors sentiment. The index was invented and popularized by money manager Don Hays. The indicator is based on intra-day price patterns. The main idea is that the majority of traders (emotional, news-driven) overreact at the beginning of the trading day because of the overnight news and economic data. There is also a lot of buying on market orders and short covering at the opening. Smart, experienced investors start trading closer to the end of the day having the opportunity to evaluate market performance. Therefore, the basic strategy is to bet against the morning price trend and bet with the evening price trend. The SMI may be calculated for many markets and market indices (S&P 500, DJIA, etc.) The SMI sends no clear signal whether the market is bullish or bearish. There are also no fixed absolute or relative readings signaling about the trend. Traders need to look at the SMI dynamics relative to that of the market. If, for example, SMI rises sharply when the market falls, this fact would mean that smart money is buying, and the market is to revert to an uptrend soon. The opposite situation is also true. A rapidly falling SMI during a bullish market means that smart money is selling and that market is to revert to a downtrend soon. The SMI is, therefore, a trend-based indicator. Some analysts use the smart money index to claim that precious metals such as gold will continually maintain value in the future. WARNING: - For purpose educate only - This script to change bars colors.
Strategi Pine Script®
oleh HPotter
15
Momentum Performance This Indicator displays the momentum (performance) of the symbol in percent. You can compare the performance with other symbols. The default benchmarks are the S&P 500, the MSCI World and the FTSE All World EX US. The default length corresponds to one year in the timeframes monthly, weekly and daily. In intraday the default length is 200, but you can also set your own setting. You have also the opportunity to display a average momentum performance of the main symbol.
Penunjuk Pine Script®
oleh brettkind
SPX Intraday Mood IndicatorThe SPX Intraday Mood Indicator tries to gauge the intraday market direction of the S&P 500 (SPX) by focusing on internal market data. Based on the 0DTE Mood Indicator concept. Overall strength/weakness is converted into a directional Mood Percentage which can help with choosing a trade type. Use at your own risk and discretion. Potential trade ideas offer no guarantees. Intraday Charts Only. Turn off extended hours data. Only works on SPX. This first version is untested and I am only sharing it to gather feedback on its accuracy, use at your own risk.
Penunjuk Pine Script®
oleh millerrh
50
5MA_X_LThis is a 5 day moving average crossing long strategy in 10 min. chart, used in short term momentum trading strategy. Momentum trading Strategy: When S&P 500 index is at up trend (or above 60 sma ), buy 10+ stocks in top 20% stock RS ranking at equal weight using this MA5X_L strategy. Change stocks when any stock exited by algorithm. Back test start since 2020/7/1, each long entry for condition 1 is $30000, condition 2 is $20000, with max of 2 long positions. Setup: 10 minutes chart Buy condition 1) 3 wma cross up 195 wma (5day) 2) 3wma > 78wma > 195wma UP Trend Arrangement (UTA) Exit condition 1) 3 wma cross under 195 wma 2) position profit > 20% and 3 wma cross under 6 ATRs line (green)
Strategi Pine Script®
oleh FinTasticTrading
Stochastic Optimized Trend Tracker *Strategy*Stochastic OTT is Anıl Özekşi's latest derived version of Optimized Trend Tracker on Stochastic Oscillator. He tried to solve the fake signals of Stochastic Oscillator by adopting OTT on the indicator. He advised users to set the stochastic smoothing parameters to 500 and 200 on his latest video about SOTT. He personally uses 1 min charts on stock market so the parameters of the indicator might have to be optimized for other time frames nad markets. He exaggerated the Stochastic to 1000's to have better signals of percent values of OTT . Also hes used VIDYA in both calculations of OTT and Stochastic smoothing. Said, Kıvanç Özbilgiç. I just made a Strategy version of the script so that we lads can backtest it. The codes for that are yet again from Kıvanç Özbilgiç :) I just copy-pasted a few and did some adjustments. Hope you enjoy! #betonyetmez
Strategi Pine Script®
oleh lucidreamer15
11
Stochastic OTTStochastic OTT is Anıl Özekşi's latest derived version of Optimized Trend Tracker on Stochastic Oscillator. You might like to view the original version of the indicator if you don't know about OTT yet: He tried to solve the fake signals of Stochastic Oscillator by adopting OTT on the indicator. He advised users to set the stochastic smoothing parameters to 500 and 200 on his latest video about SOTT. He personally uses 1 min charts on stock market so the parameters of the indicator might have to be optimized for other time frames nad markets. He exaggerated the Stochastic to 1000's to have better signals of percent values of OTT. Also hes used VIDYA in both calculations of OTT and Stochastic smoothing. Hope you'll enjoy the SOTT in your profitable trades. Kıvanç
Penunjuk Pine Script®
oleh KivancOzbilgic
49
stop out or margin call price levelsAbstract This script finds the potential stop out or margin call price levels without considering timeframe. This script computes stop out or margin call price levels that over leveraged positions buy cheap enough. You can use this indicator to follow stop hunters. Introduction Stop hunting exists because of benefit conflict. When most of retails traders are in the correct direction, big banks do not want to buy more expensive then retail traders. Therefore, Big banks create sell pressure to make retail traders misunderstand their trade decisions are wrong. When retail traders decide to cut loss, it is time big banks buy cheaper. Many courses recommend average true range as a stop loss reference. However, in different timeframe, average true ranges are different. Therefore, we need to have a method to measure potential stop hunting levels which is not relative to timeframe. There is a method because there are observable levels where over leveraged positions must cut loss. For example, for a 100 leverage position, its margin call level is 0.005, so 0.005 drawdown is a potential stop hunting level. Computing For buy potential stop out or margin call price level = low * ( 1 - ratio ) For sell potential stop out or margin call price level = high * ( 1 + ratio ) Parameters There are 4 levels available for adjusting. The default values are : (1) 0.001 : 500 leverage , 50% margin call (2) 0.0025 : 200 leverage , 50% margin call (3) 0.005 : 100 leverage , 50% margin call (4) 0.010 : 50 leverage , 50% margin call Usage (1) Find an oversold price level. If you don't want to use an another indicator, you can use previous low. (2) Memorize their stop out or margin call price levels of that level. (2) Consider buy near those levels. (3) If there are quick price rejection near those levels, better entry opportunities. (4) Take profit and stop loss : you decide. Conclusion This script can find potential stop out or margin call price levels that over leveraged positions buy cheap enough. If you are bored, you can consider find 100 signals you are interested in and share your observation. Reference Brokers, leverage and margin call threshold
Penunjuk Pine Script®
oleh clocks156t174
1
Main MAs and EMAs multi-timeframe for supportObjective is to map out different multi-timeframe support/resistance , all at once. Includes weekly, daily and 4H EMAs and MAs, as per the follow (allowing customization) WEEKLY (in pink/purple variations): - 13 EMA - 21 EMA - 34 EMA - 50 M.A DAILY (in green variations): - 21 EMA - 50 EMA - 120 M.A. - 200 M.A. 4H (in yellow/golden colors): - 400 EMA - 500 EMA - 675 EMA - 715 EMA - 920 EMA - 1150 EMA Notes: - Quite useful to all types of assets; crypto, commodities , stocks, etc... - Ideally not to be visible all the time, as it can "pollute" the charts. But very helpful in moments of great volatility
Penunjuk Pine Script®
oleh Ferafer
Pinescript - Common Label & Line Array Functions Library by RRBPinescript - Common Label & Line Array Functions Library by RagingRocketBull 2021 Version 1.0 This script provides a library of common array functions for arrays of label and line objects with live testing of all functions. Using this library you can easily create, update, delete, join label/line object arrays, and get/set properties of individual label/line object array items. You can find the full list of supported label/line array functions below. There are several libraries: - Common String Functions Library - Standard Array Functions Library - Common Fixed Type Array Functions Library - Common Label & Line Array Functions Library - Common Variable Type Array Functions Library Features: - 30 array functions in categories create/update/delete/join/get/set with support for both label/line objects (45+ including all implementations) - Create, Update label/line object arrays from list/array params - GET/SET properties of individual label/line array items by index - Join label/line objects/arrays into a single string for output - Supports User Input of x,y coords of 5 different types: abs/rel/rel%/inc/inc% list/array, auto transforms x,y input into list/array based on type, base and xloc, translates rel into abs bar indexes - Supports User Input of lists with shortened names of string properties, auto expands all standard string properties to their full names for use in functions - Live Output for all/selected functions based on User Input. Test any function for possible errors you may encounter before using in script. - Output filters: hide all excluded and show only allowed functions using a list of function names - Output Panel customization options: set custom style, color, text size, and line spacing Usage: - select create function - create label/line arrays from lists or arrays (optional). Doesn't affect the update functions. The only change in output should be function name regardless of the selected implementation. - specify num_objects for both label/line arrays (default is 7) - specify common anchor point settings x,y base/type for both label/line arrays and GET/SET items in Common Settings - fill lists with items to use as inputs for create label/line array functions in Create Label/Line Arrays section - specify label/line array item index and properties to SET in corresponding sections - select label/line SET function to see the changes applied live Code Structure: - translate x,y depending on x,y type, base and xloc as specified in UI (required for all functions) - expand all shortened standard property names to full names (required for create/update* from arrays and set* functions, not needed for create/update* from lists) to prevent errors in label.new and line.new - create param arrays from string lists (required for create/update* from arrays and set* functions, not needed for create/update* from lists) - create label/line array from string lists (property names are auto expanded) or param arrays (requires already expanded properties) - update entire label/line array or - get/set label/line array item properties by index Transforming/Expanding Input values: - for this script to work on any chart regardless of price/scale, all x*,y* are specified as % increase relative to x0,y0 base levels by default, but user can enter abs x,price values specific for that chart if necessary. - all lists can be empty, contain 1 or several items, have the same/different lengths. Array Length = min(min(len(list*)), mum_objects) is used to create label/line objects. Missing list items are replaced with default property values. - when a list contains only 1 item it is duplicated (label name/tooltip is also auto incremented) to match the calculated Array Length - since this script processes user input, all x,y values must be translated to abs bar indexes before passing them to functions. Your script may provide all data internally and doesn't require this step. - at first int x, float y arrays are created from user string lists, transformed as described below and returned as x,y arrays. - translated x,y arrays can then be passed to create from arrays function or can be converted back to x,y string lists for the create from lists function if necessary. - all translation logic is separated from create/update/set functions for the following reasons: - to avoid redundant code/dependency on ext functions/reduce local scopes and to be able to translate everything only once in one place - should be faster - to simplify internal logic of all functions - because your script may provide all data internally without user input and won't need the translation step - there are 5 types available for both x,y: abs, rel, rel%, inc, inc%. In addition to that, x can be: bar index or time, y is always price. - abs - absolute bar index/time from start bar0 (x) or price (y) from 0, is >= 0 - rel - relative bar index/time from cur bar n (x) or price from y0 base level, is >= 0 - rel% - relative % increase of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - inc - relative increment (step) for each new level of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - inc% - relative % increment (% step) for each new level of bar index/time (x) or price (y) from corresponding base level (x0 or y0), can be <=> 0 - x base level >= 0 - y base level can be 0 (empty) or open, close, high, low of cur bar - single item x1_list = "50" translates into: - for x type abs: "50, 50, 50 ..." num_objects times regardless of xloc => x = 50 - for x type rel: "50, 50, 50 ... " num_objects times => x = x_base + 50 - for x type rel%: "50%, 50%, 50% ... " num_objects times => x_base * (1 + 0.5) - for x type inc: "0, 50, 100 ... " num_objects times => x_base + 50 * i - for x type inc%: "0%, 50%, 100% ... " num_objects times => x_base * (1 + 0.5 * i) - when xloc = xloc.bar_index each rel*/inc* value in the above list is then subtracted from n: n - x to convert rel to abs bar index, values of abs type are not affected - x1_list = "0, 50, 100, ..." of type rel is the same as "50" of type inc - x1_list = "50, 50, 50, ..." of type abs/rel/rel% produces a sequence of the same values and can be shortened to just "50" - single item y1_list = "2" translates into (ragardless of yloc): - for y type abs: "2, 2, 2 ..." num_objects times => y = 2 - for y type rel: "2, 2, 2 ... " num_objects times => y = y_base + 2 - for y type rel%: "2%, 2%, 2% ... " num_objects times => y = y_base * (1 + 0.02) - for y type inc: "0, 2, 4 ... " num_objects times => y = y_base + 2 * i - for y type inc%: "0%, 2%, 4% ... " num_objects times => y = y_base * (1 + 0.02 * i) - when yloc != yloc.price all calculated values above are simply ignored - y1_list = "0, 2, 4" of type rel% is the same as "2" with type inc% - y1_list = "2, 2, 2" of type abs/rel/rel% produces a sequence of the same values and can be shortened to just "2" - you can enter shortened property names in lists. To lookup supported shortened names use corresponding dropdowns in Set Label/Line Array Item Properties sections - all shortened standard property names must be expanded to full names (required for create/update* from arrays and set* functions, not needed for create/update* from lists) to prevent errors in label.new and line.new - examples of shortened property names that can be used in lists: bar_index, large, solid, label_right, white, left, left, price - expanded to their corresponding full names: xloc.bar_index, size.large, line.style_solid, label.style_label_right, color.white, text.align_left, extend.left, yloc.price - all expanding logic is separated from create/update* from arrays and set* functions for the same reasons as above, and because param arrays already have different types, implying the use of final values. - all expanding logic is included in the create/update* from lists functions because it seemed more natural to process string lists from user input directly inside the function, since they are already strings. Creating Label/Line Objects: - use study max_lines_count and max_labels_count params to increase the max number of label/line objects to 500 (+3) if necessary. Default number of label/line objects is 50 (+3) - all functions use standard param sequence from methods in reference, except style always comes before colors. - standard label/line.get* functions only return a few properties, you can't read style, color, width etc. - label.new(na, na, "") will still create a label with x = n-301, y = NaN, text = "" because max default scope for a var is 300 bars back. - there are 2 types of color na, label color requires color(na) instead of color_na to prevent error. text_color and line_color can be color_na - for line to be visible both x1, x2 ends must be visible on screen, also when y1 == y2 => abs(x1 - x2) >= 2 bars => line is visible - xloc.bar_index line uses abs x1, x2 indexes and can only be within 0 and n ends, where n <= 5000 bars (free accounts) or 10000 bars (paid accounts) limit, can't be plotted into the future - xloc.bar_time line uses abs x1, x2 times, can't go past bar0 time but can continue past cur bar time into the future, doesn't have a length limit in bars. - xloc.bar_time line with length = exact number of bars can be plotted only within bar0 and cur bar, can't be plotted into the future reliably because of future gaps due to sessions on some charts - xloc.bar_index line can't be created on bar 0 with fixed length value because there's only 1 bar of horiz length - it can be created on cur bar using fixed length x < n <= 5000 or - created on bar0 using na and then assigned final x* values on cur bar using set_x* - created on bar0 using n - fixed_length x and then updated on cur bar using set_x*, where n <= 5000 - default orientation of lines (for style_arrow* and extend) is from left to right (from bar 50 to bar 0), it reverses when x1 and x2 are swapped - price is a function, not a line object property Variable Type Arrays: - you can't create an if/function that returns var type value/array - compiler uses strict types and doesn't allow that - however you can assign array of any type to another array of any type creating an arr pointer of invalid type that must be reassigned to a matching array type before used in any expression to prevent error - create_any_array2 uses this loophole to return an int_arr pointer of a var type array - this works for all array types defined with/without var keyword and doesn't work for string arrays defined with var keyword for some reason - you can't do this with var type vars, only var type arrays because arrays are pointers passed by reference, while vars are actual values passed by value. - you can only pass a var type value/array param to a function if all functions inside support every type - otherwise error - alternatively values of every type must be passed simultaneously and processed separately by corresponding if branches/functions supporting these particular types returning a common single type result - get_var_types solves this problem by generating a list of dummy values of every possible type including the source type, tricking the compiler into allowing a single valid branch to execute without error, while ignoring all dummy results Notes: - uses Pinescript v3 Compatibility Framework - uses Common String Functions Library, Common Fixed Type Array Functions Library, Common Variable Type Array Functions Library - has to be a separate script to reduce the number of local scopes/compiled file size, can't be merged with another library. - lets you live test all label/line array functions for errors. If you see an error - change params in UI - if you see "Loop too long" error - hide/unhide or reattach the script - if you see "Chart references too many candles" error - change x type or value between abs/rel*. This can happen on charts with 5000+ bars when a rel bar index x is passed to label.new or line.new instead of abs bar index n - x - create/update_label/line_array* use string lists, while create/update_label/line_array_from_arrays* use array params to create label/line arrays. "from_lists" is dropped to shorten the names of the most commonly used functions. - create_label/line_array2,4 are preferable, 5,6 are listed for pure demonstration purposes only - don't use them, they don't improve anything but dramatically increase local scopes/compiled file size - for this reason you would mainly be using create/update_label/line_array2,4 for list params or create/update_label/line_array_from_arrays2 for array params - all update functions are executed after each create as proof of work and can be disabled. Only create functions are required. Use update functions when necessary - when list/array params are changed by your script. - both lists and array item properties use the same x,y_type, x,y_base from common settings - doesn't use pagination, a single str contains all output - why is this so complicated? What are all these functions for? - this script merges standard label/line object methods with standard array functions to create a powerful set of label/line object array functions to simplify manipulation of these arrays. - this library also extends the functionality of Common Variable Type Array Functions Library providing support for label/line types in var type array functions (any_to_str6, join_any_array5) - creating arrays from either lists or arrays adds a level of flexibility that comes with complexity. It's very likely that in your script you'd have to deal with both string lists as input, and arrays internally, once everything is converted. - processing user input, allowing customization and targeting for any chart adds a whole new layer of complexity, all inputs must be translated and expanded before used in functions. - different function implementations can increase/reduce local scopes and compiled file size. Select a version that best suits your needs. Creating complex scripts often requires rewriting your code multiple times to fit the limits, every line matters. P.S. Don't rely too much on labels, for too often they are fables. List of functions*: * - functions from other libraries are not listed 1. Join Functions Labels - join_label_object(label_, d1, d2) - join_label_array(arr, d1, d2) - join_label_array2(arr, d1, d2, d3) Lines - join_line_object(line_, d1, d2) - join_line_array(arr, d1, d2) - join_line_array2(arr, d1, d2, d3) Any Type - any_to_str6(arr, index, type) - join_any_array4(arr, d1, d2, type) - join_any_array5(arr, d, type) 2. GET/SET Functions Labels - label_array_get_text(arr, index) - label_array_get_xy(arr, index) - label_array_get_fields(arr, index) - label_array_set_text(arr, index, str) - label_array_set_xy(arr, index, x, y) - label_array_set_fields(arr, index, x, y, str) - label_array_set_all_fields(arr, index, x, y, str, xloc, yloc, label_style, label_color, text_color, text_size, text_align, tooltip) - label_array_set_all_fields2(arr, index, x, y, str, xloc, yloc, label_style, label_color, text_color, text_size, text_align, tooltip) Lines - line_array_get_price(arr, index, bar) - line_array_get_xy(arr, index) - line_array_get_fields(arr, index) - line_array_set_text(arr, index, width) - line_array_set_xy(arr, index, x1, y1, x2, y2) - line_array_set_fields(arr, index, x1, y1, x2, y2, width) - line_array_set_all_fields(arr, index, x1, y1, x2, y2, xloc, extend, line_style, line_color, width) - line_array_set_all_fields2(arr, index, x1, y1, x2, y2, xloc, extend, line_style, line_color, width) 3. Create/Update/Delete Functions Labels - delete_label_array(label_arr) - create_label_array(list1, list2, list3, list4, list5, d) - create_label_array2(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array3(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array4(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array5(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array6(x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - update_label_array2(label_arr, x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - update_label_array4(label_arr, x_list, y_list, str_list, xloc_list, yloc_list, style_list, color1_list, color2_list, size_list, align_list, tooltip_list, d) - create_label_array_from_arrays2(x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) - create_label_array_from_arrays4(x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) - update_label_array_from_arrays2(label_arr, x_arr, y_arr, str_arr, xloc_arr, yloc_arr, style_arr, color1_arr, color2_arr, size_arr, align_arr, tooltip_arr, d) Lines - delete_line_array(line_arr) - create_line_array(list1, list2, list3, list4, list5, list6, d) - create_line_array2(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array3(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array4(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array5(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array6(x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - update_line_array2(line_arr, x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - update_line_array4(line_arr, x1_list, y1_list, x2_list, y2_list, xloc_list, extend_list, style_list, color_list, width_list, d) - create_line_array_from_arrays2(x1_arr, y1_arr, x2_arr, y2_arr, xloc_arr, extend_arr, style_arr, color_arr, width_arr, d) - update_line_array_from_arrays2(line_arr, x1_arr, y1_arr, x2_arr, y2_arr, xloc_arr, extend_arr, style_arr, color_arr, width_arr, d)
Penunjuk Pine Script®
oleh RagingRocketBull
13
Bollinger DCA v1Simple "benchmark" strategy for ETFs, Stocks and Crypto! Super-easy to implement for beginners, a BTD (buy-the-dip) strategy means that you buy a fixed amount of an ETF / Stock / Crypto every time it falls. For instance, to BTD the S&P 500 ( SPY ), you could purchase $500 USD each time the price falls. Assuming the macro-economic conditions of the underlying country remain favourable, BTD strategies will result in capital gains over a period of many years, e.g. 10 years. Recommended Chart Settings: Asset Class: ETF / Stocks / Crypto Time Frame: H1 (Hourly) / D1 (Daily) / W1 (Weekly) / M1 (Monthly) Necessary ETF Macro Conditions: 1. Country must have healthy demographics, good ratio of young > old 2. Country population must be increasing 3. Country must be experiencing price-inflation Necessary Stock Conditions: 1. Growing revenue 2. Growing net income 3. Consistent net margins 4. Higher gross/net profit margin compared to its peers in the industry 5. Growing share holders equity 6. Current ratios > 1 7. Debt to equity ratio (compare to peers ) 8. Debt servicing ratio < 30% 9. Wide economic moat 10. Products and services used daily, and will stay relevant for at least 1 decade Necessary Crypto Conditions: 1. Honest founders 2. Competent technical co-founders 3. Fair or non-existent pre-mine 4. Solid marketing and PR 5. Legitimate use-cases / adoption Default Robot Settings: Contribution (USD): $500 When: Dips below lower Bollinger Band *Robot buys $500 worth of ETF , Stock, Crypto, every time price falls below the lower Bollinger Band *Equity curve can be seen from the bottom panel* Risk Warning: This strategy is low-risk, however it assumes you have a long time horizon of at least 5 to 10 years. The longer your holding-period, the better your returns. The only thing the user has to keep-in-mind are the macro-economic conditions as stated above. If unsure, please stick to ETFs rather than buying individual stocks or cryptocurrencies.
Strategi Pine Script®
oleh UnknownUnicorn1373033
1
Fixed price Stop Loss [Takazudo]This strategy is a demo for fixed price stop loss. This strategy enables you to specify fixed price stop loss. Let's say your deposit is USD. When you trade EURCAD, you need to specify the quantity for trade. Here comes three chances for trade. A: SL pips: 500 B: SL pips: 200 C: SL pips: 100 In these trade, the risk is different for each. ABC risk ratio is 5:2:1. And, you cannot know how much to lose if the price hits the stop loss. This is a huge problem. With this strategy, You can specify the fixed risk price for each trade. If you specify 100 USD for the risk, this strategy calculates how much quantity to buy or sell for each entry. In the case above, this strategy guides you how much quantity to buy or sell like below. A: 2,000 qty (SL: 500pips) B: 5,000 qty (SL: 200pips) C: 10,000 qty (SL: 100pips) If you make entries with those quantity and the price hits the stop loss, You will lose the money like below. A: 100 USD B: 100 USD C: 100 USD This is what this script does. Fixed price SL. I tested this caliculation for OANDA's main 28 currency pairs forex listed below. AUDUSD, EURUSD, GBPUSD, NZDUSD, USDCAD, USDCHF, USDJPY, AUDCAD, AUDCHF, AUDJPY, AUDNZD, CADCHF, CADJPY, CHFJPY, EURAUD, EURCAD, EURCHF, EURGBP, EURJPY, EURNZD, GBPAUD, GBPCAD, GBPCHF, GBPJPY, GBPNZD, NZDCAD, NZDCHF, NZDJPY I may add more pairs later. Note: The entry strategy in this script is not intented to win. Check the result. Be careful.
Strategi Pine Script®
oleh Takazudo