Multiple Running Algo and margin requirement

Forums ProRealTime English forum ProOrder support Multiple Running Algo and margin requirement

Viewing 12 posts - 1 through 12 (of 12 total)
  • #175499
    gfx

    Hello all,

    I just added a second trading system to my IG PRT account.

    I wanted to keep both systems independant to avoid over coding or facing issues that I would not have keeping them appart.

    But, I noticed that once the first one was in position, any triggered order from the second one would be rejected by IG ( which I understand due to margin requirement).

    Thing is that once the order is rejected, the trading system which triggered the order it is stopped by IG.

    Have you already faced this issue ? Is there any work around ?

    thks.

    Gfx

     

     

    #175500

    If it’s margin related, then it’s an issue  you only can work out by funding your account.

     

    #175506

    If it’s on your Demo Account then you can easily increase Capital by adding more virtual money up to £10m.

     

    #175507

    Or reduce your contract size / exposure on each of your strategy, if possible.

    #175514
    gfx

    ok thks. So I understand that there is no work around to having both systems in a single one and to manage dual triggers.

    Having two accounts, one for each, or allocating 50% of account size to each will definitively reduce the profits.

    Indeed, most of the time, they are not supposed to open trade at the same time.

    Thks for helping.

    #175536

    You can of course, compile the 2 strategies into a single one. You’ll have to set the required conditions to only trade one strategy at a time.

    #175539
    #175540

    Sorry, the link seems not to work.

     

    #175541
    #175544

    Here is a copy of my post.

    You can assembly all of your strategies into a bigger file.

    “DEFPARAM CumulateOrders = false” will do the hard job!

    Of course you may need to name variables in different ways, say, a1s1 or cond1s1 for the first strategy, then a2s1/cond2s1….. a1s2/cond1s2 for the second strategy etc….

    You may name a variable StrategyID = 0 when NOT ONMARKET, then set it to any number you want each buy/sell is executed so you know which strategy was triggered.

    Example:

     

    #175546
    gfx

    Thks for the framework.  DEFPARAM CumulateOrders = True shall still be ok if I use the StrategyId variable. Correct ? Indeed, one strategy requires scaling in with is not possible if I set DEFP to False.

    Won’t StrategyId be reset at each candle ? I remember that there was an issue with PRT as far as keeping value persistent in variables.

     

     

     

     

    #175551

    Yes with DEFPARAM = True, you can decide to accumulate positions or not with (NOT) ON MARKET.

    As to variables, use different names for each strategy, but for StrategyID.

    You can even set different trading and closing hours for each strategy.

    Whatever you want to make common to ALL strategies needs to be written outside them.

     

Viewing 12 posts - 1 through 12 (of 12 total)

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