Skip to main content
6 events
when toggle format what by license comment
Mar 27 at 7:21 history bounty ended Javier Hernando
Mar 26 at 12:38 vote accept Javier Hernando
Mar 26 at 10:03 comment added Shawn Hemelstrand One should only delete missing values in any case if there are strong reasons for doing so (such as clearly erroneously coded values or an artefact of some pivoting of the data, which should anyway be fixed before moving forward).
Mar 26 at 10:02 comment added Shawn Hemelstrand The findLinearCombos function uses a QR decomposition to check for linear combinations and then removes them. This is not the same as VIF, which estimates how much the variance is inflated by the inclusion of certain predictors as a result of multi-collinearity. I don't promote any action for missingness before finding out why it exits. Filter the data for NA values, check their cause, figure out if it is due to completely random factors or because of observed data, and then act accordingly (per the article I referenced). Without knowing more about the NA values, I can't give concrete words.
Mar 26 at 9:20 comment added Javier Hernando First of all, appreciate your effort and time of your response. As far I can see the missingness is a strong problem of my database, in fact, seems to be a problem with one of the variables there, which in the long format process was distorted. But I need to point out some details of you comments. Which na.action would you recommend? na.omit /na.exclude, AFA I know lme don't work under the listwise deletion procedure losing statistical power. About the collinearity, didn't know about check_collinearity. Is it different from caret::findLinearCombos?
Mar 26 at 0:29 history answered Shawn Hemelstrand CC BY-SA 4.0