开云体育

10 seems to me above IB criteria for an efficient ordering, try staying below 5.
Also the rate of your change have an impact: Think "human", IB is very tolerant to anything that match human pace.

Why do you need to change so frequently a TRAIL order ?
Looks like you expect IB to react faster than your algo, but somewhere this is a catch 22 situation because IB may react too fast too. You may have to consider improving speed of your code and directly send a sell at market or hedging your position by going opposite? then release both, this increase trades and may improve IB view of your efficiency (I never try hedging for that reason).

Seems close to this thread?? /g/twsapi/topic/80863099#46628
Look to me that the link to IB article is broken, try search with keyword/sentence is "Order Efficiency Ratio" or "Optimizing Order Efficiency"

IB require some "efficiency" in the management of your orders, IB even give you report tool to analyze your account order efficiency (or lack thereof).

This is a Pandora-box issue because there are a lot of tradeoff behind it, many of theses tradeoffs require strategical choices: Speed versus flexibility versus safety when lack of liquidity etc ...
Suggestion: study IB offers first, . They do a lot for you and are well integrated.

Did you look at the sample Program.py provided w/ the API? It seems to imply you can just pass an empty string. I wonder why it's not the default argument?

Anyway... it's interesting that there's basically . Thanks for point it out.

Perhaps a little experimentation w/ a paper trading account is in order?

-Good luck

I forgot to attach a screenshot of what the order looks like on TWS, sorry for the double post.

So I took all your advice and I finally got it to work on paper. Will be testing it live tomorrow. Really appreciate all the help and advice.

For the next iteration, I am trying to replace trailing stop with a MIT and STP order, so that I can take profit on the upside and get protection from the downside until the cash out time at 3:50.

I added replaced the code accordingly, I looped over my tickers, their prices etc, but I get this error now, ERROR 490 104 Cannot modify a filled order. I have been trying it on paper the whole day but I only can seem to get the first ticker to fill properly, I don't know why it worked fine when it was just a trailing stop loss.

Am I understanding how STP and MIT orders work?

The first order gets sent properly (buy, stop market, market if touched and exit at 3:50 for AAPL), but the subsequent orders cascade down as a subset of the first orders, even different tickers. I have never seen this before, not sure what I am doing wrong.

I am doing a loop exactly like this . Any ideas?

def BracketOrder(self, parentOrderId:int, openinglimitPrice:float, quantity:Decimal, takeProfitPrice:float, stopLossPrice:float, timeCancel:str, timeSwitch:str, adaptive_type:str):

    # 1st part: Buy Adaptive Algo order
    opening = Order()
    opening.orderId = parentOrderId
    ....
    opening.conditionsCancelOrder = True 
    opening.conditionsIgnoreRth = True
    algo.FillAdaptiveParams(opening, adaptive_type)
    .....
    timeCondition = TimeCondition()
    timeCondition.time = timeCancel
    timeCondition.isMore = True
    opening.conditions.append(timeCondition)

    # 2nd part: Take profit if a price is touched
    takeProfit = Order()
    takeProfit.orderId = opening.orderId + 2
    takeProfit.action =  "SELL" if quantity > 0 else "BUY"
    takeProfit.orderType = "MIT"
    takeProfit.totalQuantity = abs(quantity)
    takeProfit.auxPrice = takeProfitPrice
    takeProfit.parentId = parentOrderId
    takeProfit.tif = "GTC"
    takeProfit.transmit = False

    # 2nd part: Stop loss
    stopLoss = Order()
    stopLoss.orderId = opening.orderId + 3
    stopLoss.action =  "SELL" if quantity > 0 else "BUY"
    stopLoss.orderType = "STP"
    stopLoss.totalQuantity = abs(quantity)
    stopLoss.auxPrice = stopLossPrice
    stopLoss.parentId = parentOrderId
    stopLoss.tif = "GTC"
    stopLoss.transmit = False

    # # 3rd part: Sell market order
    closing = Order()
    closing.orderId = opening.orderId + 4
    ...
    closing.parentId = parentOrderId
    closing.tif = "GTC"
    closing.transmit = True
    closing.conditionsCancelOrder = False
    closing.conditionsIgnoreRth = True

    timeCondition = TimeCondition()
    ....
    closing.conditions.append(timeCondition)

    bracketOrder = [opening, takeProfit, stopLoss, closing]
    return bracketOrder

On Tue, Jun 27, 2023 at 12:28 PM, omgwtfsalty@... wrote:

Why should I ignore the Rth, I don't want to trade beyond the regular trading hours, unless there is another reason?

It's a poorly named and confusing variable for the same reason it's bad to use double-negatives. But, if you read the description carefully, you'll probably want to set it to True. They should have named it something like conditionsValidOutsideRTH.

: Indicates whether or not conditions will also be valid outside Regular Trading Hours.

Hi Jürgen, are you saying that because the opening orders and exit orders might be too close to each other? Then yeah probably I should make the opening order expire around 3pm.

Why should I ignore the Rth, I don't want to trade beyond the regular trading hours, unless there is another reason?

If i set the opening order to expire at 3pm and the closing order to activate at 3:50, even if there is a partial fill, my partial order will be taken care of correct?