Screener a week late?
Forums › ProRealTime English forum › ProScreener support › Screener a week late?
- This topic has 5 replies, 3 voices, and was last updated 5 years ago by grimweasel47.
-
-
09/14/2019 at 4:23 AM #107523
Hi Guys
I have an issue with the code below in that for the Engulfing and Outside bars the screener is displaying results a week late? Ie it searches for a price action signal but doesn’t display the most current weekly candle, but the one prior? Yet when I use the same code in a standalone screener (ie just engulfing and outside bars) it reports the correct, latest bar in the results? Any help would be apricated as I use this scanner each weekend on the UK shares universe!
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152//Bullish/Bearish Candle Detector//Detection of Hammer / Shooting StarHammer = (((high - low)>3*(open -close)) and ((close - low)/(.001 + high - low) > 0.6) and ((open - low)/(.001 + high - low) > 0.6))Shooter = (open[1] < close[1] and open > close[1] and high - max(open, close) >= abs(open - close) * 3 and min(close, open) - low <= abs(open - close))//shooter wickIndy6 = (close = highest[10](high[0]))//Hammer WickIndy7 = (close = lowest[10](low[0]))//detect BUOBBUOB =((close[1] < open[1]) and (open[0] < low [1]) AND (close > open[1]) and (close [0] > high [1])and (close > open))//detect BEOBBEOB =((close[1] > open [1]) and (close[0] < low [1]) AND (open[0] > high[1]) and (close [0] < low [1]) and (close < open))//detect BEEBBEEB = ((close[1] > open [1]) and (open[0] >=close [1]) and (close[0] < open [1]) and (close < open))//detect BUEBBUEB = ((close[1] < open[1]) and (open <= close[1]) and (close > open[1]) and (close > open))C1 = BUOBC1a = BUEBC2 = BEOBC2a = BEEBC3a= HammerC3b= Shooter//Detection of IB BullIBBull = (open[1] > close[1] and close > open and close <= open[1] and close[1] <= open and close - open < open[1] - close[1] )//Detection of Bear IBIBBear = (close[1] > open[1] and open > close and open >= close[1] and open[1] >= close and open - close > close[1] - open[1] )// Close greater or less than 10 emaMAH = (close < exponentialaverage[10])MAL = (close > exponentialaverage[10])///Screener for Price ActionScreener [c1 and MAL]((close/DClose(1)-1)*100 AS "%VAR" )//detect BUOBScreener [c1a and MAL]((close/DClose(1)-1)*100 AS "%VAR" )//detect BUEBScreener [c2 and MAH]((close/DClose(1)-1)*100 AS "%VAR" )//detect BEOBScreener [c2a and MAH]((close/DClose(1)-1)*100 AS "%VAR" )//detect BEEBScreener [c3a and MAL and Indy7]((close/DClose(1)-1)*100 AS "%VAR" )//detect HammerScreener [c3b and MAH and Indy6]((close/DClose(1)-1)*100 AS "%VAR" )//detect Shooterscreener [IBBull]((close/DClose(1)-1)*100 AS "%VAR" )//detect Inside Bar with bull trendscreener [IBBear]((close/DClose(1)-1)*100 AS "%VAR" )// detect IB with bear trendAnd yet here is the standalone screener?
1234567891011121314151617181920//detect BUOBBUOB =((close[1] < open[1]) and (open[0] < low [1]) AND (close > open[1]) and (close [0] > high [1])and (close > open))//detect BEOBBEOB =((close[1] > open [1]) and (close[0] < low [1]) AND (open[0] > high[1]) and (close [0] < low [1]) and (close < open))//detect BEEBBEEB = ((close[1] > open [1]) and (open[0] >=close [1]) and (close[0] < open [1]) and (close < open))//detect BUEBBUEB = ((close[1] < open[1]) and (open <= close[1]) and (close > open[1]) and (close > open))MA1 = exponentialaverage[10](close)C1 = close > MA1C2 = Close < MA1Screener [BUOB and C1]Screener [BEOB and C2]Screener [BEEB and C2]Screener [BUEB and C1]All I did was copy the above code into the main price action screener?
Many thanks in anticipation of help!
09/14/2019 at 9:40 AM #107530Do you have end-of-day-data?
If yes, then on the weekly TF you’ll have data updated when each weekly candlestick closes, while for daily TF when a daily candlestick closes.
09/14/2019 at 2:12 PM #107540Hi Robert
Yes, I’m using end of day data as I trade shares on a weekly basis. I couldn’t understand why one scanner showed the most previous week’s candles and the other two weeks prior, yet both scanners as using the same code as far as I can see??
09/14/2019 at 2:28 PM #107541Why are you using all those SCREENER instructions at the end, just one is allowed.
I’m afraid the last one overrides the previous three.
09/16/2019 at 10:00 AM #10768009/16/2019 at 12:01 PM #107702Robert – thanks so much!! That solved the issue. All these years using ‘screener’ and I didn’t one you should only have one screener line command per script. That totally explains why it was never working properly! Thanks again!
I have replaced all the screener lines with one command line that seems to work much better:
1Screener [(c1 and c5) or (c2 and c6) or (c3a and C5 and Indy7) or (c3b and c6 and Indy6) or (DCC and Indy6) or (PL and Indy7) or (IBBull and C5) or (IBBear and C6) ]((close/DClose(1)-1)*100 AS "%VAR" ) -
AuthorPosts
Find exclusive trading pro-tools on