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
When applying LIME to simulated data with a binary outcome, LIME results do not always match the data generating process. This arises because the family argument in the call to glmnet is set to gaussian by default and does not reflect the model type (classification versus regression). See e.g.,
I was wondering whether this is intentional/documented somewhere? As one possible fix, one could add a family argument to the model_permutations function that then can be used in the glm.fit and glmnet function calls. If you'd be willing to add a corresponding PR, I could prepare one.
The text was updated successfully, but these errors were encountered:
When applying LIME to simulated data with a binary outcome, LIME results do not always match the data generating process. This arises because the
family
argument in the call toglmnet
is set togaussian
by default and does not reflect the model type (classification versus regression). See e.g.,lime/R/lime.R
Line 48 in 0281c56
and
lime/R/lime.R
Line 56 in 0281c56
I was wondering whether this is intentional/documented somewhere? As one possible fix, one could add a
family
argument to themodel_permutations
function that then can be used in theglm.fit
andglmnet
function calls. If you'd be willing to add a corresponding PR, I could prepare one.The text was updated successfully, but these errors were encountered: