aml4td / aml4td/website

Discuss deviance residuals in the class metrics chapter

Open
#129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
171
Forks
17
Avg merge
12d 6h
Merged PRs (30d)
2

Description

Some references to dive into

  • Pregibon, D. 1981. "Logistic Regression Diagnostics." The Annals of Statistics 9 (4): 705–24. (Section 4.2 defines the signed deviance residual d_i = ±sqrt(2 * [l(saturated) - l(fitted)]) used in the text.)
  • McCullagh, P., and J. A. Nelder. 1989. Generalized Linear Models. 2nd ed. Chapman & Hall. (Section 2.4 covers unit deviances for general likelihoods, which is the basis for the multiclass extension.)
  • Dunn, P. K., and G. K. Smyth. 1996. "Randomized Quantile Residuals." Journal of Computational and Graphical Statistics 5 (3): 236–44. (An alternative that stays signed and approximately normal for discrete (including multiclass) outcomes.)
  • Liu, D., and H. Zhang. 2018. "Residuals and Diagnostics for Ordinal Regression Models: A Surrogate Approach." Journal of the American Statistical Association 113 (522): 845–54. (A signed alternative when the classes are ordered.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the class metrics chapter and review the four cited references, especially the sections on signed deviance, unit deviances, randomized quantile residuals, and ordinal models. Done means the chapter clearly discusses the relevant residual choices and their multiclass or ordinal context, with the references incorporated.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.