(possible) Inaccurate Description of Variable Ordering in Figure 8.32 Caption (Page 291)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- matlab
- Domain
- documentation
Research direction
Find the caption for Figure 8.32 in the material for Section 8.15.2 and compare it with the 'order','AOE' snippet on page 290 and the plotted correlations. Correct the caption so it describes the ordering accurately; done when the caption no longer claims variables are sorted by correlation magnitude in non-decreasing order.
Written by the indexing model from the issue text.
Description
Dear Professors,
While reviewing Section 8.15.2 (pages 290–291), I noticed a slight inaccuracy in the caption of Figure 8.32 (page 291) regarding how variables are ordered in the plot.
The caption of Figure 8.32 states:
"Variables are ordered automatically to reflect correlation magnitude in non-decreasing order. The top-left corner contains the most strongly positively correlated variables."
but:
- In the snippet on page 290 (line 20), the plot is generated using
'order','AOE', which orders variables by the angles of the first two eigenvectors (as correctly explained in the main text on page 290), rather than sorting correlation magnitudes in non-decreasing order. - Looking across the top row of Figure 8.32 from left to right, the correlations with the first variable (
QualLif) actually progress from strongly positive (0.81,0.83, ...,0.70) through weak/uncorrelated (-0.37,-0.44forProtestandBankrup) to strongly negative (-0.86,-0.74forLowISEEandUrbanFra).
Thanks as always for the time
- Dominant language
- MATLAB
- Stars
- 30
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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 UniprJRC/DSwithMATLAB
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#243 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#242 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
UniprJRC/DSwithMATLAB#240 ·
-
Suggestion for the next edition
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UniprJRC/DSwithMATLAB#238 · 2 comments ·
-
Suggestion for the next edition
Difficulty 1/5 Under an hour Newbie friendliness 72/100
UniprJRC/DSwithMATLAB#236 · 1 comment ·
All issues in UniprJRC/DSwithMATLAB
Similar issues
-
bug priority: p3 size: xs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Ax/Atb trim the caller's GpuIds in place, so blocksize-1 solvers run on one GPU after the first anglePossibly taken @AnderBiguri claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
mathworks/MATLAB-Coding-Guidelines#7 · 3 comments ·