Chapter 3: Comparing Decomposers and Solvers

[CejkaLuk]

Notes related to this chapter can be found in Notion: Thesis Structure.

General draft & post-supervisor quality points to check

Grammar, Spelling, etc.

• [x] Address and remove TODOs (including \TODO)
• [x] Hyphenation:
  • [x] "non-zero" is not as popular -> use "nonzero" instead
  • [x] Replace all "sub-" prefixes with "sub" (for example: "sub-optimal" -> "suboptimal" - correct according to the Oxford dictionary)
• [x] Full stops and commas:
  • [x] Full stops and commas after equations if the equations are part of a sentence
  • [x] Thousands separated by comma
  • [x] Bullet points that are meant to be a part of the sentence should be separated by a comma and the last bullet should have a dot at the end (if it ends the sentence)
• [x] Bullet points - consistent formatting, e.g., if they're individual sentences -> colon + capital letter right after. If they're part of a sentence, then colon + small letter right after.
• [x] Titles of Chapter/Section/etc. follow correct capitalization
• [x] Double-check spelling using TeXstudio and Grammarly

  Text formatting

• [x] Numbers in the text must not be in math mode
• [x] References to sections etc. have a capital letter in the text (Section~\ref{}, Figure~\ref{}, Table~\ref{})
• [x] Quotes, or statements in "" should be italicized
• [x] No indented line after an object that slices a text in two
• [x] Use "" for multiplication only in in-line code, e.g., `U = R I`
• [x] Mathematics formatting:
  • [x] Variables in cursive font
  • [x] Constants in non-cursive (using \mathrm{})
  • [x] Do not use "*" for multiplication in math mode as it signifies convolution
  • [x] Use \mathbf{} for matrices and vectors (\mathbb{} is used for sets)
  • [x] Shortcuts in sub- and super-script should not be in cursive, e.g. X^{new} "new" should not be cursive)
  • [x] \nonumber\,. should be before newline
• [x] Code formatting:
  • [x] Courier font and grey background (in-line and code block)
  • [x] Check code in all lstlistings for correct syntax highlighting
  • [x] Code blocks:
  • [x] Consistent spacing in code - Do: for( int... i++ ); Don't: for ()
  • [x] Consistent formatting of {} - Do: void func()\n{ \n}; Don't void func() { \n}
  • [x] No spacing from the left part of the listing
• [x] Citations in the text:
  • [x] Spaces between text and citations
  • [x] Multiple citations must be in one \cite{a, b, c} command, not \cite{a}\cite{b}\cite{c}
• [x] Variables in cursive font, e.g., ICMx (x can be one of 8, 16, 32)
• [x] Consistent label names
  • Template: {Type:chapter->section->subsection->subsubsection->specific-content-name}
• [x] No line overflowing (text, in-line code, etc.)
• [x] Consistent footnotes - they must either contain URL if a Url follows, or not.

  Low priority

• [x] TiKZ Figures:
  • [x] Either convert the necessary figures to TiKZ OR create an issue to fix a specific figure
  • Some papers include the TiKZ source code

[CejkaLuk]

Commit for Chapter 01:

• [x] "linear time-dependent partial differential equations"
• [x] Use "A 3-component vector" instead of "The 3-component vector"

Commit for Chapter 02:

• [x] Order of decomposers and solvers should be consistent in tables, e.g., alphabetical. For example, in Table:implementation->decomposition-project->implemented-solutions->solvers->compatibile-decomposers-and-solvers the decomposers are not in the same order as in the other tables.
  • Device and then alphabetical.
• [x] Missing word in the sentence If the absolute value of $lu_{j, j}$ falls this interval, it is considered a \textit{bad element} that requires pivoting.. Should be something like "... absolute value falls outside of this interval..."
  • [x] Double-check with Grammaly
• [x] Use maximum absolute difference instead of maximum difference.

[CejkaLuk]

Supervisor review

Page-specific

• [x] Figure 3.2(b) is missing the explanation of iterations. Consider explaining them as done in Figure 3.4(b).
  • The content of the Figure is understandable, however, it can be disruptive to leave out the description of something in the figure.
  • However, this is not necessary to include in every image.
• [x] Remind the meaning of the abbreviations near Table 3.10.

General

• [x] For people that do not study the implementation aspect in detail, it may be nice to include the full names of the decomposers/solvers in the tables.
  • For example, somewhere around Table 3.3 explain the abbreviations and provide links to sections that describe the particular procedure