Rank: Newbie
Groups: Registered, Registered Users, Subscribers
Joined: 11/29/2008(UTC)
Posts: 5
|
I am having what seems a really stupid problem, and I am sure that the error is between the keyboard and the chair, but here it is anyway :)
I am having trouble with a very simple test.
Enter a trade when a > b. This gives false entries for the system that occur when a < b.
I went an extra step to create a custom indicator that has value 0 when a < b and 1 when a > b. The same erroneous errors occur.
This is the only entry criterion for the system (just to try to resolve this issue).
Any ideas where I should be looking?
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers, Unverified Users
Joined: 10/28/2004(UTC)
Posts: 3,111
Location: Perth, Western Australia
Was thanked: 16 time(s) in 16 post(s)
|
I'd start looking by looking at the codes defining 'a' and 'b', but then again, as you didn't post them it is very hard to do from here.
The next thing to analyse is the trade results to see when each trade was considered etc and then finally executed. If you're system is rapid-fire or hair-trigger, you might find trade delays are having you enter trades when it shouldn't.
The last thing to check is the position of these trades in relation to other trades. Are you really wanting to enter when 'a > b' or are you really wanting to enter when 'a crosses b' ??
wabbit [:D]
|
|
|
|
|
|
| Users browsing this topic |
|
Guest (Hidden)
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
