I am not a native English speaker, either but I am not sure which part of parameterization is incorrect:
Murray Ruggiero in another thread openly admitted that his software lacks some of the most basic features that I asked him about (tick data backtesting capabilities, correct currency conversions of non base currency performance data, among others). Let me know if you need a link. Some have a strong incentive to make backtesting sound its complicated and complex and only their software feature take a "right" approach, difference here is that I have no incentive whatsoever other than helping newbies as yourself to cut down on needless complexity and just see the forest for what it really is, a bunch of trees.
First of all TradersStudio backtests down to 1 minute bars. I really don't believe that most traders should be using Tick data, too much noise, too short of a timeframe for most people to trade. TradersStudio does handle correct currency conversion for futures back to USD, so yes some traders that might not be enough, but the dollar is the world reserve currency so for a lot of people that all they need. Where did I say it did not handle currency conversion correctly ?.
TradersStudio WFA is also very powerful and in fact is used by Robert Pardo who is created with inventing walk forward analysis.
If your a scalper then then TradersStudio is not for you. I believe it is of value for all other traders.
Walk forward testing and my WF analyzer , compiles a report for only out of sample results. We select the best parameters on a training set and then trade for N bars, After N bars we drop off the oldest N bars from the training set and add the newer data, then walk it forward. We compile the Walk forward results without using them to gauge the test. Yes if you run it multiple times and modify the system you do get some bias, but my wf analyzer gives you a true walk forward analysis. Now , my reports give you a deep analysis of the walk forward results, in sample, out of sample, how boundary trades are handled over the analysis period.
He has a point, you are not disclosing who you are , we don't know if that is really your thesis because you whited out the name , date ect. See it's easy to attack me because my login is my name. It's always been my name. You can look up my articles, see my linkedin ect. If you are going to use your background in putting people down, just tell us your name so we can "Google it"
See all WF tests are out of sample tests , but not all out of sample tests are WF. For example you could train on 80% of the data and then test on out of sample 20%. and only accept the system if out of sample results are good. That is classic out of sample testing and not what I do. Walk forward uses multiple windows and regardless of performance on out of sample windows selects best set of parameters from training.
See you are correct, terms in trading are different than strict statistical definitions, but when in Rome do as the Romans do. I need to call WF testing WF. If I call it out of sample testing then people will ask why don't I have walk forward analysis in my product.
... it is the exact same thing as optimizing on in-sample data and testing out-of-sample. No difference. Nothing new in town. What is new, and imho a horrible way is how the data is sliced into in- and out-of-sample segments. And here is why: First of all people are deluded into thinking that you end up with a lof ot out-of-sample testing periods. You dont. You end up with a very small data window for out-of-sample.......................08 in-sample