text:
% interface=en

\startcomponent co-documents

\environment contextref-env
\product contextref

\startFLOWchart [opzet-1]

  \startFLOWcell
    \shape{procedure}
    \name{onderdeel}
    \location{1,1}
    \text{\translate[nl=onderdeel,en=component]}
  \stopFLOWcell
  \startFLOWcell
    \shape{procedure}
    \name{omgeving-3}
    \location{1,2}
    \text{\translate[nl=omgeving,en=environment]}
    \connect [tb] {onderdeel}
  \stopFLOWcell

\stopFLOWchart

\startFLOWchart [opzet-2]

  \startFLOWcell
    \shape{procedure}
    \name{produkt}
    \location{1,1}
    \text{\translate[nl=produkt,en=product]}
    \connect [rl] {onderdeel}
  \stopFLOWcell
  \startFLOWcell
    \shape{procedure}
    \name{omgeving-2}
    \location{1,2}
    \text{\translate[nl=omgeving,en=environment]}
    \connect [tb] {produkt}
  \stopFLOWcell

  \includeFLOWchart[opzet-1][x=2,y=1]

\stopFLOWchart

\startFLOWchart [opzet-3]

  \startFLOWcell
    \shape{procedure}
    \name{projekt}
    \location{1,1}
    \text{\translate[nl=projekt,en=project]}
    \connect [rl] {produkt}
  \stopFLOWcell
  \startFLOWcell
    \shape{procedure}
    \name{omgeving-1}
    \location{1,2}
    \text{\translate[nl=omgeving,en=environment]}
    \connect [tb] {projekt}
  \stopFLOWcell

  \includeFLOWchart[opzet-2][x=2,y=1]

\stopFLOWchart

\chapter[documents]{Documents}

\section{Introduction}

Why should one use \TEX\ in the first place? Many people
start using \TEX\ because they want to typeset math. Others
are charmed by the possibility of separating content and
make||up. Yet another kind of user longs for a programmable
system. And let us not forget those users that go for quality.

When using \TEX\ one does not easily run into capacity
problems. Typesetting large documents with hundreds of
pages is typically a job for \TEX. If possible, when coding
a document one should look beyond the current document.
These days we see documents that were originally typeset
for paper being published in electronic format. And how
about making a stripped version of a 700 page document? A
strict separation between content and layout (make||up) on
the one hand and an acceptable redundancy in structure on
the other is often enough to guarantee multiple use of one
document source.

A system like \CONTEXT\ is meant to make life easier.
When coding a document the feeling can surface that \quotation
{this or that should be easier}. This feeling often
reflects the truth and the answer to the question can often
be found in this manual, although sometimes obscured. It
takes some time to learn to think in structure and content,
certainly when one is accustomed to mouse driven
word processors. In this chapter we focus on the structure of
collections of documents.

\section[startstop]{Start and stop}
\index{start}
\index{stop}
\index{structure}
\macro{\tex{starttext}}

In a self contained text we use the following commands to
mark the begin and end of a text:

\startexample
\starttyping
\starttext
\stoptext
\stoptyping
\stopexample

The first command takes care of a number of initializations
and the last command tells \TEX\ that processing can stop.
When this command is left out \TEX\ will display a \type{*}
(a star) on the command line at the end of the job. \TEX\
will expect a command, for example \type{\end}.

It is advisable to type the document setups before the
\type{\start}||command, the so called setup area of the
document. In this way a clever word||processor can identify
where the text starts, and therefore can include those
setups when it partially processes the document, given of
course that it supports partial processing of files.

In the example below a very simple layout is being used.

\startexample
\starttyping
\starttext

\subject{Introduction}

\unknown\ America has always been a land set firmly not in the past, but
in the future. On a recent visit to England, I found dozens of wonderful
bookstores chock full of the past --- ancient history, rooms full of it,
and great literature in such monumental stacks as to be overwhelming. In
the usual American bookstore, history might occupy a few bookcases; great
literature has its honoured place, but this year's paperbacks dominate. The
past is not disregarded, but neither does it loom so large and run so deep
in our blood.

\blank

{\bf Greg Bear, introduction to Tangents (1989).}

\stoptext
\stoptyping
\stopexample

The commands \type{\starttext...\stoptext} may be nested.
Within a text a new text containing \type{\starttext} and
\type{\stoptext} may be loaded.

\section[structure]{Structure}
\index{structure}
\index{products}
\index{projects}
\index{environments}
\index{components}
\macro{\tex{startproject}}
\macro{\tex{startproduct}}
\macro{\tex{startenvironment}}
\macro{\tex{startlocalenvironment}}
\macro{\tex{startcomponent}}
\macro{\tex{project}}
\macro{\tex{product}}
\macro{\tex{environment}}
\macro{\tex{components}}

In this section a structured approach of managing your
documents is discussed. For very simple and self containing
documents you can use the following approach:

\starttyping
\environment this
\environment that

\starttext
... some interesting text ...
\stoptext
\stoptyping

When you have to typeset very bulky documents it is better
to divide your document in logical components. \CONTEXT\
allows you to setup a project structure to manage your
texts. You have to know that:

\startitemize

\item A group of texts that belong together have to be
      maintained as a whole. We call this a {\em project}.

\item Layout characteristics and macros have to be defined
      at the highest level. For this, the term {\em
      environment} has been reserved.

\item Texts that belong together in a project we call {\em
      products}.

\item A product can be divided into components, these
      components can be shared with other products.
      Components can be processed individually.

\stopitemize

Programmable word processors can be adapted to this
structure.

A {\em project}, {\em environment }, {\em product} or {\em
component} is started and stopped with one of the following
commands:

\showsetup{startproject}
\showsetup{startproduct}
\showsetup{startenvironment}
\showsetup{startcomponent}

Before a \type{\start}||\type{\stop}||pair commands can be
added. When a file is not found on the directory \CONTEXT\
looks for the files on higher level directories. This
enables the user to use one or more environments for
documents that are placed on several subdirectories.

\placetable
  [here][tab:structure commands]
  {The structure commands that can be used in the files that
   make up a project.}
\starttable[|l|c|c|c|c|]
\HL
\VL \bf command     \VL
    \bf project     \VL
    \bf environment \VL
    \bf product     \VL
    \bf componnent  \VL\SR
\HL
\VL \type{\project <<name>>}
    \VL           \VL        \VL  \yes  \VL  \yes  \VL\FR
\VL \type{\environment <<name>>}
    \VL    (\yes) \VL (\yes) \VL (\yes) \VL (\yes) \VL\MR
\VL \type{\product <<name>>}
    \VL     \yes  \VL        \VL        \VL (\yes) \VL\MR
\VL \type{\componentonderdeel <<name>>}
    \VL           \VL        \VL (\yes) \VL (\yes) \VL\LR
\HL
\stoptable

To treat products and components as individual documents,
the commands in \in{table}[tab:structure commands] are used.
The commands marked with \yes\ are obligatory and the
commands marked with (\yes) are optional. The content is
typed before the \type{\stop} command.

\startbuffer
\startproject documents

\environment layout

\product  teacher
\product  pupil
\product  curriculum

\stopproject
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  An example of a project file.
\stopfiguretext

\startbuffer
\startproduct teacher

\project   documents

\component teacher1
\component teacher2

\stopproduct
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  The product \type{teacher.tex} (a teacher manual)
  can be defined as shown on the opposite site.
\stopfiguretext

\startbuffer
\startcomponent teacher2

\project documents
\product teacher

... text ...

\stopcomponent
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  Here we see the component.
\stopfiguretext

In most cases working with only \type {\starttext} and
\type {\stoptext} in combination with \type {\input} or
\type {\enviroment} is sufficient. A project structure has
advantages when you have to manage a great number of texts.
Although it is more obvious to process {\em products} as a
whole, it also enables you to process {\em components}
independently, given that the stucture is defined properly.

In principal a project file contains only a list of products
and environments. If you would process the project file all
products will be placed in one document. This is seldom
wanted. This manual for example has a project structure.
Every part is a product and every chapter is a component.
There are several environments that are loaded in the main
project file.

Schematically the coherence between files could be
displayed as illustrated in \in {figures} [fig:structure
1], \in [fig:structure 2] \in {and} [fig:structure 3].

\placefigure
  [here][fig:structure 1]
  {An example of project structure.}
  {\FLOWchart[opzet-3]}

\placefigure
  [here][fig:structure 2]
  {An example with only products.}
  {\FLOWchart[opzet-2]}

\placefigure
  [here][fig:structure 3]
  {An example with only one component.}
  {\FLOWchart[opzet-1]}

It is good practice to put all setups in one environment.
In case a component or product has a different layout you
could define {\em localenvironments}:

\startexample
\starttyping
\startlocalenvironment[<<names>>]
... setups ...
\stoplocalenvironment
\stoptyping
\stopexample

A local environment can be typed in an environment file or
is a separate file itself. When a separate file is used the
local environment is loaded with:

\startexample
\starttyping
\localenvironment <<name>>
\stoptyping
\stopexample

Below you will find an example of a project structure.

\startbuffer
\startproject demos

\environment environ
\product     example

\stopproject
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  file: \type{demos.tex}
  \blank
  This file is used to define the products and environments.
\stopfiguretext

\startbuffer
\startenvironment environ

\setupwhitespace[big]

\setupfootertexts[part][chapter]

\stopenvironment
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  file: \type{environ.tex}
  \blank
  In the environment we type the setups that relate to all
  the different products. More than one environment or local
  environments per product can be used.
\stopfiguretext

\startbuffer
\startproduct example

\project demos

\startfrontmatter
  \completecontent
\stopfrontmatter

\startbodymatter
  \component first
  \component second
\stopbodymatter

\startbackmatter
  \completeindex
\stopbackmatter

\stopproduct
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  file: \type{example.tex}
  \blank
  The product file contains the structure of the product.
  Because indexes and registers can be evoked quite easily
  we do not use a separate file.
\stopfiguretext

\startbuffer
\startcomponent first

\part{One}

\completecontent

\chapter{First}

..... text .....

\chapter{Second}

..... text .....

\completeindex

\stopcomponent
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  file: \type{first.tex}
  \blank
  In the components of a product we place the textual
  content, figures etc. It is also possible to request the
  tables of content and registers per product.
\stopfiguretext

\startbuffer
\startcomponent second

\part{Two}

\completecontent

\chapter{Alfa}

..... text .....

\chapter{Beta}

..... text .....

\completeindex

\stopcomponent
\stopbuffer

\startfiguretext[left,offset]{none}
  \startMiniFile
    \typebuffer
  \stopMiniFile
  file: \type{second.tex}
  \blank
  The product contains more than one component. We could have
  defined a product for each part and a component for each
  chapter.
\stopfiguretext

The files \type{first.tex}, \type{second.tex} and
\type{example.tex} can be processed separately. As long as
there is one product in this project you can also process
\type{project.tex}. If you process an environment there will
be no pages of output.

\section[directories]{Directories}
\index{files+directories}
\index{directories}

Many \TEX\ implementations look for a file in all
directories and subdirectories when a requested file is not
in the current directory. This is not only time||consuming
but may lead to errors when the wrong file (a file with the
same name) is loaded.

For this reason \CONTEXT\ works somewhat differently. A file
that is not available on the working directory is searched
for on the parent directories. This means that environments
can be placed in directories that are parents to the
products that use them. For example:

\starttyping
/texfiles/course/layout.tex
/texfiles/course/teacher/manual.tex
/texfiles/course/student/learnmat.tex
/texfiles/course/otherdoc/sheets.tex
\stoptyping

The last three files (in different subdirectories) all use
the same environment \type {layout.tex}. So, instead of
putting all files into one directory, one can organize them
in subdirectories. When a project is properly set up, that
is, as long as the project file and specific environments
can be found, one can process components and products
independently.

\section[versie]{Versions}
\index{testing}
\index{references+checking}
\index{index+checking}
\macro{\tex{version}}

During the process of document production it is useful to
generate a provisional version. This version shows the
references and the typesetting failures. The provisional
version is produced when you type:

\showsetup{version}

By default the definitive version is produced. In case a
preliminary version is produced the word {\em concept} is
placed at the bottom of each page. The keyword \type
{temporary} shows some information on for instance overfull
lines, references, figure placement, and index entries. Most
messages are placed in the margin. In some cases these
messages refer to the next pages because \TEX\ is processing
in advance.

\section[modes]{Modes}
\index{selective typesetting}
\index{modes}
\index{styles}
\index{specials}
\index{output format}
\index[texexec+mode]{\TEXEXEC+mode}
\macro{\tex{setupoutput}}
\macro{\tex{startmode}}
\macro{\tex{startnotmode}}
\macro{\tex{enablemode}}
\macro{\tex{disablemode}}
\macro{\tex{doifmodeelse}}
\macro{\tex{doifmode}}
\macro{\tex{doifnotmode}}

\TEX\ can directly produce \DVI\ or \PDF. A document can be
designed for paper and screen, where the last category
often has additional functionality. From one document we
can generate different alternatives, both in size and in
design. So, from one source several alternatives can be
generated.

Processing a file in practice comes down to launching \TEX\
with the name of the file to be processed. Imagine that by
default we generate \DVI\ output. Switching to \PDF\ is
possible by enabling another output format in the file itself
or a configuration file, but both are far from comfortable.

\starttyping
\setupoutput[pdftex]
\stoptyping

for direct \PDF\ output, or for \PDF\ produced from
\POSTSCRIPT:

\starttyping
\setupoutput[dvips,acrobat]
\stoptyping

The key to the solution of this problem is \TEXEXEC. This
\PERL\ script provides \CONTEXT\ with a
command||line||interface. When we want \PDF\ instead of
\DVI, we can launch \TEXEXEC\ with:

\starttyping
texexec  --pdf  filename
\stoptyping

There are more options, like making A5||booklets; more on
these features can be found in the manual that comes with
\TEXEXEC. However, one option deserves more time: modes.

\starttyping
texexec  --pdf  --mode=screen  filename
\stoptyping

The idea behind modes is that within a style definition, at
each moment one can ask for in what mode the document is
processed. An example of a mode dependant definition is:

\starttyping
\startmode[screen]
  \setupinteraction[state=start]
  \setupcolors[state=start]
\stopmode
\stoptyping

if needed, accompanied by:

\starttyping
\startnotmode[screen]
  \setupcolors[state=start,conversion=always]
\stopnotmode
\stoptyping

One can also pass more than one mode, separated by comma's.
There are also some low level mode dependant commands.
Given that we are dealing with a screen mode, we can say:

\starttyping
\doifmodeelse {screen} {do this} {and not that}
\doifmode     {screen} {do something}
\doifnotmode  {screen} {do something else}
\stoptyping

A mode can be activated by saying:

\starttyping
\enablemode[screen]
\disablemode[screen]
\stoptyping

Again, we can pass more modes:

\starttyping
\enablemode[paper,A4]
\stoptyping

One strength of \TEXEXEC\ is that one is not forced to
enable modes in a file: one can simply pass a command line
switch. Just as with choosing the output format: the less
we spoil the document source with output and mode settings,
the more flexible we are.

To enable users to develop a style that adapts itself to
certain circumstances, \CONTEXT\ provide system modes. For
the moment there are:

\starttabulate[|lT|p|]
\NC *list         \NC the list one called for is placed indeed     \NC \NR
\NC *register     \NC the register one called for is placed indeed \NC \NR
\NC *interaction  \NC interaction (hyperlinks etc) are turned on   \NC \NR
\NC *sectionblock \NC the named sectionblock is entered            \NC \NR
\stoptabulate

System modes are prefixed by a \type {*}, so they will not
conflict with user modes. An example of a sectionblock mode
is \type {*frontmatter}. One can use these modes like:

\starttyping
\startmode[*interaction]
  \setuppapersize[S6][S6]
\stopmode
\stoptyping

\section{Modes Manual}

\todo{Merge with previous section}

Every user will at one moment run into modes. Modes are used for
conditional processing. You enable or disable modes:

\starttyping
\enablemode[screen]
\disablemode[proof]
\stoptyping

as well as prevent modes being set:

\starttyping
\preventmode[doublesided]
\stoptyping

Later on you can act upon this mode using:

\starttyping
\startmode[screen]
  \setupinteraction[state=start]
\stopmode
\stoptyping

The counterpart of this command is:

\starttyping
\startnotmode[screen]
  \setupinteraction[state=start]
\stopnotmode
\stoptyping

You can set modes in your document or in styles, but you can
also do that at runtime:

\starttyping
texexec --pdf --mode=screen --result=myfile-s myfile
texexec --pdf --mode=A4     --result=myfile-a myfile
texexec --pdf --mode=letter --result=myfile-l myfile
\stoptyping

You can test for more modes at the same time:

\starttyping
\startmode[color,colour]
  \setupcolors[state=start]
\stopmode
\stoptyping

If you want to satisfy a combination of modes, you use:

\starttyping
\startmode[final]
  \setuplayout[markings=on]
\stopmode
\startallmodes[final,color]
  \setuplayout[markings=color]
\stopallmodes
\stoptyping

The counterpart is

\starttyping
\startnotallmodes[print,proof]
  \setuplayout[markings=off]
\stopnotallmodes
\stoptyping

Instead of the \type {start}||\type {stop} variants, you can use
the \type {\doif} alternatives. These have the advantage that they
can be nested.

\starttyping
\doifmodeelse     {modes} {action} {alternative}
\doifmode         {modes} {action}
\doifnotmode      {modes} {action}
\doifallmodeselse {modes} {action} {alternative}
\doifallmodes     {modes} {action}
\doifnotallmodes  {modes} {action}
\stoptyping

Mode can be combined with variables:

\starttyping
\setupvariables[document][alternative=print]

\enablemode[document:\getvariable{document}{alternative}]

\startmode[document:print]
  ...
\stopmode

\startmode[document:screen]
  ...
\stopmode
\stoptyping

An alternative for such an selective approach is to use setups:

\starttyping
\setupvariables[document][alternative=print]

\startsetups[document:print]
  ...
\stopsetups

\startsetups[document:screen]
  ...
\stopsetups

\setups[document:\getvariable{document}{alternative}]
\stoptyping

The difference is that mode blocks are processed in the order that
the document (or style) is loaded, while setups are stored and
recalled later.

In addition to your own modes, \CONTEXT\ provides a couple
of system modes. These are preceded by a \type {*}, as in:

\starttyping
\startmode[*first]
  % this is the first run
\stopmode
\stoptyping
 The following system modes are available (more will implemented):

% \start \setuptype[color=]

\startswitch
{\type{color-c},\type{color-m},\type{color-y},\type{color-k}}

These are rather special modes related to color separation. They are
only set when channels are split off.

\stopswitch

\startswitch {\type{figure}}

This mode is set when a graphic is found. You can use this mode in
for instance figure postprocessing actions.

\stopswitch

\startswitch {\type{text}, \type{project}, \type{product},
\type{component}, \type{environment}}

These modes are set when one enters one of the associated
structuring environments. Nesting is supported.

\stopswitch

\startswitch {\type{list}}

After using \type {\determinelistcharacteristics} this mode reflects
if list entries were found.

\stopswitch

\startswitch {\type{pairedbox}} This mode is enabled when a paired
box (legenda and such) is constructed. \stopswitch

\startswitch {\type{combination}} This mode is enabled when a
combination (often used for graphics) is constructed. \stopswitch

\startswitch {\type{interaction}}

When interaction is enabled, this mode is true. You can for instance
use this mode to add different content to for instance screen and
paper versions.

\stopswitch

\startswitch {\type{register}}

After using \type {\determineregistercharacteristics} this mode
reflects if register entries were found.

\stopswitch

\startswitch {\type{sectionnumber}}

This mode is enabled when a section head is numbered. You can access
the mode while building the section head, which is true when you have
your own commands hooked into the head mechanism.

\stopswitch

\startswitch {\type{frontpart}, \type{bodypart}, \type{backpart},
\type{appendix}}

The state of main sections in a document as well as user defined
ones, are reflected in system modes.

\stopswitch

\startswitch {\type{suffix-\jobfilesuffix}}

You can use this mode to differentiate between input file types. We
use this for instance to distinguish between different XML content
variants when pretty|-|printing (given that they can be recognized
on their suffix).

\stopswitch

\startswitch {\type{first}}

Often multiple runs are needed to get a document right. Think of
cross references, object references, tables of contents, indices,
etc. You can use this mode to determine if the first run is taking
place. For instance, when you do real time graphic conversions, it
makes sense to do that only once.

\stopswitch

\startswitch {\type{last}}

This mode is set if the last run in a session is taking place.
Normally this is not known in advance, unless one has asked for an
additional imposition pass.

\stopswitch

\startswitch {\type{background}}

This mode is set when there is a (new) background defined.

\stopswitch

\startswitch {\type{postponing}}

While postponing some content using the postpone mechanism this mode
is enabled.

\stopswitch

\startswitch {\type{grid}}

When you are typesetting on a grid, special care has to be taken not
spoil grid snapping. You can use this mode to test if you are in
grid typesetting mode.

\stopswitch

\startswitch {\type{header}}

This mode is enabled when there is a page header, i.e.\ the header
has non|-|zero dimensions.

\stopswitch

\startswitch {\type{footer}}

This mode is enabled when there is a page footer, i.e.\ the header
has non|-|zero dimensions.

\stopswitch

\startswitch {\type{makeup}}

The makeup mechanisms are used to build single pages like title
pages. This mode is set during construction.

\stopswitch

\startswitch {\type{pdf}, \type{dvi}}

One of these modes is set, which one depends on the output driver
that is loaded.

\stopswitch

\startswitch {\type{*language-id}, \type{language-id}}

When a language is chosen, its id is set as mode. For example, when the main
language is English, and the current language Dutch, we can test for the
modes \type {**en} and \type {*nl} (watch the extra \type {*}).

\stopswitch

\startswitch {\type{marking}}

This flag is set when a marking (e.g.\ in a header or footer) is
being typeset (processed).

\stopswitch

\section {Regimes}

When you key in an english document, a normal \kap {QWERTY}
keyboard combined with the standard \ASCII\ character set
will do. However, in many countries dedicated keyboards and
corresponding input encodings are used. This means that
certain keystrokes correspond to non||standard \ASCII\
characters and these need to be mapped onto the characters
present in the font. Unless the input encoding matches the
output (font) encoding, intermediate steps are needed to
take care of the right mapping. For instance, input
code~145 can become command \type {\eacute} which can
result in character~123 of a certain font.

Although all kind of intermediate, direct or indirect,
mappings are possible, in \CONTEXT\ the preferred method is
to go by named glyphs. The advantage of this method is that
we can rather comfortably convert the input stream into
different output streams as needed for typesetting text (the
normal \TEX\ process) and embedding information in the file
(like annotations or font vectors needed for searching
documents).

The conversion from input characters into named glyphs is
handled by regimes. While further mapping is done
automatically and is triggered by internal processes,
regimes need to be chosen explicitly. This is because only
the user knows what he has input.

Most encodings (like \type {il2}) have an associated regime. You
can get some insight in what a regime involves by showing it:

\starttyping
\showregime[il2]
\stoptyping

In addition there are a couple of platform dependent ones:

\starttabulate[|lT|lp|]
\HL
\NC \bf regime \NC \bf platform \NC \NR
\HL
\NC ibm \NC the old standard \MSDOS\ code page       \NC \NR
\NC win \NC the western europe \MSWINDOWS\ code page \NC \NR
\HL
\stoptabulate

If you want to know what regimes are available, you can take a
look at the \type {regi-*.tex} files. A regime that becomes more
and more popular is the utf-8 regime. If you want some insight in
what vectors provide, you can use commands like:

\starttyping
\showunicodevector[001]
\stoptyping

and

\starttyping
\showunicodetable[001]
\stoptyping

where the last one produces a rather large table.

\stopcomponent

max_stars_repo_name: marcpaterno/texmf

max_issues_repo_name: marcpaterno/texmf

max_forks_repo_name: marcpaterno/texmf


text:
\chapter{Evaluation}

This evaluation chapter attempts to evaluate the progress made, how time was spent and whether or not the project was successful in completing all of the stories. This chapter discusses the good things in the work and the aspects for which it can be improved. This evaluation should also cover how complete the application is and how the requirements fit into the end product.

\section{Requirements Completion}
This section focuses on discussing how complete each story is from Section \ref{STORIES}. The stories are listed with the completion level detailed beneath each story in a sub-list.

\begin{itemize}
    \item Design a working prototype of the application
    \begin{itemize}
        \item The application has a mostly functional prototype that gives any user the ability to understand how the application should function.
    \end{itemize}

    \item Refine the design of the prototype to ensure compliance with Material Design guidelines \cite{MATERIALDESIGNGUIDELINES}.
    \begin{itemize}
        \item The design was constantly refined throughout the production of the application, as discussed in Chapter \ref{IMPLEMENTATION}. The explicit design decisions that were changed were discussed in detail earlier in Section \ref{DESIGNCHANGESSECTION}, but Material Design was a heavy influence throughout the project.
    \end{itemize}

    \item Utilise a functional Continuous Integration software (Bitrise \cite{BITRISE}) to perform routine tests and ensure the application works across multiple devices, resolutions, and API versions.
    \begin{itemize}
        \item Bitrise was used continuously throughout the development cycle and will continue to work outside of this project. It tests devices on each API between 21 and 29, not only those but also most of the APIs use different screen sizes to ensure that parts are functional on both flagship smartphones and cheaper alternatives.
    \end{itemize}

    \item Stick to the multiple coding standards for Python (PEP8), Kotlin (Coding Style Guidelines) and any other languages that have been chosen on the GitHub Wiki
    \url{https://github.com/Pasarus/FelineAdoptionAgencyMajorProject/wiki}
    \begin{itemize}
        \item I stuck to the PEP8 standards for all python. The Kotlin style guideline was not always stuck to as I was new to the language and the style at the start of the project, but I believe that I have stuck as close as possible with my current level of expertise in Kotlin.
    \end{itemize}

    \item Create a Cat Finder tool in the application that allows a person to find a cat to adopt similar to Cats Protection's find-a-cat \cite{CATSPROTECTION}. This should be a list, probably a RecyclerView that has a Material\gls{Card} that allows us to view some basic details and save the cat. The Card should include Image, Name, Age, and Location with more details available on tap, opening a more information screen. This should be done in line with the Material Guidelines \cite{MATERIALDESIGNGUIDELINES}.
    \begin{itemize}
        \item The Cat Finder tool was fully implemented using, a RecyclerView and emulates most of the features from Cats Protection's find-a-cat. The \gls{Card} is functional and shows the Image, Name, Age, and Location of the cats, with further information available after tapping the cards, completed in line with Material Design Guidelines in all aspects except for Navigation Transitions functioning correctly.
    \end{itemize}

    \item A tool that displays detailed \gls{Card}s that represent the data of any Cat that has been saved by a user. These \gls{Card}s should be more detailed than those created in the Cat Finder tool, as these Cats are ones of keen interest to potential Adopters and should be featured as such.
    \begin{itemize}
        \item The Cat Saver functionality is fully implemented, and the saved Cats are synced by the user being logged in. The \gls{Card}s are more detailed than those in the Cat Finder tool and should keep users more interested in these cats.
    \end{itemize}

    \item Login functionality that allows a user to sync data across devices (their saved cats and user data), allow a user to adopt a cat only when logged in and view their status for approval of the adoption of a cat.
    \begin{itemize}
        \item Login functionality is fully implemented and is used to sync all data across multiple devices using one login account. It is implemented with Firebase Authentication.
    \end{itemize}

    \item Utilise Google Firebase as storage for all data required by the application, with appropriate security enforced to ensure that user data is protected in line with current EU and UK data protection legislation including GDPR \cite{GDPRARTICLE1}.
    \begin{itemize}
        \item The methodology of system security revolves around only storing data that is crucial to process function. All data is secure and transmitted using end-to-end encryption. Data is only available with a secure login to the Firebase Firestore at present.
    \end{itemize}

    \item Create adequate secondary screens to support the functionality of the application, including Settings, Help, Feedback, About, and My Account screens. When a user has logged in allow access to My Account otherwise request login before access is given because then data retrieval is possible.
    \begin{itemize}
        \item Settings is not fully implemented due to limitations from time; however, Help, Feedback, About and My Account screens are all fully functional.
    \end{itemize}

    \item Create a sufficiently well-presented Landing/Home screen that allows a user to see their adoption statuses, and a featured cat so users can immediately see a cat, and their adoption statuses as easily as possible. Keeping a user in the app if possible if they accidentally click on it, would potentially lead to more users adopting, the user is likely to be more distracted by the immediate availability of a cute featured cat.
    \begin{itemize}
        \item Home screen is created and feature complete. Featured cat functionality works well showing a random cat.
    \end{itemize}

    \item Support Android 21+ for development in an aim to make the application available to at minimum 85\% of all Android users.
    \begin{itemize}
        \item Android 21 to 29 is fully supported, and the application should work on all API variations in between. Confirmed via manual testing and continuous integration.
    \end{itemize}

    \item Provide a correctly signed and as functional as possible release version of the application as an APK for Android.
    \begin{itemize}
        \item APK has been signed correctly and constructed, tested on physical devices. Connection to Firebase is successful due to SHA1 certificate being present based on signed Android key.
    \end{itemize}

\end{itemize}

\section{Design Decisions}

Prototyping went very well, and it became invaluable during the implementation of the application. The prototype worked in the way that was hoped, and the prototype was used many times throughout the implementation sprints to guide design and influence decision making.

UX Design overall has a few flaws. While the main screens and navigation methodologies are of good quality, the sub-screens, however, do have some features that overlap or should be redesigned to look and feel nicer to navigate and use. Notably, the adoption status information and cat information screens, while the prototype looks good the end-product does not have the same feel or easy on the eyes design, with more time I would like to improve those screens, as while they are functional, they are not pleasant to view.

DataService as a central function of the entire application was invaluable. It holds functionality needed throughout the application as well as holds key member variables that control the state of the application. To do this project again, I would heavily recommend the use of a Singleton class that holds an application state that is accessible without GUI components, that relates to the current application state. The DataService is used in almost all screens to some functionality, and without it, the application would not function, it, however, could, in theory, be replaced and allow the use of almost any other back-end.

Firebase is the fundamental backbone of the project. Firebase provides authentication functionality, data storage, file hosting, UI integration testing and secure communication with each feature. It's implementation while not necessarily easy, the tools have great interactability which would not necessarily have been possible without Firebase, given the time constraints.

The design process went overall quite well, and I believe that I followed the basic design principles I set out with. I found design was done in a waterfall fashion to a higher degree than my agile process would suggest, but that was due to the fact that Android applications require some UX prototyping before any other work can be completed.

\section{Tool Suitability}

GitHub is a git hosting platform with other tools for software development. It was used to great effect and became very useful, and its suitability is very high for this project. Use of the repository functionality including the wiki and Kanban project boards ensured the project could follow an agile approach, with the GitHub issues being prioritised on each sprint's project board.

Bitrise is a Continuous integration platform aimed at mobile application development. It has a very user-friendly interface, and integration took about 3 minutes to set up initially. While initial integration was not sufficient and had to be expanded upon, a great base test flow was given, to begin with.

Android Studio and PyCharm were the IDEs of choice when developing during this project. PyCharm was the IDE of choice for python development and worked flawlessly. Android Studio has a feature called AVM or Android Virtual Machine, and these AVMs do not run easily on AMD based processor architectures without some modifications, this is because of the way Intel has produced proprietary software for virtualisation of x86 architectures, while AMD lacks behind.

Coding Standards, the PEP8 and Kotlin Lang style guides are excellent standards for writing code that is maintainable and readable by a general developer who is just starting to get used to the language. It reduces jumbled code and allows a maintainer to jump in and produce the same level of code quality as the rest of the file.

Firebase was invaluable in the completion of the project and provided a solid, well tested, and free for low traffic backbone for development. Firebase is aimed towards the development of projects of this kind and was very suitable to the tasks it was used in.

With regards to testing, UI instrumentation tests where the UI tests are performed on many devices were invaluable, ensuring applications do start and navigation is performed correctly on all supported API levels. The unit testing is performed only on parts of the code base that does not require Activity, and as such is somewhat limited in scope, however, the testing coverage aim is an individual test class should test every branch of code execution in the class it is testing. The tools used for this were JUnit and espresso, espresso has a test recorder that made writing UI instrumentation tests much faster.

I found that by the end of the project, the tool suitability had been ironed out. I found that all of the tools that were used fit very well for their requirements in all stages of the project.

\section{How to Improve}

In this section, there is a discussion on how the project could have been improved if done again, including design decisions, time management, and code quality for both readability and maintainability.

    \subsection{Design Decisions}
    Ensuring broader research into tools available before designing and implementing what someone else has already done. Before I was made aware of Firebase and it's capabilities, I started to design and implement a web framework, that would, in essence, provide basic sign-in authentication, and data storage. I got far enough to have a basic RESTful API functional from my PC. Had I researched how it is done more thoroughly, I would have made the correct Design Decision earlier and saved myself work and time.

    \subsection{Time Management}
    As the project dragged, and as with a team size of 1, I found that sticking to a ridged agile process took too much time, if I were to start again, I would do away with the sprints and adopt a Kanban only approach. While a sprint gave ample opportunity for review, the time spent reviewing and rearranging the Kanban board every sprint could have been spent on development, design, and quality assurance.

    Notably, due to the COVID19 pandemic, my ability to focus and work on my dissertation was hampered by home life. With a younger brother, mother, and partner present at the house, I found my time for work dwindled rather rapidly. I would typically when writing a lengthy report, spend much time at the university planning and writing my report, this was not possible, but I would certainly do that if I were able to do it all over again.

    While my retrospectives and personal notes on how I progressed throughout the project are useful in writing this report, I firmly believe that the development of this project should have taken place at the same time as I was writing this report. The design chapter would have been easier to write shortly after the design was completed; the design is the part of the project completed earliest; the same is true for the other chapters.

    \subsection{Pull Requests and Code Review}
    If I were to start this project again, I would prefer to refine my workflow and replace the testing on every commit with the testing on pull requests and perform a code review of the produced code. While working in industry in a team, I found it invaluable to either look over my code again or have someone else with a fresh pair of eyes look at my code. Then when the builds have passed, I would merge the branch relating to the pull request, and this would reduce bugs and mean that the Master branch always had working code present according to the tests.

    \subsection{Automated Testing Login and Firebase Functionality}
    One major stickler for the maintainability for this application is the lack of testing for any login required features. While Manual tests were devised and should cover these areas, if these could be performed regularly on every commit with automated tests, and functional regression would be noticed immediately.

    Furthermore testing that involved ensuring Database viability was more limited than it should be, while due to the nature of callback tests being hard to perform a better testing methodology should have been developed to improve detection of instability and feature regression further.

    With better test coverage, increased confidence could be had in utilising programming practices such as merciless refactoring, and more structured scrum sprints.

\section{Further Development}

To further development, there are a few things that would need to be worked on:

\begin{itemize}
    \item A UX design review, to ensure Material Design guidelines are followed
    \item Actual integration with real data for an adoption charity
    \item Refine of the filter features for the cat finder
    \item Improve how parts of the application look where there is no data to display such as default splash screens replace RecyclerViews
    \item Improve the Cat details screen and the Adoption status details screen
    \item Improve text scaling for different screen sizes
    \item Improve the form sections to ensure that all required details are given
    \item Location functionality instead of an actual address. Confirmed later as an address by an administrator.
    \item A separate application that is developed to ensure an administrator that can process applications and conduct appointments on time with the following features:
    \begin{itemize}
        \item Appointment request lists and the phone numbers to call
        \item Form to fill in appointment times
        \item Map integration to get to the address given using directions
        \item Checklist for investigations into the premises/user
        \item Ability to update the Cat list to ensure they are marked as reserved after an appointment has been confirmed.
        \item Tracking in case of emergency while on company/charity time, only while the app is in the foreground to avoid privacy invasion.
    \end{itemize}
\end{itemize}

ext: tex


text:
\usepackage{ifthen}
%\usepackage{newfile}
\usepackage{etoolbox}
\usepackage{environ}
\usepackage{xspace}
\usepackage{stringstrings}
\usepackage{datetime2}
\DTMsetstyle{iso}
\edef\compiletime{\DTMnow}
\newwrite\compiletimefile
\openout\compiletimefile=\jobname.compiletime
\write\compiletimefile{\compiletime}
\closeout\compiletimefile
\usepackage[colorlinks]{hyperref}
\hypersetup{
    citecolor = {citecolor}
}
\usepackage{tikz}
\usepackage[
  backend=bibtex8,
  style=alphabetic,
  url=true,
  doi=true,
]{biblatex}
\usepackage{xcolor}
\definecolor{citecolor}{rgb}{0,0.5,0.25}
\definecolor{homeworkcolor}{rgb}{0.2,0.0,0.6}

% layout
\settocdepth{section}
\setsecnumdepth{chapter}
\def\semester#1{\chapter{#1}}
\def\signature#1{\begin{flushright}\itshape#1\end{flushright}}
% make section numbers stick out to the left
\makeatletter
\def\@seccntformat#1{\protect\makebox[0pt][r]{\csname the#1\endcsname\quad}}
\makeatother

% refs

% index
\def\topic#1{\index{#1}\xspace}

% define lesson on a per-teacher basis
\newcounter{lessoncount}
\newenvironment{lesson}[1]
  {\stepcounter{lessoncount}\begin{section}{#1}}
  {\end{section}}
\def\defteacher#1#2#3{%
  \newtoggle{show#1}
  \toggletrue{show#1}
  \NewEnviron{#1}[1]
  {%
    \iftoggle{show#1} {%
      \begin{lesson}{{##1}~~(\capitalize{#1})}%
        \InputIfFileExists{content/#1mac}{}{}%
        \BODY%
      \end{lesson}
    }{}
  }
}

\def\notesname{Notes}

% notes
\newenvironment{notes}
    {\bigskip\begin{center}\large\bfseries\notesname\end{center}\endgraf}
    {}

\input{teacherlist}

% math macros
\include{mathmac}

% write aula count
\def\writeaulacount{%
\newwrite\countfile
\openout\countfile=\jobname.count
\write\countfile{\thelessoncount}
\closeout\countfile
}

max_stars_repo_name: tsouanas/aulabook-fmcmon

max_issues_repo_name: tsouanas/aulabook-fmcmon

max_forks_repo_name: tsouanas/aulabook-fmcmon


text:
% !TeX spellcheck = en_US
% !TeX root = ../main.tex
\section{Discussion}
\label{sec:discussion}

We have introduced an analytical framework for the dynamic network analysis of legal documents and demonstrated its utility by applying it to a dataset comprising federal statutes and regulations in the United States and Germany over a period of more than $20$ years.
The limitations of this work concern two separate areas:
the methods introduced in Section~\ref{sec:methods} and the results presented in Section~\ref{sec:results}.

To gravitate toward its ideal formulation, our framework requires further refinement based on experiences from applications to diverse datasets.
Our model is deliberately document type and country agnostic, such that it can be easily instantiated for new data.
Similar studies using legal documents from a variety of jurisdictions would be of immense value for improving our framework,
and they could provide further context for the results reported in Section~\ref{sec:results}.
Furthermore, our network analytical framework could be complemented by a framework for natural legal language processing,
as the combination of relational information and linguistic information will likely lead to insights that would not be possible using either of these sources alone.

When preparing this article, we found that combining documents of different types in one graph representation raises many conceptual questions.
Some of these questions relate to the presentation of our results, e.g.,
whether to depict dynamics in absolute or relative terms (thereby either impairing comparisons across document types of different sizes or visually overstating dynamics for small baselines).
Others concern design decisions when defining our methods,
e.g., whether tokens from documents of different types should have the same weight when determining cluster families even if there is a striking imbalance between the total number of tokens in documents of these types (as is the case in our United States data).
Here, one alternative would be to rescale the token counts before constructing the cluster family graph,
such that the total influence of tokens from one specific document type is equal across all types.
While this would change the results to a certain extent,
it is difficult to assess whether the modified method would be superior because comparable investigations of multimodal legal document networks currently do not exist.

The results stated in Section~\ref{sec:results} are limited in geographic scope (United States and Germany), temporal scope ($1998$--$2019$), and institutional scope (legislative and executive branch on the federal level).
Most importantly, our findings cover only codified law.
As the United States and Germany are typically assumed to follow distinct legal traditions (common law and civil law),
which are often thought to differ, inter alia, in their reliance on court precedent, including court decisions might have disparate impact on our results for both countries.
However, it could also provide empirical evidence against the traditional classification.
Irrespective of legal traditions, unlocking and integrating judicial data is an important direction for future work.

Regarding both growth and connectivity, the next steps consist in eliminating the uncertainties and limitations affecting our data.
For example, as highlighted in Section~\ref{subsec:data:instance}, one important stride toward a more comprehensive picture of the connectivity between legal documents is the extraction and resolution of non-atomic references.
At the macro level, connectivity could also be evaluated at other resolutions (e.g., the chapter level) or when including hierarchy edges,
and our analysis could be expanded using further statistics, such as motif counts and their evolution over time.
Furthermore, applying our methods to other document types or other countries would help us assess whether the rocket structure we found in our data is characteristic of legal systems in general.
When assessing connectivity at the meso level, the dynamic map of law provided by our cluster families could be further refined, especially at other resolution levels.
At the micro level of connectivity, a more fine-grained star taxonomy might be in order because in both countries, there exists some functional overlap between hinge stars and sink stars.
For the profiles, a sensible step forward would be to apply the tracing methodology at other levels of resolution (e.g., at the level of individual sections), and the statistics we track could be complemented by similarity measures allowing us to compare between the different units of law we analyze.

Beyond the specific opportunities for further research outlined above,
our work raises three larger questions to be explored in the future:
\begin{enumerate}
	\item \emph{When quantitatively analyzing legal documents, how should we choose the unit of analysis?}\\
	On the one hand, no clear consensus exists as to what constitutes a \emph{unit of law} or a \emph{legal rule}.
	But on the other hand, the choice has far-reaching consequences for all analyses.
	Furthermore, even analyzing all documents at the same structural level presents problems:
	Legal rules come in various sizes, and at times, a single paragraph might be longer than the average document due to drafting decisions by the agents in the legal system.
	This complicates comparisons and creates countless opportunities for erroneous interpretations.
	Detailing the full rationale behind all choices we made when presenting our results in Section~\ref{sec:results} is beyond the scope of this article.
	However, an extensive exposition of the possible choices and the tradeoffs surrounding them would benefit the research community at large and, therefore, constitutes a fecund field for future findings.
	\item \emph{How can we measure the \emph{regulatory energy} of statutes?}\\
	The analysis of individual statutes such as the Gramm-Leach-Bliley Act and the Dodd-Frank Act suggests that legislative outputs impact their environments at potentially different rates (e.g., by prompting further rule making),
	i.e., that they have a certain \emph{regulatory energy} that they emit over time.
	This hypothesis could be validated, inter alia, using external data on regulatory relevance, e.g., the filings concerning regulatory risk that are required for annual and transition reports pursuant to sections 13 or 15(d) of the Securities Exchange Act of $1934$ under 17~CFR~249.310 -- Form 10-K \cite{bommarito2017}.
	However, other approaches are equally possible and merit further investigation.
	\item \emph{How can we connect our empirical findings to established theories in law and political science?}\\
	Although beyond the scope of this work, some of our findings can be combined with analyses using established theories on the composition and evolution of codified law in both legal scholarship and political science.
	The most prominent example here is the question of delegation:
	How does it happen and what are its limits, in theory and in practice?
	This touches the heart of democratic legitimacy, and it presents a promising opportunity for empirical legal studies to contribute to mainstream legal and political science discourse that we are planning to seize in the future.
\end{enumerate}

max_stars_repo_name: QuantLaw/Measuring-Law-Over-Time

max_issues_repo_name: QuantLaw/Measuring-Law-Over-Time

max_forks_repo_name: QuantLaw/Measuring-Law-Over-Time


text:
\section{Related work}\label{sec:related_work}

\input{Y_other_animations}

One general purpose animation program is ANIMAL~\cite{2002-JVLC-Roessling,ANIMAL};
it provides the animator
with a rich menu
of elements common to many algorithms.
Steps in the animation are linked to steps in the pseudocode, a feature that
appears to be unique for Animal.
Though there is a large variety of options for creating interesting and
compelling animations,
it appears that the animations produced by the animator are passive.

Galles~\cite{Galles} is an animation tool with very
sophisticated creation options.
Primarily designed to be passive, it could conceivably, with a parser
for a graph input format and a mechanism to allow the user to view and
manipulate the input graph, be made interactive.
It suffers, however, from the fact that the
animator must navigate a complex Java-based interface with multiple classes.

Although secondary to its main purpose as a library of data structures and
algorithms,
LEDA~\cite{1999-LEDA-Mehlhorn} offers a graph window facility that can be
used to create animations of graph algorithms.
The documentation gives several examples and illustrates the rich functionality of
the drawing and visualization capability of graph windows.
Since LEDA is a general purpose, C++-based, programming language for
algorithms and data structures, it is easily augmented with extensions that
are integrated seamlessly with the core API; in this case, graph windows work
in concert with core graph functions and macros.
%%  (which are similar to, but
%% more sophisticated than, those in GDR).
Two major disadvantages of LEDA are (a)~it is a commercial product with
non-trivial licensing cost; and (b)~the windowing
system, at least in the last cost-free version, is based on X11 and hence not
portable.

Several online applets feature graph algorithm animation. Of these,
JAVENGA~\cite{JAVENGA} stands out. It is highly interactive. The drawing and
editing of
graphs is simple and intuitive, and graphs can be viewed in all three major
representations (drawing, adjacency matrix and adjacency list).
The variety of graph algorithms available is impressive:
breadth-first and depth-first search, topological sort, strongly connected
components, four shortest path algorithms, two minimum spanning tree
algorithms, and a network flows algorithm.
Animations can be run one step at a time with the option of moving backwards
or continuously with an adjustable number of milliseconds per step.
Javenga's main drawback is that the explorer is unable to save graphs for
future sessions, presumably an artifact of it being an applet.

The tool that probably comes closest to Galant is j-Alg~\cite{j-Alg};
it is highly interactive, has a relatively easy to use interface, and has sophisticated animations for a large variety of algorithms,
including \cmt{give partial list}.
In many ways its functionality, look and feel, and variety of animations
already implemented it far surpasses Galant in its current form.
The only drawback is that there is no readily available mechanism
for creating new animations.
New animations are typically developed as
student projects and require a fair amount of effort --- not surprising given
the sophistication of the results.

\cmt{Appears that there are several passive animation tool with sophisticated
creation mechanism --- almost like movie production.}

\cmt{Need to mention interactive Java Applets; they don't seem to work on my
  Mac -- must have at some point on the previous Mac}

AlgoViz~\cite{AlgoViz}
is a large catalog of algorithm animations, continually updated by
contributors who either submit new animations or comment on existing ones.
The animations listed are rated with respect to four categories:
lecture aid (roughly corresponding to passive), self study supplement (passive with
easy to use interface),
stand-alone (interactive),
and debugging aid (creative in a limited sense).
The perspective of most of the entries is classroom use with the role of the
animator implicit.
For example, several different animations constructed using Galles are posted.
Like any large repository with many contributors, AlgoViz is difficult to
monitor and
maintain: comments on the animations are not necessarily useful and some of the links are broken.

The OpenDSA project~\cite{%
2011-ProgramVisualization-Shaffer,2011-Koli-Shaffer,2012-SIGCSE-Fouh%
}
aims to create a textbook compilation of a variety of
(mostly passive) visualizations.

Earlier animation tools/systems include John Stasko's Xtango~\cite{Xtango},
SAMBA~\cite{SAMBA} and Polka~\cite{Polka,1992-TR_GIT-Stasko}, and, of course,
that of but
Bentley and Kernighan~\cite{1987-Animation-Bentley}.
SAMBA is especially notable for its emphasis on simplifying the creation of
animations so that students can easily accomplish it.
All of these suffer, however, from using old technology, requiring off-line creation
of problem instances and having no graph-algorithm specific implementations
or graph creation interfaces to offer.

% [Last modified: 2013 06 26 at 18:34:44 GMT]

max_stars_repo_name: mfms-ncsu/galant

max_stars_repo_licenses: Naumen Condor-1.1 MS-PL

max_issues_repo_name: mfms-ncsu/galant

max_issues_repo_licenses: Naumen Condor-1.1 MS-PL

max_forks_repo_name: mfms-ncsu/galant

max_forks_repo_licenses: Naumen Condor-1.1 MS-PL


text:
\documentclass[10pt,letterpaper]{article}
\usepackage[margin=1in]{geometry}
\usepackage{setspace}
\usepackage{fancyhdr}
\usepackage{lastpage}
\pagestyle{fancyplain}

% Put watermark on
% \usepackage{draftwatermark}
% \SetWatermarkText{Draft}
% \SetWatermarkScale{7}

\lhead{}
\chead{Central Massachusetts Amateur Radio Association}
\rhead{}
\lfoot{\texttt{https://github.com/mide/cmara-meeting-minutes/}}
\cfoot{}
\rfoot{Page \thepage\ of \pageref{LastPage}}

\begin{document}

\begin{center}
{\huge December 2016 Business Meeting}\\
\emph{of the}\\
{\Large Central Massachusetts Amateur Radio Association}\\
\emph{Submitted by Mark Ide \texttt{W1IDE}, Secretary}
\end{center}

\section{Meeting Called to Order}
The CMARA December 2016 business meeting was called to order on December 15, 2016 by CMARA president Bob Peloquin (\texttt{KB1VUA}) at 7:14 PM.

\section{Attendance}

\subsection{Officers Present}
\begin{tabular}{|l|l|l|c|}
  \hline
  \textbf{Position} & \textbf{Name}  & \textbf{Callsign} & \textbf{Present} \\ \hline
  President         & Bob Peloquin   & \texttt{KB1VUA}   & Yes \\
  Vice President    & Art Kass       & \texttt{WA1RCQ}   & Yes \\
  Secretary         & Mark Ide       & \texttt{W1IDE}    & Yes \\
  Treasurer         & Jim Singer     & \texttt{N1EKO}    & Yes \\
  Webmaster         & Lynn Glagowski & \texttt{WB1CCL}   & Yes \\
  \hline
\end{tabular}

\subsection{Board of Directors Present}
\begin{tabular}{|l|l|c|}
  \hline
  \textbf{Name}     & \textbf{Callsign} & \textbf{Present} \\ \hline
  Adrian Zeffert    & \texttt{AB2IX}    & Yes \\
  Harold Carlson    & \texttt{N1ZC}     & Yes \\
  Dick Jubinville   & \texttt{W1REJ}    & Yes \\
  Terry Glagowski   & \texttt{W1TR}     & Yes \\
  Randy Dore        & \texttt{W4FEB}    & Yes \\
  Johnathan Sherman & \texttt{WW2JS}    & Yes \\
  \hline
\end{tabular}

\subsection{Members Present}

\texttt{AB1MT},
\texttt{AB1YH},
\texttt{AB2IX},
\texttt{K1BML},
\texttt{K1RAU},
\texttt{KA3RLZ},
\texttt{KB1EZF},
\texttt{KB1LOU},
\texttt{KB1VUA},
\texttt{KB1VXH},
\texttt{KB1VXY},
\texttt{KC1ACX},
\texttt{KC1BHD},
\texttt{KC1ETB},
\texttt{KC1FPI},
\texttt{KC1GIB},
\texttt{KM1D},
\texttt{N1FSK},
\texttt{N1HTB},
\texttt{N1KWX},
\texttt{N1ZC},
\texttt{W1BNC},
\texttt{W1CAB},
\texttt{W1GD},
\texttt{W1IDE},
\texttt{W1PA},
\texttt{W1REJ},
\texttt{W1TR},
\texttt{W3DEC},
\texttt{W4FEB},
\texttt{WA1JXR},
\texttt{WA1MDD},
\texttt{WA1RCQ},
\texttt{WB1CCL},
\texttt{WW2JS}

\subsection{Guests \& Visitors}
\texttt{KB2SAE},
\texttt{KC1GSR},
\texttt{KC1GSS},
\texttt{KC1SGT},
\texttt{W1AAM},
\texttt{W1GJM},
\texttt{W1RVY},
Amanda G.

\noindent\\
\emph{(Note: If we haven't received your dues, you're considered a guest. If you feel this is a mistake, contact the club treasurer.)}

\section{Reports}

\subsection{Secretary's Report}
The secretary's report for November 2016 was voted in, as published, by verbal vote.

\newpage
\subsection{Treasurer's Report}
The treasurer's report for November 2016 was voted in, as read, by verbal vote.

\subsubsection{November 2016 Treasurer's Summary}
\noindent
\begin{tabular}{|l|r|}
  \hline
  Beginning Checking Balance & \texttt{\$4,678.10} \\
  Income: Membership Dues & \texttt{+\$165.00} \\
  Expense: Membership Badges & \texttt{-\$18.94} \\
  Expense: USPS Postage & \texttt{-\$2.62} \\
  Ending Checking Balance & \texttt{\$4,821.54} \\
  \hline
  \hline
  CD & \texttt{\$4,767.78} \\
  \hline
  \hline
  Repeater Fund (Maintain minimum \$500 in checking) & \texttt{\$910.00} \\
  \hline
  \hline
  Radio Donation Sales & \texttt{\$1,268.04} \\
  \hline
  \hline
  \textbf{Total Club Account} (Checking + CD) & \texttt{\$9,589.32} \\
  \hline
\end{tabular}

\subsection{Committee Reports}

\subsubsection{Membership Committee Report}
Membership is growing, which is good. There is nothing else to report.

\subsubsection{Repeater Trustees Report}
\begin{enumerate}
\item There is no new business to report.
\item We have reports of the repeater working all the way to Cape Cod, which is great news.
\end{enumerate}

\subsubsection{Field Day Committee Report}
\begin{enumerate}
\item We were in the top 10 in our category, and all of our points counted towards our score.
\end{enumerate}

\section{Old Business}
There was no old business tabled.

\section{New Business}

\subsection{New CMARA Members}
No new CMARA members were voted in.

\subsection{Other New Business}

December is the month in which we perorm our annual elections for officers and board members. A total of 41 members voted this evening and the results are as follow.
\begin{enumerate}
\item Office of President\\
\begin{tabular}{|l|l|l|l|l|}
\hline
\textbf{Vote Count} & \textbf{Percentage} & \textbf{Name} & \textbf{Callsign} & \textbf{Election Status} \\
\hline
41 Votes & 100\% & Robert Peloquin Jr. & \texttt{KB1VUA} & Elected \\
\hline
\end{tabular}
\item Office of Vice President\\
\begin{tabular}{|l|l|l|l|l|}
\hline
\textbf{Vote Count} & \textbf{Percentage} & \textbf{Name} & \textbf{Callsign} & \textbf{Election Status} \\
\hline
41 Votes & 100\% & Brian Loverro & \texttt{K1BML} & Elected \\
\hline
\end{tabular}
\item Office of Secretary\\
\begin{tabular}{|l|l|l|l|l|}
\hline
\textbf{Vote Count} & \textbf{Percentage} & \textbf{Name} & \textbf{Callsign} & \textbf{Election Status} \\
\hline
41 Votes & 100\% & Mark Ide, Jr. & \texttt{W1IDE} & Elected \\
\hline
\end{tabular}
\item Office of Treasurer\\
\begin{tabular}{|l|l|l|l|l|}
\hline
\textbf{Vote Count} & \textbf{Percentage} & \textbf{Name} & \textbf{Callsign} & \textbf{Election Status} \\
\hline
25 Votes & 61\% & James Singer & \texttt{N1EKO} & Elected \\
1 Vote & 2\% & Herbert Gilbert & \texttt{KC1GIB} & \\
1 Vote & 2\% & Randolph Dore & \texttt{W4FEB} & \\
1 Vote & 2\% & Dan Rau & \texttt{K1RAU} & \\
\hline
13 Votes & 33\% & \emph{(blank)} & &  \\
\hline
\end{tabular}
\item Office of Webmaster\\
\begin{tabular}{|l|l|l|l|l|}
\hline
\textbf{Vote Count} & \textbf{Percentage} & \textbf{Name} & \textbf{Callsign} & \textbf{Election Status} \\
\hline
40 Votes & 98\% & Linda Glagowski & \texttt{WB1CCL} & Elected \\
\hline
1 Vote & 2\% & \emph{(blank)} & &  \\
\hline
\end{tabular}
\item Board of Directors (Six Seats)\\
\begin{tabular}{|l|l|l|l|l|}
\hline % 246
\textbf{Vote Count} & \textbf{Percentage} & \textbf{Name} & \textbf{Callsign} & \textbf{Election Status} \\
\hline
41 Votes & 100\% & Greg Algieri & \texttt{WA1JXR} & Elected \\
40 Votes & 98\% & George Szarka, Jr. & \texttt{AB1MT} & Elected \\
40 Votes & 98\% & James Garner & \texttt{KC1BHD} & Elected \\
39 Votes & 95\% & Terry Glagowski & \texttt{W1TR} & Elected \\
39 Votes & 95\% & Johnathan Sherman & \texttt{WW2JS} & Elected \\
11 Votes & 27\% & Randolph Dore & \texttt{W4FEB} & Elected \\
9 Votes & 22\% & Adrian Zeffert & \texttt{AB2IX} &  \\
4 Votes & 11\% & Harold Carlson, Jr. & \texttt{N1ZC} & \\
3 Votes & 7\% & John Spencer & \texttt{WA1MDD} & \\
3 Votes & 7\% & Richard Jubinville & \texttt{W1REJ} & \\
3 Votes & 7\% & Eugene Bouchard & \texttt{N1KWX} & \\
1 Vote & 2\% & William Acito, Jr. & \texttt{W1PA} & \\
1 Vote & 2\% & Gerald Kersus & \texttt{W1GD} & \\
1 Vote & 2\% & Robert Peloquin Jr. & \texttt{KB1VUA} & \\
1 Vote & 2\% & Dan Rau & \texttt{K1RAU} & \\
\hline
10 Votes & 25\% & \emph{(blank)} & &  \\

\hline
\end{tabular}
\end{enumerate}

\section{For the Good of the Club}

\subsection{New Hams \& Upgrades}
No new hams nor hams with upgrades were present.

\subsection{Other News}
\begin{enumerate}
  \item John (\texttt{{WW2JS}}) gave custom made CMARA mugs to Sandy (\texttt{N1FSK}) and Bob (\texttt{KB1VUA}) for everything they've done for the club. Thank you John, Sandy and Bob.
\end{enumerate}

\section{Next Meeting}
The next meeting will be Thursday, January 19, 2017 at 7:00 PM. It will be located at the Oakdale United Methodist Church, 15 North Main Street, West Boylston, MA 01583.

\section{Meeting Adjourned}
The meeting was adjourned December 15, 2016 at 7:24 PM PM by CMARA president Bob Peloquin (\texttt{KB1VUA}).

\section{Post-Meeting Presentation}

We had the annual potluck dinner. Thanks to everyone who made this year yet another success!

\end{document}

max_stars_repo_name: cmara/meeting-minutes

max_issues_repo_name: cmara/meeting-minutes

max_forks_repo_name: cmara/meeting-minutes


text:
\section{Inverse Scattering Time Analysis}

We hace derived the inverse scattering time matrix element from previous section as follows
\begin{equation} \label{5.1}
  \begin{aligned}
    \qty(\frac{1}{\tau(\varepsilon,k_x)})^{ll'}_{N} =
    \frac { \eta_{imp}^2 L_x^2 \hbar V_{imp}}{\qty(eB)^2}
    \delta(\varepsilon - \varepsilon_{N})
    \int_{-\infty}^{\infty} d {k'}_x
    &
    J_l\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x])
    J_{l'}\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x]) \\
    & \times
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    {\chi}_{N}\qty(\frac{\hbar}{eB}\bar{k})
    {\chi}_{N}\qty(\frac{\hbar}{eB} \qty[{k'}_x - {k}_x - \bar{k}])|^2.
  \end{aligned}
\end{equation}

\noindent
The disorder in the system is not supposed to change the eigenenergies of the bare system, hence all off-diogonal elements of the self-energy were neglected. Thesefore we can consider only the central diagonal element (${l=l'=0}$) of the inverse scattering time matrix which has the largest contribution
\begin{equation} \label{5.2}
  \begin{aligned}
    \qty(\frac{1}{\tau(\varepsilon,k_x)})^{00}_{N} =
    \frac { \eta_{imp}^2 L_x^2 \hbar V_{imp}}{\qty(eB)^2}
    \delta(\varepsilon - \varepsilon_{N}) &
    \int_{-\infty}^{\infty} d {k'}_x \;
    J_0^2\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x])
    \\
    & \times
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    {\chi}_{N}\qty(\frac{\hbar}{eB}\bar{k})
    {\chi}_{N}\qty(\frac{\hbar}{eB} \qty[{k'}_x - {k}_x - \bar{k}])|^2.
  \end{aligned}
\end{equation}

% and introduce new variable as follows
% \begin{equation} \label{5.3}
%     y_1 = \frac{\hbar}{eB}[{k'}_x - k_x] \longrightarrow
%     d{k'}_x = \frac{eB}{\hbar}dy_1
% \end{equation}
% and
% \begin{equation} \label{5.4}
%     y_2 = \frac{\hbar}{eB}\bar{k} \longrightarrow
%     d\bar{k} = \frac{eB}{\hbar}dy_2
% \end{equation}
% then above equation modified to
% \begin{equation} \label{5.5}
%   \begin{aligned}
%     \qty(\frac{1}{\tau(\varepsilon,k_x)})^{ll}_{N} =
%     \frac { N_{imp}^2 A^2 \hbar V_{imp}}{16\pi^4 \qty(eB)^2}
%     \qty(\frac{eB}{\hbar})^3
%     \delta(\varepsilon - \varepsilon_{N}) &
%     \int_{-\infty}^{\infty} dy_1\;
%     J_l^2\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x])
%     \\
%     & \times
%     \qty|
%     \int_{-\infty}^{\infty} d\bar{k} \;
%     {\chi}_{n_{\beta}}\qty(\frac{\hbar}{eB}\bar{k})
%   \end{aligned}
% \end{equation}

% \noindent
% Lets consider how this expression change when we have turn off the dressing field ($E = 0$). Thesefore the inverse scattering time becomes valid for only $l=0$
% \begin{equation} \label{5.3}
%   \begin{aligned}
%     \qty(\frac{1}{\tau(\varepsilon,k_x)})^{00}_{N}\Bigg|_{E=0}  =
%     \frac { N_{imp}^2 A^2 \hbar V_{imp}}{16\pi^4 \qty(eB)^2}
%     \delta(\varepsilon - \varepsilon_{N})
%     \int_{-\infty}^{\infty} d {k'}_x \;
%     \qty|
%     \int_{-\infty}^{\infty} d\bar{k} \;
%     {\chi}_{N}\qty(\frac{\hbar}{eB}\bar{k})
%     {\chi}_{N}\qty(\frac{\hbar}{eB} \qty[{k'}_x - {k}_x - \bar{k}])|^2.
%   \end{aligned}
% \end{equation}

\noindent
Now we can introduce a new parameter with physical meaning of scatterin-induced broadening of the Landau level as follows
\begin{equation} \label{5.3}
  \Gamma^{00}_{N}(\varepsilon,k_x) \equiv \hbar \qty(\frac{1}{\tau(\varepsilon,k_x)})^{00}_{N}
\end{equation}
and this modify our previous expressing as
\begin{equation} \label{5.4}
  \begin{aligned}
    \Gamma^{00}_{N}(\varepsilon,k_x)  =
    \frac { \eta_{imp}^2 L_x^2 \hbar^2 V_{imp}}{\qty(eB)^2}
    \delta(\varepsilon - \varepsilon_{N}) &
    \int_{-\infty}^{\infty} d {k'}_x \;
    J_0^2\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x])
    \\
    & \times
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    {\chi}_{N}\qty(\frac{\hbar}{eB}\bar{k})
    {\chi}_{N}\qty(\frac{\hbar}{eB} \qty[{k'}_x - {k}_x - \bar{k}])|^2.
  \end{aligned}
\end{equation}
In addition, for the case of elastic scattering within the same Landau level, one can present the delta distribution of the energy using the same physical interpretation as follows
\begin{equation} \label{5.5}
  \delta(\varepsilon - \varepsilon_{N}) \approx
  \frac{1}{\pi \Gamma^{00}_{N}(\varepsilon,k_x)}
\end{equation}
and this leads to
\begin{equation} \label{5.6}
  \begin{aligned}
    \qty[\Gamma^{00}_{N}(\varepsilon,k_x)]^2  =
    \frac { \eta_{imp}^2 L_x^2 \hbar^2 V_{imp}}{\pi\qty(eB)^2}
    \int_{-\infty}^{\infty} d {k'}_x \;
    J_0^2\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x])
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    {\chi}_{N}\qty(\frac{\hbar}{eB}\bar{k})
    {\chi}_{N}\qty(\frac{\hbar}{eB} \qty[{k'}_x - {k}_x - \bar{k}])|^2.
  \end{aligned}
\end{equation}
and
\begin{equation} \label{5.7}
  \begin{aligned}
    \Gamma^{00}_{N}(\varepsilon,k_x)  =
    \qty[
    \frac { \eta_{imp}^2 L_x^2 \hbar^2 V_{imp}}{\pi\qty(eB)^2}
    \int_{-\infty}^{\infty} d {k'}_x \;
    J_0^2\qty(\frac{g\hbar}{eB}[{k}_x - {k'}_x])
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    {\chi}_{N}\qty(\frac{\hbar}{eB}\bar{k})
    {\chi}_{N}\qty(\frac{\hbar}{eB} \qty[{k'}_x - {k}_x - \bar{k}])|^2
    ]^{-1/2}.
  \end{aligned}
\end{equation}

\noindent
This can be write in more compact form as follows
\begin{equation} \label{5.8}
  \begin{aligned}
    \Gamma^{00}_{N}(\varepsilon,k_x)  =
    \qty[
    \frac { \eta_{imp}^2 L_x^2 \hbar^2 V_{imp}}{\pi\qty(eB)^2}
    \int_{-\infty}^{\infty} d {k'}_x \;
    J_0^2\qty(g\sigma[{k}_x - {k'}_x])
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    {\chi}_{N}\qty(\sigma\bar{k})
    {\chi}_{N}\qty(\sigma\qty[{k'}_x - {k}_x - \bar{k}])|^2
    ]^{-1/2}
  \end{aligned}
\end{equation}
where
\begin{equation} \label{5.9}
    g = \frac{eE\omega_0^2}{\hbar\omega(\omega_0^2 - \omega^2)} \quad\quad
    \sigma = \frac{\hbar}{eB}
\end{equation}
and
\begin{equation} \label{5.10}
  \chi_N(x) = \frac{\sqrt{\kappa}}{\sqrt{2^{N}N!\sqrt{\pi}}}
  \exp(-\frac{\kappa^2 x^2}{2})
  \mathcal{H}_N\qty(\kappa x) \quad \text{with} \quad
  \kappa \equiv \sqrt{\frac{m_e \omega_0}{\hbar}}.
\end{equation}

\noindent
Using above definition we can identify Gauss-Hermite functions ($\vartheta_N$) and this can re-write as
\begin{equation} \label{5.11}
  \begin{aligned}
    \Gamma^{00}_{N}(\varepsilon,k_x)  =
    \qty[
    \frac { \eta_{imp}^2 L_x^2 \hbar^2 V_{imp}}{\pi\qty(eB)^2}
    \int_{-\infty}^{\infty} d {k'}_x \;
    J_0^2\qty(g\sigma[{k}_x - {k'}_x])
    \kappa^4
    \qty|
    \int_{-\infty}^{\infty} d\bar{k} \;
    \vartheta_{N}\qty(\sigma\kappa\bar{k})
    \vartheta_{N}\qty(\sigma\kappa\qty[{k'}_x - {k}_x - \bar{k}])|^2
    ]^{-1/2}
  \end{aligned}
\end{equation}
where
\begin{equation} \label{5.12}
  \vartheta_N(x) = \frac{1}{\sqrt{2^{N}N!\sqrt{\pi}}}
  \exp(-\frac{x^2}{2})
  \mathcal{H}_N\qty(x) \quad,\quad
  \kappa^2 = \frac{m_e\omega_0}{\hbar} = \frac{eB}{\hbar}
\end{equation}
and this will be simplified to (with parmater change $k'_x \rightarrow k_1$ and $\bar{k}_x \rightarrow k_2$)
\begin{equation} \label{5.13}
  \begin{aligned}
    \Gamma^{00}_{N}(\varepsilon,k_x)  =
    \eta
    \qty[
    \int_{-\infty}^{\infty} d {k}_1 \;
    J_0^2\qty(\lambda_1[{k}_x - {k}_1])
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(\lambda_2 k_2)
    \tilde{\chi}_{N}\qty(\lambda_2 \qty[{k}_1 - {k}_2 - {k}_x])|^2
    ]^{-1/2}
  \end{aligned}
\end{equation}
where
\begin{equation} \label{5.14}
    \eta = \eta_{imp} L_x \qty[\frac { V_{imp}}{\pi}]^{1/2} \quad,\quad
    \lambda_1 = g\sigma \quad,\quad
    \lambda_2 = \sigma \kappa.
\end{equation}
\noindent
Now we can analyze the behaviour of the normalized $N$-th Landau level for broadening as follows
\begin{equation} \label{5.15}
    \Lambda_N(k_x) \equiv
    \frac{\qty(1/\tau)^{00}_{N}}{\qty(1/\tau)^{00}_{0}\big|_{E=0}} =
    \frac{\Gamma^{00}_{N}(\varepsilon,k_x)}{\Gamma^{00}_{0}(\varepsilon,k_x)\big|_{E=0}}
\end{equation}
and this will be
\begin{equation} \label{5.16}
    \Lambda_N (k_x) =
    \qty[
    \frac
    {\int_{-\infty}^{\infty} d {k}_1 \;
    J_0^2\qty(\lambda_1[{k}_x - {k}_1])
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(\lambda_2 k_2)
    \tilde{\chi}_{N}\qty(\lambda_2 \qty[{k}_1 - {k}_2 - {k}_x])|^2}
    {\int_{-\infty}^{\infty} d {k}_1 \;
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{0}\qty(\lambda_2 k_2)
    \tilde{\chi}_{0}\qty(\lambda_2 \qty[{k}_1 - {k}_2 - {k}_x])|^2}
    ]^{1/2}.
\end{equation}

\noindent
Lets calculate these constants for GaAs-based quantum well with following given physical constants and system external paramters.

\begin{table}[ht!]
\begin{center}
\begin{tabular}{ |l|c|l| }
 \hline
 \textbf{Physical constant name} & \textbf{Symbol} & \textbf{Value in SI-units} \\ [0.5ex] \hline\hline
 Electron charge  & e & $1.602\times10^{-19} \;\text{C}$ \\ \hline
 Electron mass & $m$ & $9.109\times10^{-31}\; \text{kg}$ \\ \hline
 Reduced Planck's constant &  $\hbar$ & $1.054\times10^{-34} \;\text{kg}\text{m}^2\text{s}^{-1}$ \\ \hline
 Speed of light & $c$ & $2.998\times10^8\; \text{ms}^{-1}$ \\ \hline
 Vacuum permittivity & $\varepsilon_0$ & $8.854\times10^{-12}\; \text{C}^{2}\text{s}^2\text{kg}^{-1}\text{m}^{-3}$ \\ \hline
\end{tabular}
\caption {\label{tab:5.1}Physical constant values in SI-units}
\end{center}
\end{table}

\begin{table}[ht!]
\begin{center}
\begin{tabular}{ |l|c|l| }
 \hline
 \textbf{External paramter name} & \textbf{Symbol} & \textbf{Value in SI-units} \\ [0.5ex] \hline\hline
 Average intensity  & $I$ & $\tilde{I} \times 100\;\text{W}/\text{cm}^{2} = \tilde{I}\times10^6\;\text{W}/\text{m}^{2}$ \\ \hline
 Magnetic field & $B$ & $1.2\;\text{T}$ \\ \hline
 Driving frequency & $\omega$ & $2\times10^{12} \;\text{rad}\text{s}^{-1}$ \\ \hline
 Effective mass &  $m_e$ & $0.071\times m = 6.467 \times10^{-32} \; \text{kg}$ \\ \hline
\end{tabular}
\caption {\label{tab:5.2}System external paramter values. (${\tilde{I}}$ is a dimentionless value.)}
\end{center}
\end{table}

\noindent
Therfore we can calculate following values
\begin{equation} \label{5.17}
  \omega_0 = \frac{eB}{m_e} = 2.97265 \times 10^{12}\; \text{s}^{-1}
\end{equation}
\begin{equation} \label{5.18}
  \sigma = \frac{\hbar}{eB} = 5.4851 \times 10^{-16}\; \text{m}^{2}
\end{equation}
\begin{equation} \label{5.19}
  E = \sqrt{\frac{2I}{c\varepsilon_0}}
\end{equation}
\begin{equation} \label{5.20}
  g = \frac{eE\omega_0^2}{\hbar\omega(\omega_0^2 - \omega^2)}
  = \frac{e\omega_0^2}{\hbar\omega(\omega_0^2 - \omega^2)}  \sqrt{\frac{2I}{c\varepsilon_0}}
  = 3.80958 \times 10^{7}\times \sqrt{\tilde{I}}\; \text{m}^{-1}
\end{equation}
\begin{equation} \label{5.21}
  \kappa = \sqrt{\frac{m_e \omega_0}{\hbar}}
  = 4.2698 \times 10^{7}\; \text{m}^{-1}
\end{equation}
Since
\begin{equation} \label{5.22}
  \lambda_1 = g\sigma
  = 2.08959 \times 10^{-8} \times \sqrt{\tilde{I}}\; \text{m} \quad \text{and} \quad
  \lambda_2 = \kappa\sigma = 2.34203 \times 10^{-8}\; \text{m}
\end{equation}
we can choose our integral dummy variables $k_1$, $k_2$ and momentum variable $k_x$ are in one range as follows
\begin{equation} \label{5.23}
  k_x,k_1,k_2 \approx 10^{8}\; \text{m}^{-1}
\end{equation}

\noindent
Using above values we can re-write the normalized energy broadening of the $N$-th Landau level as
\begin{equation} \label{5.24}
    \Lambda_N (k_x) =
    \qty[
    \frac
    {\int_{-\infty}^{\infty} d {k}_1 \;
    J_0^2\qty(2.090\sqrt{\tilde{I}}\times[{k}_x - {k}_1])
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(2.342 \times k_2)
    \tilde{\chi}_{N}\qty(2.342 \times \qty[{k}_1 - {k}_2 - {k}_x])|^2}
    {\int_{-\infty}^{\infty} d {k}_1 \;
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{0}\qty(2.342 \times k_2)
    \tilde{\chi}_{0}\qty(2.342 \times \qty[{k}_1 - {k}_2 - {k}_x])|^2}
    ]^{1/2}.
\end{equation}
\begin{figure}[ht!]
  \centering
  \includegraphics[scale=0.7]{figures/fig51.pdf}
  \caption{Normalized energy band broadening with $k_x$ for different Landau levels ($N=0,1,2,3,4$) for $\tilde{I}=1$.}
  \label{fig:5.1}
\end{figure}

\noindent
To check the variability of this expression with $k_x$ value we check it with a constant intensity. Therefore let $\tilde{I}=1$ and we can re-write above as
\begin{equation} \label{5.25}
    \Lambda_N (k_x) =
    \qty[
    \frac
    {\int_{-\infty}^{\infty} d {k}_1 \;
    J_0^2\qty(2.090\times[{k}_x - {k}_1])
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(2.342 \times k_2)
    \tilde{\chi}_{N}\qty(2.342 \times \qty[{k}_1 - {k}_2 - {k}_x])|^2}
    {\int_{-\infty}^{\infty} d {k}_1 \;
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{0}\qty(2.342 \times k_2)
    \tilde{\chi}_{0}\qty(2.342 \times \qty[{k}_1 - {k}_2 - {k}_x])|^2}
    ]^{1/2}.
\end{equation}
then introduce new variable
\begin{equation} \label{5.26}
  k_1 - k_x = \tilde{k} \quad \longrightarrow \quad dk_1 = d\tilde{k}
\end{equation}
and since $k_1$ can vary between all the range we can modify our Eq. \eqref{5.25} as follows
\begin{equation} \label{5.27}
    \Lambda_N (k_x) =
    \qty[
    \frac
    {\int_{-\infty}^{\infty} d \tilde{k} \;
    J_0^2\qty(2.090\times \tilde{k})
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(2.342 \times k_2)
    \tilde{\chi}_{N}\qty(2.342 \times \qty[\tilde{k}- {k}_2])|^2}
    {\int_{-\infty}^{\infty} d \tilde{k} \;
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{0}\qty(2.342 \times k_2)
    \tilde{\chi}_{0}\qty(2.342 \times \qty[\tilde{k} - {k}_2])|^2}
    ]^{1/2}
\end{equation}
and letting $\tilde{k} = k_1$ we can find that this is do not depend on the value of $k_x$. Therefore
\begin{equation} \label{5.28}
    \Lambda_N =
    \qty[
    \frac
    {\int_{-\infty}^{\infty} d k_1 \;
    J_0^2\qty(2.090\times k_1)
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(2.342 \times k_2)
    \tilde{\chi}_{N}\qty(2.342 \times \qty[k_1 - {k}_2])|^2}
    {\int_{-\infty}^{\infty} d k_1\;
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{0}\qty(2.342 \times k_2)
    \tilde{\chi}_{0}\qty(2.342 \times \qty[k_1 - {k}_2])|^2}
    ]^{1/2}
\end{equation}

\noindent
Now we can draw the values of $\Lambda_N$ agaist $k_x$ to compare the differese of each Landau level's normalized energy band broadening as given in Figure \ref{fig:5.1}.

\noindent
Now let's check how the $\Lambda_N$ value change with the applied dressing field's intensity. Using following equation we can identify $\Lambda_N$ dependency on dressing field's intensity as given in Figure \ref{fig:5.2}.
\begin{equation} \label{5.29}
    \Lambda_N  =
    \qty[
    \frac
    {\int_{-\infty}^{\infty} d {k}_1 \;
    J_0^2\qty(2.090\sqrt{\tilde{I}}\times{k}_1)
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{N}\qty(2.342 \times k_2)
    \tilde{\chi}_{N}\qty(2.342 \times \qty[{k}_1 - {k}_2])|^2}
    {\int_{-\infty}^{\infty} d {k}_1 \;
    \qty|
    \int_{-\infty}^{\infty} d{k}_2 \;
    \tilde{\chi}_{0}\qty(2.342 \times k_2)
    \tilde{\chi}_{0}\qty(2.342 \times \qty[{k}_1 - {k}_2])|^2}
    ]^{1/2}.
\end{equation}

\begin{figure}[ht!]
  \centering
  \includegraphics[scale=0.6]{figures/fig52.pdf}
  \caption{Normalized energy band broadening with $\tilde{I}$ for different Landau levels.}
  \label{fig:5.2}
\end{figure}

\noindent
Here we can identify that we can change the each Landau level normalized energy broadening value using apllied electromagnetic field. When the applied field's intensity increase the energy broadening gets reduced which make changes in conductivity.

\noindent
To make comparison we can select the experiment parameters from previous analysis on transverse conductivity in [*Ref: Akira Endo and Naomichi Hantno]. In this study we have assumed that the broadening of Landau levels are same and the value for $\Gamma_N$ non-existing dressing field is $0.24\;\text{me}V$. Therefore in our study for the comparison we can assume that the least Landau level broadening has this value.
\begin{equation} \label{5.30}
  \Gamma^{00}_{N=0}\big|_{E=0} = 0.24 \;\text{meV}
\end{equation}

\noindent
Then using the calculated normalized broadening relations for each Landu levels, we can evaluate the energy band broadening values as follows
\begin{equation} \label{5.31}
  \Gamma^{00}_{N} = \Lambda_N \times \Gamma^{00}_{N=0}\big|_{E=0}.
\end{equation}
Therfore, the energy band broadening for Landau level with dressing field can be calculate as
\begin{equation} \label{5.32}
  \Gamma^{00}_{N} = \Lambda_N \times \Gamma^{00}_{N=0}\big|_{E=0}.
\end{equation}
and
\begin{equation} \label{5.33}
  \Gamma^{00}_{N} = 0.24 \times \Lambda_N  \;\text{meV}.
\end{equation}
\begin{equation} \label{5.34}
  \Gamma^{00}_{N}(\tilde{I}) = 0.24 \times
  \qty[
  \frac
  {\int_{-\infty}^{\infty} d {k}_1 \;
  J_0^2\qty(2.090\sqrt{\tilde{I}}\times{k}_1)
  \qty|
  \int_{-\infty}^{\infty} d{k}_2 \;
  \tilde{\chi}_{N}\qty(2.342 \times k_2)
  \tilde{\chi}_{N}\qty(2.342 \times \qty[{k}_1 - {k}_2])|^2}
  {\int_{-\infty}^{\infty} d {k}_1 \;
  \qty|
  \int_{-\infty}^{\infty} d{k}_2 \;
  \tilde{\chi}_{0}\qty(2.342 \times k_2)
  \tilde{\chi}_{0}\qty(2.342 \times \qty[{k}_1 - {k}_2])|^2}
  ]^{1/2} \text{meV}.
\end{equation}

xx


text:
\chapter{State of the Art in Procedural Modeling}
\label{sec:relatedwork}

%plants

\section{Plants and Trees}
Algorithmic Beauty of Plants by Lindenmayer and Przemyslaw \citep{PrzemyslawAlgoBeauty} is the first complete work discussing the generation of plant geometry using procedural methods such as L-systems and fractals. To model and visualise realistic ecosystems, Przemyslaw extended the l-systems concept to a system which allowed communication between systems (open l-systems \citep{PrzemyslawPlants} \citep{Deussen98}). Visual editing of procedural plants models is discussed in \citet{interactivebonsai}.

%road networks
\section{Road Networks}
The foundation for procedural city and building modeling was provided by Parish and Muller \citet{Parish01} in their paper \emph{"Procedural Modeling of Cities"}. The main contribution of this paper is the use of extended L-systems for the generation of city roadmaps. They also propose a method for the texturing of facades. An intuitive editing approach for road networks with the use of tensor fields and bush techniques is presented by Chen et al. \citet{Chen08}.

%building architecture
\section{Architecture}
An attempt was made to use L-systems for the creation of buildings \citet{Parish01}, however this did not prove to be effective. L-systems are designed to handle growth-like processes, it has been acknowledged that the construction process of a building is not a growth like process. Instead, building construction is better expressed by series of partitioning steps. These partitioning steps can be described by another kind of rewriting grammar called \emph{set grammar}. In \citet{Wonka03} Wonka presents a method for the automatic creation of building using such grammar systems. In this work Wonka introduces the idea of a specialized type of set grammar called \emph{split grammar} which operates on shapes. In \citet{Muller06} the split rules from the split grammar concept are defined in a grammar system called \emph{CGA Shape}, which was the first procedural system for the creation of detailed buildings with consistent mass
models. The process of creating a ruleset in CGA shape for a specific type of building is not straightforward and requires a trained expert. Lipp et al. \citet{Lipp08} introduce a visual method for the editing of the CGA Shape grammar for procedural architecture to simplify the rule building process.

\section{Procedural Game Worlds}
%content here%

max_stars_repo_name: Estevo-Aleixo/dynamicstructures

max_issues_repo_name: Estevo-Aleixo/dynamicstructures

max_forks_repo_name: Estevo-Aleixo/dynamicstructures


text:
\subsection{Parameter sharing}

Parameters share the same value and are trained together.

max_stars_repo_name: adamdboult/nodeHomePage

max_issues_repo_name: adamdboult/nodeHomePage

max_forks_repo_name: adamdboult/nodeHomePage


text:
% !TeX spellcheck = en_GB
\documentclass[a4paper,fleqn]{report}

\usepackage{docStyle}

\lstset{language=Bash}

\begin{document}

	\pagestyle{MyStyle}

	\begin{titlepage}
		\centering
		\null
		\vspace{5cm}

		{\huge\bfseries MANUAL\par}
		\vspace{1.5cm}
		\includegraphics[width=0.5\linewidth]{images/prompt.png}
		\vfill

		{\Large\itshape Matthijs Lasure\par}

		\vspace{1.5cm}

		% Bottom of the page
		{\large 2016\par}

	\end{titlepage}

	\tableofcontents

	\part{Quick start}
	\input{tex/quickstart}

	\part{Options etc}
	\chapter{MonteCarlo}
	\input{tex/files}
	\chapter{Getting converted: the ConvertDump utility}\label{chap:convertdump}
	\input{tex/convertDump}

	\part{Files}

	\part{Misc}
	\chapter{Misc}

	\newpage
	\begin{spacing}{0.75}
		\addcontentsline{toc}{chapter}{Referenties}
		%\footnotesize
		\label{Referenties}
		\clearpage
		\renewcommand{\bibname}{Referenties}
		\bibliography{bachelorthesis}
	\end{spacing}

\end{document}

max_stars_repo_name: MatthijsLasure/documentation

max_issues_repo_name: MatthijsLasure/documentation

max_forks_repo_name: MatthijsLasure/documentation