-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying intercept models is not documented & a PITA #13
Comments
This is already a problem of mboost not just gamboostLSS
We should put it in the description (ideally in gamboost and gamboostLSS) and check if there is an easy fix for that in mboost, but we have to fix the problem there. |
not sure I agree. that issue never comes up for (non-pathological specifications of) |
Well, the point probably is that it usually doesn't make sense in mboost but it should be implemented there anyway as all the interfaces for model fitting are provided from mboost. Perhaps one should try to interpret cars$int <- 1
gamboost(dist ~ bols(int, intercept = FALSE) + bols(..., intercept = FALSE), data = cars) one could then write gamboost(dist ~ bols(1, intercept = FALSE) + bols(..., intercept = FALSE), data = cars)
## or even better
gamboost(dist ~ 1 + bols(..., intercept = FALSE), data = cars)
|
Do we agree that there is no realistic use case for a pure intercept base learner in If so, I think it's a user interface / formula parsing issue for gamboostLSS (i.e., a If not, when/why would I ever want to specify a naked intercept in |
Just to be clear: I don't think we need to / should enable formulas I do think having a shorthand for "this parameter is not affected by any covariates" via |
@hofnerb @ja-thomas just re-read your comments, you're right of course, I was being a Gscheithaferl 😏 |
I think having to do
instead of
sucks major d*** in terms of usability. At least it should be documented somewhere that this is the way we want users to specify an intercept model / formula.....
The text was updated successfully, but these errors were encountered: