Long Time to run System Code Causes Rejection?

Forums › ProRealTime English forum › ProOrder support › Long Time to run System Code Causes Rejection?

Viewing 15 posts - 16 through 30 (of 30 total)
1 2
  • 06/28/2023 at 8:47 AM #216895
    PeterSt

    Here is the link from Laurent (this link hopefully works, his die not) :

    https://www.prorealcode.com/topic/systeme-de-trading-arrete-a-cause-dun-manque-dhistorique/

    06/28/2023 at 9:05 AM #216897
    GraHal
    PeterSt wrote:

    Yeah, that is why my systems with 4000+ lines of code also run.

    Code with 4000 lines could take less time to run than code with 400 lines. Calculations etc within 400 lines may tip time to run over a critical threshold and so my 400 line System gets Rejected whereas your 4000 line System is fully executed.

    06/28/2023 at 9:07 AM #216898
    GraHal
    PeterSt wrote:

    link from Laurent

    My Systems are running on DFB / SB and so no problems with expired Futures as Laurent.

    06/28/2023 at 9:38 AM #216901
    PeterSt

    Did you make that Technical Report ?
    PRT asks for it and I can’t provide it as I have my systems running (after trying hard).

    I agree about the 4000 vs 400 etc.

    06/28/2023 at 10:16 AM #216906
    GraHal

    I’m getting a M6 TF System to fail 3 times in succession (twice done already) for insufficient history then I’ll submit a Technical Report.

    So you want me to type in text  @Johan  (space after text??) at bottom of the Tech Report??

    06/28/2023 at 10:25 AM #216907
    PeterSt

    You can just as well type something like “For Johan”.

    Point is : He is waiting for it, and IG should skip the issue (I am not talking to IG, but PRT(-IB)).

    Let it fail one time should be sufficient. 🙂

    Thanks !
    (we all help each other)

    06/28/2023 at 10:33 AM #216909
    GraHal

    After failing 3 times in succession, I sent this as part of the Tech Report …

    Hello
    Fao: Johan at PRT.

    The Strategy above gets Rejected repeatedly for ‘Insufficient Historical Data’ (you will know the full Rejection wording).

    Please can you advise what part of the code is causing the Rejection and how to fix it?

    https://www.prorealcode.com/topic/long-time-to-run-system-code-causes-rejection/page/2/#post-216906

    Above Discussion put the problem in context.

    Many Thanks
    GraHal

    06/28/2023 at 10:45 AM #216913
    PeterSt

    Passed on …

    1 user thanked author for this post.
    avatar GraHal
    07/11/2023 at 8:03 AM #217527
    PeterSt

    I only now realise that I restarted systems on the 6th of July, and yesterday as well. All went in one go. So this issue should be solved.
    (not that I was told by PRT)

    07/11/2023 at 9:01 AM #217530
    GraHal
    PeterSt wrote:

    All went in one go. So this issue should be solved.

    All started in one go, or all stopped in one go??
    Why do you think this Issue should be solved?

    See here …

    https://www.prorealcode.com/topic/autotrading-keeps-failing-preloadbars-not-working/

     

    07/11/2023 at 10:40 AM #217533
    GraHal

    Same System as I submitted to PRT via Technical Report is still being Rejected (just twice!) due to ‘Insufficient Data History’ … so this Issue hasn’t been solved.

    07/11/2023 at 8:26 PM #217545
    GraHal

    I’ve had a thought that ‘Rejection due to insufficient historical data’ may not be caused by the PRT Platform / Servers?

    It may be that the IG Servers have a time limit for execution of code, go beyoond this cut-off and the System gets Rejected.

    Just an idea / thought, I have no basis for above.

    Nothing back from PRT since an acknowlegement on 28 June after I submitted a Technical Report.

    07/11/2023 at 10:22 PM #217546
    JS

    I think the problem has nothing to do with the IG servers because all our algos run on the PRT servers. From the PRT servers, only the orders are sent to the broker (IG servers). I personally think that the PRT servers are overloaded and that PRT prioritizes… like demo versus live, algos that use a lot of historical data versus little historical data…(at startup)…

    The capacity of the PRT servers is not unlimited and who has priority…?

    07/12/2023 at 4:57 AM #217553
    PeterSt

    I had it on PRT-IB (Live) …
    It could theoretically (?) explain why it does not seem to bother me any more ? But hard to say because maybe I was just lucky (like out of a few dozen attempts 4 started eventually on the 28th).
    I started 3 systems since July 6 and they all went/stayed  in at the first attempt.
    I never had to (re)start a system on PRT-IG in this period of time.

    07/14/2023 at 4:47 PM #217669
    GraHal

    I’m 98% sure that the Rejection I’ve had (dozens of times on same System) with the reason given as ‘Insufficient Historical Data’ is meaningless / does not apply (in my case / this System).

    See here for why I have said above.

    https://www.prorealcode.com/topic/supertrended-moving-averages-from-tradingview/#post-217668

    Time will tell and I will report back if any change.

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 30 total)
1 2

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
long time below ema50
long time to launch prorealtime
rejection errors at top of running screen – waste of space and time!
run time variables
time of candle opening vs time of candle closing
“multi time frame macd divergences” screener
1 short and 1 long per day max
2 trading strategies in one system
6 jan 24 prt not available – too long to respond
a completely simple nas macd system

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