Possible Notation / Conceptual Inaccuracy in `BaseValue` Description – Chapter 8.1 (Exercise 8.1) page 251
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Find the Chapter 8.1 text following Exercise 8.1 on page 251 and review the description of the BaseValue name-value pair for bar and barh. Check that the wording distinguishes the baseline value from the axes' intersection and explains which axis the baseline applies to for each function. Done when the text accurately describes both behaviors.
Written by the indexing model from the issue text.
Description
Dear Professors,
While reviewing the examples and exercises in Chapter 8.1, I focused on the explanation of the 'BaseValue' name-value pair following Exercise 8.1 on page 251.
The text currently states:
"The
'BaseValue'name-value pair inbarandbarhspecifies where the $x$-axis intersects the $y$-axis."
Looking at this definition, I wondered whether this formulation might contain a small technical/notational inaccuracy regarding how MATLAB handles coordinate axes and baseline positioning:
- Axis Intersection vs. Baseline Position: The
'BaseValue'property does not shift the axes or alter the intersection of the Cartesian coordinate system ($x$-axis and $y$-axis). In MATLAB graphics, axis placement and intersections are controlled viaAxesproperties (such asXAxisLocationandYAxisLocation). - Behavioral Difference in
barvs.barh:- For
bar(vertical bars),BaseValuesets the horizontal baseline value on the $y$-axis from which the bars originate. - For
barh(horizontal bars),BaseValuesets the vertical baseline value on the $x$-axis from which the bars originate.
- For
I was wondering if a clearer formulation might be:
"The
'BaseValue'name-value pair inbarandbarhspecifies the baseline value from which the bars originate (along the $y$-axis forbarand along the $x$-axis forbarh)."
or if there was a specific subtlety in the text's phrasing that I haven't fully grasped yet.
I hope this observation is helpful, and thank you as always for your time and guidance!
- 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 ·