Mulakan

Cari dalam skrip untuk "分享回复展开144条回复瑞丰天"

Moving Average ChannelIntended for use on BTC long term (BNC:BLX Weekly) with Logarithmic charts only As Bitcoin is adopted, it moves through market cycles. These are created by periods where market participants are over-excited causing the price to over-extend, and periods where they are overly pessimistic where the price over-contracts. Identifying and understanding these periods can be beneficial to the long term investor. This long term investment tool is a simple and effective way to highlight those periods. Buying Bitcoin when the price drops below the green line has historically generated outsized returns. Selling Bitcoin when price goes above the red line has been historically effective for taking profits. NOTE: 144 Week = 2¾ Years. 104 Weeks = 2 Years. Originally created by Philip Swift
Penunjuk Pine Script®
oleh jaggedsoft
3
Slow Volume Oscillator Indicator - Just a Better Way To TradeThis script is nothing new. However, I feel that traders do not know the full potential it can provide if they just increase the lookback periods. Tradingview's default Vol Osc uses a fast setting of 5 and a slow setting of 10. It just paints pointless scribbling. Slow all your indicators down and wake up to a whole new world of Technical Analysis. To create consistency with variables I typically use Fib numbers for lookback periods. (3,5,8,13,21,34,55,89,144,233,377,610,987) As noted in chart. An increase in volume can be either bullish or bearish. It's up to you to decide which way price action will move. If you use with other indicators you can create more confirmations. More confirmations = peace of mind My favorite indicators are (Detrended Price Oscillator, Momentum, MACD, Chaikin Money Flow, Ultimate Oscillator, and this Volume Oscillator) Here is just one example of MACD strategy indicator that can be used with this Vol Oscillator
Penunjuk Pine Script®
oleh Craig_Claussen
4
MACD Multi-MA StrategyThis script applies the average of each major MA (SMA, RMA, EMA, WVMA, WMA) to the MACD formula. The logic is simple. When all 5 MA's are in agreement in direction, then then script will notify users of change. I posted this as a strategy to help show how logic does in back test. If you use my simple yet effective solution to find take profit locations, you can blow this back testing out of the water!!! To set alerts simply turn script into study //@version=2 study(title="MACD Multi-MA Study", overlay=false) src = close len1 = input(8, "FAST LOOKBACK") len2 = input(144, "SLOW LOOKBACK") ///////////////////////////////////////////// length = len2-len1 ma = vwma(src, length) plot(ma, title="VWMA", color=lime) length1 = len2-len1 ma1 = rma(src, length1) plot(ma1, title="RMA", color=purple) length2 = len2-len1 ma2 = sma(src, length2) plot(ma2, title="SMA", color=red) length3 = len2-len1 ma3 = wma(src, length3) plot(ma3, title="WMA", color=orange) length4 = len2-len1 ma4 = ema(src, length4) plot(ma4, title="EMA", color=yellow) long = ma > ma and ma1 > ma1 and ma2 > ma2 and ma3 > ma3 and ma4 > ma4 short = ma < ma and ma1 < ma1 and ma2 < ma2 and ma3 < ma3 and ma4 < ma4 alertcondition(long == true, title='MACD LONG SIGNAL', message='MACD LONG!') alertcondition(short == true, title='MACD SHORT SIGNAL', message='MACD SHORT!')
Strategi Pine Script®
oleh Craig_Claussen
13
Multi SMA EMA WMA HMA BB (4x5 MAs Bollinger Bands) Adv MTF - RRBMulti SMA EMA WMA HMA 4x5 Moving Averages with Bollinger Bands Advanced MTF by RagingRocketBull 2019 Version 1.0 This indicator shows multiple MAs of any type SMA EMA WMA HMA etc with BB and MTF support, can show MAs as dynamically moving levels. There are 4 MA groups + 1 BB group, a total of 4 TFs * 5 MAs = 20 MAs. You can assign any type/timeframe combo to a group, for example: - EMAs 12,26,50,100,200 x H1, H4, D1, W1 (4 TFs x 5 MAs x 1 type) - EMAs 8,10,13,21,30,50,55,100,200,400 x M15, H1 (2 TFs x 10 MAs x 1 type) - D1 EMAs and SMAs 8,10,12,26,30,50,55,100,200,400 (1 TF x 10 MAs x 2 types) - H1 WMAs 7,77,89,167,231; H4 HMAs 12,26,50,100,200; D1 EMAs 89,144,169,233,377; W1 SMAs 12,26,50,100,200 (4 TFs x 5 MAs x 4 types) - +1 extra MA type/timeframe for BB There are several versions: Simple, MTF, Pro MTF, Advanced MTF and Ultimate MTF. This is the Advanced MTF version. The Differences are listed below. All versions have BB - Simple: you have 2 groups of MAs that can be assigned any type (5+5) - MTF: +2 custom Timeframes for each group (2x5 MTF) +1 TF for BB, TF XY smoothing - Pro MTF: 4 custom Timeframes for each group (4x3 MTF), 1 TF for BB, MA levels and show max bars back options - Advanced MTF: +2 extra MAs/group (4x5 MTF), custom Ticker/Symbols, Timeframe <>= filter, Remove Duplicates Option - Ultimate MTF: +individual settings for each MA, custom Ticker/Symbols Features: - 4x5 = 20 MAs of any type - 4x MTF groups with XY step line smoothing - +1 extra TF/type for BB MAs - 4x5 = 20 MA levels with adjustable group offsets, indents and shift - supports any existing type of MA: SMA, EMA, WMA, Hull Moving Average (HMA) - custom tickers/symbols for each group - you can compare MAs of the same symbol across exchanges - show max bars back option - show/hide both groups of MAs/levels/BB and individual MAs - timeframe filter: show only MAs/Levels with TFs <>= Current TF - hide MAs/Levels with duplicate TFs - support for custom TFs that are not available in free accounts: 2D, 3D etc - support for timeframes in H: H, 2H, 4H etc Notes: - Uses timeframe textbox instead of input resolution dropdown to allow for 240 120 and other custom TFs - Uses symbol textbox instead of input symbol to avoid establishing multiple dummy security connections to the current ticker - otherwise empty symbols will prevent script from running - Possible reasons for missing MAs on a chart: - there may not be enough bars in history to start plotting it. For example, W1 EMA200 needs at least 200 bars on a weekly chart. - price << default Y smoothing step 5. For charts with low/fractional prices (i.e. 0.00002 << 5) adjust X Y smoothing as needed (set Y = 0.0000001) or disable it completely (set X,Y to 0,0) - TradingView Replay Mode UI and Pinescript security calls are limited to TFs >= D (D,2D,W,MN...) for free accounts - attempting to plot any TF < D1 in Replay Mode will only result in straight lines, but all TFs will work properly in history and real-time modes. This is not a bug. - Max Bars Back (num_bars) is limited to 5000 for free accounts (10000 for paid), will show error when exceeded. To plot on all available history set to 0 (default) - Slow load/redraw times. This indicator becomes slower, its UI less responsive when: - Pinescript Node.js graphics library is too slow and inefficient at plotting bars/objects in a browser window. Code optimization doesn't help much - the graphics engine is the main reason for general slowness. - the chart has a long history (10000+ bars) in a browser's cache (you have scrolled back a couple of screens in a max zoom mode). - Reload the page/Load a fresh chart and then apply the indicator or - Switch to another Timeframe (old TF history will still remain in cache and that TF will be slow) - in max possible zoom mode around 4500 bars can fit on 1 screen - this also slows down responsiveness. Reset Zoom level - initial load and redraw times after a param change in UI also depend on TF. For example: D1/W1 - 2 sec, H1/H4 - 5-6 sec, M30 - 10 sec, M15/M5 - 4 sec, M1 - 5 sec. M30 usually has the longest history (up to 16000 bars) and W1 - the shortest (1000 bars). - when indicator uses more MAs (plots) and timeframes it will redraw slower. Seems that up to 5 Timeframes is acceptable, but 6+ Timeframes can become very slow. - show_last=last_bars plot limit doesn't affect load/redraw times, so it was removed from MA plot - Max Bars Back (num_bars) default/custom set UI value doesn't seem to affect load/redraw times - In max zoom mode all dynamic levels disappear (they behave like text) 1. based on 3EmaBB, uses plot*, barssince and security functions 2. you can't set certain constants from input due to Pinescript limitations - change the code as needed, recompile and use as a private version 3. Levels = trackprice implementation 4. Show Max Bars Back = show_last implementation 5. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params 6. Smoothing is applied by default for visual aesthetics on MTF. To use exact ma mtf values (lines with stair stepping) - disable it Good Luck! You can explore, modify/reuse the code to build your own indicators.
Penunjuk Pine Script®
oleh RagingRocketBull
3
The Scale Of Sacred SoundsBased on the Sacred Sound Scale How to use it: This indicator is designed to capture the inferred behavior of traders and investors by using two groups of averages. Meant for longer trades and trend indicator. Used on any timescale as needed. Can trade on long or short where the slow MA crosses fast Ma or where the Slow MA compresses and flips open again. Follow the trend to the end - pot of gold at the end of the rainbow :-) References: Based on Daryl Guppy GMMA and www.guppytraders.com Read more at: whatmusicreallyis.com There is one tuning in which the frequencies 432, 528, 424 and 440 Hz can peacefully coexist. The scale has 32+1 pure harmonic tones and the reference frequency of 256 Hz. It comes from the Natural Ascending Series of Harmonics 32 to 64 of the 8 Hz Fundamental Tone, and represents its 6th double. I call this tuning The Scale of Sacred Sounds. Representation using ancient Sumerian/Babylonian/Vedic math: 32; 33; 34; 35; 36; 37; 38; 39; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 60; 61; 62; 63; 64 Representation using musical ratios: 1/1; 33/32; 17/16; 35/32; 9/8; 37/32; 19/16; 39/32; 5/4; 41/32; 21/16; 43/32; 11/8; 45/32; 23/16; 47/32; 3/2; 49/32; 25/16; 51/32; 13/8; 53/32; 27/16; 55/32; 7/4; 57/32; 29/16; 59/32; 15/8; 61/32; 31/16; 63/32; 2/1 The math for deriving one of the above series from the other is simple. Divide all numbers from the ancient series by the first, then simplify the fractions. Conversely, the series of ratios can be turned into the series of integers by calculating their least common denominator (the smallest whole number that is a multiple of all numbers under the fraction bar) and discarding it. Logarithmic representation using musical constants (definition given further down): 0,000; 30,772; 60,625; 89,612; 117,783; 145,182; 171,850; 197,826; 223,144; 247,836; 271,934; 295,464; 318,454; 340,927; 362,905; 384,412; 405,465; 426,084; 446,287; 466,090; 485,508; 504,556; 523,248; 541,597; 559,616; 577,315; 594,707; 611,802; 628,609; 645,138; 661,398; 677,399; 693,147
Penunjuk Pine Script®
oleh riseofthecapitalist
7
Multi SMA EMA WMA HMA BB (4x3 MAs Bollinger Bands) Pro MTF - RRBMulti SMA EMA WMA HMA 4x3 Moving Averages with Bollinger Bands Pro MTF by RagingRocketBull 2018 Version 1.0 This indicator shows multiple MAs of any type SMA EMA WMA HMA etc with BB and MTF support, can show MAs as dynamically moving levels. There are 4 MA groups + 1 BB group. You can assign any type/timeframe combo to a group, for example: - EMAs 50,100,200 x H1, H4, D1, W1 (4 TFs x 3 MAs x 1 type) - EMAs 8,13,21,55,100,200 x M15, H1 (2 TFs x 6 MAs x 1 type) - D1 EMAs and SMAs 12,26,50,100,200,400 (1 TF x 6 MAs x 2 types) - H1 WMAs 7,77,231; H4 HMAs 50,100,200; D1 EMAs 144,169,233; W1 SMAs 50,100,200 (4 TFs x 3 MAs x 4 types) - +1 extra MA type/timeframe for BB compile time: 25-30 sec full redraw time after parameter change in UI: 3 sec There are several versions: Simple, MTF, Pro MTF, Advanced MTF and Ultimate MTF. This is the Pro MTF version. The Differences are listed below. All versions have BB - Simple: you have 2 groups of MAs that can be assigned any type (5+5) - MTF: +2 custom Timeframes for each group (2x5 MTF) - Pro MTF: +4 custom Timeframes for each group (4x3 MTF), MA levels and show max bars back options - Advanced MTF: +2 extra MAs/group (4x5 MTF), custom Ticker/Symbol, backreferences for type, TF and MA lengths in UI - Ultimate MTF: +individual settings for each MA, custom Ticker/Symbols Features: - 4x3 = 12 MAs of any type including Hull Moving Average (HMA) - 4x MTF groups with step line smoothing - BB +1 extra TF/type for BB MAs - 12 MA levels with adjustable group offsets, indents and shift - show max bars back - you can show/hide both groups of MAs/levels and individual MAs Notes: 1. based on 3EmaBB, uses plot*, barssince and security functions 2. you can't set certain constants from input due to Pinescript limitations - change the code as needed, recompile and use as a private version 3. Levels = trackprice implementation 4. Show Max Bars Back = show_last implementation 5. uses timeframe textbox instead of input resolution to allow for 120 240 and other custom TFs. Also supports TFs in hours: 2H or H2 6. swma has a fixed length = 4, alma and linreg have additional offset and smoothing params 7. Smoothing is applied by default for visual aesthetics on MTF. To use exact ma mtf values (lines with stair stepping) - disable it MTF Notes: - uses simple timeframe textbox instead of input resolution dropdown to allow for 120, 240 and other custom TFs, also supports timeframes in H: 2H, H2 - Groups that are not assigned a Custom TF will use Current Timeframe (0). - MTF will work for any MA type assigned to the group - MTF works both ways: you can display a higher TF MA/BB on a lower TF or a lower TF MA/BB on a higher TF. - MTF MA values are normally aligned at the boundary of their native timeframe. This produces stair stepping when a higher TF MA is viewed on a lower TF. Therefore X Y Point Density/Smoothing is applied by default on MA MTF for visual aesthetics. Set both to 0 to disable and see exact ma mtf values (lines with stair stepping and original mtf alignment). - Smoothing is disabled for BB MTF bands because fill doesn't work with smoothed MAs after duplicate values are replaced with na. - MTF MA Value fluctuation is possible on the current bar due to default security lookahead Smoothing: - X,Y == 0 - X,Y smoothing disabled (stair stepping on high TFs) - X == 0, Y > 0 - X,Y smoothing applied to all TFs - Y == 0, X > 0 - X smoothing applied to all TFs < deltaX_max_tf, Y smoothing disabled - X > 0, Y > 0 - Y smoothing applied to all TFs, then X smoothing applied to all TFs < deltaX_max_tf X Smoothing with Y == 0 - shows only every deltaX-th point starting from the first bar. X Smoothing with Y > 0 - shows only every deltaX-th point starting from the last shown Y point, essentially filling huge gaps remaining after Y Smoothing with points and preserving the curve's general shape X Smoothing on high TFs with already scarce points produces weird curve shapes, it works best only on high density lower TFs Y Smoothing reduces points on all TFs, removes adjacent points with prices within deltaY, while preserving the smaller curve details. A combination of X,Y produces the most accurate smoothing. Higher delta value - larger range, more points removed. Show Max Bars Back: - can't set plot show_last from input -> implemented using a timenow based range check - you can't delete/modify history once plotted, so essentially it just sets a start point for plotting (from num_bars bars back) that works only in realtime mode (not in replay) Levels: You can plot current MA value using plot trackprice=true or by checking Show Price Line in Style. Problem is: - you can only change color (not the dashed line style, width), have both ma + price line (not just the line), and it's full screen wide - you can't set plot trackprice from input => implemented using plotshape/plotchar with fixed text labels serving as levels - there's no other way of creating a dynamic level: hline, plot, offset - nothing else works. - you can't plot a text var - all text strings must be constants, so you can't change the style, width and text labels without recompiling. - from input you can only adjust offset, indent and shift for each level group, and change color - the dot below each level line is the exact MA value. If you want just the line swap plotshape with plotchar, recompile and save as your private version, adjust Y shift. To speed up redraw times: reduce last_bars to ~2000, recompile and use as your own private version Pinescript is a rudimentary language (should be called Painscript instead) that can basically only plot data. You can't do much else. Please see the code for tips and hints. Certain things just can't be done or require shady workarounds and weeks of testing trying to resolve weird node.js compiler errors. Feel free to learn from/reuse/change the code as needed and use as your own private version. See comments in code. Good Luck!
Penunjuk Pine Script®
oleh RagingRocketBull
7