Yes valid point. I favor Colo but it gets expensive. Good post!decided it was safer to rest thing on a larger entitites server (rithmics), as they are more robust to power/network outages
Yes valid point. I favor Colo but it gets expensive. Good post!decided it was safer to rest thing on a larger entitites server (rithmics), as they are more robust to power/network outages
Yes valid point. I favor Colo but it gets expensive. Good post!
Likely bad code.
Not necessarily. A fast market can jump a stoploss order. Even a stop loss needs a counter party to trade with. If everyone is running for the hills and price has moved far from your stop it may never fill.
This is a crazy strategy. I just saw your limit order. Any trading strategy needs to be aligned with the volatility of the financial instrument.
Your strategy attempts to avoid risk, which will never work. There is no reward without risk.
You must embrace risk, then go from there
).I don't have a time to go through the entire thread but upon reading the first few posts this is my comment:So my trading platform/system was trading for the first time in a fast market today (I shut it down for the last couple of days, out of fear). Market taught me a lesson, and exposed a flaw in my execution logic: The market will reject stop orders if the market is already below the stop price, leaving a position un-hedged. I should have known this.... but I didn't, and almost got bit. Fortunately, I was paying attention and was able to manually step in quickly and turned a 80 tick loss into a 20 tick gain (via luck, not skill).
Moral of the story.... be careful out there, especially when you're auto-trading and your system is walking into unfamiliar territory.
There are stop-orders for futures:
Stop Order Notes
- The stop order's trigger price is validated differently depending on the market state.
- During the Continuous market state, a Buy stop order must be > last trade price and a Sell stop order must be < last trade price. Absent a last trade price, the settlement price is used.
- During the Pre-Open and No Cancel market states, a Buy stop order must be > settlement price and a Sell stop order must be < settlement price.
2nd bullet is exactly my issue. I sent a bracket to Rithmic, my opening limit rested on the exchange and the legs of my bracket rested on rithmics servers until the open was filled. Once rithmic got confirmation of the fill, they sent my target and stop to the exchange. 1-2 milliseconds is all it took for me to miss. I didn't anticipate this being an issue, but I should have.
So my trading platform/system was trading for the first time in a fast market today (I shut it down for the last couple of days, out of fear). Market taught me a lesson, and exposed a flaw in my execution logic: The market will reject stop orders if the market is already below the stop price, leaving a position un-hedged. I should have known this.... but I didn't, and almost got bit. Fortunately, I was paying attention and was able to manually step in quickly and turned a 80 tick loss into a 20 tick gain (via luck, not skill).
Moral of the story.... be careful out there, especially when you're auto-trading and your system is walking into unfamiliar territory.
So curious what did you decide to do in such case? If I understand correctly, the exchange rejected the order because trigger price was outside of the protection range. I don't think there is anything you (or vendor) can do about it. My system re-submits but if I get three rejects (configurable), the strategy is suspended and manual involvement is required from that point.bad design on my part to not handle this
In Rithmic, go to Configure Brackets and check "on" the option to: "convert stops to market on reject".
the webinar I was talking about:
note: video is for trader pro but works the same for non-pro version.
hope that helps,
Greg