Gamestudio Links
Zorro Links
Newest Posts
AssetAdd() vs. modern asset list?
by jcl. 02/21/24 15:01
How many still using A8
by Aku_Aku. 02/20/24 12:18
Zorro Trader GPT
by TipmyPip. 02/16/24 06:53
Support PEEK for time and calendar functions
by AndrewAMD. 02/14/24 22:23
Deeplearning Script
by tomaslolo. 02/07/24 18:28
The Super-System
by TipmyPip. 02/06/24 19:32
AUM Magazine
Latest Screens
The Bible Game
A psychological thriller game
SHADOW (2014)
DEAD TASTE
Who's Online Now
2 registered members (AndrewAMD, Ayumi), 594 guests, and 7 spiders.
Key: Admin, Global Mod, Mod
Newest Members
sakolin, rajesh7827, juergen_wue, NITRO_FOREVER, jack0roses
19043 Registered Users
Previous Thread
Next Thread
Print Thread
Rate Thread
Ensuring common test period across WFO trials #485871
05/01/22 15:42
05/01/22 15:42
Joined: Jul 2017
Posts: 783
Z
Zheka Offline OP
User
Zheka  Offline OP
User
Z

Joined: Jul 2017
Posts: 783
I am trying to select "the best" number of WFO cycles. However, the more WFO cycles - the longer the total OOS Test period; and so performance stats are not directly comparable.

What would be the way to achieve common test period across such trials?

Last edited by Zheka; 05/01/22 15:42.
Re: Ensuring common test period across WFO trials [Re: Zheka] #485876
05/02/22 09:08
05/02/22 09:08
Joined: Apr 2008
Posts: 585
Austria
Petra Offline
Support
Petra  Offline
Support

Joined: Apr 2008
Posts: 585
Austria
For a fixed period use WFOPeriod instead of NumWFOCycles. For the best number, use the wfoprofile script from the new Zorro version.

Re: Ensuring common test period across WFO trials [Re: Zheka] #485885
05/02/22 13:36
05/02/22 13:36
Joined: Jul 2017
Posts: 783
Z
Zheka Offline OP
User
Zheka  Offline OP
User
Z

Joined: Jul 2017
Posts: 783
The problem is that oos Test period depends on NumWFOCycles. So, wfoprofile script compares apples to oranges.

For EndDate=2022 and NumYears=5, with NumWFOCycles=12, the test period starts in 09/2021, with NumWFOCycles=6, it starts in 05/2020.

Calculating a different StartDate depending on NumWFOCycles is probably possible. But is there a simpler/ready solution?

Re: Ensuring common test period across WFO trials [Re: Zheka] #485888
05/03/22 10:49
05/03/22 10:49
Joined: Apr 2008
Posts: 585
Austria
Petra Offline
Support
Petra  Offline
Support

Joined: Apr 2008
Posts: 585
Austria
Yes, DIAG is 8, so with 15 you have already a diag.txt and should see the broker commands inside. Look for BrokerBuy, BrokerSell etc.

Re: Ensuring common test period across WFO trials [Re: Zheka] #485889
05/03/22 12:38
05/03/22 12:38
Joined: Jul 2017
Posts: 783
Z
Zheka Offline OP
User
Zheka  Offline OP
User
Z

Joined: Jul 2017
Posts: 783
Petra, you confused the thread

Re: Ensuring common test period across WFO trials [Re: Zheka] #485890
05/03/22 13:33
05/03/22 13:33
Joined: Apr 2008
Posts: 585
Austria
Petra Offline
Support
Petra  Offline
Support

Joined: Apr 2008
Posts: 585
Austria
Yes. But this one is for you: The test starts at the start date plus one training period. So for getting always the same test start you only need to determine the training period and then shift the start date by the difference of current and longest training period.

Re: Ensuring common test period across WFO trials [Re: Zheka] #485892
05/03/22 14:19
05/03/22 14:19
Joined: Jul 2017
Posts: 783
Z
Zheka Offline OP
User
Zheka  Offline OP
User
Z

Joined: Jul 2017
Posts: 783
Any change in the Start/EndDate in Test vs Train will lead to re-split of data among N WFO periods and application of params to periods they were not trained for, no?

Re: Ensuring common test period across WFO trials [Re: Zheka] #485901
05/04/22 12:52
05/04/22 12:52
Joined: Apr 2008
Posts: 585
Austria
Petra Offline
Support
Petra  Offline
Support

Joined: Apr 2008
Posts: 585
Austria
Right. After you trained it, leave the dates alone.


Moderated by  Petra 

Gamestudio download | chip programmers | Zorro platform | shop | Data Protection Policy

oP group Germany GmbH | Birkenstr. 25-27 | 63549 Ronneburg / Germany | info (at) opgroup.de

Powered by UBB.threads™ PHP Forum Software 7.7.1