-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH: new ordered models, add generalized ordered logit and generalized ordered link models #8444
Comments
another thought gologit corresponds to mnlogit in the sense of common exog but choice specific params I guess a more general version would be the analogy to conditional mnlogit, i.e. common params but choice specific exog For common exog, as in gologit, we would be replicating exog k times, i.e. number of choices and non-common exog should not be too large Is this correct? How can we know when creating the design matrix which exog_k belong to an observation? I guess what this means is that we cannot create a single design matrix, we need to keep several different exog_k and have linear predictor for each k (one params, many exog_k) So, I have the option to either have one exog and choice specific params (including overlapping params) or have several exog, common and choice specific ones. possible implementation for using params_k and one exog: params_k = params[mask_k] This requires full dot product params_e * exog_all where params_e can have many zeros, but we don't need to duplicate exog data arrays. simples case: full gologit edit This would make it easier to include linear restrictions on parameters,, i.e. mapping from restricted to full parameters. |
Green, Hensher Primer section 7.2 |
see comment #8442 (comment) and following
It's also a cumulative link model, where params differ by choice P(y < k) = F(x beta_k)
My guess the only or main difference to OrderedModel is to split up params in
_bounds
andlinpred
to compute thresholds with category level specific params_{k} and params_{k-1}loglike_obs just uses
_bounds
methodscore and hessian are currently computed by numdiff
not checked yet:
I guess there is a computational problem when integration
_bounds
are not increasing,I guess we need to directly impose nonnegativity of probabilities, prob = max(F(upp) - F(low), 0).
Do we still get sum(probs) = 1 if non-negativity constraint is binding?
Williams 2016 has section 5 on p. 18 about negative probabilities, sounds like they are not clipped to zero
Williams, Richard. “Understanding and Interpreting Generalized Ordered Logit Models.” The Journal of Mathematical Sociology 40, no. 1 (January 2, 2016): 7–20. https://doi.org/10.1080/0022250X.2015.1112384.
The text was updated successfully, but these errors were encountered: