Robustness and OOS



Hello


This is a request that l believe is more than a "feature".


Currently, the robustness tests in SQ do not exclude OOS data. For example, if you run a WF, the windows will be based on the IS period(s), but they will often overlap, and thus use the data, from OOS. This has many unfortunate ramifications for the output. The most obvious one is that the OOS results will be significantly inflated since OOS is no longer OOS (by definition). Systems which performs well OOS, will also be much more likely to pass any test. This defeats the purpose with robustness testing. The whole point is that OOS should always, at every junction of the process, be unseen and untouched by the process itself. Currently however, the process is "data peaking".


There are obviously some ways to get around this in many cases by manually manipulating windows etc in the retester. But the process is cumbersome and it would be much better if OOS data is, by default, never used in any of the robustness testing processes.


Thank you.

Attachments
No attachments
  • Votes +2
  • Project StrategyQuant X
  • Type Feature
  • Status New
  • Priority Normal

History

AE
#1

Phronesis

01.02.2021 12:58

Task created

AE
#2

Phronesis

01.02.2021 12:58
Voted for this task.
b
#3

bentra

01.02.2021 17:43
Voted for this task.
b
#4

bentra

01.02.2021 17:48
Agreed, while some of the cross checks have a nice switch to turn off and on the OOS and the cross check on different markets seems to work with OOS properly too, all of the "Extensive (Slowest)" cross checks have no easy way to do this. 

Votes: +2

Drop files to upload

or

choose files

Max size: 5MB

Not allowed: exe, msi, application, reg, php, js, htaccess, htpasswd, gitignore

...
Wait please