-
Notifications
You must be signed in to change notification settings - Fork 370
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
Error in Terms
when no intercept is requested
#574
Comments
This has been fixed now, hasn't it? |
Still doesn't work AFAICT (even after converting |
It's the |
But do we still want to support |
It might make more sense to have a single, consistent means of requesting no intercept, and IMO |
I agree. And, in fact, we might go so far as to make no intercept the default, so you'd need to explicitly have |
On the one hand, I like that because it requires being explicit (which is almost always a good thing) and will require people to think harder about the exact model they're fitting, but on the other hand I think it could be surprising for some people since implicit intercept is the default in R, SAS, and likely others as well. So... I'm undecided on that, but leaning toward +1 require |
I think that forcing the user to use an explicit +1 is a good idea. The fact that earlier languages made the intercept the default doesn't mean that the choice is appropriate now. Including |
We've had that discuss in many different places already, but I'll restate my preferred solution: require people to either say |
+1 to Milan's proposal. And if we end up not doing that, +1 to Doug's. |
Explicitness is good by me, so I like Milan's solution. |
This does not work
but this does
The text was updated successfully, but these errors were encountered: