Update terms for ESS, TSS, and SSR to specify uncentered vs centered?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- tex
- Domain
- documentation
Research direction
Locate the lecture text containing the displayed TSS, SSR, and ESS definitions, using the wording from this issue and the original discussion in pull request #217. Update the terminology as proposed, including the centered-case note, then verify that the rendered equations and note are correct.
Written by the indexing model from the issue text.
Description
I think a more commonly seen definitions of (centered) TSS, ESS and SSR are given here where the decomposition only holds when $X$ includes intercept term.
So, I think it might be clearer if we replace
Here are some more standard definitions:
* The **total sum of squares** is $:= \| y \|^2$.
* The **sum of squared residuals** is $:= \| \hat u \|^2$.
* The **explained sum of squares** is $:= \| \hat y \|^2$.
> TSS = ESS + SSR
with
Define:
* The (uncentered) **total sum of squares** (TSS) is $:= \| y \|^2$.
* The (uncentered) **sum of squared residuals** (SSR) is $:= \| \hat u \|^2$.
* The **explained sum of squares** (ESS) is $:= \| \hat y \|^2$.
We have the relationship:
$$
\text{TSS} = \text{ESS} + \text{SSR}
$$
```{note}
For the centered case, see [here](https://en.wikipedia.org/wiki/Explained_sum_of_squares).
```
Please let me know your thoughts on this!
Originally posted by @HumphreyYang in https://github.com/QuantEcon/lecture-python-advanced.myst/pull/217#discussion_r2250749514
- Dominant language
- TeX
- Stars
- 37
- Forks
- 26
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 QuantEcon/lecture-python-advanced.myst
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
broken-links bug documentation
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in QuantEcon/lecture-python-advanced.myst
Similar issues
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
bug docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day