Quote from dandxg:
This is really funny, but I have been debating the ideas of MM, game theory, and stats for a good month now. Hopefully my post will add to this thread and not highjack it. I understand the basics of game theory, stats, and have read Tharp's book Financial Freedom.
So let's say you have a method that runs 2-1, 3-1, reward to risk with better than 50% closer to 70%. It's a descretionary method and I determined these stats by looking at 200 trades minimum manually backtesting. If I have 3 losing trades in a row, which my stats show is the max consecutive loss out of 200 do I take the next trade because it should be a winner? Or do I quit as I did because I was at max DD per contract ( I trade e-minins ). Since there is a degree of discretion in the trade set up, I stopped because I felt I was out of tune with the market that day. Do you agree? Tharp says that 200 samples is probably too small. I could have atleast 10 straight losers in 90% win over 100 trades. So which is right, which is better. A backest of many trades over atleast 30 over the last few weeks of give market condition. Look forward to some thoughtful replies.![]()
Dan
Examine why the trades didn't work out. The answer should illuminate next steps:
If your original analysis was correct (based on the systems entry signals) - stick with the system
If your original analysis was wrong - determine why and fix.
If you're unsure whether the decision to trade was "right" or "wrong" (as defined by your system) -- time to explicitly redefine the system to minimize the discretionary component.
A couple suggestions:
1) Keep a journal. The idea here is to develop a historical database for pattern recognition at a later date sometime in the future. You're winners should have something in common. As well as your losers...
2) Conventional wisdom suggests any system requires a logical rational as its success.
Why does your system work? What market, psychological or fundamental principle does the System exploit?
If theres no other reason than 'it backtests well', time to reevaluate the entire thing.
