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
In the current mboost() implementation only one argument weights exists that is used for data and for resampling weights.
Data weights can occur for example as weights in surveys or as integration weights for functional response. Resampling weights are important as resamplling is mostly used to find the optimal stopping iteration.
It is somewhat weird that the weights are rescaled in mboost_fit(), so that they sum up to 1 only when the weights are not integers, cf. rescale_weights() https://github.com/boost-R/mboost/blob/master/R/helpers.R#L29
Thus, the rescaling is only done when the weights are not integers (assuming that resampling weights are integers and data weights are not?)
And one has to be careful what cv() does when creating folds to be used in cvrisk(), in the case thatmodel.weightsof the fitted object are not all equal to 1, see
In the current
mboost()
implementation only one argumentweights
exists that is used for data and for resampling weights.Data weights can occur for example as weights in surveys or as integration weights for functional response. Resampling weights are important as resamplling is mostly used to find the optimal stopping iteration.
It is somewhat weird that the weights are rescaled in
mboost_fit()
, so that they sum up to 1 only when the weights are not integers, cf.rescale_weights()
https://github.com/boost-R/mboost/blob/master/R/helpers.R#L29
Thus, the rescaling is only done when the weights are not integers (assuming that resampling weights are integers and data weights are not?)
And one has to be careful what
cv()
does when creating folds to be used incvrisk()
, in the case thatmodel.weights
of the fitted object are not all equal to 1, see@fabian-s
The text was updated successfully, but these errors were encountered: