System Error Message when Probacktesting

Forums › ProRealTime English forum › ProOrder support › System Error Message when Probacktesting

  • This topic has 25 replies, 4 voices, and was last updated 4 years ago by avatarIRP.
Viewing 15 posts - 1 through 15 (of 26 total)
1 2
  • 01/11/2020 at 12:14 PM #116419
    IRP

    Greetings …

    I have been a user of PRT for more than a year and consider myself at least an average user (haven’t looked into coding yet) being able to set up trading programs made possible with PRT’s ease of use.

    yesterday, I proceeded to make another program, and, inexplicably, after running the Backtesting, the system gave an error message as per attached pic.  This error message apepars in the simplest of programming entry and exit conditions and am perplexed as to why it happened.

    This message is generated regardless of entry and exit conditions.  I even place an entry condition akin to: “if current price is greater than price 20 periods ago”, Enter trade.  Exit condition = if W%R less than previous W%R, exit trade.  I have tried 4 other trading scenarios with similar error messages.

    Any help would be most welcome.

     

    01/11/2020 at 1:16 PM #116422
    GraHal

    Easiest way for you and for us to spot the problem would be for you to post your System code on here.

    I would then try your code on my Platform.

    Also others may spot the problem in your code straight away.

    01/11/2020 at 1:53 PM #116424
    Nicolas

    What platform version? Timeframe used and instrument please?

    01/13/2020 at 2:10 PM #116646
    IRP

    Dear Nicolas,

    Thanks for reaching out!

    The instrument is US TECH 100 / time frame is 1 minute (or any time frame for that matter) / version = 10.3.  I don’t code, I used the interface that lets you bypass the need for coding and this happens with the most simple automated trading / code set up.

     

    Best regards,

     

    01/13/2020 at 2:22 PM #116649
    IRP

    Hello GraHal,

     

    Thanks for reaching out … this issue happens with any automated generated code (that worked previously in other times) and during a multitude of different time intervals tested.  I don’t think it is the question of spotting the problem with coding … I have developed and successfully tested dozens and dozens of PRT programs, have finance background and know enough about the indicators to know that the criteria for entry and exit are not likely to be the problem.  This happens even with the simplest of code, such as: If price (Current) > Price (Previous) ===> enter trade and the same principle for exit … hope this gets solved soon.  BTW, version = 10.3

    Have a good day!

    1 user thanked author for this post.
    avatar GraHal
    01/13/2020 at 3:08 PM #116658
    GraHal

    Others appear not to be experiencing the same problem that you are so I thought trying your code would be a good starting point?

    How would you want me to proceed then … in order to help you?

    If I make a simple System with the Assisted Creation tool and I do not get the problem that you are getting what will my efforts prove or how will it help you ?

    I will however, do above and report back shortly.

    01/13/2020 at 3:13 PM #116659
    GraHal

    There we are it worked … see attached.

    Please you copy and past the code below into your Platform and see what you get 🙂

     

    01/13/2020 at 3:16 PM #116661
    GraHal

    Here are results for the US Tech 100 on 1 min TF as that what you stated above

    01/13/2020 at 5:27 PM #116668
    Nicolas

    @GraHal

    First time I came across that kind of period for the MACD?

    MACD[37/3, 77/3, 9]

    Why divided by 3?


    @IRP

    Any chance to share the code of your simple conditions please? In order to isolate the problem, it is necessary for us to replicate the same issue! thanks.

    01/13/2020 at 5:33 PM #116669
    GraHal
    Nicolas wrote:

    First time I came across that kind of period for the MACD?

    Yeah weird eh! It came out that way from the Easy Creation Tool, I did nothing.

    01/13/2020 at 10:19 PM #116702
    Vonasi

    I see that error message sometimes if my internet or wifi is weak or it is a weekend and lots of other people are on the local internet! Sometimes the connection is weak for too long during a back test and the back test stops as the connection to the PRT servers is lost I guess. Are you on a good internet connection?

    1 user thanked author for this post.
    avatar GraHal
    01/14/2020 at 3:04 AM #116714
    IRP

    Hey Vonasi!

    Thanks for the feedback.  Just checked, and it’s 94.5 mbps.

    01/14/2020 at 3:14 AM #116715
    IRP

    Hello there … I just proceeded as per your suggestion and error still occurs.

    I have used the itnernet connection of my neighbor as well and error still occurs.  Obs: my speed is 95.4 mbps.

    01/14/2020 at 3:16 AM #116716
    IRP

    Hello GraHal,

     

    The simple code I used follows for your review.  Many thanks!!!!

     

     

    01/14/2020 at 3:17 AM #116717
    IRP

    The above code was done just for testing purposes just to see if I would get an error message or not (got the error message, sadly speaking)

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

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
parsing error when call value from indicator
3-10 oscillator swing trading system
a completely simple nas macd system
auto tradeing system
automatic trading error: instruction ” graph” may not be used
avoid return of a value when “0”
back testing error as you chack longer periods
backtests not saving results when platform closed and reopened
bollinger band error
cascade ordering system

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