You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tinatorabi is planning to implement a wrapper around the ASP solver that picks the best model from the model path based on a validation set. More generally I can envision us wanting to provide some limited hyperparameter selection based on a dataset split. This issue is to discuss a possible interface for this. In order to keep the package agnostic about the kind of data, I think there are two options:
solve(A, y, solver, Itrain, Ival) # with Itrain, Ival vectors of row-indicessolve(Atrain, ytrain, Aval, yval, solver)
Maybe we can simply provide both and make the first option just a wrapper of the second option?
@tinatorabi is planning to implement a wrapper around the ASP solver that picks the best model from the model path based on a validation set. More generally I can envision us wanting to provide some limited hyperparameter selection based on a dataset split. This issue is to discuss a possible interface for this. In order to keep the package agnostic about the kind of data, I think there are two options:
Maybe we can simply provide both and make the first option just a wrapper of the second option?
@wcwitt - do you have a view on this?
The text was updated successfully, but these errors were encountered: