开始

Configurable

Moving Averages + BB & R.VWAP StDev (multi-tf)█ Moving Averages + Bollinger Bands and Rolling Volume Weighted Average Price with Standard Deviation Bands (Multi Timeframe) Multiple moving averages can be independently applied. The length , type and timeframe of each moving average are configurable . The lines and colors are customizable too. This script can display: Moving Averages Bollinger Bands Rolling VWAP and Standard Deviation Bands Types of Moving Averages: Simple Moving Average (SMA) Exponential Moving Average (EMA) Smoothed Moving Average (SMMA) Weighted Moving Average (WMA) Volume Weighted Moving Average (VWMA) Least Squares Moving Average (LSMA) Hull Moving Average (HMA) Arnaud Legoux Moving Average (ALMA) █ Moving Average Moving Averages are price based, lagging (or reactive) indicators that display the average price of a security over a set period of time. A Moving Average is a good way to gauge momentum as well as to confirm trends, and define areas of support and resistance. █ Bollinger Bands Bollinger Bands consist of a band of three lines which are plotted in relation to security prices. The line in the middle is usually a Simple Moving Average (SMA) set to a period of 20 days (the type of trend line and period can be changed by the trader, a 20 day moving average is by far the most popular). The SMA then serves as a base for the Upper and Lower Bands which are used as a way to measure volatility by observing the relationship between the Bands and price. █ Rolling VWAP The typical VWAP is designed to be used on intraday charts, as it resets at the beginning of the day. Such VWAPs cannot be used on daily, weekly or monthly charts. Instead, this rolling VWAP uses a time period that automatically adjusts to the chart's timeframe. You can thus use the rolling VWAP on any chart that includes ​volume information in its data feed. Because the rolling VWAP uses a moving window, it does not exhibit the jumpiness of VWAP plots that reset. Based on the previous script :
Pine Script™指标
由Yatagarasu_提供
3
Algorithm Builder - Single TrendHello traders I. SCRIPTS ACCESS AND TRIALS 1. For the trial request access, they have to be done through my website . 2. My website URL is in this script signature at the very bottom (you'll have to scroll down a bit and going past the long description) and in my profile status available here : Daveatt Due to the new scripts publishing house rules, I won't mention the URL here directly. As I value my partnership with TradingView very much, I prefer showing you the way for finding them :) 3. You may also contact me directly for more information II. Algorithm Builder - Single Trend 2.1 Concept The Algorithm Builder - Single Trend was made to detect the convergence (also called confluence) of many unrelated indicators, giving a BUY or SELL signal whenever all the selected sub-indicators are converging in the same direction. The Single Trend gives one single entry per identified trend - unlike the Multiple Trends editions (also available on my scripts page) which may give more than 1 entry per trend. The traders select the sub-indicators they want, and see in real-time the BUY and SELL triangles being updated. 2.2 Why the Algorithm Builder Single Trend may help you I worked with many traders during my career, and their feedback about trading is often pretty similar. They all tried a lot of complicated indicators, losing their capital, and finally getting back to the basics (even to the basic indicators if I might say) The art is finding a good combination of indicators and setting strict money/risk management rules. Easy in concept, but more than 90+% of traders lose money on the markets... which teach us that trading is not only about drawing trendlines, or using cool indicators but finding ways to ease our psychology while trading. 2.3 The Algorithm Builder trading framework The sub-indicators (full list on our website) weren't chosen randomly. They're based on a trading method we've developed over the last 6 years - while working with traders and other trading quants. The Algo Builders are made to detect a convergence - and as such, will give a signal once a trend has been identified. They're not made to detect reversal but have been designed to give a signal when all sub-indicators are either ALL bullish (green) or ALL bearish (red). We provide a framework based on indicators we selected because they: 1. make sense to be used altogether 2. work on asset classes like INDEX, CRYPTO, STOCK OPTIONS, FOREX, COMMODITIES 3. it may expand your knowledge about what detecting a convergence with pre-selected indicator really means 2.3.1 Supports and Resistances The indicator displays the main algorithmic supports and resistances according to our trading method. I think they're relevant for all asset classes, but you're absolutely free to use any different supports/resistances logic if you want to. I'm not against it because I know that pivots, Fibonacci levels, etc. may work very well also. 2.3.2 Alerts Alerts are enabled obviously :) III. Pain points that we're trying to solve with our Algorithm Builders Issue #1 There are many informations / indicators / strategies / backtests / noise. Finding the right ones is not a simple task. Solution #1 A reliable system that removes the external noise is much needed in trading to stay "in the game". Issue #2 Trading could be quite stressful - The majority doesn't lose in trading because technical analysis is hard, but because managing our psychology is one of the hardest things a human can do. Solution #2 Some ways to reduce the "trading stress" could be: getting better quality signals and trading like a "machine". Forgetting about Twitter and trusting the system you designed. Issue #3 Trading without strict rules and only based on what we feel, or what we think the market should do is the fastest way to kiss our money goodbye. Only 1 indicator generally is not enough. Traders generally use a combination of several indicators but they're monitoring them individually. It's normal then to feel exhausted at the end of the day ^^ (to say the least)... and exhaustion leads to mistakes which leads to..... (I'm sure you got it) ... capital loss. Solution #3 As a trader, I needed a trading framework and a method. I offer our trading method but they're plenty others out there. We cannot claim obviously it's the best ever ....but let's say we're using those exact same scripts ourselves for our trading. And this what we've been recommending our clients to trade with for the past years. Also, having a tool detecting the convergence of several indicators and giving 1 unique signal for BUY/SELL position will save you a lot of time/energy, and perhaps might help you out getting better trading performance. IV. Resolving a complex puzzle and having fun in the process Trading has to stay a passion and not (only be) a source of intense stress. The most successful traders I know are "trading geeks" - literally always looking for optimizing, searching for the best possible entries, setups, indicators, tools, etc. For them, it's not even about the money anymore, but only about beating their previous performance. Why are they doing this? Because it's fun Might appears as a bold statement, but I guarantee that looking for setups is fun. One of our users even told us, that it's like playing with "Legos" and we couldn't possibly agree more. V. Designing a system that "makes sense" Another bold statement now. Brace yourselves ladies and gentlemen The Algorithm Builders allow to design trading systems quickly. What could takes days/weeks/months to find out... might be now within your reach in less than a few hours. With a bit of practice, less than an hour might be enough per asset/timeframe to fine a system that make sense to you and adapted to your trading capital and psychology. Assuming our users read our guides and are fully committed to learning a new way of trading - then we do guarantee you'll be able to design kick-ass trading systems that make sense. "Making sense" doesn't mean at all it's guaranteed to win, it means you're the one defining the convergence of indicators, using your Algorithm Builder, and observe that most of the time - whenever there is a BUY signal, the candlesticks are going upwards - whenever there is a SELL signal, it's going downwards. This is a necessary step to make real progress from a trading analyst perspective - and hopefully could lead to profits. VI. Algorithm Builder versus the main trader enemy(=psychology) This indicator has the goal to help solving one of the MAIN issues encountered by traders. Most of traders realize, they can't perform with only 1 indicator (or 1 price pattern or 1 price action) and need a combination of multiple indicators before getting in a trade. Far from being a magic pill, if it could at least reduce the stress you have while trading, then we'll consider we made a great job - it's a technical "useless noise remover", and needs to be followed strictly. Such trust in a trading system can only be built by testing your Algorithm Builder configuration on either: 1. a demo account 2. or a live account with small bids. And then, increasing progressively the bids if your capital increases progressively. Though, you should still use your common sense. (for instance: if we get a BUY signal right on a big timeframe resistance we're hitting for the first time). I'm aware this is a new way of trading but for many, and while we cannot foresee the future, neither predict performance, we believe it might save you a lot of time to find good signals. My maximum level of happiness will be reached the day when our users will contact me and showing me setups being mine. I'm sure that even I can learn from my users and, we can all learn from each other Algorithm Builder configuration VII. What is a wrong or bad configuration? Simply put. If you see that most of your signals react such as described below: 1. a buy triangle predicts, most of the time an upwards move 2. a sell triangle predicts, most of the time a downwards move 3. you estimated yourself the stop-loss needed to give enough room for your trades. 4. take profits based on algorithmic support and resistances or your own take profit method. So what's a good Algorithm Builder configuration? A configuration you're happy with and makes sense. A better Algorithm Builder setup is one used in demo or a live account w/ small bids for a few weeks, and you're consistent in your trading performance. If you have any doubt or question, please hit me up directly or ask in the comments section of this script. I'll never claim I have the best trading methodology or the best indicators. You only will be the judge, and I'll appreciate all the questions and feedback you're sending my way. They help me a ton to develop indicators based on all the requests I received. Kind regards, Dave
Pine Script™指标
由Daveatt提供
4
JZW: 8 MA's (EMA, SMA or WMA) Multi TimeframeUp to 8 Moving Averages can be applied to your chart. Each one is individually configurable for the following: 1. Length 2. Method: EMA, SMA or WMA. 3. Timeframe: Current, 1H, 2H, 4H, 6H, 12H, 1D, 3D, Weekly or Monthly. Any MA's set to the current or higher timeframe than the chart will be displayed. Suggested use: set 2 or 3 MA's to a higher timeframe (e.g. daily or weekly) to determine the overall trend and set the others to the current timeframe for intraday trading. The example chart is set to EMA's 3, 5, 10, 20, 50 on current timeframe (4H) and EMA's 50, 100 & 200 for daily. My first published script, hope you all find this useful! Any feedback would be welcome.
Pine Script™指标
由joezwarr提供
3
Support Resistance Minutes BarsThis indicator plots horizontal lines for the high and low of each of the last x (configurable from 1 to 20) bars, each of which may be anywhere from 1 minute to thousands of minutes--preview image is for 90-minute bars. I have found that it goes nicely alongside the daily version of this indicator. 120 minute levels x10 with 1-day levels x10: 240 minute levels x20 with 1-day levels x20: 300 minute levels x8 with 1-day levels x10: 618 minute levels x3 with 1-day levels x1:
Pine Script™指标
由Lemrin提供
Support Resistance Weekly Bars - Repost (website issue)This indicator plots horizontal lines for the high and low of each of the last x weeks (configurable from 1 to 20). Increasing this number beyond 20 is not possible due to some technical Pine limitations. I am also publishing a daily and monthly version...add them all to the same chart! Written for TV user: kvpatel Reposting because something broke, and the first version is no longer available in my list of scripts to update (needed to fix a bug).
Pine Script™指标
由Lemrin提供
1
Awesome Oscillator and MACD, AntiStep VersionAny indicator based on moving averages (MAs) lags real-time movement. Immediately after large ("step") changes in level, the pre-step values that are still within the MA window cause the result to falsely reflect continued movement, even if real-time values remain flat or move in the opposite direction. To counter this, when a step change of a configurable size is detected, my technique temporarily shrinks the MA window size to include only those values occurring since the step change, and then allow the size to increase to normal length as we move away from the step change. Changes from my previous AO/MACD indicator: Added anti-step capabilities, including brand-new functions that implement my anti-step technique in ema() and rma(). Created generalized alpha_ma() function, which allows ema function creation using custom alpha structures. Created "_external" versions of all antistep functions, allowing step detection to be based on some other series, aside from the one being averaged (this is required for the macd signal ma). Added options to calculate ao and macd using SMA, EMA, or RMA, including anti-step versions of all three. Added bull and bear signal indicators based on previous descriptions. Comparison with anti-step enabled and disabled: Comparison with different tolerance levels (positive tolerance detects fewer steps; negative tolerance detects more steps):
Pine Script™指标
由Lemrin提供
3
Awesome Oscillator and MACD HistogramThis is a quick script that combines two standard indicators, the Awesome Oscillator and MACD histogram, to highlight the beginnings of periods of fast price movement (divergence between the two). Since MACD's EMA responds more quickly than AO's SMA, look for periods of green over gold as a bullish signal, and red under blue as a bearish signal. Of course both indicators are lagging in nature, but the presence of this divergence often leads larger, continued movement in the same direction. Bullish Signals Change from red to green below 0 with either blue or gold above 0 (strengthened on second green bar): Rising green above 0 with gold below 0: Bearish Signals Change from green to red above 0 with either blue or gold below 0 (strengthened on second red bar): Deepening red below 0 with blue above 0:
Pine Script™指标
由Lemrin提供
12
Automatic Support, Resistance, Fibonacci LevelsThis indicator plots absolute high and low values for up to five completely adjustable time periods (in months, weeks, days, hours, minutes) and optionally calculates the Fibonacci levels on the pair of absolutes of your choice, ascending or descending, and mimics the shading available in the built-in Fib charting tools (e.g. retracement). Here are a few screenshots of the same chart with various options selected. 3-Month, 4-Week, and 5-Day absolutes with 3-Monthly Fib plotted: The same chart with 4-Weekly Fib: The same chart with 5-Daily Fib: 5-Day, 12-Hour, 90-Minute absolutes with 12-Hourly Fib: Zoomed in, on a 30-minute interval, with 90-minute Fib: With descending ("inverted") 90-minute Fib: I started putting this together for Vazzyb, who was looking for a way to automate plotting horizontal support and resistance levels for monthly, weekly, and daily extremes, and then I added additional features as they occurred to me. Special thanks to Paaax, who suggested I add Fib levels. I am leaving the code open, so you may feel free to grab snippets you like and use them for your own purposes. Of particular interest may be my custom "calc_fib()" function, which accepts any series pair, as well as a Boolean indicating whether to invert, and returns an array with each of the major Fibonacci levels: . If anyone likes this enough to feel generous, please feel free: BTC 3KmFchJ18QvMzAJKDcFQXvyK9p1EHWQdhP BCH qqtrw64ptuwprk5vtj3z8qwkvh3v0jawxq7khqng7x ETH 0x9b51361A278910Ba3945C7519C9f0FA8a77df18d LTC MDeWWsP7XCG2zQuZ2dYALZXQ52u2qkc8fh P.S. If you want the time lengths to be as close to accurate as possible, don't forget to change the number of days per week when using for cryptocurrency!
Pine Script™指标
由Lemrin提供
20
Reset Every (Price)Someone requested a high/low price indicator that would reset the "remembered" prices daily. I started out doing just that, and then decided to make it much more configurable. Choose the units (minutes, hours, days, weeks, months) and the number of those units, and this will reset the highest/lowest value remembered to the current values on your chosen time interval. This should work with any time interval you desire, within reason...asking for resets every 4000 hours on a monthly chart will probably not work. GE, monthly, every 7 months: Ford, weekly, every 18 months: Dow Jones Industrial Average, weekly, every 90 days: LTCBTC, daily, every 10 days: ETHUSD, 30 minutes, every 10 days: BTCUSD, 1 minute, every 10 hours: EURUSD, 1 minute, every 50 minutes: Also, I am about to publish another version of this with just one source input that can be applied to any indicator...stay tuned!
Pine Script™指标
由Lemrin提供
3
PVT OscillatorThis is the non-accumulating portion of the price-volume trend (PVT)--the amount by which PVT would change each bar--which I have turned into a zero-centered oscillator. The plot is a 9-day EMA of the PVT change, multiplied by 1000 for readability, with lime/red corresponding to whether the actual PVT increased or decreased for that bar. As always, the length of this moving average is adjustable, as is the source of price(s) to use--open, close, high, low, HL2, HLC3, or OHLC4.
Pine Script™指标
由Lemrin提供
6
Fractal Breakout V2Version 2 of my fractal pattern aid ( Version 1 ). I added a bouncing line between the high and low trend lines, connecting consecutive extreme points. I also chased down a pesky bug in the slope calculation...and for now I have disabled the ability to change resolution basis for extreme detection (e.g. 30m on a 1hr chart). For fun, I added some shading to make it more apparent at a glance what is happening, but if you find it gimmicky, there's an option to turn that off. I am inexperienced with pattern recognition, so please send feedback if you have any ideas that would make this more useful. Thanks! Lemrin
Pine Script™指标
由Lemrin提供
11
Fractal BreakoutFirst of all, huge credit to synapticEx , whose brilliant use of the security function inspired me to figure out a way to get quasi-shape boundaries automatically drawn on a chart. This study draws upper and lower trend lines, based on configurable fractal*** reversal detection, calculates slope from the last two upper or lower reversal points, and then extends a dotted line along the same slope...until the next upper (or lower) reversal occurs. If the high (or low) breaks this extension, the dotted line becomes solid to aid visibility. Reversal detection is configurable to use any number of ticks, but probably four to eight will work best. I made the inclusion of volume in the reversal logic optional (off by default) and left the existing SMA input found in synapticEx's code intact, albeit with a lower default. With the addition of trend lines, I found volume hindered identification of reversals, although I could try various other filters than the SMA included originally. I have also left intact the very nice ability to change the period and use the requested period identify reversals, courtesy of synapticEx. This could be used in a strategy, as the values plotted are actual values that are available to include in logic and do not include knowledge of the future. However , information is not available until the floor of half the number of ticks used in reversal detection (I then offset by that number to line things up visually). Having never heard of it until now, I just Googled the Bill Williams Alligator strategy, which looks interesting, so maybe I could see how this could be ported to that. ***As I typed this, I remembered that while making reversal detection configurable, I changed the detection logic simply to look for highest (or lowest) of the desired length of ticks. I don't know whether this is not strictly fractal anymore, but if desired, with a little work, I could make it require consecutive, consistent changes before and after each reversal again. Here are a few screenshots from hourly ticks, using the "current" (hourly) period, with and without volume, and playing with the number of points used to identify reversals. Not using volume Using volume
Pine Script™指标
由Lemrin提供
8