nonlinear predict inference versus conditional moment test (cmt)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Start by reading the notes on predict_nonlinear (#2296), margins, cm_test (#2096), and the chi-square tests (#3904), then consult the cited Cameron and Trivedi reference. Clarify whether predicted probabilities and conditional moment tests share reusable derivatives or require separate variance calculations. Done means defining an implementable scope and testable formulas for the proposed functionality.
Written by the indexing model from the issue text.
Description
(just some notes, that I didn't realize before. I didn't check details of formulas yet, so I'm not sure how much the corresponding code will overlap.)
use case: predicted probabilities for count distributions versus conditional moment test
predicted probabilities for count distributions are a deterministic function of the parameters and exog. We can use delta method or endpoint transformation to get standard errors and confidence intervals.
(predict_nonlinear #2296 and similar to margins)
Testing whether predicted probabilities are compatible with observed probabilities uses a "residual", i.e. moment condition that expected difference between observed indicator function and predicted probability is zero. This is a random variable (endog is random) and not a deterministic function.
Test depends on two components, variance of extra moment condition and of their covariance to score-obs (and implied distribution of params) (using partitioned inverse of full moment conditions).
cm_test #2096, and chisquare tests #3904
Cameron Trivedi count book 2nd ed. p. 194 for predicted probabilities using cm-test (and OPG version with auxiliary regression)
Using derivative of moment condition or predict function overlaps between the two.
- Dominant language
- Python
- Stars
- 11.6k
- Forks
- 3.6k
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 96
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statsmodels/statsmodels
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
statsmodels/statsmodels#10271 ·
-
type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
statsmodels/statsmodels#10269 ·
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
statsmodels/statsmodels#10266 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
statsmodels/statsmodels#9627 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
statsmodels/statsmodels#9293 · 1 comment ·
All issues in statsmodels/statsmodels
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100