When using the standard modeling workflow, without stacked ensembles, I do not experience any hardship in setting individual parameter ranges like this:
Also I know, how to update parameters and how to pull them from workflow objects.
What I do not know is, how this works with metalearner stacks. If I am not fundamentally wrong, the argument "param_info" is used for this purpose.
As the documentation of ensemble_model_spec states, param_info can take a.dials parameter object as an input. However, ether I am not getting the concept of dials param objects right, or there is some problem with my code, because my solution is resulting in "all models failed, see .notes column".
This error message is not helpful, as I do not have a tuned object created by for example a tune_grid function. Where do I see a notes column here? From this point on I am stucked, because I have no clear indication about the source of the error.
When using the standard modeling workflow, without stacked ensembles, I do not experience any hardship in setting individual parameter ranges like this:
xgb_grid <- grid_latin_hypercube( learn_rate(range = c(-5.0, -0.1)), size = 30 )
Also I know, how to update parameters and how to pull them from workflow objects.
What I do not know is, how this works with metalearner stacks. If I am not fundamentally wrong, the argument "param_info" is used for this purpose. As the documentation of ensemble_model_spec states, param_info can take a.dials parameter object as an input. However, ether I am not getting the concept of dials param objects right, or there is some problem with my code, because my solution is resulting in "all models failed, see .notes column". This error message is not helpful, as I do not have a tuned object created by for example a tune_grid function. Where do I see a notes column here? From this point on I am stucked, because I have no clear indication about the source of the error.
reprex: