main-german-university-of-hamburg.tex

% !TeX spellcheck = de-DE
% LTeX: language=de-DE
% !TeX encoding = utf8
% !TeX program = lualatex
% !TeX TXS-program:compile = txs:///lualatex/[--shell-escape]
% !BIB program = biber
% -*- coding:utf-8 mod:LaTeX -*-

% The following package allows \\ at the title page
% For more information see https://github.com/latextemplates/scientific-thesis-cover/issues/4
\RequirePackage{kvoptions-patch}
\documentclass[
  % fontsize=11pt is the standard
  % ()Aus scrguide.pdf - der Dokumentation von KOMA-Script)
  % Nach DUDEN steht in Gliederungen, in denen ausschließlich arabische Ziffern für die Nummerierung
  % verwendet werden, am Ende der Gliederungsnummern kein abschließender Punkt
  % (siehe [DUD96, R3]). Wird hingegen innerhalb der Gliederung auch mit römischen Zahlen
  % oder Groß- oder Kleinbuchstaben gearbeitet, so steht am Ende aller Gliederungsnummern ein
  % abschließender Punkt (siehe [DUD96, R4])
  numbers=autoendperiod,
  ngerman,  % Neue deutsche Rechtschreibung; der Parameter wird an andere Pakete weiter gegeben
  a4paper,  % KOMAScript allows for both paper=a4 and (standard) a4paper - https://tex.stackexchange.com/a/61044/9075
  twoside,  % We are optimizing for both screen and two-side printing. So the page numbers will jump, but the content is configured to stay in the middle (by using the geometry package)
  bibliography=totoc,
  % idxtotoc,   % Index ins Inhaltsverzeichnis
  % liststotoc, % List of * ins Inhaltsverzeichnis, mit liststotocnumbered werden die Abbildungsverzeichnisse nummeriert
  headsepline,
  cleardoublepage=empty,
  parskip=half,
  %               draft    % um zu sehen, wo noch nachgebessert werden muss - wichtig, da Bindungskorrektur mit drin
  draft=false
]{scrbook}
\usepackage{scrlayer-scrpage}

\usepackage{iftex}

\usepackage{ifplatform}

% backticks (`) werden als solches in verbatim-Umgebungen dargestellt
% Details unter:
%   - https://tex.stackexchange.com/a/341057/9075
%   - https://tex.stackexchange.com/a/47451/9075
%   - https://tex.stackexchange.com/a/166791/9075
\usepackage{upquote}

% Setze Deutsch als Sprache
\usepackage[english,main=ngerman]{babel}
% Neue deutsche Trennmuster
\babelprovide[hyphenrules=ngerman-x-latest]{german}
%
% Hinweis von http://tex.stackexchange.com/a/321066/9075
% Ermögliche die Benutzung von "= als Trennstriche
\addto\extrasenglish{\languageshorthands{ngerman}\useshorthands{"}}

% Ein "abstract" ist eine "Kurzfassung", keine "Zusammenfassung"
\addto\captionsngerman{%
  \renewcommand\abstractname{Kurzfassung}%
}

% Links verhalten sich so, wie sie sollen
% Zeilenumbrüche bei URLs auch bei Bindestrichen erlauben, auch wenn es verwirrend sein könnte: Gehört der Bindestrich zur URL oder ist es ein Trennstrich?
% Siehe https://tex.stackexchange.com/a/3034/9075.
\usepackage[hyphens]{url}
% \urlstyle{same}
%
% Hinweis von http://tex.stackexchange.com/a/10419/9075.
\makeatletter
\g@addto@macro{\UrlBreaks}{\UrlOrds}
\makeatother

%math stuff
\usepackage[
  centertags,    % (default) center tags vertically
  % tbtags,        % 'Top-or-bottom tags': For a split equation, place equation numbers level with the last (resp. first) line, if numbers are on the right (resp. left).
  sumlimits,    % (default) Place the subscripts and superscripts of summation symbols above and below
  % nosumlimits,   % Always place the subscripts and superscripts of summation-type symbols to the side, even in displayed equations.
  intlimits,     % Like sumlimits, but for integral symbols.
  % nointlimits,   % (default) Opposite of intlimits.
  namelimits,    % (default) Like sumlimits, but for certain 'operator names' such as det, inf, lim, max, min, that traditionally have subscripts placed underneath when they occur in a displayed equation.
  % nonamelimits,  % Opposite of namelimits.
  % leqno,         % Place equation numbers on the left.
  % reqno,         % Place equation numbers on the right.
  fleqn,         % Position equations at a fixed indent from the left margin rather than centered in the text column.
]{amsmath}
\SetMathAlphabet{\mathcal}{normal}{OMS}{amsa}{m}{n} %% AMS font for mathcal

%%% Doc: http://mirror.ctan.org/tex-archive/macros/latex/contrib/mh/doc/mathtools.pdf
% Erweitert amsmath und behebt einige Bugs
\usepackage[fixamsmath,disallowspaces]{mathtools}

%%% Doc: http://www.ctan.org/info?id=fixmath
% LaTeX's default style of typesetting mathematics does not comply
% with the International Standards ISO31-0:1992 to ISO31-13:1992
% which indicate that uppercase Greek letters always be typeset
% upright, as opposed to italic (even though they usually
% represent variables) and allow for typesetting of variables in a
% boldface italic style (even though the required fonts are
% available). This package ensures that uppercase Greek be typeset
% in italic style, that upright $\Delta$ and $\Omega$ symbols are
% available through the commands \upDelta and \upOmega; and
% provides a new math alphabet \mathbold for boldface
% italic letters, including Greek.
\usepackage{fixmath}

%for theorems, replacement for amsthm
\usepackage[amsmath,hyperref]{ntheorem}
\theorempreskipamount 2ex plus1ex minus0.5ex
\theorempostskipamount 2ex plus1ex minus0.5ex
\theoremstyle{break}
\newtheorem{definition}{Definition}[chapter]

%%% Doc: http://mirror.ctan.org/tex-archive/macros/latex/contrib/onlyamsmath/onlyamsmath.dvi
% Warnt bei Benutzung von Befehlen die mit amsmath inkompatibel sind.

% Braucht man evtl. nicht.
% \usepackage[
% 	all,
% 	warning
% ]{onlyamsmath}

%% !!! If you change the font, be sure that words such as "workflow" can
%% !!! still be copied from the PDF. If this is not the case, you have
%% !!! to use glyphtounicode. See comment at cmap package.
%%
%% Background: "workflow" contains "fl" which is a ligature, which in turn
%%             is rendered as one character in the PDF and needs to be split
%%             whily copying.

\ifluatex
  \usepackage[no-math]{fontspec}
  \usepackage{unicode-math}

  % See https://tug.org/FontCatalogue/texgyretermes/ for more information
  \setmainfont{texgyretermes}[
    Extension = .otf,
    UprightFont = *-regular,
    BoldFont = *-bold,
    ItalicFont = *-italic,
    BoldItalicFont = *-bolditalic,
    Ligatures=TeX
  ]
  % See https://tug.org/FontCatalogue/texgyreheros/ for more information
  \setsansfont[Scale=.9]{TeX Gyre Heros Regular}
  % shapely l, upright quotes
  % Normal scaling is too large --> thus, we use ",Scale=.9"
  \ifwindows
    \setmonofont[StylisticSet={1,3},Scale=.9]{Inconsolata}
  \else
    \setmonofont[StylisticSet={1,3},Scale=.9]{Inconsolatazi4}
  \fi

  % Enable proper ligatures
  % For more information see https://ctan.org/pkg/selnolig
  % language "english" or "ngerman" is passed to selnolig by the document class
  \usepackage{selnolig}

\else
  \RequirePackage{newtxtext}
  \RequirePackage{newtxmath}
  \RequirePackage[zerostyle=b,scaled=.9]{newtxtt}

  % Has to be loaded AFTER any font packages. See https://tex.stackexchange.com/a/2869/9075.
  \usepackage[T1]{fontenc}
\fi

% DE: Noch mehr Symbole
%\usepackage{stmaryrd} %fuer \ovee, \owedge, \otimes
%\usepackage{marvosym} %fuer \Writinghand %patched to not redefine \Rightarrow
%\usepackage{mathrsfs} %mittels \mathscr{} schoenen geschwungenen Buchstaben erzeugen
%\usepackage{calrsfs} %\mathcal{} ein bisserl dickeren buchstaben erzeugen - sieht net so gut aus.

% EN: Fallback font - if the subsequent font packages do not define a font (e.g., monospaced)
%     This is the modern package for "Computer Modern".
%     In case this gets activated, one has to switch from cmap package to glyphtounicode (in the case of pdflatex)
% DE: Fallback-Schriftart
%\usepackage[%
%    rm={oldstyle=false,proportional=true},%
%    sf={oldstyle=false,proportional=true},%
%    tt={oldstyle=false,proportional=true,variable=true},%
%    qt=false%
%]{cfr-lm}

% EN: Headings are typeset in Helvetica (which is similar to Arial)
% DE: Schriftart fuer die Ueberschriften - ueberschreibt lmodern
%\usepackage[scaled=.95]{helvet}

% DE: Für Schreibschrift würde tun, muss aber nicht
%\usepackage{mathrsfs} %  \mathscr{ABC}

% EN: Font for the main text
% DE: Schriftart fuer den Fliesstext - ueberschreibt lmodern
%     Linux Libertine, siehe http://www.linuxlibertine.org/
%     Packageparamter [osf] = Minuskel-Ziffern
%     rm = libertine im Brottext, Linux Biolinum NICHT als serifenlose Schrift, sondern helvet (von oben) beibehalten
%\usepackage[rm]{libertine}

% EN: Alternative Font: Palantino. It is recommeded by Prof. Ludewig for German texts
% DE: Alternative Schriftart: Palantino, Packageparamter [osf] = Minuskel-Ziffern
%     Bitte nur in deutschen Texten
%\usepackage{mathpazo} %ftp://ftp.dante.de/tex-archive/fonts/mathpazo/ - Tipp aus DE-TEX-FAQ 8.2.1
% EN: The euro sign
% DE: Das Euro Zeichen
%     Fuer Palatino (mathpazo.sty): richtiges Euro-Zeichen
%     Alternative: \usepackage{eurosym}
% \newcommand{\EUR}{\ppleuro}

% DE: Schriftart fuer Programmcode - ueberschreibt lmodern
%     Falls auskommentiert, wird die Standardschriftart lmodern genommen
%     Fuer schreibmaschinenartige Schluesselwoerter in den Listings - geht bei alten Installationen nicht, da einige Fontshapes (<>=) fehlen
%\usepackage[scaled=.92]{luximono}
%\usepackage{courier}
% DE: BeraMono als Typewriter-Schrift, Tipp von http://tex.stackexchange.com/a/71346/9075
%\usepackage[scaled=0.83]{beramono}

\usepackage{setspace}
% Alternative package: https://ctan.org/pkg/leading

% Symbole Check und Cross
\usepackage{pifont}
\newcommand{\dingcheck}{\ding{51}}
\newcommand{\dingcross}{\ding{55}}
%for scaling see http://tex.stackexchange.com/a/130236/9075

% DE: Noch mehr Symbole
%\usepackage{stmaryrd} %fuer \ovee, \owedge, \otimes
%\usepackage{marvosym} %fuer \Writinghand %patched to not redefine \Rightarrow
%\usepackage{mathrsfs} %mittels \mathscr{} schoenen geschwungenen Buchstaben erzeugen
%\usepackage{calrsfs} %\mathcal{} ein bisserl dickeren buchstaben erzeugen - sieht net so gut aus.

\automark[section]{chapter}
\setkomafont{pageheadfoot}{\normalfont\sffamily}
\setkomafont{pagenumber}{\normalfont\sffamily}

\ihead[]{}
\chead[]{}
\ohead[]{\headmark}
\cfoot[]{}
\ofoot[\usekomafont{pagenumber}\thepage]{\usekomafont{pagenumber}\thepage}
\ifoot[]{}

% Optischer Randausgleich und Grauwertkorrektur. Siehe See http://www.ctan.org/tex-archive/macros/latex/contrib/microtype/

\usepackage[
  babel=true,
  expansion=alltext,
  protrusion=alltext-nott,
  final
]{microtype}

% \texttt{test -- test} - diese Einstellung behält "--" bei (und konveriert sie nicht zu einem Bindestrich)
\DisableLigatures{encoding = T1, family = tt* }

% tracking=true muss als Parameter des microtype-packages mitgegeben werden
% Deaktiviert, da dies bei Algorithmen seltsam aussieht

%\DeclareMicrotypeSet*[tracking]{my}{ font = */*/*/sc/* }%

% Hier wird festgelegt, dass alle Passagen in Kapitälchen automatisch leicht gesperrt werden.
% Quelle: http://homepage.ruhr-uni-bochum.de/Georg.Verweyen/pakete.html
% Deaktiviert, da sonst "BPEL", "BPMN" usw. wirklich komisch aussehen.
% Macht wohl nur bei geisteswissenschaftlichen Arbeiten Sinn.
%\SetTracking{ encoding = *, shape = sc }{ 45 }

\usepackage{graphicx}

% Base folder, so there is no need to repeat this over and over again.
\graphicspath{ {figures/} }

%%% Doc: http://mirror.ctan.org/tex-archive/macros/latex/contrib/pdfpages/pdfpages.pdf
\usepackage{pdfpages} % Include pages from external PDF documents in LaTeX documents

% Diagonal lines in a table - http://tex.stackexchange.com/questions/17745/diagonal-lines-in-table-cell
% Slashbox is not available in texlive (due to licensing) and also gives bad results. Thus, we use diagbox
\usepackage{diagbox}

\ifluatex
  \usepackage{spelling}
  \spellingoutput{off}
\fi

\usepackage[dvipsnames, table]{xcolor}

\definecolor{uhhred}{cmyk}{0,100,100,0}

% Code Listings
\usepackage{listings}

\definecolor{eclipseStrings}{RGB}{42,0.0,255}
\definecolor{eclipseKeywords}{RGB}{127,0,85}
\colorlet{numb}{magenta!60!black}

% JSON definition
% Source: https://tex.stackexchange.com/a/433961/9075

\lstdefinelanguage{json}{
  basicstyle=\normalfont\ttfamily,
  commentstyle=\color{eclipseStrings}, % style of comment
  stringstyle=\color{eclipseKeywords}, % style of strings
  numbers=left,
  numberstyle=\scriptsize,
  stepnumber=1,
  numbersep=8pt,
  showstringspaces=false,
  breaklines=true,
  frame=lines,
  % backgroundcolor=\color{gray}, %only if you like
  string=[s]{"}{"},
  comment=[l]{:\ "},
  morecomment=[l]{:"},
  literate=
    *{0}{{{\color{numb}0}}}{1}
    {1}{{{\color{numb}1}}}{1}
    {2}{{{\color{numb}2}}}{1}
    {3}{{{\color{numb}3}}}{1}
    {4}{{{\color{numb}4}}}{1}
    {5}{{{\color{numb}5}}}{1}
    {6}{{{\color{numb}6}}}{1}
    {7}{{{\color{numb}7}}}{1}
    {8}{{{\color{numb}8}}}{1}
    {9}{{{\color{numb}9}}}{1}
}

\lstset{
  % everything between (* *) is a latex command
  escapeinside={(*}{*)},
  %
  language=json,
  %
  showstringspaces=false,
  %
  basicstyle=\footnotesize\ttfamily,
  %
  commentstyle=\slshape,
  %
  % Default: \rmfamily, damit werden die Strings im Quellcode hervorgehoben. Zusaetzlich evtl.: \scshape oder \rmfamily durch \ttfamily ersetzen. Dann sieht's aus, wie bei fancyvrb
  stringstyle=\ttfamily,
  %
  breaklines=true,            % Zeilen werden umbrochen
  %
  breakatwhitespace=true,
  %
  % Alternative: fixed
  columns=flexible,
  %
  tabsize=2,                  % Groesse von Tabs
  %
  numbers=left,
  %
  numberstyle=\tiny,
  %
  basewidth=.5em,
  %
  xleftmargin=.5cm,
  %
  % aboveskip=0mm,
  %
  % belowskip=0mm,
  %
  captionpos=b
}

\ifpdftex
  % Ermögliche Umlaute falls \lstinputputlisting genutzt wird
  % Siehe https://stackoverflow.com/a/29260603/873282 und https://tex.stackexchange.com/a/24532/9075 für Details.
  % listingsutf8 hat im Juni 2020 nicht funktioniert.
  \lstset{extendedchars=true, literate=
    {á}{{\'a}}1 {é}{{\'e}}1 {í}{{\'i}}1 {ó}{{\'o}}1 {ú}{{\'u}}1
  {Á}{{\'A}}1 {É}{{\'E}}1 {Í}{{\'I}}1 {Ó}{{\'O}}1 {Ú}{{\'U}}1
  {à}{{\`a}}1 {è}{{\`e}}1 {ì}{{\`i}}1 {ò}{{\`o}}1 {ù}{{\`u}}1
  {À}{{\`A}}1 {È}{{\'E}}1 {Ì}{{\`I}}1 {Ò}{{\`O}}1 {Ù}{{\`U}}1
  {ä}{{\"a}}1 {ë}{{\"e}}1 {ï}{{\"i}}1 {ö}{{\"o}}1 {ü}{{\"u}}1
  {Ä}{{\"A}}1 {Ë}{{\"E}}1 {Ï}{{\"I}}1 {Ö}{{\"O}}1 {Ü}{{\"U}}1
  {â}{{\^a}}1 {ê}{{\^e}}1 {î}{{\^i}}1 {ô}{{\^o}}1 {û}{{\^u}}1
  {Â}{{\^A}}1 {Ê}{{\^E}}1 {Î}{{\^I}}1 {Ô}{{\^O}}1 {Û}{{\^U}}1
  {Ã}{{\~A}}1 {ã}{{\~a}}1 {Õ}{{\~O}}1 {õ}{{\~o}}1
  {œ}{{\oe}}1 {Œ}{{\OE}}1 {æ}{{\ae}}1 {Æ}{{\AE}}1 {ß}{{\ss}}1
  {ű}{{\H{u}}}1 {Ű}{{\H{U}}}1 {ő}{{\H{o}}}1 {Ő}{{\H{O}}}1
  {ç}{{\c c}}1 {Ç}{{\c C}}1 {ø}{{\o}}1 {å}{{\r a}}1 {Å}{{\r A}}1
  }
\fi

\lstloadlanguages{% Check dokumentation for further languages...
  %[Visual]Basic
  %Pascal
  %C
  %C++
  %XML
  %HTML
}

% For easy quotations: \enquote{text}
% This package is very smart when nesting is applied, otherwise textcmds (see below) provides a shorter command
\usepackage[autostyle=true]{csquotes}

% Enable using "`quote"' - see https://tex.stackexchange.com/a/150954/9075
\defineshorthand{"`}{\openautoquote}
\defineshorthand{"'}{\closeautoquote}

% bessere Abstaende innerhalb der Tabelle (Layout))
% -------------------------------------------------
% \toprule, \midrule, \bottomrule
% Doc: https://texdoc.org/serve/booktabs/0
\usepackage{booktabs}

% Extended enumerate, such as \begin{compactenum}
\usepackage{paralist}
\usepackage[
  backend       = biber, %biber does not work with 64x versions alternative: bibtex8; minalphanames only works with biber backend
  sortcites     = true,
  bibstyle      = alphabetic,
  citestyle     = alphabetic,
  giveninits    = true,
  useprefix     = false, %"von, van, etc." will be printed, too. See below.
  minnames      = 1,
  minalphanames = 3,
  maxalphanames = 4,
  maxbibnames   = 99,
  maxcitenames  = 2,
  natbib        = true,
  eprint        = true,
  url           = true,
  doi           = true, %source: http://tex.stackexchange.com/a/23118/9075
  isbn          = true, %source: http://tex.stackexchange.com/a/23118/9075
  backref       = true]{biblatex}

% enable more breaks at URLs. See https://tex.stackexchange.com/a/134281.
\setcounter{biburllcpenalty}{7000}
\setcounter{biburlucpenalty}{8000}

\bibliography{bibliography}
%\addbibresource[datatype=bibtex]{\bibliography{bibliography}}

% Do not put "vd" in the label, but put it at "\citeauthor"
% Source: http://tex.stackexchange.com/a/30277/9075
\makeatletter
\AtBeginDocument{\toggletrue{blx@useprefix}}
\AtBeginBibliography{\togglefalse{blx@useprefix}}
\makeatother

% Thin spaces between initials
% http://tex.stackexchange.com/a/11083/9075
\renewrobustcmd*{\bibinitdelim}{\,}

% Keep first and last name together in the bibliography
% http://tex.stackexchange.com/a/196192/9075
\renewcommand*\bibnamedelimc{\addnbspace}
\renewcommand*\bibnamedelimd{\addnbspace}

% Replace last "and" by comma in bibliography
% See http://tex.stackexchange.com/a/41532/9075
\AtBeginBibliography{%
  \renewcommand*{\finalnamedelim}{\addcomma\space}%
}

% enable hyperlinked author names when using \citeauthor
% source: http://tex.stackexchange.com/a/75916/9075
\DeclareCiteCommand{\citeauthor}
{
  \boolfalse{citetracker}%
  \boolfalse{pagetracker}%
  \usebibmacro{prenote}
}
{
  \ifciteindex
  {\indexnames{labelname}}
  {}%
  \printtext[bibhyperref]{\printnames{labelname}}
}
{\multicitedelim}
{\usebibmacro{postnote}}

% Farbige Tabellen
% ----------------
% Das Paket colortbl wird inzwischen automatisch durch xcolor geladen
%
% Erweiterte Funktionen innerhalb von Tabellen
% --------------------------------------------
%%% Doc: http://mirror.ctan.org/tex-archive/macros/latex/contrib/multirow/multirow.sty
\usepackage{multirow} % Mehrfachspalten
%
%%% Doc: Documentation inside dtx Package
\usepackage{dcolumn}  % Ausrichtung an Komma oder Punkt

%%% Doc: http://mirror.ctan.org/tex-archive/macros/latex/contrib/supertabular/supertabular.pdf
%\usepackage{supertabular}

%%% Fussnoten/Endnoten ===================================================

%%% Doc: http://mirror.ctan.org/tex-archive/macros/latex/contrib/footmisc/footmisc.pdf
%
\usepackage[
  bottom,      % Footnotes appear always on bottom. This is necessary specially when floats are used
  stable,      % Make footnotes stable in section titles
  % perpage,     % Reset on each page
  % para,        % Place footnotes side by side of in one paragraph.
  % side,        % Place footnotes in the margin
  ragged,      % Use RaggedRight
  % norule,      % Suppress rule above footnotes
  multiple,    % Rearrange multiple footnotes intelligent in the text.
  % symbol,      % Use symbols instead of numbers
]{footmisc}

\counterwithout{footnote}{chapter} % Continuous numbering of footnotes across chapters

\interfootnotelinepenalty=10000 % Verhindert das Fortsetzen von Fussnoten auf der gegenüberligenden Seite

% EN: Put footnotes below floats
% DE: Fußnoten unter Gleitumgebungen ("floats") platzieren
% Source: https://tex.stackexchange.com/a/32993/9075
\usepackage{stfloats}
\fnbelowfloat

% EN: Extended support for footnotes
% DE: Fußnoten
%
%\usepackage{dblfnote}  %Zweispaltige Fußnoten
%
% Keine hochgestellten Ziffern in der Fußnote (KOMA-Script-spezifisch):
%\deffootnote[1.5em]{0pt}{1em}{\makebox[1.5em][l]{\bfseries\thefootnotemark}}
%
% Abstand zwischen Fußnoten vergrößern:
%\setlength{\footnotesep}{.85\baselineskip}
%
% EN: Following command disables the separting line of the footnote
% DE: Folgendes Kommando deaktiviert die Trennlinie zur Fußnote
%\renewcommand{\footnoterule}{}
%
%\addtolength{\skip\footins}{\baselineskip} % Abstand Text <-> Fußnote

% DE: Fußnoten immer ganz unten auf einer \raggedbottom-Seite
% DE: fnpos kommt aus dem yafoot package
%\usepackage{fnpos}
%\makeFNbelow
%\makeFNbottom

% TODO (and comment) configuration
%
% - \todo (from todo, easy-todo, todonotes) / \TODO (from fixmetodonotes) - for "normal" TODOs
% - \todofix - "important" TODOs
%
% - \textcomment - highlights text and has a hover comment
% - \sidecomment - just puts a comment to the side. Note: \comment MUST NOT be used as command name, it is already defined by much packages (mathdesign, mindflow, verbatim, and others)
%
% - \missingfigure
%
% - \textmarker
% - \modified
% - \change      - adresses a review comment

% Enable nice comments
\usepackage{pdfcomment}

\newcommand{\textcomment}[2]{\colorbox{yellow!60}{#1}\pdfcomment[color={0.234 0.867 0.211},hoffset=-6pt,voffset=10pt,opacity=0.5]{#2}}

% Small PDF comment
% 1. Parameter: Comment
\newcommand{\sidecomment}[1]{\pdfcomment[color={0.045 0.278 0.643},voffset=4pt,icon=Note]{#1}}
% Disabled variant - for the final PDF
%\newcommand{\sidecomment}[1]{}

\newcommand{\todo}[1]{TODO!\sidecomment{#1}}

% Änderungen
%
% 1. Parameter: Review-Kommentar
% 2. Parameter: Neuer Text
\newcommand{\change}[2]{{\color{red}#2}\pdfcomment[color={0.234 0.867 0.211},voffset=8pt,opacity=0.5]{#1}}
% Disabled variant - for the final PDF
%\newcommand{\change}[2]{#2}

% Define default commands
\makeatletter
\@ifundefined{missingfigure}{\newcommand{\missingfigure}{... missing figure ...}}{}
\@ifundefined{textcomment}{\newcommand{\textcomment}[2]{#1 \todo{#2}}}{}
\@ifundefined{sidecomment}{\newcommand{\sidecomment}[1]{\marginpar{#1}}}{}
\@ifundefined{todo}{\newcommand{\todo}[1]{\sidecomment{#1}}}{}
\@ifundefined{TODO}{\newcommand{\TODO}[1]{\todo{#1}}}{}
\@ifundefined{todofix}{\newcommand{\todofix}[1]{\todo{#1}}}{}
\@ifundefined{change}{\newcommand{\change}[2]{#1 $\rightarrow$ #2}}{}
\makeatother

% Textmarker (Textfarbe rot)
\newcommand{\textmarker}[1]{{\color{red} #1}\xspace}

% Modified (Text blau)
\newcommand{\modified}[1]{{\color{blue!60!black} #1}\xspace}

\usepackage[group-minimum-digits=4,per-mode=fraction]{siunitx}
\addto\extrasgerman{\sisetup{locale = DE}}

% See http://tex.stackexchange.com/a/83051/9075
% Normally, doesn't work with hyperref, but cleveref fixes that
\usepackage[ngerman]{varioref}


% Enable that parameters of \cref{}, \ref{}, \cite{}, ... are linked so that a reader can click on the number an jump to the target in the document
\usepackage{hyperref}

% Enable hyperref without colors and without bookmarks
\hypersetup{
  hidelinks,
  colorlinks=true,       % Links erhalten Farben statt Kaeten
  raiselinks=true,       % calculate real height of the link
  allcolors=black,
  pdfstartview=Fit,
  breaklinks=true,       % Links ueberstehen Zeilenumbruch
  hypertexnames=false,   % Fix jumping to algorithm line - http://tex.stackexchange.com/a/156404/9075
}

% Enable correct jumping to figures when referencing
\usepackage[all]{hypcap}

% Hint by https://tex.stackexchange.com/a/193370/9075 to suppress strange outputs of the babel package
% Example strange output: Package babel Info: Redefining ngerman shorthand "|
\usepackage{etoolbox}
\makeatletter
\patchcmd{\@decl@short}{\bbl@info}{\@gobble}{}{}
\makeatother


%%%
% Ermoeglicht es, Abbildungen um 90 Grad zu drehen
% Alternatives Paket: rotating Allerdings wird hier nur das Bild gedreht, während bei lscape auch die PDF-Seite gedreht wird.
%Das Paket lscape dreht die Seite auch nicht
\usepackage{pdflscape}

\usepackage[caption=false,font=footnotesize]{subfig}

% Alternative for making subfigures:
% Part of the caption package. See http://www.ctan.org/pkg/caption
% Ersetzt die Pakete subfigure und subfig - siehe https://tex.stackexchange.com/a/13778/9075
%
% (subfigure is outdated. subfig is maintained, but subcaption is better)
% See: http://tex.stackexchange.com/questions/13625/subcaption-vs-subfig-best-package-for-referencing-a-subfigure
%\usepackage[hypcap=true]{subcaption}

\usepackage{mindflow}

% https://ctan.org/pkg/algorithms
% Consists of two environments: algorithm and algorithmic
% Although oudated, it defines the "algorithm" float enviornment
% TODO: Define floating environment "algorithm" in other ways
\usepackage[chapter]{algorithm}

% https://ctan.org/pkg/algpseudocodex
% Successor of algorithmicx; more modern than https://ctan.org/pkg/algorithms
\usepackage{algpseudocodex}

\floatname{algorithm}{Algorithmus}
\renewcommand{\listalgorithmname}{Algorithmenverzeichnis}

\newcommand{\commentchar}{\ensuremath{/\mkern-4mu/}}
\algrenewcommand{\algorithmiccomment}[1]{\hfill $\commentchar$ #1}

% cleveref für cref statt autoref, da cleveref auch bei Definitionen funktioniert
\usepackage[capitalise,nameinlink,noabbrev]{cleveref}

\crefname{table}{Tabelle}{Tabellen}
\Crefname{table}{Tabelle}{Tabellen}
\crefname{figure}{Abbildung}{Abbildungen}
\Crefname{figure}{Abbildung}{Abbildungen}
\crefname{equation}{Gleichung}{Gleichungen}
\Crefname{equation}{Gleichung}{Gleichungen}
\crefname{theorem}{Theorem}{Theoreme}
\Crefname{theorem}{Theorem}{Theoreme}
\crefname{listing}{Listing}{Listings}
\Crefname{listing}{Listing}{Listings}
\crefname{section}{Abschnitt}{Abschnitte}
\Crefname{section}{Abschnitt}{Abschnitte}
\crefname{paragraph}{Abschnitt}{Abschnitte}
\Crefname{paragraph}{Abschnitt}{Abschnitte}
\crefname{subparagraph}{Abschnitt}{Abschnitte}
\Crefname{subparagraph}{Abschnitt}{Abschnitte}

\usepackage{lipsum}

% For demonstration purposes only
% These packages can be removed when all examples have been deleted
\usepackage[math]{blindtext}
\usepackage{mwe}
\usepackage[realmainfile]{currfile}
\usepackage{tcolorbox}
\tcbuselibrary{listings}

%introduce \powerset - hint by http://matheplanet.com/matheplanet/nuke/html/viewtopic.php?topic=136492&post_id=997377
\DeclareFontFamily{U}{MnSymbolC}{}
\DeclareSymbolFont{MnSyC}{U}{MnSymbolC}{m}{n}
\DeclareFontShape{U}{MnSymbolC}{m}{n}{
  <-6>    MnSymbolC5
  <6-7>   MnSymbolC6
  <7-8>   MnSymbolC7
  <8-9>   MnSymbolC8
  <9-10>  MnSymbolC9
  <10-12> MnSymbolC10
  <12->   MnSymbolC12%
}{}
\DeclareMathSymbol{\powerset}{\mathord}{MnSyC}{180}

\addto\captionsngerman{%
  \renewcommand*{\glossaryname}{Bedeutung}%
}
\usepackage[
  translate=babel,
  abbreviations,         % create "abbreviations" glossary
  nomain,                % don't create "main" glossary
  stylemods=longbooktabs % do the adjustments for the longbooktabs styles
]{glossaries-extra}
\setglossarystyle{long3col-booktabs}

% Hint by https://tex.stackexchange.com/a/463188/9075
% \usepackage{glossary-longextra}

% Following is required if the abbreviation list should be sorted automatically (\printglossary / \printglossaries)
% Not required, if we printed the entries in-order (using \printunsrtglossaries)
% Required to have the German chapter name % Source: https://tex.stackexchange.com/a/426392/9075
\makeglossaries

\input{abbreviations}


\usepackage{xspace}
% Macht \xspace und \enquote kompatibel
\makeatletter
\xspaceaddexceptions{\grqq \grq \csq@qclose@i \} }
\makeatother

% Enable hyphenation at other places as the dash.
% Example: applicaiton\hydash specific
\makeatletter
\newcommand{\hydash}{\penalty\@M-\hskip\z@skip}
% Definition of "= taken from http://mirror.ctan.org/macros/latex/contrib/babel-contrib/german/ngermanb.dtx
\makeatother

\ifluatex
  % Enable correct rendering of ligatures - provided by https://ctan.org/pkg/autotype
  % See ADR-0008 for alternatives
  \usepackage{autotype}
\fi

% correct bad hyphenation here
\hyphenation{
  Spe-zi-fi-ka-tion
  In-te-gra-tion
  An-for-de-rung An-for-de-run-gen
  Be-nut-zer-ober-flä-che
  Mes-sung-en
  aus-zu-tau-schen
  Lauf-zeit-in-for-ma-tionen
  % May not be hypphenated
  AROMA TOSCA BPMN OASIS OMG DMTF IT DevOps
}

\input{commands}

\usepackage{geometry}
% Package URL: https://ctan.org/pkg/scientific-thesis-cover
\usepackage[
  title={Is Oil the future?},
  author={Lars K.},
  type=bachelor,
  institute=iaas, % or other institute names - or just a plain string using {Demo\\Demo...}
  course={Medieninformatik},
  examiner={Prof.\ Dr.\ Uwe Fessor},
  supervisor={Dipl.-Inf.\ Roman Tiker,\\Dipl.-Inf.\ Laura Stern,\\Otto Normalverbraucher,\ M.Sc.},
  startdate={July 5, 2018},
  enddate={January 5, 2019}
]{scientific-thesis-cover}


\ifpdftex
  % Enable copy and paste of text from the PDF
  % Only required for pdflatex. It "just works" in the case of lualatex.
  % Alternative: cmap or mmap package
  % mmap enables mathematical symbols, but does not work with the newtx font set
  % See: https://tex.stackexchange.com/a/64457/9075
  % Other solutions outlined at http://goemonx.blogspot.de/2012/01/pdflatex-ligaturen-und-copynpaste.html and http://tex.stackexchange.com/questions/4397/make-ligatures-in-linux-libertine-copyable-and-searchable
  % Trouble shooting outlined at https://tex.stackexchange.com/a/100618/9075
  %
  % According to https://tex.stackexchange.com/q/451235/9075 this is the way to go
  \input{glyphtounicode}
  \pdfgentounicode=1
\fi
% DM: line-breaking-description env vom daniel w.

% credit goes to daniel w. :-)
%% --- Descriptions with line breaks in labels ---------------------------------
\usepackage{calc}

\newcommand*\Descriptionlabel[1]{%
  \raisebox{0pt}[1ex][0pt]{
    \makebox[\labelwidth][1]{
      \parbox[t]{\labelwidth}{
        \hspace{0pt}\textbf{#1:}}}}
}

\newcommand*\Descriptionlabelx[1]{%
  \parbox[t]{\textwidth}{
    \textbf{#1}\\\mbox{}}
}

\newenvironment{Description}{
  \begin{list}{}{
      \let\makelabel\Descriptionlabelx
      \setlength\labelwidth{1em}
      \setlength\leftmargin{\labelwidth+\labelsep}
    }
    }
    {
  \end{list}
}

% globally change line spacing of lists
% paralist has suspended development since 10 years.
% enumitem has been updated 2011-09-28
\usepackage[inline]{enumitem}
\setlist{partopsep=0pt,itemsep=1pt}

%------------------------------------------------------------------------
% fquote Fancy Quotation environment
% supports empty/optional author

% Use \sloppy to make right-margin easier?
% Set picture units to be relative to font size (em)?
% Use begingroup to rest units afterwards?

\usepackage{xifthen}% provides \isempty test
\definecolor{quotemark}{gray}{0.7}

%fquote environment with author as optional parameter
%usage: \begin{fquote}quote\end{fquote} or \begin{fquote}[Author]quote\end{fquote}
\newenvironment{fquote}[1][]{%
  \newcommand{\fqauthor}{\relax}
  \ifthenelse{\isempty{#1}}
  {}% do nothing
  {\renewcommand{\fqauthor}{\hfill\textsc{--- #1}}}
  \vspace{1em}
  \begin{list}{}{%
      \setlength{\leftmargin}{0.2\textwidth}
      \setlength{\rightmargin}{0.2\textwidth}
    }
    \item[]%
          \begin{picture}(0,0)(0,0)
            \put(-15,-5){\makebox(0,0){%
                \scalebox{4.5}{\textcolor{quotemark}{\bfseries``}}}%
            }
          \end{picture}\em\ignorespaces%
          }{%
          \newline%
          \makebox[0pt][l]{\hspace{0.6\textwidth}%
            \begin{picture}(0,0)(0,0)
              \put(15,10){\makebox(0,0){%
                  \scalebox{4.5}{\textcolor{quotemark}{\rmfamily\bfseries''}}}%
              }
            \end{picture}}%
          \fqauthor
  \end{list}
}

%German fquote
%  1 parameter for the author's name, may be empty ("{}")
%  guaranteed German quotes (works with lualatex and babel package)
%  usage: \begin{gfquote}{Author}quote\end{gfquote}
\newenvironment{gfquote}[1]{%
  \newcommand{\fqauthor}{\relax}
  \ifthenelse{\isempty{#1}}
  {}% do nothing
  {\renewcommand{\fqauthor}{\hfill\textsc{\textemdash #1}}}
  \vspace{1em}
  \begin{list}{}{%
      \setlength{\leftmargin}{0.2\textwidth}
      \setlength{\rightmargin}{0.2\textwidth}
    }
    \item[]%
          \begin{picture}(0,0)(0,0)
            \put(-15,-5){\makebox(0,0){%
                \scalebox{4.5}{\textcolor{quotemark}{\bfseries \glqq}}}%
            }
          \end{picture}\em\ignorespaces%
          }{%
          \newline%
          \makebox[0pt][l]{\hspace{0.6\textwidth}%
            \begin{picture}(0,0)(0,0)
              \put(15,10){\makebox(0,0){%
                  \scalebox{4.5}{\textcolor{quotemark}{\rmfamily\bfseries \grqq}}}%
              }
            \end{picture}}%
          \fqauthor
  \end{list}
}

% fix incompatibilities between KOMA and other packages, mainly float.
% should be loaded at the very end - see http://tex.stackexchange.com/a/156256/9075
\usepackage{scrhack}


\begin{document}
\raggedbottom     % Variable Seitenhoehen zulassen
\ifluatex
  % Enable correct rendering of ligatures - provided by https://ctan.org/pkg/autotype
  % See ADR-0008 for alternatives
  \autotypelangoptions{ngerman}{ligbreak}
\fi

\pagenumbering{arabic}
\frontmatter
\newgeometry{centering,left=2cm,right=2cm,top=2cm,bottom=2cm}
\begin{titlepage}
%\includegraphics[scale=0.3]{figures/UHH-Logo_2010_Farbe_CMYK.pdf}
\includegraphics[scale=0.3]{figures/UHH-Logo_2010_Farbe_CMYK.png}
\vspace*{2cm}
\Large
\begin{center}
              {\color{uhhred}\textbf{\so{BACHELORTHESIS}}}
%TODO ...oder {\color{uhhred}\textbf{\so{MASTERTHESIS}}}
\vspace*{2.0cm}\\
{\LARGE \textbf{Titel}}
\vspace*{2.0cm}\\
vorgelegt von
\vspace*{0.4cm}\\
Max Musterstudent
\end{center}
\vfill

\noindent
{\small
MIN-Fakultät\\[.2cm]
Fachbereich Informatik \\[.2cm]
Ggf. Professur/Institut \\[.2cm]       %TODO Optional, entweder "Ggf. " oder ganze Zeile löschen
Studiengang: Wirtschaftsinformatik \\[.2cm]
Matrikelnummer: 1234567 \\[.5cm]
Ggf. Abgabedatum: XX.XX.20XX \\[.5cm]  %TODO Optional, entweder "Ggf. " oder ganze Zeile löschen
Erstgutachterin: Prof. Dr. Bertha Beispiel \\[.25cm]
Zweitgutachter: Dr. Eduard Exempel               %TODO Bei Bedarf Geschlechter der Gutachter/innen anpassen
}
\end{titlepage}

\restoregeometry

\pagestyle{plain.scrheadings}
\renewcommand*{\chapterpagestyle}{plain.scrheadings}

% Kurzfassung / abstract
% auch im Stil vom Inhaltsverzeichnis
\section*{Kurzfassung}
% Silbentrennung auf Englisch
\begin{otherlanguage}{american}
  \emph{Write an abstract for your work.
    Replace each of the points below with one sentence (two if you must) and you have your abstract.
    Write it when you finished your entire report.
    \footnote{https://www.easterbrook.ca/steve/2010/01/how-to-write-a-scientific-abstract-in-six-easy-steps/}}

  \emph{Introduction.}
  In one sentence, what’s the topic?
  Phrase it in a way that your reader will understand.
  If you’re writing a PhD thesis, your readers are the examiners – assume they are familiar with the general field of research, so you need to tell them specifically what topic your thesis addresses.
  Same advice works for scientific papers – the readers are the peer reviewers, and eventually others in your field interested in your research, so again they know the background work, but want to know specifically what topic your paper covers.

  \emph{State the problem you tackle.}
  What’s the key research question?
  Again, in one sentence.
  (Note: For a more general essay, I’d adjust this slightly to state the central question that you want to address)
  Remember, your first sentence introduced the overall topic, so now you can build on that, and focus on one key question within that topic.
  If you can’t summarize your thesis/paper/essay in one key question, then you don’t yet understand what you’re trying to write about.
  Keep working at this step until you have a single, concise (and understandable) question.

  \emph{Summarize (in one sentence) why nobody else has adequately answered the research question yet.}
  For a PhD thesis, you’ll have an entire chapter, covering what’s been done previously in the literature.
  Here you have to boil that down to one sentence.
  But remember, the trick is not to try and cover all the various ways in which people have tried and failed; the trick is to explain that there’s this one particular approach that nobody else tried yet (hint: it’s the thing that your research does).
  But here you’re phrasing it in such a way that it’s clear it’s a gap in the literature.
  So use a phrase such as “previous work has failed to address…”.
  (if you’re writing a more general essay, you still need to summarize the source material you’re drawing on, so you can pull the same trick – explain in a few words what the general message in the source material is, but expressed in terms of what’s missing)

  \emph{Explain, in one sentence, how you tackled the research question.}
  What’s your big new idea?
  (Again for a more general essay, you might want to adapt this slightly: what’s the new perspective you have adopted? or:
  What’s your overall view on the question you introduced in step 2?)

  \emph{In one sentence, how did you go about doing the research that follows from your big idea.}
  Did you run experiments?
  Build a piece of software?
  Carry out case studies?
  This is likely to be the longest sentence, especially if it’s a PhD thesis – after all you’re probably covering several years worth of research.
  But don’t overdo it – we’re still looking for a sentence that you could read aloud without having to stop for breath.
  Remember, the word ‘abstract’ means a summary of the main ideas with most of the detail left out.
  So feel free to omit detail!
  (For those of you who got this far and are still insisting on writing an essay rather than signing up for a PhD, this sentence is really an elaboration of sentence 4 – explore the consequences of your new perspective).

  \emph{As a single sentence, what’s the key impact of your research?
    Here we’re not looking for the outcome of an experiment.
  }
  We’re looking for a summary of the implications.
  What’s it all mean?
  Why should other people care?
  What can they do with your research.
  (Essay folks: all the same questions apply: what conclusions did you draw, and why would anyone care about them?)
\end{otherlanguage}

\microtypesetup{protrusion=false}

% In case you have trouble with headings reaching into the page numbers, enable the following three lines.
% Hint by http://golatex.de/inhaltsverzeichnis-schreibt-ueber-rand-t3106.html
%
%\makeatletter
%\renewcommand{\@pnumwidth}{2em}
%\makeatother
%
% Bei einem ungünstigen Seitenumbruch im Inhaltsverzeichnis, kann dieser mit
%  \addtocontents{toc}{\protect\newpage}
% an der passenden Stelle im Fließtext erzwungen werden.
\tableofcontents

\listoffigures

\listoftables

% We use lstlisting environments with caption paramters.
% Thus, we need that command.
% Alternative: \listof{Listing}{List of Listings}
\lstlistoflistings

%mittels \newfloat wurde die Algorithmus-Gleitumgebung definiert.
%Mit folgendem Befehl werden alle floats dieses Typs ausgegeben
%\listof{Algorithmus}{Verzeichnis der Algorithmen}
%\listofalgorithms %Ist nur für Algorithmen, die mittels \begin{algorithm} umschlossen werden, nötig

% Abkürzungsverzeichnis / Acronyms / Abbreviations
\printglossary[type=\acronymtype,title={Abkürzungsverzeichnis}]
% \printglossaries
% \printnoidxglossaries
% \printunsrtglossaries cannot be used, because then no indexing happens; source: https://tex.stackexchange.com/a/287128/9075

\microtypesetup{protrusion=true}

% Headline and footline
\renewcommand*{\chapterpagestyle}{scrplain}
\pagestyle{scrheadings}
\mainmatter

%%% ===============================================================================
\chapter{Introduction}\label{sec:introduction}
%%% ===============================================================================

\emph{Purpose and scope of your entire report}.
The purpose of your entire report is to make a \emph{scientific argument using the scientific method}.
A scientific argument always has the following steps that all must come in this order.
%
\begin{itemize}
  \item[SM1] \emph{Explicate the assumptions and state of the art} on which you are going to conduct your research to investigate your research problem/test the hypothesis.
  \item[SM2] Clearly and precisely \emph{formulate a research problem or hypothesis}.
  \item[SM3] \emph{Describe the (research) method} that you followed to investigate the problem / to test the hypothesis in a way that \emph{allows someone else to reproduce your steps}.
        The method must includes steps and criteria for evaluating whether you answered your question successfully or not.
  \item[SM4] \emph{Provide execution details} on how you followed the method in the given, specific situation.
  \item[SM5] \emph{Report your results} by describing and summarizing your measurements.
        You must not interpret your results.
  \item[SM6] \emph{Now interpret your results} by contextualizing the measurements and drawing conclusion that lead to answering your research problem or defining further follow-up research problems.
\end{itemize}
%
This template will mark various parts of the structure with SM1-SM6 to recall to you which step of a scientific argument is used and where.

\emph{Purpose and scope of \cref{sec:introduction}}.
The introduction chapter is a summary of your work and your scientific argument that shall be understandable to anyone in your scientific field, e.g., anyone in Data Science.
A reader must be able to comprehend the problem, method, relevant execution details, results, and their interpretation by reading the introduction and the introduction alone.
Section~\ref{sec:introduction:topic} introduces the general topic of your research.
Section~\ref{sec:introduction:state-of-art} discusses the state of the art and identifies a research.
Section~\ref{sec:introduction:research-question} then states the research problem to investigate.
Section~\ref{sec:problem-exposition:research-method} explains the research method that was followed, possibly with execution details.
Section~\ref{sec:introduction:results} then presents the results and their interpretation.
Only if a reader thinks they are not convinced or they need more details to reproduce your study, they shall have to read further.
The individual chapters and sections provide the details for each of the steps in your scientific argument.

You usually write the introduction chapter \emph{after} you wrote all other chapters, but you should keep on making notes for each of the sections as you write the later chapters.
.

\emph{Purpose and scope of the introduction paragraph to a chapter}.
The paragraph you are reading above is a typical introductory paragraph to a chapter.
It is a high-level summary of the chapters' topic (SM1 and SM2).
It gives the reader some guidance by breaking down the chapter topic into subtopics that are clearly named (SM3) in the right order with forward references to the corresponding sections (SM4).
It may close with announcing the result you obtain (SM6) but this is usually not done in the opening paragraph of the introduction.

% ---------------------------------------------------------------------------------
\section{Context and Topic (SM1)}\label{sec:introduction:topic}
% ---------------------------------------------------------------------------------

\emph{Purpose and scope}.
You begin with providing the general scientific audience an introduction into the specific topic of your work.
The aim of this section is to first introduce the \emph{general subject of study} (``Giraffes are well-known animals and everyone's favorite''), the \emph{specific topic of societal or scientific interest} to investigate (``Giraffes have blue tongues'') and the \emph{objective of society/science towards} this topic (``it is unknown at the moment how the blue color tone evolved'').
It must be understandable by the general scientific public.
Every \emph{term} with a specific meaning must be highlighted and introduced in precise language/concepts that only builds on a general scientific background.

At the end of this section, you have explained and established a general goal that society/science universally agrees to be worth achieving (``knowing how everyone's favorite animal evolved the colour of their tongue'').

% ---------------------------------------------------------------------------------
\section{State of the Art (SM1)}\label{sec:introduction:state-of-art}
% ---------------------------------------------------------------------------------

\emph{Purpose and scope}.
You provide a more in-depth introduction into the research topic by contrasting the current state of the art in society/science in relation to the research topic you introduced in \cref{sec:introduction:topic}.
This introduction has to

\begin{itemize}
  \item present established facts, methods, and results that provide a deeper understanding of the research topic (``prior work on giraffe genomes, relevance of giraffes for societal well-being, giraffes being a model-animal for various other studies, etc.'')
  \item discuss in which ways prior and recent ideas still fall short of reaching the general goal you explained in \cref{sec:introduction:topic} (``prior work only sequenced the genome of one giraffe and did not consider genes of ancient ancestors'')
\end{itemize}

You have to provide citations/literature references for each of the statements and claims you are making.
This section is usually a summary of the related work discussion in \cref{sec:background}.

At the end of this section, you have established a \emph{knowledge gap} between the state of the art and the general objective you developed in \cref{sec:introduction:topic}.
\emph{Stating a (knowledge) gap between a status quo and a desired situation is the \emph{first step} of a writing scientific argument.}

% ---------------------------------------------------------------------------------
\section{Research Question (SM2)}\label{sec:introduction:research-question}
% ---------------------------------------------------------------------------------

\emph{Purpose and scope}.
In this section you state in which way you will address the knowledge gap you identified at the end of \cref{sec:introduction:state-of-art}.
You usually cannot address and resolve the entire knowledge gap in your work.
The purpose of this section is to clearly detail the specific part of the knowledge that you will address.
You thereby make all the assumptions explicit that underlie your work (``in this report we focus on genomes of female giraffes who lived in the years 1950-2000 in South Africa'').

Your general research question states
\begin{itemize}
  \item The starting point/assumptions you are making from which your research starts (``for the given 13 genomes of female giraffes...''), and
  \item the final objective/solution you want to reach (``...identify the genes involved in color expression of giraffe tongues...'')
  \item and the evaluation criteria that will determine whether you are successful (``...that are present in at least 75\% of the studied giraffes'')
\end{itemize}

You will usually break your general research question down into sub-research questions.
You may do this here.
The sub-research questions have to form a chain that take you in smaller steps from the starting point/assumptions of your general research question to your final objective and evaluation.

% ---------------------------------------------------------------------------------
\section{Method or Approach (SM3, SM4)}\label{sec:introduction:method}
% ---------------------------------------------------------------------------------

\emph{Purpose and scope}.
In this section you outline the method that you applied to answer the research questions, or the new technical approach that you developed to answer it.
It is a summary of the steps that someone else has to take in order to reproduce your steps.
Mention here the data sets you had to obtain/gather/analyze, interviews with stakeholders you had to make to further develop the research questions, technical artifacts (programs, algorithms, models) you could apply or that you had to develop (and how they work).

The section is most readable if you give each of the steps in your method its own paragraph.
In each paragraph you first briefly explain the concept of the step in your method (SM3, ``we explored the data through visual analytics'') and then provide details in execution (SM4, ``we used tool X, we developed dashboard Y'') include a forward reference to the respective chapter that provides more details.

% ---------------------------------------------------------------------------------
\section{Findings (SM5, SM6)}\label{sec:introduction:results}
% ---------------------------------------------------------------------------------

\emph{Purpose and scope}.
You close the introduction by clearly stating the evaluation setup you designed to evaluate the success of your study regarding the research objective, which comes in two steps.
It is most likely a summary of your evaluation in \cref{sec:evaluation}.

\section*{Results (SM5)}

You state the evaluation method that is in line with your research question from \cref{sec:introduction:research-question} and summarize the measurements you obtained but you do not interpret them, i.e., you only report the numbers but you do not include judging statements.

\section*{Interpretation (SM6)}

You summarize your interpretation of the results and draw conclusions.
State whether and to which degree the research question from \cref{sec:introduction:research-question} has been answered successfully or not.

Finally state briefly how much closer society and science have come in answering the general objective you outlined in \cref{sec:introduction:topic}.

%%% ===============================================================================
\section{Background (SM1)}\label{sec:background}
%%% ===============================================================================

\emph{Purpose and scope}.
The background chapter has multiple roles.
\begin{itemize}

  \item \emph{Preliminaries.}
        It has to provide all (and exactly the) information that is necessary to understand the methodological and technical parts of your work in the specific area of study.
        Assume as starting point another student in your degree who did not study the specific subject you are studying but has the task to understand your work.
        Which concepts, terms, definitions, etc. does the student have to know?
        Which formulas, symbols, etc. are standard in this topic?
        Only introduce definitions if you actually need them in any of the subsequent chapters.

  \item \emph{Related Work.}
        It has to provide a comprehensive discussion of all prior work in the area on this subject.
        Your discussion has to summarize these prior works and has to explain in which way the research question you are solving (\cref{sec:introduction:research-question}) has not bee solved yet because prior work had more limiting assumptions, addressed a different angle, their results are not complete etc. Depending on the subject you are studying, the related work part can be larger and warrant an entire chapter on its own, or be fully concluded within \cref{sec:introduction:state-of-art}.

        You can close the related work discussion by clarifying the positioning and formulation of your research question (SM2) in relation to all the prior work, making more explicit whether you address an existing research question under different premises or whether you work on a modified or completely new research question.
\end{itemize}

%%% ===============================================================================
\section{Problem Exposition (optional)}\label{sec:problem-exposition}
%%% ===============================================================================

\emph{Purpose and scope}.
Introduce the problem context in more detail if \cref{sec:introduction:topic} does not provide all necessary information about the problem to follow the rest of the report.
This can include further details on the data you studied, context assumptions and requirements, etc.

If you have to expose the problem in more detail here, then this chapter should also provide a more detailed explanation of research question and the method you are applying, i.e., you can now provide more concrete sub-problems compared to \cref{sec:introduction:research-question} more details for the method \cref{sec:introduction:method} because you now have explained the problem much better.
A typical structure can be.

% ---------------------------------------------------------------------------------
\section{Context/Business Understanding (SM1)}\label{sec:problem-exposition:context-understanding}
% ---------------------------------------------------------------------------------

provide details

% ---------------------------------------------------------------------------------
\section{Data Understanding (SM1)}\label{sec:problem-exposition:data-understanding}
% ---------------------------------------------------------------------------------

provide details

% ---------------------------------------------------------------------------------
\section{Detailed Research Questions (SM2)}\label{sec:problem-exposition:research-problems}
% ---------------------------------------------------------------------------------

provide details based on \cref{sec:problem-exposition:context-understanding} and \ref{sec:problem-exposition:data-understanding}

% ---------------------------------------------------------------------------------
\section{Detailed Method (SM3)}\label{sec:problem-exposition:research-method}
% ---------------------------------------------------------------------------------

provide details based on \cref{sec:problem-exposition:context-understanding} and \ref{sec:problem-exposition:data-understanding}

%%% ===============================================================================
\section{First Real Chapter addressing first Research Problem}\label{sec:problem1}
%%% ===============================================================================

\emph{Purpose and scope}.
After you stated research context (SM1), research problem (SM2), and research method (SM3) in \cref{sec:introduction} and possibly \cref{sec:problem-exposition}, the remainder of your entire report addresses execution (SM4), results (SM5), and interpretation (SM6).
You usually do this by addressing various sub-problems again through scientific arguments following the 6 steps SM1-SM6.

Have a short chapter introduction that recalls and explains the first research problem of your thesis.
The problem has to show up in the introduction in \cref{sec:introduction:research-question} or in \cref{sec:problem-exposition:research-problems} already.
This provides the background (SM1) for this chapter while the first research problem of the thesis becomes the research question/hypothesis (SM2) for this chapter.

Next, explain in the chapter intro how you solve the research problem in this chapter by breaking it down in further sub-problems.
By this, you outline the method (SM3) through which you are going to solve the problem of this chapter.
This is necessary to give the reader guidance of what's to come in this chapter and how it fits into the thesis as a whole.
Explain that you will address the first sub-problem in \cref{sec:problem1:subproblem1} and the second sub-problem in \cref{sec:problem1:subproblem2}, etc. The sections then provide the details for execution and results.

% ---------------------------------------------------------------------------------
\section{First Sub-Problem}\label{sec:problem1:subproblem1}
% ---------------------------------------------------------------------------------

\emph{The first paragraph describes the first sub-problem and develops the requirements a solution has to satisfy (SM2 for this section).}
The requirements have to be based on the knowledge and reasoning developing in the preceding chapters and sections.
Try to use an example to illustrate the problem and the desired properties of the solution.
Check that every term/concept you use here has already been defined already in a previous section.
If you cannot describe your problem without defining new terms, you may have to add another section before this one that develops the terms and concepts you need to explain the problem.

\emph{The second paragraph describes the method/approach how you address the problem (SM3 for this section).}
Describe the method in a level of detail that allows another student to reproduce your steps.
Make use of appendices % (see \cref{sec:appendix1})
if certain details take too much space.

\emph{The third, fourth, and following paragraph provides details on applying the method or developing a new approach, i.e., execution (SM4) and may explain results (SM5)}, i.e. details on the steps needed to reproduce the results.

Results (SM5) can come in many forms, e.g., conceptual diagrams, algorithms, tables, charts, a list of articles from a literature research etc. You must reference them (``\cref{fig:my_label} shows.
..'') and describe the results in text.
If you use diagrams, tables, or charts, you cannot expect the reader to know what to you expect them to see in a diagram, table or chart.
Describe to them how to read these, explain the meaning of particular elements, point out special observations.
But you may only describe the results you must not interpret them.
Make use of appendices if certain details take too much space.

\begin{figure}
  \centering
  %%%\includegraphics{/path/to/figure.pdf}
  \caption{A scientific figure that has to be explained in the text}
  \label{fig:my_label}
\end{figure}

\emph{After describing the results, you may interpret them (SM6).}
Here you can infer what a particular observation means (for you), how it can be applied, or what others can do with it.
You must not write interpretations before completely describing your results.
This is a common mistake done by most beginner writers.
You want to quickly get to the point, which is the final finding or interpretation.
But you forget that your reader does not understand yet what you are interpreting - they do not know yet what you do know.
An interpretation can only be followed after all results have been described.
The interpretation must be based on the written description only.
Then you can be sure that your readers can follow your interpretation and reach the same conclusions as you have.

Ideally, your interpretation leads to the next sub-problem in \cref{sec:problem1:subproblem2}.

% ---------------------------------------------------------------------------------
\section{Second Sub-Problem}\label{sec:problem1:subproblem2}
% ---------------------------------------------------------------------------------

You now build on the solution to the first sub-problem of \cref{sec:problem1:subproblem1} (SM1) and recall second sub-problem (SM2, you detailed in the introduction of this chapter) and follow the same pattern as before (SM3-SM6).

Note that not all sections may not include all parts SM1-SM6 in all detail.
Some sections do not require to repeatedly state the background (SM1) or the research problem (SM2) if they were already clearly defined in a previous section.
Sometimes, a section is only dedicated to describing the method (SM3) and execution (SM4) and does not contain any results or interpretations.
Sometimes results (SM5) and interpretations (SM6) only come in the evaluation chapter.

What is important for you when you are writing a scientific argument is not to slavishly have SM1-SM6 in each section explicitly, but that you are always fully aware of the following:
%
\begin{itemize}
  \item Which step of a scientific argument am I currently writing (SM1, SM2, ..., SM6)?
  \item Does the step that I am writing come in the right order, i.e., if you are writing about execution (SM4, e.g., details of building a model), is there a preceding paragraph or section that describes the method (SM3) and is that one preceded by a clear statement of the (sub-)problem addressed (SM2)?
  \item Are you really \emph{not} writing interpretation SM6 before SM5, SM4, or SM3?
  \item Is it clear to the reader which part of the scientific argument you are currently making?
\end{itemize}

%%% ===============================================================================
\section{Second Real Chapter}\label{sec:sub-problem2}
%%% ===============================================================================

Have a short chapter introduction that recalls what you already achieved in \cref{sec:problem1} and explain the second research problem of your thesis.
The problem has to show up in the introduction in \cref{sec:introduction:research-question} or in \cref{sec:problem-exposition:research-problems} already.
etc.

%%% ===============================================================================
\section{Evaluation}\label{sec:evaluation}
%%% ===============================================================================

\emph{Purpose and scope}.
The evaluation chapter should be the most formal and rigorously structured chapter of your thesis as the validity of your evaluation argument depends on it.

% ---------------------------------------------------------------------------------
\section{Objective (SM2)}\label{sec:evaluation:objective}
% ---------------------------------------------------------------------------------

Clearly state what you want to evaluate and what you want to measure.

% ---------------------------------------------------------------------------------
\section{Setup (SM3)}\label{sec:evaluation:setup}
% ---------------------------------------------------------------------------------

State which data, participants, tools, etc. you chose and why.
Clearly state how you measure outcomes and how you compare them to baselines, reference groups, etc.

% ---------------------------------------------------------------------------------
\section{Execution (SM4)}\label{sec:evaluation:execution}
% ---------------------------------------------------------------------------------

Provide all details on the execution that are necessary to allows another person to reproduce your results at a later point.

% ---------------------------------------------------------------------------------
\section{Results (SM5)}\label{sec:evaluation:results}
% ---------------------------------------------------------------------------------

You only report the measurements.
You must present and reference them (``\cref{fig:my_label2} shows.
..'') and describe the results in text.
If you use diagrams, tables, or charts, you cannot expect the reader to know what to you expect them to see in a diagram, table or chart.
Describe to them how to read these, explain the meaning of particular elements, point out special observations.
But you may only describe the results you must not interpret them.
Make use of appendices if certain details take too much space.

\begin{figure}
  \centering
  %%%\includegraphics{/path/to/figure.pdf}
  \caption{Another scientific figure that has to be explained in the text}
  \label{fig:my_label2}
\end{figure}

% ---------------------------------------------------------------------------------
\section{Discussion (SM6)}\label{sec:evaluation:discussion}
% ---------------------------------------------------------------------------------

An interpretation can only be followed after all results have been described.
The interpretation must be based on the written description in \cref{sec:evaluation:results} only.
Then you can be sure that your readers can follow your interpretation and reach the same conclusions as you have.


\chapter{LaTeX Hinweise}
\label{sec:latexhints}

% Benötigt für eine korrekte Darstellung der Hinweise im erzeugten PDF
\newcount\LTGbeginlineexample
\newcount\LTGendlineexample
\newenvironment{ltgexample}%
{\LTGbeginlineexample=\numexpr\inputlineno+1\relax}%
{\LTGendlineexample=\numexpr\inputlineno-1\relax%
  \tcbinputlisting{%
    listing only,
    listing file=\currfilepath,
    colback=green!5!white,
    colframe=green!25,
    coltitle=black!90,
    coltext=black!90,
    left=8mm,
    title=Zugehöriger \LaTeX{}-Quelltext aus \texttt{\currfilepath},
    listing options={
        frame=none,
        language={[LaTeX]TeX},
        escapeinside={},
        firstline=\the\LTGbeginlineexample,
        lastline=\the\LTGendlineexample,
        firstnumber=\the\LTGbeginlineexample,
        basewidth=.5em,
        aboveskip=0mm,
        belowskip=0mm,
        numbers=left,
        xleftmargin=0mm,
        numberstyle=\tiny,
        numbersep=8pt%
      }
  }
}%

Hier sollen allgemeine \LaTeX-Hinweise gegeben werden, damit man Minimalbeispiele vorliegen hat, um sofort loszulegen.

\section{Trennung von Absätzen}

\begin{ltgexample}
Pro Satz eine neue Zeile.
Das ist wichtig, um sauber versionieren zu können.
In LaTeX werden Absätze durch eine Leerzeile getrennt.
Analogie zu Word: Bei Word werden neue Absätze durch einmal Eingabetaste herbeigeführt.
Dies führt bei LaTeX jedoch nicht zu einem neuen Absatz, da LaTeX direkt aufeinanderfolgende Zeilen zu einer Zeile zusammenfügt.
Mächte man nun einen Absatz haben, muss man zweimal die Eingabetaste drücken.
Dies führt zu einer leeren Zeile.
In Word gibt es die Funktion Großschreibetaste und Eingabetaste gleichzeitig.
Wenn man dies drückt, wird einer harter Umbruch erzwungen.
Der Text fängt am Anfang der neuen Zeile an.
In LaTeX erreicht man dies durch Doppelbackslashes (\textbackslash\textbackslash) erzeugt.
\\
Dies verwendet man quasi nie.

Folglich werden neue Abstäze insbesondere \emph{nicht} durch Doppelbackslashes erzeugt.
Beispielsweise begann der letzte Satz in einem neuen Absatz.
Eine ausführliche Motivation hierfür findet sich in \url{http://loopspace.mathforge.org/HowDidIDoThat/TeX/VCS/#section.3}.
\end{ltgexample}

Möchte man die Art des Absatzes ändern, so kann man die Dokumentklassenoption \texttt{parskip} verwenden.
Beispielsweise kann man mit \texttt{parskip=off} erreichen, dass statt eines freien Bereichs die erste Zeile des Absatzes eingezogen wird.

\section{Notes separated from the text}

The package mindflow enables writing down notes and annotations in a way so that they are separated from the main text.

\begin{ltgexample}
\begin{mindflow}
This is a small note.
\end{mindflow}
\end{ltgexample}

\section{Handling TODOs}

\begin{ltgexample}
\textmarker{Markierter Text.}
\end{ltgexample}

Bei \verb1\textmarker1 wird nur die Textfarbe geändert, da dies auch bei einigen Worten gut funktioniert.

\begin{ltgexample}
\textcomment{Markierter Text.}{Kommentar dazu.}
\end{ltgexample}

\begin{ltgexample}
\hl{In Gelb hervorgehoben.}
Provided indirectly by pdfcomment.sty (soulpos).
\end{ltgexample}

\begin{ltgexample}
\modified{Manuelle Markierung für Text, der seit der letzten Version geändert wurde.}
\end{ltgexample}

\begin{ltgexample}
Das ist ein Text.
\change{FL1: Text angepasst}{Geänderter Text}.
\end{ltgexample}

\begin{ltgexample}
Hier nur ein Kommentar\sidecomment{Kommentar}.
\end{ltgexample}

\begin{ltgexample}
\todo{Hier muss noch kräftig Text produziert werden}
\end{ltgexample}

\section{Hyphenation}

\LaTeX{} automatically hyphenates words.
When using \href{https://ctan.org/pkg/microtype}{microtype}, there should be fewer hyphenations than in other settings.
It might be necessary to tweak the hyphenations nevertheless.
Here are some hints:

\begin{ltgexample}
In case you write \enquote{application-specific}, then the word will only be hyphenated at the dash.
You can also write \verb1applica\allowbreak{}tion-specific1 (result: applica\allowbreak{}tion-specific), but this is much more effort.

You can now write words containing hyphens which are hyphenated at other places in the word.
For instance, \verb1application"=specific1 gets application"=specific.
This is enabled by an additional configuration of the babel package.
\end{ltgexample}

\section{Typesetting Units}

\begin{ltgexample}
Numbers can be written plain text (such as 100), by using the \href{https://ctan.org/pkg/siunitx}{siunitx} package as follows:
\SI{100}{\km\per\hour},
or by using plain \LaTeX{} (and math mode):
$100 \frac{\mathit{km}}{h}$.
\end{ltgexample}

\begin{ltgexample}
\SI{5}{\percent} of \SI{10}{kg}
\end{ltgexample}

\begin{ltgexample}
Numbers are automatically grouped: \num{123456}.
\end{ltgexample}

\section{Surrounding Text by Quotes}

\begin{ltgexample}
Please use the \enquote{enquote command} to quote something.
Quoting with "`quote"' or ``quote'' also works.

\end{ltgexample}

\section{Cleveref examples}
\label{sec:ex:cref}

Cleveref demonstration: Cref at beginning of sentence, cref in all other cases.

\begin{figure}
  \centering
  \includegraphics[width=.75\linewidth]{example-image-a}
  \caption{Example figure for cref demo}
  \label{fig:ex:cref}
\end{figure}

\begin{table}
  \centering
  \begin{tabular}{ll}
    \toprule
    Heading1 & Heading2 \\
    \midrule
    One      & Two      \\
    Thee     & Four     \\
    \bottomrule
  \end{tabular}
  \caption{Example table for cref demo}
  \label{tab:ex:cref}
\end{table}

\begin{ltgexample}
\Cref{fig:ex:cref} shows a simple fact, although \cref{fig:ex:cref} could also show something else.

\Cref{tab:ex:cref} shows a simple fact, although \cref{tab:ex:cref} could also show something else.

\Cref{sec:ex:cref} shows a simple fact, although \cref{sec:ex:cref} could also show something else.
\end{ltgexample}

\section{Abbildungen}

\begin{ltgexample}
\Cref{fig:label} zeigt etwas Interessantes

\begin{figure}
  \centering
  Füge deine Abbildung hier ein.
  \caption{Bildunterschrift.}
  \label{fig:label}
\end{figure}
\end{ltgexample}

\section{Sub Figures}

An example of two sub figures is shown in \cref{fig:two_sub_figures}.

\begin{ltgexample}
\begin{figure}[!b]
  \centering
  \subfloat[Case I]{\includegraphics[width=.4\linewidth]{example-image-a}%
    \label{fig:first_case}}
  \hfil
  \subfloat[Case II]{\includegraphics[width=.4\linewidth]{example-image-b}%
    \label{fig:second_case}}
  \caption{Example figure with two sub figures.}
  \label{fig:two_sub_figures}
\end{figure}
\end{ltgexample}

\section{Tables}

\begin{ltgexample}
\begin{table}
  \caption{Simple Table}
  \label{tab:simple}
  \centering
  \begin{tabular}{ll}
    \toprule
    Heading1 & Heading2 \\
    \midrule
    One      & Two      \\
    Thee     & Four     \\
    \bottomrule
  \end{tabular}
\end{table}
\end{ltgexample}

\begin{ltgexample}
% Source: https://tex.stackexchange.com/a/468994/9075
\begin{table}
  \caption{Table with diagonal line}
  \label{tab:diag}
  \begin{center}
    \begin{tabular}{|l|c|c|}
      \hline
      \diagbox[width=10em]{Diag \\Column Head I}{Diag Column\\Head II} & Second & Third \\
      \hline
       & foo & bar              \\
      \hline
    \end{tabular}
  \end{center}
\end{table}
\end{ltgexample}


\section{Quellcode}

\begin{ltgexample}
\Cref{lst:XML} zeigt XML-Quelltext.
\Cref{line:comment} enthält einen Kommentar.

\begin{lstlisting}[
  language=XML,
  caption={Beispiel-XML-Listing},
  label={lst:XML}]
<listing name="example">
  <!-- comment --> (* \label{line:comment} *)
  <content>not interesting</content>
</listing>
\end{lstlisting}
\end{ltgexample}

Der zusätzliche Paramter \verb+float+ führt dazu, dass das Listing auch floated.
\Cref{lst:flXML} zeigt das gleitendede Listing.

\begin{ltgexample}
\begin{lstlisting}[
  % Es ist möglcih, die Abstände bei Bedarf einzustellen
  % aboveskip=2.5\baselineskip,
  % belowskip=-.8\baselineskip,
  float,
  language=XML,
  caption={Beispiel-XML-Listing -- gleitend},
  label={lst:flXML}]
<listing name="example">
  Floating
</listing>
\end{lstlisting}
\end{ltgexample}

Es ist möglich auch JSON zu setzen, wie in \cref{lst:json} gezeigt.

\begin{ltgexample}
\begin{lstlisting}[
  float,
  language=json,
  caption={Beispiel-JSON-listing},
  label={lst:json}]
{
  key: "value"
}
\end{lstlisting}
\end{ltgexample}

Java ist auch möglich -- \cref{lst:java}.

\begin{ltgexample}
\begin{lstlisting}[
  caption={Example Java listing},
  label=lst:java,
  language=Java,
  float]
public class Hello {
    public static void main (String[] args) {
        System.out.println("Hello World!");
    }
}
\end{lstlisting}
\end{ltgexample}

\section{Itemization}

One can list items as follows:

\begin{ltgexample}
\begin{itemize}
  \item Item One
  \item Item Two
\end{itemize}
\end{ltgexample}

With the package paralist, one can create itemizations with lesser spacing:

\begin{ltgexample}
\begin{compactitem}
  \item Item One
  \item Item Two
\end{compactitem}
\end{ltgexample}

One can enumerate items as follows:

\begin{ltgexample}
\begin{enumerate}
  \item Item One
  \item Item Two
\end{enumerate}
\end{ltgexample}

With the package paralist, one can create enumerations with lesser spacing:

\begin{ltgexample}
\begin{compactenum}
  \item Item One
  \item Item Two
\end{compactenum}
\end{ltgexample}

With paralist, one can even have all items typeset after each other and have them clean in the TeX document:

\begin{ltgexample}
\begin{inparaenum}
  \item All these items...
  \item ...appear in one line
  \item This is enabled by the paralist package.
\end{inparaenum}
\end{ltgexample}

\section{Abkürzungen}

Mit \verb+\gls{...}+ können Abkürzungen eingebaut werden, beim ersten Aufrufen wird die lange Form eingesetzt.
Beim wiederholten Verwenden von \verb+\gls{...}+ wird automatisch die Kurzform angezeigt.
Außerdem wird die Abkürzung automatisch in die Abkürzungsliste eingefügt.
Mit \verb+\glspl{...}+ wird die Pluralform verwendet.
Möchte man, dass bei der ersten Verwendung direkt die Kurzform erscheint, so kann man mit \verb+\glsunset{...}+ eine Abkürzung als bereits verwendet markieren.
Das Gegenteil erreicht man mit \verb+\glsreset{...}+.

Definiert werden Abkürzungen in der Datei \textit{abbreviationstex} mithilfe von \verb+\newacronym{...}{...}{...}+.

Mehr Infos unter: \url{https://ctan.org/pkg/bib2gls}.

\begin{ltgexample}
Beim ersten Durchlauf betrug die \gls{fr} 5.
Beim zweiten Durchlauf war die \gls{fr} 3.
Die Pluralform sieht man hier: \glspl{er}.
Um zu demonstrieren, wie das Abkürzungsverzeichnis bei längeren Beschreibungstexten aussieht, muss hier noch \glspl{rdbms} erwähnt werden.

\gls{dante} is a local \TeX\ user group.
The German-speaking local \TeX\ user group is \gls{dante}.
A \gls{gp} is a medical doctor.
I went to my surgery to see the \gls{gp}.
\end{ltgexample}

\section{Other Features}

\begin{ltgexample}
The words \enquote{workflow} and \enquote{dwarflike} can be copied from the PDF and pasted to a text file.
\end{ltgexample}

\begin{ltgexample}
The symbol for powerset is now correct: $\powerset$ and not a Weierstrass p ($\wp$).

$\powerset({1,2,3})$
\end{ltgexample}

\begin{ltgexample}
Brackets work as designed:
<test>
One can also input backticks in verbatim text: \verb|`test`|.
\end{ltgexample}


\section{Varioref examples}
\label{sec:ex:vref}

Varioref demonstration: Vref at beginning of sentence, vref in all other cases.

\begin{ltgexample}
\Vref{fig:ex:cref} shows a simple fact, although \vref{fig:ex:cref} could also show something else.

\Vref{tab:ex:cref} shows a simple fact, although \vref{tab:ex:cref} could also show something else.

\Vref{sec:ex:cref} shows a simple fact, although \vref{sec:ex:cref} could also show something else.
\end{ltgexample}

\section{Citations}

When referencing something from the bibliography file, it will automatically appear in the references section.
If a reference is not cited, it is not appearing there.

\begin{ltgexample}
Standard case: Citing indirectly citing something~\cite{mwe}.
In case one wants to name the author: \textcite{mwe} shows a minimal \LaTeX{} example.
\end{ltgexample}

Note that \texttt{\textbackslash textcite\{mwe\}} prints both the author and the reference to the bibliography entry.

Remember that you have to call \texttt{biber main-german} to generate the bibliography data for \texttt{lualatex}.
You will need to run \texttt{lualatex} twice to ensure that the page numbers are updated correctly.


In the bibliography, use \texttt{\textbackslash textsuperscript} for \enquote{st}, \enquote{nd}, \ldots:
E.g., \enquote{The 2\textsuperscript{nd} conference on examples}.
When you use \href{https://www.jabref.org}{JabRef}, you can use the clean up command to achieve that.
See \url{https://help.jabref.org/en/CleanupEntries} for an overview of the cleanup functionality.

\section{Miscellaneous Examles}
\label{ssec:example}

Referencetest: \Cref{ssec:example}, \cref{fig:Abbildung} und \cref{alg:example}.

\begin{ltgexample}
Checkmark: \dingcheck.
Crossmark: \dingcross.
\end{ltgexample}

\begin{figure}
  \missingfigure{}
  \caption{Abbildung}
  \label{fig:Abbildung}
\end{figure}

\begin{landscape}
  \begin{figure}
    \missingfigure{}
    \caption{Gedrehte Abbildung}
    \label{fig:AbbildungGedreht}
  \end{figure}
\end{landscape}

\subsection{Algorithmen}

\begin{algorithm}
  \caption{$algo$}
  \label{alg:example}
  \begin{algorithmic}[1]
    \State $a \gets 0$
    \State State 2\label{alg1:state2}
  \end{algorithmic}
\end{algorithm}

\begin{algorithm}
  \caption{Algorithmus 2}
  \label{alg:example2}
  \begin{algorithmic}[1]
    \State $a \gets 0$
    \State State 2\label{alg2:state2}
  \end{algorithmic}
\end{algorithm}

\Cref{alg:example} hat bereits einen Algorithmus gezeigt.
Test der Zeilenreferenzierung: Zeile~\ref{alg1:state2} (\cref{alg:example}) und Zeile~\ref{alg2:state2} (\cref{alg:example2}).

\subsection{Definitionen}
\begin{definition}[Title]
  \label{def:def1}
  Definition Text
\end{definition}

\Cref{def:def1} zeigt \ldots

\subsection{Aufzählungen}

\begin{enumerate}[label=\alph*)]
  \item a
  \item b
  \item c
  \item d
\end{enumerate}

Equivalent to paralist's inparaenum:
\begin{enumerate*}[label=\alph*)]
  \item a
  \item b
  \item c
  \item d
\end{enumerate*}

\begin{description}
  \item[first] Erstens
  \item[second] Zweitens
  \item[third] Drittens
\end{description}

\begin{description}
  \item[\texttt{first}] Erstens
  \item[\texttt{second}] Zweitens
  \item[\texttt{third}] Drittens
\end{description}

%works only if package enumitem is loaded
\begin{description}[font=\ttfamily]
  \item[first] Erstens
  \item[second] Zweitens
  \item[third] Drittens
\end{description}

\begin{description}[style=unboxed]
  \item[first label with a long description text breaking over one line. Enabled by enumitem package] Erstens
  \item[second] Zweitens
  \item[third] Drittens
\end{description}

\begin{Description}
  \item[first label with a long description text breaking over one line. Defined in template.tex] Erstens
  \item[second] Zweitens
  \item[third] Drittens
\end{Description}

\begin{itemize}
  \item Erstens
  \item Zweitens
  \item Drittens
\end{itemize}

Optionaler Parameter ändert den Marker, der vorangestellt ist.
Siehe \url{http://www.weinelt.de/latex/item.html}.
\begin{itemize}
  \item[A] Erstens
  \item[B] Zweitens
  \item[C] Drittens
\end{itemize}

Falsche Benutzung des optionalen Parameters wie folgt:
\begin{itemize}
  \item[first] Erstens
  \item[second] Zweitens
  \item[third] Drittens
\end{itemize}
Dabei ist zu beachten, dass es sich bei Einbindung von \texttt{enumitem} anders verhält als bei \texttt{paralist}.

\subsection{fquote}

\begin{fquote}[T.\ Informatiker]
  Bis nächsten Freitag ist das Programm fertig.
\end{fquote}

\begin{gfquote}{T.\ Informatiker}
  Bis nächsten Freitag ist das Programm fertig.
\end{gfquote}

%%% ===============================================================================
\chapter{Zusammenfassung und Ausblick}\label{sec:conclusion}
%%% ===============================================================================

Your conclusions are not just a factual summary of your work, but they position, interpret, and defend your findings against the state of the art that you discussed in \cref{sec:introduction:state-of-art}.
You specifically outline which concrete findings or methodological contributions advance our knowledge towards the general objective you introduced in \cref{sec:introduction:topic}.
Objectively discuss which parts you solved and in which parts you failed.

You should explicitly discuss limitations and shortcomings of your work and detail what kind of future studies are needed to overcome these limitations.
Be specific in the sense that your arguments for future work should be based on concrete findings and insights you obtained in your report.


%%% ===============================================================================
%%% Bibliography
%%% ===============================================================================


\printbibliography

% Enfore empty line after bibliography
\ \\
%
\noindent
Alle Links wurden zuletzt am 29.03.2021 geprüft.

%%% ===============================================================================

%\IfDefined{printindex}{\printindex}
%\IfDefined{printnomenclature}{\printnomenclature}

\clearpage
\appendix
% 'Anhang' ins Inhaltsverzeichnis
%\phantomsection
%\addcontentsline{toc}{chapter}{Anhang}
\addcontentsline{toc}{part}{Anhang}

%%% ===============================================================================
\chapter{My first appendix}\label{sec:appendix1}
%%% ===============================================================================

\lipsum[1]

\pagestyle{empty}
\renewcommand*{\chapterpagestyle}{empty}
\clearpage
\backmatter
\thispagestyle{empty}

\vspace*{\fill}
\pagestyle{empty}

{\normalsize
\begin{center}\textbf{Eidesstattliche Erklärung}\end{center}
\blindtext[1]
\vspace*{1cm}\\
Hamburg, den XX.XX.20XX
\hspace*{\fill}\begin{tabular}{@{}l@{}}\hline
\makebox[5cm]{Vorname Nachname}
\end{tabular}
\vspace*{3cm}

%TODO Dies ist optional, ggf. löschen!
\begin{center}\textbf{Veröffentlichung}\end{center}
\blindtext[1]
\vspace*{1cm}\\
Hamburg, den XX.XX.20XX
\hspace*{\fill}\begin{tabular}{@{}l@{}}\hline
\makebox[5cm]{Vorname Nachname}
\end{tabular}
}
\vspace*{\fill}
\end{document}