The optimizer results show all results as 0 / 0% for Gain

Forums ProRealTime English forum ProOrder support The optimizer results show all results as 0 / 0% for Gain

Viewing 8 posts - 1 through 8 (of 8 total)
  • #88348

    Hi @nicolas, I’ve been having problems with the optimizer in PRT for the last 2-3weeks. The results show all results as 0 / 0% for Gain etc. It’s not my code because the problem occurs with even a simple test code (e.g. 2MA) – see screenshot below

    Is anyone else having this problem? I’ve submitted a help request to PRT and IG and waiting for a response but it’s taking them a long time… so I thought I’d check with you in case it’s a known issue?

    Maybe I need to roll back to an older version of Java?

    any help would be appreciated, thanks !

    #88367

    I moved your post to a new topic.

    Could you post a picture of your variables optimization window?

    What happen if you replace the “yyy” with a real number and without optimizing (as a normal backtest)?

    1 user thanked author for this post.
    #88370

    I was having the same problem a while back and seem to recall that I worked out that the problem was due to position sizing with decimal places. If a position size of 1 is used then results were displayed correctly but a position size with any decimals resulted in the zero results optimization window, I think I sent a report!

    2 users thanked author for this post.
    #88371
    #88390

    Problem solved !! thanks @Vonasi

    I changed position size from 0.1 to 1 and it all works fine again.

    On a related note, I’m live-trading with small sizes and I can’t set Max size to be <1 which is a bit worrying, so I will raise this with IG and PRT support

    thanks to you both – Nicolas and Vonasi – for your help!

    #88406

    It would be nice if PRT could fix this bug as it would be good to be able to optimize strategies with variable position sizing using decimal places. Being able to adjust position size based on perceived or calculated risk is a handy tool to be able to use but we can’t do this at the moment due to this bug.

    #88570

    I made a technical report referring to this topic.

    1 user thanked author for this post.
    #93931

    FYI, this issue has been fixed and deployed in the current version.

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

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