IntradayBarIndex always zero
Forums › ProRealTime English forum › ProScreener support › IntradayBarIndex always zero
- This topic has 22 replies, 3 voices, and was last updated 5 years ago by Nicolas.
-
-
08/23/2018 at 5:17 AM #78830
Not sure what I’m doing wrong, but I could not figure out why my filter was not returning results with the following code:
timeframe(2 minutes)
if (IntradayBarIndex > 14) then
….
When I tested for IntradayBarIndex (using SCREENER [Filter](IntradayBarIndex) ), I discovered that it’s always zero?
Thanks for any help.
08/23/2018 at 4:42 PM #7886408/23/2018 at 11:08 PM #78883There’s a lot of code that goes into Filter, but it doesn’t really matter what Filter is, because I was only using that as a test to reveal what value IntradayBarIndex was.
The example was to prove that the previous code – if (IntradayBarIndex > 14) then – never returns any results.
08/24/2018 at 8:18 AM #78892I can’t replicate your issue. Please find below 2 tests in ProScreener. First one return all intradaybarindex numbers without any condition, second one returns intradaybarindex if it is superior to 14.
On a daily timeframe, there is no intradaybarindex.
Do you have live data subscription for the stock list you are scanning?
08/24/2018 at 3:28 PM #78969Thanks Nicolas, I’ll try that Monday.
Yes I do have a live data subscription through IG on the ASX.
08/30/2018 at 3:07 AM #79349Here are the results Nicolas.
Not sure what’s going on?
08/30/2018 at 8:39 AM #7935708/31/2018 at 1:24 AM #79439I hadn’t set a timeframe in code, but as you can see from the screen dump, my charts are displaying in 2 min bars.
That said, I changed the code as follows and got the same result:
timeframe(2 minutes)
test=1
SCREENER[test](intradaybarindex)08/31/2018 at 7:21 AM #7944608/31/2018 at 7:32 AM #79449That was set to daily, and if I change it to 2 minutes, IntradayBarIndex returns a value.
My screening code uses multiple time frames. What is the purpose of the function “timeframe”, if when I set to 2 minutes as in the above example, it does not produce the expected results?
08/31/2018 at 7:39 AM #79450That’s what I thought. I do not really have an answer to the fact that this instruction does not increment in this case, sorry. But we finally managed to find the problem .. If you need help to review the screener code for it to fit, I can help.
08/31/2018 at 7:43 AM #79451I am not sure we have found anything – surely this is a bug?
You have not explained why I cannot use, or rely on this function when I use the timeframe function.
The problem I had at the beginning of this thread still exists. Do you have a workaround?
08/31/2018 at 8:44 AM #79453surely this is a bug?
Yes this does sound like a bug and needs reporting to PRT as this is why we are testing (by usage) MTF on the Demo Platform??
Please send a Technical Report to PRT (unless Nicolas has a different viewpoint etc).
08/31/2018 at 9:54 AM #79457You have not explained why I cannot use, or rely on this function when I use the timeframe function.
Surely because I don’t know !? that’s what I explained in my previous post.. 😐
Anyway, to get the intradaybarindex we know that we need to launch ProScreener in an intraday timeframe. So, if your screener rely also on Daily TF conditions, just put them under a TIMEFRAME(daily) instruction. If it is not operating as intended, please post the code, as I will not be able to sort it out without it. Thank you.
And .. for what it’s worth, I sent a question to ITF to get answers about this limitation. Once I get useful infos, I let you know.
09/06/2018 at 12:17 PM #79876 -
AuthorPosts
Find exclusive trading pro-tools on