You may find some example files in the comments section of WFO library.

Hi, do you have an ETA on the updated script to fix RubbArray out of range?

You are trying to perform too massive optimization. Its results do not fit your available memory. When I receive an answer from MQ to my request regarding the memory problem, I'll update the FAQ with more details in addition to my instructions I've sent you via PM.

Data is corruped. Please remove WF global variables, old csv-file in Tester/Files, and tester cache. Then start optimization anew.

HOW TO FIX?  I TRIED TO DELETE ALL WF global variables, old csv-file in Tester/Files BUT STILL POP UP THIS ERROR

Please send all details to me via private message (what you did exactly, source codes, tester and EA settings, all generated files, what is shown in the logs).

May I know why the out sample test(yellow parts) in report don't have DDmax? 

Because it was not designed so. To calculate a drawdown we need to start with a capital, which is unclear in the case of forward test - one might prefer to take the intermediate balance after the optimization window, but it will apparently provide a biased estimation. But calculating drawdown relative to the initial balance would be unintuitive and raise even more questions.