Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Well, you can enter positions with limit orders and just accept that sometimes you won't get filled. Fills on limit orders are mostly a problem when you want to get breakouts or when you absolutely insist on buying on the exact line of support or selling on the exact line of resistance.
Think logically about what you are trying to accomplish and then try and find methods that would work but can also be adapted to include some more "actual market" type of adjustments. For instance, rather than buying at support, buy at support + x ticks. Of course when buying / selling breakouts this type of adjustment may not work and market orders may be needed.
With regards to stops, I never use stop-limits. When I want to get out, I don't want to miss my stop just because I am quibbling over a tick.
Considering that your system is so sensitive to slippage, I can tell you right now that it won't work going forward. Have you run a backtest to determine whether the system is viable (in-sample / out-of-sample testing, etc..)? Gut feel tells me that the system won't stand up to a rigorous backtest.
If you want to pursue algorithmic trading, research Kevin Davey. He has a very good track record for the period he made public, has a book (which I have not read), posts here as kevinkdog and he also has a website where he helps people find systems that work.
I am not sure if you are still struggling with this topic, but here are a few things to keep in mind.
If you ever use a trailing stop or some sort of stop based on a condition that is called during bar updates, consider the time frame that it is running on. If you set this update on the OnBarUpdate method and you are using a larger timeframe 5 minutes, 1 minute, heck even 500 ticks may be too large and you may miss some of the price action that occurred in the more granular time frame. Try setting this at something very granular like 20-50 ticks, or better yet a different event handler like OnMarketData, this would chase the price a little faster and get you out quicker.
Also consider the benifit of a resting market order for your stop. I don't know if you are submitting your stop order as a SetStopLoss that gets held at the exchange, but this would likely get triggered better than if you have a condition called like.
if(condition = true)
{
ExitLong();
}
In a fast market you may get serious slippage with this approach. Also consider different instruments that have a lower spread. The ES is one of the worst because it has a 12.5 dollar spread that it will hit all market orders with, once you factor in slippage too it will kill you. Try the YM or NQ, these have far less slippage relative to their tick value and overall movement.
