Title | Conditional logit model and clogit | |
Author | William Sribney, StataCorp |
It’s a “normal” message, but, in Stata 4.0 (or earlier), you may want to be concerned depending on your data.
Stata’s clogit has always done 1:n_i matching using the exact conditional likelihood. But in version 4.0 and earlier, it used an approximation to the likelihood for m_i:n_i matching when m_i > 1.
In Stata 5.0 and 6.0, clogit always uses the exact conditional likelihood. So, it doesn’t matter what type of data you have; it always gives appropriate estimates.
First, let me explain what I mean by 1:n_i matching, etc. Let i index the groups (called strata by clogit in versions 4.0 and earlier). 1:n_i matching means that in the i-th group, there is 1 subject (i.e., observation) with a dependent variable y = 1 and there are n_i subjects with y = 0.
For 1:n_i matching, version 4.0 clogit and versions 5.0 and 6.0 clogit give EXACTLY the same answers.
“Multiple positive outcomes within groups encountered” means there is at least one group j with m_j:n_j matching, where m_j > 1; i.e., in the j-th group, there are 2 or more subjects with y = 1. This general model is often called the conditional fixed-effects logit model.
In version 4.0 and earlier, the approximation used for m_j:n_j matching was only good when m_j << n_j (as the Methods and Formulas section discussed). For m_j approximately the same as n_j (or bigger than), it is a terrible approximation.
In versions 5.0 and 6.0, clogit ALWAYS uses the exact conditional likelihood, so there is no cause for concern when you see the “multiple positive outcomes within strata encountered”—except if you think you should have 1:n_i matched data, in which case you have an error in your dataset.
The new recursive algorithm was not implemented before version 5.0 because it was not well-known.
Often one will see in a text or review that m_j:n_j matching is computationally impossible for anything but small m_j. But this is only true if one uses an enumerative algorithm that steps through all C(m_j+n_j, m_j) possibilities.
The recursive algorithm is proportional to m_j (actually it's the minimum of m_j and n_j), so it gets slower as m_j increases but not unduly.
The bottom line is we strongly recommend anyone doing m_j:n_j matching upgrade to at the current version of Stata and use clogit.
Learn
Free webinars
NetCourses
Classroom and web training
Organizational training
Video tutorials
Third-party courses
Web resources
Teaching with Stata
© Copyright 1996–2024 StataCorp LLC. All rights reserved.
×
We use cookies to ensure that we give you the best experience on our website—to enhance site navigation, to analyze usage, and to assist in our marketing efforts. By continuing to use our site, you consent to the storing of cookies on your device and agree to delivery of content, including web fonts and JavaScript, from third party web services.
Cookie Settings
Last updated: 16 November 2022
StataCorp LLC (StataCorp) strives to provide our users with exceptional products and services. To do so, we must collect personal information from you. This information is necessary to conduct business with our existing and potential customers. We collect and use this information only where we may legally do so. This policy explains what personal information we collect, how we use it, and what rights you have to that information.
These cookies are essential for our website to function and do not store any personally identifiable information. These cookies cannot be disabled.
This website uses cookies to provide you with a better user experience. A cookie is a small piece of data our website stores on a site visitor's hard drive and accesses each time you visit so we can improve your access to our site, better understand how you use our site, and serve you content that may be of interest to you. For instance, we store a cookie when you log in to our shopping cart so that we can maintain your shopping cart should you not complete checkout. These cookies do not directly store your personal information, but they do support the ability to uniquely identify your internet browser and device.
Please note: Clearing your browser cookies at any time will undo preferences saved here. The option selected here will apply only to the device you are currently using.