Comment

Comment by Vincent Granville on May 24, 2018 at 1:16pm

Dear R Bohn,

We do not delete comments and we like to have contrasted opinions. My main argument is that logistic regression should not be taught first. If you are working with a team of statisticians, and the analysis performed correctly, and the data is sound, I have no doubt that you will understand each other. But when explaining your results to your CEO or engineers, you may face incomprehension. This is just similar to my arguments that you don't need statistical tests of hypotheses or p-values. Engineers (including myself, though technically being a statistician) have been using alternate models that produce the same results if not better (being data-driven rather than model-driven), easier to understand, and you don't even need to know what a random variable is to understand how it works.

Vincent 

Comment by R Bohn on May 24, 2018 at 12:21pm

I am sorry to report that this article is nonsense.  It's not the conclusion - use it or don't use it, there are now many alternatives to logistic regression. (Which in the machine learning world is a "linear classifier." ) 

The difficulty is that most of the discussion is Just Wrong. Analytically incorrect. No correspondence to the usual definitions, use, and interpretation of logistic regression.

• The diagram is incomprehensible. If it is intended to be the standard representation of logistic regression, it has multiple errors.
  • LR maps from -infinity to +infinity (on the X scale), not from 0 to 1. 
  • The y axis is correct.  
  • The colors and the points show the curve (called the logistic curve or similar) as the boundary between positive and negative outcomes, for points defined by two independent variables (here x and y). That is not at all what the curve means. See e.g. https://en.wikipedia.org/wiki/File:Logistic-curve.svg
• "There are hundreds of types of logistic regression." Maybe in a world with a different definition, but the standard definition does not include Poisson models. Of course as always there are a variety of possible algorithms that can be used to solve a logistic model. 
  • From https://www.medcalc.org/manual/logistic_regression.php  "Logistic regression is a statistical method for analyzing a dataset in which there are one or more independent variables that determine an outcome. The outcome is measured with a dichotomous variable (in which there are only two possible outcomes).
    In logistic regression, the dependent variable is binary or dichotomous, i.e. it only contains data coded as 1 (TRUE, success, pregnant, etc.) or 0 (FALSE, failure, non-pregnant, etc.)."
• "If you transform your variable you can instead use linear regression." Yes, and that is how logistic regressions are usually solved! That is, LRs are solved by transforming the variables (using a logit transform ) and solving the resulting equation, which is linear in the variables. In practice, many other transformation equations can be used instead, but the logit transform has a nice interpretation.
  • 
  • where 
• "Coefficients are not easy to interpret." I suppose that easy is in the eye of the beholder, but there is a standard and straightforward interpretation. 
  • "The logistic regression coefficients show the change in the predicted logged odds of having the characteristic of interest for a one-unit change in the independent variables." It does take a few examples to figure out what "log odds" means, unless you do a lot of horse racing. But after that, it is a clever and powerful way to think about changes in the probability of an outcome. 
  • The (corrected) version of the logistic curve corresponds to an equivalent way to interpret the coefficient values. 

There certainly are some mild criticisms of logistic regression, but in situations where a linear model is reasonably accurate, it is a good quick model to try. Of course, if the situation is highly nonlinear, a tree model is going to be better. Furthermore, the particular logistic equation generally used should not be considered sacred. 

My interpretation is that this article is an attack on a straw man, an undefined  and radically unconventional model that is here being called  "logistic regression." It would be a shame if anyone took it seriously. We will see if the author/site manager leaves this comment up. If he does, I invite him to respond and explain  the meaning of diagram. 

By the way, I agree with  much of the discussion on the medcalc website I'm quoting, but not all of it. 

Comment by Rodolfo Antonio Muriel Rodríguez on May 22, 2018 at 8:10am

Vincent Granville Thanks for the answer; Do you recommend any book?

Comment by Vincent Granville on May 22, 2018 at 7:03am

First things to learn should probably be:

• On overview of how algorithms work
• Different types of data and data issues (missing data, duplicated data, errors in data)
• How to identify useful metrics
• Lifecycle of data science projects
• Introduction to programming languages
• Communicating results to non experts and understanding requests from decision makers (translating requests into action items for the data scientist)
• Overview of popular techniques with pluses and minuses, and when to use them
• Case studies

Comment by Rodolfo Antonio Muriel Rodríguez on May 22, 2018 at 6:06am

Thanks for the article...but what should be the first thing to learn?