Cost trigger of a guaranteed stoploss

Forums › ProRealTime English forum › ProRealTime platform support › Cost trigger of a guaranteed stoploss

Viewing 15 posts - 1 through 15 (of 15 total)
  • 03/08/2021 at 4:36 PM #163480
    Albaran

    Hi there,

    It’s all in the title; when is the cost of a guaranteed stop loss triggered?

    Two cases come to mind:

    a) A stoploss yielding a loss

    b) a stoploss yielding a profit

    And with which command is it triggered? Whenever using the stop command or only when using below kind of command:

    and not with below kind of command

    ?

    03/08/2021 at 5:12 PM #163495
    Nicolas

    Both will be Guaranteed Stop. A pending stop order is a stoploss and a stoploss is a pending stop order 🙂

    2 users thanked author for this post.
    avatar Albaran, avatar robertogozzi
    03/08/2021 at 5:15 PM #163496
    Albaran

    Okay thanks! It’s what I thought but I wanted to be sure of it 🙂

    06/04/2021 at 10:43 AM #171121
    Albaran

    Does a QUIT command also count as a garantueed stop loss if you toggle the use of garantueed stop losses when you launch your system?

    06/09/2021 at 9:44 PM #171513
    XORANDNOT
    Albaran wrote:

    And with which command is it triggered? Whenever using the stop command or only when using below kind of command:

    Set stop loss x

    Sell at fulllongstop stop

    A bit carefulness is needed. “Sell at xx stop” only triggers a guaranteed stop, when this has been activated before by “set stop loss x”, because in this case all stops (whenever they are changed) for a position will be guaranteed.

    If you don’t use “set stop loss x” or similar commands at all in your code, all stop losses set by “sell at xx stop” will NOT be guaranteed !

    “Quit” only closes all currently open positions at market price and therefore does not execute any stop loss.

    1 user thanked author for this post.
    avatar Albaran
    08/24/2021 at 6:10 PM #176123
    Albaran

    Just to be sure, IG says that the cost of a guaranteed stop loss is +1pt if triggered.

    So to be all sure, it’s cost = 1pt. * number of contracts * (value of contract or value per point), right?

    And is it + 1pt. regardless of the underlying you’re trading in? I want to code the cost into the algorithm..

    (I couldn’t really find any other information other than the +1pt. on the IG website hence why I’m asking it here)

    08/24/2021 at 6:27 PM #176124
    Albaran

    Also, is there a way to make use of the guaranteed stoploss with “DEFPARAM cumulateorders = True” ?

    PRT says you either have to change the above into false or make use of other types of stops..

     

    08/26/2021 at 8:00 AM #176252
    JS

    When set DefParam CumulateOrders to False it only prevent your system to execute more than one (1) trade in the same direction.

    08/26/2021 at 11:59 AM #176288
    Albaran
    JS wrote:

    When set DefParam CumulateOrders to False it only prevent your system to execute more than one (1) trade in the same direction.

    Let me rephrase my question: “Is it possible to make use of a guaranteed stoploss of the type “$LOSS” with DefParam CumulateOrders = True ?”

    PRT says that the two of them are not compatible and according to @XORANDNOT, in order to to benefit from the guaranteed stoploss protection, you need to make use of the command “set stop loss x”.

    So my question is whether or not there’s a way to circumvent this incompatibility by coding it in a different way?

     

     

    08/26/2021 at 1:35 PM #176297
    JS

    I don’t think you can code it in a different way when PRT says that the combination of “DefParam CumulateOrders = True” and guaranteed stop loss orders are not compatible.

     

    08/26/2021 at 3:15 PM #176302
    GraHal

    I would hazard a guess that hardly anyone on here uses Guaranteed Stops, hence why there are not many answers forthcoming?

     

    08/26/2021 at 4:03 PM #176307
    JS

    @GraHal: Maybe because it is a special case of CumulateOrders combined with Guaranteed Stops.

    I can imagine that there is a (IG) limit to the amount of contracts in combination with Guaranteed Stops or a limitation between (cumulated) margin and Guaranteed Stops…etc.

    08/29/2021 at 6:18 PM #176443
    XORANDNOT
    Albaran wrote:

    Let me rephrase my question: “Is it possible to make use of a guaranteed stoploss of the type “$LOSS” with DefParam CumulateOrders = True ?”

    PRT says that the two of them are not compatible and according to @XORANDNOT, in order to to benefit from the guaranteed stoploss protection, you need to make use of the command “set stop loss x”.

    So my question is whether or not there’s a way to circumvent this incompatibility by coding it in a different way?

    If you want to have an exact answer, try it out on a very short time scale (1 minute or 10 seconds) in your demo account. This is what demo is made for.

    08/30/2021 at 9:45 AM #176471
    GraHal

    I was thinking the same, please let us know the results / outcome Albaran

    10/15/2021 at 11:10 AM #179727
    Albaran

    @GraHal: it’s as @XORANDNOT says..

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

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
guaranteed trailing stop with indicator
stoploss not put in place
stoploss on a moving average
trailing stoploss problems

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