Possible Running Header Typo and Figure 8.2 Layout Disconnect – Chapter 8.3 (Pages 253–254)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 53/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- matlab
- Domain
- documentation
Research direction
Start by locating the source for Chapter 8.3 and the layout around pages 253–254, including the Figure 8.1 and Figure 8.2 assets or references. Check whether the running header and waterfall chart placement match the intended section and exercise flow. Done means the reported inconsistencies are confirmed and corrected in the source.
Written by the indexing model from the issue text.
Description
Dear Professors,
While reviewing Chapter 8.3 on pages 253 and 254, I noticed a couple of minor layout and typesetting inconsistencies:
- Running Header Typo (Page 253):
The running header at the top left of page 253 reads8.3 Plots for Bivariate Seriesdirectly above Figure 8.1. However, Figure 8.1 illustrates univariate plots belonging to Section 8.1, whereas Section 8.3 officially begins further down the page. This is not a real proper error, but can be in other circumstances a useful note to point out
- Figure 8.2 Layout Disconnect (Page 254):
Figure 8.2 (Waterfall chart) is placed at the top of page 254, right inside the code listing for Exercise 8.3. Because Figure 8.2 actually illustrates Exercise 8.2 (from page 252), placing it directly above the bivariate script kindly creates a visual disconnect for readers following the exercise flow
I hope those observations can be useful
- 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 78/100
UniprJRC/DSwithMATLAB#241 ·
-
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 ·
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 ·