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
At least for brms-fitted reference models, factor predictor columns in the $data element of the brmsfit get an attribute contrasts assigned. This makes sense and in the future, this should probably also be respected by projpred when fitting the submodels. For now, I think the warnings produced by some predict() methods (see below) should be suppressed and some documentation should be added, stating that any contrasts attributes from the reference model's dataset are ignored.
Reprex (a bit artificial since options(projpred.glm_fitter = "fit_glm_callback") is currently a "hidden" feature, but I encountered a similar issue while trying to solve #70):
Removed the fixed in develop label because #284 was just a quick fix suppressing the warnings. As explained above, in the future, contrasts attributes should also be respected by projpred when fitting the submodels.
At least for brms-fitted reference models,
factor
predictor columns in the$data
element of thebrmsfit
get an attributecontrasts
assigned. This makes sense and in the future, this should probably also be respected by projpred when fitting the submodels. For now, I think the warnings produced by somepredict()
methods (see below) should be suppressed and some documentation should be added, stating that anycontrasts
attributes from the reference model's dataset are ignored.Reprex (a bit artificial since
options(projpred.glm_fitter = "fit_glm_callback")
is currently a "hidden" feature, but I encountered a similar issue while trying to solve #70):The text was updated successfully, but these errors were encountered: