Should SplitDataRequest include the problem (or the target)?
The recently-added optional SplitData
call (#118 (closed)) only takes the data as input. It seems that for some problems/datasets, knowing some more about the problem is required to split correctly (for example, can't do a stratified split without knowing the target column).
We could add a field to SplitDataRequest
with some necessary information (or the whole problem).
Edited by Remi Rampin