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)
I had a bunch of erratic outcomes in backtesting so I stripped down the code and ...
Using the PRC2 from the downloads area, and NOW the only condition in the strategy is the Math.Abs portion of the code
My pseudo code [idea to test]
IF the (Absolute Value of the ((PRC2.SqHI2 minus HIGH) is GREATER THAN
( the Absolute Value of the ((LOW minus PRC2.SqLOW2 ))
Then Go LONG ...
ie there is more potential to go up than there is to go down if that is true. The reason I am using Abs is to cover cases when the HI might already be greater than the Sqh2 .... reversing logic to go shorts ... on the screen shot you will see that the trigger bars are (in this example) in position to take SHORT, but 1 went LONG instead.. 33.3333% of trades going the wrong way do not a happy tester make!
Likely it is my mis use of the tool, but I dont know any better lol
Thanks especially for a fix ... been hitting on this all weekend trying to find the problem
Jon
Can you help answer these questions from other members on NexusFi?
Thats the plan ... it is ... just the way the results come out it has no pattern that I can determine what the error comes from. The screen shot shows two very similar, consecutive entries, but one is long and the other short.
I have looked at the code, I cant really see where it recalculates ... but it is definitely too complex for my wetware.
Any thoughts on a version that doesnt recalculate, or let it recalculate but only allow changes to the current bar? Something like a 'window' to stop changes to already plotted data?