Open ngreifer opened 2 years ago
Thanks for the suggestion. I think a table with some metadata on the included wrappers would be a nice addition, including
Upfront checks are usually limited to only using the default wrappers, there is an internal function .check.SL.library
that is called early in the code, but right now that only checks for the required package for the wrapper.
Yes, I think that would be helpful. I think the second bullet you mention might not be so valuable to users since ideally whatever kind of input the user gives is preprocessed before being passed to the fitting function.
It would be nice if there was possibility of knowing which learners worked for binary vs. continuous outcomes. The only to find this out is to manually try them and receive an intimidating number of error messages if you guessed incorrectly. This could instead be stored as metadata for each learner and reported using
listWrappers()
, and if the user supplies an incompatible learner toSL.library
, a single breaking error message could appear before running the full CV process.