Startup ATL + OBV = Wickoff+ Weinstein
Forums › ProRealTime English forum › ProScreener support › Startup ATL + OBV = Wickoff+ Weinstein
- This topic has 25 replies, 7 voices, and was last updated 4 years ago by leoulve.
-
-
11/04/2019 at 8:43 PM #112094
Hello
To discuss about the screener
The idea is to find a startup bottom by screening volume activity.
Even with this code modification, sometime the condition
ATL + OBV condition1234567891011121314151617181920212223//ATL All time low identificationATL = lowest[BarIndex](low)//for i = 1 to barindex// If low[i]<ATL or ATL=0 then// ATL=Low// else// ATL=ATL[1]// Endif//Next//High volume activitymyOBV = OBV(close)avgOBV=average[20](myOBV)stdevOBV=2*std[20](myOBV)BollUp = avgOBV+stdevOBV//ATL zone and volume activityc1=close<2*ATLc2=myOBV>BollUPscreener[ c1 and c2 ]11/04/2019 at 8:52 PM #112098Basically
The idea is coming from this lecture from Wyckoff, Weinstein
https://speculateurmalin.fr/comment-stan-weinstein-analyse-un-graphique/
11/04/2019 at 9:31 PM #11210911/05/2019 at 9:44 AM #112159Firstly, try this small modification to be sure ProScreener isn’t stopping on the first barindex:
123456789101112131415//ATL All time low identificationATL = lowest[max(1,BarIndex)](low)//High volume activitymyOBV = OBV(close)avgOBV=average[20](myOBV)stdevOBV=2*std[20](myOBV)BollUp = avgOBV+stdevOBV//ATL zone and volume activityc1=close<2*ATLc2=myOBV>BollUPscreener[ c1 and c2 ]1 user thanked author for this post.
11/05/2019 at 12:34 PM #112191Hello,
The idea that I applied to evaluate the actions is based on the application of a macd to the Obv, with a configuration (10,20,10), and on the obv macd I apply some bolliguer bands. In this way the possible changes are very well detected.11/05/2019 at 1:06 PM #11219711/05/2019 at 8:54 PM #112233Hello,
The idea that I applied to evaluate the actions is based on the application of a macd to the Obv, with a configuration (10,20,10), and on the obv macd I apply some bolliguer bands. In this way the possible changes are very well detected.
Hi JJ Tec could you share a graph , that I can see and understand your point?
11/05/2019 at 8:59 PM #112234Is there a minimum time period to consider an accumulation phase as valid?
Hi @Nicolas
There is no minimum of time period, it can be very fast or very slow.
For the code modication, this test give the same result , the problem doesn’t come from the BarIndex
test12//ATL All time low identificationATL = lowest[max(1,BarIndex)](low)11/06/2019 at 9:42 AM #11224711/06/2019 at 11:41 AM #112257The idea I have is to apply the Chaikin flow calculation formula, to the OBV, but using as periods 10 and 20. One of the problems I see in the OBV is that it counts the volume based on the closing price, but I think that It is more appropriate to adjust the sum based on whether the price is above 50% of the total range. On the other hand, the volume may lead to a mistake, so perhaps, capitalization should be used (closing * volume).
11/06/2019 at 12:03 PM #11226111/06/2019 at 12:12 PM #11226311/06/2019 at 12:20 PM #11226511/06/2019 at 5:23 PM #11228011/07/2019 at 8:08 PM #112370Thanks
But I don’t understand, do we need to recalculate the OBV or can we use the function already programmed by prorealtime?
The problem comes that screener indicates stocks that are not between ATL and 2 ATL.
And I don’t understand where the problem comes from
1 user thanked author for this post.
-
AuthorPosts