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:
Set stop loss x
and not with below kind of command
Sell at fulllongstop stop
?
Both will be Guaranteed Stop. A pending stop order is a stoploss and a stoploss is a pending stop order 🙂
Okay thanks! It’s what I thought but I wanted to be sure of it 🙂
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?
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.
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)
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..
JSParticipant
Senior
When set DefParam CumulateOrders to False it only prevent your system to execute more than one (1) trade in the same direction.
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?
JSParticipant
Senior
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.
I would hazard a guess that hardly anyone on here uses Guaranteed Stops, hence why there are not many answers forthcoming?
JSParticipant
Senior
@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.
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.
I was thinking the same, please let us know the results / outcome Albaran
@GraHal: it’s as @XORANDNOT says..
