Support codings with "implicit intercept" #107
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthewwardrop
force-pushed
the
master
branch
2 times, most recently
from
b07ba3f
to
48fd2e4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some use cases, it would be nice to have patsy code a design matrix as if it were going to include an intercept (so e.g. it would exclude some categorical levels), but then not include the intercept. See #80 for details.
This pull request adds an
implicit_interceptparameter to some of the public functions (dmatrix,dmatrices,incr_dbuilder,incr_dbuilders, anddesign_matrix_builders). When set toTrue, it codes the matrix as if an intercept were included but doesn't actually include the intercept.