IntradayBarIndex always zero

Forums ProRealTime English forum ProScreener support IntradayBarIndex always zero

Viewing 15 posts - 1 through 15 (of 23 total)
  • #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.

    #78864

    What is “Filter”? I’d like to replicate but kind of difficult without the whole screener code.

    #78883

    There’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.

    #78892

    I 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?

    #78969

    Thanks Nicolas, I’ll try that Monday.

    Yes I do have a live data subscription through IG on the ASX.

    #79349

    Here are the results Nicolas.

    Not sure what’s going on?

    #79357

    What timeframe please?

    #79439

    I 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)

    #79446

    I was talking about the chosen timeframe in the dropdown list in the ProScreener window. Please.

    #79449

    That 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?

    #79450

    That’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.

    #79451

    I 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?

    #79453

    surely 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).

    #79457

    You 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.

    #79876

    The correct intradaybarindex incrementation in other timeframes than the default one, should be fixed in a next update.

    1 user thanked author for this post.
Viewing 15 posts - 1 through 15 (of 23 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login