Add module for testing generic curve-like values

module Generic.Curve2d
    exposing
        ( scaling
        , translation
        )

import Fuzz exposing (Fuzzer)
import OpenSolid.Geometry.Expect as Expect
import OpenSolid.Geometry.Fuzz as Fuzz
import OpenSolid.Point2d as Point2d exposing (Point2d)
import OpenSolid.Vector2d as Vector2d exposing (Vector2d)
import Test exposing (Test)

parameterValue : Fuzzer Float
parameterValue =
    Fuzz.floatRange 0 1

scaling : Fuzzer a -> (Point2d -> Float -> a -> a) -> (a -> Float -> Point2d) -> Test
scaling fuzzer scaleAbout pointOn =
    Test.fuzz4
        fuzzer
        Fuzz.point2d
        Fuzz.scalar
        parameterValue
        "scaleAbout"
        (\curve basePoint scale t ->
            let
                scaledCurve =
                    scaleAbout basePoint scale curve

                originalPoint =
                    pointOn curve t

                pointOnScaledCurve =
                    pointOn scaledCurve t

                scaledPoint =
                    Point2d.scaleAbout basePoint scale originalPoint
            in
            pointOnScaledCurve |> Expect.point2d scaledPoint
        )

translation : Fuzzer a -> (Vector2d -> a -> a) -> (a -> Float -> Point2d) -> Test
translation fuzzer translateBy pointOn =
    Test.fuzz3
        fuzzer
        Fuzz.vector2d
        parameterValue
        "translateBy"
        (\curve displacement t ->
            let
                translatedCurve =
                    translateBy displacement curve

                originalPoint =
                    pointOn curve t

                pointOnTranslatedCurve =
                    pointOn translatedCurve t

                translatedPoint =
                    Point2d.translateBy displacement originalPoint
            in
            pointOnTranslatedCurve |> Expect.point2d translatedPoint
        )


module Utils.List exposing (move, indexedFoldl, indexedFoldr)

move : Int -> Int -> List a -> List a
move from to list =
    -- TODO: clear this function
    let
        reducer append i next ( state, found, list ) =
            if state == 0 && from == i then
                ( 1, Just next, list )
            else if state == 1 && to == i then
                let
                    list_ =
                        found
                            |> Maybe.map (\item -> append item next list)
                            |> Maybe.withDefault []
                in
                    ( 2, Nothing, list_ )
            else
                ( state, found, next :: list )
    in
        if from < to then
            let
                ( _, _, list_ ) =
                    indexedFoldl (reducer appendLeft) ( 0, Nothing, [] ) list
            in
                List.reverse list_
        else if from > to then
            let
                ( _, _, list_ ) =
                    indexedFoldr (reducer appendRight) ( 0, Nothing, [] ) list
            in
                list_
        else
            list

indexedFoldl : (Int -> a -> b -> b) -> b -> List a -> b
indexedFoldl func init xs =
    xs
        |> List.foldl (countUp func) ( init, 0 )
        |> Tuple.first

indexedFoldr : (Int -> a -> b -> b) -> b -> List a -> b
indexedFoldr func init xs =
    xs
        |> List.foldr (countDown func) ( init, (List.length xs) - 1 )
        |> Tuple.first

-- internals

appendLeft : a -> a -> List a -> List a
appendLeft a b list =
    b :: (a :: list)

appendRight : a -> a -> List a -> List a
appendRight a b list =
    a :: (b :: list)

countUp : (Int -> a -> b -> b) -> a -> ( b, Int ) -> ( b, Int )
countUp func value ( acc, index ) =
    ( func index value acc, index + 1 )

countDown : (Int -> a -> b -> b) -> a -> ( b, Int ) -> ( b, Int )
countDown func value ( acc, index ) =
    ( func index value acc, index - 1 )


module Passing.Unexposed exposing (all)

import Expect
import Test exposing (..)

all : Test
all =
    describe "all"
        [ test "Expect.equal works" <|
            \() ->
                "success"
                    |> Expect.equal "success"
        , testTrue
        ]

testTrue : Test
testTrue =
    test "Expect.true works" <|
        \() ->
            True
                |> Expect.true "this should never fail!"

testUnexposed : Test
testUnexposed =
    test "This test is unexposed and should not run!" <|
        \() ->
            Expect.fail "This should fail if run!"


module TextReverser where

import Graphics.Input as Input
import Html (Html, CssProperty, style, prop, text, on, getValue, toElement)
import Html.Tags (div, input)
import Html.Attributes (..)
import String

-- VIEW

scene : String -> Element
scene string =
    toElement 400 200 (stringReverser string)

stringReverser : String -> Html
stringReverser string =
    div []
        [ stringInput string
        , reversedString string
        ]

reversedString : String -> Html
reversedString string =
    div [ style myStyle ] [ text (String.reverse string) ]

stringInput : String -> Html
stringInput string =
    input
        [ id "new-todo"
        , placeholder "Text to reverse"
        , autofocus True
        , value string
        , on "input" getValue actions.handle identity
        , style myStyle
        ]
        []

myStyle : [CssProperty]
myStyle =
    [ prop "width" "100%"
    , prop "height" "40px"
    , prop "padding" "10px 0"
    , prop "font-size" "2em"
    , prop "text-align" "center"
    ]

-- SIGNALS

main : Signal Element
main =
    scene <~ actions.signal

actions : Input.Input String
actions =
    Input.input ""


module OpenSolid.Core.Encode (interval, vector2d, vector3d, direction2d, direction3d, point2d, point3d, boundingBox2d, boundingBox3d, axis2d, axis3d, plane3d, frame2d, frame3d) where

{-| JSON encoders for the core OpenSolid types.
-}

import Json.Encode exposing (..)
import OpenSolid.Core.Types exposing (..)


Add visual test of convex hull construction

module ConvexHull exposing (..)

import Html exposing (Html)
import Html.Events
import OpenSolid.BoundingBox2d as BoundingBox2d exposing (BoundingBox2d)
import OpenSolid.Point2d as Point2d exposing (Point2d)
import OpenSolid.Polygon2d as Polygon2d
import OpenSolid.Svg as Svg
import Random exposing (Generator)
import Svg
import Svg.Attributes

type alias Model =
    { points : List Point2d
    }

type Msg
    = Click
    | NewRandomPoints (List Point2d)

renderBounds : BoundingBox2d
renderBounds =
    BoundingBox2d.fromExtrema
        { minX = 0
        , maxX = 800
        , minY = 0
        , maxY = 600
        }

pointsGenerator : Generator (List Point2d)
pointsGenerator =
    let
        { minX, maxX, minY, maxY } =
            BoundingBox2d.extrema renderBounds

        pointGenerator =
            Random.map2 (\x y -> Point2d.fromCoordinates ( x, y ))
                (Random.float (minX + 30) (maxX - 30))
                (Random.float (minY + 30) (maxY - 30))
    in
    Random.int 2 32
        |> Random.andThen
            (\listSize -> Random.list listSize pointGenerator)

generateNewPoints : Cmd Msg
generateNewPoints =
    Random.generate NewRandomPoints pointsGenerator

init : ( Model, Cmd Msg )
init =
    ( { points = [] }, generateNewPoints )

update : Msg -> Model -> ( Model, Cmd Msg )
update message model =
    case message of
        Click ->
            ( model, generateNewPoints )

        NewRandomPoints points ->
            ( { model | points = points }, Cmd.none )

view : Model -> Html Msg
view model =
    let
        convexHull =
            Polygon2d.fromConvexHull model.points
    in
    Html.div [ Html.Events.onClick Click ]
        [ Svg.render2d renderBounds <|
            Svg.g []
                [ Svg.polygon2d
                    [ Svg.Attributes.fill "lightblue"
                    , Svg.Attributes.stroke "blue"
                    ]
                    convexHull
                , Svg.g [] <|
                    List.indexedMap
                        (\index point -> Svg.text2d [] point (toString index))
                        (Polygon2d.vertices convexHull)
                , Svg.g [] (List.map (Svg.point2d []) model.points)
                ]
        ]

main : Program Never Model Msg
main =
    Html.program
        { init = init
        , update = update
        , view = view
        , subscriptions = always Sub.none
        }


Create a function that draw an arc given the two endpoints and the maximum displacement from a straight line.

module Arc where

import Color as C
import Graphics.Collage as GC
import List as L
import Mouse
import Signal ((<~))

cX = 1000
cY = 500

main = plotArc 5 (0, 0) << canvasCoords <~ Mouse.position

canvasCoords : (Int, Int) -> (Float, Float)
canvasCoords (x, y) = (toFloat x - cX/2, cY/2 - toFloat y)

plotArc h head tail =
  GC.collage cX cY [
  GC.circle 5 |> GC.filled C.red |> GC.move head,
  GC.circle 5 |> GC.filled C.blue |> GC.move tail,
  arc 100 tail head h |> GC.traced GC.defaultLine  ]

arc res tail head h =
  let
    mid = midpoint head tail
    l = length tail head
    r = (l^2 + 4 * h^2) / (8 * h)
    inclination = rotationAngle tail head + degrees 90
    arcCenter = polar mid (r-h) inclination

    arcLength = 2 * atan2 (0.5 * l) (r - h)
    tailAngle = rotationAngle arcCenter tail
    incrAngle i = arcLength * i * 0.01 + tailAngle

    points = L.map (polar arcCenter r << incrAngle) [ 0 .. res ]
  in GC.path points

midpoint (x1, y1) (x2, y2) = (0.5 * (x1 + x2), 0.5 * (y1 + y2))

length (x1, y1) (x2, y2) = sqrt ((x1 - x2)^2 + (y1 - y2)^2)

rotationAngle (x1, y1) (x2, y2) = atan2 (y2 - y1) (x2 - x1)

type alias Point = (Float, Float)

polar : Point -> Float -> Float -> Point
polar (x0, y0) r theta =
  let
    x = r * (cos theta)
    y = r * (sin theta)
  in (x0 + x, y0 + y)


% Order matters!
\include{docversion}
\include{colors}
\include{header-footer}
\include{fonts}
\include{headings}

Set page counter to 1

% Order matters!
\include{docversion}
\include{colors}
\include{header-footer}
\include{fonts}
\include{headings}

% We consider the cover to be p.1
\setcounter{page}{1}


\input{../../common/style/global.tex}
\input{../../common/style/layout.tex}
\input{res/local}

\title{\textbf{Norme di Progetto}}
\author{BugBuster}

\date{23 Maggio 2016}

\begin{document}

%\maketitle

\makeFrontPage

\tableofcontents
\listoffigures
\listoftables

\include{res/versions}
\include{res/listOfSections}

\end{document}

Remove list of tables and figures There's no tables or figures in the document

\input{../../common/style/global.tex}
\input{../../common/style/layout.tex}
\input{res/local}

\title{\textbf{Norme di Progetto}}
\author{BugBuster}

\date{23 Maggio 2016}

\begin{document}

%\maketitle

\makeFrontPage

\tableofcontents
%\listoffigures
%\listoftables

\include{res/versions}
\include{res/listOfSections}

\end{document}


\chapter{Removed systems}

This appendix contains a list of systems that were removed for one of
several reasons:

\begin{itemize}
\item The code used to work, but is no longer working due to updates
  in code that it depends on.  More work is needed for it to be usable
  again.
\item The code never worked, and it needs more work in order for it to
  be considered part of \sysname{}.
\item The code never worked, and we have no ambition to make it work,
  but it nevertheless contains interesting ideas that we might revive
  in the future.
\end{itemize}

\section{Stack-oriented \clanguage{} backend}

Removed 2016-08-09.

SHA1 ID: b983763485ac5efb6fe3319f015b414b3e7ea5f5

Add section for removed concrete Common Lisp backend.

\chapter{Removed systems}

This appendix contains a list of systems that were removed for one of
several reasons:

\begin{itemize}
\item The code used to work, but is no longer working due to updates
  in code that it depends on.  More work is needed for it to be usable
  again.
\item The code never worked, and it needs more work in order for it to
  be considered part of \sysname{}.
\item The code never worked, and we have no ambition to make it work,
  but it nevertheless contains interesting ideas that we might revive
  in the future.
\end{itemize}

\section{Stack-oriented \clanguage{} backend}

Removed 2016-08-09.

SHA1 ID: b983763485ac5efb6fe3319f015b414b3e7ea5f5

\section{Concrete \commonlisp{} backend}

Removed 2016-08-09.

SHA1 ID: 3e0ca56b20ab49b27ae16bbe2046b975ac27be3e


\chapter*{}

\mbox{}

\textit{,,First they ignore you. Then they laught about you. Then
they fight you. And then you win.''}

\raggedleft{---  Mahatma Gandhi}

Add my own quote of choice.

\chapter*{}

\mbox{}

\textit{,,If you think technology can solve your security problems, then you don't understand the problems and you don't understand the technology.''}

\raggedleft{---  Bruce Schneier}


\author{Guido van Rossum\\
	Fred L. Drake, Jr., editor}
\authoraddress{
	\strong{PythonLabs}\\
	Email: \email{python-docs@python.org}
}

\date{December 31, 2002}	% XXX update before release!
\release{2.3}			% software release, not documentation
\setreleaseinfo{a1+}		% empty for final release
\setshortversion{2.3}		% major.minor only for software

Revert merge from 2.3 alpha 1 release branch; the change does not apply to the trunk.

\author{Guido van Rossum\\
	Fred L. Drake, Jr., editor}
\authoraddress{
	\strong{PythonLabs}\\
	Email: \email{python-docs@python.org}
}

\date{\today}			% XXX update before release!
\release{2.3}			% software release, not documentation
\setreleaseinfo{a1+}		% empty for final release
\setshortversion{2.3}		% major.minor only for software


\author{Guido van Rossum}

\authoraddress{
	Corporation for National Research Initiatives (CNRI) \\
	1895 Preston White Drive, Reston, Va 20191, USA \\
	E-mail: \email{guido@CNRI.Reston.Va.US}, \email{guido@python.org}
}

\date{July 6, 1999}			% XXX update before release!
\release{1.5.2}

Set the date and version to reflect the actual status, not the last released status. Has to be changed just before publishing anyway.

\author{Guido van Rossum}

\authoraddress{
	Corporation for National Research Initiatives (CNRI) \\
	1895 Preston White Drive, Reston, Va 20191, USA \\
	E-mail: \email{guido@CNRI.Reston.Va.US}, \email{guido@python.org}
}

\date{\today}			% XXX update before release!
\release{1.5.2$+$}


% vim: set tw=160:

\chapter*{Gleicheitsgrundsatz}
Aus Gründen der Lesbarkeit wurde in dieser Arbeit darauf verzichtet, geschlechtsspezifische Formulierungen zu verwenden. Jedoch möchte der Author ausdrücklich
festhalten, dass die bei Personen verwendeten maskulinen Formen für beide Geschlechter zu verstehen sind.\\

Make it really equal :-)

% vim: set tw=160:

\chapter*{Gleicheitsgrundsatz}
Aus Gründen der Lesbarkeit wurde in dieser Arbeit darauf verzichtet, geschlechtsspezifische Formulierungen zu verwenden. Jedoch möchte der Author ausdrücklich
festhalten, dass die bei Personen verwendeten femininen oder maskulinen Formen für beide Geschlechter zu verstehen sind.


%----------------------------------------------------------------------------------
% Exemplo do uso dos estilos bibliográficos tcc-{alpha,num}.bst.
% Veja o arquivo tcc.cls para mais detalhes e instruções.
%----------------------------------------------------------------------------------

-- Atenção! Sempre confira as entradas BibTeX copiadas de
bibliotecas digitais, pois muitas vezes as mesmas possuem o
formato incorreto, ou falta alguma informação necessária para
a referência.

@article{KOEHLEROTTIGER02,
   author={Jana Koehler and Daniel Ottiger},
   journal={AI Magazine},
   number={3},
   pages={59--78},
   publisher={American Association for Artificial Intelligence (AAAI)},
   title={An AI-Based Approach to Destination Control in Elevators},
   volume={23},
   year={2002},
}

@misc{HORN10,
   author={Emily Horn},
   title={IBM News room - 2010-04-29 IBM Survey Shows Strengths, Gaps in U.S. Office Buildings - United States},
   url={http://www-03.ibm.com/press/us/en/pressrelease/30191.wss},
   urlaccessdate={Ago. 2015},
   year={2010}
}

@misc{MCGAR15,
   author={Justin McGar},
   title={Smart Elevators and the Internet of Things},
   url={https://sourceable.net/smart-elevators-and-the-internet-of-things/},
   urlaccessdate={Ago. 2015},
   year={2015}
}

Remove comments from bibliography file.


% Encoding: UTF-8

@Article{ostgaard2002,
  author = {Foo Bar},
  title =  {Energy},
  year =   {2012}
}

@Comment{jabref-meta: DATABASE_TYPE:BibTeX;}

@Comment{jabref-meta: saveActions:enabled;pages[PageNumbersFormatter,DateFormatter,]title[LowerCaseChanger,];}

@Comment{jabref-meta: saveOrderConfig:original;;false;;false;;false;}

Update structure of example file to new serialization

% Encoding: UTF-8

@Article{ostgaard2002,
  author = {Foo Bar},
  title =  {Energy},
  year =   {2012}
}

@Comment{jabref-meta: DATABASE_TYPE:BibTeX;}

@Comment{jabref-meta: saveActions:enabled;pages[PageNumbersFormatter,DateFormatter]
title[LowerCaseChanger]
;}

@Comment{jabref-meta: saveOrderConfig:original;;false;;false;;false;}


\RequirePackage[l2tabu, orthodox]{nag} % nag you about old packages and commands
\documentclass{article}
% Document Classes
% article - basic use
% report - longer reports
% beamer - writing presentations

% Document Class Options
% 10pt,11pt,12pt - size of main font
% twocolumn - typeset two columns

% The LaTeX Font Catalogue - for all types of good alternate fonts
% http://www.tug.dk/FontCatalogue/

\usepackage{graphicsx} % allow importing images
\usepackage{placeins} % use \FloatBarrier for barriers for images to sections
\usepackage[margin=1in]{geometry} % change margins
\usepackage[hidelinks]{hyperref} % make nice URL links, remove decorations
\usepackage{booktabs} % make nicer tables

\pagenumbering{gobble} % suppress page numbering

\title{\LaTeX~Notes}
\author{}
\date{}

\begin{document}

\maketitle

% manual bibliography
\begin{thebibliography}{9}

\bibitem{lamport94} % citation key
    Leslie Lamport,
    \emph{\LaTeX\@: a document preparation system},
    Addison Wesley, Massachusetts,
    2nd edition,
    1994.

\end{thebibliography}

\end{document}

Add LaTeX note on pipe character

\RequirePackage[l2tabu, orthodox]{nag} % nag you about old packages and commands
\documentclass{article}
% Document Classes
% article - basic use
% report - longer reports
% beamer - writing presentations

% Document Class Options
% 10pt,11pt,12pt - size of main font
% twocolumn - typeset two columns

% The LaTeX Font Catalogue - for all types of good alternate fonts
% http://www.tug.dk/FontCatalogue/

\usepackage{graphicsx} % allow importing images
\usepackage{placeins} % use \FloatBarrier for barriers for images to sections
\usepackage[margin=1in]{geometry} % change margins
\usepackage[hidelinks]{hyperref} % make nice URL links, remove decorations
\usepackage{booktabs} % make nicer tables
\usepackage[T1]{fontenc} % allow pipe character natively + maybe other perks

\pagenumbering{gobble} % suppress page numbering

\title{\LaTeX~Notes}
\author{}
\date{}

\begin{document}

\maketitle

Here is a pipe symbol without doing anything special: |.

% manual bibliography
\begin{thebibliography}{9}

\bibitem{lamport94} % citation key
    Leslie Lamport,
    \emph{\LaTeX\@: a document preparation system},
    Addison Wesley, Massachusetts,
    2nd edition,
    1994.

\end{thebibliography}

\end{document}


% TeX file: 5.2 Discussion of Future Work

\par

Add bit on support vector machine implementation

% TeX file: 5.2 Discussion of Future Work
\par One idea that arose during the preliminary stages of the project that has
now become a work currently in progress is the implementation of support vector
machines. A support vector machine is a powerful algorithm used for prediction
in machine learning, often for classification purposes. In theory, it can allow
the user to draw flexible yet robust boundaries between data points given some
criterion. If properly implemented, models generated by this algorithm could
shed light on an entire class of inquiries, like what parts of the brain would
activate given increasing parametric gains and losses, and vice versa. The
mechanism by which support vector machines work make such topics natural to work
with, while also introducing an additional degree of resolution and confidence
in findings that pertain to these topics.
\par \indent
12345678901234567890123456789012345678901234567890123456789012345678901234567890|


\setlength{\parindent}{1em}
\title{Formal Semantics of the LLVM IR}
\author{David Lazar and Chucky Ellison (\texttt{\{lazar6,celliso2\}@illinois.edu})}
\organization{University of Illinois at Urbana-Champaign}

\maketitle

\setlength{\parindent}{8em}
% FIXME use dragon-vector.pdf for printing/high-quality
% some versions of acrobat reader break when using the vector :\
\includegraphics[width=0.14\textwidth]{latex/dragon.pdf}
\setlength{\parindent}{1em}

\begin{kblock}[text]
\section{Abstract}
This is the \K semantic definition of the LLVM assembly language (also known as the LLVM intermediate representation, or LLVM IR for short).
We aim to completely define the LLVM IR version 3.0+.
\textcolor{red}{This is a work-in-progress.}
\end{kblock}

Make the size of the dragon independent of the text width.

\setlength{\parindent}{1em}
\title{Formal Semantics of the LLVM IR}
\author{David Lazar and Chucky Ellison (\texttt{\{lazar6,celliso2\}@illinois.edu})}
\organization{University of Illinois at Urbana-Champaign}

\maketitle

\setlength{\parindent}{8em}
% FIXME use dragon-vector.pdf for printing/high-quality
% some versions of acrobat reader break when using the vector :\
\includegraphics[scale=0.27]{latex/dragon.pdf}
\setlength{\parindent}{1em}

\begin{kblock}[text]
\section{Abstract}
This is the \K semantic definition of the LLVM assembly language (also known as the LLVM intermediate representation, or LLVM IR for short).
We aim to completely define the LLVM IR version 3.0+.
\textcolor{red}{This is a work-in-progress.}
\end{kblock}


%!TEX root = ./article.tex

% Article Title
\def \ArticleTitle{Cloud4Things}

% Author(s) Name(s)
\def \AuthorA{Marcus Vin\'icius Paulino Gomes}

% Author(s) Email(s)
\def \AuthorAemail{marcus.paulino.gomes@tecnico.ulisboa.pt}

% Institution(s) Name(s)
\def \InstitutionA{Instituto Superior T\'ecnico, Universidade de Lisboa}

% Article Title
\newcommand {\Title} {\ArticleTitle}

% Authors
\newcommand {\Authors} {\IEEEauthorblockN{\AuthorA}}

% Institution
\newcommand {\Institutions} {\IEEEauthorblockA{\InstitutionA}\\
                            Email: \AuthorAemail}

% Variable to control if the bibliography must be include
\def \hasBibliography{1}

Update the article title according the change made in the dissertation.

%!TEX root = ./article.tex

% Article Title
\def \ArticleTitle{Cloud4Things: using Cloud infrastructure to support Smart Place applications}

% Author(s) Name(s)
\def \AuthorA{Marcus Vin\'icius Paulino Gomes}

% Author(s) Email(s)
\def \AuthorAemail{marcus.paulino.gomes@tecnico.ulisboa.pt}

% Institution(s) Name(s)
\def \InstitutionA{Instituto Superior T\'ecnico, Universidade de Lisboa}

% Article Title
\newcommand {\Title} {\ArticleTitle}

% Authors
\newcommand {\Authors} {\IEEEauthorblockN{\AuthorA}}

% Institution
\newcommand {\Institutions} {\IEEEauthorblockA{\InstitutionA}\\
                            Email: \AuthorAemail}

% Variable to control if the bibliography must be include
\def \hasBibliography{1}


\begin{table}[htbp]
\centering
\begin{tabular}{cccccc}

\hline
\rowcolor{lightgray}
\textbf{rlzi} & \textbf{sid} & \textbf{eid} & \textbf{gmv\_PGA} & \textbf{gmv\_SA(0.3)} & \textbf{gmv\_SA(1.0)} \\
\hline
0 & 0 & 0 & 0.062 & 0.119 & 0.157 \\
0 & 1 & 0 & 0.086 & 1.533 & 0.260 \\
0 & 2 & 0 & 0.223 & 1.647 & 0.232 \\
... & ... & ... & ... & ... & ... \\
1 & 4 & 99 & 2.467 & 0.750 & 1.918 \\
1 & 5 & 99 & 0.601 & 0.828 & 2.272 \\
1 & 6 & 99 & 0.514 & 0.340 & 1.202
\hline

\end{tabular}
\caption{Example of a ground motion fields csv output file for a scenario (\href{https://raw.githubusercontent.com/gem/oq-engine/master/doc/manual/oqum/hazard/verbatim/output_scenario_gmfs.csv}{Download example})}
\label{output:gmf_scenario}
\end{table}

Add a missing newline in a csv table [skip CI]

\begin{table}[htbp]
\centering
\begin{tabular}{cccccc}

\hline
\rowcolor{lightgray}
\textbf{rlzi} & \textbf{sid} & \textbf{eid} & \textbf{gmv\_PGA} & \textbf{gmv\_SA(0.3)} & \textbf{gmv\_SA(1.0)} \\
\hline
0 & 0 & 0 & 0.062 & 0.119 & 0.157 \\
0 & 1 & 0 & 0.086 & 1.533 & 0.260 \\
0 & 2 & 0 & 0.223 & 1.647 & 0.232 \\
... & ... & ... & ... & ... & ... \\
1 & 4 & 99 & 2.467 & 0.750 & 1.918 \\
1 & 5 & 99 & 0.601 & 0.828 & 2.272 \\
1 & 6 & 99 & 0.514 & 0.340 & 1.202 \\
\hline

\end{tabular}
\caption{Example of a ground motion fields csv output file for a scenario (\href{https://raw.githubusercontent.com/gem/oq-engine/master/doc/manual/oqum/hazard/verbatim/output_scenario_gmfs.csv}{Download example})}
\label{output:gmf_scenario}
\end{table}


@article{JV02,
author       =       "D. Joyner and H. Verrill",
title        =       "{\it Notes on toric varieties}, posted at Math ArXiV,
http://front.math.ucdavis.edu/math.AG/0208065",
journal    =       "(appeared as {\it Computing with toric varieties},
Journal of Symbolic Computation, Volume 42, Issue 5, May 2007, Pages 511-532)",
year         =        2002
}

@book{F93,
author       =       "W. Fulton",
title        =       "Introduction to toric varieties",
publisher    =       "Princeton University Press",
year         =       1993
}

@book{Gua05,
author       =       "J. Fields, D. Joyner, Cen Tjhai, R. Miller, T. Boothby, R. Baart,
J. Cramwinckel, E. Roijackers and E. Minkes,"
title    =       "Manual for GUAVA - an error-correcting codes
package for GAP, version 3.10.",
publisher    =       "www.gap-system.org/pkg/guava/",
year         =       2009
}

Fix problems with the Gua05 BibTeX entry.

@article{JV02,
author       =       "D. Joyner and H. Verrill",
title        =       "{\it Notes on toric varieties}, posted at Math ArXiV,
http://front.math.ucdavis.edu/math.AG/0208065",
journal    =       "(appeared as {\it Computing with toric varieties},
Journal of Symbolic Computation, Volume 42, Issue 5, May 2007, Pages 511-532)",
year         =        2002
}

@book{F93,
author       =       "W. Fulton",
title        =       "Introduction to toric varieties",
publisher    =       "Princeton University Press",
year         =       1993
}

@book{Gua05,
author       =       "J. Fields and D. Joyner and Cen Tjhai and R. Miller and T. Boothby and R. Baart and
J. Cramwinckel and E. Roijackers and E. Minkes",
title    =       "Manual for GUAVA --- an error-correcting codes
package for GAP, version 3.10",
publisher    =       "www.gap-system.org/pkg/guava/",
year         =       2009
}


\documentclass[12pt]{report}
\usepackage{mystyle}
\usepackage{subfiles}

\begin{document}

\subfile{./tex/front-matter}
\subfile{./tex/introduction}
\subfile{./tex/engineering}
\subfile{./tex/background}
\subfile{./tex/prototypes}
\subfile{./tex/case-study-fourth-year-system}
\subfile{./tex/case-study-research-ide}
\subfile{./tex/platform}
\subfile{./tex/conclusion}

\include{./tex/citations}

% Add appendices now.
\appendix

\subfile{./tex/appendix-use-cases-1}
\subfile{./tex/appendix-use-cases-2}
\subfile{./tex/appendix-framework-research}

%\chapter{Extra Simulation Results}
%
%\chapter{Review of Linear Algebra}

\end{document}

Move platform before research IDE

\documentclass[12pt]{report}
\usepackage{mystyle}
\usepackage{subfiles}

\begin{document}

\subfile{./tex/front-matter}
\subfile{./tex/introduction}
\subfile{./tex/engineering}
\subfile{./tex/background}
\subfile{./tex/prototypes}
\subfile{./tex/case-study-fourth-year-system}
\subfile{./tex/platform}
\subfile{./tex/case-study-research-ide}
\subfile{./tex/conclusion}

\include{./tex/citations}

% Add appendices now.
\appendix

\subfile{./tex/appendix-use-cases-1}
\subfile{./tex/appendix-use-cases-2}
\subfile{./tex/appendix-framework-research}

%\chapter{Extra Simulation Results}
%
%\chapter{Review of Linear Algebra}

\end{document}


\chapter{Using command tables}

A \emph{command table} is an object that is used to determine what
commands are available in a particular context and the ways in which
commands can be executed.

Simple applications do not manage command tables explicitly.  A
default command table is created as a result of a call to the macro
\texttt{define-application-frame} and that command table has the same
name as the application frame.

Each command table has a \emph{name} and that CLIM manages a global
\emph{namespace} for command tables.

\Defun {find-command-table} {name \key (errorp t)}

This function returns the command table with the name \textit{name}.
If there is no command table with that name, then what happens depends
on the value of \textit{errorp}.  If \textit{errorp} is \emph{true},
then an error of type \texttt{command-table-not-found} is signaled.
If \textit{errorp} is \emph{false}, otherwise \texttt{nil} is
returned.

Add documentation for function for creating command tables.

\chapter{Using command tables}

A \emph{command table} is an object that is used to determine what
commands are available in a particular context and the ways in which
commands can be executed.

Simple applications do not manage command tables explicitly.  A
default command table is created as a result of a call to the macro
\texttt{define-application-frame} and that command table has the same
name as the application frame.

Each command table has a \emph{name} and that CLIM manages a global
\emph{namespace} for command tables.

\Defun {find-command-table} {name \key (errorp t)}

This function returns the command table with the name \textit{name}.
If there is no command table with that name, then what happens depends
on the value of \textit{errorp}.  If \textit{errorp} is \emph{true},
then an error of type \texttt{command-table-not-found} is signaled.
If \textit{errorp} is \emph{false}, otherwise \texttt{nil} is
returned.

\Defmacro {define-command-table} {name \key inherit-from menu
  inherit-menu}

\Defmacro {make-command-table} {name \key inherit-from menu
  inherit-menu (errorp t)}

By default command tables inherit from
\texttt{global-command-table}. According to the CLIM~2.0
specification, a command table inherits from no command table if
\texttt{nil} is passed as an explicit argument to
\textit{inherit-from}. In revision~2.2 all command tables must inherit
from \texttt{global-command-table}. McCLIM treats a \texttt{nil} value
of \textit{inherit-from} as specifying \texttt{'(global-command-table)}.


\begin{table}[htbp]
\centering
\resizebox{\columnwidth}{!}{
\begin{tabular}{cclll}

\hline
\rowcolor{lightgray}
\textbf{ordinal} & \textbf{branch\_path} & \textbf{weight} \\
\hline
0 & b1$\sim$b11\_b21 & 0.1125 \\
1 & b1$\sim$b11\_b22 & 0.075 \\
2 & b1$\sim$b12\_b21 & 0.0375 \\
3 & b1$\sim$b12\_b22 & 0.025 \\
4 & b2$\sim$b11\_b21 & 0.3375 \\
5 & b2$\sim$b11\_b22 & 0.225 \\
6 & b2$\sim$b12\_b21 & 0.1125 \\
7 & b2$\sim$b12\_b22 & 0.075 \\
\hline

\end{tabular}
}
\caption{Example of a realizations file}
\label{output:realizations}
\end{table}

Reduce the size of gigantic Table 4.3

\begin{table}[htbp]
\centering
\begin{tabular}{cclll}

\hline
\rowcolor{lightgray}
\textbf{ordinal} & \textbf{branch\_path} & \textbf{weight} \\
\hline
0 & b1$\sim$b11\_b21 & 0.1125 \\
1 & b1$\sim$b11\_b22 & 0.075 \\
2 & b1$\sim$b12\_b21 & 0.0375 \\
3 & b1$\sim$b12\_b22 & 0.025 \\
4 & b2$\sim$b11\_b21 & 0.3375 \\
5 & b2$\sim$b11\_b22 & 0.225 \\
6 & b2$\sim$b12\_b21 & 0.1125 \\
7 & b2$\sim$b12\_b22 & 0.075 \\
\hline

\end{tabular}
\caption{Example of a realizations file}
\label{output:realizations}
\end{table}


% TeX file: 5.2 Discussion of Future Work
\par One idea that arose during the preliminary stages of the project that has
now become a work currently in progress is the implementation of support vector
machines. A support vector machine is a powerful algorithm used for prediction
in machine learning, often for classification purposes. In theory, it can allow
the user to draw flexible yet robust boundaries between data points given some
criterion. If properly implemented, models generated by this algorithm could
shed light on an entire class of inquiries, like what parts of the brain would
activate given increasing parametric gains and losses, and vice versa. The
mechanism by which support vector machines work make such topics natural to work
with, while also introducing an additional degree of resolution and confidence
in findings that pertain to these topics.
\par \indent
12345678901234567890123456789012345678901234567890123456789012345678901234567890|

Add bit on decision trees

% TeX file: 5.2 Discussion of Future Work
\par One idea that arose during the preliminary stages of the project that has
now become a work currently in progress is the implementation of support vector
machines. A support vector machine is a powerful algorithm used for prediction
in machine learning, often for classification purposes. In theory, it can allow
the user to draw flexible yet robust boundaries between data points given some
criterion. If properly implemented, models generated by this algorithm could
shed light on an entire class of inquiries, like what parts of the brain would
activate given increasing parametric gains and losses, and vice versa. The
mechanism by which support vector machines work make such topics natural to work
with, while also introducing an additional degree of resolution and confidence
in findings that pertain to these topics.
\par \indent Another scheme that has the potential to be even more difficult to
implement is decision trees. What decision trees lack in predictive power, they
make up many fold in interpretability. Models generated via a decision tree can
clearly and simultaneously show the principle variables responsible as well as
how multiple variables interact with each other in the prediction of an outcome.
This would greatly facilitate the investigation of such questions as how much
does a brain area's activity have to change before the subject changes his/her
answer, or how great of an increase in potential gain is necessary for the brain
to recognize it over a given potential loss.


\section{Intro}

Aims and contributions of this work. Example from my last paper to see the format:
\surl{http://purl.pt/24107/1/iPres2013_PDF/CLEAR\%20a\%20credible\%20method\%20to\%20evaluate\%20website\%20archivability.pdf}

\begin{enumerate}
  \item Introduce the importance for blog preservation
  \item Explain the difficulties in harvesting blogs
  \item Explain why open source and Invenio
  \item Introduce the blog crawler
\end{enumerate}

Challenges consist of:
\begin{enumerate}
  \item Providing a high degree of automation
  \item Dealing with large volumes of data
\end{enumerate}

Add few sentences to intro.

\section{Intro}

Aims and contributions of this work. Example from my last paper to see the format:
\surl{http://purl.pt/24107/1/iPres2013_PDF/CLEAR\%20a\%20credible\%20method\%20to\%20evaluate\%20website\%20archivability.pdf}

\begin{enumerate}
  \item Introduce the importance for blog preservation
  \item Explain the difficulties in harvesting blogs
  \item Explain why open source and Invenio
  \item Introduce the blog crawler
\end{enumerate}

Challenges consist of:
\begin{enumerate}
  \item Providing a high degree of automation
  \item Dealing with large volumes of data
\end{enumerate}

Semi-structured nature of Web pages

Labeled ordered rooted trees
XML Path Language(XPath)


\documentclass{article}
\usepackage{algorithm,algorithmic,amsmath}

\begin{document}

  \begin{algorithmic}[1]
  \STATE initial population $\gets$ (pair, starting distribution) \
  \STATE population $\gets$ initial population

    \WHILE {repetitions $\leq$ max repetitions}
      \FOR{player in population}
      \FOR{opponent in (population - player)}
        \STATE match $\gets$ (player, opponent)
        \STATE results $\gets$ cache (match)
        \ENDFOR
      \ENDFOR
      \STATE population $\gets$ sorted(results)

      \STATE parent $\gets$  first in population
      \STATE child $\gets$ parent
      \STATE kill off $\gets$ random player from population
      \STATE population $\gets$   child replaces kill off
    \ENDWHILE
  \end{algorithmic}

\end{document}

Correct Moran process algorithm chart

\documentclass{article}
\usepackage{algorithm,algorithmic,amsmath}

\begin{document}

  \begin{algorithmic}[1]
  \STATE initial population $\gets$ (pair, starting distribution) \
  \STATE population $\gets$ initial population

    \WHILE {repetitions $\leq$ max repetitions}
      \FOR{player in population}
      \FOR{opponent in (population - player)}
        \STATE match $\gets$ (player, opponent)
        \STATE results $\gets$ cache (match)
        \ENDFOR
      \ENDFOR
      \STATE population $\gets$ sorted(results)
      \STATE parent $\gets$ selected randomly in proportion to total match payoffs
      \STATE child $\gets$ parent
      \STATE kill off $\gets$ random player from population
      \STATE population $\gets$ child replaces kill off
    \ENDWHILE
  \end{algorithmic}

\end{document}


\section{Abstract-""Syntax-""Tree (AST)}

Add AST diagramm to Entwurfsdokument.

\section{Abstract-""Syntax-""Tree (AST)}

\begin{figure}%

    \caption{Klassendiagramm des Abstract-""Syntax-""Trees}
    \includegraphics[angle=90,height=\textheight]{diagrams/ast_component.pdf}
    \label{ast_diag}
\end{figure}%


\chapter{Internet Data Handling \label{netdata}}

This chapter describes modules which support handling data formats
commonly used on the internet.  Some, like SGML and XML, may be useful
for other applications as well.

\localmoduletable

Remove comments about XML and HTML; those sections are no longer part of this chapter.

\chapter{Internet Data Handling \label{netdata}}

This chapter describes modules which support handling data formats
commonly used on the Internet.

\localmoduletable


% vim: set tw=160:

\chapter*{Kurzfassung}

\chapter*{Abstract}

Put both abstracts on one page. Thanks Peter!

% vim: set tw=160:

% 2010 Peter A. Menzel

\noindent
\begin{minipage}{\textwidth}
%%% minipage um Kapitel Kurzfassung UND Kapitel Abstract
%%% auf eine Seite zu binden
\chapter*{Kurzfassung}
\blindtext

\chapter*{Abstract}
\blindtext

\end{minipage}


\begin{table}[htbp]
\centering
\begin{tabular}{ccc}

\hline
\rowcolor{lightgray}
\textbf{site\_id} & \textbf{lon} & \textbf{lat} \\
\hline
0 & -122.57000 & 38.11300 \\
1 & -122.11400 & 38.11300 \\
2 & -122.00000 & 37.91000 \\
3 & -122.00000 & 38.00000 \\
4 & -122.00000 & 38.11300 \\
5 & -122.00000 & 38.22500 \\
6 & -121.88600 & 38.11300 \\
\hline

\end{tabular} (\href{https://raw.githubusercontent.com/gem/oq-engine/master/doc/manual/oqum/hazard/verbatim/output_scenario_sites.csv}{Download example})}
\label{output:sitemesh}
\end{table}

Fix a broken link [skip CI]

\begin{table}[htbp]
\centering
\begin{tabular}{ccc}

\hline
\rowcolor{lightgray}
\textbf{site\_id} & \textbf{lon} & \textbf{lat} \\
\hline
0 & -122.57000 & 38.11300 \\
1 & -122.11400 & 38.11300 \\
2 & -122.00000 & 37.91000 \\
3 & -122.00000 & 38.00000 \\
4 & -122.00000 & 38.11300 \\
5 & -122.00000 & 38.22500 \\
6 & -121.88600 & 38.11300 \\
\hline

\end{tabular} \caption{Example of a sites csv output file for a scenario (\href{https://raw.githubusercontent.com/gem/oq-engine/master/doc/manual/oqum/hazard/verbatim/output_scenario_sites.csv}{Download example})}
\label{output:sitemesh}
\end{table}


\documentclass[11pt]{article}

\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[english]{babel}
\usepackage{hyperref}

\begin{document}
\end{document}

Add title and initial author to paper

\documentclass[11pt]{article}

\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[english]{babel}
\usepackage{hyperref}

\title{Fast set implementation based on a hybrid hashtable and AVL}
\author{Julian Ganz}

\begin{document}

\maketitle{}

\end{document}


\documentclass[twocolumn]{article}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{url}
\usepackage{xeCJK}
\setmainfont{Helvetica}
\setCJKmainfont{YuMincho}
\title{report}
\author{himkt}
\date{\today}

\begin{document}
\maketitle
\section{introduction}
hello, world\cite{greenwade93}.

\bibliographystyle{plain}
\bibliography{reference}
\end{document}

Update the xetex margin config

\documentclass[twocolumn]{article}
\usepackage[top=10truemm,bottom=10truemm,left=10truemm,right=10truemm]{geometry}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{url}
\usepackage{xeCJK}
\setmainfont{Helvetica}
\setCJKmainfont{YuMincho}
\title{report}
\author{himkt}
\date{\today}

\begin{document}
\maketitle
\section{introduction}
hello, world\cite{greenwade93}.

\bibliographystyle{plain}
\bibliography{reference}
\end{document}


%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode

% Modify the following line to match your school
% Available options include `Harvard`, `Princeton`, and `NYU`.
\documentclass[School=Harvard]{Dissertate}

\begin{document}

% the front matter
\input{frontmatter/personalize}
\maketitle
\copyrightpage
\abstractpage
\tableofcontents
%\authorlist
\listoffigures
\dedicationpage
\acknowledgments

\onehalfspacing

% include each chapter...
\setcounter{chapter}{-1}  % start chapter numbering at 0
\include{chapters/introduction}
\include{chapters/chapter1}
\include{chapters/chapter2}
\include{chapters/chapter3}
\include{chapters/conclusion}
\begin{appendices}
    \include{chapters/appendixA}
\end{appendices}

\singlespacing

% the back matter
\clearpage
\bibliography{references}
\addcontentsline{toc}{chapter}{References}
\bibliographystyle{apalike2}

\include{endmatter/colophon}

\end{document}

Use double spacing throughout main text

%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode

% Modify the following line to match your school
% Available options include `Harvard`, `Princeton`, and `NYU`.
\documentclass[School=Harvard]{Dissertate}

\begin{document}

% the front matter
\input{frontmatter/personalize}
\maketitle
\copyrightpage
\abstractpage
\tableofcontents
%\authorlist
\listoffigures
\dedicationpage
\acknowledgments

\doublespacing

% include each chapter...
\setcounter{chapter}{-1}  % start chapter numbering at 0
\include{chapters/introduction}
\include{chapters/chapter1}
\include{chapters/chapter2}
\include{chapters/chapter3}
\include{chapters/conclusion}
\begin{appendices}
    \include{chapters/appendixA}
\end{appendices}

\singlespacing

% the back matter
\clearpage
\bibliography{references}
\addcontentsline{toc}{chapter}{References}
\bibliographystyle{apalike2}

\include{endmatter/colophon}

\end{document}


\documentclass[9pt,b5paper,tombo,openany]{jsbook}

\usepackage[dvipdfmx]{graphicx}
\usepackage{listings}
\usepackage{inconsolata}
\usepackage{url}

\lstset{basicstyle={\footnotesize\ttfamily}}

\setlength{\textwidth}{\fullwidth}
\setlength{\evensidemargin}{\oddsidemargin}

\begin{document}

\tableofcontents

\chapter{はじめに}

\setcounter{page}{1}

\chapter{あとがき}

\thispagestyle{empty}
\vspace*{\stretch{1}}
\begin{flushright}
\begin{minipage}{0.5\hsize}
\begin{description}
  \item{著者：}こじろー・まっきー
  \item{発行：}2016年8月14日
  \item{印刷：}POPLS (\verb|http://www.inv.co.jp/~popls/|)
\end{description}
\end{minipage}
\end{flushright}

\end{document}

Add chapter for openstack upgrade

\documentclass[9pt,b5paper,tombo,openany]{jsbook}

\usepackage[dvipdfmx]{graphicx}
\usepackage{listings}
\usepackage{inconsolata}
\usepackage{url}

\lstset{basicstyle={\footnotesize\ttfamily}}

\setlength{\textwidth}{\fullwidth}
\setlength{\evensidemargin}{\oddsidemargin}

\begin{document}

\tableofcontents

\chapter{はじめに}

\setcounter{page}{1}

\chapter{OpenStackアップグレード超入門}

\chapter{あとがき}

\thispagestyle{empty}
\vspace*{\stretch{1}}
\begin{flushright}
\begin{minipage}{0.5\hsize}
\begin{description}
  \item{著者：}こじろー・まっきー
  \item{発行：}2016年8月14日
  \item{印刷：}POPLS (\verb|http://www.inv.co.jp/~popls/|)
\end{description}
\end{minipage}
\end{flushright}

\end{document}


\chapter{Binary trees}
\label{chap-binary-trees}

Add specification of class NODE.

\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.


\begin{figure}[H]
	\centering
	\includegraphics[width=.6\textwidth]{img/ss1.png}
	\caption{Oscilloscope screenshot of the completed half-wave rectifier
		outlined in Figure~\ref{fig:schem1}.}
	\label{fig:ck1data}
\end{figure}

\begin{figure}[H]
	\centering
	\input{tbl/circuit2.tex}
	\caption{Brightness observations for the circuit shown in
		Figure~\ref{fig:schem2}.}
	\label{tab:ckt2data}
\end{figure}

\begin{figure}[H]
	\centering
	\input{tbl/circuit3.tex}
	\caption{Output measurements of the zener diode voltage
		regulator described in Figure~\ref{fig:schem3}.}
	\label{tab:ckt3data}
\end{figure}

\begin{figure}[H]
	\centering
	\input{tbl/circuit4.tex}
	\caption{Measured current with a variable resistance.  The experiment was
		performed with a source voltage of both~\SI{16}{\volt}
		and~\SI{32}{\volt}, as depicted in Figure~\ref{fig:schem4}}
	\label{tab:ckt4data}
\end{figure}

Insert gnuplot'd plots into document.

\begin{figure}[H]
	\centering
	\input{img/circuit3.tex}
\end{figure}

\begin{figure}[H]
	\centering
	\input{img/circuit4.tex}
\end{figure}

\begin{figure}[H]
	\centering
	\includegraphics[width=.6\textwidth]{img/ss1.png}
	\caption{Oscilloscope screenshot of the completed half-wave rectifier
		outlined in Figure~\ref{fig:schem1}.}
	\label{fig:ck1data}
\end{figure}

\begin{figure}[H]
	\centering
	\input{tbl/circuit2.tex}
	\caption{Brightness observations for the circuit shown in
		Figure~\ref{fig:schem2}.}
	\label{tab:ckt2data}
\end{figure}

\begin{figure}[H]
	\centering
	\input{tbl/circuit3.tex}
	\caption{Output measurements of the zener diode voltage
		regulator described in Figure~\ref{fig:schem3}.}
	\label{tab:ckt3data}
\end{figure}

\begin{figure}[H]
	\centering
	\input{tbl/circuit4.tex}
	\caption{Measured current with a variable resistance.  The experiment was
		performed with a source voltage of both~\SI{16}{\volt}
		and~\SI{32}{\volt}, as depicted in Figure~\ref{fig:schem4}}
	\label{tab:ckt4data}
\end{figure}


%&manual
% The line above is used to indicate to the compiler that the pre-compiled preamble be used if it is available (a manual.fmt file will be searched for)

\documentclass{article}

\usepackage{manual}     % Simply include the package created specifically for lab manuals

\renewcommand{\arraystretch}{1.5}

% Define the variables that are required for generating the title of the document
\course{Dummy Course}
\experimentnumber{0}
\title{Dummy Experiment}

\csname endofdump\endcsname     % This indicates the end of the "static" part of the preamble which is pre-compiled and placed in the manual.fmt file to speed up compilation.

\begin{document}

   \maketitle

   \input{theory}

   \newpage
   \maketitle           % Generate the title using the customized command defined in manual-defs.tex

   \setcounter{equation}{0}     % Restart equation numbering in the experiment section

   \input{experiment}

\end{document}

Update to use new maketitle macros

%&manual
% The line above is used to indicate to the compiler that the pre-compiled preamble be used if it is available (a manual.fmt file will be searched for)

\documentclass{article}

\usepackage{manual}     % Simply include the package created specifically for lab manuals

\renewcommand{\arraystretch}{1.5}

% Define the variables that are required for generating the title of the document
\coursetitle{Dummy Course}
\experimentnumber{0}
\experimenttitle{Dummy Experiment}

\csname endofdump\endcsname     % This indicates the end of the "static" part of the preamble which is pre-compiled and placed in the manual.fmt file to speed up compilation.

\begin{document}

   \maketitle

   \input{theory}

   \newpage
   \maketitle           % Generate the title using the customized command defined in manual-defs.tex

   \setcounter{equation}{0}     % Restart equation numbering in the experiment section

   \input{experiment}

\end{document}


% Encoding: UTF-8

@TechReport{,
  title = {Commercial Television and Voter Information},
  year =  {2016},
  url =   {http://d.repec.org/n?u=RePEc:cla:levrem:784828000000000363&r=ict}
}

Remove year from RepecNepImporterTest as this case does not seem to appear in the wild

% Encoding: UTF-8

@TechReport{,
  title = {Commercial Television and Voter Information},
  url =   {http://d.repec.org/n?u=RePEc:cla:levrem:784828000000000363&r=ict}
}


\documentclass[a4paper]{report}

%% Language and font encodings
\usepackage[english]{babel}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[useregional]{datetime2}
\usepackage[makeroom]{cancel}
\usepackage{titlesec}
\usepackage[hidelinks]{hyperref}

%% Put Chapter Number and name on one line
\titleformat{\chapter}[hang]
{\normalfont\huge\bfseries}{\chaptertitlename\ \thechapter:}{0.5em}{}

%% Sets page size and margins
\usepackage[a4paper,top=2cm,bottom=2cm,left=3cm,right=3cm,marginparwidth=1.75cm]{geometry}

\title{CommonUnits --- Draft}
\author{CommonUnits Contributors}

%% Custom Macros
\newcommand{\cu}{CommonUnits}

\newcommand{\fhref}[2]{
    \href{#2}{#1}\footnote{\url{#2}}
}

\begin{document}
\maketitle

%% Roman numbers for Special Chapters
\pagenumbering{roman}
\tableofcontents
\include{Preface}
\include{Contributors}
\pagenumbering{arabic}
\include{1.Challenges}
\end{document}

Update indentation to two spaces


@article{bank1985transient,
    title={Transient simulation of silicon devices and circuits},
    author={Bank, Randolph E and Coughran, William M and Fichtner, Wolfgang and
    Grosse, Eric H and Rose, Donald J and Smith, R Kent},
    journal={IEEE Transactions on Computer-Aided Design of Integrated Circuits
    and Systems},
    volume={4},
    number={4},
    pages={436--451},
    year={1985},
    publisher={IEEE}
},

@article{hosea1996analysis,
  title={Analysis and implementation of \textsc{tr-bdf}\oldstylenums{2}},
  author={Hosea, ME and Shampine, LF},
  journal={Applied Numerical Mathematics},
  volume={20},
  number={1},
  pages={21--37},
  year={1996},
  publisher={Elsevier}
}

@book{edward2010hughes,
    title={Hughes Electrical And Electronic Technology},
    author={Edward, H.},
    isbn={9788131733660},
    year={2010},
    edition={10},
    pages={1--198},
    publisher={Pearson Education}
}

Use small caps in title.

@article{bank1985transient,
    title={Transient simulation of silicon devices and circuits},
    author={Bank, Randolph E and Coughran, William M and Fichtner, Wolfgang and
    Grosse, Eric H and Rose, Donald J and Smith, R Kent},
    journal={IEEE Transactions on Computer-Aided Design of Integrated Circuits
    and Systems},
    volume={4},
    number={4},
    pages={436--451},
    year={1985},
    publisher={IEEE}
},

@article{hosea1996analysis,
  title={Analysis and implementation of \TRBDFII},
  author={Hosea, ME and Shampine, LF},
  journal={Applied Numerical Mathematics},
  volume={20},
  number={1},
  pages={21--37},
  year={1996},
  publisher={Elsevier}
}

@book{edward2010hughes,
    title={Hughes Electrical And Electronic Technology},
    author={Edward, H.},
    isbn={9788131733660},
    year={2010},
    edition={10},
    pages={1--198},
    publisher={Pearson Education}
}


\section{Our technique}

\begin{verbatim}
(defmacro with-test-and-test-not
    ((test-var test-not-var) &body body)
  `(cond ((and (null ,test-var)
               (null ,test-not-var))
	  ,@body)
	 ((null ,test-not-var)
	  (cond ((or (eq ,test-var #'eq)
                     (eq ,test-var 'eq))
		 ,@body)
		((or (eq ,test-var #'eql)
                     (eq ,test-var 'eql))
		 ,@body)
		(t
		 ,@body)))
	 ((null ,test-var)
	  (cond ((or (eq ,test-not-var #'eq)
                     (eq ,test-not-var 'eq))
		 ,@body)
		((or (eq ,test-not-var #'eql)
                     (eq ,test-not-var 'eql))
		 ,@body)
		(t
		 ,@body)))
	 (t
	  (error "Both test and test-not given."))))
\end{verbatim}

Remove macro handling TEST and TEST-NOT. We need a better test case.


\usepackage[empty]{fullpage}
\usepackage{titlesec}

% Font
\setmainfont{JetBrains Mono}

% Page Margin
\addtolength{\oddsidemargin}{-0.5in}
\addtolength{\evensidemargin}{-0.5in}
\addtolength{\textwidth}{1.0in}
\addtolength{\topmargin}{-0.5in}
\addtolength{\textheight}{1.0in}

% Center Title
\titleformat{\section}[block]{\Large\bfseries\filcenter}{}{}{}

Use compact option for titlesec.

\usepackage[empty]{fullpage}
\usepackage[compact]{titlesec}

% Font
\setmainfont{JetBrains Mono}

% Page Margin
\addtolength{\oddsidemargin}{-0.5in}
\addtolength{\evensidemargin}{-0.5in}
\addtolength{\textwidth}{1.0in}
\addtolength{\topmargin}{-0.5in}
\addtolength{\textheight}{1.0in}

% Center Title
\titleformat{\section}[block]{\Large\bfseries\filcenter}{}{}{}


\chapter{Translating AST to HIR}
\label{chap-translating-ast-to-hir}

The translation of an abstract syntax tree
\seechap{chap-abstract-syntax-tree} to medium-level intermediate
representation \seechap{chap-ir} is done by an algorithm that is
similar to that of CPS-conversion.%
\footnote{CPS means Continuation Passing Style.}

As with CPS-conversion, translation makes the control structure
explicit.  Another similarity is that translation is done from the end
of the program to the beginning.

Translation of a form is accomplished with respect to a
\emph{compilation context}.  This context contains a \emph{list of
  lexical variables} to which the values of the translated AST must be
assigned.  The length of the list corresponds to the number of values
required by the context.  The context also contains a \emph{list of
  successors} which represent MIR instructions to which transfer
control after evaluation of the current AST.

Introduce sections for ASDF system, package, and compilation context.

\chapter{Translating AST to HIR}
\label{chap-translating-ast-to-hir}

The translation of an abstract syntax tree
\seechap{chap-abstract-syntax-tree} to high-level intermediate
representation \seechap{chap-ir} is done by an algorithm that is
similar to that of CPS-conversion.%
\footnote{CPS means Continuation Passing Style.}

As with CPS-conversion, translation makes the control structure
explicit.  Another similarity is that translation is done from the end
of the program to the beginning.

\section{\asdf{} system name}

\section{Package}

\section{Compilation context}

Translation of a form is accomplished with respect to a
\emph{compilation context}.  This context contains a \emph{list of
  lexical variables} to which the values of the translated AST must be
assigned.  The length of the list corresponds to the number of values
required by the context.  The context also contains a \emph{list of
  successors} which represent MIR instructions to which transfer
control after evaluation of the current AST.


\newpage
\section{Use Case - Hugin Link (HL)}
\label{UseCase:HL}

\begin{description}
\item[Priority:] Must
\item[Deadline:] M15
\item[Responsible:]
\end{description}

\subsubsection*{Description of the Use Case}

Enter a textual description of the use case. Link to other use cases or functionalities if needed.

\subsubsection*{Must-Requirements List of the Use Case}

\begin{enumerate}
\item Short Description
\end{enumerate}

\subsubsection*{Should-Requirements List of the Use Case}

\begin{enumerate}
\item Short Description
\end{enumerate}

\subsubsection*{Could-Requirements List of the Use Case}

\begin{enumerate}
\item Short Description
\end{enumerate}

Update in the use case Hugin Link

%!TEX root = ../MainDoc.tex
\newpage
\section{Use Case - Hugin Link (HL)}
\label{UseCase:HL}

\begin{description}
\item[Priority:] Must
\item[Deadline:] M15
\item[Responsible:] A. Fern\'andez
\end{description}

\subsubsection*{Description of the Use Case}

This use case contains all the functionality needed to link the AMIDST toolbox with the HUGIN software. This linkage is addressed by converting Hugin models into AMIDST models, and vice versa. This feature is extremely useful as it allows expanding the testing possibilities of the AMIDST models within a well-stablished platform as Hugin. Also, the link to Hugin can be used for providing some extra functionality to AMIDST that will not be implemented. Finally, the linkage is useful for comparison purposes, i.e., a new inference algorithm implemented in AMIDST could be compared with some state-of-the-art algorithm included in Hugin.

\subsubsection*{Must-Requirements List of the Use Case}

\begin{enumerate}
\item Bayesian network converter from AMIDST to Hugin format.
\item Bayesian network converter from Hugin to AMIDST format.
\item Possibility of saving the converted Hugin network in a \texttt{.net} file.
\end{enumerate}

\subsubsection*{Should-Requirements List of the Use Case}

\begin{enumerate}
\item
\end{enumerate}

\subsubsection*{Could-Requirements List of the Use Case}

\begin{enumerate}
\item Converter from AMIDST to HUGIN  and vice versa of some functionality that is not relevant for model representation.
\end{enumerate}


\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.

\Defgeneric {left} {node}

Given a node, return the left child of that node.

\Defclass {simple-node}

This class is a subclass of the class \texttt{node}.  It does not add
any slots, and is only meant for client code to be able to distinguish
between a node with a parent and a node without one.

\Defclass {node-with-parent}

This class is a subclass of the class \texttt{node}.  It adds a slot
for storing a reference to the parent node in a binary tree.

Improve description of generic function LEFT.

\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.

\Defgeneric {left} {node}

Given a node, return the left child of that node.  The value returned
by this function may be either an instance of (a subclass of) the
class \texttt{node} or \texttt{nil} if the left child of \textit{node}
is the empty tree.

\Defclass {simple-node}

This class is a subclass of the class \texttt{node}.  It does not add
any slots, and is only meant for client code to be able to distinguish
between a node with a parent and a node without one.

\Defclass {node-with-parent}

This class is a subclass of the class \texttt{node}.  It adds a slot
for storing a reference to the parent node in a binary tree.


% Copyright 2018 Google LLC
%
% Use of this source code is governed by an MIT-style
% license that can be found in the LICENSE file or at
% https://opensource.org/licenses/MIT.

%%% script AUTHOR: Paul Crowley, Eric Biggers%%%
%%% script TITLE: {Adiantum}: length-preserving encryption for entry-level processors%%%

%!TeX spellcheck = en-US

\RequirePackage{etex}
\documentclass[journal=tosc,preprint,floatrow]{iacrtrans}
\usepackage{etoolbox}
\newtoggle{iacr}
\toggletrue{iacr}

\author{Paul~Crowley \and Eric~Biggers}
\institute{Google LLC \\ \email[paulcrowley@google.com,ebiggers@google.com]{{paulcrowley,ebiggers}@google.com}}

\input{shared-part.tex}

Switch IACR version to final

% Copyright 2018 Google LLC
%
% Use of this source code is governed by an MIT-style
% license that can be found in the LICENSE file or at
% https://opensource.org/licenses/MIT.

%%% script AUTHOR: Paul Crowley, Eric Biggers%%%
%%% script TITLE: {Adiantum}: length-preserving encryption for entry-level processors%%%

%!TeX spellcheck = en-US

\RequirePackage{etex}
\documentclass[journal=tosc,final,floatrow]{iacrtrans}
\usepackage{etoolbox}
\newtoggle{iacr}
\toggletrue{iacr}

\author{Paul~Crowley \and Eric~Biggers}
\institute{Google LLC \\ \email[paulcrowley@google.com,ebiggers@google.com]{{paulcrowley,ebiggers}@google.com}}

\input{shared-part.tex}


\chapter{Introduction}
\pagenumbering{arabic}%

\sysname{} is a library that supplies a collection of different kinds
of \emph{trees}.

Expand on the purpose of Clump.

\chapter{Introduction}
\pagenumbering{arabic}%

\section{Purpose}

\sysname{} is a library that supplies a collection of different kinds
of \emph{trees}.

\sysname{} differs from other libraries with trees, such as
\texttt{cl-containers} in that it has a \emph{stratified design}.
This design allows client code to intervene at all levels, from the
level of near-concrete representation of the trees, up to the most
abstract interface where the trees are used as dictionaries,
sequences, or some other abstract data types.

Also, the stratified design makes it possible for client code to use
the lower levels of abstraction of \sysname{} in order to create
completely new abstractions, not foreseen by this library.

The price to pay for this stratified design is, of course, that lower
abstraction levels are exposed to client code, and are therefore
limited in the way that they can evolve.  As a consequence, we have
tried to create these lower abstraction levels in a way that they are
unlikely to require radical modifications.


\section{Benefits of our method}

As already mentioned in \refSec{sec-our-technique}, the main advantage
of our technique is that it allows for a \emph{modular} structure of
the \texttt{loop} implementation.

This modularity also makes it very simple for additional clause types
to be added by the \commonlisp{} implementation, such as the extension
for iterating over the user-extensible sequences described by Rhodes
in his paper on user-extensible sequences
\cite{Rhodes:2007:USC:1622123.1622138}.  This extension defines the
new \texttt{loop} keywords \texttt{element} and \texttt{elements} for
this purpose.

Add label to section so that it can be referred to.

\section{Benefits of our method}
\label{sec-benefits}

As already mentioned in \refSec{sec-our-technique}, the main advantage
of our technique is that it allows for a \emph{modular} structure of
the \texttt{loop} implementation.

This modularity also makes it very simple for additional clause types
to be added by the \commonlisp{} implementation, such as the extension
for iterating over the user-extensible sequences described by Rhodes
in his paper on user-extensible sequences
\cite{Rhodes:2007:USC:1622123.1622138}.  This extension defines the
new \texttt{loop} keywords \texttt{element} and \texttt{elements} for
this purpose.


\documentclass[11pt]{article}

\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[english]{babel}
\usepackage{hyperref}

\usepackage{amsfonts}
\usepackage{graphicx}

\DeclareGraphicsRule{.1}{mps}{*}{}

\title{Fast set implementation based on a hybrid hashtable and AVL}
\author{
    Julian Ganz\\
}

\begin{document}

\maketitle{}

\tableofcontents{}

\input{intro}
\input{overview}
\input{data-layout}
\input{operations}
\input{AVL-ops}
\input{bloom-filter}
\input{parameters}
\input{misc}

\end{document}

Add cleared pages between sections

\documentclass[11pt]{article}

\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[english]{babel}
\usepackage{hyperref}

\usepackage{amsfonts}
\usepackage{graphicx}

\DeclareGraphicsRule{.1}{mps}{*}{}

\title{Fast set implementation based on a hybrid hashtable and AVL}
\author{
    Julian Ganz\\
}

\begin{document}

\maketitle{}

\tableofcontents{}

\input{intro}
\clearpage

\input{overview}
\clearpage

\input{data-layout}
\clearpage

\input{operations}
\clearpage

\input{AVL-ops}
\clearpage

\input{bloom-filter}
\clearpage

\input{parameters}
\clearpage

\input{misc}

\end{document}


\documentclass[]{article}
\usepackage[utf8]{inputenc}
\usepackage{hyperref}
\usepackage{listings}
\usepackage{epigraph}
\usepackage{fontspec}
\usepackage[toc,title]{appendix}
\usepackage{float}

% Itemize with custom spacing
\newenvironment{myitemize}
{ \begin{itemize}
    \setlength{\itemsep}{0pt}
    \setlength{\parskip}{0pt}
    \setlength{\parsep}{0pt}     }
{ \end{itemize}                  }

% color setting for inline code embedding

%opening
\title{Tsukiji}
\author{Michael The \and Hugo Reinbergen}

\begin{document}

\input{frontpage}

\include{foreword}
\include{summary}

\tableofcontents
\listoffigures

\include{introduction}
\include{problem_definition}
\include{relatedwork}
\include{requirements}
\include{design}
\include{implementation}
\include{evaluation}
\include{conclusion}
\include{recommendation}

\bibliographystyle{unsrt} % sort references by appearance
\bibliography{refs}

\begin{appendices}
\include{trade_protocol}
\include{SIG}
\include{project_description}
\include{infosheet}
\end{appendices}

\end{document}

Add a myenumerate, similar to myitemize. A tighter list.

\documentclass[]{article}
\usepackage[utf8]{inputenc}
\usepackage{hyperref}
\usepackage{listings}
\usepackage{epigraph}
\usepackage{fontspec}
\usepackage[toc,title]{appendix}
\usepackage{float}

% Itemize with custom spacing
\newenvironment{myitemize}
{ \begin{itemize}
    \setlength{\itemsep}{0pt}
    \setlength{\parskip}{0pt}
    \setlength{\parsep}{0pt}     }
{ \end{itemize}                  }

\newenvironment{myenumerate}
{ \begin{enumerate}
    \setlength{\itemsep}{0pt}
    \setlength{\parskip}{0pt}
    \setlength{\parsep}{0pt}     }
{ \end{enumerate}                  }

% color setting for inline code embedding

%opening
\title{Tsukiji}
\author{Michael The \and Hugo Reinbergen}

\begin{document}

\input{frontpage}

\include{foreword}
\include{summary}

\tableofcontents
\listoffigures

\include{introduction}
\include{problem_definition}
\include{relatedwork}
\include{requirements}
\include{design}
\include{implementation}
\include{evaluation}
\include{conclusion}
\include{recommendation}

\bibliographystyle{unsrt} % sort references by appearance
\bibliography{refs}

\begin{appendices}
\include{trade_protocol}
\include{SIG}
\include{project_description}
\include{infosheet}
\end{appendices}

\end{document}


% State of the Art Chapter

Introduce the SOTA here.

Update State of the Art section

% State of the Art Chapter

\section{Linux Kernel}

Blah.

\subsection{Linux Kernel Modules}

Blah.

\section{Software Composition Analysis}

SCA be here.

\subsection{Static Binary Analysis}

SBA be here.


\nomenclature{UART}{Universal Asynchronous Receiver Transmitter}
%\nomenclature{}{}
%\nomenclature{}{}
%\nomenclature{}{}
%\nomenclature{}{}

Add information for package nomenclature

%Bei der Verwendung des Pakets nomenclature muss der Befehl makeindex ausgeführt werden, um das Abkürzungsverzeichnis zu aktualisieren.
%When using the package nomenclature, you have to execute the command makeindex to update the list of abbreviations.
%https://tex.stackexchange.com/questions/27824/using-package-nomencl
%latex <filename>.tex
%makeindex <filename>.nlo -s nomencl.ist -o <filename>.nls
%latex <filename>.tex

\nomenclature{UART}{Universal Asynchronous Receiver Transmitter}
%\nomenclature{}{}
%\nomenclature{}{}
%\nomenclature{}{}
%\nomenclature{}{}


This paper introduces "pat", a C++ performance analysis toolkit on Linux.
"pat" combines unit tests and perf_event to give programmers the power of white-box performance analysis.

"pat" behaves like a normal unit test library.
It provides macros and assertions to ensure correctness and to evaluate performance of a region of code.
We want to point out that, under the high reliability, the evaluation is precise.
With perf_event, "pat" can analyze running time of a region without interference to scheduler.
Moreover, perf_event also gives "pat" precise cycle counts that is useful for tools who are sensitive to variance of timing, such as compilers.
With pure and precise timing information, "pat" helps to measure the bottleneck of regions of a program.

We develop "pat" under the new BSD license, and it's also the unit-test library of the "bold" project.

Change project name from pat to SkyPat

This paper introduces SkyPat, a C++ performance analysis toolkit on Linux.
SkyPat combines unit tests and perf_event to give programmers the power of white-box performance analysis.

SkyPat behaves like a normal unit test library.
It provides macros and assertions to ensure correctness and to evaluate performance of a region of code.
We want to point out that, under the high reliability, the evaluation is precise.
With perf_event, SkyPat can analyze running time of a region without interference to scheduler.
Moreover, perf_event also gives SkyPat precise cycle counts that is useful for tools who are sensitive to variance of timing, such as compilers.
With pure and precise timing information, SkyPat helps to measure the bottleneck of regions of a program.

We develop SkyPat under the new BSD license, and it's also the unit-test library of the "bold" project.


\documentclass[11pt]{article}

\usepackage[margin=0.75in]{geometry}

\title{The title of your project proposal}
\author{
  Kong, Victor\\
  \texttt{VictorKong94}
  \and
  Li, Karen\\
  \texttt{karenceli}
  \and
  Liu, Anna\\
  \texttt{liuanna}
  \and
  Qin, Eric\\
  \texttt{j170382276}
  \and
  Xia, Yunfei\\
  \texttt{yfxia}
}

\bibliographystyle{siam}

\begin{document}
\maketitle

\abstract{You should have a short abstract.}

\section{Introduction}

Identify a published fMRI paper and the accompanying data
\cite{lindquist2008statistical}.  You should explain the basic idea of the
paper in a paragraph.  You should also perform basic sanity check on the data
(e.g., can you downloaded, can you load the files, confirm that you have the
correct number of subjects).

Briefly explain what reproducibility means and in what sense you will
try to reproduce this study.

\section{Data}

\section{Methods}
\section{Results}
\section{Discussion}

\bibliography{project}

\end{document}

Fix Karen's and Eric's names

\documentclass[11pt]{article}

\usepackage[margin=0.75in]{geometry}

\title{The title of your project proposal}
\author{
  Kong, Victor\\
  \texttt{VictorKong94}
  \and
  Li, Ce\\
  \texttt{karenceli}
  \and
  Liu, Anna\\
  \texttt{liuanna}
  \and
  Qin, Weidong\\
  \texttt{j170382276}
  \and
  Xia, Yunfei\\
  \texttt{yfxia}
}

\bibliographystyle{siam}

\begin{document}
\maketitle

\abstract{You should have a short abstract.}

\section{Introduction}

Identify a published fMRI paper and the accompanying data
\cite{lindquist2008statistical}.  You should explain the basic idea of the
paper in a paragraph.  You should also perform basic sanity check on the data
(e.g., can you downloaded, can you load the files, confirm that you have the
correct number of subjects).

Briefly explain what reproducibility means and in what sense you will
try to reproduce this study.

\section{Data}

\section{Methods}
\section{Results}
\section{Discussion}

\bibliography{project}

\end{document}


\documentclass{article}
\usepackage[utf8]{inputenc}

\title{<%= project_name %>}
\author{<%= user.first_name %> <%= user.last_name %>}
\date{<%= month %> <%= year %>}

\usepackage{natbib}
\usepackage{graphicx}

\begin{document}

\maketitle

\section{Introduction}
There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.

\begin{figure}[h!]
\centering
\includegraphics[scale=1.7]{universe.jpg}
\caption{The Universe}
\label{fig:univerise}
\end{figure}

\section{Conclusion}
``I always thought something was fundamentally wrong with the universe'' \citep{adams1995hitchhiker}

\bibliographystyle{plain}
\bibliography{references}
\end{document}

Fix typo and file extension in example tex template

\documentclass{article}
\usepackage[utf8]{inputenc}

\title{<%= project_name %>}
\author{<%= user.first_name %> <%= user.last_name %>}
\date{<%= month %> <%= year %>}

\usepackage{natbib}
\usepackage{graphicx}

\begin{document}

\maketitle

\section{Introduction}
There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.

\begin{figure}[h!]
\centering
\includegraphics[scale=1.7]{universe}
\caption{The Universe}
\label{fig:universe}
\end{figure}

\section{Conclusion}
``I always thought something was fundamentally wrong with the universe'' \citep{adams1995hitchhiker}

\bibliographystyle{plain}
\bibliography{references}
\end{document}


% For math stuff like \boldsymbol
\usepackage{amsmath}

% Used for printing Matlab m-files with syntax highlighting
% \usepackage[framed,numbered,autolinebreaks,useliterate]{mcode}

\newcommand{\bs}[1]{%
    \boldsymbol{#1}
}

% \usepackage{minted}
% \renewcommand{\theFancyVerbLine}{
%    \sffamily\textcolor[rgb]{0.5,0.5,0.5}{\scriptsize\arabic{FancyVerbLine}}}

% TODO Items
\newcommand\TODO[1]{[TODO: #1]}

Include image and citation packages

% Postscript figures
\usepackage{psfig}

% Float an image in the correct location /begin{figure}[H]
\usepackage{float}

% Citation package
\usepackage{cite}

% For math stuff like \boldsymbol
\usepackage{amsmath}

% Used for printing Matlab m-files with syntax highlighting
% \usepackage[framed,numbered,autolinebreaks,useliterate]{mcode}

\newcommand{\bs}[1]{%
    \boldsymbol{#1}
}

% \usepackage{minted}
% \renewcommand{\theFancyVerbLine}{
%    \sffamily\textcolor[rgb]{0.5,0.5,0.5}{\scriptsize\arabic{FancyVerbLine}}}

% TODO Items
\newcommand\TODO[1]{[TODO: #1]}


\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.

Add description of class SIMPLE-NODE.

\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.

\Defclass {simple-node}

This class is a subclass of the class \texttt{node}.  It does not add
any slots, and is only meant for client code to be able to distinguish
between a node with a parent and a node without one.


\documentclass[a4paper,ngerman]{article}

% Make it possible to enable or disable TOC
\newif\ifShowTOC

Use etoolbox, mainly for checking for undefined macros

\documentclass[a4paper,ngerman]{article}

% Make it possible to enable or disable TOC
\newif\ifShowTOC

% Utility stuff, used, for example, in x3-mmd-compat
% That is why we need to include it here, and not in -begin
\usepackage{etoolbox}


%
% Copyright 2014, General Dynamics C4 Systems
%
% This software may be distributed and modified according to the terms of
% the GNU General Public License version 2. Note that NO WARRANTY is provided.
% See "LICENSE_GPLv2.txt" for details.
%
% @TAG(GD_GPL)
%

\apidoc
{sel4_nbwait}
{NBWait}
{Perform a non-blocking wait on an endpoint or notification object}
{static inline seL4\_MessageInfo seL4\_NBWait}
{
\param{seL4\_CPtr}{src}{\invokedcapdesc}
\param{seL4\_Word*}{sender}{\senderdesc}
}
{\messageinforetdesc}
{See \autoref{sec:sys_nbwait}}

Fix documented return type of NBWait.

%
% Copyright 2014, General Dynamics C4 Systems
%
% This software may be distributed and modified according to the terms of
% the GNU General Public License version 2. Note that NO WARRANTY is provided.
% See "LICENSE_GPLv2.txt" for details.
%
% @TAG(GD_GPL)
%

\apidoc
{sel4_nbwait}
{NBWait}
{Perform a non-blocking wait on an endpoint or notification object}
{static inline seL4\_MessageInfo\_t seL4\_NBWait}
{
\param{seL4\_CPtr}{src}{\invokedcapdesc}
\param{seL4\_Word*}{sender}{\senderdesc}
}
{\messageinforetdesc}
{See \autoref{sec:sys_nbwait}}


\section{Data layout}

Add note about disjunctive buckets

\section{Data layout}

    As already implicated, the data is divided into several buckets --like in a
    regular hashtable.

    As to be expected, any element which may be part of the set is mapped onto
    a bucket injectively.
    The sets made up from the elements which would be mapped to a specific
    bucket $e(b)$ are disjunctive to the elements which would be mapped to
    another bucket of the same table:

    \begin{equation}
        e(b_1) \cap e(b_2) = \emptyset
    \end{equation}

    Note that $e(b)$ is the set of \em all\em{} elements which \em may\em{}
    potentially be part of the bucket, rather than elements which \em are\em{}
    elements of the bucket.


\chapter{Translating AST to MIR}
\label{chap-translating-ast-to-mir}

The translation of an abstract syntax tree
\seechap{chap-abstract-syntax-tree} to medium-level intermediate
representation \seechap{chap-ir} is done by an algorithm that is
similar to that of CPS-conversion.%
\footnote{CPS means Continuation Passing Style.}

As with CPS-conversion, translation makes the control structure
explicit.  Another similarity is that translation is done from the end
of the program to the beginning.

Translation of a form is accomplished with respect to a
\emph{compilation context}.  This context contains a \emph{list of
  lexical variables} to which the values of the translated AST must be
assigned.  The length of the list corresponds to the number of values
required by the context.  The context also contains a \emph{list of
  successors} which represent MIR instructions to which transfer
control after evaluation of the current AST.

Replace MIR by HIR which is what the AST translates to.

\chapter{Translating AST to HIR}
\label{chap-translating-ast-to-hir}

The translation of an abstract syntax tree
\seechap{chap-abstract-syntax-tree} to medium-level intermediate
representation \seechap{chap-ir} is done by an algorithm that is
similar to that of CPS-conversion.%
\footnote{CPS means Continuation Passing Style.}

As with CPS-conversion, translation makes the control structure
explicit.  Another similarity is that translation is done from the end
of the program to the beginning.

Translation of a form is accomplished with respect to a
\emph{compilation context}.  This context contains a \emph{list of
  lexical variables} to which the values of the translated AST must be
assigned.  The length of the list corresponds to the number of values
required by the context.  The context also contains a \emph{list of
  successors} which represent MIR instructions to which transfer
control after evaluation of the current AST.


\section{Profiling- und Performancetests}

Add Prover subsection to Profiling section.

\section{Profiling- und Performancetests}
Um einen Überblick über den Zeitaufwand der einzelnen Programmkomponenten zu gewinnen sowie zeitliche HotSpots zu identifizieren, wurden Profiling Tests mittels VisualVM vorgenommen. Hierbei wurden einzelne meist komplexere Testprogramme aus der GUI gestartet und untersucht um einen Eindruck des Programms unter möglichst realen Bedingungen zu erlangen.

\subsection{Parser}

\subsection{Interpreter}

\subsection{Prover}
Das Überprüfen eines Testprogramms dauerte im Schnitt etwa 2 Sekunden. Am Beispiel der Testprogramme test\_fibonacci.ww und bubblesort2.ww lag die Beweiszeit bei 1865 ms bzw. 1895 ms. Da vor dem Beweisen ein Parsen des Codes und Typsystemüberprüfungen nötig sind fallen etwa 100 bis 200 ms auf diese Aufgaben zurück. Die Transformation des Codes in das wp-Kalkül benötigte für bubblesort2.ww 142 ms und für test\_fibonacci.ww 36 ms. Das Umwandeln einer einzelnen Annotation ins SMTLIB Format betrug bei beiden Tests wenige Millisekunden (im Schnitt etwa 4 ms). Da jedoch die Annotationen einzeln umgewandelt und überprüft werden liegt die Gesamtzeit der Umwandlungen ins SMTLIB Format deutlich höher. Das Testprogramm bubblesort2.ww enthielt 13 und test\_fibonacci.ww 11 zu überprüfende Annotationen. Somit liegt der Zeitbedarf für das Umwandeln aller Annotation bei etwa 50 ms. Ebenso wird jede Annotation anschließend mittels externem Beweiser überprüft. Einzelne Annotationen zu beweisen dauerte etwa 15 bis 17 ms und demnach lag der Gesamtzeitaufwand des Beweisers für das gesamte Programm bei 220 ms für bubblesort2.ww und bei 170 ms für test\_fibonacci.ww. Nach Überprüfung weiterer Testprogramme ergibt sich somit ein ungefährer Überblick über den anteiligen Zeitaufwand der Prover Komponenten:
\begin{table}[h]
\centering
\caption{Ungefährer Zeitaufwand der Proverkomponenten}
\label{zeitaufwandprover}
\begin{tabular}{|l|l|}
\hline
\textbf{Komponente} & \textbf{Zeitaufwand} \\
\hline
Parser + Typsystem & 10\% \\
\hline
wp-Kalkül & 8\% \\
\hline
SMTLIB Erstellung & 4\% \\
\hline
Z3 & 15\% \\
\hline
\end{tabular}
\end{table}


\usepackage{xcolor}
\usepackage{graphicx}
\usepackage{polytexnic_commands}
\usepackage{pygments}
\usepackage{amsmath}
\usepackage{fancyvrb} % to get 'Verbatim' environment
\usepackage{relsize}
\usepackage[hyperfootnotes=false]{hyperref}
\hypersetup{hyperfootnotes=false}

\definecolor{darkblue}{rgb}{0,0.18,0.45}
\definecolor{darkgreen}{rgb}{0,0.39,0}

\hypersetup{colorlinks,linkcolor=darkblue,urlcolor=blue}

\DefineVerbatimEnvironment%
  {code}{Verbatim}{fontsize=\relsize{-0.5},fontseries=b}
% The metacode environment exists solely to allow meta-discussion of the code
% environment, as in
%   %= lang:latex
%   \begin{metacode}
%   %= lang:ruby
%   \begin{code}
%   def foo
%     "bar"
%   end
%   \end{code}
%   \end{metacode}
\DefineVerbatimEnvironment%
  {metacode}{Verbatim}{fontsize=\relsize{-0.5},fontseries=b}

Remove codelisting definition from template

\usepackage{xcolor}
\usepackage{graphicx}
\usepackage{polytexnic_commands}
\usepackage{pygments}
\usepackage{amsmath}
\usepackage{fancyvrb} % to get 'Verbatim' environment
\usepackage{relsize}
\usepackage[hyperfootnotes=false]{hyperref}
\hypersetup{hyperfootnotes=false}

% Links
\definecolor{darkblue}{rgb}{0,0.18,0.45}
\definecolor{darkgreen}{rgb}{0,0.39,0}
\hypersetup{colorlinks,linkcolor=darkblue,urlcolor=blue}

% Code environments
\DefineVerbatimEnvironment%
  {code}{Verbatim}{fontsize=\relsize{-0.5},fontseries=b}
% The metacode environment exists solely to allow meta-discussion of the code
% environment, as in
%   %= lang:latex
%   \begin{metacode}
%   %= lang:ruby
%   \begin{code}
%   def foo
%     "bar"
%   end
%   \end{code}
%   \end{metacode}
\DefineVerbatimEnvironment%
  {metacode}{Verbatim}{fontsize=\relsize{-0.5},fontseries=b}


\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.

\Defclass {simple-node}

This class is a subclass of the class \texttt{node}.  It does not add
any slots, and is only meant for client code to be able to distinguish
between a node with a parent and a node without one.

\Defclass {node-with-parent}

This class is a subclass of the class \texttt{node}.  It adds a slot
for storing a reference to the parent node in a binary tree.

Add description of generic function LEFT.

\chapter{Binary trees}
\label{chap-binary-trees}

\Defclass {node}

This class is the base class for all node types in binary trees.

\Defgeneric {left} {node}

Given a node, return the left child of that node.

\Defclass {simple-node}

This class is a subclass of the class \texttt{node}.  It does not add
any slots, and is only meant for client code to be able to distinguish
between a node with a parent and a node without one.

\Defclass {node-with-parent}

This class is a subclass of the class \texttt{node}.  It adds a slot
for storing a reference to the parent node in a binary tree.


% ------------------------------------------
%  IEEE ARTICLE TEMPLATE
% ------------------------------------------
% Author(s):
% Institution(s):
% ------------------------------------------
\documentclass[journal,twocolumn,letterpaper,10pt]{ieee-sty/IEEEtran}
\usepackage[acronym]{glossaries}

% Generates the acronyms list
\makeglossaries

% Acronyms list
\input{acronyms/acronyms.tex}

% ------------------------------------------
%  MAIN DOCUMENT
% ------------------------------------------
\begin{document}

% Variables file
\input{variables.tex}

% Article title
\title{\Title}

% Author(s) Name
\author{\Authors\\
        \Institutions}

\maketitle

% Abstract
\input{abstract/abstract.tex}

% Keywords
\input{keywords/keywords.tex}

% Sections
\input{sections/main.tex}

% Print the acronyms list
\printglossaries

\if\hasBibliography 1
% Bibliography
\bibliographystyle{IEEEtran}
% Bibliography file
\bibliography{IEEEabrv,bibliography/article}
\fi

\end{document}

Add new package to fix the figure captions.

% ------------------------------------------
%  IEEE ARTICLE TEMPLATE
% ------------------------------------------
% Author(s):
% Institution(s):
% ------------------------------------------
\documentclass[journal,twocolumn,letterpaper,10pt]{ieee-sty/IEEEtran}
\usepackage[acronym]{glossaries}
\usepackage{graphicx, hyperref, url}
\usepackage{caption}

% Generates the acronyms list
\makeglossaries

% Acronyms list
\input{acronyms/acronyms.tex}

% ------------------------------------------
%  MAIN DOCUMENT
% ------------------------------------------
\begin{document}

% Variables file
\input{variables.tex}

% Article title
\title{\Title}

% Author(s) Name
\author{\Authors\\
        \Institutions}

\maketitle

% Abstract
\input{abstract/abstract.tex}

% Keywords
\input{keywords/keywords.tex}

% Sections
\input{sections/main.tex}

% Print the acronyms list
\printglossaries

\if\hasBibliography 1
% Bibliography
\bibliographystyle{IEEEtran}
% Bibliography file
\bibliography{IEEEabrv,bibliography/article}
\fi

\end{document}


% This file was derived from a template created by Joshua Ryan Smith
% (joshua.r.smith@gmail.com). The template can be found in the git repo at:
% http://github.com/jrsmith3/latex_template

\documentclass[letterpaper,12pt]{article}

% Document graphics and formatting
% ================================
\usepackage{graphicx}
\graphicspath{ {dat/}{build/} }
% \usepackage{showkeys}
% \usepackage{endfloat}
% \usepackage{url}
\usepackage[version=3]{mhchem}

% Document metadata
% =================
\newcommand{\Title}{}
\newcommand{\AuthorName}{}
\newcommand{\AuthorEmail}{}

\usepackage[pdftex,colorlinks=true,hidelinks]{hyperref}
\hypersetup{
pdftitle={\Title},
pdfauthor={\AuthorName (\AuthorEmail)},
pdfsubject={},
pdfkeywords={},
pdfcreator={pdfTeX}
}

% Label index
% ===========
% eq:
% --
%
% fig
% ---
%
% sec
% ---
%
% tab
% ---

\title{\Title}
\author{\AuthorName}

\begin{document}

\maketitle

\begin{abstract}

\end{abstract}

\section{}

% \bibliographystyle{nar}
% \bibliography{}
\end{document}

Include author metadata in LaTeX document

% This file was derived from a template created by Joshua Ryan Smith
% (joshua.r.smith@gmail.com). The template can be found in the git repo at:
% http://github.com/jrsmith3/latex_template

\documentclass[letterpaper,12pt]{article}

% Document graphics and formatting
% ================================
\usepackage{graphicx}
\graphicspath{ {dat/}{build/} }
% \usepackage{showkeys}
% \usepackage{endfloat}
% \usepackage{url}
\usepackage[version=3]{mhchem}

% Document metadata
% =================
\newcommand{\Title}{ {{cookiecutter.project_name}} }
\newcommand{\AuthorName}{ {{cookiecutter.full_name}} }
\newcommand{\AuthorEmail}{ {{cookiecutter.email}} }

\usepackage[pdftex,colorlinks=true,hidelinks]{hyperref}
\hypersetup{
pdftitle={\Title},
pdfauthor={\AuthorName (\AuthorEmail)},
pdfsubject={},
pdfkeywords={},
pdfcreator={pdfTeX}
}

% Label index
% ===========
% eq:
% --
%
% fig
% ---
%
% sec
% ---
%
% tab
% ---

\title{\Title}
\author{\AuthorName}

\begin{document}

\maketitle

\begin{abstract}

\end{abstract}

\section{}

% \bibliographystyle{nar}
% \bibliography{}
\end{document}


%
% Copyright (c) 2006-2010 Citrix Systems, Inc.
%
% All rights reserved.
%
% Authors: Ewan Mellor, Richard Sharp, Dave Scott
%

%% Document title
\newcommand{\doctitle}{Citrix XenServer Management API}

\newcommand{\coversheetlogo}{citrix_logo_black.eps}

%% Document date
\newcommand{\datestring}{21st May 2010}

\newcommand{\releasestatement}{}

%% Document revision
\newcommand{\revstring}{API Revision 1.7}

%% Document authors
\newcommand{\docauthors}{
}
\newcommand{\legalnotice}{Copyright \copyright{} 2006-2010 Citrix Systems, Inc. All Rights Reserved.}

Update version number in API documentation PDF

%
% Copyright (c) 2006-2010 Citrix Systems, Inc.
%
% All rights reserved.
%
% Authors: Ewan Mellor, Richard Sharp, Dave Scott
%

%% Document title
\newcommand{\doctitle}{Citrix XenServer Management API}

\newcommand{\coversheetlogo}{citrix_logo_black.eps}

%% Document date
\newcommand{\datestring}{\today}

\newcommand{\releasestatement}{}

%% Document revision
\newcommand{\revstring}{API Revision 1.8}

%% Document authors
\newcommand{\docauthors}{
}
\newcommand{\legalnotice}{Copyright \copyright{} 2006-2010 Citrix Systems, Inc. All Rights Reserved.}


%
% Copyright (c) 2006-2010 Citrix Systems, Inc.
%
% All rights reserved.
%
% Authors: Ewan Mellor, Richard Sharp, Dave Scott
%

%% Document title
\newcommand{\doctitle}{Citrix XenServer Management API}

\newcommand{\coversheetlogo}{citrix_logo_black.eps}

%% Document date
\newcommand{\datestring}{\today}

\newcommand{\releasestatement}{}

%% Document revision
\newcommand{\revstring}{API Revision 1.8}

%% Document authors
\newcommand{\docauthors}{
}
\newcommand{\legalnotice}{Copyright \copyright{} 2006-2010 Citrix Systems, Inc. All Rights Reserved.}

Update API version number in docs

%
% Copyright (c) 2006-2010 Citrix Systems, Inc.
%
% All rights reserved.
%
% Authors: Ewan Mellor, Richard Sharp, Dave Scott
%

%% Document title
\newcommand{\doctitle}{Citrix XenServer Management API}

\newcommand{\coversheetlogo}{citrix_logo_black.eps}

%% Document date
\newcommand{\datestring}{\today}

\newcommand{\releasestatement}{}

%% Document revision
\newcommand{\revstring}{API Revision 1.9}

%% Document authors
\newcommand{\docauthors}{
}
\newcommand{\legalnotice}{Copyright \copyright{} 2006-2011 Citrix Systems, Inc. All Rights Reserved.}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%     DANKSAGUNG
%%%     2007/10/17
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\chapter*{Danksagung}

.....

\vspace{1.5cm}

\begin{center}
\raggedleft{\campusAuthor}
\end{center}

\vspace{1.5cm}

\campusCity, im April 2008

Use current date for acknowledgement.


@article{Anscombe1948,
   author = {Anscombe, Francis J},
   title = {The transformation of Poisson, binomial and negative-binomial data},
   journal = {Biometrika},
   volume = {35},
   number = {3/4},
   pages = {246-254},
   ISSN = {0006-3444},
   year = {1948},
   type = {Journal Article}
}

Remove 'Journal Article' text from reference -- it's obviously a journal article.

@article{Anscombe1948,
   author = {Anscombe, Francis J},
   title = {The transformation of Poisson, binomial and negative-binomial data},
   journal = {Biometrika},
   volume = {35},
   number = {3/4},
   pages = {246-254},
   ISSN = {0006-3444},
   year = {1948}
}


\chapter{Interactive Workload}\label{section:workload}

\section{Query Specifications}

\subsection{Complex Reads Query Descriptions}

\input{query-cards/interactive01}
\input{query-cards/interactive02}
\input{query-cards/interactive03}
\input{query-cards/interactive04}
\input{query-cards/interactive05}
\input{query-cards/interactive06}
\input{query-cards/interactive07}
\input{query-cards/interactive08}
\input{query-cards/interactive09}
\input{query-cards/interactive10}
\input{query-cards/interactive11}
\input{query-cards/interactive12}
\input{query-cards/interactive13}
\input{query-cards/interactive14}

\subsection{Short Reads Query Descriptions}

\input{interactive-short-reads}

\subsection{Update Query Descriptions}

\input{interactive-update}

\section{Substitution Parameters}

\todo{These could also be reworked as query cards.}
\input{interactive-parameters}

\section{Load Definition}

\todo{Maybe introduce YAML specification for these as well?}
\input{interactive-workload}

Move TODOs to their place

\chapter{Interactive Workload}\label{section:workload}

\section{Query Specifications}

\subsection{Complex Reads Query Descriptions}

\input{query-cards/interactive01}
\input{query-cards/interactive02}
\input{query-cards/interactive03}
\input{query-cards/interactive04}
\input{query-cards/interactive05}
\input{query-cards/interactive06}
\input{query-cards/interactive07}
\input{query-cards/interactive08}
\input{query-cards/interactive09}
\input{query-cards/interactive10}
\input{query-cards/interactive11}
\input{query-cards/interactive12}
\input{query-cards/interactive13}
\input{query-cards/interactive14}

\subsection{Short Reads Query Descriptions}

\todo{These could also be reworked as query cards.}
\input{interactive-short-reads}

\subsection{Update Query Descriptions}

\todo{Maybe introduce YAML specification for these as well?}
\input{interactive-update}

\section{Substitution Parameters}

\input{interactive-parameters}

\section{Load Definition}

\input{interactive-workload}


\usepackage[empty]{fullpage}
\usepackage[compact]{titlesec}

% Datetime
\usepackage{datetime2}

% Font
\setmainfont{JetBrains Mono}

% Page Margin
\addtolength{\oddsidemargin}{-0.5in}
\addtolength{\evensidemargin}{-0.5in}
\addtolength{\textwidth}{1.0in}
\addtolength{\topmargin}{-0.5in}
\addtolength{\textheight}{1.0in}

% H1 Style
\titleformat{\section}{\large\bfseries\center}{}{}{}

% H2 Style
\titleformat{\subsection}{\large\bfseries}{}{}{}[\titlerule]

% Commands
\newcommand{\alignright}[0]{\hfill \hfill}

\newcommand{\footer}[1]
{
    \vfill
    \footnotesize{#1}
}

% Use LaTeX blocks in Markdown and still parse inner Markdown
\let\Begin\begin
\let\End\end

Add newline to end of file.


\input{x3-paper-preamble}

% ===============================
% Author and Document Information
% ===============================

\newcommand{\documentTitle}{Paper Title}
\newcommand{\documentDate}{ \today }
\newcommand{\documentAuthor}{
    \textbf{John Q. Student}
}
\newcommand{\documentAuthorEmail}{john@student.com}
\newcommand{\documentAuthorInstitution}{University of Ponyville}

\newcommand{\documentAbstract}{%
    \lipsum[1] % Dummy abstract text
}

%\ShowTOCtrue           % Enable to show table of contents
%\DisableAbstracttrue   % Uncomment to hide abstract
%\DisableRomanSectionstrue   % Uncomment to disable roman section numbering
%\SingleColumntrue      % Disable two column layout
%\SingleColumnTOCtrue   % Will show the TOC in a single column in two-column mode

\input{x3-paper-begin}

\section{Foobar}

\lipsum[2-6] % Dummy text

\section{Barfoo}

\lipsum[7-9] % Dummy text

\input{x3-paper-end}

Add bibliography example to x3-paper

\input{x3-paper-preamble}

% ===============================
% Author and Document Information
% ===============================

\newcommand{\documentTitle}{Paper Title}
\newcommand{\documentDate}{ \today }
\newcommand{\documentAuthor}{
    \textbf{John Q. Student}
}
\newcommand{\documentAuthorEmail}{john@student.com}
\newcommand{\documentAuthorInstitution}{University of Ponyville}

\newcommand{\documentAbstract}{%
    \lipsum[1] % Dummy abstract text
}

%\ShowTOCtrue           % Enable to show table of contents
%\DisableAbstracttrue   % Uncomment to hide abstract
%\DisableRomanSectionstrue   % Uncomment to disable roman section numbering
%\SingleColumntrue      % Disable two column layout
%\SingleColumnTOCtrue   % Will show the TOC in a single column in two-column mode

\input{x3-paper-begin}

\section{Foobar}

\lipsum[2-6] % Dummy text

\section{Barfoo}

\lipsum[7-9] % Dummy text

% Bibliography
%\clearpage
%\begin{flushleft}
%    \bibliography{bibliography}
%\end{flushleft}

\input{x3-paper-end}


\chapter*{Erklärung}
\begin{otherlanguage}{ngerman}
Ich versichere hiermit eidesstattlich, dass ich die vorliegende Arbeit
selbstständig verfasst, ganz oder in Teilen noch nicht als
Prüfungsleistung vorgelegt und keine anderen als die angegebenen
Hilfsmittel benutzt habe.

Sämtliche Stellen der Arbeit, die benutzen Werken im Wortlaut oder dem
Sinn nach entnommen sind, habe ich durch Quellenangaben kenntlich
gemacht. Dies gilt auch für Zeichnungen, Skizzen, bildliche
Darstellungen und dergleichen sowie für Quellen aus dem Internet. Bei
Zuwiderhandlung gilt die Masterarbeit als nicht bestanden.

Ich bin mir bewusst, dass es sich bei Plagiarismus um schweres
akademisches Fehlverhalten handdelt, das im Wiederholungsfall weiter
sanktioniert werden kann.

{
    \vskip3cm
    \par\noindent\makebox[7cm]{\hrulefill} \hfill\makebox[7cm]{\hrulefill}
    \par\noindent\makebox[7cm][l]{Ort, Datum}      \hfill\makebox[7cm][l]{Unterschrift}
}
\end{otherlanguage}

Add link to source code to references

\vskip1cm
The Go code of the implementation, as well as the Markdown (and minor amounts of \LaTeX) used to generate
this thesis can be retrieved from GitHub at:

\url{https://github.com/julian-klode/lingolang}

\chapter*{Erklärung}
\begin{otherlanguage}{ngerman}
Ich versichere hiermit eidesstattlich, dass ich die vorliegende Arbeit
selbstständig verfasst, ganz oder in Teilen noch nicht als
Prüfungsleistung vorgelegt und keine anderen als die angegebenen
Hilfsmittel benutzt habe.

Sämtliche Stellen der Arbeit, die benutzen Werken im Wortlaut oder dem
Sinn nach entnommen sind, habe ich durch Quellenangaben kenntlich
gemacht. Dies gilt auch für Zeichnungen, Skizzen, bildliche
Darstellungen und dergleichen sowie für Quellen aus dem Internet. Bei
Zuwiderhandlung gilt die Masterarbeit als nicht bestanden.

Ich bin mir bewusst, dass es sich bei Plagiarismus um schweres
akademisches Fehlverhalten handdelt, das im Wiederholungsfall weiter
sanktioniert werden kann.

{
    \vskip3cm
    \par\noindent\makebox[7cm]{\hrulefill} \hfill\makebox[7cm]{\hrulefill}
    \par\noindent\makebox[7cm][l]{Ort, Datum}      \hfill\makebox[7cm][l]{Unterschrift}
}
\end{otherlanguage}


\chapter{Introduction}

Unicorns are $\mathbb{PRETTY}$.

Add design by contract idea.

\chapter{Introduction}

Unicorns are $\mathbb{PRETTY}$.

\section{Ideas}

\begin{itemize}
  \item Semantic types are often used to label values that have a special property. For example, a list may be sorted, a file may be open and a matrix may be symmetric. Many of these properties can be checked quite easily. We can apply this observation to the notion of \textbf{design by contract} as follows: For a semantic type that is added to a specific value type, we can specify a function that checks whether the semantic type may be applied in the context of a specific value. These functions are applied during development and testing, may be optionally turned on in production, and lead to runtime errors if the contract is violated.
\end{itemize}


## Interface: 11200
## Title: EPGP
## Notes: Effort Points\Gear Points Loot System
## Author: Alkis Evlogimenos
## Version: 0.1
## OptionalDeps: Ace2
## SavedVariables: EPGP_DB
## X-Category: Guild

Libs\AceLibrary\AceLibrary.lua
Libs\AceOO-2.0\AceOO-2.0.lua
Libs\AceEvent-2.0\AceEvent-2.0.lua
Libs\AceAddon-2.0\AceAddon-2.0.lua
Libs\AceConsole-2.0\AceConsole-2.0.lua
Libs\AceDB-2.0\AceDB-2.0.lua
Libs\AceDebug-2.0\AceDebug-2.0.lua

Libs\Compost-2.0\Compost-2.0.lua
Libs\Dewdrop-2.0\Dewdrop-2.0.lua
Libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua
Libs\Tablet-2.0\Tablet-2.0.lua

Core.lua
Encoding.lua
Standings.lua

Make version be the revision in svn. Add the website.

## Interface: 11200
## Title: EPGP
## Notes: Effort Points\Gear Points Loot System
## Author: Alkis Evlogimenos
## Version: $Rev$
## OptionalDeps: Ace2
## SavedVariables: EPGP_DB
## X-Category: Guild
## X-Website: http://code.google.com/p/epgp

Libs\AceLibrary\AceLibrary.lua
Libs\AceOO-2.0\AceOO-2.0.lua
Libs\AceEvent-2.0\AceEvent-2.0.lua
Libs\AceAddon-2.0\AceAddon-2.0.lua
Libs\AceConsole-2.0\AceConsole-2.0.lua
Libs\AceDB-2.0\AceDB-2.0.lua
Libs\AceDebug-2.0\AceDebug-2.0.lua

Libs\Compost-2.0\Compost-2.0.lua
Libs\Dewdrop-2.0\Dewdrop-2.0.lua
Libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua
Libs\Tablet-2.0\Tablet-2.0.lua

Core.lua
Encoding.lua
Standings.lua