[fikira] Harmonic Patterns 2This is "Harmonic Patterns", part 2 Open Source
(in 2 parts, otherwise many lines are gone because the script is too large):
- Crab
- Bat (+ Alt)
- Butterfly
- Shark
A "Pattern" is created by checking 5 consecutive ( pivot ) points, starting with X, A, B, C, and ending with point D.
At point D all 5 points are compared, calculated and verified.
When confirmed, a "Label" will be plotted at point D, together with the "Entry", "Take Profit" and "Stop Loss" price.
The "Entry", "Take Profit" and "Stop Loss" lines will be plotted as well at point D.
Lastly, a "Drawing" automatically will be displayed which makes the "Pattern" visible.
Please do mind, the "Drawing" is calculated differently, the "Drawing" sometimes can be displayed incorrectly
when prices are too close to each other (for example low Satoshi price changes).
THE "ENTRY", "TAKE PROFIT", "STOP LOSS" PRICES AND LINES ARE NOT AFFECTED AT ALL BY THIS, THEY WILL SHOW CORRECTLY!
- 1 "TP point" can be changed ("TP Level 0.618")
- "Labels", "Lines", "Drawings" can be disabled/enabled
- "Labels" can be made smaller or bigger ("Size Label")
- "Labels" can be placed further or closer to the bar ("Distance TP Label" > higher = closer, lower = further)
- "Lines" can be made thicker or thinner ("TP Linewidth")
- "Drawings" can be made thicker or thinner ("Drawings Linewidth")
- "Drawings" are created by comparing with 100 bars back in history (default), should it be (very rarely) a triangle is displayed flat on the left side,
possibly the first point(s) is/are further than 100 bars ago, in this case increase "Period Drawings" above 100.
- Animal symbols can be enabled/disabled
- When several "Patterns" appear on the chart, the oldest ones won't be displayed anymore, first the "Drawings", then the "Lines"
The last (present) ones will always be displayed in total without a problem!
- If you want to see "Patterns" with less correct measurement, change "Error Marge" 0.9 - 1" and "Error Marge" 1 - 1.1"), this gives max. about 10% extra margin
- Added more settings regarding "Drawing Lines"
Thank you very much!
Indikator Zig Zag
ZigZag ++ fibsI just put this as one user ask for me to do it.
So it the zigzag++ and fibs ,and other pivots type
the fibs can daily , monthly , year
the info panel need to be adjusted by either offset =distance from
or by putting a number , here its btc so I put about 500 above from close =8500
this important as otherwise it will look messy and not pretty
so for each type of asset you use , you expect to adjust this two variables or the data of fibs (daily , weekly etc)
ZigZag - lucemanb
THIS CODE IS BASED FROM THE MT4 ZIGZAG INDICATOR
THE ZIGZAG SETTINGS FOR THE MAIN ONE ON TRADINGVIEW DO NOT WORK THE SAME AS MT4
I HOPE U LOVE IT
I have had tons of experience on the ZIGZAG indicator and thought this might help someone.
Enjoy this code. Zigzag is a good indicator in many ways and people underestimate it because of its repainting
Check out some work ave done with this script. This is some intense angle trading requested by someone
ZigZag Plus [xdecow]A ZigZag Like based on candle close.
A lot of options that can be hide in options.
Triangle/bright - reversal confirmation candle
Circle/dark - higher/lower candle breakout
Square/light - Insidebar
Average True Range PercentageUseful in finding the percent change in the ATR. Google it and see how you can implement it. I use it in a zig zag indicator made by Ricardo Santos.
Happy Trading!
R100 Wave Volume v2 (*v*)This indicator is similar to the Weis Wave Volume indicator in that it shows cumulative volume for each up and down price wave. However it is calculated differently, using the Jurik moving average to determine turning points. Use this in conjunction with the R100 Wave indicator to determine the best fit Jurik length and power settings.
A great indicator to help analyse the strength of pullbacks, continuation moves and changes in behaviour.
I hope you get some value out of it. Only conditions of use are that if you improve it, let me know and if you publish something that uses it, don't hide the code! Enjoy!
Code pinched and modified from Zero Lag ZigZag by Duyck - thankyou
Jurik Moving Average (for turning points) by Everget - thankyou
and Weis Wave by Modhelius - thankyou
R100 Wave v2 (*v*)This is a Wave (or Zig Zag) indicator I made to use in conjunction with the Wave Volume indicator I use.
It uses the Jurik moving average to determine turning points, and will plot the tops and bottoms of the wave based on the most recent high- so you can also use to quickly find pivot highs and lows. If you are using with the R100 Wave Volume indicator, first adjust the wave to fit better (if required) using the Jurik length and/or power, and then use the same settings on the Wave Volume indicator. Default settings work pretty well for most stocks, but adjusting the length between 8 and 14 should be enough for a good fit, or adjust the power between 1 and 3, or get fussy and tweak it with both.
The Jurik MA has been modified to include a VWAP component, so will only work where you have volume. The last "leg" of the wave will move about until the next pivot high or low is found and then will remain fixed.
I hope you find some value with it. Only conditions of use are that if you improve it, let me know and if you publish something that uses it, don't hide the code! Enjoy!
Code pinched and modified from Zero Lag ZigZag by Duyck - thankyou
Jurik Moving Average (for turning points) by Everget - thankyou
and Weis Wave by Modhelius - thankyou
Higher High Lower Low Strategy (With Source Code)This script finds pivot highs and pivot lows then calculates higher highs & lower lows. And also it calculates support/resistance by using HH-HL-LL-LH points.
Generally HH and HL shows up-trend, LL and LH shows down-trend.
If price breaks resistance levels it means the trend is up or if price breaks support level it means the trend is down, so the script changes bar color blue or black. if there is up-trend then bar color is blue, or if down-trend then bar color is black. also as you can see support and resistance levels change dynamically.
If you use smaller numbers for left/right bars then it will be more sensitive.
source code of :
Fractal Regression Channel V0.1Port of @RicardoSantos' Fractal Regression Channel V0 from pinescript 2 to pinescript 3.
// Source:
// Original Author: @RicardoSantos
Zero Lag - ZigZag - JDThis is a alternative version of the well known "ZigZag indicator" but it uses turning points of the Jurik ma
instead of the traditional "pivot points" that are by definition lagging by a large lookback period, the (almost-) Zero Lag ZigZag lags by about 2 bars on average (depending on the candles forming)
The ZigZag pattern can be used to draw trendlines and S/R lines
It can also be used for "wave counting" in a way that reduces interpretation.
If you find other uses, please leave your ideas in the comments!
Shoutout to Everget for the awesome Jurik code!!
JD.
#NotTradingAdvice #DYOR
Simple LinesIntroduction
Making lines is great in technical analysis since it can highlights principal movements and make the analysis of the price easier when using certain methodologies (Elliott Waves, patterns).
However most of the indicators making lines (Zig-Zag, simple linear regression) are non causal (repaint), this is the challenge i tried to overcome, making an indicator capable of making lines in a smart way (able to follow price without loosing a linear approach) and with the least lag possible, i inspired myself from the behaviour of the renko when using a small brick size. This indicator does not repaint .
The code is short and i hope, understandable for all of you, making lines is not a difficult task and its important to know that when a problem appear complex it does not mean that the code used to solve this problem must be complex. Lets see the indicator in details.
The indicator
The indicator have 4 parameters, the length parameter who control the length of lines, the emphasis parameter who control the stability and also the ability to make lines closer to the price (thus minimizing the sum of squares) , the mult parameter which is similar to emphasis and a point option that we will discuss later.
When emphasis and mult are both equal to 1 the indicator will sometimes draw a perfect line, however this line will try to follow the price and thus can create a noisy result.
This is where emphasis and mult will correct this behaviour. The emphasis parameter give a more periodic look as well as some control to the lines but can also destroy them.
This should not happen with mult , this parameter also give more predictability to the lines. Overall it correct the drawbacks of the parameters combinations mentioned earlier.
Its also possible to mix both the emphasis and mult parameter, but take into account that when both are equals the result consist of less reactive lengthy lines with low accuracy. Its better to only use one of them and let the other stay to 1.
Point Option
The indicator can sometimes have a weird look, appearing almost flat or just dont appearing at all. When such thing happen use the point option.
XPDUSD without point option.
with point option :
Time Frame Problem and Its Fix
When using higher time-frames the result of the indicator can appear different, in general the higher the time frame the lengthier are the lines. In order to fix this you can use decimals in the length parameter
length and mult both equal to 5.5, emphasis cant use decimals.
Conclusion
I have highlighted a simple way to make use of the small renko box size method in order to return reactive lines without making the indicator repaint. However Its ability to be close to the price as well as being always super reactive is not a guarantee.
For any suggestion/help feel free to pm me, i would be happy to help you :)
zigzag%This is zigzag % , no repaint and no lag as it based on % changes
the main issue is the addition of take profit and stop loss together with trailing (thanks to Yatrader to his code)
set the zigzag% according to best fit of your graph for best results
Kawabunga Swing Failure Points Candles (SFP) by RRBKawabunga Swing Failure Points Candles (SFP) by RagingRocketBull 2019
Version 1.0
This indicator shows Swing Failure Points (SFP) and Swing Confirmation Points (SCP) as candles on a chart.
SFP/SCP candles are used by traders as signals for trend confirmation/possible reversal.
The signal is stronger on a higher volume/larger candle size.
A Swing Failure Point (SFP) candle is used to spot a reversal:
- up trend SFP is a failure to close above prev high after making a new higher high => implies reversal down
- down trend SFP is a failure to close below prev low after making a new lower low => implies reversal up
A Swing Confirmation Point (SCP) candle is just the opposite and is used to confirm the current trend:
- up trend SCP is a successful close above prev high after making a new higher high => confirms the trend and implies continuation up
- down trend SCP is a successful close below prev low after making a new lower low => confirms the trend and implies continuation down
Features:
- uses fractal pivots with optional filter
- show/hide SFP/SCP candles, pivots, zigzag, last min/max pivot bands
- dim lag zones/hide false signals introduced by lagging fractals or
- use unconfirmed pivots to eliminate fractal lag/false signals. 2 modes: fractals 1,1 and highest/lowest
- filter only SFP/SCP candles confirmed with volume/candle size
- SFP/SCP candles color highlighting, dim non-important bars
Usage:
- adjust fractal settings to get pivots that best match your data (lower values => more frequent pivots. 0,0 - each candle is a pivot)
- use one of the unconfirmed pivot modes to eliminate false signals or just ignore all signals in the gray lag zones
- optionally filter only SFP/SCP candles with large volume/candle size (volume % change relative to prev bar, abs candle body size value)
- up/down trend SCP (lime/fuchsia) => continuation up/down; up/down trend SFP (orange/aqua) => possible reversal down/up. lime/aqua => up; fuchsia/orange => down.
- when in doubt use show/hide pivots/unconfirmed pivots, min/max pivot bands to see which prev pivot and min/max value were used in comparisons to generate a signal on the following candle.
- disable offset to check on which bar the signal was generated
Notes:
Fractal Pivots:
- SFP/SCP candles depend on fractal pivots, you will get different signals with different pivot settings. Usually 4,4 or 2,2 settings are used to produce fractal pivots, but you can try custom values that fit your data best.
- fractal pivots are a mixed series of highs and lows in no particular order. Pivots must be filtered to produce a proper zigzag where ideally a high is followed by a low and another high in orderly fashion.
Fractal Lag/False Signals:
- only past fractal pivots can be processed on the current bar introducing a lag, therefore, pivots and min/max pivot bands are shown with offset=-rightBars to match their target bars. For unconfirmed pivots an offset=-1 is used with a lag of just 1 bar.
- new pivot is not a confirmed fractal and "does not exist yet" while the distance between it and the current bar is < rightBars => prev old fractal pivot in the same dir is used for comparisons => gives a false signal for that dir
- to show false signals enable lag zones. SFP/SCP candles in lag zones are false. New pivots will be eventually confirmed, but meanwhile you get a false signal because prev pivot in the same dir was used instead.
- to solve this problem you can either temporary hide false signals or completely eliminate them by using unconfirmed pivots of a smaller degree/lag.
- hiding false signals only works for history and should be used only temporary (left disabled). In realtime/replay mode it disables all signals altogether due to TradingView's bug (barcolor doesn't support negative offsets)
Unconfirmed Pivots:
- you have 2 methods to check for unconfirmed pivots: highest/lowest(rightBars) or fractals(1,1) with a min possible step. The first is essentially fractals(0,0) where each candle is a pivot. Both produce more frequent pivots (weaker signals).
- an unconfirmed pivot is used in comparisons to generate a valid signal only when it is a higher high (> max high) or a lower low (< min low) in the dir of a trend. Confirmed pivots of a higher degree are not affected. Zigzag is not affected.
- you can also manually disable the offset to check on which bar the pivot was confirmed. If the pivot just before an SCP/SFP suddenly jumps ahead of it - prev pivot was used, generating a false signal.
- last max high/min low bands can be used to check which value was used in candle comparison to generate a signal: min(pivot min_low, upivot min_low) and max(pivot max_high, upivot max_high) are used
- in the unconfirmed pivots mode the max high/min low pivot bands partially break because you can't have a variable offset to match the random pos of an unconfirmed pivot (anywhere in 0..rightBars from the current bar) to its target bar.
- in the unconfirmed pivots mode h (green) and l (red) pivots become H and L, and h (lime) and l (fuchsia) are used to show unconfirmed pivots of a smaller degree. Some of them will be confirmed later as H and L pivots of a higher degree.
Pivot Filter:
- pivot filter is used to produce a better looking zigzag. Essentially it keeps only higher highs/lower lows in the trend direction until it changes, skipping:
- after a new high: all subsequent lower highs until a new low
- after a new low: all subsequent higher lows until a new high
- you can't filter out all prev highs/lows to keep just the last min/max pivots of the current swing because they were already confirmed as pivots and you can't delete/change history
- alternatively you could just pick the first high following a low and the first low following a high in a sequence and ignore the rest of the pivots in the same dir, producing a crude looking zigzag where obvious max high/min lows are ignored.
- pivot filter affects SCP/SFP signals because it skips some pivots
- pivot filter is not applied to/not affected by the unconfirmed pivots
- zigzag is affected by pivot filter, but not by the unconfirmed pivots. You can't have both high/low on the same bar in a zigzag. High has priority over Low.
- keep same bar pivots option lets you choose which pivots to keep when there are both high/low pivots on the same bar (both kept by default)
SCP/SFP Filters:
- you can confirm/filter only SCP/SFP signals with volume % change/candle size larger than delta. Higher volume/larger candle means stronger signal.
- technically SCP/SFP is always the first matching candle, but it can be invalidated by the following signal in the opposite dir which in turn can be negated by the next signal.
- show first matching SCP/SFP = true - shows only the first signal candle (and any invalidations that follow) and hides further duplicate signals in the same dir, does not highlight the trend.
- show first matching SCP/SFP = false - produces a sequence of candles with duplicate signals, highlights the whole trend until its dir changes (new pivot).
Good Luck! Feel free to learn from/reuse the code to build your own indicators!
zigzag Pivots v1So I took the zigzag pivot of my last script , i remove the original zigzag and replace it by % zigzag , then i add the TP % 1 and 2 and by the cross of the uptrend of the zigzag % of the pivot points of support and resistance we can make buy and sell signal (H and L) and take the profit out by the trend using the Take profit 1 and 2.
for each time frame you need to set up the % correctly for the best fit to get optimal results
set also the bar length or resistance to best fit (now its on 20) try maybe 10 or 15
zigzag PivotsThis is based on two model : the first is the zigzag model of Ricardo Santos
the second is a pivot system for high and low to find resistance made by jaggedsoft
I try to show the connection between them and to form a cross of when the zigzag model crossing the pivot model
this is seen in show sig
best approach is to find the low based on the pivot system and try to make your buy around that spot . when there is high resistance either exit or buy when the asset cross it above . in case of short do the opposite
Weis Wave ChartThis indicator is based on the Weis Wave described by David H. Weis in his book Trades About to Happen: A Modern Adaptation of the Wyckoff Method, more info how to use this indicator can be found in this video . The Weis Wave is an adaptation of Richard D. Wyckoff’s method Wave Charts. It works in all time periods and can be applied to all asset types.
Unlike other implementations I found here on TradingView, this implementation make use of a Renko-like zig zag pattern, very similar to how it is described in David H. Weis' book. The settings for the zig zag pattern are very similar to the standard Renko settings here on TradingView, in the "Renko Assignment Method" you either chose "ATR" or "Traditional" (read more about it here ). The ATR length or the brick size is then entered in the textbox "Value". You can also chose another setting in the "Renko Assignment Method" drop down named "Part of Price" which calculate the brick size from the current close and divide it by the value in the text box "Value". It is also possible to chose if the zig zag pattern shall use the high/low, the open/close or just the close as the most extreme values in its calculation, you select this in the drop down "Price Source".
TradingView's pine script does currently not support to print non-static text on the chart, so it is not possible at this point to write out the volume on the zig zag chart. It is also not possible to have both an overlay and separate chart pane in the same indicator, therefor this indicator is split up in two.
You can find the volume indicator here:
GTM - Team signal Buy/Sellstudy(title="GTM - Team signal Buy/Sell", shorttitle="GTM - Team signal Buy/Sell", overlay=true)
len = input(10, minval=1, title="Length")
src = input(close, title="Source")
out = ema(src, len)
bearish = cross(close,out) == 1 and close > close
bullish = cross(close,out) == 1 and close < close
plotshape(bearish, color=red, style=shape.arrowdown, text="Sell", location=location.abovebar)
plotshape(bullish, color=green, style=shape.arrowup, text="Buy", location=location.belowbar)
