Wicks Cluster indicator
Forums › ProRealTime English forum › ProBuilder support › Wicks Cluster indicator
- This topic has 14 replies, 2 voices, and was last updated 2 years ago by amitoverseas40.
-
-
08/28/2022 at 12:16 PM #199740
Hi There PRC Team,
Please may I request someone to code the wickzone indicator for me?
I have checked the whole site and there isn’t anything available and I am unable to code despite my best efforts 🙁
Idea is very simple to find 2 or more wicks that are clustering the price zone on either up side OR downside and look for reversals as this is price rejection in any direction on break of these levels and keep shifting the pattern to the right.
Wick length should be a customizable parameter i.e. .40% or 50% etc.. along with the rectangle box to be customizable or simply put keep displaying
08/28/2022 at 12:24 PM #199745Hi There PRC Team,
Please may I request someone to code the wickzone indicator for me?
I have checked the whole site and there isn’t anything available and I am unable to code despite my best efforts 🙁
Idea is very simple to find 2 or more wicks that are clustering the price zone on either up side OR downside and look for reversals as this is price rejection in any direction on break of these levels and keep shifting the pattern to the right.
Wick length should be a customizable parameter i.e. .40% or 50% etc.. along with the rectangle box to be customizable or simply put keep displaying
To avoid any confusion please view the last attachement
08/29/2022 at 8:56 AM #199771Not easy to achieve, here is the first step of your query, which roughly detects the “cluster” and draw the rectangle between at least 2 wicks in the same area.
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647defparam drawonlastbaronly=truewickpercent = 50//store wicks dataif (high-max(close,open))/range>=wickpercent/100 then$wh[w] = high$wl[w] = max(close,open)$wbar[w] = barindex$wtype[w] = 1w = w + 1endifif (min(open,close)-low)/range>=wickpercent/100 then$wh[w] = min(open,close)$wl[w] = low$wbar[w] = barindex$wtype[w] = -1w = w + 1endifif islastbarupdate and w>2 then//fetch the wicks data setfor i = 0 to w-1hh=$wh[i]ll=$wl[i]for j = i+1 to w-1//within the rangemid = ($wh[j]+$wl[j])/2//upper wickif $wtype[i]=1 and $wtype[j]=1 thenif mid>=$wl[i] and mid<=$wh[i] thendrawrectangle(min($wbar[i],$wbar[j]),min(ll,$wl[j]),max($wbar[i],$wbar[j]),max(hh,$wh[j])) coloured("cyan",50) bordercolor("cyan",80)endifendif//lower wickif $wtype[i]=-1 and $wtype[j]=-1 thenif mid>=$wl[i] and mid<=$wh[i] thendrawrectangle(min($wbar[i],$wbar[j]),min(ll,$wl[j]),max($wbar[i],$wbar[j]),max(hh,$wh[j])) coloured("crimson",50) bordercolor("crimson",80)endifendifnextnextendifreturn w1 user thanked author for this post.
08/29/2022 at 9:34 AM #199780Hi Nicolas,
Many thanks for the swift response and code. I do this day in and out, and it works beautifully, until I make a mess due to manual calculations and vision impairment 🙂 this is the key to losing trade in this strategy, 2 wrong trades based on missed cluster or wicks and there goes all the profit earned 🙂
I tried to put indicator on chart it errors with too many iterations were detected of the loop. Using 11.1 1.8.0 to be precise?
Thanks
08/29/2022 at 1:16 PM #19978808/29/2022 at 1:20 PM #199789Hi Nicholas,
Tried all timeframes from 1 min to 1 hr and even with 25 units etc but either the chart is not displayed properly or I get the loop error. Any chance you can post the screen shot with settings so I can use the same please?
Thanks
08/29/2022 at 1:23 PM #199792Here it is.
1 user thanked author for this post.
08/29/2022 at 1:43 PM #199797Hi Nicolas, many thanks, for some bizzare reason it keeps the display as scewed..I’ve to do adjustment to display correctly, nontheless, concept is simple…buy above the break of blue’s and sell below the break of red! works nicely with proper risk mgmt..I call it wick pivots…need the target set..for me it’s easy to see the next target UPSIDE for Dax at 920 after break from 840…if we can get that displayed than we are good.
08/29/2022 at 2:11 PM #199803remove w from the last line or set your price scale to use “price only”.
1 user thanked author for this post.
08/29/2022 at 2:26 PM #199804Ah, now it works after removing w and with less units, many thanks Nicolas! appreciate your help!
let’s try and see if my visual impairment gets better with this…strategy hasn’t let me down but my own mistakes in identifying the levels so far!
08/29/2022 at 2:38 PM #1998071 more ask pls, apologies, to remove the levels that have been tested in order to avoid chaos on the chart and clearly see the one’s that are yet to be breached?
08/29/2022 at 2:58 PM #199813Dax ..920 almost breached with hi 915 😁
Now if we go below 850, clear way towards 820…
08/29/2022 at 3:09 PM #199815Dax ..920 almost breached with hi 915 😁
Now if we go below 850, clear way towards 820…
or towards 980ishh on clear break of 920 and above on price holding and not dropping below 870
08/29/2022 at 5:02 PM #19983808/29/2022 at 9:21 PM #199848Hi Nicolas, cannot explain with code logic , wish I could, however, simple logic is that price has moved to the right forming new highs and lows…so what happened to these precious levels tested and broken isn’t valid anymore,if this makes any sense? In my chart I posted I have tried to mention by marking the ones we can remove but keep the ones that are yet to be tested etc…
-
AuthorPosts
Find exclusive trading pro-tools on